Skip to content
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

Fixes #32775 - use directly smart_proxy_rex_ssh #37

Merged
merged 1 commit into from Jun 15, 2021

Conversation

ezr-ondrej
Copy link
Member

The ForemanRemoteExecution has been discontinued and has been moved to
smart_proxy_remote_execution_ssh. We should use those classes directly
and not rely on the compatibility layer rex_core gem.

The ForemanRemoteExecution has been discontinued and has been moved to
smart_proxy_remote_execution_ssh. We should use those classes directly
and not rely on the compatibility layer rex_core gem.
Copy link
Contributor

@adamruzicka adamruzicka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works well, ACK

@adamruzicka
Copy link
Contributor

Not sure what the test failures are about though

@ezr-ondrej
Copy link
Member Author

Those are fairly strange. do we want to finalize #24 and see if the issue is only on Jenkins?

@adamruzicka
Copy link
Contributor

do we want to finalize #24 and see if the issue is only on Jenkins?

Sounds good

@ezr-ondrej
Copy link
Member Author

[test smart_proxy_ansible]

@adamruzicka adamruzicka merged commit 3f408b6 into theforeman:master Jun 15, 2021
@adamruzicka
Copy link
Contributor

Thank you @ezr-ondrej !

@ezr-ondrej ezr-ondrej deleted the no_rex_core branch June 16, 2021 00:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants