phantomjinx commented on PR #3419: URL: https://github.com/apache/camel-k/pull/3419#issuecomment-1181493753
> > The error concering leadership election if another example of a missing API in kubernetes 1.11 (coordination.k8s.io >= 1.14) so represents another example of OCP 3.11's growing incompatibility. > > The TestNativeIntegrations seems to be a consistent failure but many of the runs tend to coincide with the leadership election issue above so difficult to say whether it is a failure of the specific test (ie. flaky test) or the platform. > > I see, but then I wonder why these hadn't been a problem (at least not so much) before we've done that global/namespace separation refactoring on the E2E testing. I'm sure we haven't changed so much on the usages of K8s APIs since then. > > Other than that, I think it's good to go. So, specifically, `TestNativeIntegrations` test has been added recently (30/06). However, I would say it is similar to other existing tests like `TestKitKnativeFullBuild`. Looking back through older test runs, I see a lot of this line: `2022-06-28T09:01:54.9464447Z Warning: the operator will not be able to create Leases. Try installing as cluster-admin to allow management of Lease resources.` [[1]](https://github.com/apache/camel-k/runs/7087685808?check_suite_focus=true#step:7:4127) So the change has been moving some of the tests to running as cluster-admin (`system:admin`), whereas previously these were run as `developer`. Now this could be worked on and its probably the case that most of the tests shouldn't run as cluster-admin, but the operator should be installed as such, which is quite a subtle division that'll need to be carefully worked out. This will , of course, apply to the runs in OCP4 as well, since they are being run as a service-account with cluster-admin privileges. -- 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-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
