[11:33] <gmb> allenap, rvba`, bigjools Awright?
[11:33] <gmb> Made it to internet at last.
[11:33] <allenap> gmb: Hello!
[11:39] <gmb> Hola
[11:57] <gmb> allenap: Do you need any help with the celery->RPC work?
[11:57] <gmb> Or rather: I'm free, Mr Humphries; what can I help with?
[13:52]  * gmb -> Location switch; bbiab
[16:07] <gmb> allenap: I’d like to help with the RPC work; is there any reason I can’t start with the “periodically report boot images” task?
[16:08] <gmb> (although I have no idea how to do peridoic RPC tasks without celerybeat)
[17:15] <onicrom> question... im seeing the following error in my maas.log
[17:15] <onicrom> ERROR 2014-08-06 13:08:35,490 maasserver ################################ Exception: {u'mac_addresses': [u'One or more MAC addresses is invalid.']} ################################
[17:15] <onicrom> not sure how it could be invalid, it pxe booted and its the actual mac
[17:59] <onicrom> i think i figured it out
[17:59] <onicrom> maas is expecting the mac to have upper case letters.
[17:59] <onicrom> (which is not that obvious)
[18:13] <allenap> gmb: Sure, that’s a good one.
[18:15] <allenap> onicrom: That sounds like a bug; MAAS should allow both, or at least normalise automatically. I’ll file a bug.
[18:19] <allenap> onicrom: Was there any more detail to that error message?
[18:20] <onicrom> filed
[18:20] <allenap> onicrom: Thanks! I’d just seen that seconds ago.
[18:20] <onicrom> allenap: its weird when i entered it using all caps the comissioning would fail
[18:21] <onicrom> when i entered it lowercase
[18:21] <onicrom> the maas.log would error
[18:21] <onicrom> the UI seems to display lowercase either way
[18:22] <onicrom> im now running into a weird issue with the dell.. i use serial over lan and as soon as the install gets to a certain point the drac remote management ip becomes unresponsive until i reboot the machine
[18:27] <allenap> blake_r, newell, jhobbs: ^
[18:28] <newell> allenap, howdy
[18:28] <onicrom> also unlreated question... what is maas using iscsi for?
[18:28] <newell> allenap, do you have  bug number?
[18:29] <newell> actually nm, I will look on launchpad
[18:30] <allenap> newell: I was pointing you to the Dell issue onicrom is having.
[18:30] <newell> yeah I see the bug now
[18:31] <newell> oh so not the bug?
[18:31] <newell> okay
[18:31] <onicrom> (im less concerned about the bug i filed as i figured out the nuance)
[18:32] <onicrom> i think it might have something to do with my preseed file as i started messing with the storage... but in either case i dont see why the dell's management interface becomes unresponse :(
[18:33] <jhobbs> onicrom: do you have to reboot the system manually?
[18:33] <newell> onicrom, can you pastebin your console output?
[18:33] <onicrom> jhobbs: i have a kvm remote console which i can three finger solute
[18:34] <jhobbs> onicrom: it should reboot automatically after an install
[18:34] <onicrom> which works and the DRAC responds as soon as the reboot is initiated
[18:34] <onicrom> jhobbs: i doesnt actually start the install actually
[18:34] <onicrom> it get stuck at the kernl booting screen before the install is initiated.
[18:34] <jhobbs> hmm
[18:35] <onicrom> just happened again :( appears to be unlreated to my preseed as i restored the default
[18:35] <onicrom> ooh weird.... the dhcp ip is pingable
[18:35] <jhobbs> are you passing serial console parameters on the kernel command line?
[18:35] <onicrom> but my console (kvm and serial) has stopping printing
[18:36] <onicrom> u am
[18:36] <onicrom> *i am
[18:36] <onicrom> but i have remote kvm too so i can watch watch would be on a monitor
[18:36] <jhobbs> console=ttyS0 and console=tty0 too?
[18:36] <onicrom> yes
[18:36] <onicrom> console=tty0 console=ttyS1,115200n8
[18:36] <newell> onicrom, anytime I have run into that issue it is because I wasn't passing the correct kernel parameters that jhobbs is mentioning
[18:36] <onicrom> to be exact
[18:37] <jhobbs> how are you passing them?
[18:37] <onicrom> in the global kernel params
[18:37] <onicrom> i see all the comissioning happen
[18:37] <jhobbs> ah ok
[18:37] <onicrom> via console (and tty0)
[18:37] <jhobbs> are you doing a fastpath install or a debian installer install?
[18:37] <jhobbs> if it's fastpath, it's the same kernel/initrd as commissioning uses
[18:38] <onicrom> debian
[18:38] <jhobbs> it'd be worth trying fastpath to see if it's specific to the d-i kernel
[18:39] <onicrom> i can certainly give that a try i want to see if the install actually works (i probably botched the last presee file)
[18:39] <jhobbs> k
[18:39] <onicrom> the machine is still pingable on its actual interface the drac is still offline :(
[18:39] <onicrom> ive noticed that with cd based installs too
[18:39] <onicrom> when it goes to 'discover' the network devices
[18:40] <jhobbs> we test with a lot of dell/drac systems on a very regular basis
[18:40] <onicrom> drac management interface goes offline
[18:40] <jhobbs> i don't remember seeing that kind of behavior before
[18:40] <onicrom> i am using the ghetto drac6e
[18:40] <onicrom> so its using a 'shared' interface it doesnt have a dedicated nic
[18:40] <jhobbs> ahh
[18:40] <jhobbs> sound ripe for kernel/firmware interaction bugs
[18:40] <onicrom> ineed
[18:41] <onicrom> *indeed
[18:41] <onicrom> i cant complain tooo much
[18:41] <onicrom> x5670 x 2 96GB ram 6x600G drives with bbu raid card
[18:41] <onicrom> for like 3k
[18:41] <onicrom> i bought 20 of them for this openstack poc :)
[18:41] <onicrom> i mean i can always complain haha
[18:42] <onicrom> i digress... i am still at a loss as to why my rmeote kvm is stuck at a kernel boot message though
[18:50] <jhobbs> is the kvm via drac or separte?
[18:50] <jhobbs> separate
[18:52] <jhobbs> if you're seeing stuff in CD installs too it's likely not a MAAS specific issue though
[18:53] <jhobbs> you might try #ubuntu-kernel or https://bugs.launchpad.net/ubuntu/+source/linux/+bugs for those
[18:55] <onicrom> kvm is separate
[18:57] <jhobbs> does pxelinux print the kernel command line parameters for you prior to trying to boot linux?
[18:57] <jhobbs> might be worth double checking that console=tty0 is still there
[18:57] <onicrom> it did
[18:57] <onicrom> i saw it in both
[18:57] <jhobbs> dang
[18:57] <onicrom> the host is still not booting but its in some state...
[18:58] <onicrom> i cant ssh in (con refused)
[18:58] <onicrom> drac not reachable and kvm shows boot message that is stale...
[18:58] <onicrom> id really like to see wtf is going on lol
[18:58] <onicrom> the install should ber finished but its possible its still going i gues...
[18:58] <jhobbs> ssh would be up if the install finished, the system would reboot afterwards
[18:59] <jhobbs> but then it wouldn't have an IP if it hung at early linux boot
[18:59] <jhobbs> wouldn't respond to pings i mean
[18:59] <onicrom> a reboot would re-enable drac
[18:59] <onicrom> exactly :) its in some weird state
[18:59] <jhobbs> you could try adding earlyprintk to the command line parameters
[19:00] <jhobbs> but.. if it gets far enough to get an ip that's past earlyprintk time
[19:00] <onicrom> btw... what is iscsi used for?
[19:00] <jhobbs> "ephemeral" booting
[19:01] <jhobbs> during enlistment, commissioning, install, nodes boot up via pxe and then mount iscsi for their root filesystem, with a ram only overlay
[19:01] <jhobbs> fastpath install that is, not d-i
[19:01] <onicrom> what about d-i?
[19:01] <jhobbs> d-i is all contained in the initrd
[19:01] <onicrom> gotcha
[19:02] <onicrom> ok i will try fast path on another node which i have kvm/serial (i only have 4 devices on kvm the rest are serial only :()
[19:03] <jhobbs> hopefully that works, it's a lot better imo anyhow
[19:08] <onicrom> i need to figure out how to customize that install :)
[19:09] <jhobbs> yeah it's something new to learn, but has the huge advantage of having a rich ubuntu environment during install
[19:10] <onicrom> well...i dont know the debian installer either
[19:10] <jhobbs> d-i is on top of busybox
[19:10] <onicrom> i was starting to play with that i have no bias
[19:10] <jhobbs> no python, not even perl, i think you don't even get awk
[19:10] <jhobbs> maybe sed
[19:11] <onicrom> ok fingers crossed building another box with fast now
[19:11] <jhobbs> well good luck, i'm off for the night
[19:12] <onicrom> wooo
[19:12] <onicrom> jhobbs: its working!
[19:20] <onicrom> any docs around on customizing the install via fastpath
[19:25] <rbasak> onicrom: http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/doc/topics/overview.rst
[19:47] <onicrom> thanks rbasak
[22:17] <lamont> what exactly is maas telling me to fix when it says: Unable to get RPC connection for cluster 'master'
[23:17] <bigjools> lamont: clusters and region appserver threads attempt to maintain bidirectional connections, without which maas won't work properly. It's possible you are firewalled since they currently use high-numbered ports for this.
[23:20] <lamont> who creates the connection, I wonder?
[23:30] <onicrom> rbasak: im looking to create a customized partition table, are there more specific exaples to configure curtin