-
Notifications
You must be signed in to change notification settings - Fork 405
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
Add Istio specific assertion in Helm Broker acceptance test #5375
Comments
Increasing timeout for test
The second problem is probably connected with wrong RBAC configuration on helm broker or lack thereof. Sidecar on helm broker should reject the request with 403 status code, instead of this request is passed and code 200(or 404) is returned. The failing test is not deterministic. To fully rule out a istio error after failed test we should check first if When full istio rbac monitoring will be apply turn on |
two things to do in that issue:
|
As mentioned in the above #4409 #531 issues the test We may think about solving this issue globally for all test by implementing istio rule checker in the Octopus for all of the tests: kyma-incubator/octopus#34 I didn't make progress on how to assert istio rules. We should disable this test at this moment because it's failing at
TestServiceBindingUsagePrefixing report after fail can be improved by displaying I created an issue about refactoring the |
The istio RBAC rules sometimes does not work, logs from the Helm-Broker shows calls from the test:
|
I've created a ticket about the Istio problem: #5694 |
Description
Acceptance-test fails with the following error:
Waiting for function failed in given timeout 5s. Function was executed 5 times. Last error: while getting catalog: while getting catalog from broker with URL: http://helm-broker.kyma-system.svc.cluster.local: Status: 404; ErrorMessage: <nil>; Description: <nil>; ResponseError: invalid character 'p' after top-level value
It happens since 19.08 so removing HB from Kyma might be an issue.
The text was updated successfully, but these errors were encountered: