/srv/irclogs.ubuntu.com/2017/04/20/#maas.txt

mupBug #1657162 changed: [2.1] cli docs refer to non-existent commands <docteam> <uosci> <MAAS:Fix Released> <https://launchpad.net/bugs/1657162>02:32
mupBug #1664996 changed: MaaS Install Rack Controller:  Instructions Unclear <docteam> <MAAS:Invalid> <https://launchpad.net/bugs/1664996>02:32
mupBug #1666274 changed: MAAS HA broken URL <docteam> <maas-at-home> <MAAS:Fix Released by petermatulis> <https://launchpad.net/bugs/1666274>02:32
babbageclunkbrendand: ping?09:06
brendandbabbageclunk, oh hey09:09
babbageclunkbrendand: hey - did you get anywhere with the Juju 2.2 problem?09:10
babbageclunkI've knocked up a little websocket client that might let us get a bit more detail.09:10
babbageclunkit basically just connects and sends a login09:11
brendandbabbageclunk, oh cool09:11
brendandbabbageclunk, let me get that instance spun up again. if you're short on time you can send me instructions, or we can have a hangout if you want09:11
babbageclunkbrendand: sending it through now - happy to hangout once the maas is spun up09:13
babbageclunkbrendand: I'll be afk for a bit so I won't see IRC responses but send me an email and I'll jump back onto my computer.09:25
brendandbabbageclunk, np09:25
babbageclunkbrendand: oh, also no worries if you're in the middle of something else - happy to try some other time if that's better?09:28
brendandbabbageclunk, no no, i really want to get this solved09:34
babbageclunkbrendand: ok cool09:34
brendandbabbageclunk, ping09:47
babbageclunkbrendand: hey - have a hangout handy?09:48
babbageclunkbrendand: https://hangouts.google.com/hangouts/_/canonical.com/brendan-xtian09:50
brendandbabbageclunk, thanks, i was just making one , but cheers09:50
fabhi12:20
=== fab is now known as Guest95025
Guest95025I am running a MAAS installation on MAAS Version 2.1.3+bzr5573-0ubuntu1 and want to know when new content is considered as stable and if I am on the latest version? I am using the ppa:maas/stable and update it via apt-get update/upgrade regulrarly12:22
Guest95025On https://launchpad.net/~maas/+archive/ubuntu/stable/+packages I found some other builds (different versions after the "bzr" code).. therefore I am not sure if I am current12:23
zeestratGuest95025: 2.1.5 is the latest in the ppa:maas/stable12:27
Guest95025thanks for the input. Are the PPA stored in linux after adding them via sudo add-apt-repository ppa:maas/stable​? I wonder why apt-get update / upgrade does not update the packages...12:28
Guest95025just re-added the PPA; how he founds 2.1.512:29
zeestratGuest95025: Yeah, add-apt-repository should add an entry in /etc/apt/sources.list.d12:29
Guest95025-rw-r--r-- 1 root root  126 Apr 20 14:27 maas-ubuntu-stable-xenial.list <-- should be the culprit; is there any system routine, which removes them?12:31
Guest95025Hmm however that's off-topic. Another question: is there a document which defines or indicates when a new version is getting defined as stable?12:33
Guest95025I found the general release plan https://launchpad.net/maas/+series; however it does not indicate when 2.1.6 is becomming the next stable or when 2.2 or 2.3 are taking over?12:34
Guest95025I got another Question regarding https://bugs.launchpad.net/maas/+bug/1660743; does anybody know why MAAS does not offer DHCP service after making an IP Binding for a MAC? After listing it on the NODES tab, no more IP is provided :-/13:01
Guest95025Could be a bug or maybe a faulty configuration on my side.13:02
kikoGuest95025, the latter doesn't make sense13:02
Guest95025kiko: what do you mean?13:02
kikoGuest95025, I mean, it's a bug or config problem. but the bug you referred to.. just appears to be cosmetic?13:04
Guest95025kiko: I dont think it is cosmetic; Whenever I create a VM to let it beeing installed via MAAS, I expect MAAS to provide an ip. Otherwise, MAAS cannot connect to install an image there?13:05
kikoMAAS always should prove DHCP IP13:05
Guest95025when I click under NODES the new machine and click COMMISSION, there is an error message from MAAS "MAAS is not providing DHCP"13:07
Guest95025An nmap to all Ips managed by MAAS also indicate that the VM retrieved no IP address; before the VM is displayed within "NODES" nmap returned an IP for the VM...13:08
=== lutostag_ is now known as lutostag
mupBug #1684111 changed: MaaS assigns static IP addresses from dynamic range <MAAS:New> <https://launchpad.net/bugs/1684111>17:42
=== frankban is now known as frankban|afk
xygnaltrying to add a dhcp snippet for next-server.  i was able to add it for my first subnet, but the others reject with Unable to validate DHCP config,  no available rack controller.19:52
xygnalall subnets are set for dhcp management19:53
xygnal:/19:53
xygnalmanaged allocation, i mean19:56
xygnaland when i look in dhcpd.conc insee identical blov19:59
xygnalblocks for each subnet, except for their ranges obviosly, and the one subnet that worked has the added snippet.20:00
xygnalverified all subnets using the same rack controller20:00
xygnalwhich shows healthy20:00
newellxygnal: I just pinged the guy on the team who implemented that20:30
newellltrager: ^20:31
ltragerxygnal: what config are you trying to use?20:41
xygnaldefine config?20:43
xygnalall untagged vlan, all same fabric, multiple subnets20:45
ltragerthe snippet you are trying to use20:45
xygnalah, trying to add a next-server block to each subnet20:46
xygnalworked for the first subnet, others refuse with that error20:46
xygnalnext-server ip.ad.dr.ess; is the actual code strong20:48
xygnalwith a real IP obviously20:48
xygnalhm.... I wonder if its because i'm setting next-server that is in a differnet subnet20:49
xygnalwe are using DHCP forwarding I believe (routers forwarding DHCP to our server)20:49
xygnalthinking about it now, yeah.  The IP I am giving it for the first subnet is the same subnet, I believe.  BUt the other subnets, it would be external.20:50
xygnalperhaps that is why20:50
xygnalhonestly just testing possible solutions (from other bug reports) about the problem we are having20:50
xygnalwhere nodes comissioning are given an IP address on the WRONG subnet, and fail comission20:51
ltragerxygnal: so what MAAS does is pass the config you give it to DHCPD, it then validates the config as it is what is using it21:09
ltragerxygnal: your saying your just using next-server <ip address>?21:09
=== lutostag_ is now known as lutostag
=== mup_ is now known as mup
xygnalltrager correct.  Thats all I added.  Worked for the first subnet, same exact syntax with another subnet selected from the dropdown, i get that error22:10
xygnalwhats the proper way to remove a node from the dhcp leases file22:18
xygnalI see *6* copies of the lease for this box failing comission, I want to remove it without confusing MAAS22:18
xygnalso that I can comission again 'clean'22:19
ltragerxygnal: leases should be cleaned up for you22:20
ltragerblake_r, mpontillo: ^?22:20
ltragerxygnal: can you show me the error you are seeing, I havn't been able to reproduce it22:23
mpontilloxygnal: are you sure the lease is still active? the ISC lease file is like a transaction log, not a snapshot of current lease state22:24
blake_rxygnal: the leases clean them self up, the dhcpd.leases file itself is append only so those leases will never go awat22:24
blake_rthat is how isc-dhcp works22:24
blake_rbut the ip address will go free after 10 minutes22:24
xygnalgotcha22:27
blake_rso you using dhcp relay22:28
blake_rdoes your dhcpd.conf look correct?22:28
ltragerI'm wondering if next-server can only be used once?22:29
xygnalIts a per-subnet keyword22:30
xygnalI can put it in global and it accepts it but somehow i imagine it doesnt work22:31
xygnalwe are using dhcp relay in that we have them forwarding DHCP requests from those subnets to our own server22:31
ltragerxygnal: could you post the full error message your getting?22:31
xygnalltrager the full error was pasted above22:32
blake_rxygnal can you post the maas generated dhcpd.conf and your dhcp relay config on the bug22:32
xygnalblake: the one I just updated?22:32
blake_ris commissioning getting the wrong IP or is it just deployment22:33
blake_ryes the bug your commenting on22:33
xygnalwe apparently dont have any relay configured in MAAS itself.22:33
xygnalI think we did not think we needed it22:33
xygnalas all of the subnets are in the same fabric and vlan22:33
xygnaland the forwarding of DHCP requests is being done via the router22:34
xygnalif we need to have dhcp relay components beyond this enabled and configured, please point me to the info on it22:35
xygnalso I can make sure we are doing that correctly22:35
xygnalstill want the config, or is my config 'invalid' the way we are using it?22:35
xygnalyeah.  the docs seem to reference relaying between VLANs, and we are not using VLANs22:36
mpontilloxygnal: you must tell MAAS which VLAN is the VLAN the traffic is being relayed to22:37
xygnalall one fabric, one network interface, untagged, many subnets22:37
xygnalthere is no VLAN.  All untagged.22:37
mpontilloxygnal: for example, browse to the VLAN with the helper address in the UI, and there should be a "Relay DHCP" command; you should use that to specify which VLAN on the rack receives the relayed DHCP traffic22:38
mpontilloxygnal: ... I'm confused then; how would the DHCP server know which network to provide the IP from if it's just a single flat network?22:39
blake_rxygnal: yeah I am with mpontillo, if its flat the dhcp relay is not needed22:39
xygnalthats why we didnt enable dhcp relay22:39
mpontilloxygnal: ok, maybe I was confused since your attachment on the bug was called "dhcp_relay.pdf" ;-)22:40
xygnalyes... corey wrote that part22:40
xygnalwe forward the DHCP traffic from the routers of each subnet22:41
xygnalso when the DHCP request comes in, it comes from the IP of that router22:41
mpontilloxygnal: yes, I understand that. but that still sounds a bit unconventional. so a host comes online and it broadcasts out a DHCP request. so all the routers on the network with a configured IP helper address are going to forward that DHCP request to MAAS. first one wins?22:42
xygnalwe had hoped that hte source address of the forward would be the clue DHCPD needed to know which subnet it should be22:42
xygnalas the source address of the forward is aways the router for that subnet22:43
xygnalbut i'm guessing that does not work? is that an official it wont work?22:43
xygnalneed to be sure if we are going back to the drawing board22:43
mpontilloxygnal: you have indeed described how DHCP works, in general, but I do not believe it will work in that specific configuration you described, with multiple forwarders on the same L2 networks22:44
mpontillo*network22:44
mpontilloxygnal: what is going to happen is you will amplify the DHCP requests on that network segment and the DHCP server will see N request packets, where N is the number of routers configured with an IP helper address22:45
xygnalwait wait22:45
xygnalok22:45
xygnalso if i have multiple subnets listed in one fabric, which means all one shared-network entry in DHCPd.conf22:45
xygnalit can't tell which host should go in which one?22:46
xygnalis that BECAUSE of the forwarding on the switches that it is unable to tell?22:46
mpontilloxygnal: yeah; MAAS needs to know which networks are on with fabrics (and/or VLANs) it sounds like maybe you need to create multiple fabrics in MAAS22:46
xygnalwe tried multiple fabrics,  and that allows comissions to pass, but then deployments failed to get a DHCP address at all and fails with Unconfigured for network22:47
xygnalwhen digging on how you are supposed to do multiple subnets on the same interface,  the shared-networks option in dhcpd,conf appeared to be the right syntax to use22:48
mpontilloxygnal: the fabrics in MAAS should match your network topology and you should browse to the untagged/default VLAN on each fabric and tell it which fabric on the rack controller the traffic is being relayed to22:48
xygnaland one fabric = one shared-network in dhcpd.conf22:48
mpontilloxygnal: MAAS should configure that appropriately if the fabrics are modeled correctly22:48
xygnali'm a little confused on what correct configuration would be then22:49
xygnalI thought relaying could not be used unless we had VLANs being used22:49
xygnalso seperate subnets on the same untagged VLAN should be in seperate fabrics?22:50
xygnalone per subnet?22:50
mpontilloxygnal: can you post a topology diagram of your network somehow? it's unclear to me exactly what you're doing. separate subnets on the same untagged VLAN is just fine, but I very much doubt that multiple DHCP relays on the same L2 segment will work in any scenario, MAAS or not22:53
xygnalyes its the switch for each subnet that is forwarding22:55
xygnalso each subnet has ONE forwarder22:55
xygnaldedicated to that subnet22:55
xygnaldont think I have a  toplogy handy.  I'll talk to Corey about that tomorrow to see if he alrady has something.22:56
xygnalall of the switches are on VLAN500, but that is the 'native vlan', so no tagging is needed22:57
xygnalnative vlan, as in, on the cisco switch's settings22:57
xygnalthere should never be any forwarding by more than one switch for the same subnet22:58
xygnalso i'm a little confused about how you think multiple forwarders is a problem there22:58
mpontilloxygnal: yes, if each L2 and each L3 subnet has one forwarder, that should be fine.  I may have misunderstood one of your earlier statements. sounds like the issue is that each L2 needs to be modeled as a separate fabric in MAAS23:03
xygnalthese are all the same L2 then, no?  Its L3 that is different subnet to subnet23:04
xygnalok i see23:07
xygnaleach subnet is a seperate23:08
xygnalits own L2 vlan (port-tagged)23:08
xygnalso we would need a fabric for each subnet then23:08
xygnalyes?23:08
xygnalwe tried the separate fabric, and that got us past Comission failures, but thats when we started having Deploy failures that would fail with no network (Unmanaged) even though it had a network when we selected Deploy23:09
xygnalwe'll switch over the seperate Fabrics per L223:09
xygnalgather data on the DEPLOY problem23:10
xygnaland update the bug report23:10
xygnalsound good?23:10
mpontilloxygnal: yeah, so each port-tagged subnet would be considered its own l2 and thus its own fabric, that's where you had me confused. in MAAS a VLAN on a fabric should be its own broadcast domain23:21
mpontilloxygnal: is each subnet configured on the same interface on the rack controller? I fear that might be throwing off MAAS too.23:24
mpontilloxygnal: because when MAAS looks at that network it may assume all those subnets are thus on the same L2, even if it's on the same L2 only on the rack controller?23:24
mupBug #1683909 changed: [2.2] Subnet changes during deployment <MAAS:Opinion> <https://launchpad.net/bugs/1683909>23:33

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!