kube upgrade via Horizon - Change popup message from "force" parameter
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Agustin Carranza |
Bug Description
Brief Description
-----------------
"Force" parameter should include offline subclouds when selected to the strategy as the help message says.
After selecting the "force" parameter we dont have the offline subcloud added to the strategy. do we expect to have the subcloud added to the strategy or we have a wrong help message?
if the help message is wrong, I saw force parameter can do:
force kube upgrade to a subcloud which is in-sync with system controller
then we need to change the message based on this functionality.
Severity
-----------------
<Minor: System/Feature is usable with minor issue>
Steps to Reproduce
-----------------
deploy a dc system with multiple subclouds
ensure you have an offline subcloud
select the force parameter and create a strategy to kube-upgrade
Expected Behavior
-----------------
??
Actual Behavior
-----------------
When "force" parameter was selected the offline subcloud was not added to strategy steps:
Reproducibility
-----------------
State if the issue is 100% reproducible
System Configuration
-----------------
Dc system
Branch/Pull Time/Commit
-----------------
stx.6.0/ Build_2022-
Test Activity
-----------------
Feature Testing
Changed in starlingx: | |
assignee: | nobody → Agustin Carranza (acarranz) |
affects: | starlingx → ubuntu |
affects: | ubuntu → starlingx |
Changed in starlingx: | |
status: | New → In Progress |
tags: | added: stx.gui |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.7.0 |
Reviewed: https:/ /review. opendev. org/c/starlingx /gui/+/ 842143 /opendev. org/starlingx/ gui/commit/ 2dd7455be5bc681 aae8f83663720f8 02f343aa85
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 2dd7455be5bc681 aae8f83663720f8 02f343aa85
Author: Agustin Carranza <email address hidden>
Date: Tue May 17 11:24:34 2022 -0400
Fix for 'Apply to' and 'Force' fields behavior
On 'Create Strategy' form the following fields are not usable when
selecting a subcloud:
* subcloud apply type
* maximum parallel subclouds
Now they are hidden in such case.
Input element for subcloud name was changed to a dropdown list.
If 'All subclouds' is selected, the strategy is applied to all
subclouds and the fields mentioned are hidden. If any other
subloud name is selected, such fields are shown.
It was created another 'force' element for kubernetes strategy
which shows a help message that is consistent with the expected
behavior. The original element is left for 'upgrade' strategy only.
Test Plan
PASS:
Build package
Install package on DC with at least one subcloud
Open gui on a browser and navigate to Distributed Cloud Admin ->
Orchestration -> Orchestration Stragegy -> Create Strategy:
* Check 'force' parameter is hidden for 'Patch' and 'Firmware' strategy
types.
* Check 'force' help text describes actual behavior.
* Check 'subcloud' field is a dropdown menu and shows available
subclouds.
* Check 'subcloud apply type' and 'maximum parallel subclouds' fields
are not shown when a single subcloud is selected in the dropdown
menu.
Closes-bug: 1973210
Closes-bug: 1973805
Signed-off-by: Agustin Carranza <email address hidden> 4f6e55610916556 5394ec63114
Change-Id: I909bb548f9b645