Skip to content
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

UnixPb: Use wget to download ant-contrib on centos6 #2488

Merged
merged 3 commits into from
Mar 2, 2022

Conversation

Haroon-Khel
Copy link
Contributor

@Haroon-Khel Haroon-Khel commented Feb 24, 2022

  • commit message has one of the standard prefixes
  • faq.md updated if appropriate
  • other documentation is changed or added (if applicable)
  • playbook changes run through VPC or QPC (if you have access)
  • for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

ref #2486

@Haroon-Khel
Copy link
Contributor Author

@sxa
Copy link
Member

sxa commented Feb 24, 2022

Kicked off vpc https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/1397/

This has failed for the same reasons as documented in #2314 so you will need to cleanup the machine using the commands described in there - it's got up to vboxnet127 again.

@Haroon-Khel
Copy link
Contributor Author

@sxa I followed the instructions in your issue. Kicked off another vpc https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/1398/

@Haroon-Khel
Copy link
Contributor Author

The centos6 docker check has passed on this pr btw so atleast we know this pr fixes that issue

@sxa
Copy link
Member

sxa commented Mar 1, 2022

Looks like a lot of failures in VPC around the ant contrib download, but unclear if that's this change or an outage on the HTTP server end.

@Haroon-Khel
Copy link
Contributor Author

Haroon-Khel commented Mar 1, 2022

I've added ca-certificates to the ubuntu, debian, centos and rhel install lists. Kicked off another vpc https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/1399/

Looks like a lot of failures in VPC around the ant contrib download, but unclear if that's this change or an outage on the HTTP server end.

Some OS's (ubuntu16 and 20) are able to verify sourcefourge.net's certificate, while others cannot

Resolving downloads.sourceforge.net... 204.68.111.105
Connecting to downloads.sourceforge.net|204.68.111.105|:443... connected.
ERROR: cannot verify downloads.sourceforge.net's certificate, issued by `/C=US/O=Let\'s Encrypt/CN=R3':
  Issued certificate has expired.

I think machines with a 2021 ca-certificate version can verify, while those with an older version cannot. Hence why I am testing to see if updating ca-certificates at the beginning of the playbook (Common role) will allow the machine to verify the ant-contrib download

@Haroon-Khel
Copy link
Contributor Author

Ubuntu 16+ and centos7+ have a 2021 ca-certifcates package available for them in their respective package manager repo. Centos 6 does not. I thought I fixed Centos 6's issue (earlier centos6 pr check was able to download ant-contrib fine) but the vpc still shows that it is having trouble downloading ant-contrib

@Haroon-Khel
Copy link
Contributor Author

Haroon-Khel commented Mar 1, 2022

Centos 6 VPC and Docker check now seem to be experiencing a network issue when connecting to Centos vault

VPC

TASK [CentOS6-Cent7SSL : Install prereqs for building ca-certificate bundle ...] ***
16:59:05 fatal: [127.0.0.1]: FAILED! => {"changed": false, "changes": {"installed": ["asciidoc", "java-1.6.0-openjdk"]}, "msg": "https://vault.centos.org/centos/6/os/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 7 - \"Failed to connect to 2600:1f13:2e7:2901:d2b0:c3b2:9347:934c: Network is unreachable\"\nTrying other mirror.\nhttps://vault.centos.org/centos/6/extras/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 7 - \"Failed to connect to 2600:1f13:2e7:2901:d2b0:c3b2:9347:934c: Network is unreachable\

Docker check

Step 3/10 : RUN sed -i -e 's!mirrorlist!#mirrorlist!g' /etc/yum.repos.d/CentOS-Base.repo;     sed -i -e 's!#baseurl=[http://mirror.centos.org/centos/\$releasever!baseurl=https://vault.centos.org/6.10/!g](http://mirror.centos.org/centos//$releasever!baseurl=https://vault.centos.org/6.10/!g)' /etc/yum.repos.d/CentOS-Base.repo;     yum -y update; yum clean all;     yum -y install gcc openssl-devel bzip2-devel sqlite-devel sudo wget python3 epel-release;     yum -y install ansible
 ---> Running in 5bdbf0d52442
Loaded plugins: fastestmirror, ovl
Setting up Update Process
https://vault.centos.org/6.10//os/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 7 - "Failed to connect to 2600:1f16:c1:5e03:a992:8ee1:99d2:6f8: Cannot assign requested address"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: base. Please verify its path and try again
Loaded plugins: fastestmirror, ovl
Cleaning repos: base extras updates
Cleaning up Everything
Loaded plugins: fastestmirror, ovl
Setting up Install Process
Determining fastest mirrors
https://vault.centos.org/6.10//os/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 7 - "Failed to connect to 2600:1f13:2e7:2901:d2b0:c3b2:9[34](https://github.com/adoptium/infrastructure/runs/5379065682?check_suite_focus=true#step:4:34)7:934c: Cannot assign requested address"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repositor

Possibly intermittent actions/runner-images#2264. Will kick off another centos6 vpc when Previous vpc job finishes

@Haroon-Khel
Copy link
Contributor Author

https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/1399/
Upgrading ca-certificates at the beginning of the playbook run seems to have fixed those OS's that failed earlier. Centos8 is still acting up, but due to an issue unrelated to this pr

Kicked off a Centos6 only VPC
https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/1400/

@Haroon-Khel
Copy link
Contributor Author

VPC and Docker pr check both passed. I think this can be merged

@Haroon-Khel Haroon-Khel requested review from sxa and Willsparker March 2, 2022 13:06
Copy link
Member

@sxa sxa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants