[04:20] Bug #1545693 changed: Commissioning HTTP 401 with "Auto" address but okay with "DHCP" address

=== frankban|afk is now known as frankban [08:20] hello, im having throuble to make maas cluster. I have successfully installed and runned maas with dhcp and dns, and when i try to install another ubuntu machine and choice the option enter the maas ip, my machine shuted down imediately. Im using Ubuntu 14.05 LTS [08:21] How to make another machine to work as maas cluster? Im using maas version 1.7 [11:36] How to cleanup maas dhcpd ? [11:49] BlackDex what does clean up means? [12:06] KpuCko: Well the leases are empty/depleated [12:06] and i want a clean start [12:06] multiple juju deployments [12:07] failed etc... And now a clean start [12:30] hmmm juju deployments, you mean openstack? [12:38] Bug #1615618 opened: [2.1] 'SERVICE_STATE' object has no attribute 'getStatusInfo' [12:45] KpuCko: Yes, openstack in this case. I now stoped maas-dhcpd removed the leases file and started it again [12:45] that seems to work for now [12:46] i don't understand you completly but you can use sudo openstack-install -u [12:46] this will remove juju bootstrap [13:05] that doesn't release the maas-dhcpd leasese ofcourse [13:05] those leases are mainted longer and outside of juju [13:09] if you want to delete dhcp leases you can do this by manually editing the /var/lib/maas/dhcp/dhcpd.leases file [13:18] KpuCko: That is what i did by deleting that file :).. Thx [13:18] BlackDex sorry.. [13:19] KpuCko: No problem. I now know that that is the way to do it [14:57] Bug #1615013 opened: Autopilot: Nagios uses the wrong subnet IP to reach one host

[14:57] Bug #1615686 opened: dns zoneconfig error with /30 networks <4010> === frankban is now known as frankban|afk [16:57] Bug # changed: 1523104, 1524152, 1524482, 1524563, 1524883, 1525070, 1525264, 1525411, 1525445, 1526107, 1526123, 1526197, 1526532, 1526957, 1526971, 1546143, 1547874, 1547877, 1553297, 1553352, 1554494, 1557434, 1566503, 1567144, 1568102, 1569873, 1569984, 1570104, 1570995, 1576116, 1577013, [16:57] 1577954, 1580285, 1585400, 1585666, 1586499, 1587539, 1587548, 1587896, 1587936, 1587939, 1587998, 1588000, 1593789, 1594975, 1594991, 1595753, 1596046, 1597324, [16:57] 1597787, 1598028, 1598149, 1598461, 1598937, 1599841, 1600198, 1600720, 1602721, 1604128, 1604169, 1604461, 1604465, 1604962, 1605252, 1611342, 1611711, 1614865 [17:15] Bug #1615210 changed: [SRU] Please SRU MAAS 2.0 (final) into Xenial [17:15] Bug #1612293 changed: [1.9] eth0 tried to get a DHCP IP, no matter what

[17:45] Bug #1614864 changed: [2.1] Error on request (48) subnet.list: column maasserver_staticroute.created does not exist [19:24] Bug #1606948 changed: [trunk] Filter scrolling for according always shows despite only having 1 item [19:39] Bug #1606948 opened: [trunk] Filter scrolling for according always shows despite only having 1 item [19:45] Bug #1606948 changed: [trunk] Filter scrolling for according always shows despite only having 1 item [19:45] Bug #1615794 opened: unique_together issue/error between django and postgresql [20:00] Bug # changed: 1592954, 1599996, 1602486, 1603198 [20:18] Bug # changed: 1525260, 1550645, 1559316, 1570608, 1571006, 1577960 [20:27] Bug # opened: 1525260, 1550645, 1559316, 1570608, 1571006, 1577960 [20:30] Bug # changed: 1525260, 1550645, 1559316, 1570608, 1571006, 1577960, 1612676, 1612680, 1615013 [20:33] Bug #1612676 opened: [Card sorting] Move DNS to Networks or make it accessible from Networks [20:33] Bug #1612680 opened: [Card sorting] Move DHCP configuration on a higher level in Networks or make it accessible from the Networks main page [20:33] Bug #1615013 opened: Autopilot: Nagios uses the wrong subnet IP to reach one host

[20:35] would anyone know why this says success but it does not update the actual vid maas 19-root subnet update cidr:192.168.24.0/23 vid=10 i have been stuck with this for the last 2h [20:45] oz_, what command are you issuing? put it in a pastebin perhaps? [20:45] oz_, why did you want 2h to ask? :) [20:45] s/want/wait ugh [20:45] Bug #1612676 changed: [Card sorting] Move DNS to Networks or make it accessible from Networks [20:45] Bug #1612680 changed: [Card sorting] Move DHCP configuration on a higher level in Networks or make it accessible from the Networks main page [20:45] Bug #1615013 changed: Autopilot: Nagios uses the wrong subnet IP to reach one host

[20:48] @kiko here is the paste bin of the comand http://pastebin.com/SHf1c7Xi [20:49] hmmm. roaksoax, mpontillo: what's wrong with the above? [20:50] i have two vlans i would like to have them under the same fabric-2 for example and i need to assign subnets to those VLANS but i am struggling with the documentation [20:50] or lack of ;-) [20:50] oz_, is there a VID of 10 in that fabric? [20:51] oz_: kiko: the vid must be updated on the vlan, not the subnet [20:51] mpontillo, why do we return "success" in that case though? [20:52] kiko: heh, I guess the bug is that we updated every field you asked (none of which matched) [20:52] @kiko so at the moment there are twi vlan's one vlan 10 with vid10 and vlan 101 with vid 101 then i run the command above wanting to assign subnet to the VLAN [20:52] mpontillo, exactly -- this is the second time in 2 days I've run into this [20:52] mpontillo, would you file a bug specific to the general problem? [20:53] mpontillo, what oz_ wants to do is to say "serve this subnet on this vlan" [20:53] kiko, sure [20:53] mpontillo, how is he supposed to do that? [20:54] update the vlan to match the vlan id field where the subnet should live [20:55] @mpontillo can you paste an example command please? [20:56] oz_: yeah give me ~10 minutes to set up a test environment [20:57] mpontillo, I don't think even I understood that one -- how does the subnet know it should go to vid, say, 10? [20:57] updating the vlan to vid 10.. how does the subnet get related? [20:59] @kiko so in maas 2.0 i saw that you can do that in GUI and with some messing around it works but then i can't use autopilot and so i am back to 1.9 [21:00] kiko: you would first create a VLAN with vid=10 on that fabric, then move the subnet to the new vlan [21:00] oz_, indeed, autopilot implies juju and right now that implies maas 1.x [21:00] mpontillo, how do you do the part that comes after ", then"? [21:00] the first is easy [21:01] Bug # changed: 1015559, 1026211, 1032821, 1036165, 1037591, 1041165, 1044393, 1046830, 1049494, 1049951, 1052867, 1052869, 1052877, 1052880, 1053025, 1053143, 1054517, 1054521, 1059474, 1063721, 1063881, 1064225, 1231129, 1426089, 1498225, 1498262, 1499147, 1500678, 1592843, 1598275, 1612681 [21:01] I need to split brb [21:08] @mpontillo also in theory i get this working and everything deploys fine. What happens then when tomorrow i route another vlan to the cloud? Do i need keep tagging vlans first in maas then in openstack? [21:12] oz_: that is an interesting question, but assuming that these machines are deployed in MAAS and running for a long time, I don't think it will do what you want. MAAS will only configure VLAN interfaces on a deployed node at deployment time [21:12] oz_: it sounds like you want something to go and update the VLAN configuration post-deployment [21:15] yes i want to use autopilot because it works. I tried for 2 weeks to get conjure-up to deploy openstack in maas an i have failed. But i have 10 nodes at the moment. if this works i will buy support from canonical and then i am planing to add 5 nodes immediately but then i will need to add another 15 vlans... is that something that iw workable in maas/autopilot? [21:16] oz_, yep, it should definitely be workable [21:17] oz_: right, I'm sure it's possible to get working. adding 15 more VLANs may not be fully automated, depending on the approach. hard to say without digging deeper [21:24] @mpontillo ok thanks, if you can help with the commands on how to assign VLANS initially i can continue testing [21:24] oz_: yeah, sorry, I'm testing MAAS 2.1 now so am having a few hurdles [21:27] oz_: so, first I would do "maas 19-root fabrics read" to ensure you know where you want to put a new VLAN [21:28] oz_: then (let's assume it's on fabric-1) I would do "maas 19-root vlans create fabric-1 vid=10" [21:28] @mpontillo done that [21:28] oz_: the returned JSON structure from the create call will have an id field. in my case it says "id": 5034 [21:29] oz_: then when you update the VLAN, do it the same way you did before, except write vlan=5034 [21:32] oz_: alternatively, if you want to create a brand new VLAN instead of reassigning an existing one, you could do (for example): maas 19-root subnets create cidr=172.16.98.0/24 vlan=5034 [21:32] oz_: sorry, meant a brand new subnet, not a brand new VLAN (obviously) [21:32] maybe i will try that the update command was not too succesful [21:33] @ mpontillo [21:33] how do i delte exiswitn cidr? [21:34] oz_: did you create it manually? or was it created when a rack was registered, or a machine was commissioned? [21:35] i created it manually in webui [21:36] oz_: probably something like this would work: maas 19-root subnet delete 172.16.98.0/24 [21:36] oz_: you might need to use the subet id with that command. I can check in a minute [21:37] @mpontillo ("Cannot delete some instances of model 'Subnet' because they are referenced through a protected foreign key: 'NodeGroupInterface.subnet'", []) [21:38] oz_: ah. and what happens when you update it? [21:39] oz_: that is saying you can't delete it because there is a rack interface that is using it [21:39] i dont know how to get the update command right i have been trying for a while [21:41] @mpontillo: here is the pastebin of subnet and fabrics http://pastebin.com/8rRHgxja [21:45] oz_: I think you want something like: maas 19-root subnet update 192.168.24.0/23 vlan=5005 [21:46] thanks! [21:47] i think this might work [21:47] hope so ;-) [21:49] will test today and tomorrow :) [21:49] let us know! [22:03] Hi, maas-regiond status shows action (exited), in the maas.log, maas.rpc.cluster: [ERROR] Lost all connections to region controllers. Stopping services dhcpd. [22:04] maas.service_monitor_service: [ERROR] can't update service statuses, no RPC connection to region. [22:04] What's going wrong to cause this? [22:44] roaksoax: ^^^ [23:32] catbus1: I'm not 100% sure from the context, but I'd check that the URL to the MAAS server is correct. (sudo dpkg-reconfigure maas-rack-controller) [23:34] mpontillo: checked that. both rack and region-controllers. [23:35] catbus1: what version of MAAS is this? [23:35] mpontillo: do you happen to know when I run dpkg-reconfigure, will it restart all the associated services? [23:35] 2.0 GA [23:36] catbus1: good question - yes, restarts the appropriate services [23:37] mpontillo: http://paste.ubuntu.com/23079893/ [23:38] catbus1: that much looks okay. is there anything else in /var/log/maas/*.log? [23:41] mpontillo: http://paste.ubuntu.com/23079895/, http://paste.ubuntu.com/23079897/, http://paste.ubuntu.com/23079898/ [23:42] catbus1: ah, I bet you're running inside a container? [23:42] mpontillo: yes [23:42] catbus1: the container must have the appropriate privileges to mount the images [23:44] catbus1: I do this in my LXD profile to get around that: [23:44] https://paste.ubuntu.com/23080004/ [23:46] catbus1: from the logs, it looks like the rack controller is connecting; I wonder if it disconnects due to the container issue [23:47] mpontillo: I got that configured and were able to install and configured maas fine last friday [23:53] catbus1: then I guess the question is, what could cause the rack to disconnect from the region? if the rack and region are on the same machine, usually using localhost is safe for the MAAS URL [23:54] catbus1: in the past I have seen NAT rules do string things like this [23:54] *strange things [23:58] the rack is disconnected from the region?