[Bug 1140040] New: [Build 20190701] openQA test fails in yast2_bootloader: Missing e2fsprogs requirement
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040 Bug ID: 1140040 Summary: [Build 20190701] openQA test fails in yast2_bootloader: Missing e2fsprogs requirement Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/972266/modules/yast2 _bootloader/steps/5 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: fvogt@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- yast bootloader fails to start because of "Command not found: /usr/bin/lsattr ...". ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos@64bit_virtio fails in [yast2_bootloader](https://openqa.opensuse.org/tests/972266/modules/yast2_bootloader/steps/5) ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [20190329](https://openqa.opensuse.org/tests/895647) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?version=Tumbleweed&distri=opensuse&arch=x86_64&test=jeos&flavor=JeOS-for-kvm-and-xen&machine=64bit_virtio) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040#c6
--- Comment #6 from Fabian Vogt
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040#c7
--- Comment #7 from Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040#c8
Ancor Gonzalez Sosa
The partitioner has a means to detect packages needed for a specific host and during the installation, it selects them for installation.
Seems that the bootloader module (and any other module heavily depending on partitioner) should - on start - get the list of pacakges detected and check and install them if missing.
See how that is done by AutoYaST here: https://github.com/yast/yast-autoinstallation/blob/75af746a955be0d755e645da4... Or by the installation process itself here: https://github.com/yast/yast-storage-ng/blob/a0cb655eed01b5c7004e2fffa3dacb1... Maybe yast2-bootloader can also use the Y2Storage::PackageHandler to get the list of packages and then offer the installation of those packages to the user in order to continue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040#c9
--- Comment #9 from Josef Reidinger
(In reply to Jiri Srain from comment #7)
The partitioner has a means to detect packages needed for a specific host and during the installation, it selects them for installation.
Seems that the bootloader module (and any other module heavily depending on partitioner) should - on start - get the list of pacakges detected and check and install them if missing.
See how that is done by AutoYaST here:
https://github.com/yast/yast-autoinstallation/blob/ 75af746a955be0d755e645da41061715329bcd7a/src/modules/AutoinstSoftware.rb#L842
Or by the installation process itself here: https://github.com/yast/yast-storage-ng/blob/ a0cb655eed01b5c7004e2fffa3dacb1d8ea51f0f/src/lib/y2storage/clients/ inst_disk_proposal.rb#L154
Maybe yast2-bootloader can also use the Y2Storage::PackageHandler to get the list of packages and then offer the installation of those packages to the user in order to continue.
I worry that this is not so easy, as there are also packages that uses bootloader API like yast2-vm or yast2-kdump and they also need to install respective packages. I worry that we never have this requirement and ideally we need to come with consistent API that can be used across modules like if you require given module/class it will automatic add its package requirement to some module ( Packager one ideally ) and then target module itself adds its own packages and as result everything needed is installed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040#c14
Fabian Vogt
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040
http://bugzilla.opensuse.org/show_bug.cgi?id=1140040#c25
Martin Loviska
participants (1)
-
bugzilla_noreply@novell.com