use Rocky Linux controlled openqa-testrepo-1 #171
No reviewers
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#171
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "openqa-testrepo-1-change"
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
This PR will change the content of
/etc/yum.repos.d/openqa-testrepo-1.repo
to point at a Rocky Linux controlled repository (https://git.resf.org/testing/openqa-testrepos/openqa-testrepo-1
) instead of the current repository controlled by the Fedora QA team (https://fedorapeople.org/groups/qa/openqa-repos/openqa-testrepo-1/
).How Has This Been Tested?
/etc/yum.repos.d/openqa-testrepo-1.repo
fromhttps://git.resf.org/testing/openqa-testrepos
installed.packagetest.pm
run by hand (replacingpython3-kickstart
withpandoc-common
).In the screen for the
base_update_cli
test it is clear that the repository config change exists and the repository is valid...Test location: https://openqa.rockylinux.org/tests/24832#step/base_update_cli/7
While, utimately the test fails that is due to the it looking for the
python3-kickstart
package instead of thepandoc-common
package that the repository now contains. Merge of this PR along with #170 should allow the test to complete fully.Checklist:
Great that we finally made it to self-host the files, nice trick witht he /raw/ :)
Really good idea to be using a Rocky Linux controlled repository for our tests, I like it a lot.
Result:
As expected.
Result:
All this demonstrates that the repository config change exists and the repository is valid.