[04:38] <mup> Bug #1644229 changed: MAAS 2.1.1 - Curtin - Failed to deploy CentOS7 <curtin:Incomplete> <MAAS:Expired> <https://launchpad.net/bugs/1644229>
[08:53] <junaidali> Hi everyone, I'm trying to enlist and commission a virtual machine but it is failing with the error '{"power_parameters": ["Power ID: This field is required."], "power_type": ["Select a valid choice. virsh is not one of the available choices."]}'
[08:56] <junaidali> here is the regiond log http://paste.ubuntu.com/24169761/
[08:57] <junaidali> any idea what might be the issue here, I'm facing this issue randomly in a pipeline where configuration of MAAS is automated.
[11:04] <roaksoax> junaidali: how are you trying to add it ?
[11:50] <myra> Why can't I find the boot-images command  on the MaaS cli ?
[11:50] <myra> am I missing something ?
[11:51] <brendand> myra, have you been emailing maas-devel about this?
[11:52] <junaidali> roaksoax: I'm using this command
[11:52] <junaidali> maas "${MAASCLI}" machines create autodetect_nodegroup='yes' hostname="${JUJU_POWER_ID}" tags='bootstrap' power_type='virsh' mac_addresses="${JUJU_MAC}" power_parameters_power_address='qemu+ssh://'${HOST_USER}'@'${HOST_IP}'/system' architecture='amd64/generic' power_parameters_power_id="${JUJU_POWER_ID}"
[11:54] <brendand> junaidali, maybe we need the proper packages installed to use the virsh driver
[11:54] <brendand> e.g. libvirt-bin, virsh
[11:56] <junaidali> brendand: restarting the regiond fixed the issue for me.
[11:56] <junaidali> but I've seen the issue hitting multiple times
[11:59] <junaidali> it seems like there is a sync issue between regiond and rackd. Is there any way (a CLI command etc) that we can check if both are synced properly or not?
[11:59] <roaksoax> junaidali: it is because the rack controller is not connected
[12:00] <roaksoax> junaidali: and it cannot validate
[12:01] <junaidali> roaksoax: is there a way to check if it is connected? In MAAS UI under controller, the status was green
[12:02] <junaidali> but the logs were showing connection error.
[12:03] <roaksoax> junaidali: did you check the detailed cntroller page ?
[12:03] <roaksoax> and there is, check the rack controller endpoint
[12:03] <roaksoax> iirc
[12:06] <junaidali> roaksoax: cant find iirc under services in controller page http://imgur.com/a/tZDXZ
[12:08] <junaidali> I've installed MAAS on a VM with 8GB RAM and 4 vcpus, do you think the issue might be due to the specs?
[12:10] <junaidali> One specific thing about my environment is, I'm changing MAAS IP to the IP on eth1 interface
[12:11] <junaidali> sudo maas-region local_config_set --maas-url http://${MAAS_IP}:5240/MAAS
[12:11] <junaidali> and then updating rackd
[12:12] <junaidali> sudo service maas-regiond restart; sudo sed -i "s/localhost/${MAAS_IP}/g" /etc/maas/rackd.conf; sudo service maas-rackd restart
[12:24] <mup> Bug #1672353 opened: [2.2b3] Cannot see IP address of machine while in Hardware Testing <MAAS:New> <https://launchpad.net/bugs/1672353>
[12:24] <mup> Bug #1672354 opened: [2.2b3] Cannot see IP address of machine while in Hardware Testing <hardware-testing> <MAAS:Triaged> <https://launchpad.net/bugs/1672354>
[12:33] <mup> Bug #1672353 changed: [2.2b3] Cannot see IP address of machine while in Hardware Testing <MAAS:New> <https://launchpad.net/bugs/1672353>
[12:33] <mup> Bug #1672354 changed: [2.2b3] Cannot see IP address of machine while in Hardware Testing <hardware-testing> <MAAS:Triaged> <https://launchpad.net/bugs/1672354>
[12:45] <mup> Bug #1672353 opened: [2.2b3] Cannot see IP address of machine while in Hardware Testing <MAAS:New> <https://launchpad.net/bugs/1672353>
[12:45] <mup> Bug #1672354 opened: [2.2b3] Cannot see IP address of machine while in Hardware Testing <hardware-testing> <MAAS:Triaged> <https://launchpad.net/bugs/1672354>
[12:45] <mup> Bug #1672363 opened: [2.2b3] 'deploy' API endpoint doesn't automatically allocate a machine <rsd> <MAAS:Triaged> <https://launchpad.net/bugs/1672363>
[13:15] <mup> Bug #1672370 opened: [2.2b3] Hardware testing doesn't actively sends output to MAAS <hardware-testing> <MAAS:Triaged> <https://launchpad.net/bugs/1672370>
[13:20] <roaksoax> junaidali: or maas-rack config --region-url <url> && sudo maas-rackd restart
[13:50] <junaidali> thanks roaksoax I will change that.
[15:06] <mup> Bug #1672414 opened: Custom storage on Centos <MAAS:Triaged> <https://launchpad.net/bugs/1672414>
[17:04] <stormmore> kiko, did you see my updates to the Bug #1669548?
[17:25] <_flx> hi. I have a MaaS 1.9.4 setup on ubuntu 14.04, unmanaged cluster. The default nameserver on deployed instances is the maas ip. Is there any way to tell maas to use the DNS provided by the router?
[17:28] <_flx> https://bugs.launchpad.net/maas/+bug/1581155
[17:28] <_flx> i see
[18:07] <roaksoax> /wi/win 5
[18:24] <stormmore> _flx, you can set MaaS' upstream dns
[18:25] <stormmore> _flx, that way it will act as a caching nameserver as well as a resolver
[18:27] <stormmore> kiko, you around?
[18:35] <_flx> stormmore, do I need to commission/deploy again?
[18:36] <stormmore> _flx, shouldn't need to since it is just changing what MaaS will do with DNS requests, not the nodes themselves
[18:38] <_flx> ok. testing...
[18:47] <mup> Bug #1667141 changed: [FFe] Standing FFe for MAAS 2.2 <maas (Ubuntu):Fix Released> <https://launchpad.net/bugs/1667141>
[18:47] <_flx> stormmore, doesn't work. can't resolve hostname
[18:48] <_flx> the default nameserver on the node is the maas server ip
[18:48] <_flx> and i can't resolve the hostname
[18:49] <_flx> the documentation of that feature says "Only used when MAAS is running its own DNS server."
[20:13] <mup> Bug #1671320 opened: MaaS should set /etc/environment with appropriate proxy settings for rescue mode <MAAS:New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1671320>
[20:15] <roaksoax> _flx: /win 6
[20:15] <roaksoax> err
[21:12] <stormmore> hmmm I alway use MaaS as it's own DNS server so that it can update it with the hosts
[21:13] <stormmore> anyone familiar with how tag definitions worth? what would it look like to search the hostname for a substring?
[21:44] <pmatulis> stormmore, re tags, i'm curious whether you read the docs and found them lacking
[21:51] <roaksoax> stormmore: tags definition to search the hostname for a substring? tag definitions only work for lshw output that maas collects and to autotag commmon machines
[21:51] <roaksoax> stormmore: https://docs.ubuntu.com/maas/2.1/en/manage-cli-tags
[21:51] <roaksoax> for example there, you can tag all machines that have a CUDA GPU for the example
[21:52] <roaksoax> tags dont apply to machine hostnames
[21:54] <stormmore> pmatulis, yeah I always read the docs before asking questions ;)
[21:55] <stormmore> I was really looking for a way to auto tag nodes that get the hostname worker* as worker, decided to manually tag them instead for now