Usually the updates-testing repo is enabled by default when we enable bodhi and then it gets disabled later in the cycle. It's currently disabled by default. Reproducible: Always Steps to Reproduce: 1. Deploy new image/install 2. Run "dnf upgrade" 3. Expect updates from updates-testing to be shown Actual Results: updated-testing is disabled
Proposed as a Blocker for 41-beta by Fedora user pbrobinson using the blocker tracking app because: updates-testing should be enabled from bodhi enable until final freeze
+2 blocker and +1 FE in https://pagure.io/fedora-qa/blocker-review/issue/1633 so marking as accepted FE at least.
Yep, this was missed, apologies, and thanks for catching it! The fix for this has been merged[1] and is sent to build![2] [1] https://src.fedoraproject.org/rpms/fedora-repos/pull-request/146 [2] https://koji.fedoraproject.org/koji/taskinfo?taskID=122901164
Discussed during the 2024-09-03 blocker review meeting: [1] The decision to classify this bug wasn't made: "As this is already accepted as an FE and the blocker status appears to be subject to FESCo jumping all over it, we'll delay the decision on blocker status while that happens. in any case the bug will shortly be fixed." [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-09-03/f41-blocker-review.2024-09-03-16.00.log.html
FEDORA-2024-7eb873d8d3 (fedora-repos-41-0.5) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-7eb873d8d3
FEDORA-2024-7eb873d8d3 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-7eb873d8d3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7eb873d8d3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-7eb873d8d3 (fedora-repos-41-0.5) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.