/srv/irclogs.ubuntu.com/2017/07/05/#maas.txt

=== frankban|afk is now known as frankban
mupBug #1702438 opened: [2.2] No way to specify protocol when adding a VMware chassis <cpe> <cpe-sa> <MAAS:New> <https://launchpad.net/bugs/1702438>09:36
gimmichttp://paste.ubuntu.com/25025233/13:49
gimmictrying to deploy to a node after clearing the default storage configuration and specifying raid0 across three drives13:50
gimmicI am assuming it is having problems clearing the partitions14:10
gimmicEventually failing on 14.04 with "/sys/class/block/dm-11 had no syspath (/sys/class/block/dm-11)"14:10
roaksoaxgimmic: that seems like a curtin issue. Curtin  should be clearing what was leftover on the disk before proceeding14:19
gimmicYeah. I saw a curtin update and hoped it fixed it, not so lucky14:19
gimmicTo test, is there a good way to boot the machine to a workable state I can clear the drive configurations out of myself?14:31
gimmicMaybe recommission the host and allow ssh?14:31
roaksoaxgimmic: rescue mode ?14:41
gimmicHadn't used rescue mode yet. Commissioning w/ ssh on worked. I verified /dev/sda4 was still allocated to a vg14:42
gimmicoh, unless that was the commission bits. Need caffiene14:44
roaksoaxgimmic: no, commissioning doesn't do anything with storage, so you are correct14:46
tlianQUESTION: What port/service does MAAS talk to in adding (enlisting & commissiong) new machine?15:36
tlianI am seeing the following error15:36
tlianmaasserver.websockets.protocol: [critical] Error on request (88) machine.action: No rack controllers can access the BMC of node: servername15:36
tlianMAAS and the HW management network (Cloud service) are on a different Network.  So, the issue is similar to this https://bugs.launchpad.net/maas/+bug/154727515:37
tlianNow I need to go talk to Cloud service team to open up a port so it can communicate with MAAS. What port/service (http/https/ssh ...) should I have them open?15:37
roaksoaxtlian: that seems like your rack controller cannot communicate with the BMC's of the machines15:38
roaksoaxtlian: I'm guessing that's IPMI machines15:38
roaksoaxso that would be IPMI ports15:38
tlianyes. correct15:38
tlianroaksoax: thank. I will give that a shot15:39
julenhi! I am having a little issue as well... with commissioning15:41
julenare there some extra settings for the using MaaS behind a http_proxy, which are not just adding the proxy address on the controller?15:41
julenWhile attempting to commission a node, it ends up with "Failed commissioning" and the syslog says that the systemd-timesynctl was timed out15:43
julen... and why is the node not getting the http_proxy variable as global?  ... yes, apt works, but the rest of snapd and stuff keep producing errors15:47
julenroaksoax?15:47
mupBug #1702509 opened: [2.2.1] DNS locks up regularly <MAAS:Triaged> <MAAS 2.2:Triaged> <https://launchpad.net/bugs/1702509>16:10
gimmicroaksoax: yup, if I clean up the LVM the system deploys!16:29
gimmicIs there any way I can script the partition management better? I have hundreds of nodes16:29
gimmicthe whole point of maas is that I don't have to worry about touching the bare metal as much16:29
gimmicgoing to validate it now with a fresh node and see if pre-emptively nuking the straggler LVM fixes it16:29
gimmicBasically, the templated storage pre-config is not good for my environment at all16:31
gimmicAnother question.. why doesn't maas show me what the dhcp leased address is for a node? It knows what it is, it knows the dhcp pool, it knows the arp table.. I can manually look it up but (auto assign) doesn't help much.16:40
gimmicIt should show (auto assigned: 10.10.20.23)16:40
mupBug #1702517 opened: Postgres installed with MAAS logs very aggressively <MAAS:New> <https://launchpad.net/bugs/1702517>16:46
=== frankban is now known as frankban|afk
gimmicroaksoax: so the installation process seems to fail to properly remove the vg 'vg_lscratch' during deployment16:53
gimmicI wish there was a "erase disk partitions prior to deployment" checkbox16:53
gimmicseems like that would clear it all up16:54
gimmicmaybe during comissioning16:54
roaksoaxgimmic: 'release' your failed deployment machine and erase the disks : )17:00
roaksoaxgimmic: or you can create your own commssioning script17:00
julenroaksoax: I am just looking into that. I just want to try to get the http_proxy variable set as global17:02
julenI have tried adding something after driver_04_load in the /etc/maas/preseeds/curtin_userdata but it does not take it while commissioning17:04
gimmicroaksoax: I think even saying erase the disks is failing to clean up this lvm mess17:10
gimmicthese nodes are hosed. Easiest way I found to clean up the partitions is just to dd zeroes at the start of each.. ugh17:14
mupBug #1702527 opened: cannot delete already existing subnets <MAAS:New> <https://launchpad.net/bugs/1702527>17:55
=== Guest39045 is now known as med_
gimmicAre there any examples of commissioning scripts?18:05
gimmicroaksoax: telling the failed node to erase disks seems to have hung18:06
julengimmic: I am also looking into that right now18:06
julenThere is this page: https://insights.ubuntu.com/2017/06/02/customising-maas-installs/18:07
gimmicI assume my issue is related to the same reason curtin is failing, "WARNING: Duplicate VG name vg_lscratch" and issues removing it cleanly18:07
julenbut it seems a little outdated18:07
gimmicMy issue seems to arise from how we repurposed drives from similar nodes to populate out the systems18:08
julenI guess both of our problems could be solved the same way: finding out how to modify the preseed18:08
gimmicso we have duplicate vgs in lvm, but I don't even want to use LVM. I just want to nuke the disk partitions from orbit and install18:08
julengimmic: and it is failing while commissioning, right?18:09
gimmicInitially. Then it fails during deployment too18:09
julenI cannot even manage to get the commissioning properly18:09
julena good question would be... on the older documentation, it says that one could modify the preseeds at /etc/maas/preseeds, but at the moment they look quite cryptic18:11
julenthe "commissioning" file contains just "{{preseed_data}}", but where is that defined??18:11
julengimmic: still there?18:46
gimmicYup18:46
julenI just found out how it works18:46
gimmicstill poking around18:47
julenit's actually quite simple18:47
julenyour thing is more tricky, but you can probably get a lot done with a commissioning script18:47
julendo you already know how to do it?18:48
gimmicim currently looking at throwing them all into rescue mode and simply tackling it with a remote bash script18:48
gimmicI would still need a custom deploy script to do some other tweaks, like setting up the storage automagically and allocating matching IP addresses18:49
julenbut the commissioning script part, you already understand it, right?18:49
roaksoaxgimmic: it could be that it is actually erasing which takes time20:21
roaksoaxgimmic: therey should be a quick erase option20:21
mupBug #1702560 opened: faild deploy windows 2012r2, but  boot stay ok <MAAS:New> <https://launchpad.net/bugs/1702560>20:22
mupBug #1702567 opened: Make package-dev does not include maas_api_helper.py <MAAS:Triaged> <https://launchpad.net/bugs/1702567>21:04
mupBug #1702517 changed: Postgres installed with MAAS logs very aggressively <MAAS:Invalid> <https://launchpad.net/bugs/1702517>23:28

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!