You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/06/15 09:03:05 UTC
[GitHub] [camel-k] phantomjinx opened a new issue, #3359: Upgrade can result in integration being rebuilt using the old integrationkit
phantomjinx opened a new issue, #3359:
URL: https://github.com/apache/camel-k/issues/3359
The e2e tests reveal that on occasion, eg. [here](https://github.com/openshift-integration/camel-k-testing-ocp4/runs/6886493035?check_suite_focus=true), an upgade of camel-k can result in an existing being rebuilt with the existing (not-upgraded) integrationkit.
```
1 integrations have been rebuilt
cli_upgrade_test.go:107:
Timed out after 300.020s.
Expected
<string>: kit-cakddkimeh84ri4ora90
to equal
<string>: kit-cakddkimeh84ri4ora8g
```
The problem, of course, is this only happens in the test suite occasionally, so it is difficult to pin-down due to not being a consistent error. Therefore, is this something to warrant enough concern to be investigated?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3359: Upgrade can result in integration being rebuilt using the old integrationkit
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3359:
URL: https://github.com/apache/camel-k/issues/3359#issuecomment-1183097438
Looks good then. FYI, I've noticed that from 1.8 to 1.9 we were suffering rebuilds issues, but the seems to be gone from 1.9 to 1.10(nightly). Was the original reported issue test upgrading from 1.8 to 1.9?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] phantomjinx commented on issue #3359: Upgrade can result in integration being rebuilt using the old integrationkit
Posted by GitBox <gi...@apache.org>.
phantomjinx commented on issue #3359:
URL: https://github.com/apache/camel-k/issues/3359#issuecomment-1305711681
I think this has now been resolved.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3359: Upgrade can result in integration being rebuilt using the old integrationkit
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3359:
URL: https://github.com/apache/camel-k/issues/3359#issuecomment-1183059307
I had a look at this. I did not manage to replicate the issue. Actually it happens that when we do a `kamel rebuild` after a Camel K operator upgrade, the Integration.Status is wiped and a new IntegrationKit build is triggered as well (as the new operator version dependencies are different from the old ones). Which is the method we're using in the E2E tests to ask for a rebuild after an upgrade is performed?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] phantomjinx commented on issue #3359: Upgrade can result in integration being rebuilt using the old integrationkit
Posted by GitBox <gi...@apache.org>.
phantomjinx commented on issue #3359:
URL: https://github.com/apache/camel-k/issues/3359#issuecomment-1183071117
This is where the olm upgrade tests starts the upgrade -> https://github.com/apache/camel-k/blob/main/e2e/namespace/upgrade/olm_upgrade_test.go#L120
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3359: Upgrade can result in integration being rebuilt using the old integrationkit
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3359:
URL: https://github.com/apache/camel-k/issues/3359#issuecomment-1156206604
Interesting... we're talking about same stuff in #3341 I start thinking that the `rebuild` should build from scratch then...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] phantomjinx closed issue #3359: Upgrade can result in integration being rebuilt using the old integrationkit
Posted by GitBox <gi...@apache.org>.
phantomjinx closed issue #3359: Upgrade can result in integration being rebuilt using the old integrationkit
URL: https://github.com/apache/camel-k/issues/3359
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org