-
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
time-to-pickup tests for pull rex #10591
Conversation
trigger: test-robottelo |
e84f4bf
to
548cdc0
Compare
trigger: test-robottelo |
1 similar comment
trigger: test-robottelo |
result = rhel_contenthost.execute('yggdrasil status') | ||
assert result.status == 0, f'Failed to start yggdrasil on client: {result.stderr}' |
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 beware this is not as great indication as one could think
# yggdrasil status
Connection status for joint-jaybird.example.com:
● Connected to Red Hat Subscription Management
● The yggdrasil daemon is inactive
Manage your Red Hat connector systems: https://red.ht/connector
# echo $?
0
# systemctl status yggdrasild
● yggdrasild.service - yggdrasil daemon
Loaded: loaded (/usr/lib/systemd/system/yggdrasild.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2023-02-02 08:40:22 EST; 1min 9s ago
Docs: https://github.com/redhatinsights/yggdrasil
Process: 849 ExecStart=/usr/sbin/yggdrasild (code=exited, status=1/FAILURE)
Main PID: 849 (code=exited, status=1/FAILURE)
Feb 02 08:40:22 joint-jaybird.example.com systemd[1]: Started yggdrasil daemon.
Feb 02 08:40:22 joint-jaybird.example.com yggdrasild[849]: [yggdrasild] 2023/02/02 08:40:22 /builddir/build/BUILD/yggdrasil-0.2.0/cmd/yggd/main.go:155: starting yggdrasild version 0.2.0
Feb 02 08:40:22 joint-jaybird.example.com yggdrasild[849]: [yggdrasild] 2023/02/02 08:40:22 /builddir/build/BUILD/yggdrasil-0.2.0/cmd/yggd/main.go:200: listening on socket: @yggd-dispatcher-oIHvYx
Feb 02 08:40:22 joint-jaybird.example.com yggdrasild[849]: cannot connect to broker: network Error : dial tcp: lookup expert-earwig.example.com on 192.168.122.1:53: no such host
Feb 02 08:40:22 joint-jaybird.example.com systemd[1]: yggdrasild.service: Main process exited, code=exited, status=1/FAILURE
Feb 02 08:40:22 joint-jaybird.example.com systemd[1]: yggdrasild.service: Failed with result 'exit-code'.
548cdc0
to
6c380ce
Compare
trigger: test-robottelo |
6c380ce
to
df020e3
Compare
df020e3
to
654505b
Compare
trigger: test-robottelo |
Previous prt failures occurred because the job was using the default capsule with ssh provider to go around the lack of response form mqtt client, so the negative assert was not met. Latest push changes the global setting to disallow that. From prt run 1773:
@shubhamsg199 @adamruzicka mind revisiting? |
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 don't have anything to add, lgtm
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.
Ack
tests for time-to-pickup setting introduced in 6.13 for pull-provider rex jobs
requires SatelliteQE/nailgun#888