September 2019 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[kubic-bugs] [Bug 1151083] New: With ignition.firstboot, boot is delayed by 1m30s if there is no fs with ignition label
by bugzilla_noreply＠novell.com 17 Sep '19

17 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1151083 Bug ID: 1151083 Summary: With ignition.firstboot, boot is delayed by 1m30s if there is no fs with ignition label Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: iforster(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- In some not unlikely cases, ignition is installed but not actually used. In those cases, booting should not be delayed by 1m30s. In /usr/lib/dracut/modules.d/30ignition: Add timeout.conf: [Unit] JobTimeoutSec=2 Edit module-setup.sh, add: inst_simple "$moddir/timeout.conf" "$systemdsystemunitdir/dev-disk-by\x2dlabel-ignition.device.d/timeout.conf" -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[kubic-bugs] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 15 Sep '19

15 Sep '19

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.novell.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.novell.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&… Or, you can use the general query page, at http://bugzilla.novell.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! Upstream kubeadm page does not list openSUSE Kubic as supported platform -> http://bugzilla.novell.com/show_bug.cgi?id=1119508 tmpfiles.d/kubernetes.conf uses legacy path, systemd complaining -> http://bugzilla.novell.com/show_bug.cgi?id=1124129 Tumbleweed packages not visible in MicroOS installer -> http://bugzilla.novell.com/show_bug.cgi?id=1137460 kubelet.service tries to start even without config file -> http://bugzilla.novell.com/show_bug.cgi?id=1146372 kubic image does not call cloud-init -> http://bugzilla.novell.com/show_bug.cgi?id=1146802 -- To unsubscribe, e-mail: kubic-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kubic-bugs+owner(a)opensuse.org

1 0

[kubic-bugs] [Bug 1149392] 'kubeadm init' fails to start inside openQA on aarch64
by bugzilla_noreply＠novell.com 12 Sep '19

12 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1149392 http://bugzilla.suse.com/show_bug.cgi?id=1149392#c6 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Thorsten Kukuk <kukuk(a)suse.com> --- The fixed package got accepted. Don't know if openQA is already using a proxy to test the internal packages or if it is only using the official released ones. In the later case, we need to release at first an arm snapshot with the fix to see fixed containers. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 08 Sep '19

08 Sep '19

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.novell.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.novell.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&… Or, you can use the general query page, at http://bugzilla.novell.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! Upstream kubeadm page does not list openSUSE Kubic as supported platform -> http://bugzilla.novell.com/show_bug.cgi?id=1119508 tmpfiles.d/kubernetes.conf uses legacy path, systemd complaining -> http://bugzilla.novell.com/show_bug.cgi?id=1124129 Tumbleweed packages not visible in MicroOS installer -> http://bugzilla.novell.com/show_bug.cgi?id=1137460 kubelet.service tries to start even without config file -> http://bugzilla.novell.com/show_bug.cgi?id=1146372 kubic image does not call cloud-init -> http://bugzilla.novell.com/show_bug.cgi?id=1146802 -- To unsubscribe, e-mail: kubic-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kubic-bugs+owner(a)opensuse.org

1 0

[kubic-bugs] [Bug 1149392] 'kubeadm init' fails to start inside openQA on aarch64
by bugzilla_noreply＠novell.com 06 Sep '19

06 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1149392 http://bugzilla.suse.com/show_bug.cgi?id=1149392#c5 --- Comment #5 from Thorsten Kukuk <kukuk(a)suse.com> --- # kubectl get nodes NAME STATUS ROLES AGE VERSION pi3-1 Ready master 5m2s v1.15.2 Only have one Raspberry Pi3 ;) for testing, but on that it's now working. Should work in general after the fixed package/containers are released. The working images of the devel project can be tested with kubeadm init --image-repository=registry.opensuse.org/devel/kubic/containers/container_arm/kubic -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1149701] New: Ignition needs to autodetect the platform
by bugzilla_noreply＠novell.com 06 Sep '19

06 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1149701 Bug ID: 1149701 Summary: Ignition needs to autodetect the platform Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: iforster(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- Currently the platform ignition runs on has to be specified manually on the kernel cmdline with ignition.platform.id and not specifying it at all breaks booting completely. What needs to happen instead is that if ignition.platform.id is not specified by ignition is supposed to run, it makes some educated guesses which platform it is running on (vmware, qemu, openstack, gce, etc.) and uses metal as fallback. ds-identify from cloud-init can serve as inspiration: https://github.com/cloud-init/cloud-init/blob/master/tools/ds-identify -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[kubic-bugs] [Bug 1149392] 'kubeadm init' fails to start inside openQA on aarch64
by bugzilla_noreply＠novell.com 06 Sep '19

06 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1149392 http://bugzilla.suse.com/show_bug.cgi?id=1149392#c4 --- Comment #4 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1149392) was mentioned in https://build.opensuse.org/request/show/728700 Factory / etcd-for-k8s-image -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1149392] 'kubeadm init' fails to start inside openQA on aarch64
by bugzilla_noreply＠novell.com 06 Sep '19

06 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1149392 http://bugzilla.suse.com/show_bug.cgi?id=1149392#c3 --- Comment #3 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Guillaume GARDET from comment #2) > In etcd.spec, we have: > echo -e "\n#Enable arm64\nETCD_UNSUPPORTED_ARCH=arm64\n" >> > %{buildroot}%{_fillupdir}/sysconfig.%{name} > > What is missing then? The "etcd" package is designed to run by systemd standalone on a system, but with Kubic, we use a containerized control plane. So the etcd.service isn't used at all, but etcd started directly. Additional, since the normal etcd packaging is incompatible to what kubeadm expects in a control-plane container, we have the etcd-for-k8s-image package. I need to add a wrapper script there which sets the environment variable for the container. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1149392] 'kubeadm init' fails to start inside openQA on aarch64
by bugzilla_noreply＠novell.com 06 Sep '19

06 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1149392 http://bugzilla.suse.com/show_bug.cgi?id=1149392#c2 --- Comment #2 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Thorsten Kukuk from comment #1) > I assume in openQA the etcd container does not start, too: > 2019-09-05T19:58:46.104209786+00:00 stderr F 2019-09-05 19:58:46.103705 E | > etcdmain: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=arm64 > set. In etcd.spec, we have: echo -e "\n#Enable arm64\nETCD_UNSUPPORTED_ARCH=arm64\n" >> %{buildroot}%{_fillupdir}/sysconfig.%{name} What is missing then? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kubic-bugs] [Bug 1149392] 'kubeadm init' fails to start inside openQA on aarch64
by bugzilla_noreply＠novell.com 05 Sep '19

05 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1149392 http://bugzilla.suse.com/show_bug.cgi?id=1149392#c1 --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- I assume in openQA the etcd container does not start, too: 2019-09-05T19:58:46.104209786+00:00 stderr F 2019-09-05 19:58:46.103705 E | etcdmain: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=arm64 set. -- You are receiving this mail because: You are the assignee for the bug.

1 0