Cannot bootstrap instances in ec2

roger peppe roger.peppe at canonical.com
Tue Apr 2 08:30:41 UTC 2013


It seems to work OK for me (revision 1090).


On 2 April 2013 06:39, David Cheney <david.cheney at canonical.com> wrote:
> ubuntu at ip-10-130-181-131:~$ tail -f /var/log/juju/machine-1.log
> 2013/04/02 05:37:43 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 05:37:43 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 05:37:43 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 05:37:43 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 05:37:43 ERROR JUJU:jujud:machine jujud machine command failed:
> state entity name not found in configuration
> error: state entity name not found in configuration
>
> This is broken at revision 1088 and probably earlier (still bisecting)
>
> Revision 1089 is also broken,
>
> lucky(~/src/launchpad.net/juju-core) % gb ./...
> launchpad.net/juju-core/cmd/builddb
> # launchpad.net/juju-core/cmd/builddb
> cmd/builddb/main.go:9: imported and not used:
> "launchpad.net/juju-core/state"
>
> Why didn't the tests catch this ?
>
> Dave
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev



More information about the Juju-dev mailing list