[08:13] <mup> Bug #1697541 changed: [2.2] Deployment fails if a cache set was created out of a partition of a device <curtin:Incomplete> <MAAS:Invalid> <https://launchpad.net/bugs/1697541>
[12:31] <vlad_> Hey everyone quick question or issue I wanted to discuss and see if there is an easy fix. I'm on MaaS 2.1.3 and I can't assign any networks on my 3rd fabric (fabric-2) to the second interface on a set of my nodes. Is this a UI bug / should I attempt to handle this from the CLI? Should I update?
[16:10] <mpontillo> vlad_: you should be able to if you set the interface's vlan first; is there a problem with doing that?
[20:37] <gnulnx> Could use a little help understanding the networking behind managing nodes.  PXE booting / enlisting a node obviously requires a NIC on the server to be set to boot from the network, but for things like BMC data, such as via IPMI, that is usually served from a separate NIC
[20:45] <bdx> gnulnx: totally, so ensure you have that nic connected to the mgmt network
[20:49] <gnulnx> I've yet to install a test system so I don't know what this looks like.  When adding a node, is there a place to configure both NICs?
[21:00] <bdx> gnulnx: yeah ... the maas gui/cli should let you do all of that
[21:02] <gnulnx> Thanks
[21:02] <bdx> np
[21:04] <gnulnx> IPMI NICs are usually (and in my case are) on a different network though.  How is that handled?
[21:05] <gnulnx> The rackd servers would beed a NIC on both networks, right?
[21:30] <bdx> gnulnx: right