epel/releng
6
1
Fork 0
Code Issues 16 Projects Activity

epel-release-latest-10 symlink churn, again #117

New issue
Closed
opened 2026-08-26 23:59:48 +00:00 by carlwgeorge · 2 comments
carlwgeorge commented 2026-08-26 23:59:48 +00:00
Owner
Copy link

The epel-release-latest links used in our getting started guide are symlinks on the mirror created by the new-updates-sync script. We've had a problem before with this script when it was flipping paths between architectures and causing intermittent 403 errors, and then again later when it was flipping paths between EPEL 10 minor versions. Now we have a new problem, where we legitimately have two different epel-release packages in different EPEL 10 minor versions:

  • EPEL 10.2: epel-release-10-8.el10_2
  • EPEL 10.3/10.4: epel-release-10-9.el10_3

The symlink was churning, but would usually end with the 10.2 path like we wanted. Somehow today it ended up on the 10.4 path, which caused at least one RHEL user to install the wrong release and get dependency errors.

As a short term fix, I have manually switched the epel-release-latest-10.noarch.rpm symlink back to the 10.2 path, and commented out the function call in new-updates-sync script that updates the symlinks.

We should figure out a better long term solution so that we can get the correct behavior.

The epel-release-latest links used in our [getting started guide](https://docs.fedoraproject.org/en-US/epel/getting-started/) are symlinks on the mirror created by the [new-updates-sync script](https://forge.fedoraproject.org/infra/ansible/src/branch/main/roles/bodhi2/backend/files/new-updates-sync). We've had a problem before with this script when it was [flipping paths between architectures and causing intermittent 403 errors](https://forge.fedoraproject.org/infra/tickets/issues/12326), and then again later when it was [flipping paths between EPEL 10 minor versions](https://forge.fedoraproject.org/epel/steering/issues/318). Now we have a new problem, where we legitimately have two different epel-release packages in different EPEL 10 minor versions: * EPEL 10.2: epel-release-10-8.el10_2 * EPEL 10.3/10.4: epel-release-10-9.el10_3 The symlink was churning, but would usually end with the 10.2 path like we wanted. Somehow today it ended up on the 10.4 path, which caused at least one RHEL user to [install the wrong release](https://bugzilla.redhat.com/show_bug.cgi?id=2521652) and get dependency errors. As a short term fix, I have manually switched the epel-release-latest-10.noarch.rpm symlink back to the 10.2 path, and commented out the function call in new-updates-sync script that updates the symlinks. We should figure out a better long term solution so that we can get the correct behavior.
carlwgeorge commented 2026-08-27 00:01:43 +00:00
Author
Owner
Copy link

infra/ansible#3642

https://forge.fedoraproject.org/infra/ansible/pulls/3642
carlwgeorge commented 2026-08-31 23:05:12 +00:00
Author
Owner
Copy link

That PR has been merged and deployed, and everything seems to be working as expected.

That PR has been merged and deployed, and everything seems to be working as expected.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
  
backlog status
needs review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

Archived

  
backlog status
ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

Archived

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

Archived

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

Archived

  
planned
A task that was added to a sprint from the beggining of it.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

Archived

  
priority
high
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
priority
low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
priority
medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
sprint status
blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

Archived

  
sprint status
done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

Archived

  
sprint status
in progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

Archived

  
sprint status
review
 Work items that are complete but need review, testing, or approval before being marked as done.

Archived

  
sprint status
to do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

Archived

  
technical debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

Archived

  
work item
bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

Archived

  
work item
epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
work item
spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

Archived

  
work item
task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

Archived

  
work item
user story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

Archived

No labels
backlog status
needs review
backlog status
ready
chore
documentation
planned
points
01
points
02
points
03
points
05
points
08
points
13
priority
high
priority
low
priority
medium
sprint status
blocked
sprint status
done
sprint status
in progress
sprint status
review
sprint status
to do
technical debt
work item
bug
work item
epic
work item
spike
work item
task
work item
user story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
2026 Sprint 15
Assignees
Clear assignees
No assignees
carlwgeorge
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
epel/releng#117
No description provided.