Azure Provider: Deployed service never goes to started

[Antonio Rosales]

I have been unable to deploy charm after the initial bootstrap. The agent-state never comes out of started. The bootstrap node looks to start, but the service stays in "pending."

juju --debug status -e azure
2013-08-20 22:17:03 DEBUG juju.environs.azure environprovider.go:30 opening environment "azure".
2013-08-20 22:17:06 DEBUG juju state.go:158 waiting for DNS name(s) of state server instances [juju-azure-t4s3mf6fm6]
2013-08-20 22:17:07 INFO juju open.go:69 state: opening state; mongo addresses: ["juju-azure-t4s3mf6fm6.cloudapp.net:37017"]; entity ""
2013-08-20 22:17:08 INFO juju open.go:107 state: connection established
environment: azure
machines:
  "0":
    agent-state: started
    agent-version: 1.12.0
    dns-name: juju-azure-t4s3mf6fm6.cloudapp.net
    instance-id: juju-azure-t4s3mf6fm6
    instance-state: Created
    series: saucy
  "1":
    instance-id: pending
    series: saucy
services:
  wordpress:
    charm: local:saucy/wordpress-93
    exposed: false
    relations:
      loadbalancer:
      - wordpress
    units:
      wordpress/0:
        agent-state: pending
        machine: "1"
2013-08-20 22:17:11 INFO juju supercommand.go:284 command finished

I am running the latest Juju compiled from trunk:
juju --version
1.13.2-quantal-amd64

This error happens when I use a public bucket or when upload tools is invoked (see bug 1214181).

-thanks,
Antonio

[Julian Edwards (julian-edwards)]

I can reproduce this easily.

After deployment, the second machine comes up but I cannot ssh into it:

$ juju ssh 1
Warning: Permanently added 'juju-azure-ix3trqnjtv.cloudapp.net,138.91.139.213' (RSA) to the list of known hosts.
Permission denied (publickey).
error: exit status 255

This means that cloud-init has not added the public key. This could be cloud-init's fault or juju's fault, but there's no real way of telling unless we can ssh in.

[Julian Edwards (julian-edwards)]

Ok I can confirm this is a problem with the latest saucy image. I used an old precise image of my own with a fixed cloud-init, and everything was fine.

[Scott Moser (smoser)]

I've launched an instance from the azure cmdline tools:
$ azure vm create --vm-size=extrasmall --vm-name=sm-saucy1 "--location=East US" --<email address hidden> --no-ssh-password --ssh=22 sm-saucy1 b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-13_10-amd64-server-20130821-en-us-30GB smoser

and I'm able to ssh in fine with the appropriate key.
cloud-init populated /home/smoser/.ssh/authorized_keys correctly

$ cat /etc/cloud/build.info
build_name: server
serial: 20130821
$ cat .ssh/authorized_keys
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC87JeKQoPBCWHjgGqC+yzd3kYCU1PtNd28eIjJEmxlamlDqK4DuPTNiDhY5qQ2JxiYMbhvrOHSFVBI8kveXPKcmxLl25wUJcYn7SRQHzkXgZXcLYzEeFBrO3kX3LqB6CGTyGyXv8B/P1W7leJYPBp6wUzRyioFdEJCWTGnfoU+Gwijb9sFhklcn4p5NN1Kam4+xWlOp38oquItMaYBlHM4BAuFG2zFX1dsM07PPDV1Hd1ky59cyIUwA1DxCh/iYXSPbfjcBFRneszHtkMI8M1KYN+od9q4IWBsO49F+EdE0gUsXlDx81kRs0GqoLwXqCvGOO4VD5efLhxlJ7oxsoCP

[Julian Edwards (julian-edwards)]

Scott - I think something is going wrong with
the juju customdata. Juju's ssh key is not
getting set. If I use the exact same juju code
with my custom image that I built from your
instructions a month ago, it all works fine.

Your example doesn't show custom data
working does it?

[Julian Edwards (julian-edwards)]

Nobody can recreate any more so let's invalidate this.

[Scott Moser (smoser)]

Julian,
  yeah, i thought that juju was passing ssh keys through the metadata rather than through the user-data (in #cloud-config 'authorized-keys') like it is doing.

 I'm not sure what went wrong.

For my own reference, I'll post some cloud-init logs here and also the things I did today to do this.