thumper | does anyone have familiarity with windows ? | 00:17 |
---|---|---|
thumper | I'm trying to get our windows CI machine to have go installed | 00:17 |
thumper | as for some reason it seems to have lost it | 00:17 |
thumper | I'm currently struggling with two things: | 00:17 |
thumper | when I ssh from goodra the windows shell doesn't scroll, so after a page of output it just overwrites the last line | 00:18 |
thumper | I managed to download the go 1.11.12 msi | 00:18 |
thumper | but I can't seem to get it to install... | 00:18 |
hpidcock | thumper: maybe this? https://powershellexplained.com/2016-10-21-powershell-installing-msi-files/ | 00:25 |
thumper | in my frustration I rebooted the machine | 00:25 |
thumper | I hope | 00:25 |
thumper | hpidcock: let me try that... | 00:27 |
thumper | hmm... nope, that didn't seem to help | 00:31 |
thumper | man I hate windows | 00:31 |
* thumper emails crew | 00:32 | |
hpidcock | thumper: were you trying to fix the RunUnittests-win2012 job? | 00:46 |
thumper | yep | 00:47 |
thumper | and failing | 00:47 |
hpidcock | ok I'll check it out this morning | 00:47 |
thumper | thanks hpidcock | 00:49 |
thumper | hpidcock: thanks for fixing the go part. curious, what did you need to do? | 02:59 |
thumper | I notice that mongo doesn't appear to be installed as all the tests failed | 03:00 |
hpidcock | I just fixed mongo | 03:00 |
thumper | but they ended up looking for /usr/local/bin/mongo | 03:00 |
thumper | ah sweet | 03:00 |
thumper | so what was the go problem? | 03:00 |
thumper | was it actually installed and somehow out of the path? | 03:00 |
hpidcock | thumper: for some reason it never installed, I had to use that guys powershell script to install it | 03:01 |
hpidcock | probably would have been easier in the end to use RDP to do it via the gui | 03:01 |
hpidcock | also to work around the ssh issue I did `mode con lines=9999` to fool the windows conhost.exe thinking the window height is 9999 | 03:02 |
wallyworld | thumper: trivial https://github.com/juju/juju/pull/10505 | 03:03 |
hpidcock | also had to fix up all the env vars, they were wrong and weird | 03:03 |
wallyworld | babbageclunk: timClicks: how goes the vsphere cloud-init fun and games? | 03:05 |
thumper | wallyworld: looking | 03:05 |
timClicks | have figured out how to customise the new instances' hostnames | 03:06 |
timClicks | testing to see if that's sufficient | 03:06 |
wallyworld | timClicks: ok, good to unblock if it works, but it would be preferred to follow up with a bespoke cloud init per instance | 03:07 |
thumper | wallyworld: thanks, lgtm | 03:08 |
wallyworld | thumper: the race wasn't even in test code so it seems it could occur in production | 03:08 |
* thumper nods | 03:08 | |
wallyworld | not sure of the effect etc | 03:08 |
thumper | wallyworld: to be honest, unlikely to be a big problem | 03:09 |
thumper | however, good catch | 03:09 |
wallyworld | we'll need to be careful adding new entities if we also need to use a hashcache foro those | 03:09 |
thumper | wallyworld, timClicks: how can the hostname impact the delivery of the full cloud init user data? | 03:09 |
timClicks | thumper: the import process and the vm cloning process have different args | 03:10 |
wallyworld | thumper: it's more so that all cloned instances had the same hostname | 03:10 |
wallyworld | because cloud init data was set once only in the template and cloned | 03:10 |
thumper | hmm.. | 03:11 |
thumper | ok | 03:11 |
wallyworld | so setting hostname properly is necessary but not sufficient | 03:11 |
wallyworld | still need to sort out cloud init properly | 03:11 |
wallyworld | but it may unblock | 03:11 |
wallyworld | looking for quick win to start with | 03:11 |
wallyworld | small steps, just fix one thing that is feasible | 03:12 |
wallyworld | thumper: i *think* andrew's approach also had the cloud init issue (not 100%) but the hostname was not an issue - that was introduced by the alternative workflow | 03:13 |
wallyworld | thumper: do we really care about maas 1.9 now that trusty is esm? perhaps we can remove that ci test. we don't really have the means to properly run it anyway IIANM | 03:20 |
thumper | No... I don't think we care about maas 1.9 any more | 03:21 |
wallyworld | yay, one less red dot | 03:21 |
thumper | we know that juju 2.3 and 2.4 work fine and can be a jump point if necessary | 03:21 |
wallyworld | yup | 03:21 |
thumper | we should remove the 1.9 code paths from juju for 3.0 | 03:22 |
wallyworld | yep, on the metaphorical list | 03:22 |
babbageclunk | hey timClicks, how's it going? | 04:05 |
timClicks | babbageclunk: hey sorry, was outside | 04:17 |
babbageclunk | timClicks: no worries/same | 04:17 |
babbageclunk | wallyworld: approved | 05:53 |
wallyworld | awesome ty | 05:53 |
wallyworld | kelvinliu: trivial forward port from 2.6 if you are around | 06:58 |
wallyworld | https://github.com/juju/juju/pull/10507 | 06:58 |
kelvinliu | yep looking | 06:59 |
kelvinliu | wallyworld: done! thanks! | 07:01 |
wallyworld | ty | 07:01 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!