[Bug 1402005] Re: agent-state-info: 'error executing lxc-start: command get_cgroup failed to receive response'

I don't have an easy way to repro, all this occurs fairly regularly on our jenkins slave. Ubuntu 14.04 LTS (GNU/Linux 3.13.0-29-generic x86_64) juju version: 1.20.13-trusty-amd64 1 ppa installed: http://ppa.launchpad.net/juju/stable/ubuntu $ dpkg -l | egrep -e (lxc|apparmor|cgmanager) ii

[Bug 1402005] Re: agent-state-info: 'error executing lxc-start: command get_cgroup failed to receive response'

I don't have an easy way to repro, all this occurs fairly regularly on our jenkins slave. Ubuntu 14.04 LTS (GNU/Linux 3.13.0-29-generic x86_64) juju version: 1.20.13-trusty-amd64 1 ppa installed: http://ppa.launchpad.net/juju/stable/ubuntu $ dpkg -l | egrep -e (lxc|apparmor|cgmanager) ii

[Bug 1583494] Re: Bogus fatal error during charm build

This was fixed here https://github.com/juju/charm- tools/commit/f183d17367b43f18b4c503a999193ad9a6ab768d but hasn't been released yet afaik. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583494

[Bug 1673443] Re: Packaging: Provide etcd package to provide distributed key value store on POWER

LP obliterated the formatting, see here instead: http://pastebin.ubuntu.com/24667709/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673443 Title: Packaging: Provide etcd package to provide

[Bug 1673443] Re: Packaging: Provide etcd package to provide distributed key value store on POWER

Here's what we have in the snap store today: TrackArch ChannelVersion Revision 2.3 amd64stable 2.3.8 55 candidate ^ ^ beta ^ ^ edge

[Bug 1673443] Re: Packaging: Provide etcd package to provide distributed key value store on POWER

Snap store has ppc64el builds for 2.3.8, 3.0.17, 3.1.10, and 3.2.8. `snapcraft status --arch ppc64el etcd | pastebinit` http://paste.ubuntu.com/25664865/ ** Changed in: etcd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of

[Bug 1712954] Re: upgrade to 1.13

We did some testing of docker 1.13.1 with CDK this week and it doesn't work out-of-the-box, at least not with Flannel on AWS (and Flannel is our default overlay at the moment). TL;DR is there's a new default iptables rule that breaks us. We can probably work around this in the charms, but for now

[Bug 1712954] Re: upgrade to 1.13

CDK has been updated to work with docker 1.13.1 - no need to block on k8s any longer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712954 Title: upgrade to 1.13 To manage notifications about

[Bug 1794396] Re: upgrade to docker 18.06

k8s team needs a bit more time to test on bionic. Will do that asap and report back here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794396 Title: upgrade to docker 18.06 To manage

[Bug 1794396] Re: upgrade to docker 18.06

k8s team has finished testing and we're +1 on moving this to bionic- updates. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1794396] Re: upgrade to docker 18.06

The k8s team have finished testing the package in xenial-proposed and are +1 on moving it to xenial-updates. Not removing verification tags since mwh has not yet commented. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1815683] Re: update to docker 18.09.2

Canonical Kubernetes team has verified docker.io 18.09.2 with the Charmed Distribution of Kubernetes on Xenial (using the package from xenial-proposed) and Bionic (using the package from bionic proposed). -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1851676] Re: dmidecode decodes /sys/class/dmi/id/product_serial incorrectly

Hi Peter, can you elaborate on this part please: "manifests itself by breaking provisioning in Kubernetes." Can you describe the behavior you're seeing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1851676] Re: dmidecode decodes /sys/class/dmi/id/product_serial incorrectly

We could potentially patch Charmed Kubernetes against this by not reading /sys/class/dmi/id/product_uuid (https://github.com/charmed- kubernetes/charm-kubernetes- master/blob/master/reactive/kubernetes_master.py#L2244), but instead using the workaround published by vmware at

[Bug 1851676] Re: dmidecode decodes /sys/class/dmi/id/product_serial incorrectly

Peter, Pedro, thanks for the extra detail. After reading https://github.com/kubernetes/kubernetes/issues/58927, I agree that we won't be able to fix this in Charmed Kubernetes directly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1860639] Re: Update arm64 and s390x package versions

Sorry if I'm mistaken or reading this wrong, I was looking at https://packages.ubuntu.com/bionic/containerd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860639 Title: Update arm64 and s390x

[Bug 1860639] [NEW] Update arm64 and s390x package versions

Public bug reported: Would it be possible to get a more recent version of containerd in the archive for arm64 and s390x? Right now the current version for amd64 is 1.2.6, while the version of arm64 and s390x (and ppc64el) is lagging significantly behind at 0.2.5. ** Affects: containerd (Ubuntu)