failed to retrieve the template to clone: lxc container 1.21.3

Bug #1427302 reported by Larry Michel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
New
Undecided
Unassigned

Bug Description

This is for deploying OpenStack:

+ . ./pipeline_parameters
++ export OPENSTACK_RELEASE=juno
++ OPENSTACK_RELEASE=juno
++ export COMPUTE=nova-kvm
++ COMPUTE=nova-kvm
++ export BLOCK_STORAGE=cinder-ceph
++ BLOCK_STORAGE=cinder-ceph
++ export IMAGE_STORAGE=glance-ceph
++ IMAGE_STORAGE=glance-ceph
++ export PIPELINE_ID=6f5ac399-57ee-4abc-ace2-d3c77788b4dd
++ PIPELINE_ID=6f5ac399-57ee-4abc-ace2-d3c77788b4dd
++ export NETWORKING=neutron-contrail
++ NETWORKING=neutron-contrail
++ export UBUNTU_RELEASE=trusty
++ UBUNTU_RELEASE=trusty

From console.tx:

Bootstrapping environment "maas"
Starting new instance for initial state server
Launching instance
WARNING no architecture was specified, acquiring an arbitrary node
WARNING no architecture was specified, acquiring an arbitrary node
WARNING no architecture was specified, acquiring an arbitrary node
 - /MAAS/api/1.0/nodes/node-a036d91e-c4cd-11e3-8102-00163efc5068/
Installing Juju agent on bootstrap instance
Waiting for address
Attempting to connect to hayward-54.oil:22
Attempting to connect to hayward-54.oil:22
Attempting to connect to 10.245.0.182:22
Warning: Permanently added '10.245.0.182' (ECDSA) to the list of known hosts.
Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Running apt-get upgrade
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz <[https://streams.canonical.com/juju/tools/releases/juju-1.21.3-trusty-amd64.tgz]>
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
Bootstrap complete

Seeing this error with 1.21.3:

  '5':
    agent-state: started
    agent-version: 1.21.3
    containers:
      5/lxc/0:
        agent-state-info: 'failed to retrieve the template to clone: error executing
          "lxc-wait": lxc_container: utils.c: mkdir_p: 220 Not a directory - failed
          to create directory ''/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'';
          lxc_container: lxccontainer.c: do_snapshot_destroy: 3272 Could not destroy
          snapshot %s - failed to allocate a pty; Insufficent privileges to control
          juju-trusty-lxc-template'
        instance-id: pending
        series: trusty

Tags: oil
Revision history for this message
Larry Michel (lmic) wrote :
Revision history for this message
Alexis Bruemmer (alexis-bruemmer) wrote :

Larry,

Have you only seen this bug on 1.21.3? Is it reproducible with 1.22? Do you see it with earlier versions of 1.21.x?

Revision history for this message
Dimiter Naydenov (dimitern) wrote :

This is the same issue as bug 1410876 why is this not a duplicate?

Revision history for this message
Larry Michel (lmic) wrote :

Mistakenly removed the duplicate. I am re-adding it.

Revision history for this message
Larry Michel (lmic) wrote :

Alexis,

Yes, we did see this issue with 1.21.1. Dimiter dupped this one to 1410876 which is for 1.20.13 but we see that the error messages are not quite the same and are raised from different locations in the function. One fails with lxc-wait and the other with lxc-clone.

"failed to retrieve the template to clone: error executing
          "lxc-wait": lxc_container: utils.c:...."

and

"agent-state-info: 'lxc container cloning failed: error executing "lxc-clone":
          lxc_container: utils.c:...."

I recall similar issue that was fixed in 1.22 beta but I will need to look for the bug number to see whether signature was exactly the same as this one.

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

Other bug subscribers

Remote bug watches

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