Re: [Bug 1717176] Re: Fail to install wichita box

2017-09-14 Thread Ryan Harper
On Thu, Sep 14, 2017 at 1:44 AM, ChristianEhrhardt < 1717...@bugs.launchpad.net> wrote: > Full console log and Maas error report on the failed Xenial deploy > > ** Description changed: > > - Version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) > + Maas version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) >

[Bug 1717176] Re: Fail to install wichita box

2017-09-14 Thread ChristianEhrhardt
This happens at commisioning stage "00-maas-07-block-devices" This error on commissioning is reproducible and makes it unusable. ** Summary changed: - Fail to install wichita box + Fail to install or commission wichita (power 8) ** Description changed: Maas version: 2.2.2 (6099-g8751f91-0ubu

[Bug 1717176] Re: Fail to install wichita box

2017-09-14 Thread ChristianEhrhardt
Here the console log while commisioning. It ends in http issues. The IP is correct the path seems to miss something '//' maybe ? I don't know from what this is generated but 2012-03-01 seems old? This seems to be after some install activity: Cloud-init v. 0.7.5 running 'modules:final' at Thu, 14

[Bug 1717176] Re: Fail to install wichita box

2017-09-14 Thread ChristianEhrhardt
Hmm, commisioning failed as well but obviously at a different stage. NameTimeStatus 00-maas-00-support-info Thu, 14 Sep. 2017 07:05:39 Passed 00-maas-00-support-info.err Thu, 14 Sep. 2017 07:05:39 Passed 00-maas-01-cpuinfo Thu, 14 Sep. 2017 07:05:39 Passed 00-maas-

[Bug 1717176] Re: Fail to install wichita box

2017-09-14 Thread ChristianEhrhardt
That would likely be the first md_check_array_state call. sync_action = md_sysfs_attr(md_devname, 'sync_action') It checks if the MD is idle or if it has to wait for a sync to complete (or to stop) Now this is an upgraded maas, maybe the old DB for the node's disks create some odd config. So re

[Bug 1717176] Re: Fail to install wichita box

2017-09-13 Thread ChristianEhrhardt
Cloud init rolls through without a lot of issues, then it starts curtin but that fails for the error reported above. >From start of curtin to the error there is not much more that goes on. [ 65.296194] cloud-init[4049]: curtin: Installation started. (0.1.0~bzr505-0ubuntu1~16.04.1) [ 65.30362

[Bug 1717176] Re: Fail to install wichita box

2017-09-13 Thread ChristianEhrhardt
This was to be expected as it is still in curtin, but the target release Artful/Xenial does not make a difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717176 Title: Fail to install wichit

[Bug 1717176] Re: Fail to install wichita box

2017-09-13 Thread ChristianEhrhardt
Tail of the console log and Maas error report on the failed Artful deploy ** Attachment added: "bug-1717176-deploy-artful-maas-and-console.txt" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1717176/+attachment/4949893/+files/bug-1717176-deploy-artful-maas-and-console.txt -- You recei

[Bug 1717176] Re: Fail to install wichita box

2017-09-13 Thread ChristianEhrhardt
Full console log and Maas error report on the failed Xenial deploy ** Description changed: - Version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) + Maas version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1) + curtin version : 0.1.0~bzr505-0ubuntu1~16.04.1 - Maas output in install tab: - - curtin: Instal