| pmatulis | Damnit__, what instructions are you following? in general i mean | 00:36 |
|---|---|---|
| === frankban|afk is now known as frankban | ||
| mup | Bug #1663517 opened: test_calls_decompose_machine leaving junk in reactor <tests> <MAAS:In Progress by allenap> <https://launchpad.net/bugs/1663517> | 08:57 |
| === frankban is now known as frankban|afk | ||
| zeestrat | Hey, how can I change the hostname of a region/rack controller via the GUI or CLI? | 10:59 |
| brendand | zeestrat, there might be a ui bug in changing the hostname.. | 11:25 |
| zeestrat | brendand: I'm not sure if I understand. Could you elaborate? | 11:32 |
| brendand | zeestrat, the list of controllers is at MAAS/#/nodes?tab=controllers | 11:33 |
| brendand | 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 |
| brendand | roaksoax, should we be able to update the controller hostname? | 11:33 |
| zeestrat | Yes, I noticed that. So I was hoping there was a way to do so with the CLI. | 11:34 |
| brendand | 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:39 |
| zeestrat | brendand: I couldn't find anythere there either. Shal I wait for a response from roaksoax before creating a bug? | 11:57 |
| brendand | 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:03 |
| mup | Bug #1663569 opened: [2.2] Prefer using <fabric-name>-<vlan-name> for shared network statement in dhcpd.conf <MAAS:New> <https://launchpad.net/bugs/1663569> | 12:05 |
| mup | Bug #1663569 changed: [2.2] Prefer using <fabric-name>-<vlan-name> for shared network statement in dhcpd.conf <MAAS:New> <https://launchpad.net/bugs/1663569> | 12:14 |
| mup | Bug #1663569 opened: [2.2] Prefer using <fabric-name>-<vlan-name> for shared network statement in dhcpd.conf <MAAS:New> <https://launchpad.net/bugs/1663569> | 12:17 |
| roaksoax | admcleod: no you cant | 12:28 |
| roaksoax | err | 12:28 |
| roaksoax | admcleod: sorry | 12:28 |
| roaksoax | zeestrat: no you cant | 12:28 |
| roaksoax | zeestrat: i responded on the bug | 12:28 |
| roaksoax | zeestrat: but basically, MAAS does not have a running agent on the controllers to change the hostname of the underlying system | 12:28 |
| zeestrat | 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:30 |
| zeestrat | 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 |
| roaksoax | zeestrat: does hostname -f reflect your new hostname ? | 12:35 |
| roaksoax | zeestrat: so you want ot change the underlying hostname but it doesn't reflect in MAAS | 12:36 |
| roaksoax | 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:36 |
| roaksoax | zeestrat: actually | 12:38 |
| roaksoax | zeestrat: i just tested | 12:38 |
| roaksoax | zeestrat: and it changed the hostname for me | 12:38 |
| roaksoax | zeestrat: i did: sudo hostname xyz | 12:38 |
| roaksoax | zeestrat: updated it in /etc/hosts | 12:39 |
| roaksoax | zeestrat: sudo service maas-rackd restart | 12:39 |
| roaksoax | zeestrat: and boom, new hostname | 12:39 |
| zeestrat | Oh, then I must have done something wrong. Let me try again. | 12:40 |
| roaksoax | zeestrat: try restarting maas-rackd | 12:41 |
| zeestrat | Will do. Get back to you in a few min. | 12:41 |
| roaksoax | tested again | 12:45 |
| brendand | roaksoax, also i think the controller hostname should be text and not an uneditable text-field. it's a bit confusing atm | 12:48 |
| roaksoax | brendand: maybe it is the browser, it doesn't show as an uneditable text field to me | 12:51 |
| brendand | roaksoax, when you click on it what happens? | 12:51 |
| roaksoax | nothing | 12:52 |
| === frankban|afk is now known as frankban | ||
| brendand | roaksoax, looking at the angular code it does appear to be a non-editable text field | 12:57 |
| roaksoax | brendand: maybe because I'm now looking at latest trunk :) | 12:59 |
| zeestrat | 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:05 |
| roaksoax | zeestrat: no worries, it is not something obvious anyway :) | 13:06 |
| zeestrat | Thanks for bearing with me :) | 13:06 |
| roaksoax | zeestrat: thanks for using maas :) | 13:06 |
| zeestrat | 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:10 |
| zeestrat | 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:13 |
| pmatulis | zeestrat, afaik tcp ports 5240 and 5250-5259 | 13:24 |
| roaksoax | zeestrat: 5250-5259 is for internal communication between region/rack | 13:59 |
| roaksoax | zeestrat: for user access, 5240 | 13:59 |
| zeestrat | 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:04 |
| mup | Bug #1663612 opened: [2.2, UI] During commissioning, UI shows 'Error:Node must be connected to a network.' <MAAS:New> <https://launchpad.net/bugs/1663612> | 14:26 |
| mup | Bug #1663614 opened: MAAS creates a websocket connection per tab <performance> <MAAS:Triaged> <https://launchpad.net/bugs/1663614> | 14:26 |
| MaWe_ | Hello there, I've a strange error while commisioning: "update clock skew to -7324" and "http error 401" | 15:39 |
| MaWe_ | after several unique messages (within minutes) the systen shuts down. | 15:40 |
| MaWe_ | MaaS node list shows "Failed commisioning" | 15:41 |
| MaWe_ | 3 nodes, 3 errors :-( | 15:41 |
| MaWe_ | any suggestions? | 15:41 |
| roaksoax | MaWe_: what version of MAAS are you using ? | 15:49 |
| roaksoax | MaWe_: seems like the clocks on your systems are not in sync | 15:49 |
| roaksoax | MaWe_: but cloud-init and ntp should handle that | 15:49 |
| MaWe_ | Version: 2.1.3+bzr5573-0ubuntu1~16.04.1 | 15:51 |
| MaWe_ | maas-server was out of sync, did a 'service ntp restart' and it worked. | 15:52 |
| MaWe_ | how can i test if cloud-init and ntp are ok? | 15:52 |
| roaksoax | MaWe_: go to the MAAS UI, Under the nodes tab, go to Controllers | 15:53 |
| MaWe_ | nameservers are configured and should work | 15:53 |
| roaksoax | access your controller and see the status of the services | 15:53 |
| roaksoax | make sure that ntp shows gree | 15:53 |
| mup | Bug #1663643 opened: Pod compose handles timeouts badly <pods> <MAAS:Triaged by blake-rouse> <https://launchpad.net/bugs/1663643> | 15:54 |
| MaWe_ | ntp is green | 15:54 |
| roaksoax | MaWe_: and the issue keeps happening ? cloud-init should just fix the clock-skew | 16:04 |
| MaWe_ | it keeps happening :-( | 16:06 |
| MaWe_ | sorry.. have to leave now, will reboot the machine and try it on monday. -- thanks for your help | 16:09 |
| mup | Bug #1663651 opened: [2.2, rev5710] MAAS has 'test' action, but it has nothing in it. <MAAS:New> <https://launchpad.net/bugs/1663651> | 16:30 |
| mup | Bug #1663652 opened: Maas with HA and remote rsyslog not work <MAAS:New> <https://launchpad.net/bugs/1663652> | 16:30 |
| bladernr | 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:30 |
| bladernr | roaksoax, and if so, does that only apply to the ephemeral, or is it also set when the deployed kernel is installed? | 16:31 |
| roaksoax | bladernr: you were always able to apply parameters based on tags | 16:46 |
| roaksoax | bladernr: it will apply them to deployed machines too | 16:46 |
| bladernr | ahhh, ok. What I meant, I guess was that I just learned that it was possible (so new to me). Thanks for confirming!! | 16:51 |
| mup | Bug #1663686 opened: [2.2] After machine is set 'Ready' (after commissioning), messages fail to post <MAAS:Triaged> <https://launchpad.net/bugs/1663686> | 18:09 |
| === frankban is now known as frankban|afk | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!