[04:21] Bug #1727090 changed: maas should let you configure a node's interface different from how maas' interfaces are configured [04:21] Bug #1727387 changed: [2.3beta3, UI] Network discovery - Virtual scrolling with expanded table row jumps back to expanded row <2.3qa> [04:21] Bug #1730977 changed: [2.3rc2, UI] When removing a Volume group and RAIDs the menu item says remove disk which might be confusing <2.3qa> === frankban|afk is now known as frankban === frankban is now known as frankban|afk [19:50] roaksoax: Hi, is it still true that "The 'Facebook's Wedge' OpenBMC power driver is considered experimental at this time." for MAAS 2.3? https://docs.ubuntu.com/maas/2.3/en/nodes-power-types [19:59] Does MaaS have an event bus like Ironic? https://docs.openstack.org/ironic/pike/admin/notifications.html [20:01] catbus: sorta yeah, we dont actiavely main it [20:01] ok. [20:01] thanks. [20:01] mbeierl: maas doesn't do push notification, but it does have an 'events' endpoint where all messages of a machine are set [20:01] roaksoax: where can I see info on that? [20:02] roaksoax: nvm: https://docs.ubuntu.com/maas/2.1/en/api [20:02] got it, thanks!! [21:20] any way to troubleshoot @ debug why maas cant connect to virsh ? [22:39] Hi all, I'm having an issue during commissioning. MaaS powers down the Dell server but then fails to power them on again. [22:41] I have checked that attached media is auto attached and ipmi over lan is enabled. [22:46] Bug #1746610 opened: ReferenceError: $scope is not defined when viewing "Power" tab of pod [23:44] ejat: you could use `sudo` switch to the `maas` user and do something like `virsh -c qemu+ssh://$HOST/system` to see if it works [23:44] ejat: might need to give `maas` a shell first though