This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2213073 - OpenShift console does not generate correct cloud-init config
Summary: OpenShift console does not generate correct cloud-init config
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.12.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Tal Nisan
QA Contact: Guohua Ouyang
URL:
Whiteboard:
: 2222677 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-07 05:21 UTC by Dieter
Modified: 2023-09-20 16:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-29 02:57:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2190439 0 unspecified CLOSED cloudInitConfigDrive yaml contains cloudInitNoCloud content 2023-09-27 16:51:56 UTC
Red Hat Bugzilla 2213449 0 unspecified CLOSED cloud-init fails when configuring both network and SSH key from the OpenShift console 2023-09-20 16:00:49 UTC
Red Hat Issue Tracker   CNV-29457 0 None None None 2023-08-29 02:57:31 UTC
Red Hat Knowledge Base (Solution) 7024968 0 None None None 2023-07-19 13:26:52 UTC

Description Dieter 2023-06-07 05:21:48 UTC
Description of problem:
When creating a virtual machine and adding network information using cloud-init, the YAML code for this VirtualMachine generated by the console is not correct.

How reproducible:
100%

Steps to Reproduce:
1: From the console, create a RHEL9 VM using the template, customize virtual machine 
2: Add a secondary Network interface
3: Go to scripts => Edit cloudinit => "Add network data" => use
Ethernet name: eth1
IP addresses: 10.10.21.32/24

(though the instructions say "Use commas to separate between IP addresses", this would generate an error in ifcfg-eth1 on the virtual machine, which resulted in an error by the NetworkManager)

Actual results:
Go to "YAML", the generated code is:
            networkData: |
              network:
                version: '1'
                config:
                  - type: physical
                    name: eth1
                    subnets:
                      - type: static
                        address:
                          - 10.10.21.32/24
                        gateway: 10.10.21.1

Expected results:
            networkData: |
              network:
                version: 1
                config:
                  - type: physical
                    name: eth1
                    subnets:
                      - type: static
                        address: 10.10.21.32/24
                        gateway: 10.10.21.1

This means there are 2 errors:
1) '1' should be replaced by 1
2) address should not be a list of items

Comment 1 Guohua Ouyang 2023-07-17 07:24:04 UTC
*** Bug 2222677 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.