knockknock10 commented on issue #6943:
URL: https://github.com/apache/camel-k/issues/6943#issuecomment-6721250352
> I think it could be the expected behavior. Can you provide more details,
for example, what kind of error it was?
Thanks for taking a look.
I reproduced this using a fake-client interceptor in the test. It intercepts
the Deployment `Update` operation and returns `errors.New("simulated deployment
update failure")` whenever a Deployment is being updated.
The test then verifies that:
- `Apply()` returns the simulated Deployment update error.
- The previous generation's Deployment has still been deleted.
I've attached two screenshots:
- One showing the injected Deployment update failure and the test result.
- Another showing the clean test execution.
Just to clarify, this is a simulated failure through the fake client, not a
specific error returned by a Kubernetes API server, such as a conflict or
forbidden response.
I wanted to check whether continuing with GC in this situation is
intentional, even when applying the new Deployment fails.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
