[Bug 1187423] New: [Build 20210615] autoyast does not mark wicked for installation
http://bugzilla.opensuse.org/show_bug.cgi?id=1187423 Bug ID: 1187423 Summary: [Build 20210615] autoyast does not mark wicked for installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1790669/modules/clon e/steps/8 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: yast2-maintainers@suse.de Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-autoyast_multi_btrfs@64bit fails in [clone](https://openqa.opensuse.org/tests/1790669/modules/clone/steps/8) the AY profile uses: <keep_install_network config:type="boolean">true</keep_install_network> thus wants to configure wicked; yet, ay relies on anything else to make sure wicked is there (used to be pulled in by sysconfig in the past; that was finally fixed, which results now in AY-based setups without network control daemon) ## Test suite description AutoYaST installation with multi-device Btrfs. The setup containing 4 hds using two multidevice btrfs, one mounted on / and one mounted on /test. Combines partition-less disk and disk with partition, also includes an encrypted disk. ## Reproducible Fails since (at least) Build [20210615](https://openqa.opensuse.org/tests/1790203) ## Expected result Last good: [20210614](https://openqa.opensuse.org/tests/1788253) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=autoyast_multi_btrfs&version=Tumbleweed) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1187423 http://bugzilla.opensuse.org/show_bug.cgi?id=1187423#c3 --- Comment #3 from Knut Alejandro Anderssen Gonz�lez <kanderssen@suse.com> --- (In reply to Lukas Ocilka from comment #1)
It will probably need to be added somewhere here https://github.com/yast/yast-network/blob/ 2e99b2f5f3f939024422213bdc683b62fe2b1139/src/modules/Lan.rb#L654-L673
If I'm not wrong that is only called during the second stage. It should be fixed if we call the proposal even without confirm. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com