[06:55] <mup> Bug #1691663 opened: Juju bootstrap maas centos7 yum repo not found <maas (Ubuntu):New> <https://launchpad.net/bugs/1691663>
[13:32] <mup> Bug #1691755 opened: [2.2, UI] When deleting VLAN interface, a confirmation message appears to delete physical interface <MAAS:New for ricgard> <https://launchpad.net/bugs/1691755>
[13:59] <mup> Bug #1691765 opened: [2.x] Node commissioning page should include the cloud-init logs and cloud-init output (especially for failed commissioning) <MAAS:New> <https://launchpad.net/bugs/1691765>
[14:38] <mup> Bug #1686794 changed: [2.2, UI] Cancel button broken on add user page and add ssl key page. <ui> <MAAS:Confirmed> <https://launchpad.net/bugs/1686794>
[14:38] <mup> Bug #1691768 opened: [2.2.0rc2, UI, Settings] When adding a user Cancel doesn't work and I am stuck on the add user page <ui> <MAAS:New> <https://launchpad.net/bugs/1691768>
[14:48] <roxana_> hello
[14:48] <roxana_> somebody ????
[14:49] <pmatulis> roxana_, hi, how are you?
[14:52] <kiko> manybody
[14:53] <mup> Bug #1691765 changed: [2.x] Node commissioning page should include the cloud-init logs and cloud-init output (especially for failed commissioning) <MAAS:New> <https://launchpad.net/bugs/1691765>
[14:54] <fengxia41103> Hi
[14:54] <fengxia41103> I'm trying to create a centos node maanaged by Juju
[14:54] <fengxia41103> using MAAS cloud for the provider
[14:55] <fengxia41103> I have create a MAAS server, managing two NICs, one is connected to the outside world, the other is serving DHCP to MAAS nodes on 192.168.8.x.
[14:55] <fengxia41103> I'm hitting an error nearly identical to this bug
[14:55] <fengxia41103> https://bugs.launchpad.net/maas/+bug/1688644
[14:56] <fengxia41103> MAAS server has UFW enabled firewall rules that allows ping and other ports
[14:56] <fengxia41103> but pinging from provisioned node will give Host Unreachable
[14:57] <fengxia41103> what did I miss?
[14:59] <mup> Bug #1691765 opened: [2.x] Node commissioning page should include the cloud-init logs and cloud-init output (especially for failed commissioning) <MAAS:New> <https://launchpad.net/bugs/1691765>
[15:08] <mup> Bug #1691765 changed: [2.x] Node commissioning page should include the cloud-init logs and cloud-init output (especially for failed commissioning) <MAAS:New> <https://launchpad.net/bugs/1691765>
[15:08] <mup> Bug #1691778 opened: [UX Improvement, Settings] When device discovery is disabled the active mapping field maintains its value and it is not clear that it is also disabled <ui> <MAAS:New> <https://launchpad.net/bugs/1691778>
[15:13] <fengxia41103> anyone can help me take a look at bug 1688644?
[15:20] <mup> Bug #1691778 changed: [UX Improvement, Settings] When device discovery is disabled the active mapping field maintains its value and it is not clear that it is also disabled <ui> <MAAS:New> <https://launchpad.net/bugs/1691778>
[15:20] <fengxia41103> Looks like MAAS set interface gateway to 192.168.8.254 by default, but my machine is 8.1. Manually change the gateway allowed ping to work now.
[15:23] <mup> Bug #1691778 opened: [UX Improvement, Settings] When device discovery is disabled the active mapping field maintains its value and it is not clear that it is also disabled <ui> <MAAS:New> <https://launchpad.net/bugs/1691778>
[15:25] <xygnal> roaksoax:  which file do I need to modify to add actions during or just-after comission?
[15:29] <xygnal> roaksoax: i would assume /etc/maas/preseeds/comissioning but I am not certain what synatx is safe in there.
[15:31] <roaksoax> xygnal: you can add "commissioning scripts"
[15:31] <roaksoax> xygnal: no need to modify preseeds
[15:32] <xygnal> roaksoax are there docs on this? I was trouble having finding it
[15:32] <roaksoax> xygnal: give me sec, otp
[15:37] <xygnal> roaksoax thanks.  I intend to grab disk information and set the boot device for the node.   Does any of the data collected during comission (such as disk info) stay locally on the system? Would love to just grab the disk info I need out of any local files it wrote, saving me some commmands
[15:50] <roaksoax> xygnal: ok, so commissioning scripts allow you tyo run any script you want to either, garther data, configure your underlying hardware, and allows you to do so before/after any of the scripts maas provides
[15:50] <roaksoax> xygnal: maas, currently, grabs the boot disk information and processes the data, and selects a boot disk, usual;ly, the first disk
[15:51] <xygnal> roaksoax we have a specific disk that needs to be chosen for install, and it is not the first disk.
[15:51] <xygnal> roaksoax I was hoping to grab the disk out of the comission's probe data and then set it's serial for boot device
[15:51] <xygnal> roaksoax the idea being, its set automatically.  Clients do not have to figure it out themselves.
[15:52] <roaksoax> xygnal: right. So, you could probably write your commissioning script (which can actually be anything you want), and have the commissioning script set the right boot disk
[15:54] <roaksoax> xygnal: your script could install the cli, run commands to set the boot disk to the one you want
[15:54] <roaksoax> xygnal: that said, you add new commissioning scripts in Settings page
[15:54] <xygnal> thats one way, i was thinking I would have to make API calls
[15:55] <roaksoax> xygnal: and the naming of the script determines the order on which it is run
[15:55] <xygnal> roaksoax I found someones githhub examples for using the CLI, so I understand how to do it now. ty.
[15:56] <xygnal> roaksoax can I just apt install them or would I need to make PPA additions?
[15:56] <roaksoax> xygnal: you can basically run what you need to run for the commissioning script
[15:56] <kiko> xygnal, if you want the MAAS client, make sure it's the same version you deployed into MAAS
[15:57] <roaksoax> xygnal: but if you wnat to add PPA's, you could also use the package repository feature
[15:57] <xygnal> kiko hm that is a concern, potential break point I dont want to conflict with if possible.   Can this be done using the API instead?
[15:57] <roaksoax> that allows you to add different repositories for your environment
[15:57] <xygnal> roaksoax ty
[15:57]  * roaksoax pto
[15:58] <kiko> xygnal, you can use the API, sure, and generally that's the saner approach. have you looked at the MAAS python library we've started?
[15:59] <xygnal> I have not, though I am aware of it.
[16:26] <mup> Bug #1691755 changed: [2.2, UI] When deleting VLAN interface, a confirmation message appears to delete physical interface <MAAS:Invalid> <https://launchpad.net/bugs/1691755>