Correct needle to properly detect network connected #69
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#69
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "issue_68"
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 #68 to allow needle match when network is connected before entering Network spoke and when network is not required for install for
minimal-iso
anddvd-iso
flavors.Before this change needle would also match if network was not connected but not required (ie.
minimal-iso
ordvd-iso
).NOTE: Perhaps the smallest fix yet... 32 pixels... but hours wasted.
How Has This Been Tested?
Checklist:
PR looks good. On my first pass I encountered one failure which I believe is an environmental performance thing. I'm rerunning to be sure. Here's my initial test report:
Build8.5_minimal-iso_20211205.001108.0
Build8.5_minimal-iso_20211205.001216.0
Build8.5_dvd-iso_20211205.001335.0
audit(1638686232.075:74): avc: denied { getattr } for pid=1082 comm="login" name="/" dev="tmpfs"
audit(1638686256.063:74): avc: denied { getattr } for pid=1089 comm="login" name="/" dev="tmpfs"
Build8.5_dvd-iso_20211205.001342.0
audit(1638687101.493:74): avc: denied { getattr } for pid=1091 comm="login" name="/" dev="tmpfs"
audit(1638687150.002:74): avc: denied { getattr } for pid=1095 comm="login" name="/" dev="tmpfs"
The one failure I got in my first run passed on a rerun. I think I need to find and increase the timeout, since I keep running into this. Anyways, looks good to me.
I have a couple of standard changes that I make that generally takes care of these.
I can add a PR with them to get them included as defaults if you want. I thought I was the only one running into them. Almost anywhere there are longer timeouts for
rawhide
we can add to the conditional and option forDISTRI=rocky
and double the timeout.Perfect, that would be awesome if you could toss up a PR for adding this
to defaults. I seem to run into it only sporadically, when I've got all
my workers working at a time... but it's kind of annoying nonetheless.
On 5 Dec 16:09, Trevor Cooper wrote: