Node discovery lags in 6.0 tech preview
Bug #1391305 reported by
Dmitriy Novakovskiy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
Medium
|
Fuel Python (Deprecated) | ||
Bug Description
Myself and a user from one of companies currently testing Fuel have faced similar issue today:
Given:
- VMWare Fusion, a number of VMs for Fuel Master and OpenStack nodes
- Networks are wired "properly" - the same VMs+vmnet's worked fine with MOS 5.1
What happens:
- Fuel master node install from ISO goes fine
- Slave node goes through PXE boot fine
- After bootstrapping, slave node finishes at CentOS login, but - does not appear on Fuel dashboard as discovered
At further experimentation it appears that the node eventually shows up discovered - it just takes more time then it used to take w/ MOS 5.1 on same VMs.
Diagnostic snapshot is available here: https:/
| Changed in fuel: | |
| milestone: | none → 6.0 |
| assignee: | nobody → Fuel Python Team (fuel-python) |
| importance: | Undecided → Medium |
Revision history for this message
| Łukasz Oleś (loles) wrote | #1 |
| Changed in fuel: | |
| status: | New → Incomplete |
Revision history for this message
| Dmitry Pyzhov (dpyzhov) wrote | #2 |
| Changed in fuel: | |
| status: | Incomplete → Invalid |
To post a comment you must log in.
How many nodes for OpenStack? In logs I can only see one.
How much more time?
In logs I can se that nailgun started at 16:45 and first(and only node) registered at 16:49. Everything looks ok