-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
Reinstalling the new custom pack is not getting rendered on the Web UI #315
Comments
@armab Could you please look into this issue? |
You have not answered the question here: This issue and #313 probably have the same cause. To help you we need to know how you have configured packs. In particular what are your values for |
@cognifloyd @armab We have used Shared Volumes to install the custom packs as per the documentation. One of the API Calls is showing Response 404. We have not used any Custom APIs apart from default StackStorm APIs. |
[email protected] - Please look into this |
Again: please show me your values. Feel free to replace any secrets with |
Looking at the command you are running then you need to be careful about your use of '. You look like you are trying to send through a parmetr of message with a json string of {'title':'..', ... }. But as your outer quote is the same type as the inner ones then it's going to get all a bit messed up. You get away with it on the core.local as sending cmd='echo 'OK'' - is actually treated as the concatenaton of strings:
Hence why in the parameters to the first call, it says the cmd passed was echo OK, rather than echo 'OK'. So I'd suggest using "" as the outer quotes, so that the single quotes are kept. |
@cognifloyd Here is the vaule.yaml file for your reference below. We have used Shared Volumes for the custom pack. Initially, when we tried to install the custom pack CNAS, the pack and its underlying actions/workflows got registered. However, when we are trying to update the pack, (by uninstalling the previous pack and reinstalling the cnas pack). The files are not getting rendered properly on the UI, it still showing the older files. You can see the snapshots above |
@amanda11 Thanks for the suggestion. Yes, I gave the parameter with double quotes and tried executing the action. But it failed. |
Ok, so you are using Can also share your |
@cognifloyd Here is the values for the virtualenvs volume and the configs volume: Also, the persistentVolume resource definition outside the chart: |
RWO, or
Are all of you pods on the same node? If not, then only the pods that are on the node with the read/write mount will be able to successfully modify the files. Plus, the read/write mount for virtualenvs and packs could be on different nodes, leading to partially successful pack installs. At a minimum, you need a PVC+PV with |
Good find @cognifloyd 💯 While https://github.com/StackStorm/stackstorm-k8s#method-2-shared-volumes mentions the use of NFS shares as an example (that provide @Bindu-yadav8 could you please create a PR against the https://github.com/StackStorm/stackstorm-k8s#method-2-shared-volumes and mention that somewhere? It would definitely help others. |
@cognifloyd @armab We tried to delete the existing PVC in order to reapply the changes, but the status of PVC is in "terminating" state as shown below: We also tried to check for volume attachments and tried to patch the PVC considering it a fix for the issue but this didn't work. |
@Bindu-yadav8 Do you have a storage class backed by the infrastructure that supports ReadWriteMany? See the table here with different providers: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes |
@armab good catch. |
@armab We are using Azure Disk |
@Bindu-yadav8 as suggested please consider using different Perhaps below could help: |
@armab @cognifloyd Need your assistance in deleting the existing PVC since its in terminating state from long time now. |
Hi @armab @cognifloyd, We have added NFS share for packs, virtual environment and configs. We connected to one of the pods "st2client" and inside the pod, we cloned our custom pack repository. While installing the custom pack we provided the command inside the client pod stackstorm-ha-st2client-pod- st2 pack install file://custompack However, we are seeing the below error: stderr: "st2.actions.python.St2RegisterAction: DEBUG Calling client method "register" with kwargs "{'types': ['all'], 'packs': ['cnas']}" Even when we place the custom pack in the shared NFS location, and did a POST call to Stackstorm API to install the pack, we are seeing the same error. Changes in custom pack are not reflecting in the Web UI. It is still showing the old installations API: POST METHOD- https://api.stackstorm.com/api/v1/packs/#/packs_controller.install.post |
The key piece of that error message is:
Is there a pack.yaml file in /opt/stackstorm/packs/cnas? |
@cognifloyd we had the pack.yaml before issuing the command st2 pack install, after issuing the command we see pack.yaml is not there. |
I see you used |
Yes when I tried to install email pack from stackstorm below error is coming.
|
Yeah, same message with missing pack.yaml. Can you check the content of the |
@armab & @cognifloyd we see default packs in st2api, st2actionrunner & st2 client pods at /opt/stackstorm/packs. But no email or cnas folder there. We see some log like amqp.exceptions.NotFound: Queue.declare: (404) NOT_FOUND - home node 'rabbit@stackstorm-ha-rabbitmq-0.stackstorm-ha-rabbitmq-headless.hasstorm.svc.cluster.local' of durable queue 'st2.preinit' in vhost '/' is down or inaccessible But when we did a curl from client pod to rabitmq endpoint we got rabitmq management page. Please suggest. |
Check the RabbitMQ logs for any errors. Also, could you provide more information about your K8s cluster? |
@armab & @cognifloyd, we checked the RabbitMQ logs & cluster status. Cluster status seems running from all the 3 pods, ping & erlang_cookie_sources listed too. But log in the rabbitmq pods has below errors.
We are using K8s cluster in Azure & kubernetes version is 1.22.6 with 6 nodes of Ubuntu 18.04.6 LTS & kernel version 5.4.0-1089-azure. Please suggest. |
Can you share your rabbitmq helm values? |
@cognifloyd & @armab , We have the following helm values or configurations for Rabbitmq. We had the following values commented. Did uncomment & upgraded the stackstorm deployment. Still same issue pack installation is not progressing.
=========================================================
|
Hi @cognifloyd & @armab, is RabbitMQ helm values fine or any change required, can you please suggest us. |
We have uninstalled one of the custom pack, and reinstalled it by using the command st2 pack install (File path of all the actions, rules, workflows).
By running this command, the files were installed on the K8 cluster. However, On the Stackstorm GUI, the workflows, actions are not rendering properly. The pack is still showing the older actions even after uninstalling the pack.
Uninstalled the custom pack:
Reinstalled the same custom pack:
We are not able to see the new actions on the K8 instance Web UI, and the edit parameters, executions options not visible on the Right Hand side of the Actions tab:
Is this a know issue? How to enable the options on the RHS of the Action Tab?
The text was updated successfully, but these errors were encountered: