text:
mixerfilter: add protobuf caching

Supersedes https://github.com/istio/istio/pull/11137
Fixes https://github.com/istio/istio/issues/9800
/assign @mandarjog
/assign @douglas-reid
Signed-off-by: Kuat Yessenov kuat@google.com

@kyessenov: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
074d75d1d7d4bb41ff53514007ce7f81f7a00dc8
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
074d75d1d7d4bb41ff53514007ce7f81f7a00dc8
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
074d75d1d7d4bb41ff53514007ce7f81f7a00dc8
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram caching per proxy would lead to a massive cache. It's far better to let the filter decide how to cache. In this case, we compute a cache key from a proxy, and then do a cache lookup.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
074d75d1d7d4bb41ff53514007ce7f81f7a00dc8
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram any reason for precompute not being called? The fallback if config==nil is problematic. It means that suddenly multiple go routines are accessing and updating the structure.

/test istio-unit-tests
There is no concurrent write access issue, since the cache is not written to after precompute.
The cause for missing precompute is somewhere in the mocks, but it's hard to find it.

Friendly ping @douglas-reid @mandarjog .

@kyessenov: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kyessenov PR needs rebase

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: kyessenov
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/test/client/OWNERS [kyessenov]
pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mandarjog @douglas-reid Please take another look.
Recent changes about client retires do not affect this PR. Those changes affect client configs, while this change affects service configs.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests-cni.sh
40a1824f88686330747c19a486f19f0952c9ba36
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
fb916c603b9c250c0ab4e30a3eeb6204a4e916c5
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
40a1824f88686330747c19a486f19f0952c9ba36
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
40a1824f88686330747c19a486f19f0952c9ba36
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kyessenov: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
40a1824f88686330747c19a486f19f0952c9ba36
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
40a1824f88686330747c19a486f19f0952c9ba36
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
40a1824f88686330747c19a486f19f0952c9ba36
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

authors: istio-testing kyessenov mandarjog munrodg


text:
[Test Framework] Fix ready timeout endpoints

This is causing a lot of failures on CI because we're not specifying the timeout, so it's defaulting to 30 seconds (from the retry package).
Fixes #13969

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nmittler, ozevren
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [nmittler,ozevren]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@nmittler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-security-k8s-presubmit-tests.sh
833e18c700067ce31620483e4dca38898dbd2535
link
/test integ-security-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

source: gharchive/pull-request

authors: istio-testing nmittler ozevren

repo: istio/istio

license_type: permissive

license_source: github-api


text:
Extra checks to avoid breaking ingress - which is not yet fully switched

After the merge it appears the Ingress SDS test has become flaky, making sure we enable
only for Sidecar until ingress is migrated.
Ingress uses a node agent as another sidecar.

@istio/wg-security-maintainers ptal, unblocks the repo

authors: costinm howardjohn


text:
Add test to gateway controller

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@Nino-K: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
ed3b53a898b5edf82c787f852666aec2d9763b58
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
ed3b53a898b5edf82c787f852666aec2d9763b58
link
/test lint_istio

gencheck_istio
ed3b53a898b5edf82c787f852666aec2d9763b58
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
ed3b53a898b5edf82c787f852666aec2d9763b58
link
/test lint_istio

gencheck_istio
ed3b53a898b5edf82c787f852666aec2d9763b58
link
/test gencheck_istio

unit-tests_istio
ed3b53a898b5edf82c787f852666aec2d9763b58
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
ed3b53a898b5edf82c787f852666aec2d9763b58
link
/test lint_istio

gencheck_istio
ed3b53a898b5edf82c787f852666aec2d9763b58
link
/test gencheck_istio

unit-tests_istio
ed3b53a898b5edf82c787f852666aec2d9763b58
link
/test unit-tests_istio

integ-mixer-k8s-tests_istio
ed3b53a898b5edf82c787f852666aec2d9763b58
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

authors: Nino-K istio-testing


text:
move bootstrap services to sds

Moves bootstrap services like Metrics Service, Access log Service and Tracing TLS context to use SDS
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
aa19457d9886ce5efce4f17498851f61d769ff7c
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test lint_istio

integ-galley-k8s-tests_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test lint_istio

integ-galley-k8s-tests_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test integ-galley-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test lint_istio

integ-galley-k8s-tests_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test integ-galley-k8s-tests_istio

integ-ipv6-k8s-tests_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test integ-distroless-k8s-tests_istio

integ-galley-k8s-tests_istio
6bc59e59d53bfce11dac9a3df0cd9efb396976ed
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test integ-ipv6-k8s-tests_istio

integ-galley-k8s-tests_istio
6bc59e59d53bfce11dac9a3df0cd9efb396976ed
link
/test integ-galley-k8s-tests_istio

integ-distroless-k8s-tests_istio
6bc59e59d53bfce11dac9a3df0cd9efb396976ed
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
b1ba1095df68acea482e5638f5c68d0c5c932f37
link
/test integ-ipv6-k8s-tests_istio

integ-distroless-k8s-tests_istio
6bc59e59d53bfce11dac9a3df0cd9efb396976ed
link
/test integ-distroless-k8s-tests_istio

unit-tests_istio
c989a50be9f1f0cba5638824c46756a8bb350f95
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
c989a50be9f1f0cba5638824c46756a8bb350f95
link
/test unit-tests_istio

lint_istio
42a570b250d377cef214f7f6cc9f36b52f561fd1
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

authors: istio-testing ramaraochavali


text:
enable locality weighted config when distribute is present

Fixes https://github.com/istio/istio/issues/28942
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

I am wondering should we also protect Distribute locality loadbalancing with OutlierDetection.

I am wondering should we also protect Distribute locality load balancing with OutlierDetection.

Why do you think we need distribute needs outlier detection?

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
cf5db9c3551e84122995ce0eb0b0eb6e21cb16b0
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster-tests_istio

@ramaraochavali https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/locality_weight#locality-weighted-load-balancingc From this doc, the lb weight is adjusted if the any number of  backend endpoints are unhealthy.

@hzxuzhonghu Ok. that makes sense.  So do we want to adjust the user given weights based on outlier detection status?

I think it's a better to have stuff, without that it can also work

My only point about that is user might think his weights are not honoured if he does not specify outlier detection. And if he specifies outlier detection, we can document that it is the Envoy behaviour to recalculate weights.

@hzxuzhonghu @howardjohn Which path should we take here?

I don't think we should require outlier detection for this, there is no need

approved with hold since not sure if @hzxuzhonghu agrees

@ramaraochavali: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
41482318547650fab30d2386cb4d86bb8fa24324
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn Can you please remove the hold?

@howardjohn can you please remove the hold?

@ramaraochavali this appears to have broken the istio.io tests: https://github.com/istio/istio/issues/30181

@ramaraochavali this appears to have broken the istio.io tests: https://github.com/istio/istio/issues/30181

authors: howardjohn hzxuzhonghu istio-testing nmittler ramaraochavali


text:
Revision test flake - remove integration test

Caused flake again. So removing it for now.

@su225: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-multicluster-tests_istio

lint_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-multicluster-tests_istio

lint_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-multicluster-tests_istio

lint_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test lint_istio

integ-helm-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-helm-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-multicluster-tests_istio

lint_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test lint_istio

integ-helm-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-helm-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-multicluster-tests_istio

lint_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test lint_istio

integ-helm-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-helm-tests_istio

analyze-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-multicluster-tests_istio

lint_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test lint_istio

integ-helm-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-helm-tests_istio

analyze-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-multicluster-tests_istio

lint_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test lint_istio

integ-helm-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-helm-tests_istio

analyze-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test analyze-tests_istio

release-notes_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@su225: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-test_istio

unit-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test unit-tests_istio

integ-telemetry-mc-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-mc-k8s-tests_istio

integ-security-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-telemetry-k8s-tests_istio

integ-multicluster-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-multicluster-k8s-tests_istio

integ-distroless-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-distroless-k8s-tests_istio

integ-ipv6-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-ipv6-k8s-tests_istio

integ-pilot-k8s-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-k8s-tests_istio

integ-operator-controller-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-operator-controller-tests_istio

gencheck_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test gencheck_istio

integ-pilot-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-pilot-multicluster-tests_istio

integ-security-multicluster-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-security-multicluster-tests_istio

lint_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test lint_istio

integ-helm-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test integ-helm-tests_istio

analyze-tests_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test analyze-tests_istio

release-notes_istio
3e958b382a8275dba6b496886cf91f46c982212d
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


text:
Create short names for pilot's CRD

Closes: #2650

Hi @jwendell. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Happy to type less :-), but seems like an API issue - do we need to update the api repo/examples ?
Any doc to update ?

Is this some kube thing? Also how do you delineate v1alpha2 route rule? I don’t mind short names. And this short name thing is new to me. We have been using long names everywhere. I think this becomes useful when you use kubectl to do things like kubectl list rr, etc. right ?

@costinm I don't see a doc that explicitly talks about istio resources, for example, teaching a command like kubectl get destinationpolicies. What I see are rare usages of them (for example in https://istio.io/docs/tasks/traffic-management/request-routing.html). I'll open a PR on istio website repo adding a note there.
@rshriram Yes, this is a kube thing. It allows you to type less (eg. kubectl get svc instead of kubectl get services). Indeed, its usage is restrict to CLI commands like kubectl. It's just an alias for the actual resource.
I've updated this PR also adding this short name feature to istioctl binary as well.
Note that not all resources have short names (this is also valid for kubernetes, try kubectl get). If we decide to add short names for more types in the future, it will be easy to do so after this PR is merged.

I like the short names, but it seems like there is a good chance of conflicts, esp with such short names like rr, er, etc. What happens if there are conflicts? If, for example, kubernetes adds a conflicting one in a future release? Will that break our CRD registration during install?

@frankbu I'm not sure about breaking the installation. From what I have tested locally, it seems that the CRD will be installed fine, although things are quite inconsistent in my opinion.
My experiments:

Installed a CRD (DestinationPolicy) with the short name 'svc': Install went ok and kubectl get svc returned services
Changed this CRD short name to 'dp'
Installed another CRD (EgressRule) with the short name 'dp': Install was not so ok. Status reported a conflict in the short name and kubectl get egressrule fails with the message the server doesn't have a resource type "egressrules"
Changed this CRD short name to 'svc'. kubectl get svc returned egress rules!!

This sounds like a bug in k8s for me.
However I don't think this should block us from using short names...

@louiscryan can you make a call
thx

/ok-to-test

deferring to @frankbu

I'm still a little worried about the potential conflicts, but that said, I do like short names, I always use them myself for kube resources (e.g., po, svc, ing ...).
I wonder if we should defer this until we switch to the new routing model, since the resources are different - which would also suggest different short names. For example, in the new model: RouteRule -> VirtualService, EgressRule -> ExternalService, and DestinationPolicy -> DestinationRule.

I defer to Frank on this too :)
On Wed, Feb 28, 2018 at 8:11 AM Frank Budinsky notifications@github.com
wrote:

I'm still a little worried about the potential conflicts, but that said, I
do like short names, I always use them myself for kube resources (e.g., po,
svc, ing ...).
I wonder if we should defer this until we switch to the new routing model,
since the resources are different - which would also suggest different
short names. For example, in the new model: RouteRule -> VirtualService,
EgressRule -> ExternalService, and DestinationPolicy -> DestinationRule.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/3394#issuecomment-369287236, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIoKPA-LhInHkEQfiRVsMEnuWTkKBqGiks5tZXkIgaJpZM4SA_M1
.

authors: costinm frankbu istio-testing jwendell ldemailly louiscryan rshriram


text:
Fix demo profile doc test

Please provide a description of this PR:
After adding Jaeger (https://github.com/istio/istio.io/pull/12892) to the test, the test still failed. envoyOtelAls  and opentelemetry tracing were sharing the same name otel, however they should be unique.
/cc @zirain

@istio/wg-docs-maintainers-english PTAL


text:
WIP: DEBUG

Please provide a description of this PR:

@kfaseela This also passed, it is very unexpected

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
45ade620d9c278cd59a429904e37d1163c5942a4
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
45ade620d9c278cd59a429904e37d1163c5942a4
link
true
/test integ-cni

integ-pilot_istio
45ade620d9c278cd59a429904e37d1163c5942a4
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@kfaseela look at the second commit, if i setup a delay the test failed

authors: hzxuzhonghu istio-testing


text:
Golinter

Create a golinter which applies customized linting rules to unit, integration, and e2e tests.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: JimmyCYJ
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@JimmyCYJ: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
e8e7929a86bf46d1f96cb8cf5815450f18356542
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test e2e-simple

prow/e2e-bookInfoTests-v1alpha3.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test e2e-simple

prow/e2e-bookInfoTests-v1alpha3.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-bookInfo
/test e2e-simple
/test e2e-bookInfo-envoyv2-v1alpha3
/test istio-pilot-e2e

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
08fb866d1179a747b06fb51ca853f738a2595553
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Yes, I specifically disagree with the proposal on integration tests (which
are most common and useful form of test we have).
So far all the tests we have are running out of the box - and do not appear
to be slow compared with the prow tests for example.
On Thu, May 31, 2018 at 10:13 AM, Andy Lai notifications@github.com wrote:

@hklai commented on this pull request.
In tests/util/golinter/README.md
https://github.com/istio/istio/pull/5887#discussion_r192172421:

+This golinter checks if our test files follow customerized lint rules.

+# Unit tests rules.
+## File name requirement.
+Unit tests should stay in file with suffix "_test.go".
+## Forbidden function calls.
+Unit tests should not contain any of these function calls.
+bash +testing.Short() +time.Sleep() +goroutine +
+
+# Integration tests
+## File name requirement
+Integration tests should stay in file with suffix "_integ.go" in any directory, or file with suffix "_integ.go"/"_test.go" but under a directory named "integ".
@costinm https://github.com/costinm "why would we use different files?"
I am not sure what you mean here.
The convention we are proposing should be non intrusive for most tests
files.
i.e. unit tests with _test.go suffix can exist in any packages. e2e tests
are in dedicated packages.
The only questionable ones are the integration tests that look like unit
tests which may not always run out of the box. And that is exactly what we
are trying to address here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/5887#discussion_r192172421, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFI6hzvOIQ6uo7WU_y-DNGVzX8wmuz4ks5t4CTLgaJpZM4UR4am
.

@JimmyCYJ: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
e21a24763071465fd7d06bf58e68e4f01846202c
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
5e970b9ee001aaef9caa32fe852aa1cea234d9cb
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-simple

prow/e2e-bookInfoTests-v1alpha3.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-simple

prow/e2e-bookInfoTests-v1alpha3.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: JimmyCYJ
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: zackbutcher
Assign the PR to them by writing /assign @zackbutcher in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-simple

prow/e2e-bookInfoTests-v1alpha3.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
dd32f17fc366d8fc71ae052800317bd9ec55be4e
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-simple

prow/e2e-bookInfoTests-v1alpha3.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
dd32f17fc366d8fc71ae052800317bd9ec55be4e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
dd32f17fc366d8fc71ae052800317bd9ec55be4e
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test e2e-simple

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
dd32f17fc366d8fc71ae052800317bd9ec55be4e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
dd32f17fc366d8fc71ae052800317bd9ec55be4e
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
dd32f17fc366d8fc71ae052800317bd9ec55be4e
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@JimmyCYJ: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
adb19b572c9539dd3d6881c1f8f690887d86de0f
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
dd32f17fc366d8fc71ae052800317bd9ec55be4e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
dd32f17fc366d8fc71ae052800317bd9ec55be4e
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
dd32f17fc366d8fc71ae052800317bd9ec55be4e
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
dd32f17fc366d8fc71ae052800317bd9ec55be4e
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Created https://github.com/istio/istio/pull/6039

authors: JimmyCYJ costinm istio-testing


text:
Push images to docker hub

Currently, GCR is used to store docker images after successful merges.  We should transition to docker hub and an istio org for this purpose.

Closing. currently Jenkins is pushing to docker hub.

source: gharchive/issue

repo: istio/mixer


text:
Add repositories.bzl to remove boilerplate in BUILD files

Closes #99

This change is

@lizan

This makes you update the workspace file locally; which I was trying to avoid.
I don't like the literal string as buildfile;  I have an alternative that is equivalent from a user's standpoint, but does not do the literal string.

It is the minimal change to avoid changing each BUILD file, another
approach is add a load statement to each BUILD. go_library doesn't work
without any source, so a dummy go_library target didn't work.

What is the equivalent? It is the easiest way to avoid copying BUILD
files around, especially when we have a repo (likely istio/istio) depends
on mixer, you don't have to copy BUILD for mixer dependencies to that repo.

On Dec 22, 2016 12:50 PM, "mandarjog" notifications@github.com wrote:

@lizan https://github.com/lizan

This makes you update the workspace file locally; which I was
trying to avoid.
I don't like the literal string as buildfile; I have an alternative
that is equivalent from a user's standpoint, but does not do the literal
string.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/mixer/pull/101#issuecomment-268887707, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA-A7yL7259inb2aGmdEvg-ezzqXyli3ks5rKuKJgaJpZM4LUVZs
.

So is the issue here you want to avoid pushing changes to api repo before trying them out in mixer?
Let's use gazella to automate BUILD file generations. Then if you use go tool, you can directly edit $GOROOT/.../api repo. If you use bazel, then there is a repo in /external/ that you can edit and Bazel accepts. What am I missing?

iiuc, the issue is not wanting to edit the repo in /external/.

authors: douglas-reid kyessenov lizan mandarjog


text:
Fix rbac issue

add namespace to work

@richardwxn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_operator
9a922af8465acdabe9334ca3e8066cbbbc0675d4
link
/test gencheck_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

The namespaces are not redundant.  Please add the istio-operator namespace to all objects in the repo.  See PR https://github.com/istio/istio.io/pull/5142 for why this is necessary.
Cheers
-steve

@richardwxn service.yaml also in need of a namespace.

subsumed by: https://github.com/istio/operator/pull/374

@richardwxn I can handle expanding RBAC for the operator here: https://github.com/istio/istio/issues/17841.  If you still suffer from a PDB issue, please paste the log message here or message to me on slack and I'll take a look.  If your satisfied with https://github.com/istio/operator/pull/374 - please close this issue and leave a comment.
Cheers
-steve

@sdake thanks for the clarification! I am closing this PR now as yours was merged already. I would send the error log to you on slack tmr.

authors: istio-testing richardwxn sdake

repo: istio/operator

license_source: bigquery


text:
Complete ingress controller separation

Split TPR controller into TPR and ingress stores using the aggregate controller.

you have to trust me that presubmit tests passed locally on my machine ;)

Jenkins job pilot/presubmit passed

authors: istio-testing kyessenov

repo: istio/pilot


text:
mysql同步到mysql,自定义函数报错

Branch name (分支名)
main
Bug description (缺陷描述)
自定义函数失效 mysql to mysql
to_chinese_date()

分区为空异常

repo: isxcode/spark-yun


text:
Design für "Warnungen in der Zuweisung"

Als örtliche Ausbildungsleitung möchte ich Warnungen erhalten falls Unstimmigkeiten bei der Zuweisung entstanden sind, damit ich die Anforderungen der gemeldeten Praktikumsstellen richtig erfülle.
Issue #137

Akzeptanzkriterien aus Ursprungs-Issue zur Info:

[x] Die Warnungen werden beim Versuch der Durchführung der Aktion angezeigt.
[x] Die Aktion soll erst dann durchgeführt werden, wenn alle Warnungen bestätigt worden sind.
Es wird eine Warnung angezeigt, wenn Praktikumsplätze, mit Dringlichkeit Zwingend und Dringend, nicht mit einer NWK besetzt sind
Es wird eine Warnung angezeigt, wenn Praktikumsplätze, mit namentlicher Anforderung unbesetzt sind
Es wird eine Warnung angezeigt, wenn NWKs noch nicht einem Praktikumsplatz zugewiesen sind
--> Die letzten drei Punkte sind für das Design in diesem Issue nicht wichtig; wird beim Mailversand wichtig

Zusätzliche Infos (z.B. aus Refinement):
Bei folgenden Aktionen sollen die Warnungen aktuell erscheinen:

Export der Zuweisungstabelle, Mail-Versand erfolgreiche Zuweisung
Es soll für jede NWK eine eigene Warnung erscheinen
Jede Warnung soll einzeln angezeigt werden
--> Diese drei Punkte sind für das Design in diesem Issue nicht wichtig; wird beim Mailversand wichtig

Design-Akzeptanzkriterien:

[x] Review des Designs durch Andi
[ ] Feedback aus Review wurde eingebaut
[ ] Link zum gereviewten Design wurde Developern zur Verfügung gestellt

https://www.figma.com/file/8nfnnZeFlFYMdiuGA0ZhMQ/Zuweisung?type=design&node-id=75%3A1488&mode=design&t=6h0HTzWeSTlk4rd9-1

authors: TobiasCersowsky andingerMUC

repo: it-at-m/Praktikumsplaner

license: MIT


text:
[Profile Moderation] Add icon on the banner/logo if profile is in 'Pending Moderation' status

As a profile owner, I want to see the icon on the fields under moderation so I clearly understand when my changes are visible for all users
Acceptance criteria:

IF profile status = 'Pending Moderation' THEN show the icon on the banner and/or logo (depending on which field was updated)
Show the tooltip by hovering on 'Pending Moderation' icon:
2.1. Статус модерації: Очікується
2.2. Час відправки запиту: <dd.MM.yyyy hh:mm>

Affected Areas:
- Main Page, if company is shown there
- Companies List
- Company Profile (View mode)
- Company Profile (Edit mode)
DESIGN: https://www.figma.com/design/gMu88CJcuaJSSoTGC5ZYfD/Forum?node-id=4936-69617
EPIC: #615

Actual design: tooltip on both - banner and logo

authors: MissMS alona-ruda

repo: ita-social-projects/Forum


text:
[API][Edit profile] Status code 201 is the wrong response got when data is updated in the personal cabinet

Environment: all.
Reproducible: always.
Build found: 01.07.22
Preconditions
1.Postman is opened
2.POST greencity-user.testgreencity.ga/ownSecurity/signIn
Body:
{
"email": "хххххх",
"password": "ххххх"
}
3. User has data in the personal cabinet
Steps to reproduce

Make method PUT greencity-ubs.testgreencity.ga/ubs/userProfile/user/update
{
"addressDto": [
{
"actual": true,
"addressComment": "string",
"city": "string",
"cityEn": "string",
"coordinates": {
"latitude": 0,
"longitude": 0
},
"district": "string",
"districtEn": "string",
"entranceNumber": "string",
"houseCorpus": "string",
"houseNumber": "string",
"id": 0,
"region": "string",
"regionEn": "string",
"street": "string",
"streetEn": "string"
}
],
"alternateEmail": "string",
"recipientName": "string",
"recipientPhone": "string",
"recipientSurname": "string"
}
Edit data with valid data and send request

Actual result

Response 201 (Created) status code

Expected result

Response 204 (No Content) status code

User story and test case links
E.g.: "User story #3811
Test case"

I am afraid, that it is not a relevant task. In this controller we return status code 200 OK (not 201 Created) that signifies that data is successfully updated. We also return not only response but updated user data. If we change response to 204 (No Content) status code then the controller should not to return anything.

authors: TaniaIvashkiv innayashna

repo: ita-social-projects/GreenCity


text:
[Order form] Not correct notification after changing the conditions for the order

Environment: Firefox 114.0.2 (64-bit)
Windows 11 IoT Enterprise, version 22H2
Reproducible: always
Preconditions
Through the admin account, change the minimum number of packages to the minimum amount of payment (500 UAH) for Kharkiv and Kharkiv region.
Steps to reproduce

Go to https://www.greencity.social/#/ubs
Click to order
Choose Kharkiv and Kharkiv region.

Actual result
Not correct notification -  "The minimum order amount must be 500 UAH
Please note that the minimum order must contain at least 500 packages of 120l"
Expected result
Correct notification - "The minimum order amount must be 500 UAH"

Labels to be added
"Bug", Priority ("pri: "), Severity ("severity:"), Type ("UI, "Functional"), "API" (for back-end bugs).

I checked on test and local databases and everything works fine.


text:
[UBS] Wrong text on the pop-up for choosing the address.

Environment:

Lenovo YOGA Slim 7, Windows 10 Pro, екран 1920 x 1080 пікселей,
Chrome Версія 128.0.6613.120;
Redmi Note 13 Pro 5G, Android 13TKQ1.221114.001, екран 2712 x 1220 пікселей, Chrome Версія 128.0.6613.100

Reproducible: always
Build found: commit 1b0a935da50883f70eac5f975674e5de1ba5790d
Preconditions
Login as a User on the https://www.pick-up.city/#/ubs
Steps to reproduce

Go to the Main page
Click on the button "Замовити".

Actual result
Text on the pop-up: "Вітаємо в УБС! Спочатку оберіть локацію вивезення відходів. Наразі ми працюємо тільки по м. Київ та обраних містах."

Expected result
Text on the pop-up: "Вітаємо в УБС! Оберіть локацію вивезення відходів. Наразі ми працюємо тільки в м. Києві та передмістті столиці в радіусі 20 км."
Postconditions
_
User story and test case links
User story #5192, #2924

Fixed

@kryzanivska-nastya Sorry, i didn't correct the customer's mistake in the word “передмісті” - there should be 1 letter “т”
Please fix it

It was updated:

authors: kryzanivska-nastya volo-amare


text:
[Search page] The inconsistent pagination appears when searching for a workshop

Environment: Win10 v21H2 64-bit, Chrome v 98.0.4758.82
Reproducible: always
Build found: frontend: gcp-0.0.53, backend: gcp-0.0.112
Preconditions

Go to OoS (https://oos.dmytrominochkin.cloud/#/)
Log into system as Parent (e.g. 'Email'="dub@gmail.com", 'Password'="Qwert1!")
"Київ" region is selected
Go to the main page and click ‘Найпопулярніші гуртки’ hyperlink

Steps to reproduce

Set ‘танці’ in the search field
Click ‘Search’ button

Actual result
The 10 workshops are found, the pagination is broken – no workshop cards are displayed on pages 3-9

Expected result
There are 2 pages with workshop cards
User story and test case links
User story #23
Test case OS-260
Labels to be added
"Bug", "pri: low", "severity: minor", Type "UI"

seems it was a backend issue. Now it works as expected.

Verified and closed

authors: hanna-lenko perepichai

repo: ita-social-projects/OoS-Frontend


text:
Fix responsiveness of the Main View page

Summary of issue
Fixed problems with responsive design on laptop screens.
Left and right gap was added.
Materials cards in a grid list now have horizontal scroll on small screens (~11 inches laptops and iPads). 13 inches displays fit 4 items

wrong base branch

repo: ita-social-projects/dokazovi-fe


text:
add ID to DB/orders & serch order by ID

add ID to DB/orders & serch order by ID

Also, add permissions for getting order by user , please

authors: AndriyLymych sergklukvin


text:
Emigrazione in comune non subentrato - errore bloccante -

Comune di Valle Mosso  (BI)  096073 - produzione dal 3/11/2017
Ho gia' inviato una mail alla sig.a Carbonin in data di ieri ma non ho avuto la conferma di lettura per cui ripropongo il problema qui.
"Le scrivo per verificare un problema che e' sorto nel tentativo di effettuare una cancellazione per emigrazione verso un Comune non subentrato di una persona iscritta in anpr
La persona ha l'id  19025577  ed emigra verso un comune non subentrato
All'invio dati si riceve un errore bloccante:  Operazione  2003 - cancellazione per altri motivi
errore  EN203  E-errore bloccante  -  Operazione non effettuabile - esiste un'operazione sospesa per il soggetto.
Ho verificato ma non riesco a trovare alcuna operazione sospesa, non solo per il soggetto ma in generale per tutto il comune.
La persona ha avuto, dopo il subentro, il cambio di cognome   con relativo cambio di CF ma l'operazione e' andata a buon fine senza alcun intoppo.
Mi faccia sapere come procedere dal momento che la pratica non e' perfezionabile."

Mi scuso ma la sua mail mi era sfuggita ora controlliamo

Risolto telefonicamente con il comune

repo: italia/anpr