FIX: release_identification for Rocky Linux 9 #116
Labels
No Label
priority: critical
priority: high
priority: low
priority: medium
status: abandoned
status: duplicate
status: invalid
status: peer review needed
status: wontfix
tag: content
tag: good first issue
tag: help wanted
test suite
type: bug
type: documentation
type: enhancement
type: maintenance
type: question
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: testing/os-autoinst-distri-rocky-migrated#116
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "release_ident_9"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Resolves failures of
rocky_release
andos_release
inrelease_identification
test suite.This PR is related to #114 and includes commits that @lumarel must have landed into his branch after the PR was created which would explain why his commits from June 27 are also included? Those commits are unrelated to this PR and I'm not sure the effect. I'll make this a DRAFT to be sure...
Resolves #115
How Has This Been Tested?
I was unfortunately not able to fix all tests, but the new needles should fix a whole lot of tests (incl. help fully)
Checklist:
I got a non-critical failure on
install_upload_default@_collect_data
but everything else looks good. Can take another pass if there are updates available.I ran that as cherry-picks on top of #117 and everything looks fine!
Thank you Trevor for fixing this! 🙂
@akatch The non-critical failure for
_collect_data
is because that test attempts to installtar
usingdnf
and repos inside the SUT are pointing atpub
which doesn't exist (yet).My next item to tackle is fixing some of the
lib/utils.pm
stuff so that we can point at staging (or even Peridot yumrepofs) repos for testing using test variables (likeLOCATION
). It's pretty easy to work on that with a completedinstall_default_upload
in place (which I have).That should fix this (and other) failures related to repository access like
base_update_cli
,base_package_install_remove
andmodularity_tests
.We are moving forward, thank you Trevor once again!