This bug is preventing Charmed Kubernetes from working with hacluster on
Ubuntu 20.04 (Focal).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To
** Changed in: charm-etcd
Importance: Undecided => Medium
** Changed in: charm-etcd
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891259
Title:
snap installation
We're aware of this issue and committed a fix back in March, but it
looks like we never released it.
See https://bugs.launchpad.net/etcd-snaps/+bug/1869232
** No longer affects: charm-etcd
** Changed in: etcd-snaps
Status: New => Fix Committed
--
You received this bug notification
** Also affects: charm-etcd
Importance: Undecided
Status: New
** Also affects: etcd-snaps
Importance: Undecided
Status: New
** No longer affects: cdk8s
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Removing charm-keepalived since I believe no changes are needed there.
It should pick up fixes once they are available on apt archives.
** No longer affects: charm-keepalived
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've tested containerd 1.3.3 in bionic-proposed with Charmed Kubernetes
1.17 and everything looks good on our end. Our validation tests passed
for both new deployments on containerd 1.3.3, and old deployments
upgraded from containerd 1.2.6 to 1.3.3.
>From my team's perspective, this is safe to
We need support for TLS auth with image registries that was added in
1.3.0: https://github.com/containerd/cri/issues/1143
** Bug watch added: github.com/containerd/cri/issues #1143
https://github.com/containerd/cri/issues/1143
--
You received this bug notification because you are a member of
Public bug reported:
Hey folks, we've got a Charmed Kubernetes bug[1] that requires us to run
containerd 1.3.0+ to fix. Can we get the apt package in bionic universe
updated to 1.3.1 or at least 1.3.0?
If possible, we would like to test the updated containerd package in
bionic-proposed before it
Attached docker service logs where the fork/exec error can be seen. Some
important times to consider:
~14:11:58 - docker v1.13.1 service starts
~14:36:00 - `apt install docker.io` upgrades docker to 17.03.2
~14:39:26 - Kubernetes starts trying to create new containers, fails
~14:52:18 - `service
This fails for me on xenial after upgrading from Docker v1.13.1 to
17.03.2-ce from xenial-proposed. Here's what I did:
1. Deploy a Canonical Distribution of Kubernetes cluster (which deploys worker
instances with Xenial and gets Docker v1.13.1 via `apt install docker.io`)
2. On all worker units:
Finally had a chance to try running confined kubelet with the
kubernetes-support interface in a live Kubernetes cluster. Attached a
script that more or less captures what I did.
Kubelet fails to come up with the following error:
error: failed to run Kubelet: failed to create kubelet: mkdir
Thanks for keeping this updated Jamie. Sorry for my lack of response,
this has been on my list for a long time but other stuff keeps coming
up. I am not able to devote time to testing this any time in the next
week.
I'll do my best to describe testing steps in case you want to give it a
go, but
Public bug reported:
While trying to install a snap, the configure hook failed:
$ snap install /home/ubuntu/cdk-addons_1.5.2_amd64.snap --dangerous
error: cannot perform the following tasks:
- Run configure hook of "cdk-addons" snap if present (run hook "configure":
error: cannot communicate
13 matches
Mail list logo
