[01:26] Bug #1841136 changed: [UI] "Save changes" button disabled when configuring "Manual" power type [01:26] Bug #1844437 changed: [2.6, UI] Setting manual power type doesn't allow saving [01:29] Bug #1841136 opened: [UI] "Save changes" button disabled when configuring "Manual" power type [01:29] Bug #1844437 opened: [2.6, UI] Setting manual power type doesn't allow saving [01:32] Bug #1841136 changed: [UI] "Save changes" button disabled when configuring "Manual" power type [01:32] Bug #1844437 changed: [2.6, UI] Setting manual power type doesn't allow saving [07:35] Bug #1820967 changed: MAAS failing to commission HP ProLiant DL385 G7 (AMD Opteron 6172) [07:35] Bug #1764322 opened: [UI] allow users to set owner data for a node [07:44] Bug #1795903 changed: [2.5b2, backend] could not fork new process for connection: Cannot allocate memory [07:47] Bug #1795903 opened: [2.5b2, backend] could not fork new process for connection: Cannot allocate memory [07:53] Bug #1795903 changed: [2.5b2, backend] could not fork new process for connection: Cannot allocate memory [07:59] Bug #1795903 opened: [2.5b2, backend] could not fork new process for connection: Cannot allocate memory [08:05] Bug #1795903 changed: [2.5b2, backend] could not fork new process for connection: Cannot allocate memory [08:17] Bug #1759946 changed: [2.3+, UI] Changing a subnet's fabric/vlan doesn't automatically update the interface model [08:17] Bug #1796006 changed: [model, enhacement] VM's inside a MAAS deployed KVM host (pod) should be modeled as a node with a parent [08:20] Bug #1759946 opened: [2.3+, UI] Changing a subnet's fabric/vlan doesn't automatically update the interface model [08:20] Bug #1796006 opened: [model, enhacement] VM's inside a MAAS deployed KVM host (pod) should be modeled as a node with a parent [08:23] Bug # changed: 1675981, 1685457, 1702567, 1727419, 1759946, 1796006 [08:26] Bug #1628067 changed: [2.1, FUJ] Please update FUJ text to match latest copy doc chages [08:27] Bug #1675495 changed: [2.x] Release of a new LTS should not break MAAS commissioning [08:30] Bug # opened: 1628067, 1675495, 1675981, 1685457, 1702567, 1727419 [08:42] Bug # changed: 1628067, 1675495, 1675981, 1685457, 1702567, 1727419 [08:45] Bug # opened: 1628067, 1675495, 1675981, 1685457, 1702567, 1727419 === exsdev0 is now known as exsdev [08:48] Bug # changed: 1628067, 1675495, 1675981, 1685457, 1702567, 1727419 [08:54] Bug #1584926 changed: Provide API to get node statistics, including node count by status [09:57] Bug #1798471 changed: [2.5, ESXi] Always enable SSH on ESXi deployments or provide an option to do so [10:21] Bug #1839811 changed: MAAS release node API calls, option to avoid transitioning to "Ready" [10:24] Bug #1838247 opened: apt remove maas-region-controller causes broken DB state [11:39] Bug #1810796 changed: Unexpected APC power control configuration behavior [11:42] Bug #1810796 opened: Unexpected APC power control configuration behavior [11:45] Bug #1810796 changed: Unexpected APC power control configuration behavior [11:48] Bug # changed: 1733945, 1747458, 1810955, 1826566, 1832908 [11:51] Bug # opened: 1733945, 1747458, 1810955, 1826566, 1832908 [12:03] Bug # changed: 1733945, 1747458, 1810955, 1826566, 1832908 [12:06] Bug # opened: 1733945, 1747458, 1810955, 1826566, 1832908 [12:09] Bug # changed: 1460816, 1517180, 1631129, 1733945, 1743595, 1747458, 1753486, 1810955, 1810980, 1812898, 1826566, 1826813, 1826942, 1832908, 1833046 [12:18] Bug # changed: 1754484, 1815930, 1827324, 1832957, 1833432 [12:21] Bug # changed: 1699855, 1761262, 1766334, 1828898 [12:24] Bug #1702754 changed: No way to add a node as admin user without starting commissioning [12:24] Bug #1713118 changed: [2.x] Provide curtin version as part of MAAS 'version' api [12:24] Bug #1827015 changed: MAAS wrongly reports cannot reach PowerEdge R630 BMC during machine create and fails to commission node later on [12:27] Bug #1839170 changed: Add support for IPMI system event logs [12:30] Bug #1470604 changed: [enhancement] MAAS doesn't automatically discover SOL console settings [12:30] Bug #1584949 changed: [feature] Provide Ubuntu desktop images for MAAS [12:30] Bug #1820307 changed: http error 409 instead of 503 [12:33] Bug # opened: 1470604, 1584949, 1820307, 1839170 [12:45] Bug # changed: 1470604, 1584949, 1820307, 1839170 [12:48] Bug # opened: 1470604, 1584949, 1820307, 1839170 [12:51] Bug # changed: 1470604, 1584949, 1770982, 1773422, 1820307, 1839170 [12:51] Bug #1844793 opened: Add WS API for user password change [12:54] Bug #1844795 opened: Add WS API for register_url, register_secret [13:00] Bug #1844796 opened: Remove CSRF protection from CSRF endpoint [13:03] Bug #1786114 changed: [feature] nvme namespace CRUD and discovery support [13:12] Bug #1835423 changed: No power status data for KVM [13:15] Bug #1835423 opened: No power status data for KVM [13:18] Bug #1835423 changed: No power status data for KVM [13:21] Bug #1788862 changed: [feature] add support for enabling discard on a bcache device [13:21] Bug #1832034 changed: MaaS complains that xenial is the default commissioning image when it isn't [13:24] Bug #1788862 opened: [feature] add support for enabling discard on a bcache device [13:24] Bug #1832034 opened: MaaS complains that xenial is the default commissioning image when it isn't [13:24] Bug #1835423 opened: No power status data for KVM [13:30] Bug # changed: 1788822, 1788862, 1793310, 1832034, 1832737, 1835423 [13:32] I presume I can (manually) swap netplan.io for ifupdown on my MAAS nodes if I need to? [13:32] Running 18.04 [13:32] I know I can d that with a normal 18.04 install, but maybe some extra config is required if its a MAAS box? [13:38] I have not been able to get juju bootstrap to finish successfully when using a netplan bridge so I'm going to try with ifupdown instead [13:45] Hi Huys, I'm not familiar with API yet and I try to log in with Postman. From what I understand API key in maas is divided this way : '', '', ' [13:45] But in postman when I want to create my auth token is asks me for "Consumer key - Consumer secret - Accesstoken - Token Secret" [13:45] I think I've tried all possibilities and no one is working [13:56] It's all good, was of course a bad settings issue 😛 [14:01] Ludw, Sometimes you need to come rant on IRC or send an email to your workmates before the answer reveals itself [14:01] Happens ALL THE TIME with me :) [14:04] hehe yes exactly [14:04] I'm still working on creating the token [14:14] actually the API key into MAAS dashboard is already a token ? Or it is 2 different things and I have to use this key the first time to create a token that I will use later for every request ? [14:15] The only thing I can do so far with the first key is to get API version [14:15] If I want go print my commission script I get a : User is not allowed access to this API. [14:27] I found this which solved my problem : https://github.com/CanonicalLtd/maas-docs/issues/647 [14:47] I've had several attempts now and it seems it is not possible to use ifupdown on a MAAS node running 18.04 [14:48] I presume I'll have to use 16.04 if I want to use ifupdown [14:50] why don't you want to use netplan ? [14:57] I've not been able to create a bridge that works with juju bootstrap