Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unable to upgrade using operator - upgrade pod - pod has unbound PersistentVolumeClaims
See original GitHub issueThis is a…
[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report
[ ] Documentation issue or request
Description
I tried to upgrade from “1.4.9” to “latest” (because currently there is still hardcoded “latest” upgrade pod in operator image #3924).
Then I tried from “1.5.5” to “latest” with the same result - upgrade pod won’t start because of this:
There is also this error in the operator log:
time="2018-11-01T11:58:12Z" level=error msg="error syncing key (myproject/app): object is being deleted: persistentvolumeclaims \"syndesis-upgrade\" already exists"
steps to reproduce: ./syndesis install -s ./syndesis install --project myproject --tag 1.4.9 wait for syndesis to install deploy new operator image, for example 1.5.6 version
minishift v1.26.1+1e20f27 openshift 3.10
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
fixed in CR2 prod build
@avano Yes, makes sense.