On 08.05.17 10:56, Mathias Strufe (DFKI) wrote: > Dear Peter, thanks for your answer. > > Yes since I'm waiting for additional HW I created meanwhile two VMs to > have 4 machines in total in MAAS for provisioning. > > Please find attached machine log and lxd log from the machine that stuck. > > Do not wonder thats now machine 3 ... tried a bit with different > machines and no its machine 3 thats stuck 20% ... > The VM itself is not stucked ...
Mathias, ok so it appears the lxc containers are getting stuck on creation In this case pertinent logs should be in /var/log/lxd for the LXD container hypervisor, as well as /var/log/lxc for indiv. containers From your lxd.log it appears that lxd can't download the releases file from https://cloud-images.ubuntu.com/releases. It needs to be able to reach that URL to download ubuntu images. Please ensure that you can reach the above URL *from the VM where lxd runs* Check eg. with curl, while logged in at the VM: curl https://cloud-images.ubuntu.com/releases HTH peter. > Thanks a lot! Mathias. > > > > On 2017-05-08 09:36, Peter Sabaini wrote: >> On 07.05.17 13:39, Mathias Strufe (DFKI) wrote: >>> Dear all, >>> >>> I'm new in juju and facing currently following problem ... >>> my machines stuck very very often in pending allocating state ... >>> If I run show-machine on such a stucked machine I got follow output: >>> >>> >>> machines: >>> “0”: >>> juju-status: >>> current: started >>> since: 06 May 2017 21:17:21+02:00 >>> version: 2.1.2 >>> dns-name: 10.100.0.112 >>> ip-addresses: >>> – 10.100.0.112 >>> – 10.50.0.112 >>> – 10.250.0.112 >>> – 10.30.0.112 >>> – 10.14.0.112 >>> – 10.150.0.112 >>> – 10.200.0.112 >>> – 10.14.3.112 >>> instance-id: r67qgw >>> machine-status: >>> current: running >>> message: Deployed >>> since: 06 May 2017 21:17:23+02:00 >>> series: xenial >>> containers: >>> 0/lxd/0: >>> juju-status: >>> current: pending >>> since: 06 May 2017 21:17:58+02:00 >>> instance-id: pending >>> machine-status: >>> current: pending >>> since: 06 May 2017 21:17:58+02:00 >>> series: xenial >>> 0/lxd/1: >>> juju-status: >>> current: pending >>> since: 06 May 2017 21:17:59+02:00 >>> instance-id: pending >>> machine-status: >>> current: allocating >>> message: ‘copying image for juju/xenial/amd64 from >>> https://cloud-images.ubuntu.com/daily: >>> 39% (10.18MB/s)’ >>> since: 06 May 2017 21:22:39+02:00 >>> series: xenial >>> 0/lxd/2: >>> juju-status: >>> current: pending >>> since: 06 May 2017 21:18:00+02:00 >>> instance-id: pending >>> machine-status: >>> current: pending >>> since: 06 May 2017 21:18:00+02:00 >>> series: xenial >>> constraints: mem=3584M >>> hardware: arch=amd64 cores=8 mem=32000M tags=virtual >>> availability-zone=Zone1_DC-Core >>> controller-member-status: has-vote >>> >>> >>> I figured out that the machine changes from try to try and always stuck >>> at different percentage stage while copying image ... >>> any idea about that ... >>> I had only two or three times that all machines finished that process >>> ... I don't know what to do? any ideas? >> >> Just for clarity -- you seem to be using a VM which hosts LXD >> containers, right? Are the containers stuck or the VM itself? >> >> The log messages from LXD and the log from machine 0 (juju ssh 0 ; sudo >> less /var/log/juju/machine-0.log or so) should have more info on what's >> going wrong. >> >> HTH >> peter. >> >>> >>> thanks in advance! >>> >>> Mathias. >>> >
signature.asc
Description: OpenPGP digital signature
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
