-
Notifications
You must be signed in to change notification settings - Fork 345
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
Cannot upgrade from 1.8.x to 1.9.0-SNAPSHOT #3063
Comments
A migration path during the installation of the embedded catalog must be performed to address #2987. |
I upgraded 1.9.0-SNAPSHOT's build to 0.7.1 catalog release and that installed correctly. |
phantomjinx
added a commit
to phantomjinx/camel-k
that referenced
this issue
Mar 3, 2022
* Reassigning sync.Once causes unlocking of unlocked mutex error and recommended should not be done inside the function called by the sync.Once * Instead log the error and bail out as something is wrong with the kamelets and needs to be fixed. * Upgrades the kamelet branch to load compatible kamelets, ie. those that define with spec.template rather than spec.flow
Closed
phantomjinx
added a commit
to phantomjinx/camel-k
that referenced
this issue
Mar 3, 2022
* Reassigning sync.Once causes unlocking of unlocked mutex error and recommended should not be done inside the function called by the sync.Once * Instead log the error and bail out as something is wrong with the kamelets and needs to be fixed. * Upgrades the kamelet branch to load compatible kamelets, ie. those that define with spec.template rather than spec.flow
phantomjinx
added a commit
to phantomjinx/camel-k
that referenced
this issue
Mar 3, 2022
* Reassigning sync.Once causes unlocking of unlocked mutex error and recommended should not be done inside the function called by the sync.Once * Instead log the error and bail out as something is wrong with the kamelets and needs to be fixed. * Upgrades the kamelet branch to load compatible kamelets, ie. those that define with spec.template rather than spec.flow
phantomjinx
added a commit
to phantomjinx/camel-k
that referenced
this issue
Mar 3, 2022
* Reassigning sync.Once causes unlocking of unlocked mutex error and recommended should not be done inside the function called by the sync.Once * Instead log the error and bail out as something is wrong with the kamelets and needs to be fixed. * Upgrades the kamelet branch to load compatible kamelets, ie. those that define with spec.template rather than spec.flow
phantomjinx
added a commit
to phantomjinx/camel-k
that referenced
this issue
Mar 3, 2022
* Reassigning sync.Once causes unlocking of unlocked mutex error and recommended should not be done inside the function called by the sync.Once * Instead log the error and bail out as something is wrong with the kamelets and needs to be fixed. * Upgrades the kamelet branch to load compatible kamelets, ie. those that define with spec.template rather than spec.flow
Fixed with #3078 |
phantomjinx
added a commit
to phantomjinx/camel-k
that referenced
this issue
Mar 7, 2022
* Reassigning sync.Once causes unlocking of unlocked mutex error and recommended should not be done inside the function called by the sync.Once * Instead log the error and bail out as something is wrong with the kamelets and needs to be fixed. * Upgrades the kamelet branch to load compatible kamelets, ie. those that define with spec.template rather than spec.flow
phantomjinx
added a commit
to phantomjinx/camel-k
that referenced
this issue
Mar 11, 2022
* Reassigning sync.Once causes unlocking of unlocked mutex error and recommended should not be done inside the function called by the sync.Once * Instead log the error and bail out as something is wrong with the kamelets and needs to be fixed. * Upgrades the kamelet branch to load compatible kamelets, ie. those that define with spec.template rather than spec.flow
phantomjinx
added a commit
to phantomjinx/camel-k
that referenced
this issue
Mar 25, 2022
* Reassigning sync.Once causes unlocking of unlocked mutex error and recommended should not be done inside the function called by the sync.Once * Instead log the error and bail out as something is wrong with the kamelets and needs to be fixed. * Upgrades the kamelet branch to load compatible kamelets, ie. those that define with spec.template rather than spec.flow
phantomjinx
added a commit
to phantomjinx/camel-k
that referenced
this issue
Apr 11, 2022
* Reassigning sync.Once causes unlocking of unlocked mutex error and recommended should not be done inside the function called by the sync.Once * Instead log the error and bail out as something is wrong with the kamelets and needs to be fixed. * Upgrades the kamelet branch to load compatible kamelets, ie. those that define with spec.template rather than spec.flow
squakez
pushed a commit
that referenced
this issue
Apr 18, 2022
* Reassigning sync.Once causes unlocking of unlocked mutex error and recommended should not be done inside the function called by the sync.Once * Instead log the error and bail out as something is wrong with the kamelets and needs to be fixed. * Upgrades the kamelet branch to load compatible kamelets, ie. those that define with spec.template rather than spec.flow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During upgrade tests, the 1.9.0-SNAPSHOT operator is installed in a 1.8.1 namespace but crashes on spin-up.
The log of the operator reveals the following:
Suggestion seems to be that the change in kamelet syntax is to blame (see #2987).
The text was updated successfully, but these errors were encountered: