=== jfarschman is now known as MilesDenver
=== jfarschman is now known as MilesDenver
[12:26] <TrXuk> Have tried putting new root-image, kernel and initrd into the MaaS boot locations on the MaaS server. Even tried the fix (updating the image to -proposed in a chroot env) suggested in the bug.. Nothing gets my nodes booted into MaaS properly! https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1391354
[12:26] <ubot5> Launchpad bug 1391354 in maas-images "Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more" [Undecided,Confirmed]
[12:26] <TrXuk> Help?
[14:19] <TrXuk> <TrXuk> Have tried putting new root-image, kernel and initrd into the MaaS boot locations on the MaaS server. Even tried the fix (updating the image to -proposed in a chroot env) suggested in the bug.. Nothing gets my nodes booted into MaaS properly! https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1391354 [12:26] <ubot5> Launchpad bug 1391354 in maas-images "Failure to boot ephemeral image for Utopic Fast Installer deployment: no I
[14:19] <ubot5> Launchpad bug 1391354 in maas-images "Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more" [Undecided,Confirmed]
[14:32] <blake_r> TrXuk: are you able to deploy trusty?
[14:42] <TrXuk> @blake_r I'm not able to add any nodes to MaaS in the first place
[14:42] <TrXuk> the netboot ends up dropping out to initramfs due to the bug in the link
[14:42] <TrXuk> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1391354
[14:42] <ubot5> Launchpad bug 1391354 in maas-images "Failure to boot ephemeral image for Utopic Fast Installer deployment: no ID_PATH for iSCSI device any more" [Undecided,Confirmed]
[14:43] <TrXuk> have tried the fix suggested on that bug without success. Have also tried placing newer initrd, kernels and root-images from maas daily builds into the MaaS server /var/maas locations
[14:44] <blake_r> TrXuk: this is maas 1.7?
[14:53] <TrXuk> @blake_r: yes 1.7
[14:53] <TrXuk> installed last week on a utopic install
[14:54] <TrXuk> Was initially following this: http://www.ubuntu.com/download/cloud/install-ubuntu-openstack
[15:15] <blake_r> TrXuk: check that the tgtd server is running correctly
[15:15] <blake_r> TrXuk: "service tgtd restart"
[15:40] <TrXuk> yes, it appears to be
[15:41] <TrXuk> The issue with the bug appears to be udev paths within the initrd from PXE due to a bad version of systemd/iscsi
[15:41] <TrXuk> but newer builds still cause me the same issues
[15:43] <TrXuk> @blake_r service tgt restart ?
[15:44] <TrXuk> As tgtd doesnt exist
[15:44] <TrXuk> but tgtd is running, just think it's service name is tgt
[15:44] <blake_r> TrXuk: if your trying to enlist a node it will only trusty will be ran
[15:44] <blake_r> TrXuk: i dont understand why Utopic would be running
[15:45] <blake_r> TrXuk: "tgt" is fine, give it a restart and try again
[15:45] <TrXuk> @blake_r yes, Trusty, so i've tried patching the bad trusty image without success as per the bug, and also tried putting newer maas image builds (boot-kernel, boot-initrd and root-image) into the /var/maas/etc/etc/etc/generic/x64/trusty directory
[15:45] <TrXuk> so they get used instead of the broken trusty package
[15:46] <TrXuk> neither helps
[15:46] <blake_r> TrXuk: trusty is not broken that issue only occurs on utopic
[15:46] <blake_r> TrXuk: if your dropping to an initramfs then that means your having a network issue connecting to the iscsi targer
[15:46] <TrXuk> Sorry, my MAAS server's os us utopic, the enlist image/etc is indeed trusty
[15:46] <TrXuk> which doesnt work, as per the bug
[15:47] <blake_r> TrXuk: I dont believe that is the bug you are seeing, I think it is something else, can you provide a console output of the boot?
[15:47] <TrXuk> It says it's using the trusty image (can see it) and have checked connectivity for iScsi
[15:47] <TrXuk> but thanks for the interrupt, it looks exactly like this bug, but if you're saying trusty image is working for everyone else, i'll go back to the start
[15:52] <TrXuk> @blake_r console output is exactly as shown in the bug, hard to display here as it's on a KVM so cannot pastebin out text
[15:53] <TrXuk> @I'll start with a blank trusty MaaS again though and blow away all my changes, see where we stand then
[15:57] <blake_r> TrXuk: okay let me know, we CI MAAS on both trusty and utopic
[15:57] <TrXuk> @blake_r Thanks for your help
[15:58] <TrXuk> @blake_r should I still be OK running MAAS (server) from a utopic-server OS?
[15:58] <TrXuk> as thats's what i'm currently on. Was planning to go back to trusty for the re-install as thats the only thing I havent tried
[15:59] <blake_r> It should work on utopic, are you using are stable ppa?
[15:59] <TrXuk> yes
[15:59] <blake_r> Yeah that stable ppa will work on trusty and utopic
[16:00] <TrXuk> @blake_r installation path was Utopic > Install MaaS packages > MaaS UI > Download image > Chose 14.04 X64 > image downloaded > tried booting PXE nodes > failed
[16:00] <TrXuk> Will triple check everything based on your info and check back!
=== roadmr is now known as roadmr_afk
=== roadmr_afk is now known as roadmr
=== roadmr is now known as roadmr_afk
=== roadmr_afk is now known as roadmr