New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix wpa_supplicant test #12580
Fix wpa_supplicant test #12580
Conversation
@@ -14,6 +14,7 @@ function cleanup() { | |||
kill $hostapd_pid | |||
fi | |||
modprobe -r mac80211_hwsim | |||
cat hostapd.log |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this for the test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really, I have just added line to get the results after the hostapd run.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just as suggestion: One could think about using upload_logs
in the post-run and post-fail hooks to upload this log as an openQA asset. See e.g. docker if you feel motivated 🙂
Hello @cfconrad, can you provide more insight in the history of this test? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I'd still add a SLES verification run (VR) as well, then it's ready to rock.
Congrats 🥳
@@ -14,6 +14,7 @@ function cleanup() { | |||
kill $hostapd_pid | |||
fi | |||
modprobe -r mac80211_hwsim | |||
cat hostapd.log |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just as suggestion: One could think about using upload_logs
in the post-run and post-fail hooks to upload this log as an openQA asset. See e.g. docker if you feel motivated 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm for changing the aa profile or adding allways_rollback
as aa is a main feature and I don't like to just disable it for the hole later coming test modules.
It was invented by @grisu48, thx for your research and the really great idea! Based on that idea there are several tests around it:
I would vote for a perl module which do the common works. And that is actually what |
I agree on the SLES VR. Dee maybe you could run eg this job as a verification run, just to double check that the wpa_supplicant module passes ok on SLES, and that disabling the hostapd apparmor profile does not really change the outcome of modules later in the schedule as cfconrad has hypothesized. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Nice work, the addressed issues have been resolved!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx for the update!
LGTM
I see many suggestion still opened but not resolved. Why was this merged? |
Well, the suggestions (apart from the idea to move the script to perl) were implemented. I just could not mark them as resolved myself, but I left a comment to indicate it |
maybe my fault then... but usually if I changed something in the way someone suggested it, I click the resolve button. Especially if someone put a |
AppArmor prevents the hostpad config file from being read. so execution of aa-disable hostapd before starting hostapd.
Tumbleweed - http://10.161.229.147/tests/592#step/wpa_supplicant/1
SLE15 SP2 VR - http://10.161.229.147/tests/591#step/wpa_supplicant/1
LEAP - http://10.161.229.147/tests/593#step/wpa_supplicant/1