Unable to update subcloud details
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Cristian Mondo |
Bug Description
Brief Description
-----------------
Unable to update subcloud location or description fields from Horizon or CLI
if the string has the following format:
VBOX workstation: workstation: 127.0.0.1
Severity
--------
Minor
Steps to Reproduce
------------------
1 - Open admin portal
2 - Go to Cloud Overview then select desired subcloud
3 - Click on Actions then select Edit Subcloud
4 - Update Description or location textfield adding the following string:
VBOX workstation: workstation: 127.0.0.1
5 - Finally click on submit, and an error is shown on screen.
The issue also happens from the CLI.
Expected Behavior
------------------
Should be able to update the subcloud successfully.
Actual Behavior
----------------
Subcloud details cannot be updated.
Reproducibility
---------------
Reproducible/100%
System Configuration
-------
Multi-node system
Test Activity
-------------
Developer Testing
Workaround
----------
The same string can be used, but the space after the colon must be removed.
VBOX workstation:
Changed in starlingx: | |
status: | New → In Progress |
Changed in starlingx: | |
assignee: | nobody → Cristian Mondo (cmondo) |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.8.0 stx.distcloud |
Reviewed: https:/ /review. opendev. org/c/starlingx /distcloud/ +/857762 /opendev. org/starlingx/ distcloud/ commit/ 6465ba0d328166f 62179e135fb2ab6 9284b618b7
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 6465ba0d328166f 62179e135fb2ab6 9284b618b7
Author: Cristian Mondo <email address hidden>
Date: Wed Sep 14 16:31:37 2022 -0300
Unable to update subcloud details
Adding a fix to solve the API (dcmanager-api) error that Horizon
and CLI returns when updating the description, location, or group
name on subcloud details by using the following string format:
VBOX workstation: workstation: 127.0.0.1
The API responds successfully if no space is placed after the colon
character. The error arises when the user places a space after the
colon character. This happens when the request parameters are
decoded and the values are passed to the YML safe_load method.
In order to force the string and fix the issue, the value was
enclosed in quotes.
Closes-Bug: 1989619
Test Plan - Horizon and CLI:
- Edit the subcloud from Horizon or run CLI command
- Update the description, location or group field by adding the following:
VBOX workstation: workstation: 127.0.0.1
Signed-off-by: Cristian Mondo <email address hidden> ffc2234652f5023 f3f29cab468
Change-Id: Ibe1f51d2166c0d