Bug #37475
closedrex pull provider job using rhel9 backend on capsule times out
Description
rex pull provider job using rhel9 backend on capsule times out
Description of problem:
rex pull provider job using rhel9 backend on capsule consistently fails in automation, with ssh2.exceptions.Timeout.
Trying out with manual setup I got two kinds of errors. On an initial rex run I got failed job with
{quote}Unexpected event #<Actions::ProxyAction::ProxyActionStopped: Actions::ProxyAction::ProxyActionStopped>
{quote}
On a subsequent run, the job remains in pending state with the following msg reeling:
{quote}Error loading data from Capsule: NoMethodError - undefined method `each_with_index' for nil:NilClass
{quote}
which probably accounts for the timeouts whe see in automation
Steps to Reproduce:
1. have a setup with external mqtt capsule on rhel9 backend and client with yggdrasil client.
2. run a rex job
Actual behavior:
Issues described above
Expected behavior:
Successful rex run
Additional info: * on rhel8 backend the same tests consistently pass * interestingy, there is one rex pull test that passes on rhel9 – it runs the job against client with stopped ygdrassil, then starts it while the job is pending. In this scenario the job succeeds.
Updated by The Foreman Bot 7 months ago
- Status changed from New to Ready For Testing
- Assignee set to Adam Ruzicka
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/113 added
Updated by The Foreman Bot 6 months ago
- Fixed in Releases smart_proxy_remote_execution_ssh-0.10.5 added
Updated by Adam Ruzicka 6 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_proxy_plugin|8dbdb9991b1f1f30827a7d2d5cb095e81161c160.