[11:27] <arun__> HELP
[11:27] <arun__> I am trying to setup maas
[11:28] <arun__> and adding one machine node
[11:29] <arun__> but unable to commision the same
[16:57] <JJ__> Trying to troubleshoot a problem with my maas setup relating to the public interface
[16:58] <JJ__> My private interface is managed by MAAS along with DHCP and it seems to work fine, I can run conjure-up and it tries to bootstrap a juju node
[16:59] <JJ__> however it gets stuck at running machine configuration scripts
[16:59] <JJ__> I can ping google.com from the maas server on the public interface, I can't ping google.com from the juju node after ssh in
[17:03] <roaksoax> Calvin`: not supported today unfortuantely
[17:03] <roaksoax> Calvin`: err sorry
[17:04] <roaksoax> arun__: that sound slike the machine cannot access the maas metadata. Make sure /etc/maas/rackd.conf points to itself in an IP that the machine can communicate to
[17:06] <roaksoax> JJ__: so either you setup NAT'ing
[17:06] <roaksoax> JJ__: or you tell juju to use MAAS as a proxy
[17:07] <JJ__> hmmm... currently have 2 subnets in maas
[17:07] <JJ__> one is private with dhcp managed by maas
[17:08] <JJ__> other is public with dns and dhcp provided by switch downstream
[17:09] <mup> Bug #1750884 opened: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution <cloud-init:New> <MAAS:Triaged> <nplan (Ubuntu):New> <systemd (Ubuntu):New> <https://launchpad.net/bugs/1750884>
[17:12] <roaksoax> JJ__: right, but MAAS can install things from the archive because they use the apt proxy, aka MAAS
[17:12] <roaksoax> JJ__: the system itself cannot reach the internet because it doens't have a global proxy configured
[17:13] <roaksoax> JJ__: which is why either you enable NAT'ing, or tell the services you deploy with juju to use the proxy
[17:13] <JJ__> for maas dashboard under settings I have proxy set for MAAS built-in
[17:14] <JJ__> so you can enable NAT'ing through MAAS?
[17:14] <roaksoax> JJ__: yes, that's APT proxy
[17:14] <roaksoax> JJ__: that's not  a "system" proxy
[17:14] <roaksoax> JJ__: https://askubuntu.com/questions/852154/juju-2-0-proxy-for-bootstrap/852931
[17:15] <JJ__> Ok, not that familiar with conjure-up open stack kvm install.  How do you tell the services deployed with juju to use the maas proxy?
[17:15] <roaksoax> JJ__: so you can do two things. IF you want machines to have access to the internet regardless of wether juju deployed them
[17:16] <roaksoax> JJ__: you need to enable NAT
[17:16] <roaksoax> how would you do that? If MAAS is your gateway, you need iptables rules to forward traffic
[17:16] <roaksoax> from your public net, to hte internal net
[17:16] <roaksoax> if you dont want to do that, you can tell juju to use a proxy. And that proxy would be MAAS
[17:20] <JJ__> Like this? https://askubuntu.com/questions/590449/maas-network-and-nat
[17:26] <roaksoax> JJ__: yeah similar
[17:26] <roaksoax> JJ__: personally, I always use NAT
[17:26] <roaksoax> but i jsut run a test environment
[18:23] <JJ__> roaksoax__: in reading both links about proxying and NAT, it seems they apply to a situation where the maas server is the only server with 2 nic's
[18:24] <JJ__> roaksoax__: in my situation all nodes have 2 nic's with one for the private subnet managed by MAAS and the other for public network.
[18:38] <catbus> roaksoax: Hi, wondering if you got my question yesterday and whether I missed the reply because I was on and off the chat.
[19:06] <catbus> roaksoax: I think I found the answer, https://github.com/maas/maas/blob/master/src/provisioningserver/drivers/pod/virsh.py only attach one interface. Even though I have two defined for the VM node (cloud-init is configured accordingly) but only one interface is created along with the VM creation.
[19:30] <JJ__> anyone know why maas wouldn't pass the gateway or allow the gateway to be passed from an external DHCP server?
[19:31] <roaksoax> catbus: we dont use the templates from kvm/libvirt, we use our own
[19:32] <JJ__> after commissioning I have tried auto assign, DHCP & Static for the public interface and none seem to allow the gateway to be passed to the node in its cloud config file
[19:33] <JJ__> maas correctly passes the gateway for the private managed interface
[19:37] <JJ__> if a gateway is passed it appears that NAT works, without a gateway - no NAT
[19:47] <catbus> roaksoax: I don't follow. What do you mean we don't use the templates from kvm/libvirt?
[19:47] <roaksoax> catbus: we dont create vm's based on what you have manually defined in libvirt
[19:47] <roaksoax> e.g. if you have multiple networks in libvirt
[19:47] <roaksoax> we dont use that
[19:48] <catbus> roaksoax: yeah, I have to manually attach the second nic to the VM to use the second bridge I create on the kvm host.
[19:49] <catbus> thanks for the confirmation.
[20:17] <JJ__> roaksoax__: do you know if there is an issue with maas passing gateways ending in .254 instead of .1
[20:41] <roaksoax> JJ__: no known issues, shouldn't really be an issue if maas is the gateway or is not the gateway
[20:41] <roaksoax> JJ__: when you configure DHCP you should tell it where the gateway is
[20:43] <mup> Bug #1711203 opened: Deployments fail when Secure Boot enabled <blocks-hwcert-server> <id-5a28802797729aedf99dcd37> <curtin:Invalid> <dellserver:New> <MAAS:Triaged
[20:43] <mup> by andreserl> <MAAS 2.3:Triaged by andreserl> <maas-images:Fix Released by ltrager> <grub2 (Ubuntu):In Progress by cyphermox> <https://launchpad.net/bugs/1711203>
[21:13] <JJ__> roaksoax__:  I have the gateway configured in maas and in an external dhcp for the public internet interface, it is unmanaged and although I can get maas to assign an ip address from a  range, the gateway doesn't pass through.
[21:13] <JJ__> I tested the external dhcp and it does pass the gateway
[21:18] <JJ__> roaksoax__: is it possible to deploy a node with 2 fabric's, one on a private subnet with dhcp managed by maas and one on a public subnet with dhcp provided externally
[21:24] <JJ__> roaksoax__: according to the maas docs unless I am reading it wrong, it appears for the public subnet where dhcp is not managed by maas it doesn't pass the gateway to the node during deployment.
[21:46] <roaksoax> JJ__: yes it is possible
[21:46] <roaksoax> JJ__: you just have to set the interface to DHCP
[22:01] <JJ__> roaksoax__: when I set the public interface to dhcp then maas doesn't pass the gateway in the cloud config file and I haven't found a persistent way to modify the interface on the node to add it in.