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

At running st2 pack install command from remote node, the command will be failed (but 'packs.install' will be success). #92

Closed
userlocalhost opened this issue Dec 22, 2017 · 0 comments

Comments

@userlocalhost
Copy link
Member

userlocalhost commented Dec 22, 2017

Thank you for developing this great software, this is quite useful for me.
BTW, I found a problem, or just my failure, about accessing st2 from host that runs st2-docker.

Through the Nginx, we can access to the st2auth and st2api from remote node when I install st2client and set the environment variables about ST2 like this.
2017-12-22 11 08 46

When I run st2 pack install command, an error message was shown and exit status of the st2 command would be 1.
2017-12-22 11 33 06

But the packs.install workflow was run normally and install processing was succeeded.
2017-12-22 11 28 43

I set a configuration silence_ssl_warnings to ignores the ssl verification warning.
2017-12-22 11 41 54

And I registered the CAcert of st2-docker to avoid that probolem.
2017-12-22 11 22 04

But that error message was shown and st2 pack install command was failure (although the install processing was run and succeeded) as shown before.
And the case of uninstalling pack, the same phenomenon also be occurred.

Here is the execution environment that causes that phenomenon.
2017-12-22 11 36 35

Thank you.

@arm4b arm4b closed this as completed in 6cc70fd Jul 17, 2020
transhapHigsn pushed a commit to DiligenceVault/st2-docker that referenced this issue Jun 8, 2021
You can find the old deprecated version in `DEPRECATED/all-in-one` branch archive: https://github.com/StackStorm/st2-docker/tree/DEPRECATED/all-in-one

Closes StackStorm#22, closes StackStorm#23, closes StackStorm#26, closes StackStorm#29, closes StackStorm#34, closes StackStorm#41, closes StackStorm#43, closes StackStorm#92, closes StackStorm#112, closes StackStorm#117, closes StackStorm#125, closes StackStorm#133, closes StackStorm#141, closes StackStorm#145, closes StackStorm#151, closes StackStorm#163, closes StackStorm#187,
closes StackStorm#188, closes StackStorm#189, closes StackStorm#190
Closes StackStorm#162, closes StackStorm#138, closes StackStorm#108, closes StackStorm#102, closes StackStorm#65
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant