B&R: On restore, inventory update fails when controller-1 host is online results in unlock failure when wipe_ceph_osds=true
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Ovidiu Poncea |
Bug Description
Bug Description : On duplex deployments, after reinstalling controller-1 sysinv agent does not report inventory nor does it connect to the rabbitmq of controller-0.
When wipe_ceph_osds=true partitions of OSD drives are wiped and this wipe is reported to sysinv-conductor thorough sysinv-agent. W/o this report, OSD partitions are still in the database and, on unlock, puppet manifests tries to create them and fails.
Problem is caused by https:/
Two solutions:
A. Copy the file from backup on restore (this file is backed up)
B. Fix code in https:/
Severity
--------
Major - B&R no longer works with wipe_ceph_osds=true on DX (tested). Also, on standard, reinstalling new hosts will be denied as, if sysinv.conf.default is not presend, new nodes installed will not report their inventory => we won't be able to install new nodes at all on restored setups (supposition)
Steps to Reproduce
------------------
1. Install an AIO-DX deployment, do a backup
2. Reinstall controller-0
3. Run ansible restore with wipe_ceph_osds=true
4. Unlock controller-0 & wait for it to be available
5. Re-install controller-1
6. unlock controller-1 => it fails to apply manifests as it tries to create the ceph osd partitions which are no longer present
Expected Behavior
------------------
When wipe_ceph_osds is set to true we should see that the partitions for the OSD nodes are removed from the database.
Actual Behavior
----------------
As per description
Reproducibility
---------------
100% Reproduce-able
System Configuration
-------
AIO-DX
Branch/Pull Time/Commit
-------
StarlingX_
Changed in starlingx: | |
assignee: | nobody → Ovidiu Poncea (ovidiu.poncea) |
description: | updated |
tags: | added: stx.3.0 stx.update |
Changed in starlingx: | |
status: | Triaged → In Progress |
stx.3.0 / medium - issue introduced by recent code changes and affects stx.3.0 B&R feature functionality