#12263 setup new f40/f41 maintainer test instances
Closed: Fixed 3 months ago by phsmoura. Opened 5 months ago by kevin.

We have a f39-test.fedorainfracloud.org, but we got behind and need to make 40/41 instances.

Basically that means spinning them up in aws, then adding them to ansible and configuring them.


Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

5 months ago

Metadata Update from @zlopez:
- Issue untagged with: low-gain, low-trouble
- Issue tagged with: medium-gain, medium-trouble

5 months ago

@kevin follow below the patch for dns adding f40/41 ips

diff --git a/master/fedorainfracloud.org b/master/fedorainfracloud.org
index 414abb40..a0339a78 100644
--- a/master/fedorainfracloud.org
+++ b/master/fedorainfracloud.org
@@ -86,6 +86,8 @@ iddev                 IN      A       18.216.224.72
 f37-test                        IN      A       35.90.91.173
 f38-test                        IN      A       34.222.162.17
 f39-test                        IN      A       35.90.209.72
+f40-test                        IN      A       35.90.209.73
+f41-test                        IN      A       35.90.209.74
 rawhide-test                   IN      A       35.160.127.57
 ;
 aarch64-test01         IN       A        34.215.168.74
diff --git a/master/vpn.fedoraproject.org b/master/vpn.fedoraproject.org
index f13f1b4e..877ee629 100644
--- a/master/vpn.fedoraproject.org
+++ b/master/vpn.fedoraproject.org
@@ -211,6 +211,8 @@ people3     IN  CNAME   people03

 f38-test         IN  A       192.168.100.16
 f39-test         IN  A       192.168.100.30
+f40-test         IN  A       192.168.100.35
+f41-test         IN  A       192.168.100.36
 ;f36-test         IN  A       192.168.100.32
 rawhide-test     IN  A       192.168.100.17
 el7-test         IN  A       192.168.100.18

So, the vpn ones probibly are fine, but the other ones need to be the ip's for those instances after you start them up... I can't seem to ping them here (but might be a network policy issue?)

ops sorry, I thought it would be the other way around. Here is the patch updated

index 414abb40..2abb386d 100644
--- a/master/fedorainfracloud.org
+++ b/master/fedorainfracloud.org
@@ -86,6 +86,8 @@ iddev                 IN      A       18.216.224.72
 f37-test                        IN      A       35.90.91.173
 f38-test                        IN      A       34.222.162.17
 f39-test                        IN      A       35.90.209.72
+f40-test                        IN      A       34.221.65.48
+f41-test                        IN      A       54.184.39.239
 rawhide-test                   IN      A       35.160.127.57
 ;
 aarch64-test01         IN       A        34.215.168.74
diff --git a/master/vpn.fedoraproject.org b/master/vpn.fedoraproject.org
index f13f1b4e..877ee629 100644
--- a/master/vpn.fedoraproject.org
+++ b/master/vpn.fedoraproject.org
@@ -211,6 +211,8 @@ people3     IN  CNAME   people03

 f38-test         IN  A       192.168.100.16
 f39-test         IN  A       192.168.100.30
+f40-test         IN  A       192.168.100.35
+f41-test         IN  A       192.168.100.36
 ;f36-test         IN  A       192.168.100.32
 rawhide-test     IN  A       192.168.100.17
 el7-test         IN  A       192.168.100.18

Yeah, dns has to be first so ansible knows what ip's to try and go to configure things.

Updated now. ;)

Metadata Update from @phsmoura:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 months ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog