Closed tjaeschke closed 6 years ago
Thanks for the detailed report! It would be interesting to know what the YAML looked like at the time of the export, but I guess you don't have that anymore? In any case, this should be relatively simple for me to reproduce ... I'll look into it next week.
@tjaeschke - it was the inputstream loaded with an image that still existed, right
@michaelsauter Unfortunately I don't have the yaml anymore. @clemensutschig In our debug session, yes this has been the problem, but I could reproduce the error with other resources, which remained in the system.
It seems, that the resources have to be absent or they have to be there in total, but not partially.
OK, I know where the error is. oc
fails during the export of a "broken" resource, and Tailor does not detect that properly as https://github.com/opendevstack/tailor/blob/master/openshift/openshift.go#L26 just gets the combined output. I did this to get running quickly, but it's not how oc
works - I need to separate STDOUT and STDERR, as it is already done elsewhere, e.g. at https://github.com/opendevstack/tailor/blob/master/openshift/openshift.go#L124-L130.
I used tailor to create sonarqube in openshift. I forgot to change the secrets in the env file to base64, so the the creation failed in the first run. After changing the secrets to base64 the next tailor update threw the following error:
The same error occured using
tailor status
The resources created by tailor existed partially in Openshift. After a complete cleanup in Openshift it has been possible to run tailor again without this error.