Re: Deploying Xenial charms in LXD? Read this

[Tom Barber]

Yeah I hit something like this on EC2 last night.

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 8 September 2016 at 14:28, Andrew Wilkins 
wrote:

> On Thu, Sep 8, 2016 at 9:23 PM Marco Ceppi 
> wrote:
>
>> Hey everyone,
>>
>> An issue was identified late yesterday for those deploying Xenial charms
>> to either the LXD provider or LXD instances in a cloud.
>>
>> The symptoms for this manifest as the LXD machine running is in a running
>> state (and has an IP address assigned) but the agent does not start. This
>> leaves the workload permanently stuck in a "Waiting for agent to
>> initialize" state. This problem originates from a problem in cloud-init and
>> systemd, being triggered by an update to the snapd package for xenial.
>>
>
> FYI this is not LXD-specific. I've just now seen the same thing happen on
> Azure.
>
> Thanks to James Beedy, from the community, for posting this workaround
>> which appears to be working consistently for the moment:
>>
>> juju set-model-config enable-os-refresh-update=false
>> juju set-model-config enable-os-upgrade=false
>>
>>
>> This should bypass the section of the cloud-init process that's causing
>> the hang at the moment. For those interested in tracking the bugs I believe
>> these are the two related ones for this problem:
>>
>> - https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1621229
>> - https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1576692
>>
>> I'll make sure to post an update when this has been resolved.
>>
>> Thanks,
>> Marco Ceppi
>> --
>> canonical-juju mailing list
>> canonical-j...@lists.canonical.com
>> Modify settings or unsubscribe at: https://lists.canonical.com/
>> mailman/listinfo/canonical-juju
>>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Deploying Xenial charms in LXD? Read this

[Andrew Wilkins]

On Thu, Sep 8, 2016 at 9:23 PM Marco Ceppi 
wrote:

> Hey everyone,
>
> An issue was identified late yesterday for those deploying Xenial charms
> to either the LXD provider or LXD instances in a cloud.
>
> The symptoms for this manifest as the LXD machine running is in a running
> state (and has an IP address assigned) but the agent does not start. This
> leaves the workload permanently stuck in a "Waiting for agent to
> initialize" state. This problem originates from a problem in cloud-init and
> systemd, being triggered by an update to the snapd package for xenial.
>

FYI this is not LXD-specific. I've just now seen the same thing happen on
Azure.

Thanks to James Beedy, from the community, for posting this workaround
> which appears to be working consistently for the moment:
>
> juju set-model-config enable-os-refresh-update=false
> juju set-model-config enable-os-upgrade=false
>
>
> This should bypass the section of the cloud-init process that's causing
> the hang at the moment. For those interested in tracking the bugs I believe
> these are the two related ones for this problem:
>
> - https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1621229
> - https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1576692
>
> I'll make sure to post an update when this has been resolved.
>
> Thanks,
> Marco Ceppi
> --
> canonical-juju mailing list
> canonical-j...@lists.canonical.com
> Modify settings or unsubscribe at:
> https://lists.canonical.com/mailman/listinfo/canonical-juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Deploying Xenial charms in LXD? Read this

[Marco Ceppi]

Hey everyone,

An issue was identified late yesterday for those deploying Xenial charms to
either the LXD provider or LXD instances in a cloud.

The symptoms for this manifest as the LXD machine running is in a running
state (and has an IP address assigned) but the agent does not start. This
leaves the workload permanently stuck in a "Waiting for agent to
initialize" state. This problem originates from a problem in cloud-init and
systemd, being triggered by an update to the snapd package for xenial.

Thanks to James Beedy, from the community, for posting this workaround
which appears to be working consistently for the moment:

juju set-model-config enable-os-refresh-update=false
juju set-model-config enable-os-upgrade=false


This should bypass the section of the cloud-init process that's causing the
hang at the moment. For those interested in tracking the bugs I believe
these are the two related ones for this problem:

- https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1621229
- https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1576692

I'll make sure to post an update when this has been resolved.

Thanks,
Marco Ceppi
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju