[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
Hmm...I realize this is not a problem. I posted it in AskUbuntu and have not heard anything. As this bug seemed very similar to what I was experiencing, I was wondering if one of the persons who solved or know how to solve could write a quick comment on how to do so... IP forwardingDNS forwarding you mean??? DHCP does work, but not DNS! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
This is not a MAAS problem, you need to set up IP forwarding in your maas server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
I am having same problems but with Ubuntu 14.04 LTS - I have a Ubuntu MASS Server running on one node. It has two NICs. One NIC (eth1) is connected to our organization's network. The other NIC (eth0) is private network - to manage all the nodes in the cloud. I am running DHCP server on eth0. I am trying to add another node. It can PXE boot, get IP address, but cannot connect to external network and get packages. Can you provide details on how to resolve this? I referred http://ideasnet.wordpress.com/category/ubuntu-14-04lts-cloud-computing- server-edition/ which helped in other cases, but not with this problem. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
@Paul: the problem you're having is that your nodes can't access the outside world. They are thus unable to fetch the packages needed for commissioning (see http://paste.ubuntu.com/7195406/). Unless you changed the http_proxy config option (on the settings page — or you can configure it using the CLI/API), your nodes are using the region's proxy to download packages. Have a look at the proxy's log to check if you can see something suspicious. Another common problem is when MAAS' DNS server (BIND server installed on the region) is unable to resolve names such as 'ubuntu.com'. If this is the problem then the region's /var/log/syslog file will contain errors like 'error (network unreachable) resolving …'. To solve this: if you're using Trusty's package, just configure the 'upstream_dns' option ('settings' page, at the bottom — or using the API/CLI) with your upstream DNS server address. If you're using another version, you have to do the config manually: include something like http://paste.ubuntu.com/7195395/ in /etc/bind/named.conf.options and restart the maas-dns service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
I have a similar error, when I comission a node, I get this error: Error output failed [2/5] ( 00-maas-01-lshw 00-maas-02-virtuality) I'm using Ubuntu Server 12.04.3 and Precise image for the nodes. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
Awesome, thank you Andres and Raphaël!! Please see attachment. Note to myself: 1. Login to the API by using the following steps: https://maas.ubuntu.com/docs/maascli.html 2. Then run command: maas-cli maas commissioning-results list > commissioing-results.json Best regards, ** Attachment added: "commissioning-results.json" https://bugs.launchpad.net/maas/+bug/1237364/+attachment/3977400/+files/commissioning-results.json -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
Paul, Would it be possible for you to collect console output? On the other hand, what you could try is to obtain the output of the scripts themselves from the database. These are in base64. Use thefollowing command: maas-cli commissioning-results list The results yields json output from each fo the commissioning scripts. In the field 'data' you will find the base64 encoded output. Please do share that information so we can see why the script failed. Cheers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
Another note: to debug commissioning problems, the quickest way is to have a look at the output of the scripts that failed. You can't do that with the UI right now but it's all available if you use the API/CLI: The following CLI command : $ maas-cli maas commissioning-results list will spit out all the result of the commissioning scripts. The 'data', the actual output of the script, is base64-encoded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
Btw, I just found (and fixed) bug 1278895. It means that the list of the failed scripts in the "failed [3/5] …" message is actually wrong: it's the list of the scripts that didn't fail (!). Here is the list of all the scripts that maas has: 00-maas-01-lshw 00-maas-02-virtuality 00-maas-03-install-lldpd 99-maas-01-wait-for-lldpd 99-maas-02-capture-lldp When MAAS says "failed [2/5] 00-maas-01-lshw 00-maas-02-virtuality", it means '00-maas-03-install-lldpd', '99-maas-01-wait-for-lldpd' and '99-maas-02-capture-lldp' failed. This is a nasty bug (!). It's fixed as of revision 1926. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
Hi Andrew, I could only find cloud-init.log under /var/log. Please see attachment. Thank you! ** Attachment added: "cloud-int log file" https://bugs.launchpad.net/maas/+bug/1237364/+attachment/3973386/+files/cloud-init.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
Paul, Can you also please attach the output of /var/log/cloud-init.log and/or cloud-init-output.log from the epehemeral image? On Feb 7, 2014 7:25 PM, "Paul" wrote: > Sorry, left out the important stuff: > > Host MAAS version: 1.4+bzr1693+dfsg-0ubuntu2.2 > Host OS version: ubuntu server 13.10 > Host Kernel: 3.11.0-12-generic #19-Ubuntu > > Node OS version: 12.04 > Node Kernel version: 3.2.0-54-generic #82 > > Thanks again! > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1237364 > > Title: > Commissioning with a Saucy image sets node status to "Failed tests" > > To manage notifications about this bug go to: > https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
Sorry, left out the important stuff: Host MAAS version: 1.4+bzr1693+dfsg-0ubuntu2.2 Host OS version: ubuntu server 13.10 Host Kernel: 3.11.0-12-generic #19-Ubuntu Node OS version: 12.04 Node Kernel version: 3.2.0-54-generic #82 Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
Ran into similar same Error output and the node was connected to internet: failed [2/5] ( 00-maas-01-lshw 00-maas-02-virtuality) Some information on my configuration: The DHCP server is on a different box and able to provide the correct ip, route, netmask, and gateway to node. Used the workaround " Debugging ephemeral image" and able to create user/pass to stopped it from shutdown the node machine. Once inside the node, I was able to ping out to the internet. Attached is my lshw log. Thank you very much in advance! ** Attachment added: "lshw log file" https://bugs.launchpad.net/maas/+bug/1237364/+attachment/3973373/+files/lshw_log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
The reason for the error is because node couldn't get to the Internet. Issue fixed by configuring the proxy to the MAAS server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
We ran into this issue on 14.04. maas version: 1.4+bzr1820+dfsg-0ubuntu1 deploy 12.04.3 images Error output failed [2/5] ( 00-maas-01-lshw 00-maas-02-virtuality) Desktop Computer (To be filled by O.E.M.) 64 SMBIOS version 2.7 DMI version 2.7 32-bit processes Motherboard D53427RKE Intel Corporation 0 G87790-403 GERK34400GZZ To be filled by O.E.M. BIOS Intel Corp. 0 RKPPT10H.86A.0017.2013.0425.1251 04/25/2013 65536 16711680 PCI bus BIOS EEPROM can be upgraded BIOS shadowing Booting from CD-ROM/DVD Selectable boot path Enhanced Disk Drive extensions 5.25" 1.2MB floppy 3.5" 720KB floppy 3.5" 2.88MB floppy Print Screen key INT14 serial line control INT17 printer control ACPI USB legacy emulation BIOS boot specification L2 cache 3d CPU Internal L2 524288 524288 Internal Write-trough Unified cache L1 cache 3e CPU Internal L1 131072 131072 Internal Write-trough Data cache L3 cache 3f CPU Internal L3 3145728 3145728 Internal Write-back Unified cache System Memory 40 System board or motherboard 17179869184 SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) 9905428-087.A00LF Kingston 0 2B130439 DIMM1 8589934592 64 16 SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) 9905428-087.A00LF Kingston 1 2D130939 DIMM2 8589934592 64 16 CPU Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz Intel Corp. 41 cpu@0 Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz CPU 1 18 28 64 1 64bits extensions (x86-64) mathematical co-processor FPU exceptions reporting virtual mode extensions debugging extensions page size extensions time stamp counter model-specific registers 4GB+ memory addressing (Physical Address Extension) machine check exceptions compare and exchange 8-byte on-chip advanced programmable interrupt controller (APIC) fast system calls memory type range registers page global enable machine check architecture conditional move instruction page attribute table 36-bit page size extensions debug trace and EMON store MSRs thermal control (ACPI) multimedia extensions (MMX) fast floating point save/restore streaming SIMD extensions (SSE) streaming SIMD extensions (SSE2) self-snoop HyperThreading thermal interrupt and status pending break event fast system calls no-execute bit (NX) CPU Frequency scaling Host bridge 3rd Gen Core processor DRAM Controller Intel Corporation 100 pci@:00:00.0 09 32 3300 VGA compatible controller 3rd Gen Core processor Graphics Controller Intel Corporation 2 pci@:00:02.0 09 64 3300 Message Signalled Interrupts Power Management bus mastering PCI capabilities listing USB controller 7 Series/C210 Series Chipset Family USB xHCI Host Controller Intel Corporation 14 pci@:00:14.0 04 64 3300 Power Management Message Signalled Interrupts bus mastering PCI capabilities listing Communication controller 7 Series/C210 Series Chipset Family MEI Controller #1 Intel Corporation 16 pci@:00:16.0 04 64 3300 Power Management Message Signalled Interrupts bus mastering PCI capabilities listing Serial controller 7 Series/C210 Series Chipset Family KT Controller Intel Corp
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
** Changed in: maas Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
** Changed in: maas Milestone: None => 13.10 ** Changed in: maas Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
** Changed in: maas Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
This bug was fixed in the package maas - 1.4+bzr1693+dfsg-0ubuntu1 --- maas (1.4+bzr1693+dfsg-0ubuntu1) saucy; urgency=low * New Upstream Release (LP: #1218526) - This new upstream release contains fixes and improvements of the features approved by the FFe above. - Fixes commissioning failure on Saucy with 'Failed Test' (LP: #1237364) - Fixes access of static images over http (LP: #1236544) * d/maas-cluster-controller.postinst: a2enmod version module (LP: #1236544) * d/control: Bump depends on python-django to 1.4. (LP: #1236572) * d/maas-dhcp.postinst: Fail gracefully if apparmor_parser fails, allowing to install maas-dhcp during an ISO install. (LP: #1236786) -- Andres RodriguezFri, 04 Oct 2013 12:33:05 -0400 ** Changed in: maas (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
** Branch linked: lp:ubuntu/saucy-proposed/maas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
** Changed in: maas Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Changed in: maas (Ubuntu) Status: New => Confirmed ** Changed in: maas (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs