Ask Your Question
0

i can't run instance

asked 2019-02-06 04:00:02 -0600

erchad gravatar image

i have already create instance, but when i want to run it, at horizon it come error :

Error: Failed to perform requested operation on instance "a", the instance has an error status: Please try again later [Error: Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance 42ad9bb0-8975-43a2-86d9-6101c0988925.].

please tell me what is the problem i have already read at http://google.com, and he said its hardware problem :(

edit retag flag offensive close merge delete

Comments

Please share logs from nova-compute as well

Deepa gravatar imageDeepa ( 2019-02-06 04:17:05 -0600 )edit

The error means that Nova found a compute node to run the instance, but it could not start it. You find more information in the nova-compute log, as Deepa says, but possibly also the nova-scheduler log.

Bernd Bausch gravatar imageBernd Bausch ( 2019-02-06 05:26:12 -0600 )edit

Here is nova-compute log : 

2019-02-06 15:48:24.427 16218 INFO nova.compute.resource_tracker [req-9c0c44d8-2f4b-4914-9bd4-57c8ffd682b3 - - - - -] Final resource view: name=compute phys_ram=23981MB used_ram=512MB phys_disk=457GB used_disk=0GB total_vcpus=8 used_vcpus=0 pci_stats=[]
erchad gravatar imageerchad ( 2019-02-06 09:50:46 -0600 )edit

And there is no log on nova-scheduler, but i see this on nova-conductor.log :

Build of instance 42ad9bb0-8975-43a2-86d9-6101c0988925 was re-scheduled: invalid argument: could not find capabilities for domaintype=kvm \n']
erchad gravatar imageerchad ( 2019-02-06 09:52:10 -0600 )edit
add a comment

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-02-06 18:24:15 -0600

Bernd Bausch gravatar image

updated 2019-02-06 18:25:22 -0600

I can't believe that you have no nova-scheduler log at all, and that your other logs only contain one message each.

In any case, this is obviously a misconfiguration. Have a look at nova.conf on the compute node(s): In the [libvirt] section, you will find a setting named virt_type. Correct it to be kvm instead of kvm \n.

edit flag offensive delete link more

Comments

1

i have already fixed this problem, the problem is because i haven't enable the virtualization system on BIOS

erchad gravatar imageerchad ( 2019-02-06 22:06:22 -0600 )edit
add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2019-02-06 04:00:02 -0600

Seen: 324 times

Last updated: Feb 06 '19

Related questions

Dedicated novnc proxy server

Horizon requirements

Snapshots stay in queued status

Injecting admin password with horizon

Add autocomplete tag to login form

create flavor with any user from dashboard

testing horizon with curl

cannot create image

Unable to launch an instance

Exception tuples