[02:03] <sliver> kiko: that's not clear how
[02:31] <mpontillo> sliver: you can use the ipaddresses reserve API to create a static mapping, and/or create a device with a static IP in order to get a static mapping
[02:31] <mpontillo> sliver: actually the ipaddresses reserve API is deprecated now that I think of it, you want the link-subnet API and a device or machine generally
[02:32] <mpontillo> sliver: or you can use the dns-resources API.
[02:32] <mpontillo> (but now that I think of it, that may not create a static mapping, heh. it's past beer o'clock here...)
[02:32] <sliver> yea i hear that. chat more later
[02:33] <sliver> I think that gets us back to the other issue we have where we aren't on the bmc network so reliant on relay
[02:33] <sliver> workaround in place with static
[02:33] <sliver> ilo4's will flip from dhcp allocated to static and keep the dhcp ip which is badass
[02:43] <sliver> oops just saw your pm, can do it tomorrow if you like still
[05:39] <hipolito> good morning! how does maas handle prefix delegation on fabrics?
[11:01] <mup> Bug #1683735 opened: [2.2.0rc2, UI, Nodes] Sort the machine listing by (the column) disks doesn't work <ui> <ux-qa-2.2> <MAAS:New> <https://launchpad.net/bugs/1683735>
[11:19] <mup> Bug #1683735 changed: [2.2.0rc2, UI, Nodes] Sort the machine listing by (the column) disks doesn't work <ui> <ux-qa-2.2> <MAAS:New> <https://launchpad.net/bugs/1683735>
[11:22] <mup> Bug #1683735 opened: [2.2.0rc2, UI, Nodes] Sort the machine listing by (the column) disks doesn't work <ui> <ux-qa-2.2> <MAAS:New> <https://launchpad.net/bugs/1683735>
[11:22] <mup> Bug #1683741 opened: [2.2.0rc2, Accessibility] When I am adding a device, when I have added a second interface, the x to delete it doesn't receive focus <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683741>
[11:37] <mup> Bug #1683758 opened: [2.2.0rc2, Accessibility] As I am adding a machine and  I have focused on the power type dropdown with my keyboard, when I press Enter a new MAC address gets added <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683758>
[11:46] <mup> Bug #1683758 changed: [2.2.0rc2, Accessibility] As I am adding a machine and  I have focused on the power type dropdown with my keyboard, when I press Enter a new MAC address gets added <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683758>
[11:52] <mup> Bug #1683758 opened: [2.2.0rc2, Accessibility] As I am adding a machine and  I have focused on the power type dropdown with my keyboard, when I press Enter a new MAC address gets added <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683758>
[12:07] <mup> Bug #1683765 opened: [2.2.0rc2, UI, Controllers] # selected controllers doesn't have the updated link style <ui> <ux-qa-2.2> <MAAS:New> <https://launchpad.net/bugs/1683765>
[12:37] <mup> Bug #1683769 opened: [2.2.0rc2, UX Improvement] In the device details page, the take action dropdpwn button is not needed <ui> <MAAS:New> <https://launchpad.net/bugs/1683769>
[12:37] <mup> Bug #1683776 opened: [2.2.0rc2, Accessibility] In device details-Interfaces-Add interface when I have focused (with my keyboard) on the IP assignment  dropdown and I click Enter, the contextual menu of the previous row opens <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683776>
[12:37] <mup> Bug #1683786 opened: [2.2.0rc2, Accessibility] Some (interactive) UI components open with space and others with Enter and Space <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683786>
[13:10] <mup> Bug #1683794 opened: [2.2.0rc2, Accessibility] Devices-Edit device When I am focused on IP assignment and I press Enter my changes are cancelled and the card closes <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683794>
[14:19] <mup> Bug #1683810 opened: [2.2.0rc2, Accessibility] Device/Machine details - When (using the keyboard) I have opened the Take action dropdown and I am clicking on the down/right arrow the machine/device name goes to edit mode <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683810>
[14:19] <mup> Bug #1683811 opened: [2.2.0rc2, UI, Machine details] When I am editing an interface and I click on the contextual menu of the previous interface, I cannot see the edit action <ui> <ux-qa-2.2> <MAAS:New> <https://launchpad.net/bugs/1683811>
[14:28] <mup> Bug #1683816 opened: [2.2.0rc2, Accessibility] Device/Machine details - In the machine/device summary when (using the keyboard) I am editing and I have focused
[14:28] <mup> on any of the form fields, when I hit Enter the cancel button gets clicked <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683816>
[14:34] <mup> Bug #1683816 changed: [2.2.0rc2, Accessibility] Device/Machine details - In the machine/device summary when (using the keyboard) I am editing and I have
[14:34] <mup> focused on any of the form fields, when I hit Enter the cancel button gets clicked <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683816>
[14:49] <mup> Bug #1683816 opened: [2.2.0rc2, Accessibility] Device/Machine details - In the machine/device summary when (using the keyboard) I am editing and I have focused
[14:49] <mup> on any of the form fields, when I hit Enter the cancel button gets clicked <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683816>
[14:49] <mup> Bug #1683826 opened: [2.2.0rc2, Accessibility] Machine details-Interfaces. When I tab through the page using my keyboard, the table header Name|MAC doesn't receive focus <accessibility> <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1683826>
[14:49] <mup> Bug #1683834 opened: [2.2.0rc2, Accessibility] Machine details-Interfaces. When (using my keyboard) I click on Create bridge the keyboard focus doesn't go in the open card so that I can fill the bridge details. <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683834>
[14:52] <mup> Bug #1683826 changed: [2.2.0rc2, Accessibility] Machine details-Interfaces. When I tab through the page using my keyboard, the table header Name|MAC doesn't receive focus <accessibility> <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1683826>
[14:52] <mup> Bug #1683834 changed: [2.2.0rc2, Accessibility] Machine details-Interfaces. When (using my keyboard) I click on Create bridge the keyboard focus doesn't go in the open card so that I can fill the bridge details. <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683834>
[14:59] <mup> Bug #1683826 opened: [2.2.0rc2, Accessibility] Machine details-Interfaces. When I tab through the page using my keyboard, the table header Name|MAC doesn't receive focus <accessibility> <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1683826>
[14:59] <mup> Bug #1683834 opened: [2.2.0rc2, Accessibility] Machine details-Interfaces. When (using my keyboard) I click on Create bridge the keyboard focus doesn't go in the open card so that I can fill the bridge details. <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683834>
[15:11] <rquiros183> Good day!!
[15:11] <rquiros183> i have problem to conect node to mastermass server
[15:11] <rquiros183> if i boot in pxe protocol
[15:12] <rquiros183> the boot is fall
[15:20] <mup> Bug #1683844 opened: [2.2.0rc2, Accessibility] When (using my keyboard) I have clicked on commissioning and I want to select hardware tests,  there is no way to navigate and select the scripts with my keyboard  <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683844>
[15:41] <mup> Bug #1683849 opened: [2.2.0rc2, Accessibility] (Using my keyboard) If I am in a page with no interactive elements the focus jumps from the secondary navigation to the footer and I have no way to scroll down the page <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683849>
[16:11] <mup> Bug #1683855 opened: Pod refresh errors when node has a logical volume <MAAS:New> <MAAS RSD :New> <https://launchpad.net/bugs/1683855>
[16:11] <mup> Bug #1683856 opened: [2.2.0rc2, Accessibility] Images-Custom source. When I am focused in the URL input field, when I press Enter the Show/Hide Advanced options changes state <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683856>
[16:26] <mup> Bug #1683863 opened: [2.2.0rc2, Accessibility] When I want to edit a field I should be able to see clearly how to do that from the UI <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683863>
[16:35] <mup> Bug #1683863 changed: [2.2.0rc2, Accessibility] When I want to edit a field I should be able to see clearly how to do that from the UI <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683863>
[16:41] <mup> Bug #1683863 opened: [2.2.0rc2, Accessibility] When I want to edit a field I should be able to see clearly how to do that from the UI <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683863>
[16:44] <mup> Bug #1683864 opened: [2.2.0rc2, Accessibility] The forms are not accessible <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683864>
[16:46] <alanmac> Keep getting this error when we're trying to deploy ga kernel in MaaS 2.2rc2 - Node failed to be deployed, because of the following error: ['hwe_kernel(ga-16.04) is older than min_hwe_kernel(hwe-16.04).']
[16:47] <mup> Bug #1683864 changed: [2.2.0rc2, Accessibility] The forms are not accessible <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683864>
[16:52] <kiko> alanmac, are you consuming directly from our streams, or using a local mirror?
[16:53] <alanmac> directly from your streams
[16:54] <kiko> alanmac, any funny stuff, or a straight install and run? if the latter, could you find a bug with a reasonable reproducer and give me the number so our QA team can track it for you?
[16:54] <alanmac> we get this error when the HWE kernel has been previously set on a node, then we try to deploy with GA. We have to mark them as broken, edit the min kernel on the machine summary screen, mark as fixed, then deploy and we're good.
[16:54] <kiko> that's a bug then
[16:54] <kiko> and well-caught at that
[16:54] <kiko> mpontillo, ^^
[16:54] <kiko> alanmac, do you have a proxy between you and the world?
[16:54] <alanmac> cool, wanted to make sure, I'll get this logged on launchpad and kick you all the #
[16:55] <alanmac> no, we don't
[16:55] <kiko> thanks alanmac -- how many nodes in your deployment, out of curiosity?
[16:55] <mpontillo> ltrager: ^ you might be interested in this
[16:55] <kiko> mpontillo, I just pinged him, yeah
[16:55] <alanmac> right now we have 64
[16:56] <mup> Bug #1683864 opened: [2.2.0rc2, Accessibility] The forms are not accessible <accessibility> <ui> <MAAS:New> <https://launchpad.net/bugs/1683864>
[16:56] <alanmac> but we'll have over a 100 soon
[16:56] <kiko> alanmac, mixed arch or just x86?
[16:56] <alanmac> yep, just x86
[16:56] <kiko> alanmac, hmm, shouldn't really be broken then. thanks for the heads-up
[16:56]  * ltrager takes a look
[16:56] <kiko> (i.e. it's small and single-arch)
[16:57] <mpontillo> alanmac: would you mind filing a bug about this? https://bugs.launchpad.net/maas/+filebug
[16:57] <kiko> mpontillo: <alanmac> cool, wanted to make sure, I'll get this logged on launchpad and kick you all the #
[16:57] <kiko> beat you to it
[16:57] <alanmac> yes, filling it out now!
[16:57] <mpontillo> great, thanks.
[17:03] <ltrager> alanmac, kiko, mpontillo: So the ga-16.04 kernel is an older kernel then hwe-16.04
[17:03] <alanmac> kiko mpontillo https://bugs.launchpad.net/maas/+bug/1683874
[17:03] <alanmac> yep, it makes sense for sure, but shouldn't "deploy" override what the machine summary have set?
[17:04] <kiko> ltrager, sure it is -- but why do we fail :-)
[17:05] <ltrager> alanmac, kiko: The min_hwe_kernel is a requirement which an administrator can set. Deployments are constrained by the value. This way an admin can say "only hwe-16.04 works on this machine" and hwe-16.04+ are the only kernels users are allowed to deploy
[17:05] <ltrager> This avoids the admin from having to deal with "why isn't my machine deploying" from users
[17:06] <ltrager> I could look into adding a force option to override the constraint
[17:06] <mpontillo> alanmac: just curious why you want to use the older kernel?
[17:09] <alanmac> that's a good question, we were successful with a few nodes on ga, so that's what we're sticking with right now. Just trying to get these nodes online for right now.
[17:09] <alanmac> i'd like to deploy with hwe in production
[17:14] <mup> Bug #1683874 opened: Unable to deploy with different kernel <MAAS:New> <https://launchpad.net/bugs/1683874>
[19:08] <mup> Bug #1683909 opened: Subnet changes during deployment <MAAS:New> <https://launchpad.net/bugs/1683909>
[20:08] <mup> Bug #1683919 opened: installation fails with trusty and hwe-t kernel <curtin:New> <MAAS:New> <linux (Ubuntu):New> <https://launchpad.net/bugs/1683919>
[20:14] <mup> Bug #1683919 changed: installation fails with trusty and hwe-t kernel <curtin:New> <MAAS:New> <linux (Ubuntu):New> <https://launchpad.net/bugs/1683919>
[20:23] <mup> Bug #1683919 opened: installation fails with trusty and hwe-t kernel <curtin:New> <MAAS:New> <linux (Ubuntu):New> <https://launchpad.net/bugs/1683919>