On Wed, Jan 22, 2014 at 1:57 PM, Raphaël Badin <[email protected]>wrote:
> > maas-integration.TestMAASIntegration.test_check_nodes_ready ... ok >> maas-integration.TestMAASIntegration.test_apply_tag_to_all_nodes ... ok >> maas-integration.TestMAASIntegration.test_check_tag_applied_to_all_nodes >> ... ok >> maas-integration.TestMAASIntegration.test_configure_juju ... ok >> maas-integration.TestMAASIntegration.test_juju_bootstrap ... ERROR >> SKIP: Not testing Cluster controller >> > > Diogo and I spent some time debugging this problem today and we think we > found the problem. > The new version of juju 1.17 in trusty has a timeout of 10 minutes ( > http://paste.ubuntu.com/6797885/) when bootstrapping a node. MAAS takes > a good 7 minutes to install a node, plus a couple of minutes to install > jujud on it so we suspect this might be the problem ( > https://bugs.launchpad.net/juju-core/+bug/1257649). > > Diogo is in the process of testing this hypothesis by building juju from > source after having changed the timeout to 30 minutes and then trying a run > with that tweaked juju. > I tested the hypothesis by increasing the timeout to 30 minutes, which made the bootstrap workflow go further. Unfortunately, something else broke and I couldn't confirm bootstrap completes successfully, but it was enough evidence to convince Curtis to raise the importance of bug https://bugs.launchpad.net/juju-core/+bug/1257649 and it's now targeted to the 1.18.0 release. I filed https://bugs.launchpad.net/maas/+bug/1271915 to improve the qa-lab-tests too so when juju commands fail, I think it'll make things clearer to debug. > > Cheers, > > R. > -- Diogo M. Matsubara
-- Mailing list: https://launchpad.net/~maas-builds Post to : [email protected] Unsubscribe : https://launchpad.net/~maas-builds More help : https://help.launchpad.net/ListHelp
