[08:38] <smallsam> hey folks, full disclosure, I work for CloudBolt.io and am currently integrating maas.io into our cloud management product. I've mostly been able to achieve what I need using the api, just once so far reverting to the websocket interface (FWIW that's an interesting endeavour outside of a browser). Anyhow today I've been trying to use the
[08:38] <smallsam> machines/{}/?op=deploy call to deploy bionic, but I can't reliably provision centos/centos70, ubuntu/focal, ubuntu/bionic using different combinations of osystem and distro_series to the api method. It seems the api most of the time silently uses the default osystem and release and haven't tracked out the right combination to get it working. Are
[08:38] <smallsam> there any good logs that I can enable to determine which params it is using/ignoring.
[08:38] <smallsam> For example I'm sure at one stage I was passing just distro_series = centos70 and no osystem at all, but now can't seem to reproduce that success. I just can't believe it's non-deterministic. Has anyone got any advice on how to move forward?
[09:30] <smallsam> So, stepping away from my PC for a while I managed to solve my problem. The intermittent behaviour was caused by by recycling a pool of machines and the lack of params meant the node's existing settings were used for the deploy. I was passing a json blob in the post, not form params.
[09:30] <smallsam> The deploy continued even though it was ignoring the entire json post request rather than failing which was confusing.
[09:30] <smallsam> For reference the reason I use the websocket connection is to call general.osinfo, for which there doesn't appear to be an API equivalent to enumerate all the images.
[09:39] <mup> Bug #1917594 opened: Machine summary missing OS release title <ui> <MAAS:New> <https://launchpad.net/bugs/1917594>
[12:18] <mup> Bug #1917372 changed: maas ui missing buttons after updating to 2.8.3 <MAAS:Fix Released by adam-collard> <maas-ui:Fix Released> <https://launchpad.net/bugs/1917372>
[12:21] <mup> Bug #1917372 opened: maas ui missing buttons after updating to 2.8.3 <MAAS:Fix Released by adam-collard> <maas-ui:Fix Released> <https://launchpad.net/bugs/1917372>
[12:24] <mup> Bug #1917372 changed: maas ui missing buttons after updating to 2.8.3 <MAAS:Fix Released by adam-collard> <maas-ui:Fix Released> <https://launchpad.net/bugs/1917372>
[12:24] <mup> Bug #1917377 changed: maas 2.9.2 proxmox machine violates unique constraint "maasserver_bmc_power_type_parameters_idx" <db> <index> <proxmox> <MAAS:New> <https://launchpad.net/bugs/1917377>
[12:27] <mup> Bug #1917377 opened: maas 2.9.2 proxmox machine violates unique constraint "maasserver_bmc_power_type_parameters_idx" <db> <index> <proxmox> <MAAS:New> <https://launchpad.net/bugs/1917377>
[12:30] <mup> Bug #1917377 changed: maas 2.9.2 proxmox machine violates unique constraint "maasserver_bmc_power_type_parameters_idx" <db> <index> <proxmox> <MAAS:New> <https://launchpad.net/bugs/1917377>
[12:33] <mup> Bug #1917377 opened: maas 2.9.2 proxmox machine violates unique constraint "maasserver_bmc_power_type_parameters_idx" <db> <index> <proxmox> <MAAS:New> <https://launchpad.net/bugs/1917377>
[12:39] <mup> Bug #1917377 changed: maas 2.9.2 proxmox machine violates unique constraint "maasserver_bmc_power_type_parameters_idx" <db> <index> <proxmox> <MAAS:New> <https://launchpad.net/bugs/1917377>
[12:42] <mup> Bug #1917377 opened: maas 2.9.2 proxmox machine violates unique constraint "maasserver_bmc_power_type_parameters_idx" <db> <index> <proxmox> <MAAS:New> <https://launchpad.net/bugs/1917377>
[12:48] <mup> Bug #1917377 changed: maas 2.9.2 proxmox machine violates unique constraint "maasserver_bmc_power_type_parameters_idx" <db> <index> <proxmox> <MAAS:New> <https://launchpad.net/bugs/1917377>
[15:54] <mup> Bug #1917640 opened: MAAS deploy via API fails after upgrade - apparently server crashes on apparmor error <MAAS:New> <https://launchpad.net/bugs/1917640>
[17:45] <mup> Bug #1914807 opened: rack can't contact region, deployments fails <seg> <sts> <MAAS:New> <maas (Ubuntu):Confirmed> <https://launchpad.net/bugs/1914807>
[17:45] <mup> Bug #1917652 opened: 30-maas-01-bmc-config failing on commissioning Cisco UCSC-C220-M4L <hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1917652>
[17:48] <mup> Bug #1914807 changed: rack can't contact region, deployments fails <seg> <sts> <MAAS:New> <maas (Ubuntu):Confirmed> <https://launchpad.net/bugs/1914807>
[17:48] <mup> Bug #1917652 changed: 30-maas-01-bmc-config failing on commissioning Cisco UCSC-C220-M4L <hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1917652>
[17:51] <mup> Bug #1914807 opened: rack can't contact region, deployments fails <seg> <sts> <MAAS:New> <maas (Ubuntu):Confirmed> <https://launchpad.net/bugs/1914807>
[17:51] <mup> Bug #1917652 opened: 30-maas-01-bmc-config failing on commissioning Cisco UCSC-C220-M4L <hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1917652>
[20:15] <mup> Bug #1917667 opened: Commissioning/testing scripts no longer show ETA or progress <ui> <MAAS:New> <maas-ui:New> <https://launchpad.net/bugs/1917667>
[20:15] <mup> Bug #1917669 opened: No way to view previous commissioning or testing script results <ui> <MAAS:New> <maas-ui:New> <https://launchpad.net/bugs/1917669>
[20:15] <mup> Bug #1917670 opened: Storage and interface tests not assoicated with a device <ui> <MAAS:New> <https://launchpad.net/bugs/1917670>
[20:18] <mup> Bug #1917667 changed: Commissioning/testing scripts no longer show ETA or progress <ui> <MAAS:New> <maas-ui:New> <https://launchpad.net/bugs/1917667>
[20:18] <mup> Bug #1917669 changed: No way to view previous commissioning or testing script results <ui> <MAAS:New> <maas-ui:New> <https://launchpad.net/bugs/1917669>
[20:18] <mup> Bug #1917670 changed: Storage and interface tests not assoicated with a device <ui> <MAAS:New> <https://launchpad.net/bugs/1917670>
[20:24] <mup> Bug #1917667 opened: Commissioning/testing scripts no longer show ETA or progress <ui> <MAAS:New> <maas-ui:New> <https://launchpad.net/bugs/1917667>
[20:24] <mup> Bug #1917669 opened: No way to view previous commissioning or testing script results <ui> <MAAS:New> <maas-ui:New> <https://launchpad.net/bugs/1917669>
[20:24] <mup> Bug #1917670 opened: Storage and interface tests not assoicated with a device <ui> <MAAS:New> <https://launchpad.net/bugs/1917670>
[20:28] <mup> Bug #1917671 opened: Commissioning/testing scripts not updated after starting commissioning or testing <ui> <MAAS:New> <https://launchpad.net/bugs/1917671>
[20:31] <mup> Bug #1917671 changed: Commissioning/testing scripts not updated after starting commissioning or testing <ui> <MAAS:New> <https://launchpad.net/bugs/1917671>
[20:37] <mup> Bug #1917671 opened: Commissioning/testing scripts not updated after starting commissioning or testing <ui> <MAAS:New> <https://launchpad.net/bugs/1917671>
[20:40] <mup> Bug #1917671 changed: Commissioning/testing scripts not updated after starting commissioning or testing <ui> <MAAS:New> <https://launchpad.net/bugs/1917671>
[20:43] <mup> Bug #1917671 opened: Commissioning/testing scripts not updated after starting commissioning or testing <ui> <MAAS:New> <https://launchpad.net/bugs/1917671>
[21:22] <mup> Bug #1917672 opened: When running 20.04 in ppc64el as KVM host I am not able to compose virutal machines <MAAS:New> <https://launchpad.net/bugs/1917672>
[21:25] <mup> Bug #1917672 changed: When running 20.04 in ppc64el as KVM host I am not able to compose virutal machines <MAAS:New> <https://launchpad.net/bugs/1917672>
[21:28] <mup> Bug #1917672 opened: When running 20.04 in ppc64el as KVM host I am not able to compose virutal machines <MAAS:New> <https://launchpad.net/bugs/1917672>