November 2018 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[kubic-bugs] [Bug 1085619] New: Softlockup with btrfs and kubic (CaaSP on openSUSE)
by bugzilla_noreply＠novell.com 16 Sep '21

16 Sep '21

http://bugzilla.suse.com/show_bug.cgi?id=1085619 Bug ID: 1085619 Summary: Softlockup with btrfs and kubic (CaaSP on openSUSE) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kubic Assignee: jeffm(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org, lpechacek(a)suse.com Found By: --- Blocker: --- With current openSUSE Kubic builds (CaaSP based on openSUSE Tumbleweed), we seem to run into the same issue as with CaaSP v1: bsc#1041296 - admin node freezes - no shell after putting password into login prompt Could it be that the fixes are missing in the upstream kernel? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[kubic-bugs] [Bug 1115000] New: cloud-init in TW snapshots 1105 and 1106 do not populate /etc/resolv.conf
by bugzilla_noreply＠novell.com 26 Sep '19

26 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1115000 Bug ID: 1115000 Summary: cloud-init in TW snapshots 1105 and 1106 do not populate /etc/resolv.conf Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Tools Assignee: public-cloud-maintainers(a)suse.de Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- cloud-init do not seem to correctly populate /etc/resolv.conf After a boot of Kubic with the kubeadm system role, the resulting /etc/resolv.conf has "; Created by cloud-init on instance boot automatically, do not edit" followed by the usual "### /etc/resolv.conf file autogenerated by netconfig" preamble, but has no name resolver configured This results in a system that has no working name resolution https://openqa.opensuse.org/tests/788925#step/first_boot/23 All other networking seems to behave fine EXPECTED BEHAVIOUR cloud-init should correctly populate /etc/resolv.conf when configuring the network of a system WORKAROUND docker automatically disables cloud-inits network configuration by editing /etc/cloud/cloud.cfg.d/01-network.cfg - for non-docker runtimes Kubic intends to do something similar until this bug is fixed at least. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[kubic-bugs] [Bug 1114818] New: New kubeadm NTP screen does not prefill ntp.org pool servers
by bugzilla_noreply＠novell.com 30 Jul '19

30 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1114818 Bug ID: 1114818 Summary: New kubeadm NTP screen does not prefill ntp.org pool servers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: rbrown(a)suse.com QA Contact: jsrain(a)suse.com CC: kubic-bugs(a)opensuse.org, lslezak(a)suse.com Found By: --- Blocker: --- The new kubeadm NTP screen in Kubic does not correctly prefil the NTP server field as described in https://en.opensuse.org/Kubic:CaaSPInstallationComparision EXPECTED BEHAVIOUR: "NTP server (chrony) (prefill field with dhcp answer, if there is no dhcp, prefill with ntp pool server if allowed, else leave empty and warn if it stays empty, no hard error)" ACTUAL BEHAVIOUR: NTP Server field does prefil with DHCP answer when it's available, but when it's not available it does not prefill with ntp.org pool servers (eg. 0.opensuse.pool.ntp.org, 1.opensuse.pool.ntp.org, 2.opensuse.pool.ntp.org, etc) Also, there is a cosmetic error - the screen says "Admin node configuration" when it should say "kubeadm node configuration" (the kubeadm nodes are not always admin nodes) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[kubic-bugs] [Bug 1107283] New: Don't create /cloud-init-config subvolume by default
by bugzilla_noreply＠novell.com 06 May '19

06 May '19

http://bugzilla.suse.com/show_bug.cgi?id=1107283 Bug ID: 1107283 Summary: Don't create /cloud-init-config subvolume by default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com Found By: --- Blocker: --- /cloud-init-config makes only sense if customers create their own, golden images which contain a cloud-init configuration from the beginning. On YaST, autoyast installed or with our kiwi by us created images, this subvolume does not make much sense, as the user has to boot and login at first to create the config files in this directory. So it makes no sense to provide that directory by default. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kubic-bugs] [Bug 1076265] New: openSUSE-Tumbleweed-Kubic-release will never be updated
by bugzilla_noreply＠novell.com 04 Feb '19

04 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1076265 Bug ID: 1076265 Summary: openSUSE-Tumbleweed-Kubic-release will never be updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dleuenberger(a)suse.com Found By: --- Blocker: --- openSUSE-Tumbleweed-Kubic-release is only on the Kubic media, which means, it will never be updated. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kubic-bugs] [Bug 1105992] Transactional-Update broken in snapshot 20180824
by bugzilla_noreply＠novell.com 23 Nov '18

23 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1105992 http://bugzilla.suse.com/show_bug.cgi?id=1105992#c20 --- Comment #20 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1105992) was mentioned in https://build.opensuse.org/request/show/651388 15.0 / transactional-update -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kubic-bugs] [Bug 1105992] New: Transactional-Update broken in snapshot 20180824
by bugzilla_noreply＠novell.com 22 Nov '18

22 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1105992 Bug ID: 1105992 Summary: Transactional-Update broken in snapshot 20180824 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kubic Assignee: iforster(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- 0824 introduced transactional-update 2.6 https://build.opensuse.org/package/rdiff/openSUSE:Factory/transactional-upd… It's failing all tests and appears to be displaying incorrect behaviour https://openqa.opensuse.org/tests/742638#step/transactional_update/57 Compared to 0822 I'm noticing the following differences: https://openqa.opensuse.org/tests/741289#step/transactional_update/57 (note: the code for the test does not appear to have changed: https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/test… ) Update test #2 is meant to be a no-op, because it should be updating when there is nothing to do In 0822 the pointless `cleanup up` test produced the following logs: > # Result: > Checking for newer version. > transactional-update 2.6 started > Options: cleanup up > Separate /var detected. > Adding cleanup algorithm to snapshot #6 > Adding "important=yes" to snapshot #6 > zypper: nothing to update > transactional-update finished > trup-0- In 0824 the exact same test produces the following logs: > # Result: > Checking for newer version. > transactional-update 2.6 started > Options: cleanup up > Separate /var detected. > Adding cleanup algorithm to snapshot #6 > Adding "important=yes" to snapshot #6 > /usr/sbin/transactional-update: line 760: [: too many arguments > Creating read-only snapshot of current system state (#8) > Copying /etc state into snapshot /.snapshots/9/snapshot > Copying /etc state into snapshot /.snapshots/10/snapshot > Calling zypper up > Loading repository data... > Reading installed packages... > > Nothing to do. > Trying to rebuild kdump initrd > Please reboot your machine to activate the changes and avoid data loss. > transactional-update finished > trup-0- I find the following lines in 0824 suspicious, leading me to the questions below: > /usr/sbin/transactional-update: line 760: [: too many arguments Why does txl-upd now complain about too many arguments? > Creating read-only snapshot of current system state (#8) > Copying /etc state into snapshot /.snapshots/9/snapshot > Copying /etc state into snapshot /.snapshots/10/snapshot Why does txl-upd make 3 snapshots (8, 9, 10) even when there is nothing to do? Why does txl-upd make 2 snapshots for /etc? (This is less suspicious, I'm just curious) Bug marked as Major because it makes all of Kubics tests red ;) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[kubic-bugs] [Bug 1076265] openSUSE-Tumbleweed-Kubic-release will never be updated
by bugzilla_noreply＠novell.com 16 Nov '18

16 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1076265 http://bugzilla.opensuse.org/show_bug.cgi?id=1076265#c5 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |rbrown(a)suse.com --- Comment #5 from Richard Brown <rbrown(a)suse.com> --- Should be fixed after https://bugzilla.suse.com/show_bug.cgi?id=1116332 is resolved -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1116116] dex Version: was not built properly
by bugzilla_noreply＠novell.com 15 Nov '18

15 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1116116 http://bugzilla.suse.com/show_bug.cgi?id=1116116#c1 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |rbrown(a)suse.com Assignee|kubic-bugs(a)opensuse.org |jmassaguerpla(a)suse.com --- Comment #1 from Richard Brown <rbrown(a)suse.com> --- Assigning to the maintainer of caasp-dex (or at least the last person who touched it) and setting to P3 as suggested -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1116116] New: dex Version: was not built properly
by bugzilla_noreply＠novell.com 15 Nov '18

15 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1116116 Bug ID: 1116116 Summary: dex Version: was not built properly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: pgeorgiadis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Reproducer: ~~~~~~~~~~~~ * In TW: > zypper -n in caasp-dex; caasp-dex version > dex Version: was not built properly > Go Version: go1.10.2 > Go OS/ARCH: linux amd64 * Everywhere, using our container > drpaneas@ASRock-Intel-Ethernet:~> docker run -it --rm registry.opensuse.org/devel/caasp/kubic-container/container/kubic/caasp-dex… > dex Version: was not built properly > Go Version: go1.10.2 > Go OS/ARCH: linux amd64 This happens also for the caasp-dex CaaSP container image within our SUSE Registry. PS: priority up to P3 (after talking with Flavio). -- You are receiving this mail because: You are the assignee for the bug.

1 0