machine agent on unit 0 cannot access the state

Bug #1065750 reported by Dave Cheney
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Critical
Dave Cheney

Bug Description

As of revision 661 this morning

/var/log/cloud-init-output.log
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
^M 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0^M100 10 100 10 0 0 8000 0 --:--:-- --:--:-- --:--:-- 10000
2012/10/11 22:20:46 JUJU state: opening state; mongo addresses: ["localhost:37017"]
2012/10/11 22:20:46 JUJU:DEBUG watcher: reading most recent document to ignore past history...
2012/10/11 22:20:46 JUJU:DEBUG presence: synchronizing watcher knowledge with database...
2012/10/11 22:20:46 JUJU:DEBUG watcher: loading new events from changelog collection...
2012/10/11 22:20:46 JUJU storing no-secrets environment configuration
2012/10/11 22:20:46 JUJU bootstrap-state initial password ""
jujud-machine-0 start/running, process 10711
ec2:
ec2: #############################################################
ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
ec2: 1024 c3:01:00:43:d3:84:d5:57:74:5c:f3:36:d5:3c:34:be root@ip-10-83-11-236 (DSA)
ec2: 256 f9:bd:38:10:34:ba:cb:31:09:0b:4d:bb:c9:43:c5:eb root@ip-10-83-11-236 (ECDSA)
ec2: 2048 8a:6a:0c:e0:8a:0b:9d:66:fb:25:63:ad:6f:39:a8:d2 root@ip-10-83-11-236 (RSA)
ec2: -----END SSH HOST KEY FINGERPRINTS-----
ec2: #############################################################
cloud-init boot finished at Thu, 11 Oct 2012 22:20:46 +0000. Up 172.24 seconds

but the machine agent cannot connect to the state

2012/10/11 22:20:46 JUJU machiner: machine agent starting
2012/10/11 22:20:46 JUJU state: opening state; mongo addresses: ["localhost:37017"]
2012/10/11 22:20:46 JUJU machiner: unauthorized access
2012/10/11 22:20:49 JUJU machiner: rerunning machiner
2012/10/11 22:20:49 JUJU machiner: machine agent starting
2012/10/11 22:20:49 JUJU state: opening state; mongo addresses: ["localhost:37017"]
2012/10/11 22:20:49 JUJU machiner: unauthorized access

Related branches

description: updated
Revision history for this message
Dave Cheney (dave-cheney) wrote :

What is crazy is juju status works

% juju status
machines:
  0:
    dns-name: ec2-54-242-147-225.compute-1.amazonaws.com
    instance-id: i-742c7409
services: {}

Revision history for this message
Dave Cheney (dave-cheney) wrote :

The problem was I was missing "admin-secret", which is now a required configuration variable. environs/config is programmed to provide "" as a default, which isn't a valid value. I will make a valid (non "") admin-secret mandatory.

Changed in juju-core:
assignee: nobody → Dave Cheney (dave-cheney)
Changed in juju-core:
milestone: 1.4 → 2.0
status: Confirmed → In Progress
milestone: 2.0 → 1.5
milestone: 1.5 → 1.4
Changed in juju-core:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.