-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
RBAC e2e test is consistently failing #606
Comments
@Brian-Xincheng-Zhang, please find someone to work on this. |
I don't think it is not auth related. assign back to @Brian-Xincheng-Zhang , please try mixer guys. |
I had a chat with Mandar.
|
We have a EngProd oncall now? @sebastienvas |
Yutong, you are the engprod oncall next week:
https://docs.google.com/spreadsheets/d/1FaHwPpad3F3hva2suJweNeTnocjKtLnbgLkyMRPzgUY/edit#gid=0
…-- Brian
On Wed, Aug 30, 2017 at 9:24 PM, Yutong Zhang ***@***.***> wrote:
We have a EngProd oncall now? @sebastienvas
<https://github.com/sebastienvas>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#606 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AdAwSzcyLf6Souc-uyxFW0Bwzlykthwmks5sdjV_gaJpZM4PD6BH>
.
|
This impacts release 0.2.1 |
it's failing all the time, we need to make it pass again and then make it mandatory so it stays passing ps: right now though nothing seems to pass, even non rbac see #653 for one of the causes |
Fixed |
fixed in #711 |
Automatic merge from submit-queue [DO NOT MERGE] Auto PR to update dependencies of proxy This PR will be merged automatically once checks are successful. ```release-note none ```
* Add the istiod SA and Cluster binding. Using kubect apply -k ...cluster will support both istio and istiod in same cluster. * Initial yaml for istiod. For now kustomize only - no need for helm ( we may add a small helm wrapper later) * Initial merging of istiod enablement * Remove old istiod * Fix name * Forgot to add 2 files * Add the settings for SDS/secure token * Fix knative test * Fix the prow kind * Added few comments and remove one more 'values' for istiod
* grpc adapter connection auth. * proto.lock.
* use 1.17 for istio 1.11 and 1.12 * bump regular go version too * backport changes from `Istio 1.12` that fix e2e tests on `Go 1.17` Signed-off-by: Yaroslav Skopets <yaroslav@tetrate.io> Co-authored-by: Yaroslav Skopets <yaroslav@tetrate.io>
…tio#606) * OSSM-742 Improve Maistra container images build (istio#534) * OSSM-742 Improve Maistra container images build * Simplify make rules and Dockerfiles * Fix dockerfiles lint issues * Reorganize files and apply image naming convention * Update MAISTRA_VERSION and ISTIO_VERSION * Adapt images builds relying on upstream build tool * Add copyright and license into scripts
* OSSM-742 Improve Maistra container images build (for maistra-2.3) (istio#606) * OSSM-742 Improve Maistra container images build (istio#534) * OSSM-742 Improve Maistra container images build * Simplify make rules and Dockerfiles * Fix dockerfiles lint issues * Reorganize files and apply image naming convention * Update MAISTRA_VERSION and ISTIO_VERSION * Adapt images builds relying on upstream build tool * Add copyright and license into scripts * chore: updates image labels to reflect actual targeted versions * chore: removes vendor left-overs Co-authored-by: bmangoen <bmangoen@gmail.com>
* OSSM-742 Improve Maistra container images build (for maistra-2.3) (istio#606) * OSSM-742 Improve Maistra container images build (istio#534) * OSSM-742 Improve Maistra container images build * Simplify make rules and Dockerfiles * Fix dockerfiles lint issues * Reorganize files and apply image naming convention * Update MAISTRA_VERSION and ISTIO_VERSION * Adapt images builds relying on upstream build tool * Add copyright and license into scripts * chore: updates image labels to reflect actual targeted versions * chore: removes vendor left-overs Co-authored-by: bmangoen <bmangoen@gmail.com>
The current rbac-no-auth e2e test is currently failing % of the time.
After looking at the logs, the failure seems to be consistenly the mixer test and that the metrics are not being propagated
mixer_test.go:212: Could not find value: value not found for map[string]string{}
mixer_test.go:216: Bad metric value: got 0.000000, want at least 1.000000
The text was updated successfully, but these errors were encountered: