No slave-nodes available after MOS installation using virtualbox scripts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Dmitry Bilunov |
Bug Description
MOS installation using virtualbox scripts
ISO: 284, 291
VB scripts: latest master
server:
1) Install latest VB scripts on server
2) Copy ISO to iso folser
3) Update config.sh with:
elif [ "$CONFIG_FOR" = "8GB" ]; then
vm_slave_
vm_slave_
vm_slave_
vm_slave_
...
headless=1
skipfuelmenu="yes"
4) Run ./launch_8GB.sh
Expected behaviour:
Slave nodes are up and available for deploying.
Got next output:
Waiting for VM "fuel-master" to power on...
VM "fuel-master" has been successfully started.
Waiting for product VM to install. Please do NOT abort the script...
Checking for internet connectivity on the host system... OK
Checking local DNS configuration... ./functions/
OK
Enabling outbound network/internet access for the product VM...
Waiting until the network services are restarted...
FAIL
#######
# WARNING: some of the Fuel features will not be supported #
# because there is no Internet connectivity #
#######
Master node has been installed.
...
Slave nodes have been created. They will boot over PXE and get discovered by the master node.
To access master node, please point your browser to:
http://
The default username and password is admin:admin
But no nodes are available for deploying:
[root@fuel ~]# fuel nodes
id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id
---|---
tags: | added: vbox-scripts |
Changed in fuel: | |
milestone: | none → 8.0 |
assignee: | nobody → Fuel Library Team (fuel-library) |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: area-library |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Dmitry Bilunov (dbilunov) |
tags: | added: team-bugfix |
Changed in fuel: | |
status: | In Progress → Fix Committed |
tags: | added: on-verification |
tags: | removed: on-verification |
tags: | added: on-verification |
i reproduce this bug on mos-components-ci scripts. ISO 291-295