[08:11] <mup> Bug #1706459 changed: All auto-allocated VMs go to the first pod <cdo-qa> <pod> <MAAS:Won't Fix> <https://launchpad.net/bugs/1706459>
[10:52] <BlackDex> Hello.
[11:01] <BlackDex> I'm having an issue with MAAS
[11:01] <BlackDex> i have a maas node which has a tagged interface for the PXE network
[11:02] <BlackDex> but the nodes are all untagged on that vlan
[11:02] <BlackDex> i'm not able to configure the nodes to have an untagged network in the PXE network, since the MAAS node doesn't show it as an untagged network
[11:45] <roaksoax_> BlackDex: what version of MAAS are you using ?
[11:45] <BlackDex> 2.2
[11:45] <BlackDex> 2.2.1 to be exact
[11:46] <roaksoax_> BlackDex: so your fabric-untagged does not hold the subnet, or the other way around ?
[11:49] <BlackDex> on the maas node it doesn't indeed
[11:50] <BlackDex> the maas node has it as a tagged interface
[11:50] <BlackDex> while the nodes have them untagged
[11:57] <roaksoax_> BlackDex: ok, maybe i'm not following, but what you are saying is mAAS is providing dhcp on a tagged interface (e.g eth0.1234)
[11:58] <BlackDex> roaksoax_: that is correct
[11:58] <BlackDex> and the nodes are connected via 1234 vlan untagged
[11:59] <roaksoax_> BlackDex: right, so IIRC< that's is now a supported scenario (it wasn't before)
[11:59] <roaksoax_> BlackDex: hwat is the issue you are experiencing
[11:59] <BlackDex> Well
[11:59] <BlackDex> The issue is
[11:59] <BlackDex> That, if i want to configure a node
[12:00] <BlackDex> so, create a bond for example
[12:00] <BlackDex> and have that bond connected as an untagged interface, i cant select that
[12:01] <BlackDex> i need to select a vlan, which makes it tagged.
[12:01] <BlackDex> if i do not configure het network my self, so no bonding what ever. it seems to work
[12:02] <BlackDex> but creating a bond on a node, which is fysically connected to vlan 1234 UNTAGGED, i can't configure that within the node config, because MAAS only allows me to have that configured as a TAGGED interface
[12:08] <roaksoax_> BlackDex: right, so in the model, is the subnet in question under the untagged vlan or under the vlan X ?
[12:08] <BlackDex> what do you mean with model?
[12:08] <roaksoax_> BlackDex: under the Subnets tab
[12:12] <BlackDex> no, that subnet is under a tagged network
[12:12] <BlackDex> if i try to change that i'm not able to allow dhcp on it so that PXE will work
[12:12] <roaksoax_> BlackDex: i'll try to reproduce but AFAIK, we should support the escenario now
[12:13] <roaksoax_> (we didn't use to support that, we should support that now though)
[12:13] <BlackDex> well, i have an other network on that untagged
[12:13] <BlackDex> so maybe that causes the problem
[12:13] <BlackDex> on the maas node that is
[12:17] <BlackDex> i currently have it fixed by switching the tagged/untagged on the maas node. So that the PXE network is untagged, but not really the best solution in my opinion
[12:17] <roaksoax_> BlackDex: yeah, I dont have something to reproduce right now, ut I do know one in the team has reproduced it
[12:17] <roaksoax_> i just need to double check with him
[12:17] <BlackDex> oke cool :)
[13:29] <tai271828_> hi, I failed to deploy node in another subnet with external DHCP. is it possible for MAAS to deploy node in another vlan with an external dhcp? my maas is 2.1.x.
[13:31] <pmatulis> tai271828_, does the node show up with a status of 'New'? that is, does 'enlistment' work?
[13:31] <tai271828_> more details: my maas controller is in vlan A with subnet A and an external DHCP A, deployment works fine. I try to deploy a node in vlan B with subnet B and an external DHCP B (for IP in subnet B) and my controller seems lost the ip of the node (enlist and commission works)
[13:31] <tai271828_> pmatulis: enlistment works, the status could be "Ready"
[13:33] <tai271828_> pmatulis: I could get info from the node (looks like the info from the cloud-init of the node) by watching the log of MaaS server, log: rsyslog/node/messages
[13:33] <pmatulis> tai271828_, 'Ready' implies the node has also 'commissioned'. did you tell MAAS to 'commission' that node?
[13:33] <tai271828_> pmatulis: yes, I tell MaaS to commission that node, and then it is from "New" to "Ready". and then I began to deploy it
[13:35] <pmatulis> tai271828_, in that case, then, yes, you should be able, in principle, to 'deploy' with an external DHCP
[13:37] <tai271828_> pmatulis: even the external DHCP is in another subnet differing from where the MaaS controller is in? : (
[13:39] <pmatulis> yep
[13:41] <tai271828_> pmatulis: ok. then my vlan of the subnet does not show "there is an external DHCP". Something may be related to it.
[13:41] <tai271828_> pmatulis: thanks for your comments
[13:43] <pmatulis> tai271828_, you will need to set the node's IP assignment mode to 'DHCP' and have a 'reserved IP range' covering the external DHCP range to make sure MAAS never uses such IPs (not necessary if both ranges can never conflict)
[13:44] <tai271828_> pmatulis: yeah, actually I did in this way.
[13:46] <tai271828_> pmatulis: at the begining of the deployment process, it looks good. I can see the dhcp server is requested and offer expected IPs. and in the mean time, MaaS controller "lost" the configuration of the IP of the node. It became "unconfigured" from "10.101.47.52(DHCP)"  (10.101.47.52 is the ip of subnet B)
[13:51] <tai271828_> I guess my networks of two subnets may block something if two subnets with their own external DHCP is a working case...
[15:48] <mup> Bug #1706696 opened: maas auto-allocates machines via pods even when zone is included in constraints <cdo-qa> <MAAS:New> <https://launchpad.net/bugs/1706696>
[15:48] <mup> Bug #1706700 opened: [UI, Tables] When only one row action is available, expose it in the UI instead of having a contextual menu <ui> <MAAS:Triaged by karlwaghorn-moyce> <https://launchpad.net/bugs/1706700>
[17:33] <mup> Bug #1706723 opened: Failed talking to pod: int() argument must be a string, a bytes-like object or a number, not 'NoneType' <MAAS:New> <https://launchpad.net/bugs/1706723>
[20:18] <mup> Bug #1706763 opened: [2.2] Add ability to add tags to a pod that can be used on allocation constraints <pod> <MAAS:Triaged> <https://launchpad.net/bugs/1706763>
[20:27] <mup> Bug #1706763 changed: [2.2] Add ability to add tags to a pod that can be used on allocation constraints <pod> <MAAS:Triaged> <https://launchpad.net/bugs/1706763>
[20:33] <mup> Bug #1706763 opened: [2.2] Add ability to add tags to a pod that can be used on allocation constraints <pod> <MAAS:Triaged> <https://launchpad.net/bugs/1706763>
[23:54] <mup> Bug #1706811 opened: [2.2,2.3] Avoidable power errors occur when there is a mismatch among racks <MAAS:New> <https://launchpad.net/bugs/1706811>