Using different interface for Admin/PXE fails provisioning
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Unassigned | ||
6.1.x |
Won't Fix
|
High
|
Rodion Tikunov | ||
7.0.x |
Fix Released
|
High
|
Unassigned |
Bug Description
Version found: Fuel 6.1 nightly build 2015-06-13
Steps to reproduce:
1. Create a 1 node cluster consisting only of a controller.
2. Make sure that 2 of the interfaces of this controller are on the same l2 as PXE/Admin network. As example our eth0 and eth1 are both on the same l2.
3. Now specify that the controller PXE boots in following order: eth0, eth1
4. At discovery phase let the controller PXE boot from eth1
5. After node is discovered assign the controller role and assign eth0 as the Admin/PXE network
6. Deploy as usual
Current result:
Deployment fails at provisioning for the node which changed it's pxe/admin interface. The fuel-agent contains a bug: http://
fuel_agent.
fuel_agent.
fuel_agent.
fuel_agent.
Expected result:
Deployment should succeed or user experience should disable changing PXE/admin interface.
Workaround:
I had to manually change the code /usr/lib/
Changed in fuel: | |
milestone: | none → 6.1 |
assignee: | nobody → Fuel provisioning team (fuel-provisioning) |
importance: | Undecided → High |
Changed in fuel: | |
assignee: | Fuel provisioning team (fuel-provisioning) → Aleksandr Gordeev (a-gordeev) |
tags: | added: customer-found feature-image-based |
tags: | added: feature |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
no longer affects: | fuel/8.0.x |
tags: | added: tricky |
Changed in fuel: | |
assignee: | Aleksey Kasatkin (alekseyk-ru) → Ivan Kliuk (ivankliuk) |
tags: | added: on-verification |
tags: | added: area-python |
Sam Stoelinga, could you provide at least full fuel-agent.log from failed node?
it could be found on bootstrap loaded node at /var/log/ or on masternode in /var/log/ docker- logs/remote/ <node>/ bootstrap.
If possible please share with us diagnostic snapshot.