StarlingX

  1. Bug #1883458
  2. Activity log

Activity log for bug #1883458

Date Who What changed Old value New value Message
2020-06-14 22:12:21 Tee Ngo bug added bug
2020-06-14 22:12:27 Tee Ngo starlingx: assignee Tee Ngo (teewrs)
2020-06-15 01:04:06 OpenStack Infra starlingx: status New In Progress
2020-06-15 17:48:59 Ghada Khalil summary Data migration to 20.06 in the system controller will fail if there is an unmanaged subcloud Data migration in the system controller will fail if there is an unmanaged subcloud
2020-06-15 17:49:54 Ghada Khalil description Brief Description ----------------- There is a code flaw in the data migration script 50-dcmanager-subcloud-status-migration.py that can fail data migration to 20.06 in the system controller if there is a subcloud that has never been managed. Severity -------- Major Steps to Reproduce ------------------ Bring up a 20.01 distributed cloud Add a couple of subclouds without managing them Perform upgrade of the system controller to 20.06 Expected Behavior ------------------ System Controller upgrade to 20.06 completes successfully Actual Behavior ---------------- System Controller failed during the data migration step as subcloud load status records, which are created based on the data of patch status records, failed to be inserted when patch updated_at field is empty. Reproducibility --------------- 100% reproducible System Configuration -------------------- Distributed Cloud Branch/Pull Time/Commit ----------------------- June 6th master load Last Pass --------- First time this was tested with subclouds that have never been managed. This is not a typical use case in production but is a legitimate one nonetheless. Timestamp/Logs -------------- N/A Test Activity ------------- Developer Testing of another feature Workaround ---------- Brief Description ----------------- There is a code flaw in the data migration script 50-dcmanager-subcloud-status-migration.py that can fail data migration to 20.06 in the system controller if there is a subcloud that has never been managed. Severity -------- Major Steps to Reproduce ------------------ Bring up a 20.01 distributed cloud Add a couple of subclouds without managing them Perform upgrade of the system controller to 20.06 Expected Behavior ------------------ System Controller upgrade to 20.06 completes successfully Actual Behavior ---------------- System Controller failed during the data migration step as subcloud load status records, which are created based on the data of patch status records, failed to be inserted when patch updated_at field is empty. Reproducibility --------------- 100% reproducible System Configuration -------------------- Distributed Cloud Branch/Pull Time/Commit ----------------------- June 6th master load Last Pass --------- First time this was tested with subclouds that have never been managed. This is not a typical use case in production but is a legitimate one nonetheless. Timestamp/Logs -------------- N/A Test Activity ------------- Developer Testing of another feature Workaround ----------
2020-06-15 17:50:12 Ghada Khalil tags stx.4.0 stx.distcloud stx.update
2020-06-15 17:50:30 Ghada Khalil starlingx: importance Undecided High
2020-06-15 17:51:05 Ghada Khalil bug added subscriber Daniel Badea
2020-06-15 19:39:19 OpenStack Infra starlingx: status In Progress Fix Released