Actions
Issue #9180
closed
pulp-installer CI doesn't properly test upgrading RPM packages
Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:
Description
The task pulp_common : Add pulpcore RPM repositories doesn't replace the old repo URL when users specify a new one pulp_pkg_repo. This should be properly fixed, but this bug is written for a CI workaround.
The katello repo had "latest" in its URL, but the foreman repos have pulpcore minor releases like "3.6" in their URL. This triggers the problem when a user upgrades, or the CI upgrades.
Related issues
Updated by pulpbot over 3 years ago
- Status changed from NEW to POST
Updated by mdepaulo@redhat.com over 3 years ago
- Related to Issue #9182: pulp_installer should support replacing the RPM repo URL added
Updated by mdepaulo@redhat.com over 3 years ago
- Status changed from POST to CLOSED - DUPLICATE
Actually this is performed by #8586, even on the 3.7 branch.
Maybe I was confused by the fact that the molecule prepare.yml on that branch needed it.
Updated by mdepaulo@redhat.com over 3 years ago
- Is duplicate of Issue #8568: Overall task status remains in 'running' state while all the reports are in the final state added
Updated by mdepaulo@redhat.com over 3 years ago
- Is duplicate of deleted (Issue #8568: Overall task status remains in 'running' state while all the reports are in the final state)
Updated by mdepaulo@redhat.com over 3 years ago
- Is duplicate of Issue #8586: Installer is failing when upgrade pulpcore package added
Updated by dalley over 3 years ago
- Sprint/Milestone deleted (
3.14.4)
Dropping from the release since it's a dup.
Actions
.