Fixes _boot_to_anaconda
doesn't handle closest mirror gracefully in 8.5
#66
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#66
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "issue_65"
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 fixes #65 by providing a new needle, code and medium type modifications to connect the network interface automatically at boot.
How Has This Been Tested?
Checklist:
Before running these tests, make sure to reload your fifloader templates:
./fifloader.py --clean --load templates.fif.json
The specified test suites all connect to the network successfully. However, I am seeing a failure in
install_default@uefi
at theuefi_postinstall
step. The failure message is# Test died: no candidate needle with tag(s) 'root_console' matched
:Test report:
Build8.5_boot-iso_20211121.121813.0
# Test died: no candidate needle with tag(s) 'root_console' matched
Build8.5_boot-iso_20211121.121818.0
Will change this review to an approval on confirmation that the failure I'm seeing is unrelated to the fix for this test.
Interesting. Did you run the same POSTs I provided after running
./fifloader.py
? It was on oversight for me to include theQEMUCPU=host
parameter POST as it should not be required. I'll rerun after rolling back my vm.This is the case where also summarizing the test parameters used via
build_report.sh
might prove useful and / or it might be a good idea to always use thearchive
functionality when the job(s) were used to support a PR submission.I did run the exact same POSTs as outlined in the description for this PR. However, I just reran that suite again, twice, and both times it passed. Race condition?