snap-kube-apiserver

1.19-rc0 configure hooks broken

Bug #1887193 reported by Cory Johns
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snap-kube-apiserver
Fix Committed
High
George Kraft
snap-kube-controller-manager
New
High
George Kraft
snap-kube-proxy
New
High
George Kraft
snap-kube-scheduler
New
High
George Kraft
snap-kubelet
New
High
George Kraft

Bug Description

Attempting to install the kube-apiserver snap currently in 1.19/candidate (rev 1709) fails with the following:

ubuntu@ip-172-31-82-63:~$ sudo snap install kube-apiserver --channel=1.19/candidate
error: cannot perform the following tasks:
- Run configure hook of "kube-apiserver" snap if present (run hook "configure": error: error running snapctl: invalid option name: "add-dir-header,")

George Kraft (cynerva)
no longer affects: charm-kubernetes-master
Changed in snap-kube-apiserver:
assignee: nobody → George Kraft (cynerva)
status: New → In Progress
importance: Undecided → High
Revision history for this message
George Kraft (cynerva) wrote :

Committed:
https://git.launchpad.net/snap-kube-apiserver/commit/?id=e98646186e79ae1d10125dccfbd24b78118395e0
https://git.launchpad.net/snap-kube-controller-manager/commit/?id=6900d218376f65823e51bde70a779d7ebdc1084e
https://git.launchpad.net/snap-kube-scheduler/commit/?id=0a995f9e80f7d65b24a01b9f557456f91ae417ae
https://git.launchpad.net/snap-kubelet/commit/?id=96d1ee8cd178724e9c994622a6c6c8fa4d4c2864
https://git.launchpad.net/snap-kube-proxy/commit/?id=d150816b82f5d2c21ace2ce48cb46cf642f25989

summary: - kube-apiserver snap for 1.19-rc0 broken
+ 1.19-rc0 configure hooks broken
no longer affects: snap-kube-controller-manager
Changed in snap-kube-controller-manager:
assignee: nobody → George Kraft (cynerva)
Changed in snap-kube-proxy:
assignee: nobody → George Kraft (cynerva)
Changed in snap-kube-scheduler:
assignee: nobody → George Kraft (cynerva)
Changed in snap-kubelet:
assignee: nobody → George Kraft (cynerva)
Changed in snap-kube-controller-manager:
importance: Undecided → High
Changed in snap-kube-proxy:
importance: Undecided → High
Changed in snap-kube-scheduler:
importance: Undecided → High
Changed in snap-kubelet:
importance: Undecided → High
Changed in snap-kube-apiserver:
status: In Progress → Fix Committed
Revision history for this message
George Kraft (cynerva) wrote :

Follow-up fix for a similar error on kube-scheduler:

https://git.launchpad.net/snap-kube-apiserver/commit/?id=de73068ad7f506ed4f340f31a07a29f52173fc7b
https://git.launchpad.net/snap-kube-scheduler/commit/?id=f3fea42288c2b5cf4f5a289990a50cfdaec69a81
https://git.launchpad.net/snap-kube-controller-manager/commit/?id=ee7aac029d195da30522af8c510b377ac55e90f4
https://git.launchpad.net/snap-kubelet/commit/?id=4f9cb3004677aeeb64e9debf0bffa0b3d6ec4ffe
https://git.launchpad.net/snap-kube-proxy/commit/?id=346681d7831394b4efb842cc75e880de23a82048

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.