openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #25144
BAREMETAL: Unable to launch the instance due to "No valid host was found"
Hi,
I have open stack Grizzly installed configures with baremetal environment .
Following: https://wiki.openstack.org/wiki/Baremetal
OS: Ubuntu 12.04 LTS
Install Mode : Multi node setup (controller and the compute hosts are two separate nodes.)
Error: I'm unable to launch the instance due to error "No valid host was found"
nova flavor-list | grep 10
| 10 | SB | 2048 | 10 | 0 | | 1 | 1.0 | True | {u'cpu_arch': u'x86_64', u'baremetal:deploy_kernel_id': u'821affce-d908-4b07-81b8-f5eaf7c6ab21', u'baremetal:deploy_ramdisk_id': u'c8abfc1d-bc43-48ef-ade3-b1de96af219f'} |
nova baremetal-node-list
+----+------+------+-----------+---------+-------------------+------------+---------------+-------------+---------------+
| ID | Host | CPUs | Memory_MB | Disk_GB | MAC Address | PM Address | PM Username | PM Password | Terminal Port |
+----+------+------+-----------+---------+-------------------+------------+---------------+-------------+---------------+
| 2 | bm1 | 1 | 2048 | 10 | E8:39:35:2B:F9:E0 | 10.0.0.22 | Administrator | | None |
+----+------+------+-----------+---------+-------------------+------------+---------------+-------------+---------------+
nova baremetal-interface-list 2
+----+-------------+---------+-------------------+
| ID | Datapath_ID | Port_No | Address |
+----+-------------+---------+-------------------+
| 2 | 0 | 0 | E8:39:35:2B:F9:E0 |
+----+-------------+---------+-------------------+
nova boot --flavor SB --image my-image INS2
+-------------------------------------+--------------------------------------+
| Property | Value |
+-------------------------------------+--------------------------------------+
| status | BUILD |
| updated | 2013-07-15T15:56:02Z |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-SRV-ATTR:host | None |
| key_name | None |
| image | my-image |
| hostId | | |
+-------------------------------------+--------------------------------------+
nova show 88affe47-02a4-46c8-b155-aadce5df5134
+-------------------------------------+------------------------------------------------------------------------------------+
| Property | Value |
+-------------------------------------+------------------------------------------------------------------------------------+
| status | ERROR |
| updated | 2013-07-15T15:56:02Z |
| OS-EXT-STS:task_state | None |
| OS-EXT-SRV-ATTR:host | None |
| key_name | None |
| | |
| fault | {u'message': u'NoValidHost', u'code': 500, u'details': u'No valid host was found. |
| | ', u'created': u'2013-07-15T15:56:02Z'} |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-AZ:availability_zone | None |
| config_drive | |
+-------------------------------------+------------------------------------------------------------------------------------+
DNSMASQ is running and all other services WRT to Openstack running.
nova.conf
#########
# Baremetal
scheduler_host_manager=nova.scheduler.baremetal_host_manager.BaremetalHostManager
firewall_driver=nova.virt.firewall.NoopFirewallDriver
compute_driver=nova.virt.baremetal.driver.BareMetalDriver
ram_allocation_ration=1.0
reserved_host_memory_mb=0
[baremetal]
sql_connection=postgresql://nova:mwx4s3gzsjy8@192.168.124.81/nova_bm
instance_type_extra_specs=cpu_arch:x86_64
driver=nova.virt.baremetal.pxe.PXE
power_manager=nova.virt.baremetal.ipmi.IPMI
terminal=shellinaboxd
nova-scheduler.log
##################
2013-07-15 10:13:52.808 31607 INFO nova.service [-] Caught SIGTERM, exiting
2013-07-15 10:13:55.294 26398 AUDIT nova.service [-] Starting scheduler node (version 2013.1)
2013-07-15 10:13:56.816 INFO nova.openstack.common.rpc.common [req-7424f636-7b56-47b6-a758-7871568de350 None None] Connected to AMQP server on 192.168.124.81:5672
2013-07-15 10:13:56.841 INFO nova.openstack.common.rpc.common [req-7424f636-7b56-47b6-a758-7871568de350 None None] Connected to AMQP server on 192.168.124.81:5672
2013-07-15 10:39:20.208 WARNING nova.scheduler.driver [req-96b23651-acac-46a7-ba20-2440d4244572 e29d4b006311421896a3469d7efb3621 33a71acc451e4bfc8105a1b7d01bfe8c] [instance: 4cd2d334-856d-435c-81bd-cc0d71177163] Setting instance to ERROR state.
2013-07-15 10:41:30.646 WARNING nova.scheduler.driver [req-2360fa22-90a0-4319-bdc7-0c75119beb23 e29d4b006311421896a3469d7efb3621 33a71acc451e4bfc8105a1b7d01bfe8c] [instance: a689c1f0-ee76-467f-aee6-bf613f641126] Setting instance to ERROR state.
2013-07-15 10:50:59.934 WARNING nova.scheduler.driver [req-9788e857-47be-488d-8338-eab2edf3919a e29d4b006311421896a3469d7efb3621 33a71acc451e4bfc8105a1b7d01bfe8c] [instance: cfe18217-f803-48ca-89d2-0b396327afb5] Setting instance to ERROR state.
2013-07-15 10:56:02.472 WARNING nova.scheduler.driver [req-a8abeb9a-a8ec-4775-8c9d-d1492a5fa63a e29d4b006311421896a3469d7efb3621 33a71acc451e4bfc8105a1b7d01bfe8c] [instance: 88affe47-02a4-46c8-b155-aadce5df5134] Setting instance to ERROR state.
Any help on this would be really helpful
Thanks
Shanthakumar K
Follow ups