Re: juju 2.3.3 failing to bootstrap localhost

2018-02-21 Thread John Meinel 
That sounds more like the 'ubuntu' user inside the container is having
trouble? Juju connects to initially launched machines as the ubuntu user,
not as your username.

John
=:->


On Thu, Feb 22, 2018 at 5:32 AM, 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@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: 9
> 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  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
>>
>>
> --
> Feng Xia
>
> Advisory Engineer
> Datacenter Group (DCG), Lenovo US
> 8000 Development Dr, Morrisiville, NC 27509
> W: http://www.lenovo.com
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: juju 2.3.3 failing to bootstrap localhost

2018-02-21 Thread Tim Penhey 
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@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        : 9
> 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  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
>>
> 

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

Re: juju 2.3.3 failing to bootstrap localhost

2018-02-21 Thread fengxia 
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@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        : 9
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  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



--
Feng Xia

Advisory Engineer
Datacenter Group (DCG), Lenovo US
8000 Development Dr, Morrisiville, NC 27509
W: http://www.lenovo.com


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

Re: juju 2.3.3 failing to bootstrap localhost

2018-02-21 Thread Nicholas Skaggs 

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  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


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

Re: juju 2.3.3 failing to bootstrap localhost

2018-02-21 Thread fengxia 

Some progress. It's complaining about "password expired"? What does it mean?

Here is a debug trace running via `juju bootstrap --show-log --debug



(dev) fengxia@ubuntu:~$ juju bootstrap --show-log --debug localhost devlocal
21:17:23 INFO  juju.cmd supercommand.go:56 running juju [2.3.3 gc go1.9.2]
21:17:23 DEBUG juju.cmd supercommand.go:57   args: 
[]string{"/snap/juju/3452/bin/juju", "bootstrap", "--show-log", 
"--debug", "localhost", "devlocal"}
21:17:23 DEBUG juju.tools.lxdclient client.go:235 LXD snap socket not 
found, falling back to debian socket: "/var/lib/lxd"
21:17:23 DEBUG juju.tools.lxdclient client.go:252 connecting to LXD 
remote "local": "unix:///var/lib/lxd/unix.socket"
21:17:23 INFO  juju.tools.lxdclient client.go:306 using LXD API version 
"1.0"
21:17:23 INFO  juju.tools.lxdclient client.go:355 LXD "default" profile 
uses network bridge "lxdbr0"
21:17:23 INFO  cmd provider.go:189 Resolved LXD host address on bridge 
lxdbr0: 10.170.130.1:8443
21:17:23 INFO  cmd cloudcredential.go:51 no credentials found, checking 
environment
21:17:23 DEBUG juju.tools.lxdclient client.go:229 Using environment 
LXD_DIR as socket path: "/var/lib/lxd"
21:17:23 DEBUG juju.tools.lxdclient client.go:252 connecting to LXD 
remote "local": "unix:///var/lib/lxd/unix.socket"
21:17:23 INFO  juju.tools.lxdclient client.go:306 using LXD API version 
"1.0"
21:17:23 INFO  juju.tools.lxdclient client.go:355 LXD "default" profile 
uses network bridge "lxdbr0"
21:17:23 DEBUG juju.cmd.juju.commands bootstrap.go:835 authenticating 
with region "" and credential "localhost" ()

21:17:23 DEBUG juju.cmd.juju.commands bootstrap.go:963 provider attrs: map[]
21:17:24 INFO  cmd authkeys.go:114 Adding contents of 
"/home/fengxia/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
21:17:24 INFO  cmd authkeys.go:114 Adding contents of 
"/home/fengxia/.ssh/id_rsa.pub" to authorized-keys
21:17:24 DEBUG juju.cmd.juju.commands bootstrap.go:1019 preparing 
controller with config: map[default-series:xenial 
no-proxy:127.0.0.1,localhost,::1 ftp-proxy: 
update-status-hook-interval:5m https-proxy: 
enable-os-refresh-update:true apt-mirror: name:controller 
development:false max-status-history-size:5G image-stream:released 
max-action-results-age:336h proxy-ssh:false 
uuid:ffe164a4-5717-41eb-8531-6b1c7d460d42 net-bond-reconfigure-delay:17 
test-mode:false cloudinit-userdata: authorized-keys:ssh-rsa 
B3NzaC1yc2EDAQABAAABAQDFrgQso2OVedVHYDH3ey9bM/mHKvz45FDK1LCq9Ap+eLDanJObvCFzQvWRfZdOVPfsmdSbP3vKm0vetM/fqRrlWFQbg2A13WwC95hAXAbN0VpmI5kx7izWPGuN8rBX5EsgWZS9crZkS9jQ5Cri/5feGihbH4kqDr06+RzimFqu5qozl+SKCTJv30a25x0YxvKoxmnJPNra4xiPh6woDFro7c7+sW++fDTg1hgXoau5ldsDWOoreC3l2tCgX8A6tDuwe4fCAisMUzGBlfDVRBNGABx7WVe6hk9/gzmMVohsmnVkPYY1L5o/clDiztWJJuqSzZFNYPgjxDceBz/ONlPX 
juju-client-key
ssh-rsa 
B3NzaC1yc2EDAQABAAABAQCVAgY29fjJrLRtvCoYdvaGMrGdQXStURUn5b+BonX2+3UgCyE770kh8Ml7BCxwg8N46QdrERKxQBOharM6oUGXHpug4Svesh0ao74GqNd8O7Lc6Zm9QxTKH+fBhSt5zvkuQ5LG34pjYtPk2EouVDdnYlYMQf/z8ojaQUjoeX54beO7TciShyAgq6JdW7X326VY6uhiVkgi1bBLat3WjBn+X9wuMVdL7YTyM0vEBEudWNF5e9Hyh1owIfAxF6x6xMuMDd9ynfbvwOsLNFSsdMDHGImGL3mRtD8oOMOaVxfYr+d6v3jBWJewFvl2jhjGNoFKmQOvSZPZW1fdY/naJ7Wx 
fengxia@ubuntu
 apt-http-proxy: ignore-machine-addresses:false fan-config: 
logging-config: automatically-retry-hooks:true 
container-networking-method: provisioner-harvest-mode:destroyed 
resource-tags: max-status-history-age:336h type:lxd apt-ftp-proxy: 
apt-https-proxy: http-proxy: transmit-vendor-metrics:true 
firewall-mode:instance logforward-enabled:false enable-os-upgrade:true 
container-inherit-properties: agent-metadata-url: 
ssl-hostname-verification:true egress-subnets: 
max-action-results-size:5G image-metadata-url: 
disable-network-management:false apt-no-proxy: agent-stream:released]
21:17:24 DEBUG juju.tools.lxdclient client.go:229 Using environment 
LXD_DIR as socket path: "/var/lib/lxd"
21:17:24 DEBUG juju.tools.lxdclient client.go:252 connecting to LXD 
remote "remote": "10.170.130.1:8443"
21:17:24 INFO  juju.tools.lxdclient client.go:306 using LXD API version 
"1.0"
21:17:24 INFO  cmd bootstrap.go:508 Creating Juju controller "devlocal" 
on localhost/localhost
21:17:24 INFO  juju.cmd.juju.commands bootstrap.go:572 combined 
bootstrap constraints:
21:17:24 DEBUG juju.environs.bootstrap bootstrap.go:199 model 
"controller" supports service/machine networks: false
21:17:24 DEBUG juju.environs.bootstrap bootstrap.go:201 network 
management by juju enabled: true

21:17:24 INFO  cmd bootstrap.go:233 Loading image metadata
21:17:24 INFO  cmd bootstrap.go:303 Looking for packaged Juju agent 
version 2.3.3 for amd64
21:17:24 INFO  juju.environs.bootstrap tools.go:72 looking for bootstrap 
agent binaries: version=2.3.3
21:17:24 DEBUG juju.environs.tools tools.go:102 finding agent binaries 
in stream: "released"
21:17:24 DEBUG juju.environs.tools tools.go:104 reading agent binaries 
with major.minor version 2.3
21:17:24 DEBUG juju.environs.tools

Re: juju 2.3.3 failing to bootstrap localhost

2018-02-21 Thread fengxia 

Here is a debug trace running via `juju bootstrap --show-log --debug



(dev) fengxia@ubuntu:~$ juju bootstrap localhost devlocal

Creating Juju controller "devlocal" on localhost/localhost
Looking for packaged Juju agent version 2.3.3 for amd64
To configure your system to better support LXD containers, please see: 
https://github.com/lxc/lxd/blob/master/doc/production-setup.md

Launching controller instance(s) on localhost/localhost...
 - juju-b88ca2-0 (arch=amd64)
Installing Juju agent on bootstrap instance
Fetching Juju GUI 2.11.3
Waiting for address
Attempting to connect to 10.170.130.158:22


On 02/21/2018 04:11 PM, 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?



--
Feng Xia

Advisory Engineer
Datacenter Group (DCG), Lenovo US
8000 Development Dr, Morrisiville, NC 27509
W: http://www.lenovo.com


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

juju 2.3.3 failing to bootstrap localhost

2018-02-21 Thread fengxia 

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?

--
Feng Xia

Advisory Engineer
Datacenter Group (DCG), Lenovo US
8000 Development Dr, Morrisiville, NC 27509
W: http://www.lenovo.com


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