3

I have a MAAS installation with it's interface at 10.12.1.3/MAAS. It is responsible for DHCP/DNS and the configurations are as follows: ip: 10.12.1.4 subnet mask: 255.255.255.0 broadcast ip: 10.12.1.255 router ip: 10.12.1.1 ip range low: 10.12.1.10 ip rane high: 10.12.1.100

I am booting virtualbox machines on the same machine as the cluster controller/region controller, and they enlist fine. I change their name in MAAS, accept, and commission them. The enlistment and commission process take a very long time (just food for thought). Once the machine has been commissioned, (it says ready in MAAS nodes list). Run JuJu bootstrap. Juju has the following environments.yaml:

environments:
    maas:
        type: maas
        maas-server: 'http://10.12.1.3/MAAS/'
        maas-oauth: pVreWZYhzaAFmqNjV3:W96PuEtANsr3n2SkGR:xF8dccH7NPUjhpejauzek$
        admin-secret: 'whatever'
        default-series: precise
        #authorized-keys-path: ~/.ssh/id_rsa.pub

when I run juju bootstrap, then power on the virtualbox VM, I get this:

picked arbitrary tools &{"1.18.1-precise-amd64" "https://streams.canonical.com/juju/tools/releases/juju-1.18.1-   precise-amd64.tgz" "65ea92cd8812bff3e49df78f9e8e964e91c44af0abd49d880c4333a78c8abfda" %!q(int64=5368375)} - /MAAS/api/1.0/nodes/node-f942c69e-c400-11e3-bc28-0025906c5dd6/
Waiting for address
 Attempting to connect to test.draco:22

This screen will hang out for 10 minutes, and then I recieve the following:

 ERROR juju.provider.common bootstrap.go:123 bootstrap failed: waited for 10m0s without being able to connect: ssh: connect to host test.draco port 22: Connection refused

if I run a juju status while it is attempting to bootstrap, I get the following:

ERROR state/api: websocket.Dial wss://nova1.draco:17070/: dial tcp 10.12.1.10:17070: connection refused

over and over again.

I am using the 12.04.4 MAAS ubuntu install, and Juju version: 1.18.1-precise-amd64

The ssh keys have been generated, uploaded to maas, re-generated and uploaded to MAAS again. Also, the machine that juju is supposed to build will finish building (status in MAAS changes to "Allocated to bla") despite the environment bootstrap failure, and then it will power off. The status in MAAS goes back to "ready" and if I turn the virtual machine back on, it seems to go back into enlisting.

Anyone know what could be going wrong?

Improve this question

1 Answer 1

Reset to default
0

Running a juju status -e maas could give a better insight just in case. It seems to me that ssh is working as a but the host refuses connection, by this line: 

 ssh: connect to host test.draco port 22: Connection refused

Are you aware that

#authorized-keys-path: ~/.ssh/id_rsa.pub

is actually commented out? You ought to uncomment the path to SSH keys, and if the problem persists you could check the file permissions for ssh keys. Hope it helps.

Improve this answer
3
  • The "connection refused" part suggests that there is a network connectivity problem and that things never even get as far as checking keys. Poster needs to figure out why the connection to port 22 fails before they have to worry about keys.
    – Mad Wombat
    Feb 9, 2018 at 19:01
  • @MadWombat you're not wrong. Connection "refused" because of authentication, hence pointing the cause to key path. Even though the answer seems irrelevant we had a similar problem, that's how I pointed that out directly. And btw, interesting to see a comment after 3 years :) Cheers to that.
    – altinturk
    Feb 12, 2018 at 8:38
  • lol, didn't realize it was such an old question. I was looking for an answer for my own juju question and didn't check the date.
    – Mad Wombat
    Feb 12, 2018 at 17:57

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .