-
Notifications
You must be signed in to change notification settings - Fork 115
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
Check ansible playbook after job schedule... #15802
Check ansible playbook after job schedule... #15802
Conversation
c48735d
to
e0f6f3c
Compare
trigger: test-robottelo |
PRT Result
|
trigger: test-robottelo |
PRT Result
|
526319a
to
aa91b5d
Compare
trigger: test-robottelo |
PRT Result
|
aa91b5d
to
a8ff012
Compare
trigger: test-robottelo |
PRT Result
|
675aba6
to
ae23433
Compare
trigger: test-robottelo |
PRT Result
|
ae23433
to
35c6150
Compare
trigger: test-robottelo |
PRT Result
|
35c6150
to
823e9c2
Compare
trigger: test-robottelo |
PRT Result
|
verify job invocation for different user should show after job schedule (cherry picked from commit d4ceb5d)
verify job invocation for different user should show after job schedule (cherry picked from commit d4ceb5d)
verify job invocation for different user should show after job schedule
After adding a new user and running the job, the system displayed the root user instead of the new user.
The automation test below is written to verify that the new user is correctly set after the job runs.