[08:43] <Maassive> Hello every1
[08:44] <Maassive> Im having crisis enlisting nodes
[08:44] <Maassive> can someone help
[08:56] <Maassive> hello???
[08:56] <Maassive> anyone there
[11:04] <gmb> Maassive: Hi, sorry we missed your pings earlier. Are you still having trouble?
[11:05] <Maassive> yes
[11:05] <Maassive> well here is the case. I have managed to enlist my new node
[11:05] <Maassive> and it shows ready
[11:06] <Maassive> however when I start it. it remains on
[11:06] <Maassive> pxelinux.cfg/XX-XX-XX-XX-XX-XX-XX where the X's are a MAC address
[11:06] <Maassive> then revert to pxelinux.cfg/default
[11:06] <Maassive> though 1st time it did boot pxelinux.cfg/XX-XX-XX-XX-XX-XX-XX where the X's are a MAC address
[11:06] <Maassive> is is this ipmi issue?
[11:07] <rvba> Maassive: what do you mean exactly by "it remains on pxelinux.cfg/XX-XX-XX-XX-XX-XX-XX" ?
[11:08] <Maassive> while booting it shows the followng
[11:09] <Maassive> pls gimme 2 min to wirte exact msg
[11:09] <Maassive> quick thing do I need to add the ssh key in MAAS
[11:10] <Maassive> trying to load: pxelinux.cfg/XX-XX-XX-XX-XX-XX-XX where the X's are a MAC address
[11:10] <Maassive> here is what im getting, then shortly it reverts to pxelinux.cfg/default
[11:12] <rvba> Does the pxelinux.cfg/XX-XX-XX-XX-XX-XX-XX file exists?
[11:13] <rvba> This mechanism is in place to let you use a node-specific template if you want to.  But it's normal that the default template is used if you haven't customized anything.
[11:14] <Maassive> but while commissioning it went ok, after finishing the commissioning it showed this
[11:15] <Maassive> is this ipmi issue? or do i need ssh keys to be added
[11:16] <rvba> If your node is ready, it means it went through commissioning fine.  Which means the IPMI config is all right.
[11:17] <rvba> Maassive: if you want to be able to connect to your node, you need to upload your ssh key into MAAS.
[11:18] <Maassive> ssh key of the node? or the main MAAS server??
[11:18] <rvba> Maassive: http://maas.ubuntu.com/docs/juju-quick-start.html#adding-an-ssh-key
[11:18] <rvba> On the MAAS server.
[11:18] <Maassive> trying to find ~/.ssh/id_rsa.pub
[11:18] <rvba> Maassive: that public key will be installed on the node.
[11:19] <Maassive> it doesnt exist on the MAAS server
[11:19] <rvba> It must be on the client from which you'll want to ssh into your node later.
[11:19] <rvba> (i.e. usually your workstation)
[11:21] <Maassive> thx, but how can I get it if I cant even login to the workstation
[11:21] <Maassive> it shows login screen
[11:21] <Maassive> I try the user & pass
[11:21] <Maassive> no luck.
[11:23] <Maassive> the only thing I can access at the moment is the MAAS server
[11:23] <rvba> Okay.  If you want to SSH into the node from there and there is no SSH key you need to create one: simply run 'ssh-keygen -t rsa'
[11:23] <Maassive> the rest shows the login screen: maas-enlisting-node
[11:23] <Maassive> user:
[11:23] <Maassive> pass:
[11:24] <rvba> That's the node.  You don't need to do anything manually on there.
[11:24] <Maassive> u mean run the ssh command on the MAAS server
[11:25] <rvba> Run the ssh-keygen command where you want the key to be created.  Then we will upload that key to the MAAS server.  And then you'll be able to SSH into the node using it.
[11:26] <Maassive> ok will run it on the MAAS server to generate
[11:26] <Maassive> then paste it on MAAS web interface
[11:27] <rvba> Yeah
[11:30] <Maassive> i did that
[11:30] <Maassive> but
[11:30] <Maassive> noticed that the end of the pub file is
[11:30] <Maassive> root@lbgmaas1
[11:30] <Maassive> shall I also include ?
[11:31] <rvba> Yes, all the content of the file.
[11:32] <Maassive> even the begining ssh-rsa
[11:32] <Maassive> I did
[11:32] <Maassive> went back clicked on start node
[11:33] <Maassive> nothing is up
[11:33] <rvba> The machine needs to get installed, it will take a couple of minutes.
[11:33] <Maassive> just the status is now Allocated to root
[11:33] <rvba> Has the machine been powered up?
[11:33] <Maassive> Ive powered it up
[11:34] <Maassive> manually
[11:34] <Maassive> lets see
[11:35] <rvba> You can power it up manually, but if the machine supports IPMI and if the IPMI credentials on the machine are correct, MAAS can do that for you.
[11:36] <Maassive> they are correct
[11:36] <Maassive> however
[11:36] <Maassive> here is what I got
[11:36] <Maassive> could not find kernel image: /amd64/generic//install/linux
[11:38] <rvba> That's not good.  Did you import the install images?
[11:39] <Maassive> yes indeed
[11:40] <Maassive> the maas-import-isos command?
[11:42] <Maassive> ???
[11:42] <rvba> Yes, maas-import-pxe-files
[11:43] <rvba> Did you customize the configuration in /etc/maas ?
[11:43] <Maassive> didnt customise.
[11:44] <Maassive> shall I re-run maas-import-pxe-files
[11:44] <rvba> Yes, please.
[11:44] <Maassive> running maas-import-pxe-files
[11:46] <Maassive> quick thing, does it matter keeping the distro to default
[11:46] <Maassive> ?
[11:48] <rvba> If you're talking about the distro that gets installed on the machine (the one configured on the settings page), it just needs to be in sync with the images being downloaded if you customize the config.
[11:50] <Maassive> I didnt do any customisation for the config. just wondering if it matters to keep the default distro in the node page
[11:51] <Maassive> also would it matter ticking Fallback to Ubuntu master archive option
[11:51] <Maassive> and ticking Keep mirror list up to date
[11:51] <Maassive> and ticking  Fetch new releases automatically
[11:51] <rvba> You can leave these unticked for now.
[11:52] <Maassive> ok unitcked them
[11:52] <Maassive> rebooting the node
[11:52] <rvba> You can change the default distro if you want to install something else.  But let's keep the default until it works.
[11:52] <Maassive> manualy
[11:53] <Maassive> oops still the same
[11:53] <Maassive> shall i do service restart
[11:53] <Maassive> for the MAAS
[11:54] <rvba> No, that shouldn't be necessary.
[11:55] <rvba> Did the import script work without errors?
[11:55] <Maassive> yes it worked with no errors
[11:55] <rvba> Can you paste the output to http://paste.ubuntu.com/ ?
[11:57] <Maassive> http://paste.ubuntu.com/6550718/plain/
[11:58] <Maassive> Dunno but could this be realted to pasting ssh keys after commissioning??
[12:01] <rvba> I don't think it's related.
[12:02] <Maassive> any suggestion??
[12:02] <Maassive> re-ran the command
[12:03] <Maassive> here is the output
[12:03] <Maassive> http://paste.ubuntu.com/6550744/plain/
[12:04] <rvba> Yeah, the import went okay.
[12:04] <rvba> Can you have a look into the MAAS logs and see if you can spot anything suspicious?
[12:04] <Maassive> which path pls
[12:04] <rvba> Maassive: http://paste.ubuntu.com/6550747/
[12:08] <Maassive> thx does this make sense? http://paste.ubuntu.com/6550759/plain/
[12:10] <rvba> It's a bit weird, something/someone tried to add a node using the CLI/API but provided a wrongly-formatted MAC address.
[12:10] <rvba> I don't think it's related to the problem at hand.
[12:10] <rvba> Maassive: I'm especially interesting in the content of '/var/log/maas/pserv.log
[12:10] <rvba> s/interesting/interested/
[12:12] <Maassive> does it make sense http://paste.ubuntu.com/6550777/plain/
[12:17] <rvba> Everything seems all right in there…
[12:19] <Maassive> do u need more than the last 40 line?
[12:19] <rvba> Please paste the entire file just for safety.
[12:21] <Maassive> http://paste.ubuntu.com/6550805/plain/
[12:23] <rvba> In fact, what's at the end of the file doesn't look too good.  Looks like the install image is not present.
[12:25] <rvba> Maassive: I need to step out for a bit, do you mind re-stating the problem (with links to the log files) on http://askubuntu.com/questions/ask (tag=maas), I'll get back to you there.
[13:58] <rvba> gmb: could you please have a look at https://code.launchpad.net/~rvb/maas-test/multiple-archives/+merge/198401 ?
[15:19] <rvba> gmb: my zone listing page branch is up for review: https://code.launchpad.net/~rvb/maas/az-ui-listing/+merge/198372
[15:41] <gmb> rvba: Excellent. I'll do that before I EoD.
[15:44] <rvba> Ta
[16:00] <rvba> gmb: thanks for the review.
[16:59] <roaksoax> smoser: howdy!
[16:59] <roaksoax> smoser: were you able to look at https://code.launchpad.net/~andreserl/maas/package_split_for_charm/+merge/198316
[17:00] <roaksoax> rvba: howdy! so did you see bug #1259299
[17:00] <roaksoax> rvba: i thought the default cluster would be created only when installing maas-cluster-controller on the same machine as the region
[17:00] <roaksoax> and not when the region was the only one being installed
[17:00] <smoser> roaksoax, no. i'd not looked at it.
[17:01] <roaksoax> smoser: coul you please when you have the time? Thanks!
[17:01] <smoser> roaksoax, line 112 looks qustionable
[17:01] <smoser> as does anything that says "if there is an error, ignore it"
[17:12] <roaksoax> smoser: well that's my intention since that mpackage requires a working maas-region-controller working
[17:12] <roaksoax> smoser: and with the split we might not have one
[17:13] <roaksoax> smoser: but i can revert that
[17:14] <roaksoax> smoser: done
[18:23] <roaksoax> smoser: i'm starting with the charm work btw
[21:11] <d1n0> i have a maas process (ipmipower) that is consuming all the cpu, any suggestions