[06:04] <Ram___> Hello..
[06:05] <Ram___> I am relatively new to using MAAS. I did a couple of hardware certifications successfully.
[06:05] <Ram___> Facing any issue trying to certify another server  -Deployment failed.
[06:06] <Ram___> Is this a place I can get help?
[06:06] <Ram___> I just got to know about this chatting site.
[06:07] <Ram___> If it is not an appropriate, kindly let me know, I will exit. I see many people's names on the right pane of this window.
[08:57] <mup> Bug #1731191 changed: [2.3rc2, UI] The padding of the icons in hardware testing is not right <2.3qa> <ui> <ui-papercut> <MAAS:Fix Released by deadlight> <https://launchpad.net/bugs/1731191>
[10:42] <mup> Bug #1763219 changed: [2.4, UI, vanilla] Delete fabric confirmation text is misplaced <vanilla-transaition> <MAAS:Fix Released by deadlight> <https://launchpad.net/bugs/1763219>
[11:10] <mup> Bug #1730967 changed: [2.3rc2, UI] Secondary navigation wrapping incorrectly at medium viewports after window resize <2.3qa> <ui> <MAAS:Fix Released by deadlight> <https://launchpad.net/bugs/1730967>
[11:17] <ebbex> What could be causing "Error while calling DescribePowerTypes: RPC connection timed out to rack controller 'holy-joey' (6wfh3t)."
[11:19] <ebbex> I just did the same with 2 vm's in a test env and everything worked fine. Now "attaching" a deployed "real hardware" machine as a rackd controller, nothing happens.
[11:21] <ebbex> region-controller 'hopping-hippo' (10.0.0.1/24) and rack-controller (10.0.0.2/24) are connected on the same dumb hp procurve switch.
[11:22] <roaksoax> ebbex: that implies a rack controller cannot communicate to the region
[11:22] <roaksoax> or viceversa
[11:24] <ebbex> in what language/ip/network are they having problems? What the hell are they upto? Their IP's are right there, I can ping/curl/ssh/netcat between them.
[11:50] <ebbex> Is maas perhaps doing cluster communication on 169.254.*.* ?
[11:55] <roaksoax> ebbex: They communicate via RPC
[11:55] <roaksoax> and that seems that something may be wrong
[11:56] <roaksoax> ebbex: sudo service maas-rackd restart
[11:56] <roaksoax> and see what happens ?
[12:39] <ebbex> I had a quick glance in the /var/log/maas/rackd.log on the rackd box, looks like it could be some weird ipv6 stuff?
[12:39] <ebbex> Connection refused. (While requesting RPC info at b'http://[::ffff:127.0.0.1]:5240/MAAS/rpc/').
[12:40] <ebbex> but disabling ipv6 and/or restart of the system might have cured it.
[12:40] <roaksoax> ebbex: /etc/maas/rackd.conf -> change "lolcahost" to an actual IP address of itself
[12:40] <roaksoax> if it is in a single region/rack
[12:41] <ebbex> I'm trying to set up a ha-thing. Right now it's one regiond+rackd and two rackd.
[12:43] <mup> Bug #1730969 changed: [2.3rc2, UI] Machine details secondary nav hidden at medium viewport <2.3qa> <ui> <MAAS:Fix Released by deadlight> <https://launchpad.net/bugs/1730969>
[12:45] <roaksoax> ebbex: ok, so single region/rack should point to itself
[12:46] <roaksoax> ebbex: the other two rack should obviously point to the other rack
[12:46] <roaksoax> err
[12:46] <roaksoax> other region
[12:46] <ebbex> Yup, with you so far :)
[12:49] <ebbex> Also, noticed that I can't select a bond type (or rather the list is empty) in maas 2.4... And once deployed it ends up being an active-backup bond.
[12:53] <roaksoax> ebbex: you mean, you can't select a bond type before you deploy ?
[12:55] <ebbex> Yep.
[12:56] <roaksoax> ebbex: if you could file a bug and provide a screenshot would be really helpful, that seems like a bug that we definitely need to fix asap
[12:56] <ebbex> Sure
[12:56] <roaksoax> ebbex: thank you!
[14:16] <mup> Bug #1711570 changed: [2.3, UI] The scrollbar doesn't work properly in the expanded header. <ui> <MAAS:Fix Released by deadlight> <https://launchpad.net/bugs/1711570>
[15:01] <mup> Bug #1684136 changed: [2.2.0rc2, UI, DNS] The page header in the domain details page doesn't follow the pattern styling <ui> <ux-qa-2.2> <MAAS:Fix Released> <https://launchpad.net/bugs/1684136>
[15:31] <mup> Bug # changed: 1681820, 1682483, 1686065, 1727403
[15:49] <mup> Bug #1769929 opened: [2.4b3] traceback while enlisting <MAAS:New> <https://launchpad.net/bugs/1769929>
[17:37] <bdx> hello all
[17:38] <bdx> is there a migration path for those running 2.3.x snap to go to 2.4.x snap?
[18:41] <mza> is it possible to install to an iscsi target via maas?
[18:57] <roaksoax> bdx: not one documented at the moement, since we haven't officially released a 2.4 snap yet, as it requires core 18
[18:57] <roaksoax> mza: not at the moment
[18:58] <dsop_> hi all. for remote setups, do the controllers (region and rack) need to be physically connected to each other? or can a rack controller be in a datacenter, connected via regular network, then recreate maas network there?
[18:58] <dsop_> to rephrase, do controllers need to be physically close/connected to each other
[19:02] <roaksoax> dsop_: they dont /have/ to be, but we dont recommend rack controller on split site due to latency and stuff
[19:02] <dsop_> thank you @roaksoax. Latency isn't a big issue, this is a colocation center with a big pipe to our office.
[19:02] <mza> roaksoax: thanks
[19:09] <roaksoax> dsop_: dsop_ you should be ok then
[19:12] <dsop_> awesome. thank you!