| === frankban|afk is now known as frankban | ||
| DesktopMan | question: I don't quite understand what configuring fabrics and subnets in maas do | 08:45 |
|---|---|---|
| DesktopMan | does it alter interfaces and routing tables? | 08:45 |
| mup | Bug #1690781 opened: Compose machine failure: Start tag expected, '<' not found, line 1, column 1 <MAAS:New> <https://launchpad.net/bugs/1690781> | 10:21 |
| mup | Bug #1690784 opened: An ip address from a reserved range is used for auto-assigning <MAAS:New> <https://launchpad.net/bugs/1690784> | 10:45 |
| cnf | DesktopMan: you configure networking for machines in maas | 11:12 |
| mup | Bug #1690810 opened: Failed to probe and enlist VMware nodes <maas (Ubuntu):New> <https://launchpad.net/bugs/1690810> | 12:57 |
| === dannf` is now known as dannf | ||
| mup | Bug #1690784 changed: An ip address from a reserved range is used for auto-assigning <MAAS:Invalid> <https://launchpad.net/bugs/1690784> | 13:24 |
| mup | Bug #1690810 changed: Failed to probe and enlist VMware nodes <maas (Ubuntu):New> <https://launchpad.net/bugs/1690810> | 13:27 |
| === gimmic_ is now known as gimmic | ||
| ThiagoCMC | Hey guys, what is this new MaaS' feature, called Pods? | 15:05 |
| mup | Bug #1649501 opened: No rack controllers can access the BMC of node <maas (Ubuntu):New> <https://launchpad.net/bugs/1649501> | 15:06 |
| ThiagoCMC | Can I deploy a bare metal server with MaaS, turn it into a KVM server by installing "apt install ubuntu-virt-server", then, use the Pods feature to manage its VMs from MaaS? | 15:07 |
| roaksoax | ThiagoCMC: yes | 15:09 |
| ThiagoCMC | Wow! | 15:09 |
| roaksoax | ThiagoCMC: the only caveat is that you need the vm's to PXE boot from maas itself | 15:09 |
| ThiagoCMC | That's awesome! | 15:09 |
| ThiagoCMC | Hmmm... | 15:09 |
| ThiagoCMC | Right, so, at the bare metal, I need to reconfigure the /etc/network/interfaces and add a Linux Bridge there? | 15:09 |
| ThiagoCMC | So the VMs can PXE boot on the same segment as its bare metal... | 15:10 |
| ThiagoCMC | Oh, wait... | 15:10 |
| roaksoax | ThiagoCMC: we added virsh as a pod for testing and development. So if you have a KVM/libvirt running out there, as long as the networking can pxe boot of maas, it will jsut work | 15:10 |
| roaksoax | ThiagoCMC: not necessarily, but at a minimum yes | 15:10 |
| roaksoax | ThiagoCMC: you could have, say connect the vm's on a different vlan where you have another rack controller running | 15:10 |
| roaksoax | ThiagoCMC: but yes, at the very minimum, your vm's need to be able to pxe boot off maas for this to work | 15:11 |
| ThiagoCMC | But if the VMs PXE boot, MaaS will "think" that it is just another bare metal server, isn't it? | 15:11 |
| roaksoax | ThiagoCMC: yes, but it will a vm' inside the pod | 15:11 |
| roaksoax | or a machine inside the pod | 15:11 |
| ThiagoCMC | Right, so, before PXE booting the VM, I need to first, install KVM/Libvirt and "Add pod" on MaaS, is that correct? | 15:12 |
| roaksoax | ThiagoCMC: honestly, I have not tested deploying a machine with maas, then adding it as a pod. but i dont see why would that not work | 15:12 |
| roaksoax | ThiagoCMC: that's correct. say you have a kvm/libvirt, where you configure a bridge in the same vlan as MAAS' pxe. You can add a pod in MAAS | 15:12 |
| roaksoax | ThiagoCMC: and you will be able to create VM's and such | 15:13 |
| ThiagoCMC | :-D | 15:13 |
| ThiagoCMC | Thank you! I'll try that now... | 15:13 |
| ThiagoCMC | roaksoax, what the "virsh address" syntax looks like? | 15:25 |
| ThiagoCMC | I mean... How it looks like (sorry about my English). | 15:25 |
| ThiagoCMC | I'm trying to "Add pod" using a syntax like this: "qemu+ssh://root@hail.cloud.example.com/system" but, the following error appear: "Failed talking to pod: The command was not found or was not executable: virsh" | 15:49 |
| ThiagoCMC | but virsh is there, user "ubuntu", not "root", it works... | 15:50 |
| pmatulis | ThiagoCMC, user 'ubuntu' works but not 'root'? | 15:51 |
| pmatulis | (the user needs to be in group 'libvirtd') | 15:52 |
| ThiagoCMC | both ubuntu and root works lolcally, but not via "add pod" | 15:52 |
| ThiagoCMC | Mayeb this: "qemu+ssh://ubuntu@hot-alpapa.maas/system" is not a correct syntax. | 15:53 |
| ThiagoCMC | From MaaS, I can "ssh ubuntu@hot-alpapa.maas" and run virsh. | 15:54 |
| ThiagoCMC | But "add pod" doesn't work... | 15:54 |
| ThiagoCMC | And there is no Pods documentation here: https://docs.ubuntu.com/maas/devel/en/ | 15:55 |
| pmatulis | ThiagoCMC, yeah, use 2.2 branch | 15:56 |
| ThiagoCMC | I'm on it! | 15:56 |
| ThiagoCMC | maas 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 | 15:57 |
| pmatulis | ThiagoCMC, i mean the 2.2 docs | 15:57 |
| mup | Bug #1690848 opened: [VLAN details] In the Subnets on this VLAN table the (Unassigned) space is a link that links to the device discovery <ui> <MAAS:New> <https://launchpad.net/bugs/1690848> | 15:57 |
| pmatulis | devel is behind 2.2 for the next little while | 15:57 |
| ThiagoCMC | Where is the "Add pod / virsh" at the 2.2 doc? | 15:57 |
| ThiagoCMC | I can olny find this: https://docs.ubuntu.com/maas/2.2/en/intel-rsd | 15:58 |
| ThiagoCMC | Pod but not via virsh. | 15:58 |
| pmatulis | right. docs need to be added for virsh Pods. i opened a doc bug a little while ago | 15:58 |
| pmatulis | ThiagoCMC, maybe you want to track it and add any notes you may have - https://github.com/CanonicalLtd/maas-docs/issues/430 | 15:59 |
| ThiagoCMC | Nice... I'll, soon as I figure it out... =P | 16:00 |
| mup | Bug #1690848 changed: [VLAN details] In the Subnets on this VLAN table the (Unassigned) space is a link that links to the device discovery <ui> <MAAS:New> <https://launchpad.net/bugs/1690848> | 16:03 |
| mup | Bug #1690848 opened: [VLAN details] In the Subnets on this VLAN table the (Unassigned) space is a link that links to the device discovery <ui> <MAAS:New> <https://launchpad.net/bugs/1690848> | 16:09 |
| === frankban is now known as frankban|afk | ||
| mup | Bug #1690878 opened: Unreliable PXE-booting of Quanta S910-X31E <hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1690878> | 17:54 |
| mup | Bug #1690878 changed: Unreliable PXE-booting of Quanta S910-X31E <hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1690878> | 17:57 |
| mup | Bug #1690878 opened: Unreliable PXE-booting of Quanta S910-X31E <hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1690878> | 18:03 |
| mup | Bug #1690882 opened: Send hostname of Pod to driver to allow better log messages <MAAS:Triaged> <https://launchpad.net/bugs/1690882> | 18:03 |
| mup | Bug #1690883 opened: Drivers cannot post notifications <MAAS:Triaged> <https://launchpad.net/bugs/1690883> | 18:03 |
| mup | Bug #1690882 changed: Send hostname of Pod to driver to allow better log messages <MAAS:Triaged> <https://launchpad.net/bugs/1690882> | 18:06 |
| mup | Bug #1690883 changed: Drivers cannot post notifications <MAAS:Triaged> <https://launchpad.net/bugs/1690883> | 18:06 |
| mup | Bug #1690882 opened: Send hostname of Pod to driver to allow better log messages <MAAS:Triaged> <https://launchpad.net/bugs/1690882> | 18:15 |
| mup | Bug #1690883 opened: Drivers cannot post notifications <MAAS:Triaged> <https://launchpad.net/bugs/1690883> | 18:15 |
| ThiagoCMC | pmatulis, commented there on maas-docs issue 430, not working yet. | 18:17 |
| pmatulis | ThiagoCMC, alright. i'll try to get to this soon | 18:19 |
| ThiagoCMC | Thank you! | 18:20 |
| mup | Bug #1690884 opened: [2.2] apparmor_parser: enable to replace "/usr/sbin/dhcpd" [spurious error during dist-upgrade in container?] <MAAS:Incomplete> <https://launchpad.net/bugs/1690884> | 18:27 |
| mup | Bug #1690884 changed: [MAAS 2.2] apparmor_parser: enable to replace "/usr/sbin/dhcpd" [spurious error during dist-upgrade in container?] <AppArmor:New> <MAAS:Won't Fix> <https://launchpad.net/bugs/1690884> | 18:57 |
| mup | Bug #1690884 opened: [MAAS 2.2] apparmor_parser: enable to replace "/usr/sbin/dhcpd" [spurious error during dist-upgrade in container?] <AppArmor:New> <MAAS:Won't Fix> <https://launchpad.net/bugs/1690884> | 19:03 |
| mup | Bug #1690884 changed: [MAAS 2.2] apparmor_parser: enable to replace "/usr/sbin/dhcpd" [spurious error during dist-upgrade in container?] <AppArmor:New> <MAAS:Won't Fix> <https://launchpad.net/bugs/1690884> | 19:06 |
| atm_it | clear | 19:20 |
| atm_it | Hello, i have an issue with maas. I cannot ssh to some nodes deployed with maas | 19:25 |
| roaksoax | atm_it: Hi there. for the machines to be 'deployed', they must have obtained keys from MAAS allowing you to SSH into them | 19:36 |
| roaksoax | atm_it: that said, are your machines in 'deployed' state ? | 19:37 |
| atm_it | yes, they are in deployed state and i've uploaded the keys to maas | 19:42 |
| atm_it | i noticed i can ssh to juju and autopilot but not the openstack nodes | 19:43 |
| atm_it | This was the error message i got from Landscape when trying to deploy openstack "juju ended with exit code 1 (out='', err='Adding contents of "/var/lib/landscape/juju-homes/3/ssh/juju_id_rsa.pub" to authorized-keys Creating Juju controller "3" on landscape-maas Loading image metadata Looking for packaged Juju agent version 2.1.2 for amd64 Starting new instance for initial controller Launching controller instance(s) on landscape-maas... | 19:44 |
| roaksoax | atm_it: could be that it caused the keys not to be imported | 19:45 |
| roaksoax | atm_it: ssh ubuntu@ wont allow you to ssh in ? | 19:45 |
| atm_it | it doesnt allow me to ssh in | 19:45 |
| roaksoax | strange | 19:45 |
| roaksoax | atm_it: check /var/log/maas/rsyslog/machine-name/date/messages and see if there show any error before importing ? | 19:46 |
| atm_it | okay | 19:46 |
| atm_it | this is the error i get when i try to ssh | 19:46 |
| atm_it | ubuntu@autopilot:~$ ssh ubuntu@node1 Permission denied (publickey). | 19:46 |
| roaksoax | atm_it: my guessis that something is failing preventing cloud-init from injecting the keys | 19:52 |
| roaksoax | can you pastebin the requested log ? | 19:52 |
| atm_it | okay, will do that | 19:54 |
| atm_it | here's the log | 20:18 |
| atm_it | https://pastebin.com/B3Hq5dtK | 20:18 |
| roaksoax | atm_it: in that log it doesn't seem as if the machine contacted maas and run metadata after install | 20:20 |
| atm_it | let me send the log of another deployed node which i cant ssh into | 20:24 |
| roaksoax | atm_it: so, what I think the issue is that cloud-init is failing before it actually imports the ssh keys for maas | 20:27 |
| atm_it | is there a way to determine if cloud-init completed successfully? | 20:29 |
| atm_it | i'll redeploy the affected nodes and see if it solves the issue | 20:48 |
| atm_it | also, can you show me what to look for in the logs, for a successful deployment? | 20:49 |
| atm_it | thanks | 20:49 |
| mup | Bug #1690919 opened: Lots of "maasserver.websockets.base.HandlerDoesNotExistError" in regiond.log <MAAS:New> <https://launchpad.net/bugs/1690919> | 21:25 |
| ThiagoCMC | Guys, MaaS is creating a RAID1 on top of /dev/sda1 and /dev/sdb! Why? | 21:30 |
| ThiagoCMC | Why not sda1 + sdb1 ? | 21:30 |
| ThiagoCMC | MaaS did: "md0 : active raid1 sda1[0] sdb[1]" =/ | 21:30 |
| ThiagoCMC | It is syncing and I'll ignore this for now... | 21:31 |
| mup | Bug #1690919 changed: Lots of "maasserver.websockets.base.HandlerDoesNotExistError" in regiond.log <MAAS:New> <https://launchpad.net/bugs/1690919> | 21:34 |
| mup | Bug #1690919 opened: Lots of "maasserver.websockets.base.HandlerDoesNotExistError" in regiond.log <MAAS:New> <https://launchpad.net/bugs/1690919> | 21:37 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!