=== narindergupta is now known as narinderg_cfk
Razvahaasn you around?11:09
Razvait seems that my LAN servers cannot detect MAAS DHCP11:12
Razvaany ideas of how to debug this?11:12
Razvaps aux | grep dhcp11:13
Razvadhcpd     6631  0.0  0.0  32916 13324 ?        Ss   13:04   0:00 dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/maas/dhcp/dhcpd.pid -cf /var/lib/maas/dhcpd.conf -lf /var/lib/maas/dhcp/dhcpd.leases eno211:13
Razvaroot      6740  0.0  0.0   9496  2192 pts/1    S+   13:06   0:00 grep --color=auto dhcp11:13
Razvaeno2 being the LAN nic11:13
roaksoaxRazva: i'd connect a machine to that network and try to DHCP13:29
Razvaroaksoax that's exactly what I'm doing13:38
Razvabut seems that the "client" doesn't "asks" for DHCP13:38
RazvaI've reinstalled Ubuntu 14 + MAAS, the result is the same13:39
Razva0:00 /usr/sbin/dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/maas/dhcp/dhcpd.pid -cf /var/lib/maas/dhcpd.conf -lf /var/lib/maas/dhcp/dhcpd.leases em213:40
Razvaem1       Link encap:Ethernet  HWaddr d4:ae:52:c7:0f:4d13:40
Razva          inet addr:  Bcast:  Mask:
Razvaem2       Link encap:Ethernet  HWaddr d4:ae:52:c7:0f:4e13:40
Razva          inet addr:  Bcast:  Mask:
Razvaauto em213:41
Razvaiface em2 inet static13:41
Razvamaas-dhcpd start/running, process 112313:42
Razvaisc-dhcp-server stop/waiting13:42
roaksoaxRazva: my guess is that this has to do something with your network / switch configuration13:42
RazvaI've contacted the DC, they are "investigating". God I'm so tired about this issue.13:57
Razvaofftopic: do you recommend using Flat layout or LVM, for Ubuntu Cloud setups?13:57
roaksoaxRazva: depends on what you want/need. Right now we are defaulting to Flat layout for backwards compatibility. For the future, we may default for LVM13:59
=== narinderg_cfk is now known as narindergupta
Razvaok, so should I use LVM for a new cluster?14:04
roaksoaxRazva: that's totally up to you :)14:06
haasnRazva: if you manually set up networking information, can the machines reach each other?14:10
haasnRazva: also check tcpdump on all machines14:10
=== Guest76507 is now known as med_
kikoRazva, typically you'd use flat for "cattle-style" app deployment15:07
mupBug #1546143 opened: Web UI crashes when rack controller not available <MAAS:Triaged> <MAAS trunk:Triaged> <https://launchpad.net/bugs/1546143>15:31
Razvaroaksoax just fyi, it WAS a networking issue17:01
Razvaso I've lost ~3 days because of a darn DC admin who was unable to understand the simple fact that I want to DHCP boot from my VLAN :)17:01
kikoRazva, perhaps you'd be surprised to know that in any deployment canonical does, getting the setup to the point where maas can be installed and works is often a week!17:03
kikoRazva, on the roadmap we have some network health checking built in that will improve this piece of the game17:04
mupBug #1546208 opened: Spurious test failure in TestMachinePartitionListener.test__calls_handler_with_update_on_update <tests> <MAAS:Triaged> <https://launchpad.net/bugs/1546208>17:23
Razvakiko wow. well the issues were simple...17:31
Razvalike...IPMI wasn't started on iDRAC, the VLAN didn't allowed DHCP, we had another DHCP server running without our agreement etc. but all were "solvable" by me (I'm a newb)17:32
kikoRazva, simple but waste a lot of time, I bet?17:45
mupBug #1546235 opened: Spurious test failure in TestPrivateCacheBootSources.test__doesnt_have_env_http_and_https_proxy_set_if_disabled <tests> <MAAS:Triaged> <MAAS trunk:Triaged> <https://launchpad.net/bugs/1546235>18:20
Razvakiko yup, 3 days.18:30
kikoRazva, that's what I meant18:31
Razvayeah but still, they ask for a private switch, specific hardware and so on. so their request is...ideal.18:31
Razvamost issues I had with networking and me not knowing some basic things, like the fact that you have to set the VLAN nic to boot from the VLAN :D18:32
Razvaany idea why maas doesn't shows any disks for machines in "Ready" state?18:36
Razvaipmipower -D LAN_2_0 -h -u root -p G5djW*pbv --stat18:36
Razvadamn now I need to reset IPMI password :))))))))18:36
RazvaStorage 0.0GB over 0 disks18:37
kikoRazva, if you just reenlist the node MAAS sets up IPMI automatically in the enlistment process18:39
kikoRazva, there's no need to mess with the creds directly18:39
kikoRazva, the storage thing is interesting, did you successfully commission? if so, can you take a look at your hardware output on the node view and see if storage was detected correctly?18:39
Razvakiko solved my re-comissioning everything. weird.19:14
Razvathey all successfully comissioned previously.19:14
Razvaany idea if Dell servers require IPMI to be enabled from DRAC?19:20
kikoRazva, I'm pretty sure they do19:24
dbainbriIs MAAS filtering out lease updates to DNS (bind9) if the MAC address is not a known node? Is there a setting to make this not happen so all leases are updated to DNS?19:24
kikoall leases are sent to DNS dbainbri19:25
kikothe dynamic range is sent in a bulk zone19:25
kikoand provisioned nodes and devices are added individually19:26
kikothis is all assuming 1.919:26
kikodbainbri, having said that, I think we did receive a bug report where some leases were missing19:26
kikodbainbri, or a verbal/IRC report if not an actual bug19:26
dbainbriok, it looks like only those leases handed out to PXE boot devices (and in the node list) are being updated in the zone file19:33
dbainbrii am using 1.919:34
dbainbrii have some other devices that are getting addresses from DHCP, but are not making it to the zone file.19:34
kikodbainbri, do the generated DNS zone files have GENERATE statements that should cover the IPs that were handed out?19:38
kikodbainbri, if not, could you file a bug including them and the details for the nodes and actual queries (dig, etc) that are returning NXFOUND?19:39
kikookay, either way it's a bug then19:39
dbainbriok, i will take one last look around and if nothing sticks out, i will file a bug, thx.19:39
kikoI need to split but if you file it and /msg me I'll look into it tomorrow as this confirms a suspicion I have19:39
kikothanks very much19:39
kikoroaksoax, ^^19:39
roaksoaxkiko: bah, he left, but all devices that get IP's from dynamic range get a DNS based on IP19:46
mupBug #1546301 opened: "auto assign" on unmanaged subnet used the gateway IP for the node <kanban-cross-team> <landscape> <MAAS:Fix Committed> <MAAS 1.10:Triaged> <MAAS 1.9:Triaged> <https://launchpad.net/bugs/1546301>21:00
mupBug #1546301 changed: "auto assign" on unmanaged subnet used the gateway IP for the node <kanban-cross-team> <landscape> <MAAS:Fix Committed> <MAAS 1.10:Triaged> <MAAS 1.9:Triaged> <https://launchpad.net/bugs/1546301>21:06
mupBug #1546301 opened: "auto assign" on unmanaged subnet used the gateway IP for the node <kanban-cross-team> <landscape> <MAAS:Fix Committed> <MAAS 1.10:Triaged> <MAAS 1.9:Triaged> <https://launchpad.net/bugs/1546301>21:12
stormmoreamazing what you can learn about a dev team just by watching the bug changes. I love that “feature” guys :)21:24
mupBug #1544779 opened: m400 cartridge (mcdivitt) unable to deploy Xenial <curtin:New> <MAAS:New> <maas-images:New> <https://launchpad.net/bugs/1544779>22:28
Razvaany idea if Ubuntu Cloud will support the upgrade from 14 LTS to 16 LTS?22:38
Razvabecause at this point we're deploying 14 LTS (15 had a ton of issues)22:38
=== CyberJacob_ is now known as CyberJacob
=== CyberJacob is now known as Guest75342
=== hazmat_ is now known as hazmat
dbainbrikiko: submitted as https://bugs.launchpad.net/maas/+bug/154634423:45
roaksoaxdbainbri: DNS mappings are only given based on node names for the IP the PXE interface gets in 1.923:49
roaksoaxdbainbri: for anything else that get;s an IP from the Dynamic range, the DNS is based on the IP itself23:49
roaksoaxdbainbri: ah, you are using 1.8 even. Yeah so DNS for stuff in dynamic range is based on ip: 192-168-1-1.maas or similar23:51
mupBug #1546344 opened: DNS not being updated with hosts not managed by MAAS <MAAS:New> <https://launchpad.net/bugs/1546344>23:52
dbainbri@roaksoax: so MAAS isn't meant to propagate names to bind or things it gives IP addresses, except if they are PXE boot nodes?23:52
dbainbri@roaksoax: i.e. doesn't use the client ID23:53
roaksoaxdbainbri: right, so MAAS would provide DNS based on the node name for the machines we deploy, but only for the IP of the PXE interface23:55
dbainbri@roaksoax: fwiw, i son't see names based on the IP in the DNS files either (for those hosts that are not MAAS nodes)23:55
roaksoaxdbainbri: this is generated dynamically23:56
roaksoaxdbainbri: ping 192-168-1-2.maas -> try to ping like that ?23:56
dbainbriroaksoax: ok, unfortunate. would like to see it generate names for everything, at least as a config options23:56
roaksoaxdbainbri: that's not a 1.8/1.9 thing. There will be PTR records for everything that MAAS assigns statically on 2.0 though23:57
dbainbrithe IP based name (192-168-x-x.maas) isn't in the zone files and ping does not work23:58
dbainbriok, had to use the right domain (which i have customized) and that worked, but doesn't really help me ;)23:59
roaksoaxdbainbri: $GENERATE 28-150 $.10.168.192.in-addr.arpa. IN PTR 192-168-10-$.maas.23:59
roaksoaxthat's mi zone file, for example23:59

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