action #129547
closed
coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Set networking section with explicit eth0 defined in autoyast profile to avoid complicated output issue for wicked
Added by tinawang123 12 months ago.
Updated 11 months ago.
- Subject changed from Remove unnecessary elements for autoyast profile: autoyast_sle15/create_hdd /create_hdd_gnome_aarch64.xml to Set networking section with explicit eth0 defined in autoyast profile to avoid complicated output issue for wicked
- Description updated (diff)
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version set to Current
- Parent task set to #121876
- Status changed from Workable to In Progress
- Assignee set to coolgw
First try publish qcow with network setting:
./mycustom wicked-fix-129547 11152349 PUBLISH_HDD_1=autoyast-SLES-15-SP4-aarch64-gnome-allpatterns-updated-wegao.qcow2
Created job #11160403: sle-15-SP4-Server-DVD-Updates-aarch64-Build20230517-1-sle_autoyast_create_hdd_gnome_allpatterns@aarch64-virtio -> https://openqa.suse.de/t11160403
./mycustom wicked-fix-129547 11146876 HDD_1=autoyast-SLES-15-SP4-aarch64-gnome-allpatterns-updated-wegao.qcow2
Created job #11160579: sle-15-SP5-Migration-from-SLE15-SPx-aarch64-Build101.1-autoupgrade_sles15sp4_pscc_basesys-srv_all_full_auto@aarch64 -> https://openqa.suse.de/t11160579
- Related to action #128150: Fix the wickedd.service checking issue added
- Description updated (diff)
Update xml network part base https://openqa.nue.suse.com/tests/11180872#step/cleanup_before_shutdown/27.
./mycustom wicked-fix-129547 11152349 PUBLISH_HDD_1=autoyast-SLES-15-SP4-aarch64-gnome-allpatterns-updated-wegao.qcow2
Created job #11181978: sle-15-SP4-Server-DVD-Updates-aarch64-Build20230517-1-sle_autoyast_create_hdd_gnome_allpatterns@aarch64-virtio -> https://openqa.suse.de/t11181978
Seems still exist bridge, try to find one correct xml template for ONLY eth0 exist.
Use create_hdd_gnome_aarch64.xml create only eth0 verify next job:
./mycustom wicked-fix-129547 11152349 PUBLISH_HDD_1=autoyast-SLES-15-SP4-aarch64-gnome-allpatterns-updated-wegao.qcow2 \
AUTOYAST=autoyast_sle15/create_hdd/create_hdd_gnome_aarch64.xml
Created job #11183417: sle-15-SP4-Server-DVD-Updates-aarch64-Build20230517-1-sle_autoyast_create_hdd_gnome_allpatterns@aarch64-virtio -> https://openqa.suse.de/t11183417
./mycustom wicked-fix-129547 11146876 HDD_1=autoyast-SLES-15-SP4-aarch64-gnome-allpatterns-updated-wegao.qcow2
Created job #11183820: sle-15-SP5-Migration-from-SLE15-SPx-aarch64-Build101.1-autoupgrade_sles15sp4_pscc_basesys-srv_all_full_auto@aarch64 -> https://openqa.suse.de/t11183820
The bridge interface will be configured automaticly if you add kvm_server or kvm_tools pattern. Not related with explicit define eth0 or not.
coolgw wrote:
The bridge interface will be configured automaticly if you add kvm_server or kvm_tools pattern. Not related with explicit define eth0 or not.
nice finding! makes sense for virtualization I guess, then we can accept that we have br0 in cases where we install all the patterns, we just need to handle in the automation code.
I guess if nothing is failing at the moment, we can resolve this ticket.
JERiveraMoya wrote:
coolgw wrote:
The bridge interface will be configured automaticly if you add kvm_server or kvm_tools pattern. Not related with explicit define eth0 or not.
nice finding! makes sense for virtualization I guess, then we can accept that we have br0 in cases where we install all the patterns, we just need to handle in the automation code.
I guess if nothing is failing at the moment, we can resolve this ticket.
If you can accept current https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17100 then we can resolve this ticket.
In fact, I think the job to create qcow is wrong, we don't need all addons while got 'SCC_ADDONS=sdk,base,script,serverapp,desktop,legacy,contm,python3'. Another thinking is the existing issue that all patterns should depend on the module registered while not real 'all' patterns, this is currently migration test existing issue, we will fix it later.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF