Dcorch stopped auditing subclouds after upgrading from 20.06 to 20.12
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Tao Liu |
Bug Description
Brief Description
-----------------
After successful upgrade of 10 subclouds, dcmanager shows all subclouds are online/in-sync, but only one subcloud’s sysadmin password was restored (the password was reset to default during upgrade).
After investigation, it was revealed that dcorch-engine was auditing only 1 subcloud, the other 9 subclouds were not audited due to audit_status of subcloud_sync data was not set. The audit_status has an initial state of “none”. During upgrade/data migration, the subcloud_sync data was populated with initial values, however, audit_status field was not included.
Severity
--------
Critical
Steps to Reproduce
------------------
1. Upgrade DC system controller
2. Create a upgrade strategy and upgrade 10 subclouds in parallel
3. Login to subclouds using sysadmin/<password> after the upgrade is completed
Expected Behavior
------------------
Login to subclouds with the original sysadmin password (used prior to upgrade)
Actual Behavior
----------------
Login to subclouds with default password
Reproducibility
---------------
Reproducible
System Configuration
-------
A DC system with 10 subclouds
Branch/Pull Time/Commit
-------
Master March 9, 2021
Last Pass
---------
N/A
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Feature Testing
Workaround
----------
Unmanage and manage subclouds to recover
Changed in starlingx: | |
assignee: | nobody → Tao Liu (tliu88) |
Changed in starlingx: | |
importance: | Undecided → High |
tags: | added: stx.update |
tags: | added: stx.5.0 stx.distcloud |
Fix merged: /opendev. org/starlingx/ config/ commit/ e2e7d45d0e5a84f 7ef345a5a6561c5 370a85a5fd
https:/