[00:00] <batkins61> But 2.0 doesn't provide for static IP address assignment, other than snippits, correct?  I require that, because I have to slot these servers into specific addresses.
[00:01] <roaksoax> batkins61: 1.9+ allos you to xonfigure the interface in 3 ways "auto-assign" which is mAAS picks an IP for you automatically and writes e/n/i for it
[00:01] <roaksoax> batkins61: "static" you can change the IP to what you want (and MAAS writes e/n/i)
[00:02] <roaksoax> batkins61: or DHCP, which means what ever ip address you can get
[00:02] <batkins61> When I tried to select "static", the menu refused to stick, and always reset to Unconfigured
[00:02] <roaksoax> batkins61: check the logs in /var/log/maas/*.log and see if there is an error
[00:03] <roaksoax> batkins61: when you are trying to change it as static
[00:05] <batkins61> After commissioning, the interface is set to auto assign.  I tried to change it to static, but it ignores that.  Setting to DHCP with snippits works, and the nodes commission and deploy
[00:05] <batkins61> I can ICMP ping them, but they refused connect on 22.
[00:06] <roaksoax> batkins61: i have not tested what you've done, but 'static' should work, and if it doesn't there must be an error going on
[00:07] <roaksoax> batkins61: it you could please look at /var/log/maas/*.log while setting the interface as static
[00:07] <roaksoax> batkins61: and if you could file  abug
[00:07] <batkins61> Ok, let me try again.
[00:07] <roaksoax> even better
[00:07] <roaksoax> so we can fix it
[00:19] <roaksoax> batkins61: did it work ?
[00:26] <pmatulis> roaksoax, hi, can we get the topic in this channel to point to the new doc site?
[00:39] <mup> Bug # changed: 1052870, 1237723, 1253940, 1272018, 1301833, 1304613, 1306372, 1308802, 1309593, 1311119, 1313580, 1313723, 1315071, 1317677, 1317978, 1326827,
[00:39] <mup> 1330762, 1340254, 1344125, 1350459, 1351247, 1352938, 1361673, 1361773, 1376395, 1386482, 1389033, 1389809, 1389852, 1392378, 1459441, 1462635, 1623598
[00:51] <mup> Bug # changed: 1379155, 1379636, 1390145, 1430129, 1430324, 1437221
[00:57] <mup> Bug # opened: 1379155, 1379636, 1390145, 1430129, 1430324, 1437221
[01:09] <mup> Bug # changed: 1379155, 1379636, 1390145, 1430129, 1430324, 1437221
[13:07] <mup> Bug #1629868 opened: times out because of no dbus <maas-ipv6> <cloud-init (Ubuntu):New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1629868>
[14:41] <mup> Bug #1629896 opened: [2.1] Deployment defaulting to hwe-16.04 instead of ga-16.04 <MAAS:New> <https://launchpad.net/bugs/1629896>
[14:50] <mup> Bug #1629896 changed: [2.1] Deployment defaulting to hwe-16.04 instead of ga-16.04 <MAAS:New> <https://launchpad.net/bugs/1629896>
[14:53] <mup> Bug #1629896 opened: [2.1] Deployment defaulting to hwe-16.04 instead of ga-16.04 <MAAS:New> <https://launchpad.net/bugs/1629896>
[15:41] <mup> Bug #1629909 opened: [FFE] New upstream release MAAS 2.1 <maas (Ubuntu):New> <https://launchpad.net/bugs/1629909>
[15:56] <mup> Bug #1629915 opened: Specifying the default gateway in an interface different than the provisioning one does not work <MAAS:New> <https://launchpad.net/bugs/1629915>
[15:56] <mup> Bug #1629909 opened: [FFE] New upstream release MAAS 2.1 <maas (Ubuntu):New> <https://launchpad.net/bugs/1629909>
[16:39] <ybaumy> hi. im using 2.1.0~alpha4+bzr5397-0ubuntu1~16.04.1 and now im having connection issues. the hosts are getting dhcp ipv4 addresses but then... http://imgur.com/a/7yWBT
[16:39] <ybaumy> and the commissioning fails
[16:40] <ybaumy> seems like the nodes are trying to use ipv6 addresses
[16:42] <ybaumy> 2016-10-03 18:07:42 [RegionServer,1,::ffff:192.168.10.1] Successfully configured DHCPv4 on rack controller '4y3h7n'.
[16:42] <ybaumy> 2016-10-03 18:07:42 [RegionServer,1,::ffff:192.168.10.1] Successfully configured DHCPv6 on rack controller '4y3h7n'
[16:51] <pmatulis> ybaumy, i'm getting something similar. commissioning fails due to DHCP
[16:51] <baldpope> ybaumy, does the network your handing out dhcpd leases from allow traffic through firewall to internet?
[16:52] <ybaumy> yes it does
[16:52] <ybaumy> the nat is configured on the ASA
[16:53] <ybaumy> at least on the maas server its working
[16:54] <pmatulis> ybaumy, whoah, weird. after rebooting my maas yet again my node has enlisted. that wasn't happening before
[16:56] <ybaumy> hmm i dont know whats going on. how do i disable ipv6 completly. im not using it anyways
[17:01] <pmatulis> ybaumy, no idea. but commissioning seems to be proceeding as normal now (for me)
[17:02] <ybaumy> hmm maybe i know what the problem is. my dns servers changed and the proxy log shows still the old ones. which file is used for the dns servers in maas
[17:03] <pmatulis> ybaumy, i noticed when i was in a broken state the logs where showing that the rackd and regiond had lost connectitivy
[17:03] <pmatulis> this was also reflected in the web UI
[17:03] <pmatulis> yup, my node is in the 'Ready' status now
[17:32]  * baldpope sigh
[17:32] <baldpope> is there a current doc for deploying openstack/autopilot ?
[17:33] <baldpope> the one listed on ubuntu's site appears out of date with the current UI
[17:47] <HeOS> Hello! Could you say me, how can I debug a situation, when maas can't connect to SuperMicro's BMC?
[17:47] <HeOS> I see, that mass got an IP-address of the BMC, but it can't operate by power actions on the server.
[17:49] <HeOS> I've tired to run ipmitool on the controller, it works, I can connect to the server and operate it, but MAAS can't.
[17:56] <mup> Bug #1629868 opened: times out because of no dbus <maas-ipv6> <MAAS:New> <cloud-init (Ubuntu):New> <https://launchpad.net/bugs/1629868>
[17:56] <mup> Bug #1629868 changed: times out because of no dbus <maas-ipv6> <MAAS:New> <cloud-init (Ubuntu):New> <https://launchpad.net/bugs/1629868>
[17:57] <kiko> HeOS, that's odd -- what happens when MAAS tries to connect?
[17:58] <HeOS> kiko, when I add my credentials there, then I see the following error: "Connection timed out while performing power action. Check BMC configuration and connectivity and try again. "
[17:58] <HeOS> I don't see nothing in the maas' logs.
[17:58] <kiko> HeOS, I guess the first question I have is why hasn't auto-enlistment work for you?
[18:00] <HeOS> auto-enlistment is working, I see credentials there, but maas can't power on, for example, my server. So, my question is the following: how can I figure out why it's happened?
[18:01] <HeOS> kiko, I don't know, what I should to do. :(
[18:02] <kiko> HeOS, is there an IP address problem on the rack/cluster controller?
[18:02] <kiko> i.e. is it using the wrong IP address to connect?
[18:02] <kiko> HeOS, there will be something in /var/logs/*
[18:03] <HeOS> kiko, I can connect to the IPMI's ip-address from the controller by using ipmitool, it works.
[18:03] <kiko> HeOS, the question is how does it fail?
[18:03] <kiko> and the logs can tell us
[18:04] <HeOS> kiko, I'm using the following version: 2.0.0+bzr5189-0ubuntu1.
[18:04] <HeOS> kiko, what a kind of logs can help?
[18:05] <mup> Bug #1629868 changed: times out because of no dbus <maas-ipv6> <MAAS:New> <cloud-init (Ubuntu):New> <https://launchpad.net/bugs/1629868>
[18:05] <kiko> HeOS, /var/log/maas/* on the controller should help
[18:06] <HeOS> There are two files: maas.log rackd.log.
[18:08] <kiko> yep, look through those when attempting to boot the machine
[18:08] <kiko> i.e. sudo tail -f /var/log/maas/*
[18:08] <mup> Bug #1629868 opened: times out because of no dbus <maas-ipv6> <MAAS:New> <cloud-init (Ubuntu):New> <https://launchpad.net/bugs/1629868>
[18:08] <HeOS> I'm going to repeat my actions right now to get all related information from the logs. :)
[18:10] <kiko> thanks!
[18:13] <HeOS> kiko, I see only this files changed: http://paste.openstack.org/show/584061/.
[18:13] <kiko> HeOS, what did tail -f show when you clicked the button?
[18:13] <kiko> that file isn't very useful
[18:14] <kiko> roaksoax, blake_r, mpontillo: any hint as to what could be wrong above?
[18:14] <mup> Bug #1629868 changed: times out because of no dbus <maas-ipv6> <MAAS:New> <cloud-init (Ubuntu):New> <https://launchpad.net/bugs/1629868>
[18:17] <mup> Bug #1629868 opened: times out because of no dbus <maas-ipv6> <MAAS:New> <cloud-init (Ubuntu):New> <https://launchpad.net/bugs/1629868>
[18:19] <HeOS> kiko, what a button should I click?
[18:19] <HeOS> Do you mean the "Save" button in the IPMI-related config?
[18:21] <HeOS> No new information in the logs.
[18:21] <HeOS> I only see "Power error check now" message in the MAAS UI.
[18:22] <kiko> that's what we want
[18:22] <HeOS> kiko, can I enable more informative log level for the tool?
[18:24] <kiko> HeOS, you see nothing in the logs?
[18:24] <kiko> that's so strange
[18:25] <blake_r> HeOS: MAAS uses ipmipower to power control the machine, try that versus using ipmitool
[18:25] <HeOS> kiko, yes, I'm.
[18:25] <HeOS> BMC-related information: http://paste.openstack.org/show/584065/.
[18:38] <HeOS> blake_r, kiko, thanks, looks like ipmipower or BMC related problem. I'll try to inve
[18:38] <HeOS> *investigte it.
[18:40] <kiko> HeOS, thanks -- it's odd
[18:41] <baldpope> HeOS, i'm using supermicro mobo with maas - power control works fine - what's going on
[18:45] <baldpope> kiko, is there a newer doc for deploying openstack via maas/autopilot?
[18:45] <kiko> baldpope, it's called conjure-up :-) let me find a doc
[18:45] <kiko> http://conjure-up.io/
[18:46] <baldpope> kiko, looks cool
[18:46] <kiko> baldpope, however, note the "preview release"
[18:46] <baldpope> does this replace the work with juju?
[18:46] <kiko> well, it drives juju
[18:47] <kiko> but through a very nice front-end
[18:47] <baldpope> my mistake
[18:47] <baldpope> do you still need to go through the prep with maas - re: discover/commission of the new blades?
[18:48] <kiko> baldpope, yep
[18:48] <kiko> the entire stack depends on MAAS doing what it needs to
[18:49] <baldpope> k - stupid question - i wiped and re-installed my maas box - i noticed on the 16.04 install, an option for maas / rack controller install option
[18:49] <baldpope> versus the standard ubuntu install
[18:50] <baldpope> if the end results is intended to be a maas box, should I pre-select the appropriate install, or am I fine with installing via apt - post system install
[18:53] <kiko> baldpope, it doesn't really make that much difference.
[18:54] <kiko> baldpope, the maas install just leaves the machine with maas preinstalled
[19:02] <mup> Bug #1629972 opened: networking stop incorrectly disconnects from (network) root filesystem <maas-ipv6> <MAAS:New> <ifupdown (Ubuntu):New for lamont> <ifupdown (Ubuntu Xenial):New> <https://launchpad.net/bugs/1629972>
[19:05] <HeOS> baldpope, looks like, I have old version of the IPMI's firmware.
[19:05] <baldpope> HeOS, i had firmware issues with ikvm - supermicro support was reasonable in getting me an updated one
[19:10] <HeOS> Yay, it works, when I use the following command: ipmipower --workaround-flags=nochecksumcheck,noauthcodecheck -h <host> -u <user> -p <pass>
[19:41] <mup> Bug #1629982 opened: [2.1] After upgrade from 2.0 to 2.1, iscsi cannot be updated. <MAAS:New> <https://launchpad.net/bugs/1629982>
[20:37] <baldpope> yo kiko , for maas-oath - should use the api key?
[20:37] <kiko> baldpope, I think the answer is yes?
[20:38] <baldpope> you guys are killing me with being unable to paste the api key
[20:42] <kiko> baldpope, what do you mean?
[20:42] <kiko> baldpope, the API key in the MAAS web UI can't be pasted?
[20:43] <baldpope>  copy the api key from web ui, attempt to paste in conjure-up (also through openstack-install) , paste no work
[20:44] <baldpope> quit conjure, and I can paste in the putty terminal
[20:46] <baldpope> actually, maas-oauth must be looking for something different, because conjure doesn't prompt for a username, just the maas-server and maas-oauth
[20:47] <stokachu> baldpope: did you try shift+insert
[20:47] <stokachu> to paste in putty
[20:48] <baldpope> i did not stokachu , i'll try that
[20:49] <kiko> stokachu, baldpope has a point though, does the token include the user information in it?
[20:49] <stokachu> its just the api key you get from your accounts page
[20:49] <stokachu> you dont enter a username or anything
[20:49] <baldpope> http://imgur.com/W4TNZF1
[20:49] <baldpope> ok, i'll try again
[20:50] <kiko> so the key is globally unique
[20:50] <kiko> ok :)
[20:50] <baldpope> shift insert worked, ty stokachu
[20:50] <baldpope> that shit was driving me nutz
[20:50] <stokachu> yea shift+insert is not well known for some reason
[20:50] <stokachu> but it's what i always use
[20:51] <baldpope> i've always just used right click
[20:51] <stokachu> baldpope: yea that won't work with the ncurses stuff we're doing
[20:52] <baldpope> appreciate the tip - you know how many times I've had to type that api key out
[20:52] <stokachu> yea :( i know your pain
[20:52] <baldpope> almost enough to make me ditch and go to virtual pc ;)
[20:52] <baldpope> or hyper-v
[20:52] <baldpope> hah
[20:54] <baldpope> ok, after putting in maas server ip, and api key and clicking add credential, i get an error - unable to find home/user/.local/share/juju/accounts.yaml
[20:57] <baldpope> http://imgur.com/93nzldG
[21:23] <baldpope> odd, i removed the log file and ran again, worked this time - odd...
[21:23] <baldpope> i'm at deploying openstack-base
[21:30] <baldpope> also, not sure if it's supposed to have or not, but the public key tied to my user in maas did not got applied to the ubuntu account during the initial deployment when running conjure-up
[21:30] <baldpope> the assumption is that it should have?
[21:47] <cmart> Does anyone know how to get MAAS to release an IP address which was previously statically auto-assigned to a node, but that node has been deleted?
[21:52] <roaksoax> cmart: yes
[21:53] <roaksoax> cmart: hwen you delete a node it should delete all ip addresses owned by that node
[21:54] <cmart> I don't think that happened. My Subnet view in the web interface shows that the IP address is owned by "MAAS". Usage "Unknown", Interface "Unknown", Type "Static". I'm looking for a way to remove this entry in both the GUI and the CLI, and coming up short.
[21:55] <cmart> I'm only trying to re-use the IP address. MAAS won't let me statically assign it to a node, says that it conflicts with an existing IP.
[21:58] <cmart> roaksoax: "IP address is already in use."
[22:00] <roaksoax> cmart: that seems like a bug
[22:00] <roaksoax> cmart: can you please file a bug and point me to it ?
[22:13] <PCdude> hey all :)
[22:13] <PCdude> I have some questions about openstack, to prevent myself from spamming this IRC channel, I have put it in an askubuntu question
[22:13] <PCdude> http://askubuntu.com/questions/832736/openstack-with-autopilot-some-networking-clear-up
[22:13] <PCdude> Some are MAAS specific therefore I post it here
[22:34] <mup> Bug #1630034 opened: Cannot re-use static IP address <maas-cli> <ui> <MAAS:New> <https://launchpad.net/bugs/1630034>
[22:34] <cmart> ^ roaksoax ^ as requested :) Thanks so much for taking a look.
[22:51] <cmart> roaksoax I pasted the output of a couple SQL queries as a comment. I'm thinking of just deleting the row in maasserver_staticipaddress
[23:24] <roaksoax> cmart: thank you for filing, we will inviestigate that
[23:28] <cmart> roaksoax: more detail in the comments, but I worked around/resolved the issue for myself
[23:29] <roaksoax> cmart: great! thank you!
[23:29] <cmart> by deleting the static IP from the database. it's not a great solution (doesn't identify the root cause of how the address got in that state), but got me past the problem.
[23:31] <roaksoax> cmart: you could have tried doing it via the webui :)
[23:31] <cmart> I did, there was no way that I could find to delete it. I tried all I could in the web UI and API before touching the DB directly.