-
Notifications
You must be signed in to change notification settings - Fork 17
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
tests: pin Candlepin version to latest before Java 17 #85
tests: pin Candlepin version to latest before Java 17 #85
Conversation
The current way of deploying Candlepin uses an Ansible role that is no more used/supported by the Candlepin project, and thus it is rotting; the recent switch of Candlepin from Java 11 to Java 17 broke with the unmaintained role. Thus, as very short-term workaround, pin the version of Candlepin to deploy to the commit before the switch to Java 17. Signed-off-by: Pino Toscano <[email protected]>
[citest] |
OK, things generally work fine, at least from a Candlepin POV. The issues that shows up are the same that appeared for #84 too, i.e.:
Since almost everything is external (either Fedora or the |
Is this the issue that affects rhel 8.9 as well?
|
No, the above issue affects only CentOS Stream 8; the failure of RHEL 8.9 is the same for every OS, and it's...
... this. |
Every OS except rhel 9.3? |
No, including, so likely a single change would probably fix |
The weekly ci job for this role will run in a few days - we'll see if some of the issues have been fixed by then |
The current way of deploying Candlepin uses an Ansible role that is no more used/supported by the Candlepin project, and thus it is rotting; the recent switch of Candlepin from Java 11 to Java 17 broke with the unmaintained role.
Thus, as very short-term workaround, pin the version of Candlepin to deploy to the commit before the switch to Java 17.