Upgraded to st2 2.10.1 from 2.7 and dont have core.winrm_cmd?

• has this been moved to windows? I am running the st2tests scripts to validate the examples and it appears to not be part of the package, have I missed something or does the tests script test_winrm_runners just need to be updated?

  st2 run tests.test_winrm_runners token=${ST2_AUTH_TOKEN} winrm_host=amibuild-eqx-04.force10networks.com winrm_username=ncore\pgits winrm_password=... winrm_verify_ssl_cert=false winrm_transport=ntlm . id: 5c560e06d09ab707af88511f action.ref: tests.test_winrm_runners parameters: token: f.... winrm_host: .....com winrm_password: '********' winrm_transport: ntlm winrm_username: ncorepgits winrm_verify_ssl_cert: false status: failed result_task: is_winrm_host_provided result: failed: false return_code: 0 stderr: '' stdout: '' succeeded: true error: Failed to run task "run_winrm_cmd_action". Action with reference "core.winrm_cmd" doesn't exist.. Task :: run_winrm_cmd_action - Action with ref core.winrm_cmd not registered. traceback: Traceback (most recent call last): File "/opt/stackstorm/st2/local/lib/python2.7/site-packages/action_chain_runner/action_chain_runner.py", line 486, in _run_chain action_params=action_parameters, context_result=context_result) File "/opt/stackstorm/st2/local/lib/python2.7/site-packages/action_chain_runner/action_chain_runner.py", line 716, in _get_next_action raise action_exc.InvalidActionReferencedException(error) InvalidActionReferencedException: Task :: run_winrm_cmd_action - Action with ref core.winrm_cmd not registered.

Thanks in advance,

Peter M. Gits

Those actions should still be there (we didn’t remove them or change their location).

It looks like that for some reason they didn’t get registered. I would try running sudo st2ctl reload --register-runners --register-actions.

If you still don’t see those actions after running that command, please include the output of that and st2 action list --pack=core command so we can check what is going on.

yes, didn’t see it after running the above commands…

+-------------------+------+-----------------------------------------------+
| ref               | pack | description                                   |
+-------------------+------+-----------------------------------------------+
| core.announcement | core | Action that broadcasts the announcement to    |
|                   |      | all stream consumers.                         |
| core.ask          | core | Action for initiating an Inquiry (usually in  |
|                   |      | a workflow)                                   |
| core.http         | core | Action that performs an http request.         |
| core.local        | core | Action that executes an arbitrary Linux       |
|                   |      | command on the localhost.                     |
| core.local_sudo   | core | Action that executes an arbitrary Linux       |
|                   |      | command on the localhost.                     |
| core.noop         | core | Action that does nothing                      |
| core.pause        | core | Action to pause current thread of workflow    |
|                   |      | /sub-workflow.                                |
| core.remote       | core | Action to execute arbitrary linux command     |
|                   |      | remotely.                                     |
| core.remote_sudo  | core | Action to execute arbitrary linux command     |
|                   |      | remotely.                                     |
| core.sendmail     | core | This sends an email                           |
| core.uuid         | core | Generate a new UUID (default uuid4)           |
| core.windows_cmd  | core | Action to execute arbitrary Windows command   |
|                   |      | remotely.                                     |
+-------------------+------+-----------------------------------------------+

st2 --version

st2 2.10.1, on Python 2.7.6

Cheers,

Peter

How is your system set up? (single VM, k8s, etc) and how did you perform the upgrade?

Using the docker instance,

I performed the docker-compose down
performed the git pull
ran docker-compose up

and was running 2.7 and now running 2.10.1

I did not reinstall any of the packages that were already installed through the web.

Cheers,

Peter

Can’t say for certain, but my guess is that something’s not quite right with your upgrade steps, since you’re not doing a full re-deployment. Docker needs a bit different handling.

You could check that the underlying content exists in your upgraded container. Should be in /opt/stackstorm/packs/core/actions. If it does, but is not showing up in output of st2 action list -p core, you may need to re-register all content, with sudo st2ctl reload --register-all