[02:22] <jiffe> so if I want to still use my router's dhcp server for the desktops on my network I will have to segment my network and put maas machines on a different network from the desktops?
[09:17] <mup> Bug #1633822 opened: Device discovery ignores reverse DNS <MAAS:New> <https://launchpad.net/bugs/1633822>
[09:35] <mup> Bug #1633822 changed: Device discovery ignores reverse DNS <MAAS:New> <https://launchpad.net/bugs/1633822>
[09:41] <mup> Bug #1633822 opened: Device discovery ignores reverse DNS <MAAS:New> <https://launchpad.net/bugs/1633822>
[21:31] <smgoller> hey all, any ideas on troubleshooting remote virsh management? I've followed the instructions on the maas website for setting up ssh keys for a user and such, and virsh -c <my host> list --all works fine. however maas still says there's a problem logging in. any ideas?
[21:57] <pmatulis> smgoller, in what way does maas report a problem logging in?
[21:57] <smgoller> pmatulis: Failed to login to virsh console.
[21:57] <smgoller> that is via the gui
[21:58] <smgoller> no other interesting information seems to be in the logs that I can find
[22:20] <pmatulis> smgoller, so you became the 'maas' user and this works: virsh -c qemu+ssh://<user>@<kvm host>/system list --all ?
[22:20] <pmatulis> smgoller, but the web UI has a problem?
[22:21] <smgoller> yup
[22:22] <smgoller> pmatulis, that is exactly correct
[22:22] <smgoller> let me try something else.
[22:22] <pmatulis> smgoller, so the power check for a node must also not be working. i would 'tail -f' /var/log/auth.log on the kvm host and try a power check from the UI. see that pops up there
[22:22] <smgoller> ok
[22:22] <pmatulis> s/that/what
[22:24] <mup> Bug #1633247 changed: Used fallback datasource. PXE boot fail <MAAS:Invalid by charlienz> <https://launchpad.net/bugs/1633247>
[22:24] <smgoller> hm. it doesn't actually try to connect. I'm going to delete the node and re-add it.
[22:25] <pmatulis> smgoller, maybe you didn't configure the BMC correctly
[22:28] <smgoller> weird. So I copied the URL from the one not working, deleted the machine, then used the 'add chassis' with the virsh power driver and information, found it just fine

[22:28] <smgoller> chicken and egg problem maybe? Originally I had booted the VM to let maas discover it, then set the power type afterwards
[22:33] <mup> Bug #1633247 opened: Used fallback datasource. PXE boot fail <MAAS:Invalid by charlienz> <https://launchpad.net/bugs/1633247>
[22:36] <mup> Bug #1633247 changed: Used fallback datasource. PXE boot fail <MAAS:Invalid by charlienz> <https://launchpad.net/bugs/1633247>