[00:08] <EntropyWorks> it looks like your using bmc-config
[00:09] <EntropyWorks> which I don't know if I can get it to work right with iLO3
[00:16] <bigjools> that's roaksoax's work :)
[00:17] <bigjools> he would know better than I
[00:31] <EntropyWorks> bigjools: humm /usr/share/maas/preseeds/enlist_userdata looks to be the place. but if I'm reading this it wants to modify the IPMI setting not just power off and on a machine
[00:31] <bigjools> that's the detection stuff
[00:31] <bigjools> not the power template
[00:32] <bigjools> you'll have an ipmi.template somewhere
[00:32] <EntropyWorks> ah
[00:44] <EntropyWorks> bigjools: I think I got it! without modify the template
[00:45] <EntropyWorks> modified /etc/freeipmi//freeipmi.conf and added driver-type LAN_2_0
[00:45] <bigjools> nice
[00:46] <EntropyWorks> I think the IPMI config in the webgui should have a choice since someone may be in a mixed env
[00:48] <bigjools> well it is on a per-node basis
[00:49] <bigjools> we used to have more choice for ipmi IIRC but roaksoax changed it
[00:50] <EntropyWorks> yes and that is why it should be in the webgui so you could provision a driver-type LAN and then add another node and do driver-type LAN_2_0
[00:51] <EntropyWorks> with out login into the MAAS server and modifying that /etc/freeipmi/freeipmi.conf to override the default of LAN
[00:53] <EntropyWorks> the underlying tool is ipmipower
[01:03] <EntropyWorks> great... note to self do not delete the last MAC address for a node. now I can't select it to remove it...
[01:04] <bigjools> oops
[01:04] <bigjools> please file a bug
[01:04] <bigjools> (you could add a dummy mac)
[01:09] <EntropyWorks> from the webgui I can't I only see the "(name)"  which isn't a link
[01:11] <EntropyWorks> when a mac is there its "93:73:71:73:c1:47(name)"
[01:11] <EntropyWorks> and you have to click the mac address to delete or modify the node
[01:17] <bigjools> damn
[01:25] <smoser> EntropyWorks, so you still around ?
[01:25] <smoser> yeah, what i was saying was to just try putting that file into place and update-initramfs
[01:25] <smoser> and then reboot
[01:26] <EntropyWorks> yes
[01:27] <EntropyWorks> ok I think that worked. I'm rebooting that machine again just to check
[01:29] <EntropyWorks> bigjools: the link is there in the HTML  but nothing for it to underline as a link.
[01:32] <bigjools> EntropyWorks: ok thanks
[01:33] <EntropyWorks> https://bugs.launchpad.net/maas/+bug/1117875
[01:33] <smoser> EntropyWorks, ok. this makes sense now.
[01:33] <smoser> at least i think.
[01:33] <smoser> after adding that rule (and removing entry in /etc/modules) we need to run 'update-initramfs'.
[01:33] <smoser> otherwise, the module would get loaded in the initramfs
[01:34] <smoser> and then the modprobe.d rules that we were applying only are put into affect when that module (mlx4_core) is installed.
[01:34] <smoser> and since it was already getting installed in the initramfs, the changes were not doing anything.
[01:34] <smoser> so...
[01:34] <EntropyWorks> $ lsinitramfs /boot/initrd.img-3.5.0-23-generic | grep mlx4
[01:34] <EntropyWorks> etc/modprobe.d/mlx4.conf
[01:34] <EntropyWorks> lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/mellanox/mlx4
[01:34] <EntropyWorks> lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/mellanox/mlx4/mlx4_core.ko
[01:34] <EntropyWorks> lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/mellanox/mlx4/mlx4_en.ko
[01:35] <smoser> i'd really apprecate it if you would put the soft dep one in place
[01:35] <smoser> then update-initramfs
[01:35] <EntropyWorks> ok
[01:35] <smoser> then reboot
[01:35] <smoser> and, cross your fingers, please
[01:35] <smoser> :)
[01:37] <EntropyWorks> humm
[01:37] <EntropyWorks> $ update-initramfs -u -k $(uname -r)
[01:37] <EntropyWorks> update-initramfs: Generating /boot/initrd.img-3.5.0-23-generic
[01:37] <EntropyWorks> FATAL: modprobe: softdep dependency loop encountered inserting mlx4_core
[01:37] <EntropyWorks> still want me to reboot?
[01:39] <EntropyWorks> it appears that it did not add mlx4_en to the image...
[01:40] <EntropyWorks> rebooting anyway...
[01:40] <smoser> hm..
[01:40] <smoser> shoot. i remember that.
[01:40] <smoser> that is odd.
[01:47] <EntropyWorks> only the mlx4_core was loaded
[01:47] <EntropyWorks> so that didn't work
[01:47] <bigjools> EntropyWorks: which version of maas are you using?  I cannot reproduce your bug
[01:48] <smoser> right. EntropyWorks so lets try the whole update-initramfs process with the 'modprobe'.
[01:48] <smoser> er... with the 'install version
[01:48] <smoser> of mlx4.conf
[01:48] <EntropyWorks> bigjools: 0.1+bzr1269+dfsg-0ubuntu1 i'm running on quantal 12.10
[01:48] <bigjools> EntropyWorks: from the stable PPA?
[01:49] <bigjools> oh is that the version in quantal
[01:49] <EntropyWorks> yea its the default in quantal I'm not using another PPA except to mess around with salt
[01:50] <bigjools> for me, it's the names that are linkified on the node list
[01:50] <bigjools> not the macs, so I can click on it happily
[01:50] <EntropyWorks> weird
[01:50] <bigjools> can you try the PPA version?  it fixes a LOT of bugs and is about to get SRUed
[01:50] <EntropyWorks> I only installed MAAS yesterday on a clean system too
[01:51] <bigjools> https://launchpad.net/~maas-maintainers/+archive/stable/+packages
[01:52] <EntropyWorks> smoser: modifying the mlx4.conf again and initramfs  for you and reboot
[01:58] <EntropyWorks> bigjools: nice! this one has the @%#$$T@# IPMI settings that was causing me to scream at my monitor
[01:58] <bigjools> EntropyWorks: \o/
[01:59] <bigjools> I wondered why you were having trouble!
[01:59] <bigjools> keep forgetting all the old versions differences
[02:00] <EntropyWorks> *head to desk*
[02:00] <smoser> EntropyWorks, sorry for your pain.
[02:00] <smoser> did we get our modules loaded ?
[02:01] <smoser> i'm about to push this and ask for it to be loaded into raring.
[02:01] <EntropyWorks> smoser: well if it wasn't for that you wouldn't have me to trouble shoot the mlx4 issues so... i don't mind since that is one that really pissed me off for a while
[02:01] <smoser> yeah, fwiw, people generally seem to think taht the driver itself is just being stupid here.
[02:01] <smoser> that it isn't automatically loading stuff itself.
[02:01] <EntropyWorks> that worked.
[02:01] <smoser> woowhoo!
[02:02] <EntropyWorks> now just have to fix the initrd.gz that will get used for MAAS too :-)
[02:04] <EntropyWorks> $ lsmod | grep mlx4
[02:04] <EntropyWorks> mlx4_en                63080  0
[02:04] <EntropyWorks> mlx4_core             173435  1 mlx4_en
[02:04] <smoser> oh
[02:04] <smoser> and one more thing, EntropyWorks
[02:04] <smoser> you have functional network based on that, right ?
[02:05] <smoser> (just a little thing like "does it actually give you network" :)
[02:06] <EntropyWorks> yes networking works.
[02:06] <EntropyWorks> I wanted to see what happens if I unload the both and reload mlx4_en
[02:06] <EntropyWorks> that added more modules then before
[02:07] <EntropyWorks> mlx4_ib                57930  0
[02:07] <EntropyWorks> mlx4_en                63080  0
[02:07] <EntropyWorks> mlx4_core             173435  2 mlx4_ib,mlx4_en
[02:07] <EntropyWorks> ib_mad                 47134  3 mlx4_ib,ib_cm,ib_sa
[02:07] <EntropyWorks> ib_core                82363  7 mlx4_ib,ib_iser,rdma_cm,ib_cm,iw_cm,ib_sa,ib_mad
[02:07] <EntropyWorks> what i did was
[02:07] <EntropyWorks> modprobe -r mlx4_en
[02:07] <EntropyWorks> modprobe -r mlx4_core
[02:08] <EntropyWorks> modprobe mlx4_en
[02:08] <EntropyWorks> well past time to leave the office. smoser catch you tomorrow if you need more mlx4 debugging
[02:09] <smoser> thanks again.
[02:09] <smoser> EntropyWorks, right. i tested that.
[02:09] <smoser> seems generally functional.
[02:09] <smoser> but thanks for thinking
[03:01] <EntropyWorks> what ports on the MAAS server need to be open by the way? would be nice to have a ufw config in /etc/applications.d/
[03:04] <EntropyWorks> next problem I have to solve is what image has the /etc/apt/sources.list or where I need to add the http_proxy info for MAAS to work in my env
[15:54] <sam_one> morning kool kats
[21:07] <EntropyWorks> anyone have a quicker way to add machines then doing it via the webgui?
[21:10] <EntropyWorks> the nodes now have gotten Allocated but since they appear to not have working networking I'm suck.  I can't delete the node from the gui either
[21:10] <EntropyWorks> lovely
[21:25] <EntropyWorks> btw this command just fails: sudo maas createsuperuser
[21:25] <EntropyWorks> http://paste.ubuntu.com/1622243/
[21:53] <bigjools> EntropyWorks: eummmm that's really odd, I've never seen anything like that. Something is screwed in your system.
[21:54] <bigjools> you can add machines via the command line or API
[21:57] <EntropyWorks> bigjools: I was able to remove them via the maas-cli
[21:57] <bigjools> great
[21:58] <EntropyWorks> the createsuperuser thing however I have no clue.
[21:58] <bigjools> me neither
[21:58] <bigjools> my only guess is that somehow your PPA install clashes with the quantal package
[21:59] <bigjools> can you file a bug please and supply as much info as you can about your installation (versions etc)
[21:59] <EntropyWorks> maybe. it was happening before in the quantal packages too
[21:59] <EntropyWorks> sure
[22:00] <bigjools> oh weird
[22:00] <bigjools> matsubara, hi
[22:28] <EntropyWorks> bigjools: humm yea I'm think something just is wrong with my server. not sure what. going to just reload from scratch and try again.
[22:29] <bigjools> EntropyWorks: try LC_ALL=C sudo maas createsuperuser
[22:29] <EntropyWorks> nope
[22:29] <bigjools> you're missing locale info
[22:30] <bigjools> is it even set?
[22:30] <EntropyWorks> wonder if my python is screwed someplace
[22:30] <bigjools> echo $LC_ALL
[22:31] <EntropyWorks> not set
[22:31] <bigjools> ok C doesn't work
[22:31] <bigjools> set it to a valid locale
[22:31] <bigjools> en_US for example
[22:31] <bigjools> bugger
[22:31] <bigjools> you need sudo -E as well
[22:32] <bigjools> preserves env
[22:33] <EntropyWorks> yea, but no good either
[22:33] <EntropyWorks> something messed up with my install. check this out
[22:33] <EntropyWorks> $ maas-cli
[22:33] <EntropyWorks> Error: no arguments given.
[22:33] <EntropyWorks> Run /usr/lib/python2.7/dist-packages/maascli/__main__.py --help for usage details.
[22:34] <EntropyWorks> I'm got to do the sane thing and nuke this machine and try again :-)
[22:34] <bigjools> so, LC_ALL=en_US sudo -E maas createsuperuser
[22:34] <bigjools> doesn't work?
[22:35] <EntropyWorks> ah! yes that prompted me!
[22:38] <EntropyWorks> yea I see when I run locale
[22:39] <EntropyWorks> LC_ALL=
[22:39] <EntropyWorks> and  LANGUAGE=
[22:39] <EntropyWorks> so thats causing me the issue i guess
[22:41] <EntropyWorks> just reset it to en_US.UTF-8 logged out then back in and tada command works
[22:42] <bigjools> cool