[Bug 1168390] New: Update disables kubelet again
http://bugzilla.suse.com/show_bug.cgi?id=1168390 Bug ID: 1168390 Summary: Update disables kubelet again Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kubic Assignee: kubic-bugs@opensuse.org Reporter: kukuk@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- (64/66) Removing kubernetes-kubelet-1.17.2-1.4.x86_64 [.....done] Additional rpm output: Removed /etc/systemd/system/multi-user.target.wants/kubelet.service. Of course, cluster is not coming up again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1168390
Thorsten Kukuk
http://bugzilla.suse.com/show_bug.cgi?id=1168390
http://bugzilla.suse.com/show_bug.cgi?id=1168390#c1
--- Comment #1 from Richard Brown
(64/66) Removing kubernetes-kubelet-1.17.2-1.4.x86_64 [.....done] Additional rpm output: Removed /etc/systemd/system/multi-user.target.wants/kubelet.service.
Of course, cluster is not coming up again.
Bug report says 'again', but the package above (1.17.2) wasn't present in any recent snapshots (including the snapshots since the first time we fixed that, which used kubernetes 1.17.4) Is it possible this machine didn't get any updates in the intervening time, so we're jumping from old-broken-pkg to current-pkg without the intervening 1.17.4 snapshots which were mandatory for the new upgrade procedure to work? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1168390
http://bugzilla.suse.com/show_bug.cgi?id=1168390#c2
Richard Brown
http://bugzilla.suse.com/show_bug.cgi?id=1168390
http://bugzilla.suse.com/show_bug.cgi?id=1168390#c3
Thorsten Kukuk
(In reply to Thorsten Kukuk from comment #0)
(64/66) Removing kubernetes-kubelet-1.17.2-1.4.x86_64 [.....done] Additional rpm output: Removed /etc/systemd/system/multi-user.target.wants/kubelet.service.
Of course, cluster is not coming up again.
Bug report says 'again',
Yes, we had that already and we added kubelet to preset list.
but the package above (1.17.2) wasn't present in any recent snapshots (including the snapshots since the first time we fixed that, which used kubernetes 1.17.4)
Is it possible this machine didn't get any updates in the intervening time, so we're jumping from old-broken-pkg to current-pkg without the intervening 1.17.4 snapshots which were mandatory for the new upgrade procedure to work?
All machines were up-to-date and migrated to 1.17.4. There was never a package called kubernetes-kubelet-1.17.4. And the old package got "removed", so I guess it's your weakremover change? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1168390
http://bugzilla.suse.com/show_bug.cgi?id=1168390#c4
Fabian Vogt
http://bugzilla.suse.com/show_bug.cgi?id=1168390
http://bugzilla.suse.com/show_bug.cgi?id=1168390#c5
--- Comment #5 from Fabian Vogt
https://bugzilla.suse.com/show_bug.cgi?id=1168390
https://bugzilla.suse.com/show_bug.cgi?id=1168390#c7
--- Comment #7 from OBSbugzilla Bot
https://bugzilla.suse.com/show_bug.cgi?id=1168390
https://bugzilla.suse.com/show_bug.cgi?id=1168390#c8
--- Comment #8 from Swamp Workflow Management
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com