Fuel 9.2 fails to recognise disks on additional controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Incomplete
|
High
|
Max Yatsenko |
Bug Description
Detailed bug description:
I did a fresh install of MOS 9.0 and upgraded to 9.2
There are hosts with an additional disk-controller installed, and in Fuel only 2 disks instead of 6 are shown. Two other hosts have 3 disks installed and also only 2 are recognised.
With a shell on the servers, I see, that the disks are recognised by the bootstrap-OS, but not in Fuel.
When using a MOS 9.0 installation this works as expected.
Steps to reproduce:
Install MOS 9.0, upgrade to 9.2
Boot hosts and let them come up with bootstrap-image
-> check a host in fuel, disks are missing
Expected results:
6 disks recognised
(or 2nd case: 3 disks recognised)
Actual result:
only 2 disk are recognised (also for the 2nd case)
Reproducibility:
did try 2 times with the same result
(also brought up a fresh 9.0 to check if it still works there)
Workaround:
1) in case of using CEPH: add disks manually (untested)
or 2) install MOS 9.0 let host come up with bootstrap from 9.0
then switch to 9.2 on Fuel-master (I have two virtualbox-images). As soon as the hosts are talking to the 9.2 master, they are recognised correctly.
Impact:
disks cannot be used or only by manual intervention per ssh.
This seems to be only an issue for fresh 9.2 installations.
Description of the environment:
MOS 9.0 or 9.2 Fuel-master on virtualbox (to switch between versions)
3x small HW-boxes with 2x3 disks and 1x6disks
Additional information:
somehow this makes me suspect, that something changed between the bootstrap-image of 9.0 and 9.2, that causes that behaviour. unfortunately I was not able to test on 9.1
PLMK if you need additional information.
br,
Robert
Changed in mos: | |
milestone: | none → 9.x-updates |
assignee: | nobody → MOS Maintenance (mos-maintenance) |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in mos: | |
assignee: | MOS Maintenance (mos-maintenance) → Max Yatsenko (myatsenko) |
I can now confirm, that the workaround with the Fuel Master on MOS 9.0 works:
* you need a 9.0 fuel master
* boot the systems while on MOS 9.0 and wait, until they are recognised by the fuel-master.
* shut down only the 9.0 master
* boot up the 9.2 master and wait until the nodes report to that master.
* create an environment and proceed on MOS 9.2