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