Re: juju deploy ceph hangs in pending in maas environment

2015-01-29 Thread Daniel Bidwell
There is no /var/log/juju on machine-1/unit-ceph-0.  I have the
cloud-init.log at http://pastebin.com/GKA2W6Cv but am not sure what to
look for to figure out why the juju agent was never successfully
installed on it?  What do I look for?

On Thu, 2015-01-29 at 15:59 +, Marco Ceppi wrote:
 If you're able to SSH in to the machine, can we see the contents of
 `/var/log/juju/unit-ceph-0.log` and `/var/log/juju/machine-1.log`
 those will be the first place to look as to why this isn't working.
 From the sounds of it, MAAS provisioned the machine but the juju agent
 failed to install. The agent-state: pending is a clear indication it
 hasn't registered itself with the bootstrap node yet.
 
 
 Thanks,
 Marco Ceppi
 
 On Wed Jan 28 2015 at 4:50:51 PM Daniel Bidwell drbidw...@gmail.com
 wrote:
 I have ubuntu 14.04.1 with maas 1.7.1 rc4 and juju 1.20.14. My
 client
 machine is commissioned and deployed. I can ssh
 ubu...@cl1stn2.maas and
 I can juju ssh 1 successfully. I did juju deploy --config
 config.yaml
 ceph --to 1.
 
 juju status ceph looks like:
 
 juju status ceph
 environment: maas
 machines:
   1:
 agent-state: pending
 dns-name: cl1stn2.maas
 
 instance-id: 
 /MAAS/api/1.0/nodes/node-caa78cae-a5d5-11e4-b918-180373b04ac9/
 series: trusty
 hardware: arch=amd64 cpu-cores=16 mem=24576M
 tags=auitsdisk
 services:
   ceph:
 charm: cs:trusty/ceph-31
 exposed: false
 relations:
   mon:
   - ceph
 units:
   ceph/0:
 agent-state: pending
 machine: 1
 public-address: cl1stn2.maas
 networks:
   maas-em1:
 provider-id: maas-em1
 cidr: 10.20.0.0/24
 
 I don't see any attempt to contact cl1stn2.maas and the status
 stays in
 pending for ever. I can ssh to cl1stn2.maas and juju ssh 1
 successfully. I don't see anything in the all-machines.log.
 
 I can ping from the bootstrap server to the client machine and
 from the
 client machine to the bootstrap server.  They all have proper
 dns.
 
 Where do I look to find out what it is waiting for?
 --
 Daniel Bidwell drbidw...@gmail.com
 
 
 --
 Juju mailing list
 Juju@lists.ubuntu.com
 Modify settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/juju

-- 
Daniel Bidwell drbidw...@gmail.com


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


Re: juju deploy ceph hangs in pending in maas environment

2015-01-29 Thread Marco Ceppi
If you're able to SSH in to the machine, can we see the contents of
`/var/log/juju/unit-ceph-0.log` and `/var/log/juju/machine-1.log` those
will be the first place to look as to why this isn't working. From the
sounds of it, MAAS provisioned the machine but the juju agent failed to
install. The agent-state: pending is a clear indication it hasn't
registered itself with the bootstrap node yet.

Thanks,
Marco Ceppi

On Wed Jan 28 2015 at 4:50:51 PM Daniel Bidwell drbidw...@gmail.com wrote:

 I have ubuntu 14.04.1 with maas 1.7.1 rc4 and juju 1.20.14. My client
 machine is commissioned and deployed. I can ssh ubu...@cl1stn2.maas and
 I can juju ssh 1 successfully. I did juju deploy --config config.yaml
 ceph --to 1.

 juju status ceph looks like:

 juju status ceph
 environment: maas
 machines:
   1:
 agent-state: pending
 dns-name: cl1stn2.maas

 instance-id: /MAAS/api/1.0/nodes/node-caa78cae-a5d5-11e4-b918-
 180373b04ac9/
 series: trusty
 hardware: arch=amd64 cpu-cores=16 mem=24576M tags=auitsdisk
 services:
   ceph:
 charm: cs:trusty/ceph-31
 exposed: false
 relations:
   mon:
   - ceph
 units:
   ceph/0:
 agent-state: pending
 machine: 1
 public-address: cl1stn2.maas
 networks:
   maas-em1:
 provider-id: maas-em1
 cidr: 10.20.0.0/24

 I don't see any attempt to contact cl1stn2.maas and the status stays in
 pending for ever. I can ssh to cl1stn2.maas and juju ssh 1
 successfully. I don't see anything in the all-machines.log.

 I can ping from the bootstrap server to the client machine and from the
 client machine to the bootstrap server.  They all have proper dns.

 Where do I look to find out what it is waiting for?
 --
 Daniel Bidwell drbidw...@gmail.com


 --
 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: juju deploy ceph hangs in pending in maas environment

2015-01-29 Thread Andrew Wilkins
On Fri, Jan 30, 2015 at 12:28 AM, Daniel Bidwell drbidw...@gmail.com
wrote:

 There is no /var/log/juju on machine-1/unit-ceph-0.  I have the
 cloud-init.log at http://pastebin.com/GKA2W6Cv but am not sure what to
 look for to figure out why the juju agent was never successfully
 installed on it?  What do I look for?


Do you have cloud-init-output.log? That will contain the output of commands
Juju adds to cloud-init,
and so may have more useful information for debugging this.


 On Thu, 2015-01-29 at 15:59 +, Marco Ceppi wrote:
  If you're able to SSH in to the machine, can we see the contents of
  `/var/log/juju/unit-ceph-0.log` and `/var/log/juju/machine-1.log`
  those will be the first place to look as to why this isn't working.
  From the sounds of it, MAAS provisioned the machine but the juju agent
  failed to install. The agent-state: pending is a clear indication it
  hasn't registered itself with the bootstrap node yet.
 
 
  Thanks,
  Marco Ceppi
 
  On Wed Jan 28 2015 at 4:50:51 PM Daniel Bidwell drbidw...@gmail.com
  wrote:
  I have ubuntu 14.04.1 with maas 1.7.1 rc4 and juju 1.20.14. My
  client
  machine is commissioned and deployed. I can ssh
  ubu...@cl1stn2.maas and
  I can juju ssh 1 successfully. I did juju deploy --config
  config.yaml
  ceph --to 1.
 
  juju status ceph looks like:
 
  juju status ceph
  environment: maas
  machines:
1:
  agent-state: pending
  dns-name: cl1stn2.maas
 
  instance-id:
 /MAAS/api/1.0/nodes/node-caa78cae-a5d5-11e4-b918-180373b04ac9/
  series: trusty
  hardware: arch=amd64 cpu-cores=16 mem=24576M
  tags=auitsdisk
  services:
ceph:
  charm: cs:trusty/ceph-31
  exposed: false
  relations:
mon:
- ceph
  units:
ceph/0:
  agent-state: pending
  machine: 1
  public-address: cl1stn2.maas
  networks:
maas-em1:
  provider-id: maas-em1
  cidr: 10.20.0.0/24
 
  I don't see any attempt to contact cl1stn2.maas and the status
  stays in
  pending for ever. I can ssh to cl1stn2.maas and juju ssh 1
  successfully. I don't see anything in the all-machines.log.
 
  I can ping from the bootstrap server to the client machine and
  from the
  client machine to the bootstrap server.  They all have proper
  dns.
 
  Where do I look to find out what it is waiting for?
  --
  Daniel Bidwell drbidw...@gmail.com
 
 
  --
  Juju mailing list
  Juju@lists.ubuntu.com
  Modify settings or unsubscribe at:
  https://lists.ubuntu.com/mailman/listinfo/juju

 --
 Daniel Bidwell drbidw...@gmail.com


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