jupyter-notebook fails to deploy if secret is already available

[alistairlenhard]

jupyter-notebook fails to deploy if secret is already available

[henrjk]

My understanding is that tailor is used to create/update the secrets in this case (at

ods-project-quickstarters/ocp-templates/scripts/create-rshiny-app.sh

Line 101 in 7ceaa8c

tailor_update_in_dir "${OCP_CONFIG}/rshiny-app" \

)

So it seems tailor creates the secret - which it would do if it can't find the secret yet - and then is told that it already exists.

@michaelsauter could this be some permission issue? Do you have some other thoughts on what might go wrong?

[michaelsauter]

@henrjk Just looking at it with @gerardcl. The issue is the scope: if you tell Tailor to only look at resources with a certain label, then it will not look at resources without that label. Consequently Tailor thinks that it needs to create the resource because it does not "see" it in the platform. BUT if it then executes oc create, the created resource might already exist (because for resource identity, only the name matters, not the labels).

[alistairlenhard]

just another hint: if I remove the secret, rundeck seems to progress further. So my project on dev seems to be created on openshift. Now the same error would appear on [project]-test.
Do you know when the bitbucket resources are filled in this process? Currently it seems like they remain empty until both openshift dev and test are created and only then the code is pushed? I am saying this because the login to the jupyter notebook on openshift now also does not work and it does not really seem to have all sources on openshift yet for dev.

[henrjk]

@alistairlenhard The secrets that have been created originally: did they come from a quickstarter created with a prior ODS release?

Perhaps the label should be removed for the secrets?

[gerardcl]

hi @henrjk I confirm that jupyter was before 1.2.x