Comment 2 for bug 1852138

Revision history for this message
Camille Rodriguez (camille.rodriguez) wrote :

I tried one more time. Wiped lxd, everything, and reinstalled lxd as a cluster on 3 nodes, and then deployed CDK.

If fails with the error "Failed to get current cluster nodes: failed to begin transaction: not an error" pretty quickly into the deployment of CDK.

Here's the logs in /var/snap/lxd/common/lxd/logs/lxd.log between the start of the deployment to the failure.

t=2019-11-12T22:00:29+0000 lvl=info msg="Creating container" ephemeral=false name=juju-c54a63-0 project=default
t=2019-11-12T22:00:29+0000 lvl=info msg="Created container" ephemeral=false name=juju-c54a63-0 project=default
t=2019-11-12T22:00:32+0000 lvl=info msg="Starting container" action=start created=2019-11-12T22:00:29+0000 ephemeral=false name=juju-c54a63-0 project=default stateful=false used=1970-01-01T00:00:00+0000
t=2019-11-12T22:00:33+0000 lvl=info msg="Started container" action=start created=2019-11-12T22:00:29+0000 ephemeral=false name=juju-c54a63-0 project=default stateful=false used=1970-01-01T00:00:00+0000
t=2019-11-12T22:01:44+0000 lvl=warn msg="Dqlite server proxy Unix -> TLS: read unix @->@00490: use of closed network connection"
t=2019-11-12T22:01:44+0000 lvl=warn msg="Dqlite server proxy Unix -> TLS: read unix @->@00490: use of closed network connection"
t=2019-11-12T22:01:44+0000 lvl=warn msg="Excluding offline node from refresh: {ID:1 Address:139.178.67.162:8443 RaftID:1 Raft:true LastHeartbeat:2019-11-12 22:00:41.65550536 +0000 UTC Online:false updated:false}"
t=2019-11-12T22:01:44+0000 lvl=eror msg="Failed to load instances for snapshot expiry" err="failed to begin transaction: not an error"
t=2019-11-12T22:01:44+0000 lvl=warn msg="Failed to get current cluster nodes: failed to begin transaction: not an error"
t=2019-11-12T22:01:44+0000 lvl=eror msg="Failed to load containers for scheduled snapshots" err="failed to begin transaction: not an error"
t=2019-11-12T22:01:44+0000 lvl=eror msg="Error refreshing forkdns: failed to begin transaction: not an error"
t=2019-11-12T22:01:45+0000 lvl=warn msg="Failed to get current cluster nodes: failed to begin transaction: not an error"
t=2019-11-12T22:01:45+0000 lvl=warn msg="Failed to get current cluster nodes: failed to begin transaction: not an error"
t=2019-11-12T22:01:46+0000 lvl=warn msg="Failed to get current cluster nodes: failed to begin transaction: not an error"
t=2019-11-12T22:01:47+0000 lvl=warn msg="Failed to get current cluster nodes: failed to begin transaction: not an error"
t=2019-11-12T22:01:48+0000 lvl=warn msg="Failed to get current cluster nodes: failed to begin transaction: not an error"
t=2019-11-12T22:01:49+0000 lvl=warn msg="Failed to get current cluster nodes: failed to begin transaction: not an error"

On the juju side, the latest logs:

machine-0: 22:07:36 ERROR juju.worker.dependency "machiner" manifold worker returned unexpected error: cannot update observed network config: cannot get provider network config: failed to construct a model from config: failed to begin transaction: not an error
machine-0: 22:07:39 ERROR juju.worker.dependency "broker-tracker" manifold worker returned unexpected error: cannot load machine machine-0 from state: failed to begin transaction: not an error
machine-0: 22:07:40 WARNING juju.cmd.jujud determining kvm support: INFO: /dev/kvm does not exist
HINT: sudo modprobe kvm
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.15.0-46-generic/modules.dep.bin'
modprobe: FATAL: Module msr not found in directory /lib/modules/4.15.0-46-generic
: exit status 1
no kvm containers possible
machine-0: 22:07:40 ERROR juju.worker.dependency "unconverted-api-workers" manifold worker returned unexpected error: setting up container support: cannot load machine machine-0 from state: failed to begin transaction: not an error
machine-0: 22:07:42 ERROR juju.worker.dependency "storage-provisioner" manifold worker returned unexpected error: watching block devices: getting backend: getting storage provider registry: failed to begin transaction: not an error
unit-easyrsa-0: 22:07:42 ERROR juju.worker.dependency "api-address-updater" manifold worker returned unexpected error: getting storage provider registry: failed to begin transaction: not an error
unit-easyrsa-0: 22:07:50 ERROR juju.worker.dependency "uniter" manifold worker returned unexpected error: failed to initialize uniter for "unit-easyrsa-0": getting storage provider registry: failed to begin transaction: not an error
machine-1: 22:08:05 ERROR juju.worker.dependency "broker-tracker" manifold worker returned unexpected error: cannot load machine machine-1 from state: failed to begin transaction: not an error
machine-1: 22:08:07 ERROR juju.worker.dependency "storage-provisioner" manifold worker returned unexpected error: watching block devices: getting backend: getting storage provider registry: failed to begin transaction: not an error
unit-etcd-0: 22:08:09 ERROR juju.worker.dependency "uniter" manifold worker returned unexpected error: failed to initialize uniter for "unit-etcd-0": getting storage provider registry: failed to begin transaction: not an error
machine-1: 22:07:10 ERROR juju.worker.dependency "machiner" manifold worker returned unexpected error: cannot update observed network config: cannot get provider network config: failed to construct a model from config: failed to begin transaction: not an error
machine-1: 22:08:10 WARNING juju.cmd.jujud determining kvm support: INFO: /dev/kvm does not exist
HINT: sudo modprobe kvm
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.15.0-46-generic/modules.dep.bin'
modprobe: FATAL: Module msr not found in directory /lib/modules/4.15.0-46-generic
: exit status 1
no kvm containers possible
machine-1: 22:08:10 ERROR juju.worker.dependency "unconverted-api-workers" manifold worker returned unexpected error: setting up container support: cannot load machine machine-1 from state: failed to begin transaction: not an error
unit-etcd-0: 22:08:10 ERROR juju.worker.dependency "api-address-updater" manifold worker returned unexpected error: getting storage provider registry: failed to begin transaction: not an error
machine-1: 22:08:15 ERROR juju.worker.dependency "machiner" manifold worker returned unexpected error: cannot update observed network config: cannot get provider network config: failed to construct a model from config: failed to begin transaction: not an error
machine-0: 22:08:37 ERROR juju.worker.dependency "machiner" manifold worker returned unexpected error: cannot update observed network config: cannot get provider network config: failed to construct a model from config: failed to begin transaction: not an error
machine-0: 22:08:40 ERROR juju.worker.dependency "broker-tracker" manifold worker returned unexpected error: cannot load machine machine-0 from state: failed to begin transaction: not an error
machine-0: 22:08:41 WARNING juju.cmd.jujud determining kvm support: INFO: /dev/kvm does not exist
HINT: sudo modprobe kvm
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.15.0-46-generic/modules.dep.bin'
modprobe: FATAL: Module msr not found in directory /lib/modules/4.15.0-46-generic
: exit status 1
no kvm containers possible
machine-0: 22:08:41 ERROR juju.worker.dependency "unconverted-api-workers" manifold worker returned unexpected error: setting up container support: cannot load machine machine-0 from state: failed to begin transaction: not an error
machine-0: 22:08:44 ERROR juju.worker.dependency "storage-provisioner" manifold worker returned unexpected error: watching block devices: getting backend: getting storage provider registry: failed to begin transaction: not an error

And I cannot retrieve lxd cluster info anymore, it returns the same
"Error: failed to begin transaction: not an error"