[00:36] Damnit__, what instructions are you following? in general i mean === frankban|afk is now known as frankban [08:57] Bug #1663517 opened: test_calls_decompose_machine leaving junk in reactor === frankban is now known as frankban|afk [10:59] Hey, how can I change the hostname of a region/rack controller via the GUI or CLI? [11:25] zeestrat, there might be a ui bug in changing the hostname.. [11:32] brendand: I'm not sure if I understand. Could you elaborate? [11:33] zeestrat, the list of controllers is at MAAS/#/nodes?tab=controllers [11:33] if you click on one, then click on the hostname field, it doesn't let you edit it. i'm not sure if that is intentional [11:33] roaksoax, should we be able to update the controller hostname? [11:34] Yes, I noticed that. So I was hoping there was a way to do so with the CLI. [11:39] zeestrat, i can't actually see a way at the moment, the region-controllers update command has no hostname parameter that i can see [11:57] brendand: I couldn't find anythere there either. Shal I wait for a response from roaksoax before creating a bug? [12:03] zeestrat, you could file a bug along the lines of 'controller hostname field not editable'. if it's not *meant* to be editable it should not be a text field, i think [12:05] Bug #1663569 opened: [2.2] Prefer using - for shared network statement in dhcpd.conf [12:14] Bug #1663569 changed: [2.2] Prefer using - for shared network statement in dhcpd.conf [12:17] Bug #1663569 opened: [2.2] Prefer using - for shared network statement in dhcpd.conf [12:28] admcleod: no you cant [12:28] err [12:28] admcleod: sorry [12:28] zeestrat: no you cant [12:28] zeestrat: i responded on the bug [12:28] zeestrat: but basically, MAAS does not have a running agent on the controllers to change the hostname of the underlying system [12:30] roaksoax: Changing the hostname of the system is not a problem, however changing that (i.e. /etc/hostname) does not seem to update it in MAAS. [12:35] Basically we had a change of naming policy and would like this change to also reflect in MAAS on our controllers running in production. [12:35] zeestrat: does hostname -f reflect your new hostname ? [12:36] zeestrat: so you want ot change the underlying hostname but it doesn't reflect in MAAS [12:36] zeestrat: i'd recommend you re-open the bug and rename it to "changing controller's underlying machine hostname does not reflect in MAAS" [12:38] zeestrat: actually [12:38] zeestrat: i just tested [12:38] zeestrat: and it changed the hostname for me [12:38] zeestrat: i did: sudo hostname xyz [12:39] zeestrat: updated it in /etc/hosts [12:39] zeestrat: sudo service maas-rackd restart [12:39] zeestrat: and boom, new hostname [12:40] Oh, then I must have done something wrong. Let me try again. [12:41] zeestrat: try restarting maas-rackd [12:41] Will do. Get back to you in a few min. [12:45] tested again [12:48] roaksoax, also i think the controller hostname should be text and not an uneditable text-field. it's a bit confusing atm [12:51] brendand: maybe it is the browser, it doesn't show as an uneditable text field to me [12:51] roaksoax, when you click on it what happens? [12:52] nothing === frankban|afk is now known as frankban [12:57] roaksoax, looking at the angular code it does appear to be a non-editable text field [12:59] brendand: maybe because I'm now looking at latest trunk :) [13:05] roaksoax: You were absolutely right. Dumb mistake on my part. Forgot about an old node with the same name so of course MAAS complained because of the name collision. [13:06] zeestrat: no worries, it is not something obvious anyway :) [13:06] Thanks for bearing with me :) [13:06] zeestrat: thanks for using maas :) [13:10] roaksoax: With the hours we have saved we owe y'all a beer or two! Just give a ping if you come by Norway by any chance. [13:13] roaksoax: While I have you, do you know if there's a doc that describes which connections/ports are used between region and rack controllers? I saw some discussions in https://bugs.launchpad.net/maas/+bug/1352923 but nothing up to date. [13:24] zeestrat, afaik tcp ports 5240 and 5250-5259 [13:59] zeestrat: 5250-5259 is for internal communication between region/rack [13:59] zeestrat: for user access, 5240 [14:04] How about if you have region controller in HA with a VIP (keepalived as per your guide)? Do the rack controllers only talk to the VIP set in the rackd.conf, or also directly to one of the region controllers? [14:26] Bug #1663612 opened: [2.2, UI] During commissioning, UI shows 'Error:Node must be connected to a network.' [14:26] Bug #1663614 opened: MAAS creates a websocket connection per tab [15:39] Hello there, I've a strange error while commisioning: "update clock skew to -7324" and "http error 401" [15:40] after several unique messages (within minutes) the systen shuts down. [15:41] MaaS node list shows "Failed commisioning" [15:41] 3 nodes, 3 errors :-( [15:41] any suggestions? [15:49] MaWe_: what version of MAAS are you using ? [15:49] MaWe_: seems like the clocks on your systems are not in sync [15:49] MaWe_: but cloud-init and ntp should handle that [15:51] Version: 2.1.3+bzr5573-0ubuntu1~16.04.1 [15:52] maas-server was out of sync, did a 'service ntp restart' and it worked. [15:52] how can i test if cloud-init and ntp are ok? [15:53] MaWe_: go to the MAAS UI, Under the nodes tab, go to Controllers [15:53] nameservers are configured and should work [15:53] access your controller and see the status of the services [15:53] make sure that ntp shows gree [15:54] Bug #1663643 opened: Pod compose handles timeouts badly [15:54] ntp is green [16:04] MaWe_: and the issue keeps happening ? cloud-init should just fix the clock-skew [16:06] it keeps happening :-( [16:09] sorry.. have to leave now, will reboot the machine and try it on monday. -- thanks for your help [16:30] Bug #1663651 opened: [2.2, rev5710] MAAS has 'test' action, but it has nothing in it. [16:30] Bug #1663652 opened: Maas with HA and remote rsyslog not work [16:30] roaksoax, am I correct in thinking you can apply kernel parameters now based on tags? (e.g. tag=noacpi could apply the acpi=off parameter to the kernel)? [16:31] roaksoax, and if so, does that only apply to the ephemeral, or is it also set when the deployed kernel is installed? [16:46] bladernr: you were always able to apply parameters based on tags [16:46] bladernr: it will apply them to deployed machines too [16:51] ahhh, ok. What I meant, I guess was that I just learned that it was possible (so new to me). Thanks for confirming!! [18:09] Bug #1663686 opened: [2.2] After machine is set 'Ready' (after commissioning), messages fail to post === frankban is now known as frankban|afk