databaseSecret not propagated to the workers

[abellotti]

When specifying a custom databaseSecret other than postgresql-secrets, the new name is not
propagated to the workers causing them to fail starting as follows:

Error: secrets "postgresql-secrets" not found

with oc get pods showing the following

NAME                                READY   STATUS                       RESTARTS   AGE
1-event-handler-fcc8d6c9b-hqwhh     0/1     CreateContainerConfigError   0          14m
1-generic-d6764c757-986w2           0/1     CreateContainerConfigError   0          14m
1-generic-d6764c757-pvpsl           0/1     CreateContainerConfigError   0          14m
1-priority-58f8c54c75-9jgsw         0/1     CreateContainerConfigError   0          14m
1-priority-58f8c54c75-swmfr         0/1     CreateContainerConfigError   0          14m
1-remote-console-5dc47474db-gnfx6   0/1     CreateContainerConfigError   0          14m
1-reporting-5755cb5485-4wf9g        0/1     CreateContainerConfigError   0          14m
1-reporting-5755cb5485-vwnhv        0/1     CreateContainerConfigError   0          14m
1-schedule-7d46958887-c56mx         0/1     CreateContainerConfigError   0          14m
1-ui-54fbd7bd87-cdkbp               0/1     CreateContainerConfigError   0          14m
1-web-service-86cd5c895b-snst9      0/1     CreateContainerConfigError   0          14m
httpd-858c5894c7-nwgzq              1/1     Running                      0          19m
memcached-84987cbdf5-xq7kc          1/1     Running                      0          19m
orchestrator-7f4c644df9-vjqg2       1/1     Running                      0          19m
postgresql-7fd4d9b7c6-rqrbs         1/1     Running                      0          19m

[p-v-a]

it's not an issue of the manageiq-pods. These secrets (postgresql-secrets, app-secrets, kafka-secret) are hardcoded in
MIQ itself (ManageIQ/manageiq project):

• lib/container_orchestrator_spec.rb
• lib/container_orchestrator/object_definition.rb

Unless there is way of overwriting it, but I can't see how.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.