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

st2rulesengine references datastore_crypto_key incorrectly #188

Closed
lordpengwin opened this issue Mar 25, 2021 · 3 comments
Closed

st2rulesengine references datastore_crypto_key incorrectly #188

lordpengwin opened this issue Mar 25, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@lordpengwin
Copy link

lordpengwin commented Mar 25, 2021

I'm seeing a problem where the st2rulesengine is getting hung in the Init:0/2 state and I believe it is waiting for the wrong name. The rest of the entries in the deployments.yaml file have this:

   {{- if .Values.secrets.st2.datastore_crypto_key }}
   - name: st2-encryption-key-vol
     secret:
       secretName: {{ .Release.Name }}-st2-datastore-crypto-key
       items:
       - key: datastore_crypto_key
         path: datastore_key.json
   {{- end }}

where as the rulesengine has this:

   {{- if .Values.secrets.st2.datastore_crypto_key }}
   - name: st2-encryption-key-vol
     secret:
       secretName: datastore_crypto_key
       items:
       - key: datastore_crypto_key
         path: datastore_key.json
   {{- end }}

Note the difference in secretName.

The strange thing is that it works sometimes

@arm4b arm4b added the bug Something isn't working label Mar 26, 2021
@arm4b
Copy link
Member

arm4b commented Mar 26, 2021

Yeah, looks like a bug. Can you please submit a PR to fix this?

@lordpengwin
Copy link
Author

I created a PR for this: #190

Note: I also noticed that -st2sensorcontainer references it differently as the following:

secretName: {{ $.Release.Name }}-st2-datastore-crypto-key

I did not change it because I do not know enough about helm to understand if this is a problem.

@arm4b
Copy link
Member

arm4b commented Jun 1, 2021

Fixed by #190

@arm4b arm4b closed this as completed Jun 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants