[00:36] Bug #1639090 opened: [2.2] figure out how to model IPv6 autoconf addresses properly [04:19] Bug #1596452 changed: [2.0b8] Node with IPv6-only second public VLAN fails deployment [04:19] Bug #1619368 changed: maas upgrade failed from 14.04+1.9 to 16.04+2.0 === frankban|afk is now known as frankban [09:37] Bug #1639182 opened: [2.1] log format differs [10:49] Bug #1639202 opened: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter [12:20] Bug #1639219 opened: Adding interfaces should be possible when machine is deployed (and in rescue mode) [12:26] Bug #1639219 changed: Adding interfaces should be possible when machine is deployed (and in rescue mode) [12:29] Bug #1639219 opened: Adding interfaces should be possible when machine is deployed (and in rescue mode) [13:41] My nodes are fail to deploy in MAAS. Our Maas setup a Regional Controller and a cluster controller. The Cluster Controller is in a remote datacenter. This setup did work. But after rebuilding the cluster controller it failing only on the deployment step [13:44] Braven, what version of maas are you using? [13:45] 1.7, Before you say upgrade, I can not because of the hardware I am using. [13:48] Braven: confused on why you cannot because of hardware, but do you have a console log for the machine that is failing to deploy [13:48] Dell only support 14.04 on the hardware I have. [13:48] How do I get the console log? [13:49] Connect to the machine using ILO to watch the machine deploy [13:49] Assuming those machines are IPMI based [13:49] I have been watching it though the IDRAC [13:50] That would work as well, where in the deployment does it fail, can you copy and paste the output [13:50] one sec [13:51] also you can run MAAS 1.9 on 14.04 [13:51] sudo add-apt-repository ppa:maas/stable [13:51] sudo apt-get update [13:51] sudo apt-get upgrade [13:52] 1.9 is the recommened release on 14.04 [13:53] one more thing.. The deployement works in local datacenter with REginal Controller [13:56] Braven: the deploying machines in the remote datacenter need to be able to communicate to the region in the other datacenter [13:57] I can see command being issue to the Cluster Controller from the Region Controller in syslog [13:57] Well that is good, means that the cluster and region can talk [13:57] But the machines being deployed must be able to hit the metadata endpoint of the region controller [13:57] This all worked before [13:57] Do they have a route to the region in the other datacenter [13:58] we rebuilt the cluster controller [13:58] Check your "/etc/maas/clusterd.conf" [13:58] on what server? [13:58] On the cluster in the remote datacenter [13:59] Check that the IP address used for maas_url is the same IP address that the deploying machines can talk to the region with [13:59] on cluster controller or Regional controller [13:59] one sec [13:59] cluster controller [14:11] I am still here. I am still updating the MAAS servers [14:12] Braven: that is fine just ping me by name so I get notified [14:14] Bug #1639247 opened: typo in web UI when adding new subnet [14:44] Bug #1533719 opened: Adding a device with a MAC address that's belongs to another node, fails without providing any feedback [14:44] Bug #1639258 opened: [arm64/xgene-uboot] MAAS tries to fech non-existing boot-initrd and boot-kernel files [14:53] maas_url: http:///MAAS [14:53] ~ [14:53] maas_url: http:///MAAS [14:53] ~ [14:54] maas_url: http:///MAAS [14:54] ~ [15:00] hello [15:17] Util.py fetching metdata from url [15:18] Failed to query node's BMC — Power state could not be queried: <- is filling up the logs [15:34] so the issue of busy BMC is only effecting one site [15:41] Bug #1639277 opened: Assigning subnet to Interface fails on first attempt [15:42] Braven: where you able to get the logs from a deploying machine [15:42] Braven: also next time do "blake_r: msg" and it will alert me [15:42] blake_r: like this [15:42] yep [15:44] blake_r: I did upgrade to 1.9. In 1.9 should the web gui had changed? Because mine did not [15:45] Braven: yes it should have changed [15:45] Braven: "apt-cache policy maas" [15:46] blake_r: Installed: 1.9.4+bzr4592-0ubuntu1~trusty1 [15:47] Braven: the frontend is totally different in 1.9 so you should see a new version [15:48] Braven: "ps auxf | grep maas" [15:49] blake_r: maas 1085 1.8 0.0 664956 43260 ? Ssl 10:04 0:48 /usr/bin/python /usr/bin/twistd --nodaemon --uid=maas --gid=maas --pidfile=/run/maas-cluster.pid --logfile=/dev/null maas-pserv --config-file=/etc/maas/pserv.yaml [15:51] blake_r: http://paste.ubuntu.com/23426070/ [15:52] Braven: that seems wrong [15:53] Braven: try restarting the system to see, seems like a stray process is still around [15:54] blake_r: http://paste.ubuntu.com/23426076/ [15:54] blake_r: restarting the system [16:00] blake_r: http://paste.ubuntu.com/23426097/ [16:06] Braven: did you update the region controller as well? [16:07] Braven: I only see the cluster running [16:07] blake_r: I have not restarted the cluster [16:07] Braven: that process is only the cluster [16:08] Braven: the region provides the UI [16:08] blake_r: restarting it now. [16:08] Braven: did you update the region? [16:08] blake_r: yes [16:09] blake_r: Region controller is also the cluster controller in my local office [16:13] blake_r: I just released I got this when I went to upgrade the Regional http://paste.ubuntu.com/23426154/ [16:14] Braven: that would cause an issue [16:14] Braven: try [16:14] sudo apt install maas [16:14] err [16:14] sudo apt-get install maas [16:15] blake_r: it say it will install though package.. Will this delete the server that are already in teh system [16:16] Braven: no it will just upgrade to the new software [16:17] blake_r: Should I do this on Cluster controller [16:17] Braven: well you only need the cluster [16:17] so [16:17] sudo apt-get install maas-cluster-controller [16:20] The Cluster Controller is upgraded. I am now getting the new GUI [16:24] blake_r: on the subnet tab I am getting this "failed to detect a valid IP address from u'10.10.10.10.55'" I know that is a bad IP who would get into change it [16:37] blake_r: maas hpadmin networks read I found the bad entry [16:44] Bug #1639288 opened: [2.1] IPv6 autoconf addresses should not show up on the interface [17:02] how do you delete a subnet from commandline in MAAS. MAAS's gui is not erroring out [17:06] Braven, 1.9 right? [17:06] yes [17:07] Hi, it is possible to change the ip off all the hosts of maas to ipv6? [17:07] Braven, have you logged in to the cli and created a profile? [17:07] brendand: yes [17:07] should be maas profile subnet {id} delete [17:08] i don't have an instance of 1.9 up to check [17:12] Brendand: I figured it out. I was try to modify it with maas network update not maas subnet [17:13] Braven, yeah: http://maas.ubuntu.com/docs1.9/api.html#network [17:13] "This endpoint is deprecated. Use the new ‘subnet’ endpoint instead." [17:19] Thanks everyone.. I getting closer to fix everything === frankban is now known as frankban|afk [19:11] Bug #1639332 opened: Expire the DHCP lease after commissioning or make the default-lease-time configurable === zz_CyberJacob is now known as CyberJacob [22:48] Bug #1639332 changed: Expire the DHCP lease after commissioning or make the default-lease-time configurable