| === mpontillo_ is now known as mpontillo | ||
| mup | Bug #1555392 opened: [2.0a1] python3-maas-client needs to send data as bytes() <MAAS:New> <https://launchpad.net/bugs/1555392> | 00:54 |
|---|---|---|
| mup | Bug #1555393 opened: [2.0a1] python3-maas-client API 2.0 seems to no longer use op but MAASClient.post requires it and incorectly passes it along <MAAS:New> <https://launchpad.net/bugs/1555393> | 00:54 |
| mup | Bug #1539739 changed: Memory size reported by MAAS less than actual memory size by 1GB for commissioned VM <oil> <MAAS:Confirmed> <https://launchpad.net/bugs/1539739> | 01:24 |
| mup | Bug #1555406 opened: API needs to report what images have been sync to what rack controllers <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1555406> | 02:33 |
| === med_ is now known as Guest93664 | ||
| mup | Bug #1555570 opened: Problem commissioning nodes (2.0) <MAAS:New> <https://launchpad.net/bugs/1555570> | 11:46 |
| mup | Bug #1555570 changed: Problem commissioning nodes (2.0) <MAAS:New> <https://launchpad.net/bugs/1555570> | 12:38 |
| mup | Bug #1555595 opened: Changes in the UI between versions are not detected unless you clear browser cache <MAAS:Confirmed> <https://launchpad.net/bugs/1555595> | 12:38 |
| mup | Bug #1555597 opened: My previously managed network in 1.10 was migrated to 2.0 with DHCP disabled <MAAS:New> <https://launchpad.net/bugs/1555597> | 12:38 |
| imranh_ | going to assume an autopilot install of openstack shouldn't take 24hours+ | 13:05 |
| mup | Bug #1555597 changed: My previously managed network in 1.10 was migrated to 2.0 with DHCP disabled <MAAS:New> <https://launchpad.net/bugs/1555597> | 13:08 |
| imranh_ | found an error message in my install logs | 13:20 |
| imranh_ | "465 error fetching public address: "public no address"" | 13:20 |
| voidspace | roaksoax: you marked my bug as a duplicate | 13:58 |
| voidspace | roaksoax: it's not *obviously* a duplicate of the one you linked it to | 13:58 |
| voidspace | roaksoax: do you think when that bug is fixed I'll be able to commission nodes - or is there something else going on? | 13:59 |
| roaksoax | voidspace: you are running MAAS on the host system | 14:02 |
| roaksoax | voidspace: err | 14:03 |
| roaksoax | and KVM's on that host system | 14:03 |
| roaksoax | and trying to get MAAS to manage them right? | 14:03 |
| voidspace | roaksoax: no, I'm running MAAS in a KVM too | 14:03 |
| voidspace | roaksoax: maas controller and maas nodes on the same KVM defined network | 14:04 |
| voidspace | with maas running dhcp | 14:04 |
| roaksoax | voidspace: right, so I think it may still be related bug | 14:05 |
| voidspace | ok | 14:05 |
| roaksoax | voidspace: so does the rack have interfaces ? If so, are any of those interfaces the same as the IP fo the BMC ? | 14:05 |
| roaksoax | voidspace: i.e, the gateway maybe ? | 14:06 |
| roaksoax | or and actualy interface ? | 14:06 |
| voidspace | roaksoax: maas rack controller is running on a machine with a single nic - ip is 172.16.0.2, gateway is 172.16.0.1 | 14:06 |
| roaksoax | voidspace: the BMC of the VM's you are trying to manage, what's the IP ? | 14:07 |
| voidspace | roaksoax: BMC? | 14:08 |
| roaksoax | voidspace: how are you trying to power manage the VM's ? | 14:09 |
| voidspace | roaksoax: ah, I'm not - manually starting them | 14:23 |
| voidspace | roaksoax: if I was power managing them I'd put virsh connection strings into the power type | 14:23 |
| voidspace | so no bmc | 14:23 |
| roaksoax | voidspace: right, so virsh -> BMC in maas terms | 14:25 |
| roaksoax | voidspace: ok, if you can share with me a console log I could probably try to discover why it is happening | 14:25 |
| voidspace | roaksoax: ok, I've diverted to looking at another bug - I'll come back to you on this | 14:26 |
| voidspace | roaksoax: I really appreciate your help | 14:26 |
| imranh_ | well i'm giving up on using maas/landscape/autopilot | 14:58 |
| mup | Bug #1555673 opened: [2.0a1] Rack Controller interfaces UI appears greyed out. <MAAS:Confirmed> <https://launchpad.net/bugs/1555673> | 14:59 |
| voidspace | roaksoax: ok, what sort of console log do you want - I do most things through the ui | 15:03 |
| voidspace | roaksoax: I can get you any of the maas log files though | 15:03 |
| roaksoax | voidspace: the consolo log from the commissioning process.. | 15:03 |
| voidspace | roaksoax: ah | 15:04 |
| voidspace | roaksoax: ok | 15:04 |
| voidspace | roaksoax: the "Settings" tab says " | 15:04 |
| voidspace | One rack controller is not yet connected to the region. Visit the rack controllers page for more information." | 15:04 |
| voidspace | roaksoax: yet the rack controller page shows no error | 15:04 |
| voidspace | Interesting, on the settings page the Commissioning section is showing "No Usable Release" for default release used for commissioning | 15:05 |
| voidspace | same for deploy | 15:05 |
| voidspace | and now I can't enlist, time to reinstall again I think | 15:11 |
| mup | Bug #1555679 opened: [2.0a1] bridges with same mac as physical interfaces prevent rack interface discovery <MAAS:New> <https://launchpad.net/bugs/1555679> | 15:29 |
| mup | Bug #1555703 opened: [2.0a1] network provisioningserver code fails to parse ipv6 routes <MAAS:New> <https://launchpad.net/bugs/1555703> | 16:14 |
| mup | Bug #1555703 changed: [2.0a1] network provisioningserver code fails to parse ipv6 routes <MAAS:New> <https://launchpad.net/bugs/1555703> | 16:26 |
| mup | Bug #1555703 opened: [2.0a1] network provisioningserver code fails to parse ipv6 routes <MAAS:New> <https://launchpad.net/bugs/1555703> | 16:29 |
| mup | Bug #1555715 opened: [2.0a1] changing a subnet's space does not cause a refresh in networks/spaces tab in the UI <MAAS:New> <https://launchpad.net/bugs/1555715> | 16:41 |
| mag009_ | i just upgraded to 2.0 anyone have having issue with tftp not being able to bind to port 69 ? permission denied which is normal since it's running as maas user | 17:02 |
| mag009_ | ok i found out | 17:32 |
| mag009_ | you guys use... authbind but it seem the package isn't configuring the port... | 17:32 |
| mup | Bug #1555736 opened: [2.0a1] Need to release all DHCP leases at the end of commissioning <MAAS:Triaged> <https://launchpad.net/bugs/1555736> | 17:50 |
| mup | Bug #1555759 opened: [2.0a1] If no VLAN has DHCP enabled, MAAS should notify the user. <MAAS:Triaged> <https://launchpad.net/bugs/1555759> | 18:39 |
| stormmore | is there an easy way to reset the maas db? | 19:18 |
| stormmore | or is a better way to put it, is there a way to reinitialize the db? | 19:32 |
| dbainbri | Running into a situation with MAAS where on restart it looses the association between a node and its IP address and thus wipes it from the zone file. an if down/up of the interface on the node doesn't seem to get MAAS to realize the association. Anyway to get the association back and into the zone file? | 21:18 |
| roaksoax | dbainbri: is this DHCP ? | 22:00 |
| dbainbri | yes | 22:01 |
| dbainbri | roaksoax: yes | 22:01 |
| roaksoax | dbainbri: is this < 1.8 ? | 22:01 |
| dbainbri | from the UI: MAAS Version 1.9.1+bzr4543-0ubuntu1 (trusty1) | 22:02 |
| dbainbri | roaksoax: ^ | 22:02 |
| roaksoax | dbainbri: so you set the interface as DHCP in the web ui ? | 22:03 |
| dbainbri | roaksoax: yes | 22:03 |
| roaksoax | dbainbri: for a subnet where MAAS is providing DHCP for? | 22:04 |
| dbainbri | yes | 22:04 |
| roaksoax | dbainbri: interesting.. but that's probably why this happens since the interface is being set to dhcp, so it really is not static | 22:04 |
| roaksoax | dbainbri: can you please file a bug and we'll look into it | 22:04 |
| dbainbri | soaksoax: so a variable in the equation is i have a host, fixed-address entry in DHCP for this host. | 22:04 |
| dbainbri | soaksoax: i don't expect it to be static, but i am surprised that MAAS isn't picking up when a lease is renewed. it may be that with ISC DHCP a fixed-address is treated differently than a real lease. | 22:06 |
| roaksoax | dbainbri: hold on, so you are manually making a hostmap in dhcpd for the IP of that interface? | 22:08 |
| roaksoax | dbainbri: if that's the case then that'ds the bug | 22:08 |
| roaksoax | dbainbri: you can tell MAAS what IP address you want for the interface without having to manually modify that | 22:08 |
| mup | Bug #1555363 changed: "No storage information." commissioning PowerVM (Power 8) <MAAS:Invalid> <https://launchpad.net/bugs/1555363> | 22:09 |
| dbainbri | soaksoax: it is somewhat temporary (the fixed mapping). if i assign it in MAAS as a "fixed" address with MAAS assign it via DHCP? | 22:10 |
| roaksoax | dbainbri: dbainbri if it is sent to dhcp it will dhcp from the dynamic range | 22:29 |
| roaksoax | which is not ensure to give you dns mappeins | 22:29 |
| roaksoax | dbainbri: if you select an IP for the interface, it will give you the IP you want | 22:30 |
| dbainbri | and it will end up in DNS | 22:30 |
| roaksoax | dbainbri: yes | 22:30 |
| roaksoax | dbainbri: static ip assigments in MAAS (either Auto-assign, or Static, for the PXE interface, will end up in DNS) | 22:30 |
| roaksoax | dbainbri: 2.0 adds supports for PTR records for the rest of the IP's | 22:31 |
| roaksoax | but the DNS A record will always be given to the PXE interface | 22:31 |
| dbainbri | roaksoax: ok thanks. eventually i want all DHCP and don't care about assigning fixed-address, but for now i need more static addresses because of some other software. guess i will change to static IPs in MAAS | 22:31 |
| dbainbri | roaksoax: thx | 22:31 |
| mup | Bug #1553261 changed: [FFe] Standing FFe for MAAS 2.0 <maas (Ubuntu):Fix Released> <https://launchpad.net/bugs/1553261> | 22:54 |
| stormmore | Hey any chance someone could have a quick look at my vlan config https://bpaste.net/show/5b5c65b1d5b3 and make sure I don’t have any glaring mistakes? | 22:55 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!