Bug 2080836 - Remarks in cloud init script disapear after editing in scripts tab
Summary: Remarks in cloud init script disapear after editing in scripts tab
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.13.0
Assignee: Tal Nisan
QA Contact: Leon Kladnitsky
URL:
Whiteboard:
Depends On: 2080835
Blocks: 2080833
TreeView+ depends on / blocked
 
Reported: 2022-05-02 06:34 UTC by Yaacov Zamir
Modified: 2023-02-13 00:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-13 00:28:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-17915 0 None None None 2022-11-24 01:10:40 UTC

Description Yaacov Zamir 2022-05-02 06:34:38 UTC 
Description of problem:
When editing cloudinit scripts using the scripts tab, comments in the code disapear

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. create a vm using the wizard
2. go to review page
3. copy a cloud script that include comments into the YAML tab
4. edit the cloud init script using the scripts tab

Actual results:
remarks in the code disapear

Expected results:
remarks in the code are not changed

Additional info:
cloud init should not be parsed as YAML code, it is using cloud confic syntax
Comment 1 Yaacov Zamir 2022-05-02 06:38:41 UTC 
note: this bug depends #2080835
Comment 2 Gilad Lekner 2022-05-04 10:12:55 UTC 
move to 4.12 @
Comment 3 Gilad Lekner 2022-05-04 10:25:00 UTC 
move to 4.12 @yaacov ?
Comment 4 Yaacov Zamir 2022-05-04 10:36:07 UTC 
not for now, we will move all the bugs we can to 4.12 when bugs season for 4.11 is over

no need to move it to 4.12 yet, lowered the priority to indicate we may not do it in 4.11
Comment 7 Guohua Ouyang 2023-02-13 00:28:33 UTC 
Check the bug on 4.13, the problem is not reproduced, close the bug for now
Note You need to log in before you can comment on or make changes to this bug.