Ask Your Question
1

No VIFs found for node when attempting to update DHCP BOOT options.

asked 2015-02-16 00:33:41 -0500

Manab gravatar image

Hi

Please have a look on some ironic CLIs output i have attached here.

oot@Node2:~# ironic node-show e171a085-916a-49a3-bb27-27a43e910fc6 +------------------------+--------------------------------------------------------------------------+ | Property | Value | +------------------------+--------------------------------------------------------------------------+ | instance_uuid | None | | target_power_state | None | | properties | {u'memory_mb': u'196608', u'cpu_arch': u'x86_64', u'local_gb': u'20', | | | u'cpus': u'16'} | | maintenance | False | | driver_info | {u'pxe_deploy_ramdisk': u'e57895cc-1d2e-4f63-bc19-7cacbb847ac6', | | | u'ipmi_terminal_port': u'1500', u'ipmi_username': u'root', | | | u'ipmi_address': u'172.20.216.145', u'ipmi_password': u'cisco123', | | | u'pxe_deploy_kernel': u'bdb3253a-c221-4985-822f-513459a27748'} | | extra | {} | | last_error | Failed to deploy. Error: No VIFs found for node e171a085-916a- | | | 49a3-bb27-27a43e910fc6 when attempting to update DHCP BOOT options. | | created_at | 2015-02-09T14:29:05+00:00 | | target_provision_state | None | | driver | pxe_ipmitool | | updated_at | 2015-02-16T06:21:30+00:00 | | instance_info | {u'ramdisk': u'df588f5b-dc98-4153-8021-dac15b8c04df', u'kernel': | | | u'731b1700-0000-4ec3-8049-4a8d4475aa50', u'root_gb': u'10', | | | u'image_source': u'b1307f06-839d-44f4-8c2c-b1093723edaa', u'deploy_key': | | | u'PR2SCF6A01324V9XC00YXT0B00I0K7TU'} | | chassis_uuid | e9574edc-3ddb-4acb-8ab8-4a93602d857e | | provision_state | deploy failed | | reservation | None | | power_state | power off | | console_enabled | False | | uuid | e171a085-916a-49a3-bb27-27a43e910fc6 | +------------------------+--------------------------------------------------------------------------+

root@Node2:~# ironic port-list +--------------------------------------+-------------------+ | uuid | address | +--------------------------------------+-------------------+ | db69ce0e-6ab3-4149-94fa-aa6c863f9f33 | 00:25:b5:cc:10:0b | +--------------------------------------+-------------------+

root@Node2:~# ironic port-show db69ce0e-6ab3-4149-94fa-aa6c863f9f33 +------------+--------------------------------------+ | Property | Value | +------------+--------------------------------------+ | node_uuid | e171a085-916a-49a3-bb27-27a43e910fc6 | | uuid | db69ce0e-6ab3-4149-94fa-aa6c863f9f33 | | extra | {} | | created_at | 2015-02-12T08:55:28+00:00 | | updated_at | None | | address | 00:25:b5:cc:10:0b | +------------+--------------------------------------+

After this when i am running "ironic node-set-provision-state e171a085-916a-49a3-bb27-27a43e910fc6 active ", everytime the deployment is getting failed.

I am getting some warning message in ironic-conductor log as "

2015-02-15 22:08:13.368 1724 WARNING ironic.conductor.manager [-] Error in deploy of node e171a085-916a-49a3-bb27-27a43e910fc6: No VIFs found for node e171a085-916a-49a3-bb27-27a43e910fc6 when attempting to update DHCP BOOT options."

Am i missing anything?? If anymore things required, please let me know.

Thanks Manab

edit retag flag offensive close merge delete

Comments

Please respond someone.. i am eagerly waiting for the solution to this issue

Manab gravatar imageManab ( 2015-02-17 05:12:05 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-03-23 12:59:19 -0500

jjulien gravatar image

You need to boot the node using nova, at which point you will also tell Nova what network you want the node on. This will reserve for you an address and setup the PXE information in DHCP.

edit flag offensive delete link more

Comments

Hi,

When I try to boot with Nova, it fails with the ExactRamFilter verification. Nova seems to not see my ironic node. Is there anything specific to do to make my ironic nodes available to nova ?

bonclay7 gravatar imagebonclay7 ( 2015-08-11 08:16:02 -0500 )edit

Check whether your node is in active state ironic node-set-provision-state <node id=""> active and check nova hypervisor-stats (this should be populated with BM information).

Post that if you boot it via nova boot.

getvasanth gravatar imagegetvasanth ( 2015-10-27 04:34:56 -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

2 followers

Stats

Asked: 2015-02-16 00:33:41 -0500

Seen: 858 times

Last updated: Mar 23 '15