August 2023 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1173484] rebootmgrctl is-active do not retcode 1 on success
by bugzilla_noreply＠suse.com 31 Aug '23

31 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1173484 https://bugzilla.suse.com/show_bug.cgi?id=1173484#c7 --- Comment #7 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2023:3503-1: An update that has four recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1172518, 1173484, 1186510, 1197850 Sources used: openSUSE Leap 15.4 (src): rebootmgr-1.3.1-150400.9.3.4 openSUSE Leap 15.5 (src): rebootmgr-1.3.1-150400.9.3.4 Transactional Server Module 15-SP4 (src): rebootmgr-1.3.1-150400.9.3.4 Transactional Server Module 15-SP5 (src): rebootmgr-1.3.1-150400.9.3.4 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214773] ignition-fetch-offline failed on armv7l
by bugzilla_noreply＠suse.com 30 Aug '23

30 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214773 https://bugzilla.suse.com/show_bug.cgi?id=1214773#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kubic-bugs(a)opensuse.org |fvogt(a)suse.com CC| |fvogt(a)suse.com Component|MicroOS |Kernel Status|NEW |IN_PROGRESS --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- > I've tried to enable it, but it seems that it is unsupported on armv7l architecture due to conflict with CONFIG_NO_IOPORT_MAP=y in the kernel config. I think this can be avoided by just disabling non-MMIO ports if CONFIG_HAS_IOPORT_MAP=n. I'll try a patch. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214773] New: ignition-fetch-offline failed on armv7l
by bugzilla_noreply＠suse.com 30 Aug '23

30 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214773 Bug ID: 1214773 Summary: ignition-fetch-offline failed on armv7l Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, I am running openSUSE-MicroOS.armv7l-16.0.0-kvm-and-xen-Snapshot20230802.qcow2 image on armv7l KVM. I see that ignition-fetch-offline.service is failed (and whole the boot) in initrd due to the following: Aug 30 07:04:59 localhost ignition[427]: op(1): [started] loading QEMU firmware config module Aug 30 07:04:59 localhost ignition[427]: op(1): executing: "modprobe" "qemu_fw_cfg" Aug 30 07:04:59 localhost ignition[427]: op(1): [failed] loading QEMU firmware config module: exit status 1: Cmd: "modprobe" "qemu_fw_cfg" Stdout: "" Stderr: "modprobe: FATAL: Module qemu_fw_cfg not found in directory /usr/lib/modules/6.4.6-1-default\n" Aug 30 07:04:59 localhost ignition[427]: failed to fetch config: exit status 1: Cmd: "modprobe" "qemu_fw_cfg" Stdout: "" Stderr: "modprobe: FATAL: Module qemu_fw_cfg not found in directory /usr/lib/modules/6.4.6-1-default\n" Aug 30 07:04:59 localhost ignition[427]: failed to acquire config: exit status 1: Cmd: "modprobe" "qemu_fw_cfg" Stdout: "" Stderr: "modprobe: FATAL: Module qemu_fw_cfg not found in directory /usr/lib/modules/6.4.6-1-default\n" Aug 30 07:04:59 localhost ignition[427]: Ignition failed: exit status 1: Cmd: "modprobe" "qemu_fw_cfg" Stdout: "" Stderr: "modprobe: FATAL: Module qemu_fw_cfg not found in directory /usr/lib/modules/6.4.6-1-default\n" Aug 30 07:04:59 localhost systemd[1]: ignition-fetch-offline.service: Main process exited, code=exited, status=1/FAILURE Aug 30 07:04:59 localhost systemd[1]: ignition-fetch-offline.service: Failed with result 'exit-code'. Aug 30 07:04:59 localhost systemd[1]: Failed to start Ignition (fetch-offline). Aug 30 07:04:59 localhost systemd[1]: ignition-fetch-offline.service: Triggering OnFailure= dependencies. Issue here that qemu_fw_cfg.ko kernel module is missed on armv7l architecture. I've tried to enable it, but it seems that it is unsupported on armv7l architecture due to conflict with CONFIG_NO_IOPORT_MAP=y in the kernel config. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214469] New: Networking Issue After Transactional Update
by bugzilla_noreply＠suse.com 24 Aug '23

24 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214469 Bug ID: 1214469 Summary: Networking Issue After Transactional Update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: samcon(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868938 --> https://bugzilla.suse.com/attachment.cgi?id=868938&action=edit pre-update Summary: After performing a transactional update on an openSUSE Tumbleweed system, the networking bridges and virtual interfaces were not functioning. As a result, the affected device, which serves as a VM-host for an opnsense firewall, lost its network connectivity. Rolling back to an older snapshot and disabling the transactional-update.timer service was required to restore networking functionality. The issue had significant impact as all devices on the network lost internet connectivity. Manual intervention in the form of a keyboard and monitor connection was needed to perform the rollback. Description: On [Date], I performed a transactional update on my openSUSE Tumbleweed system. The system was being used as a VM-host for an opnsense firewall, which plays a critical role in managing network traffic for my network. The transactional update was carried out using the standard update procedure. After the update was applied and the system rebooted, it was immediately apparent that there were issues with the networking configuration. None of the networking bridges or virtual interfaces were functioning as expected. This resulted in a complete loss of network connectivity for all the virtual machines running on the host, as well as the host itself. Due to the severity of the issue and the impact it had on the network, I decided to manually intervene by connecting a keyboard and monitor to the affected system. After accessing the system locally, I attempted to diagnose the problem. It became evident that the issue was related to the recent transactional update, as rolling back to an older snapshot of the system resulted in the restoration of networking functionality. This process involved using the system's snapshot manager to revert to a state prior to the update. Additionally, to prevent this issue from occurring again in the future, I disabled the transactional-update.timer service. While this action helped avoid further disruption, it's important to note that transactional updates are a critical part of openSUSE Tumbleweed's update process and should ideally work without causing networking issues. Impact: The impact of this issue was significant. Due to the loss of networking bridges and virtual interfaces, all the devices on the network, including the virtual machines hosted on the affected system, lost internet connectivity. This disruption lasted until I could manually intervene, rollback to an older snapshot, and disable the transactional update timer. The incident led to downtime, network interruptions, and required manual intervention, which is not ideal for a system that's intended to provide stable and uninterrupted network services. Steps to Reproduce: - Install openSUSE Tumbleweed on a system configured as a VM-host. - Set up networking bridges and virtual interfaces. - Perform a transactional update using the standard update procedure. - Reboot the system after the update. - Observe that networking bridges and virtual interfaces are not functioning as expected, resulting in a loss of network connectivity for all devices. Expected Results: After a transactional update, the system's networking configuration, including bridges and virtual interfaces, should remain intact, and the network connectivity for all devices should not be affected. Additional Information: - Intel Pentium N6005, 4x Intel i226-V 2.5Gb LAN - Output of relevant commands`ip addr show` see attached -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1214469] Networking Issue After Transactional Update
by bugzilla_noreply＠suse.com 22 Aug '23

22 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214469 https://bugzilla.suse.com/show_bug.cgi?id=1214469#c5 --- Comment #5 from Santiago Zarate <santiago.zarate(a)suse.com> --- (In reply to Samuel Conway from comment #0) > Created attachment 868938 [details] > pre-update > > Summary: > After performing a transactional update on an openSUSE Tumbleweed system, > the networking bridges and virtual interfaces were not functioning. As a > result, the affected device, which serves as a VM-host for an opnsense > firewall, lost its network connectivity. Rolling back to an older snapshot > and disabling the transactional-update.timer service was required to restore > networking functionality. The issue had significant impact as all devices on > the network lost internet connectivity. Manual intervention in the form of a > keyboard and monitor connection was needed to perform the rollback. > > Description: > On [Date], I performed a transactional update on my openSUSE Tumbleweed > system. The system was being used as a VM-host for an opnsense firewall, > which plays a critical role in managing network traffic for my network. The > transactional update was carried out using the standard update procedure. > > After the update was applied and the system rebooted, it was immediately > apparent that there were issues with the networking configuration. None of > the networking bridges or virtual interfaces were functioning as expected. > This resulted in a complete loss of network connectivity for all the virtual > machines running on the host, as well as the host itself. > > Due to the severity of the issue and the impact it had on the network, I > decided to manually intervene by connecting a keyboard and monitor to the > affected system. After accessing the system locally, I attempted to diagnose > the problem. It became evident that the issue was related to the recent > transactional update, as rolling back to an older snapshot of the system > resulted in the restoration of networking functionality. This process > involved using the system's snapshot manager to revert to a state prior to > the update. > > Additionally, to prevent this issue from occurring again in the future, I > disabled the transactional-update.timer service. While this action helped > avoid further disruption, it's important to note that transactional updates > are a critical part of openSUSE Tumbleweed's update process and should > ideally work without causing networking issues. > > Impact: > The impact of this issue was significant. Due to the loss of networking > bridges and virtual interfaces, all the devices on the network, including > the virtual machines hosted on the affected system, lost internet > connectivity. This disruption lasted until I could manually intervene, > rollback to an older snapshot, and disable the transactional update timer. > The incident led to downtime, network interruptions, and required manual > intervention, which is not ideal for a system that's intended to provide > stable and uninterrupted network services. > > Steps to Reproduce: > > - Install openSUSE Tumbleweed on a system configured as a VM-host. > - Set up networking bridges and virtual interfaces. > - Perform a transactional update using the standard update procedure. > - Reboot the system after the update. > - Observe that networking bridges and virtual interfaces are not functioning > as expected, resulting in a loss of network connectivity for all devices. > > Expected Results: > After a transactional update, the system's networking configuration, > including bridges and virtual interfaces, should remain intact, and the > network connectivity for all devices should not be affected. > > Additional Information: > - Intel Pentium N6005, 4x Intel i226-V 2.5Gb LAN > - Output of relevant commands`ip addr show` see attached Can you describe the network configuration? I have a personal host that's also a VM host, and is also a VPN (WG) gateway and haven't had issues, despite it having two VMs having bridged networks flowchart TD A[Internet] --> system[host network adapter] system --> bridge{libvirtd-bridged network} bridge --> VM1 bridge --> VM2 bridge --> VM3 (See routed network on hetzner: https://docs.hetzner.com/robot/dedicated-server/ip/additional-ip-adresses/) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214469] Networking Issue After Transactional Update
by bugzilla_noreply＠suse.com 22 Aug '23

22 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214469 https://bugzilla.suse.com/show_bug.cgi?id=1214469#c3 --- Comment #3 from Thorsten Kukuk <kukuk(a)suse.com> --- I doubt this has anything to do with transactional-update at all. Here are many MicroOS production machines and none shows a similar behavior. I'm afraid you need to go through the log files and search for the error message, why your network interfaces don't come up anymore. That's the only way to find out, which updated packages breaks your network setup. Some SELinux failures in "transactional-update shell" are unrelated. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214401] New: SelfInstall Image - No network when Combustion running
by bugzilla_noreply＠suse.com 18 Aug '23

18 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1214401 Bug ID: 1214401 Summary: SelfInstall Image - No network when Combustion running Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: malcolmlewis(a)linuxmail.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi Testing the latest SelfInstall image (openSUSE-MicroOS.x86_64-16.0.0-SelfInstall-Snapshot20230816.raw.xz) on a bare-metal test system there is no longer network access for Combustion to use zypper to add some additional packages. I just get; Error code: Connection failed Error message: Could not resolve host: download.opensuse.org The network only comes up after the first reboot. Note: This was working fine prior to my python-kiwi bug with missing partprobe. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1212959] SelfInstall Image - Failed to create partition table
by bugzilla_noreply＠suse.com 17 Aug '23

17 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1212959 https://bugzilla.suse.com/show_bug.cgi?id=1212959#c8 Malcolm Lewis <malcolmlewis(a)linuxmail.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Malcolm Lewis <malcolmlewis(a)linuxmail.org> --- Hi All, just tested today's snapshot (20230816) and this issue is now resolved. Install completes and btrfs file system is using the whole disk as expected. Many thanks to all involved. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

1 0

[Bug 1212959] SelfInstall Image - Failed to create partition table
by bugzilla_noreply＠suse.com 15 Aug '23

15 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1212959 https://bugzilla.suse.com/show_bug.cgi?id=1212959#c7 Marcus Schäfer <marcus.schaefer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kubic-bugs@opensu | |se.org) | --- Comment #7 from Marcus Schäfer <marcus.schaefer(a)suse.com> --- Hi > I've not seen an update for python-kiwi appear as it's still on version v9.24.61? yep, on the list for today. Virt:App:Builder now has the Staging version which completed all integration test successfully, fingers crossed The submission to Factory was done in SR: 1103984 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

1 0

needinfo requested: [Bug 1212959] SelfInstall Image - Failed to create partition table
by bugzilla_noreply＠suse.com 14 Aug '23

14 Aug '23

Malcolm Lewis <malcolmlewis(a)linuxmail.org> has asked Kubic Bugs <kubic-bugs(a)opensuse.org> for needinfo: Bug 1212959: SelfInstall Image - Failed to create partition table https://bugzilla.suse.com/show_bug.cgi?id=1212959 --- Comment #6 from Malcolm Lewis <malcolmlewis(a)linuxmail.org> --- (In reply to Malcolm Lewis from comment #5) > @All, thanks for fixing this issue, will wait for the next snapshot release > and re-test to confirm. @Marcus Schäfer I've not seen an update for python-kiwi appear as it's still on version v9.24.61? From the PR you indicated it should have appeared in version v9.25.3? <https://build.opensuse.org/package/show/Virtualization:Appliances:Builder/p… on-kiwi> Or is the updated version coming from a different build repository?

1 0