-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Two new Windows machines at Azure #1932
Comments
Whoever picks this up LMK if you need access to the Azure portal. |
I'll set them up :-) I don't think I'll need access to the Azure portal, except for maybe restarting machines, but I should be able to do that via my RDP client. |
I assume this issue is referring to the same machine requirement at #1884 ? So I can close that issue? |
Hmm, for the both machines, I can connect via RDP, but I'm getting timeout issues with Ansible, despite increasing the timeout to 60 seconds. (up from 30). I was running the following:
Having put the password in |
Can you manually RDP login? |
Yeah, I had to to run the ConfigureRemotingForAnsible scripts :-) So it's not the password or IP |
Did we move the AWX server since last time? I wonder if it's an IP address/port/Firewall issue. |
No this has nothing to do with aarch64 |
I don't believe Will is using AWX (it's not fully set up for Windows yet) so will be running standalone from his laptop |
To be clear, is it failing to even connect via WinRM? If so that might be indicative of a firewall or similar blocking the port somewhere along the line |
I believe so - it's a timeout, it's not permission denied or anything.
It may be a closed port? |
Seems likely - do you have access to the Azure portal to see? |
I created them with the same groups as the other machiens I believe (We could really do with infra docs for each provider particularly when things are non-obvious) |
OK it seems to work when I connect to either 127.0.0.1 or the machines private IP address, which does suggest it's being blocked external to the machine. |
Inbound port rule now added fo rthe Win2016 machine so it should work now. |
... and the Win2019 machine |
ref #1818 |
That works now, thanks @sxa
@Haroon-Khel I'll let you know when it's installed, it's running now :-) |
Just thought I'd mention it here: The MSVS_2013 role is acting a bit weird. It will download the installer and then run it, and report that it succeeded, but then it will fail at this task: When manually checking, the |
Something's not quite right on there. Ref: https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-windows-x64-hotspot/944/console
|
Ah, that's on the 2016 one, which is in the process of having it's PB run on it. Manually installing MSVS_2013 on it now. 2019 has had it's full pb run (but I haven't setup the Jenkins user yet) |
Wasn't expecting you to still be online ;-) OK I'll let you complete it (As is now obvious I put the agent on the 2016 box) |
FYI That job above (JDK8/HotSpot) is one that will use VS2013 so will be a good test of whether the install is working. |
2016 has had it's PB run too! Again, had to manually install MSVS_2013 |
Thanks - queued up another build at https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-windows-x64-hotspot/946 FYI @andrew-m-leonard if JDK8/win/hotspot shows in failing builds tomorrow it's because of this new test run, not the nightly |
#946 still didn't work - resolved in #947 by setting |
I've rerun the JDK11 job, as I think you forgot to fill the |
|
That's an interesting spelling ... |
Yep I added in a Fixed in adoptium/temurin-build#2482 - once that is merged I can retest with the |
918 passed! 👍 |
@sxa What's left in terms of testing the machines? :-) |
From your earlier comment:
So no testing has yet been done on the 2019 machine that I'm aware of. (Also we have #1963 (comment) that needs to be resolved one way or another on the 2016 machine) |
Ah, my mistake, I thought you did that - I'll do it now |
The machine's connected 👍 The |
Testing J9 |
latest Grinder has cleared the build phase and onto testing without problems so I think it's safe. Added |
I need to request a new machine:
Please explain what this machine is needed for: Replacement of Windows 2016 tets machine at GoDaddy (already decomissioned) and Windows 2019 at AWS (To be decomissioned which this one is up). It is likely that we will decomission one of the three Win2012 test machines at Azure once these two are active.
New machines are at
52.149.211.210
and20.185.182.137
(2016 and 2019 respectively). Credentials as per the first win2012 test machine on Azure for whoever picks this up to install the playbooks on it :-)The text was updated successfully, but these errors were encountered: