Unable to launch Centos/CirrOS instance

Bug #1758112 reported by Ravi Tandon
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

Whenever I try to launch an instance (Centos or CirrOS), it fails with an Error

fault | {"message": "Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance 1f2bdbed-4a34-4ca3-93ed-5a8e0245609e.", "code": 500, "details": " File \"/usr/lib/python2.7/site-packages/nova/conductor/manager.py\", line 580, in build_instances

nova show CirrOS-2
+--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Property | Value |
+--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-SRV-ATTR:host | - |
| OS-EXT-SRV-ATTR:hostname | cirros-2 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | - |
| OS-EXT-SRV-ATTR:instance_name | instance-00000008 |
| OS-EXT-SRV-ATTR:kernel_id | |
| OS-EXT-SRV-ATTR:launch_index | 0 |
| OS-EXT-SRV-ATTR:ramdisk_id | |
| OS-EXT-SRV-ATTR:reservation_id | r-qrjz6933 |
| OS-EXT-SRV-ATTR:root_device_name | /dev/vda |
| OS-EXT-SRV-ATTR:user_data | - |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | - |
| OS-EXT-STS:vm_state | error |
| OS-SRV-USG:launched_at | - |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2018-03-22T16:55:31Z |
| description | CirrOS-2 |
| fault | {"message": "Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance 1f2bdbed-4a34-4ca3-93ed-5a8e0245609e.", "code": 500, "details": " File \"/usr/lib/python2.7/site-packages/nova/conductor/manager.py\", line 580, in build_instances |
| | raise exception.MaxRetriesExceeded(reason=msg) |
| | ", "created": "2018-03-22T16:55:46Z"} |
| flavor:disk | 1 |
| flavor:ephemeral | 0 |
| flavor:extra_specs | {} |
| flavor:original_name | m1.tiny |
| flavor:ram | 512 |
| flavor:swap | 0 |
| flavor:vcpus | 1 |
| hostId | |
| host_status | |
| id | 1f2bdbed-4a34-4ca3-93ed-5a8e0245609e |
| image | CirrOS (46c0cbff-2e40-4913-b021-bf6b82a188b9) |
| key_name | MyOpenstack |
| locked | False |
| metadata | {} |
| name | CirrOS-2 |
| os-extended-volumes:volumes_attached | [] |
| status | ERROR |
| tags | [] |
| tenant_id | a8828be48cd546ceaaddf379718c2b7b |
| updated | 2018-03-22T16:55:46Z |
| user_id | 6818b527adb8490386c921aaed1be1aa |

Please help to resolve the issue.

affects: neutron → nova
Revision history for this message
p.cipriano (ctpeter) wrote :

Same with me.

Error: Failed to perform requested operation on instance "test", 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 5bc74b2c-03b5-4be5-96dc-b60941b64dce.].

Release: "queens"
OS : CENTOS
Install_type : source

Revision history for this message
Matt Riedemann (mriedem) wrote :

There are likely failures in the nova-compute and/or nova-conductor logs, you would need to dig through those logs (or attach them) to help diagnose the reason for the build failures.

Changed in nova:
status: New → Invalid
Revision history for this message
Thaps (thaps) wrote :

I am facing same error, have resolved the issue? if yes let me know.

Revision history for this message
Ravi Tandon (ravi-100) wrote : Re: [Bug 1758112] Re: Unable to launch Centos/CirrOS instance
Download full text (6.4 KiB)

Not yet.

But I believe this error is related to resources available on the server.
I am awaiting my new server with 40 cores, earlier I was trying on a VM
with just 8 cores
and 16 GB RAM.

Whats the configuration of the server on which you have installed
openstack?

On Fri, Jul 6, 2018 at 5:31 PM Thaps <email address hidden> wrote:

> I am facing same error, have resolved the issue? if yes let me know.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758112
>
> Title:
> Unable to launch Centos/CirrOS instance
>
> Status in OpenStack Compute (nova):
> Invalid
>
> Bug description:
> Whenever I try to launch an instance (Centos or CirrOS), it fails with
> an Error
>
>
> fault | {"message": "Exceeded maximum
> number of retries. Exhausted all hosts available for retrying build
> failures for instance 1f2bdbed-4a34-4ca3-93ed-5a8e0245609e.", "code": 500,
> "details": " File
> \"/usr/lib/python2.7/site-packages/nova/conductor/manager.py\", line 580,
> in build_instances
>
>
> nova show CirrOS-2
>
> +--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
> | Property | Value
>
>
>
> |
>
> +--------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
> | OS-DCF:diskConfig | MANUAL
>
>
>
> |
> | OS-EXT-AZ:availability_zone | nova
>
>
>
> |
> | OS-EXT-SRV-ATTR:host | -
>
>
>
> |
> | OS-EXT-SRV-ATTR:hostname | cirros-2
>
>
>
> |
> | OS-EXT-SRV-ATTR:hypervisor_hostname | -
>
>
>
> |
> | OS-EXT-SRV-ATTR:instance_name | instance-00000008
>
>
>
> |
> | OS-EXT-SRV-ATTR:kernel_id |
>
>
>
> |
> | OS-EXT-SRV-ATTR:launch_index | 0
>
>
>
> |
> | OS-EXT-SRV-ATTR:ramdisk_id |
>
>
>
> |
> | OS-EXT-SRV-ATTR:reservation_id | r-qrjz6933
>
>
>
> |
> | OS-EXT-SRV-ATTR:root_device_name | /dev/vda
>
>
>
> |
> | OS-EXT-SRV-ATTR:user_data | -
>
>
>
> |
> | OS-EXT-STS:power_state | 0
>
>
>
> |
> | OS-EXT-STS:task_state | -
>
>
>
> |
> | OS-EXT-STS:vm_state | error
>
>
>
> |
> | OS-SRV-USG:launched_at ...

Read more...

Revision history for this message
Jim Ntosas (ntosas) wrote :

Hello Ravi,

If you can confirm that you have enough resources to allocate your instance (cirros only need some MB of RAM), then the issue comes from networking (neutron) and not from nova itself.

Trace neutron logs for "PortBindingFailed" to check my assumption.

Revision history for this message
Prankul Mahajan (prankul) wrote :

The same thing happened with me .
But upon launching the instance multiple times the issue disappeared.
I think this is not a bug but a server issue

Revision history for this message
Dmitry Snitko (win-di) wrote :

Hello,
I faced the same issue when, by mistake, I tried to launch an instance with public network attached only instead of local network (in my case external net had no DHCP enabled).
Thanks Jim Ntosas for the useful insight about nova vs neutron issue in #5.

Revision history for this message
Peter (zpeterg) wrote :

I had the same problem, and Dmitry's problem fixed it - I was starting and instance into public network.

Revision history for this message
Venkat Reddy Sangam (venkat-reddybe) wrote :

Hi Team,
i am facing same issue can some one help me to fix

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.