Remote B&R: Subcloud power status not updated after restore failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Tee Ngo |
Bug Description
Brief Description
-----------------
After the restore failure, the availability status of the subcloud is not updated in "dcmanager subcloud list"
Severity
--------
Major
Steps to Reproduce
------------------
1. Unmanage the subcloud
2. Prepare the restore values yaml file subcloud1_
initial_backup_dir: /scratch
backup_filename: <name-of-
on_box_data: false
3. Execute the following subcloud restore command where subcloud1_
dcmanager subcloud restore --restore-values subcloud1_
4. Verify the user receives a positive restore response with deploy status set to “pre-restore” as the request passed the syntactic validations.
Subcloud restore eventually fails with the deploy status of “restore-failed” due to missing backup tarball. The initial_backup_dir set in restore values yaml file should be /home/sysadmin, not /scratch
5. Poweroff the subcloud when its in restore-failed state
Expected Behavior
------------------
Subcloud should be shown as offline
Actual Behavior
----------------
Subcloud is shown as online, dcmanager is not auditing the subcloud that undergoes remote restore
Reproducibility
---------------
100% reproducible
System Configuration
-------
Distributed Cloud
Branch/Pull Time/Commit
-------
April 12th StarlingX load
Last Pass
---------
First time this test case is executed
Timestamp/Logs
--------------
N/A as the issue is readily reproducible
Test Activity
-------------
Feature Testing
Workaround
----------
None
tags: | added: stx.update |
Changed in starlingx: | |
assignee: | nobody → Tee Ngo (teewrs) |
tags: | added: stx.distcloud |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.5.0 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /distcloud/ +/786150
Review: https:/