tests: temporarily pin Candlepin to 4.4.2 #159
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The current latest release (4.4.3) introduces a regression that breaks the support for environments in subscription-manager. Since: - we are not testing subscription-manager here, rather the rhc role - the issue is already known by the Candlepin developers, and hopefully to be fixed in the next version hence pin the Candlepin container to the latest version before the regression, i.e. 4.4.2. This way, we can keep testing changes in the rhc role. Signed-off-by: Pino Toscano <[email protected]>
|
[citest] |
|
[citest bad] |
richm
approved these changes
Jan 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current latest release (4.4.3) introduces a regression that breaks the support for environments in subscription-manager. Since:
hence pin the Candlepin container to the latest version before the regression, i.e. 4.4.2. This way, we can keep testing changes in the rhc role.