Ask Your Question
0

Failing to create VM - Error code 500

asked 2016-07-08 10:10:22 -0500

centenor gravatar image

updated 2016-07-10 16:09:56 -0500

Hello everyone,

I am new to OpenStack and am running into an issue with creating VM's using the sample CirrOS that is included in the install. We have Horizon up and running and the flavor that we are using is an m1.tiny so I don't believe it's a resource issue on our compute node. Also, we are running OpenStack Liberty

The error reads - Build of instance e7c95f2b-0234-41cc-938b-79921f0add59 aborted: Could not clean up failed build, not rescheduling.

It's not complaining about not finding a host or lack of resources so I am not really sure what is causing this error. I've tried looking through different nova logs and have run nova service-list on the controller and everything looks okay from that end.

Are there other commands that I am unaware of that we should try or something in the logs that I'm not noticing? Let me know if you need me to post any specific logs on here, not sure which one to post

One reoccuring error that I was able to find was this in the nova-compute log when the instance fails to create

ConnectionRefused: Unable to establish connection to http://127.0.0.1:9696/v2.0/extensions.json (http://127.0.0.1:9696/v2.0/extensions...)

Keystone endpoint list -

+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------------------------+
| ID                               | Region    | Service Name | Service Type | Enabled | Interface | URL                                        |
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------------------------+
| 156835a7362c41f5bfed651ada4bdab6 | RegionOne | neutron      | network      | True    | admin     | http://serenity:9696                       |
| 17827c13ee154fd887ff350466ae10df | RegionOne | cinderv2     | volumev2     | True    | internal  | http://serenity:8776/v2/%(tenant_id)s      |
| 5d11a2b46ed84391b36cb55deb648906 | RegionOne | keystone     | identity     | True    | public    | http://serenity:5000/v2.0                  |
| 6633beca33574cc2beddacbfc2d7ee91 | RegionOne | nova         | compute      | True    | internal  | http://serenity:8774/v2/%(tenant_id)s      |
| 6af6272c87d4424c898a33987ef9f97e | RegionOne | cinderv2     | volumev2     | True    | admin     | http://serenity:8776/v2/%(tenant_id)s      |
| 78da260fafe04e8d82acd49f09e71b45 | RegionOne | glance       | image        | True    | public    | http://serenity:9292                       |
| 7da9dcf6ec7a447880489d399a17c1b9 | RegionOne | swift        | object-store | True    | public    | http://serenity:8080/v1/AUTH_%(tenant_id)s |
| 869899a4572047b1b348dc87f67b96a4 | RegionOne | swift        | object-store | True    | internal  | http://serenity:8080/v1/AUTH_%(tenant_id)s |
| 887aef20ce25428a87865dad02d76a06 | RegionOne | neutron      | network      | True    | public    | http://serenity:9696                       |
| 8d6c19e384c14001b749537489627f28 | RegionOne | nova         | compute      | True    | admin     | http://serenity:8774/v2/%(tenant_id)s      |
| 969487b56eca478381b09b3775d1d1e6 | RegionOne | glance       | image        | True    | internal  | http://serenity:9292                       |
| a0c294ea26004d72943bed6fe024cd0b | RegionOne | cinderv2     | volumev2     | True    | public    | http://serenity:8776/v2/%(tenant_id)s      |
| a7a9e2601ddc4080b939de7177ea16aa | RegionOne | cinder       | volume       | True    | internal  | http://serenity:8776/v1/%(tenant_id)s      |
| bdde4307754a41b6a19e1d75e8d4c6a8 | RegionOne | cinder       | volume       | True    | public    | http://controller:8776/v1/%(tenant_id)s    |
| be5297ae78a8455d9674c8965bbfa791 | RegionOne | neutron      | network      | True    | internal  | http://serenity:9696                       |
| c2d4abb7f6d94a10934675d6acb85fd2 | RegionOne | keystone     | identity     | True    | internal  | http://serenity:5000/v2.0                  |
| cc24a5e20abb49d7aa884dc7b79b60bd | RegionOne | nova         | compute      | True    | public    | http://serenity:8774/v2/%(tenant_id)s      |
| db6887cbeb0f44819f98fd983f1dacb8 | RegionOne | swift        | object-store | True    | admin     | http://serenity:8080/v1                    |
| ddcac1edc0954861a458538cc44773e9 | RegionOne | cinder       | volume       | True    | public    | http://serenity:8776/v1/%(tenant_id)s      |
| e2bd2c034c7c48238ce99188d6fa8a3d | RegionOne | cinder       | volume       | True    | admin     | http://serenity:8776/v1/%(tenant_id)s      |
| eef569081feb4543a0a16d0f780d636e | RegionOne | keystone     | identity     | True    | admin     | http://serenity:5000/v2.0                  |
| fad5ec4eaabb4bb5a7b6245acd1efa7c | RegionOne | glance       | image        | True    | admin     | http://serenity:9292                       |
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------------------------+

Couple of lines from neutron server log. They seem to be okay to me, but I can't spin a VM in the public or private subnet.

2016-07-10 16 ...
(more)
edit retag flag offensive close merge delete

Comments

Check the log file /var/log/neutron/server.log to confirm neutron startup and view more information on failure. Port 9696 belongs to neutron by default.

barry.davis gravatar imagebarry.davis ( 2016-07-09 11:12:30 -0500 )edit

I checked the neutron server.log & everything seems good there. I'm not seeing any errors. Just the occasional accepted logs and network timeouts

centenor gravatar imagecentenor ( 2016-07-10 16:02:50 -0500 )edit

The connection request does not match the endpoint. Change the url in section [neutron] in nova.conf on compute node to http://serenity:9696.

barry.davis gravatar imagebarry.davis ( 2016-07-10 18:29:32 -0500 )edit

Just double checked the nova.conf file on the controller and everything seems good. The url points to http://serenity:9696 & auth_url points to http://serenity:35357. The guide doesn't go over setting those options on the compute node for nova.conf on there

centenor gravatar imagecentenor ( 2016-07-10 21:57:37 -0500 )edit

Found the issue! The [neutron] section in nova.conf wasn't configured on the compute node so it kept causing that issue

centenor gravatar imagecentenor ( 2016-07-10 22:49:39 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
1

answered 2016-07-10 22:49:12 -0500

centenor gravatar image

I was able to figure out the issue thanks to some help! The solution to this issue was that the [neutron] section was only configured in the controller. It needs to be configured on both controller & compute to work properly so that the compute node knows where to authenticate to. Since it wasn't set it kept trying to authenticate to itself and failing on building a VM.

edit flag offensive delete link more

Comments

Just to add here: I had the same problem, but my compute node had the [neutron] section. However, I didn't realize that my second compute node also needed it. Nothing was working without the second compute also having it. Once I added that section to compute2:/etc/nova/nova.conf things were fine.

Esche gravatar imageEsche ( 2018-06-06 15:41:14 -0500 )edit
0

answered 2016-07-10 09:16:57 -0500

Please check keystone endpoints..

edit flag offensive delete link more

Comments

Keystone endpoints seem correct from my end. Attaching image to original post

centenor gravatar imagecentenor ( 2016-07-10 16:03:11 -0500 )edit

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

Stats

Asked: 2016-07-08 10:10:22 -0500

Seen: 1,589 times

Last updated: Jul 10 '16