Hi folks, I came in this morning to attack the LXC issues, but got stuck into two other issues first.
The local provider wasn't bootstrapping properly, it would say it was, but it wasn't. There were two issues: 2013-09-26 23:12:26 ERROR juju.worker environ.go:51 loaded invalid environment configuration: storage-port: expected int, got 8040 and 2013-09-26 22:24:47 ERROR juju runner.go:211 worker: exited "upgrader": cannot set agent tools for machine 0: empty size or checksum The first is fixed in r1895 on lp:juju-core, the config was now getting serialized through JSON, which handles all numbers as float64. the config schema was expecting an int, but was getting a float64, however the error was just printing the value, which looked like an int, hence confusion (this is fixed too RSN). The second is fixed in r1896 on lp:juju-core, this was related to the simplestreams tools changes and checking the signed tools. Log says: The local provider did not implement CustomToolsSources, so when it tried to get tools via simplestreams, it failed and then used the legacy fallback. But this meant that checksum and size info was missing. The azure provider did implement CustomToolsSources, but until the official tools repository comes online, the tools sources do need to include the public container from which tools can be fetched, or else simplestreams will fail and revert to legacy tools code. Cheers, Tim -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
