machine agent cannot start

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

Bug Description

http://bazaar.launchpad.net/~juju/juju-core/trunk/revision/1078 broke the build

Machine agents cannot start, report

ubuntu@ip-10-142-169-94:/var/log/juju$ tail -f machine-1.log
2013/04/02 06:09:08 ERROR JUJU:jujud:machine jujud machine command failed: state entity name not found in configuration
error: state entity name not found in configuration
2013/04/02 06:09:08 ERROR JUJU:jujud:machine jujud machine command failed: state entity name not found in configuration
error: state entity name not found in configuration
2013/04/02 06:09:08 ERROR JUJU:jujud:machine jujud machine command failed: state entity name not found in configuration
error: state entity name not found in configuration
2013/04/02 06:09:08 ERROR JUJU:jujud:machine jujud machine command failed: state entity name not found in configuration
error: state entity name not found in configuration
2013/04/02 06:09:08 ERROR JUJU:jujud:machine jujud machine command failed: state entity name not found in configuration
error: state entity name not found in configuration

Revision history for this message
William Reade (fwereade) wrote :

Cannot reproduce; error looks very much reminiscent of a failure to upload tools. Please add further details.

Revision history for this message
Dimiter Naydenov (dimitern) wrote :

Could this be caused by cmd/builddb/main.go failing to compile after rev 1089 - "state" imported and not used.
I'm proposing a trivial fix for that now, so after landing it, could you try again to see the bug is resolved please?

Revision history for this message
Dave Cheney (dave-cheney) wrote : Re: [Bug 1163122] Re: machine agent cannot start

I have worked my way back to rev 1077 using juju bootstrap
--upload-tools (I always do upload tools). Unless somehow --upload-tools
has been broken recently, I blame rev 1078.

On 02/04/13 21:43, Dimiter Naydenov wrote:
> Could this be caused by cmd/builddb/main.go failing to compile after rev 1089 - "state" imported and not used.
> I'm proposing a trivial fix for that now, so after landing it, could you try again to see the bug is resolved please?
>

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

http://paste.ubuntu.com/5670353/

With a fudged version string to ensure I could not be picking up stale
tools.

On 02/04/13 23:55, Dave Cheney wrote:
> I have worked my way back to rev 1077 using juju bootstrap
> --upload-tools (I always do upload tools). Unless somehow --upload-tools
> has been broken recently, I blame rev 1078.
>
> On 02/04/13 21:43, Dimiter Naydenov wrote:
>> Could this be caused by cmd/builddb/main.go failing to compile after rev 1089 - "state" imported and not used.
>> I'm proposing a trivial fix for that now, so after landing it, could you try again to see the bug is resolved please?
>>
>

William Reade (fwereade)
Changed in juju-core:
assignee: nobody → William Reade (fwereade)
Revision history for this message
William Reade (fwereade) wrote :

Discussed online: the problem is that tool search falls back to another bucket with incompatible tools for machines with series not matching that from --upload-tools.

I will resolve this by:

 1) Eliminating the cross-bucket fallback: if any tools exist in the private bucket, the public bucket will be ignored. In the given situation, this will cause the deployment to fail at provisioning time due to lack of tools, which I think qualifies as an improvement.

 2) Adding a --fake-series option, to go with --upload-tools on bootstrap and upgrade-juju, that uploads an additional copy of the built tools for each given fake series. This allows a developer running (say) quantal to upload tools for (say) precise, and thereby test cross-series environments.

Revision history for this message
William Reade (fwereade) wrote :

(2) has been merged, hopefully unblocking a few people. Cross-bucket fallback is still to be addressed.

Tim Penhey (thumper)
Changed in juju-core:
status: Confirmed → In Progress
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.