juju 2.3.3 failing to bootstrap localhost

Tim Penhey tim.penhey at canonical.com
Thu Feb 22 02:47:24 UTC 2018


How did you login to the container? It sounds like you may be missing
SSH logins?

Tim

On 22/02/18 14:32, fengxia wrote:
> Verified by login to the container. I could `apt update`, `apt install
> htop`.
> 
> At juju bootstrap terminal, I picked up this error message:
> 
> 01:27:52 DEBUG juju.provider.common bootstrap.go:564 connection attempt
> for 10.170.
> 
> 130.125 failed: WARNING: Your password has expired.
> Password change required but no TTY available.
> 
> What does it mean? I looked at my user's password expiration settings on
> the host using `chage`:
> 
> (dev) fengxia at ubuntu:~$ sudo chage -l fengxia
> Last password change                    : Dec 07, 2017
> Password expires                    : never
> Password inactive                    : never
> Account expires                        : never
> Minimum number of days between password change        : 0
> Maximum number of days between password change        : 99999
> Number of days of warning before password expires    : 7
> 
> Looks like the password should be just fine.
> 
> Any other pointer would be highly appreciated.
> 
> 
> On 02/21/2018 06:24 PM, Nicholas Skaggs wrote:
>> On 02/21/2018 04:47 PM, David Britton wrote:
>>> On Wed, Feb 21, 2018 at 04:11:44PM -0500, fengxia wrote:
>>>> Hi Juju,
>>>>
>>>> Is anyone seeing this? I'm running the same setup as yesterday's, then
>>>> updated `apt update && apt upgrade` this morning. All of a sudden `juju
>>>> bootstrap localhost ..` stuck at Attempting to connect. LXC
>>>> container was
>>>> created and had an IP, but juju won't connect somehow?
>>>>
>>>> 1. Tried reconfiguring LXD to different network addresses, not helpful.
>>>>
>>>> 2. Made sure `.local/share/juju/ssh/juju_id_rsa` has mode 0600
>>>>
>>>> Any idea what to try?
>>> If you have your lxd container created, you can get access to it
>>> directly:
>>>
>>> lxc list
>>> lxc exec <container> bash
>>> # look in /var/log/cloud*, /var/log/juju/*,
>>> # /var/log/syslog, etc for errors
>>>
>>> Also, you can run your `juju bootstrap` in --debug mode, which gives a
>>> lot more data.
>>>
>> Specifically make sure you can:
>>
>> 1) create an lxc container
>>
>> 2) ssh into the container
>>
>> 3) that container has proper connectivity, including the ability to
>> install packages
>>
>>
>> Nicholas
>>
> 



More information about the Juju mailing list