[00:12] Hello, I wanted to see if anyone could verify that both Landscape (on premises install) and MAAS will both function on Ubuntu 18.04 LTS that's scheduled to be released tomorrow. Any help would be appreciated as I'd like to use 18.04 for a Landscape/MAAS deployment for an entire datacenter. === setuid_ is now known as setuid === jamespage_ is now known as jamespage === hazmat_ is now known as hazmat [02:41] silox: MAAS is in Ubunut Bionic [02:41] 2.4b2 === essembe is now known as sbeattie [05:59] Bug #1767032 opened: [2.4b2] An edit button is shown for non-admin users in the DNS page [05:59] Bug #1767033 opened: [2.4b2] DNS records link to machines that the users doesn't have permission to view [06:11] Bug #1767032 changed: [2.4b2, UI] An edit button is shown for non-admin users in the DNS page [06:11] Bug #1767033 changed: [2.4b2] DNS records link to machines that the users doesn't have permission to view [06:17] Bug # opened: 1767032, 1767033, 1767035, 1767038 [06:23] Bug #1767035 changed: [2.4b2, UI] Normal users are shown an edit button on the AZ page [06:23] Bug #1767038 changed: [2.4b2, UI] An edit button is shown for normal users on the subnet page [06:29] Bug #1767035 opened: [2.4b2, UI] Normal users are shown an edit button on the AZ page [06:29] Bug #1767038 opened: [2.4b2, UI] An edit button is shown for normal users on the subnet page [09:09] hi guys, we have an UCS environment. Inorder to control power from MaaS, we provide the API on the HTTPS but the problem is we have a selfsigned certificate and the MAAS is not making me add UCS power type. Is there a tweak that I can make? [13:05] srihas: https is not supported on UCS [13:23] roaksoax: URL for XML API what should I enter here? [13:24] to be very clear, if I enter abc-ucs.example.int in my web browser it redirects to HTTPS [13:25] srihas: http based on [13:28] roaksoax: I didn't get, sorry [13:57] Bug #1766665 changed: maas-region fails with an error 500 in an attempt to delete a subnet [13:59] srihas: you need to point maas to a HTTP endpoint, not a HTTPS endpoing or an enpoint that forwards [14:00] roaksoax: seems something I need to do on the UCS side [14:00] roaksoax: will look into it [14:01] I think its better to to have a checkbox like: dont verify SSL sort of [14:18] srihas: please file a bug/enhancement request [14:22] roaksoax: nice, will try to do it [15:24] Bug #1767137 opened: [2.3] Default install is now importing bionic by default instead of xenial. [15:24] Bug #1767140 opened: Dead Keys do not work inside Snap Packages in Bionic [15:36] Bug #1767140 changed: Dead Keys do not work inside Snap Packages in Bionic === frankban_ is now known as frankban|afk [19:58] Bug #1767183 opened: default commissioning OS has changed to bionic in 2.3.2

[20:01] Bug #1767184 opened: arm64 machines fail to commission with bionic: Device "enP2p1s0" does not exist.

[20:10] Bug #1767183 changed: default commissioning OS has changed to bionic in 2.3.2

[20:43] Bug #1767184 changed: arm64 machines fail to commission with bionic: Device "enP2p1s0" does not exist.

[21:01] Bug #1767184 opened: arm64 machines fail to commission with bionic: Device "enP2p1s0" does not exist.

[21:05] Bug #1767184 changed: arm64 machines fail to commission with bionic: Device "enP2p1s0" does not exist.

[21:54] I know this isnt the right channel, but kind of out of options. Is there a unicorn that I need to feed or leprechaun to befriend to actually be allowed to buy support from Canonical [21:54] specifically for MAAS [21:54] and specifically so I can have the tool to build customer OSs [21:54] now going on 2 weeks of phone calls and emails to Caonical [21:55] s/Caonical/Canonical