Command: dcmanager subcloud update --group only accepts a subcloud ID
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Al Bailey |
Bug Description
Brief Description
-----------------
The subcloud group attribute can be set for a subcloud, but at the moment it needs to be an ID.
It should support the 'name' also.
There also seems to be problem if 0 is passed.
Severity
--------
Minor
Steps to Reproduce
------------------
This is an enhancement.
We know that 'Default' is a known subcloud group which always has ID 1.
so this command should work for a subcloud called subcloud1:
dcmanager subcloud update --group Default subcloud1
Expected Behavior
------------------
Should act the same as doing
dcmanager subcloud update --group 1 subcloud1
Actual Behavior
----------------
ERROR (app) Unable to update subcloud subcloud1
Reproducibility
---------------
100%
System Configuration
-------
DistributedCloud env. System controller and at least one subcloud
Branch/Pull Time/Commit
-------
Dec 9, 2020. This issue has been around since subcloud groups were added in May 2020
Last Pass
---------
N/A
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Developer Testing
Workaround
----------
Use the ID instead of the name.
Changed in starlingx: | |
assignee: | nobody → Al Bailey (albailey1974) |
Changed in starlingx: | |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: stx.5.0 stx.distcloud |
https:/ /review. opendev. org/c/starlingx /distcloud/ +/766276