Instance deployment failure due to neutron syntax error

Bug #1682222 reported by Rajini Karthik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
Invalid
Undecided
Unassigned
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

See error below in n-cpu.log
Detailed logs available at: https://stash.opencrowbar.org/logs/27/456127/2/check/dell-hw-tempest-dsvm-ironic-pxe_ipmitool/d29e3b6/:
or
http://logs.openstack.org/27/456127/2/check/gate-ironic-docs-ubuntu-xenial/7838443/console.html

2017-04-12 19:21:46.750 16295 DEBUG oslo_messaging._drivers.amqpdriver [-] received reply msg_id: cbd36fde5e9444f28f72acd31189cf31 __call__ /usr/local/lib/python2.7/d
ist-packages/oslo_messaging/_drivers/amqpdriver.py:346
2017-04-12 19:21:46.792 16295 ERROR oslo.service.loopingcall [-] Fixed interval looping call 'nova.virt.ironic.driver.IronicDriver._wait_for_active' failed
2017-04-12 19:21:46.792 16295 ERROR oslo.service.loopingcall Traceback (most recent call last):
2017-04-12 19:21:46.792 16295 ERROR oslo.service.loopingcall File "/usr/local/lib/python2.7/dist-packages/oslo_service/loopingcall.py", line 137, in _run_loop
2017-04-12 19:21:46.792 16295 ERROR oslo.service.loopingcall result = func(*self.args, **self.kw)
2017-04-12 19:21:46.792 16295 ERROR oslo.service.loopingcall File "/opt/stack/new/nova/nova/virt/ironic/driver.py", line 431, in _wait_for_active
2017-04-12 19:21:46.792 16295 ERROR oslo.service.loopingcall raise exception.InstanceDeployFailure(msg)
2017-04-12 19:21:46.792 16295 ERROR oslo.service.loopingcall InstanceDeployFailure: Failed to provision instance 651a266c-ea66-472b-bc61-dafe4870fdd6: Failed to prepa
re to deploy. Error: Failed to load DHCP provider neutron, reason: invalid syntax (neutron.py, line 153)
2017-04-12 19:21:46.792 16295 ERROR oslo.service.loopingcall
2017-04-12 19:21:46.801 16295 ERROR nova.virt.ironic.driver [req-9b30e546-51d9-4e4f-b4bd-cc5d75118ea3 tempest-BaremetalBasicOps-247864778 tempest-BaremetalBasicOps-24
7864778] Error deploying instance 651a266c-ea66-472b-bc61-dafe4870fdd6 on baremetal node 9ab67aec-921e-464d-8f2f-f9da65649a5e.

Revision history for this message
Julia Kreger (juliaashleykreger) wrote :

Thank you! This bug seems like it is more appropriate for the ironic project. I'm unable to a access the URL you posted a link to. If you could post ir-cond.log to the bug, It would assist in context and a allow us to better understand exactly what occurred.

Again, Thank you.

-Julia

Changed in ironic:
status: New → Incomplete
Revision history for this message
Rajini Karthik (rajini-karthik) wrote :
description: updated
description: updated
description: updated
Changed in ironic:
status: Incomplete → New
Revision history for this message
Vladyslav Drok (vdrok) wrote :

Same comment, it was just run on a patch with merge conflict, no actual issue with ironic or nova.

Changed in ironic:
status: New → Invalid
Changed in nova:
status: New → Invalid
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.