=== lutostag_ is now known as lutostag
=== marlinc_ is now known as marlinc
[14:05] <mup> Bug #1679882 changed: [2.1] rackd status is stuck at "NN% connected to region controllers" with Active-Active regiond <docteam> <MAAS:Incomplete> <https://launchpad.net/bugs/1679882>
[14:21] <Budgie^Smore> o/ juju world
[14:53] <vogelc> anyone else get this error after upgrading to RC2?   maasserver.websockets.protocol: [critical] Error on request (193) general.osinfo: not enough values to unpack (expected 2, got 1)
[15:56] <vogelc> anyone else get this error after upgrading to RC2?   maasserver.websockets.protocol: [critical] Error on request (193) general.osinfo: not enough values to unpack (expected 2, got 1)
[16:23] <pmatulis> vogelc, nope. just upgraded. which log? or was it STDOUT
[16:33] <ikonia> win 4
[16:33] <ikonia> oops
[17:08] <mup> Bug #1683433 opened: MAAS 2.2-rc1 refuses to deploy if all a node's interfaces are set to DHCP <MAAS:New> <https://launchpad.net/bugs/1683433>
[17:25] <alanmac> Hello all! We are trying to standup MaaS on Ubuntu 16.04 - an issue we're running into is trying to get our iLO network recognized (Version 2.1.3 of MaaS). We don't have an actual interface into this network, but do have DHCP helpers forwarding traffic. We have the subnet on the rack controller, but still not working. Do we need an interface into that network still?
[17:30] <Budgie^Smore> (Disclaimer: not an issue I have come across) You may want to make sure that the networks have routes between them, most likely the iLo's can't see the maas server
[17:35] <craigs> @Budgie^Smore I work with alanmac - they can just fine.
[17:45] <Budgie^Smore> craigs hmmm
[17:48] <craigs> actually we have a vlan that is not routed to that nic. we are going to fix that right now.
[17:48] <craigs> hopefully
[17:50] <alanmac> we are also looking to upgrade/re-install to 2.2 beta4 - https://docs.ubuntu.com/maas/2.0/en/release-notes-all#220-beta4
[17:50] <alanmac> DHCP Relay support is a major feature addition
[17:57] <Budgie^Smore> yeah that is an awesome addition :)
[17:57] <craigs> :)
[18:08] <mup> Bug #1683440 opened: 2.2 RC2 upgrade from Beta 4: Traceback error "Not enough values to unpack" on most UI tabs <hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1683440>
[18:16] <vogelc> pmatulis: The error is being logged in regiond.log
[18:39] <mup> Bug #1683448 opened: [2.2] Trackback on regiond start-up <MAAS:Triaged> <https://launchpad.net/bugs/1683448>
[19:06] <sliver> Hello all, installed maas 2.2rc2 and I may have hit a bug with ILO4 control.
[19:06] <sliver> Failed to query node's BMC - Failed to execute ('/usr/bin/ipmitool', '-I', 'lanplus', '-H', '10.62.0.61', '-U', 'administrator', '-P', 'passwordhere', '70:10:6f:bc:4f:c8', 'power', 'status') for cartridge 70:10:6f:bc:4f:c8 at 10.62.0.61: Invalid command: 70:10:6f:bc:4f:c8
[19:06] <sliver> any quick way to adjust the code call to not put in the mac
=== lifeless_ is now known as lifeless
[19:30] <pmatulis> vogelc, hmm, well i don't see it on my end
[19:33] <vogelc> pmatulis: The bug that was opened today is identical to what I have been seeing.   https://launchpad.net/bugs/1683440
[19:39] <mup> Bug #1683465 opened: no easy way to add early commands to curtin <MAAS:Triaged> <https://launchpad.net/bugs/1683465>
[19:44] <pmatulis> vogelc, you upgraded from beta4?
[19:44] <pmatulis> ah, another poster up'd from rc1
[19:45] <pmatulis> odd that i didn't get bit
[19:47] <vogelc> pmatulis: I upgraded from RC1.
[20:56] <alanmac> my coworkers and I are trying to get dhcp relay to work properly (MaaS 2.2 rc2) - we have dhcp helpers pointing to our MaaS deployment server (all in one - with controller), I added a new VLAN to get the option of adding a dhcp relay, then added a subnet - 10.62.0.0/22 to this vlan. but i'm unable to have this subnet show up in the controller.
[21:27] <mup> Bug #1683502 opened: [2.2] Random test failure: test_dehydrate_script_set_status <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1683502>
[21:27] <mup> Bug #1683503 opened: [2.2] Random test failure: test__accepts_mix_of_id_and_ipaddress <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1683503>
[21:31] <mpontillo> alanmac: when you say "show up in the controller", I assume you mean rendered in the DHCP configuration?
[21:32] <mpontillo> alanmac: you'll need to do something like "maas $PROFILE vlan update $FABRIC_NAME $VID relay_vlan=$VLAN_ID" to tell MAAS that packets from $VID are being relayed to $VLAN_ID (you need the database ID for the VLAN for $VLAN_ID)
[21:38] <alanmac> mpontillo I went into more details here: https://askubuntu.com/questions/905989/maas-2-2rc2-dhcp-relay-help
[21:39] <mpontillo> alanmac: can you expand on what you mean by "showing up in the controller"?
[21:39] <mpontillo> alanmac: if the subnet is not defined in MAAS, you must create it first
[21:39] <mpontillo> alanmac: and assign it to the VLAN you expect to relay from
[21:41] <alanmac> I stepped through the doc, had to create a new VLAN, then I added a new subnet - 10.62.0.0/22, this vlan is set with relay dhcp per the guide i quoted above. The issue I'm running into is that when i go to the Controller view and see the list of subnets available/assigned to this controller, this subnet is not one of them
[21:42] <mpontillo> newell: ^ can you take a look at sliver's question above about iLO4? I'm not familiar with that power driver
[21:42] <mpontillo> alanmac: you should be able to browse to the subnet via the top-level subnets tab; it sounds like an oversight in the networks view
[21:43] <mpontillo> alanmac: rather, in the controllers view; we should probably show which VLANs we're relaying for as well as direct attached
[21:45] <newell> sliver: Did you try running that command by itself?
[21:46] <alanmac> mpontillo in regards to sliver's issue - (we work together) - ipmi 2.0 driver works just fine
[21:46] <sliver> yes
[21:47] <newell> sliver: same error I assume?
[21:47] <sliver> the command works fine without the mac in the cli
[21:47] <sliver> same error
[21:47] <mpontillo> alanmac: I figured it might; most people just use the IMPI driver if it works; it's easiest and automatically configures itself when the node enlists, which is nice
[21:47] <sliver> I can pastebin if you desire
[21:47] <mpontillo> sliver: if you can file a bug with the details that would be great https://bugs.launchpad.net/maas/+filebug
[21:48] <sliver> ack, will do tom am
[21:52] <newell> sliver: thanks
[21:57] <alanmac> mpontillo you have time for a webex?
[21:57] <alanmac> not sure what we're missing here
[22:11] <alanmac> we are getting these through tcpdump -i any | grep -i 70:10:6f:bb:ea:28 and then I get this: 15:08:49.918268 IP 10.62.0.36.bootpc > use1foreman.bootps: BOOTP/DHCP, Request from 70:10:6f:bb:ea:28 (oui Unknown), length 300
[22:12] <alanmac> just no response back
[22:12] <mpontillo> alanmac: I answered your stackexchange question with a few more details
[22:12] <alanmac> awesome, looking
[22:12] <mpontillo> alanmac: did you enable DHCP on the VLAN you expect the relayed packets to arrive on?
[22:13] <mpontillo> alanmac: the DHCP server still needs to be told which interfaces on the rack controller it should listen to, so that might be what is missing
[22:14] <mpontillo> alanmac: also, are the iLOs trying to DHCP from MAAS? I'm a little worried about that; if the iLO/IPMI addresses change, that could confuse MAAS in the future.. you might want to make those static IPs for reliability
[22:16] <alanmac> i'm re-enabling dhcp - clicking on the VLAN and setting "Provide DHCP", I'm unable to pull down to select the controller.
[22:16] <sliver> dhcp responds on the dhcp relayed packets fine with we enable a global dynamic pool
[22:17] <sliver> when we set a mac in the ipmi settings with an ip, nothing is set in dhcp.leases
[22:17] <sliver> hence, no response
[22:17] <sliver> are we missing something obvious?
[22:18] <sliver> we do see the shared-network setup in the dhcpd.conf
[22:18] <sliver> no issue there (just gui issue)
[22:22] <mpontillo> sliver: alanmac: ah, I think I see the issue.. so you are saying you want to provide DHCP for the relay VLAN but *not* the interface itself...
[22:23] <sliver> we want to provide DHCP static mappings for BMC(ilo4) devices
[22:24] <sliver> hopefully we are on the same page :)
[22:24] <mpontillo> sliver: okay. so looking at the mailing list posting here https://lists.isc.org/pipermail/dhcp-users/2010-April/011635.html it seems MAAS should provide an empty subnet declaration for the local LAN if it is not being actively used for DHCP
[22:25] <sliver> when we do this with foreman it just sets a leases entry for the mac
[22:26] <sliver> same as I already see for hosts
[22:26] <sliver> is it more expected behavior ilo network is just left dhcp auto assign and deal?
[22:27] <mpontillo> sliver: well that makes MAAS a SPOF for your management network, whereas we would prefer you to still be able to manage your servers if your MAAS server goes up in flames
[22:28] <mpontillo> sliver: I mean, we're flattered, really ;-)
[22:30] <sliver> yea, it's a fairly common design to be honest
[22:30] <sliver> long lease times(30 days) shrug
[22:30] <sliver> we'll work around
[22:31] <sliver> should be some pre-req docs talking about it :>, foreman does it out of the box easily, but trying to get to something better :O
[22:31] <mpontillo> sliver: yeah unfortunately MAAS tends to use short lease times by default, due to the fact that dynamic ranges in MAAS are usually only temporary, and we don't want to burn IPs
[22:31] <sliver> appreciate the assistance
[22:31] <sliver> we'll go back to static ips in our design
[22:32] <sliver> makes fully remote builds more challenging heh
[22:32] <alanmac> greatly appreciated! we'll get these staticly assigned, we're almost there on provisioning, the dynamic ilos were holding us up
[23:18] <kiko> sliver, but you can still give "static" IPs over DHCP, I'm not sure that was clear from what mpontillo pointed out?