text:
make keepalive EnforcementPolicy.MinTime equals keepalive interval

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[x] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hzxuzhonghu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ozevren
If they are not already assigned, you can assign the PR to them by writing /assign @ozevren 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:

galley/OWNERS

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

fixes: #15088

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

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-new-install-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.

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

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-new-install-k8s-presubmit-tests-master

prow/codecov.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-codecov-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.

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

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-new-install-k8s-presubmit-tests-master

prow/codecov.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-codecov-master

prow/integ-mixer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-mixer-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.

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

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-new-install-k8s-presubmit-tests-master

prow/codecov.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-codecov-master

prow/integ-mixer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-multicluster-e2e-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.

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

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-new-install-k8s-presubmit-tests-master

prow/codecov.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-codecov-master

prow/integ-mixer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-multicluster-e2e-master

prow/integ-security-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
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.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hzxuzhonghu, 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:

galley/OWNERS [ozevren]

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

/test istio-codecov-master

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

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-multicluster-e2e-master

prow/integ-security-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-security-k8s-presubmit-tests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-e2e-envoyv2-v1alpha3-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.

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

Test name
Commit
Details
Rerun command

prow/integ-new-installer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-new-install-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-multicluster-e2e-master

prow/integ-security-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-security-k8s-presubmit-tests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/release-test.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test release-test-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.

/retest

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

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-multicluster-e2e-master

prow/integ-security-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-security-k8s-presubmit-tests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/release-test.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test release-test-master

prow/integ-new-installer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-new-install-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.

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

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-multicluster-e2e-master

prow/integ-security-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-security-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-new-install-k8s-presubmit-tests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-e2e-envoyv2-v1alpha3-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.

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-multicluster-e2e-master

prow/integ-security-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-security-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-new-install-k8s-presubmit-tests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-mixer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-mixer-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.

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

Test name
Commit
Details
Rerun command

prow/integ-security-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-security-k8s-presubmit-tests-master

prow/integ-new-installer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-new-install-k8s-presubmit-tests-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-mixer-k8s-presubmit-tests.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
0d08c0442d9c4b2a54062563a74b43bec0c441b5
link
/test istio-pilot-multicluster-e2e-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.

/test istio-pilot-e2e-envoyv2-v1alpha3-master

/cherrypick release-1.3

@rshriram: #15254 failed to apply on top of branch "release-1.3":
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	galley/pkg/server/server.go
Falling back to patching base and 3-way merge...
Auto-merging galley/pkg/server/server.go
CONFLICT (content): Merge conflict in galley/pkg/server/server.go
Patch failed at 0001 make keepalive EnforcementPolicy.MinTime equals keepalive interval

In response to this:

/cherrypick release-1.3

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.

authors: howardjohn hzxuzhonghu istio-testing ozevren rshriram


text:
Remove secret permission from the lesser get, list, watch group [release 1.4 branch]

Please provide a description for what this PR is for: https://github.com/istio/istio/issues/19226

Please submit to master branch and cherrypick to 1.4

Per the comment, https://github.com/istio/istio/pull/19332 is created on the master branch and this PR is closed. After https://github.com/istio/istio/pull/19332 is merged, it will be cherrypicked to release 1.4 branch.

Reopen to merge this PR to the release 1.4 branch: https://github.com/istio/istio/pull/19332 on the master branch can not be cherrypicked to release 1.4 branch through adding the cherrypick/release-1.4 label. There are following merging conflicts after adding the cherrypick/release-1.4 label in https://github.com/istio/istio/pull/19332:
Applying: Fix lint error
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	pilot/pkg/model/push_context.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/pkg/model/push_context.go
CONFLICT (content): Merge conflict in pilot/pkg/model/push_context.go
Patch failed at 0002 Fix lint error

PR lgtm, won't merge until after the security patches land to keep things simpler for our private build

source: gharchive/pull-request

authors: howardjohn lei-tang

repo: istio/istio

license_type: permissive

license_source: github-api


text:
[release-1.5] Integration tests for ingress SDS when the control plane certificate provider is k8s CA

This is an automated cherry-pick of #21090

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio_release-1.5
a586faaae31568655aaed37ec5d527a78c9940c6
link
/test integ-istioio-k8s-tests_istio_release-1.5

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.

/retest

authors: dgn istio-testing


text:
Automator: update istio/api@release-1.5 dependency in istio/istio@release-1.5

Generated by Automator - 2020-05-13T17:54:22+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio_release-1.5
69ea82bca64223ff06cb4a87ffc7d11b9dfd5d4b
link
/test integ-telemetry-k8s-tests_istio_release-1.5

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-telemetry-k8s-tests_istio_release-1.5

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.5
69ea82bca64223ff06cb4a87ffc7d11b9dfd5d4b
link
/test unit-tests_istio_release-1.5

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.

/retest


text:
Add instancesz to debug endpoints

This allows debugging ServinceInstances which is useful if there are
issues with inbound listeners, etc
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

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

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
1366fbbd2173f8c20d28ccff0642c0e618f45f5a
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.

/retest

authors: howardjohn istio-testing


text:
Build on s390x platform

Replaced hardcoded "amd64" with env. variables to enable build on other platforms. Set TARGET_ARCH on s390x platform.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[X] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X] Does not have any changes that may affect Istio users.

Hi @knm3000. 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.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
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.

/ok-to-test

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

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
97e7cbeb3b905809aadb5a8f9117eb3ae4373539
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.

/retest

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

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
97e7cbeb3b905809aadb5a8f9117eb3ae4373539
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.

/retest

authors: brian-avery istio-testing knm3000


text:
[release-1.13] Fix serviceentry endpoint setting order

Please provide a description of this PR:
Manual backport of #38661 and fixes https://github.com/istio/istio/issues/38642

@dhawton: 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.

@dhawton: 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-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_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.

@dhawton: 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-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/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.

@dhawton: 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-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_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.

@dhawton: 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-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/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.

@dhawton: 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-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/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.

@dhawton: 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-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_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.

@dhawton: 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-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_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.

@dhawton: 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-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/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.

@dhawton: 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-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_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.

@dhawton: 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-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_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.

@dhawton: 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

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

integ-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_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.

@dhawton: 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

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

integ-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

integ-pilot-istiodremote-mc_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote-mc_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.

@dhawton: 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

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

integ-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

integ-pilot-istiodremote-mc_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-multicluster_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.

@dhawton: 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

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

integ-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

integ-pilot-istiodremote-mc_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-multicluster_istio

release-test_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-test_istio

integ-distroless_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-distroless_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.

@dhawton: 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

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

integ-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

integ-pilot-istiodremote-mc_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-multicluster_istio

release-test_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-test_istio

integ-distroless_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-distroless_istio

integ-ipv6_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-ipv6_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

integ-pilot-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote_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.

@dhawton: 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

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

integ-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

integ-pilot-istiodremote-mc_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-multicluster_istio

release-test_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-test_istio

integ-distroless_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-distroless_istio

integ-ipv6_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-ipv6_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

integ-pilot-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/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.

@dhawton: 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

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

integ-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

integ-pilot-istiodremote-mc_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-multicluster_istio

release-test_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-test_istio

integ-distroless_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-distroless_istio

integ-ipv6_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-ipv6_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

integ-pilot-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

integ-security_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_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.

@dhawton: 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

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

integ-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

integ-pilot-istiodremote-mc_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-multicluster_istio

release-test_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-test_istio

integ-distroless_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-distroless_istio

integ-ipv6_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-ipv6_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

integ-pilot-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

integ-security_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_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.

@dhawton: 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

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

integ-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

integ-pilot-istiodremote-mc_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-multicluster_istio

release-test_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-test_istio

integ-distroless_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-distroless_istio

integ-ipv6_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-ipv6_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

integ-pilot-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

integ-security_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/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.

@dhawton: 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

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

integ-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

integ-pilot-istiodremote-mc_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-multicluster_istio

release-test_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-test_istio

integ-distroless_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-distroless_istio

integ-ipv6_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-ipv6_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

integ-pilot-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

integ-security_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-cni_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-cni_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.

@dhawton: 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

unit-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test unit-tests_istio

integ-telemetry_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry_istio

integ-telemetry-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-istiodremote_istio

integ-operator-controller_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-operator-controller_istio

integ-pilot_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot_istio

integ-helm_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-helm_istio

integ-pilot-istiodremote-mc_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-multicluster_istio

release-test_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-test_istio

integ-distroless_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-distroless_istio

integ-ipv6_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-ipv6_istio

gencheck_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test gencheck_istio

integ-pilot-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-pilot-istiodremote_istio

lint_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test lint_istio

analyze-tests_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test analyze-tests_istio

integ-security_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security_istio

integ-security-istiodremote_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-istiodremote_istio

integ-security-multicluster_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-security-multicluster_istio

release-notes_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test release-notes_istio

integ-cni_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-cni_istio

integ-telemetry-mc_istio
3cbf08a41f6b3229277f992b94c9d3a512555019
link
true
/test integ-telemetry-mc_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: dhawton istio-testing


text:
add some comments for xds proxy

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

Please check any characteristics that apply to this pull request.

[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@ramaraochavali: 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

release-notes_istio
e6b5b2bea220bbd8e124b03203b4be4cb56eb724
link
true
/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.

/test release-notes_istio

authors: istio-testing ramaraochavali


text:
[WIP]  Implement the server component and the command-line integration for Galley

This PR implements pkg/server and its wiring to the command-line.
BLOCKED ON: https://github.com/istio/istio/pull/6423, https://github.com/istio/istio/pull/6425, https://github.com/istio/istio/pull/6426, https://github.com/istio/istio/pull/6427, https://github.com/istio/istio/pull/6430
Full CL showing how it is used be found here: https://github.com/ozevren/istio/commit/31090e8d1b3bb148c31fe2fdb1889f397a2bc9a6

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: 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:

galley/OWNERS [ozevren]

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

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
edf1d4b2a480d4b0ee96c9bd973fa2a7185a7361
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.

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

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
ef690cf849379be10d78b1887f83fe02b2f4bcb1
link
/test e2e-dashboard

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 APPROVED
This pull-request has been approved by: ayj, 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:

galley/OWNERS [ayj,ozevren]

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

authors: istio-testing ozevren


text:
Regenerate the Citadel templates

This is to resolve doc issues due to missing Citadel yaml files in the released package.
Specifically:

istio-citadel-plugin-certs.yaml
istio-citadel-standalone.yaml
istio-citadel-with-health-check.yaml

The PR adds back the templates and re-generates them upon running the updateVersion.sh so that it will be included in the next release.
Can replace #6961 in fixing #6922.
Fixes https://github.com/istio/istio.github.io/issues/1836

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ymesika
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: andraxylia
Assign the PR to them by writing /assign @andraxylia 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:

install/OWNERS

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

authors: istio-testing ymesika


text:
super basic skeleton test

This is for a couple things:
a) an e2e test (using the e2e framework) that has minimum  dependencies and fast start which can be use as a starting point for new tests that do not rely on bookinfo
b) exercise fortio images, ingress rule svc2sc
c) wip: detect whether auth is working or not
Basic e2e skeleton test

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ee1f41f6f77986dda799e4770ad8db7b2dc2bf68
link
/test istio-presubmit

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.

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
4bb95993473cf0dd31a83a46e1aee31f116cd056
link
/test istio-presubmit

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.

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

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
712e8ebcd9f608d6bbd56b311a1735a776d350c7
link
/test e2e-suite-rbac-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
712e8ebcd9f608d6bbd56b311a1735a776d350c7
link
/test e2e-suite-rbac-no_auth

prow/e2e-suite-rbac-auth.sh
712e8ebcd9f608d6bbd56b311a1735a776d350c7
link
/test e2e-suite-rbac-auth

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.

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: simple-ingress
  annotations:
    kubernetes.io/ingress.class: istio
spec:
  rules:
  - http:
      paths:
      - path: /.* # want /fortio/.*
        backend:
          serviceName: echosrv
          servicePort: http-echo
  - destination: echosrv
    match:
    uri:
        prefix: /fortio
      rewrite:
        uri: /

Can you add more details in the description about what it is testing?

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
c2d96a98206f535d3fabdaecf3e704dbfa4e69c2
link
/test istio-presubmit

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.

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
64cd64925f5a05260b794579031bafd865cd9d07
link
/test istio-presubmit

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.

@sebastienvas is it nice or is it change requested ?

At least on this latest update where I attempted to guess/makeup the rewrite syntax, I got an error in pilot logs (vs silent failure so far) :
W0919 02:37:57.696658       1 controller.go:144] error translating object &crd.RouteRule{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"fortio-redir", GenerateName:"", Namespace:"e2e-test4", SelfLink:"/apis/config.istio.io/v1alpha2/namespaces/e2e-test4/routerules/fortio-redir", UID:"2550b924-9ce2-11e7-a553-42010a8a004e", ResourceVersion:"3180952", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{sec:63641384876, nsec:0, loc:(*time.Location)(0x1f07320)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string{"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"config.istio.io/v1alpha2\",\"kind\":\"RouteRule\",\"metadata\":{\"annotations\":{},\"name\":\"fortio-redir\",\"namespace\":\"e2e-test4\"},\"spec\":{\"destination\":{\"name\":\"echosrv\"},\"match\":{\"request\":{\"headers\":{\"uri\":{\"prefix\":\"/fortio\"}},\"rewrite\":{\"uri\":\"/debug\"}}}}}\n"}, OwnerReferences:[]v1.OwnerReference(nil), Initializers:(*v1.Initializers)(nil), Finalizers:[]string(nil), ClusterName:""}, Spec:map[string]interface {}{"destination":map[interface {}]interface {}{"name":"echosrv"}, "match":map[interface {}]interface {}{"request":map[interface {}]interface {}{"rewrite":map[interface {}]interface {}{"uri":"/debug"}, "headers":map[interface {}]interface {}{"uri":map[interface {}]interface {}{"prefix":"/fortio"}}}}}}
W0919 02:39:01.596632       1 controller.go:144] error translating object &crd.RouteRule{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"fortio-redir", GenerateName:"", Namespace:"e2e-test4", SelfLink:"/apis/config.istio.io/v1alpha2/namespaces/e2e-test4/routerules/fortio-redir", UID:"2550b924-9ce2-11e7-a553-42010a8a004e", ResourceVersion:"3181127", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{sec:63641384876, nsec:0, loc:(*time.Location)(0x1f07320)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string{"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"config.istio.io/v1alpha2\",\"kind\":\"RouteRule\",\"metadata\":{\"annotations\":{},\"name\":\"fortio-redir\",\"namespace\":\"e2e-test4\"},\"spec\":{\"destination\":{\"name\":\"echosrv\"},\"match\":{\"request\":{\"headers\":{\"uri\":{\"prefix\":\"/fortio/(.*)\"}},\"rewrite\":{\"uri\":\"/\\u00261\"}}}}}\n"}, OwnerReferences:[]v1.OwnerReference(nil), Initializers:(*v1.Initializers)(nil), Finalizers:[]string(nil), ClusterName:""}, Spec:map[string]interface {}{"destination":map[interface {}]interface {}{"name":"echosrv"}, "match":map[interface {}]interface {}{"request":map[interface {}]interface {}{"headers":map[interface {}]interface {}{"uri":map[interface {}]interface {}{"prefix":"/fortio/(.*)"}}, "rewrite":map[interface {}]interface {}{"uri":"/&1"}}}}}

cc @kyessenov

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

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
4e3b0d4019583a378a17f983ac39a7b320060161
link
/test e2e-suite-rbac-auth

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.

/retest

Where do you see I'm proposing replacing anything ? this is additive and simpler

Even if this is additive, the question is, why not reuse pilot e2e tests/code ?

There's no downside to having two sets of tests. But it's important to keep e2e tests restricted to the user-facing functionality, as documented on tutorials, and not exhaustive testing, as it affects all Istio development. What is this test for @ldemailly ? If you don't plan to document the behavior on our main docs as a task or a tutorial, then the test does not belong here.

e2e tests are e2e tests, I don't think there is a rule they can only be web site sample as end to end

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
22e8270ced9c0e6c29b5cd2777151bf9cc7560b6
link
/test istio-presubmit

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.

I agree with @ldemailly. In the future we might use a different (lighter) version of the bookinfo like @liamawhite had created before. e2e testing and demo might have different goals.

Sure, but my point is to reuse code from pilot integration tests. Otherwise we have too many variants to maintain

will update and clarify rationale later

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
297f8a67a7c94ca1815568e43a25c911aed6649c
link
/test istio-presubmit

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.

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

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
854d442529ef9a444e067c37255e5c79402ff2f8
link
/test e2e-suite-rbac-no_auth

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.

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

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
854d442529ef9a444e067c37255e5c79402ff2f8
link
/test e2e-suite-rbac-no_auth

prow/e2e-suite-rbac-auth.sh
854d442529ef9a444e067c37255e5c79402ff2f8
link
/test e2e-suite-rbac-auth

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.

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
7495ff93d7705f3e08a2c158aa50ed0d8569455e
link
/test istio-presubmit

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.

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
02f0d9639f8f45436490fd8dc269295b1dc5e437
link
/test istio-presubmit

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.

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
3ccca9b9024595361f7290889cc08f667ba4245e
link
/test istio-presubmit

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.

this is ready now, PTAL

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

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
317417e24640869d402214c4f0863b3b15df62e1
link
/test istio-presubmit

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.

/lgtm

authors: andraxylia douglas-reid istio-testing kyessenov ldemailly rshriram sebastienvas


text:
[DO NOT MERGE] Auto PR to update dependencies of mixerclient

This PR will be merged automatically once checks are successful.

Jenkins job mixerclient/presubmit passed

Jenkins job mixerclient/presubmit passed

Jenkins job mixerclient/presubmit passed

Jenkins job mixerclient/presubmit passed

Jenkins job mixerclient/proxy-regression passed

Jenkins job mixerclient/proxy-regression passed

repo: istio/mixerclient


text:
Support setting the ports in environment variables

Environment variable with highest priority. If not set, same as before.

Thanks @ymesika for this change. This is a useful customization in environments needing better control over the proxy ports.

Can you expand on the use case a bit? I am mostly curious why we only set these 3 ports?
Also why we need env var for stats and admin, which already have a setting in proxy config. AFAIK the readiness port is the same Envoy uses which is also hardcoded, so why does ztunnel have more flexibility than envoy?

I don't think we need overrides for the admin port, but it would make sense to provide the ability to configure the stats port so pilot-agent and ztunnel can co-exist on the same pod, primarily for users relying on the existing istio-dns proxy capability for custom DNS resolution. For this specific scenario, to use the mesh config yaml we'd need 2 separate copies of it with different ports. Having an env var to override the default port seems more flexible at the cost of reduced complexity of needing multiple mesh config files.

I am not sure why having 2 configs for 2 different things is a problem.

I am not sure why having 2 configs for 2 different things is a problem.

It's not a problem, but rather relatively inconvenient compared to updating the env var without needing to maintain multiple config files. If you prefer having 2 separate config files for this scenario, I don't envision needing to configure these ports via env vars.

IMO proxy config is the standard way to configure things in Istio and we have used it here, so we should be consistent.

Closing in favor of having different configs.

authors: howardjohn shashankram ymesika

repo: istio/ztunnel

license_source: bigquery


text:
[Sign up] After signing up the new user is not logged and redirected to main page istead of 'My Space' page

Environment: Windows, Google Chrome 94.0.4606.71
Reproducible: always
Build found: 04.10.2021
Preconditions
Go to Green City https://ita-social-projects.github.io/GreenCityClient/#/
Steps to reproduce

Click on 'Sign-up' button
Set correct values in 'Email' field in the following format: @domain.com
Set correct value in 'User name' field - up to 20 characters
Set correct value in the 'Password' field
Set correct value in 'Confirm password' field
Click 'Sign-up' button
Open the email box you entered in step 2
Open the email with the verification of your email address
Click on 'Підтвердьте свою електронну адресу' button
Actual result
The user is redirected to the main page and not logged in.
https://user-images.githubusercontent.com/91474733/135894360-fbb45c6b-f009-49f9-8423-b3a01dc6ae01.mp4

Expected result
User is successfully redirected to 'My habits' page.
User story and test case links
E.g.: "User story #29, #386, #455"
Labels to be added
"Bug", Priority ("high: "), Severity ("severity: high"), Type ( "Functional")

Verified - done

source: gharchive/issue

repo: ita-social-projects/GreenCity

license: MIT


text:
As a user (any role) I want to view Expert profile on “Expert” page so that I can learn more about certain expert.

User (any role) I want to view information about Expert on “Expert” page.
User (any role) I want to view Expert’s material on “Expert” page.
Experts page content should contain:

Profile section.
Material section.

Expert’s profile:

Author's picture;
First name, last name;
Position;
Topics;
Place of work;
Phone number;
Email;
Info about expert.

Click on topic’s value should redirect to "Topic page" (Direction page).
Material section:

The checkboxes with material types;
Three columns;
Three cards in a row;
"More materials" (Більше матеріалів) button. Button is shown if user has 10 or more materials.
If user has no materials it should be written "У користувача поки що немає матеріалів".

Expert’s material card should contain:

Author's picture, first name, last name, primary place of work.
Material type (article, note, video, course etc.), topic (direction) and title. For articles, notes: preview of material (3 lines). For video: player preview.
Date of adding.
Materials should be sorted by date and time of adding, newest to oldest.

Clicking on "More materials" (Більше матеріалів) should load 6 more materials to section and focus the page on them. After loading last available 1-6 materials button "More materials" should be hidden. And the information "No more new materials" ("Більше нових матеріалів немає") appears.
User should have possibility to filter materials by material type.
Material page should be opened by clicking on material card.
Materials section filtration.
By default section displays all materials with Topic (direction) mentioned. All checkboxes are unmarked by default.
If user chooses material type (article/post etc) materials should be filtered as chosen, the section reloads according to user's request.
In case of a user unmarks all checkboxes the section opens all materials.
in case of according to user's request nothing materials are found open the message with text "Вибачте, за вашим запитом матеріалів не знайдено."
If user clicks on some Topic (direction) in material card we redirect him to Topic (direction) page. Page should be in default state (with no filtration).
if user uses browser instruments “back/forward page” filtration set will be saved at list for one step (better for all).

BA checked

authors: VitaliiKulinskyi dmytrolyakhovenko

repo: ita-social-projects/dokazovi-be


text:
Yet another NPE

Just hit into NPE below yesterday (using commit 3c95089c). Tried today with latest commit from master (f30b9ad9) though it's still here. Output below is from latest version.
What's changed. I did migration to eCryptfs. I stopped kafka-backup, renamed target dir, emptied and chattr +i'd backup sink config (to prevent kafka-backup to be started by Puppet again). Then I deployed eCryptfs changes, did rsync back, then un-chattr +i'd it and reapplied Puppet.
Now main question should we try to debug this at all? Or should I just wipe it and do another fresh backup? This is QA so we have some time in case.
[2020-03-17 02:23:47,321] INFO [Consumer clientId=connector-consumer-chrono_qa-backup-sink-0, groupId=connect-chrono_qa-backup-sink] Setting offset for partition [redacted].chrono-billable-datasink-0 to the committed offset FetchPosition{offset=0, offsetEpoch=Optional.empty, currentLeader=LeaderAndEpoch{leader=kafka5.node:9093 (id: 5 rack: null), epoch=187}} (org.apache.kafka.clients.consumer.internals.ConsumerCoordinator:762)
[2020-03-17 02:23:47,697] ERROR WorkerSinkTask{id=chrono_qa-backup-sink-0} Task threw an uncaught and unrecoverable exception (org.apache.kafka.connect.runtime.WorkerTask:179)
java.lang.NullPointerException
        at de.azapps.kafkabackup.sink.BackupSinkTask.close(BackupSinkTask.java:122)
        at org.apache.kafka.connect.runtime.WorkerSinkTask.commitOffsets(WorkerSinkTask.java:397)
        at org.apache.kafka.connect.runtime.WorkerSinkTask.closePartitions(WorkerSinkTask.java:591)
        at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:196)
        at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:177)
        at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:227)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)
[2020-03-17 02:23:47,705] ERROR WorkerSinkTask{id=chrono_qa-backup-sink-0} Task is being killed and will not recover until manually restarted (org.apache.kafka.connect.runtime.WorkerTask:180)
[2020-03-17 02:23:47,705] INFO Stopped BackupSinkTask (de.azapps.kafkabackup.sink.BackupSinkTask:139)

JFYI, I wiped it out and started with fresh backup. Feel free to close this issue.

Hmm… This is weird… The relevant lines of code are these here: https://github.com/itadventurer/kafka-backup/blob/f30b9ad963c8a7d266c8eacd50bd7c5c3ddbbc16/src/main/java/de/azapps/kafkabackup/sink/BackupSinkTask.java#L121-L122
partitionWriters are filled on the open() call in https://github.com/itadventurer/kafka-backup/blob/f30b9ad963c8a7d266c8eacd50bd7c5c3ddbbc16/src/main/java/de/azapps/kafkabackup/sink/BackupSinkTask.java#L107
Which is called for every TopicPartition to open… It does not make sense to me why this happens :(
Do you have your data still available for further debugging? Would be interesting to try to reproduce. We should at least show a meaningful error instead of just throwing a NPE…

Hi! Yes, I have old directory backup still. Though using it may affect current cluster backup state I guess as I didn't changed sink name..

My guess here is this target dir was broken in some way during eCryptfs enabling attempts. Maybe some file was changed accidentally or something like this.

Hmm… Does it contain sensitive information? If not feel free to upload it to https://send.firefox.com/ and send me a link. I would try to reproduce the error.
Otherwise, you could try to reproduce it with a fresh cluster or we close the issue for now hoping you are right ;)

Happened today on another cluster too...
I have Azure backup cronjob which is stopping kafka-backup, then umounting eCryptfs, then doing azcopy sync, then mounting eCryptfs back and starting kafka-backup.
Tonight umount step failed, so script failed too (set -e). I guess this is time when issue happens. Though I need to recheck timeline carefully. Will update this issue later.

BTW can failed sink cause kafka-connect to exit? It'd be nice if whole standalone connect process will fail in case of single sink failure (when no other sink/connector exists).

BTW can failed sink cause kafka-connect to exit? It'd be nice if whole standalone connect process will fail in case of single sink failure (when no other sink/connector exists).
See #46

UPD. I did logs check just now. NPE happened earlier actually. Kafka-backup was killed by OOM multiple times... It seems -Xmx1024M or Docker memory_limit=1152M is not enough for this cluster :( Any ideas about how to calculate HEAP/RAM size for kafka-backup?

Sorry did miss the update. Feel free to just add another comment ;)
I have no idea how to calculate that right now. Have opened a new ticket #47 for that discussion

Do you want me to do some debugging on this data? I cannot upload it as it's contains company's sensitive data...

Yes please! That would be awesome!

Do you want me to do some debugging on this data? I cannot upload it as it's contains company's sensitive data...

Yes please! That would be awesome!

I'm not skilled in java debugging unfortunately... though I can run something if you guide me on this.

Ok, I will try to think how to do that during the next days maybe I find the issue myself by chance :joy: (want to write more tests)
Maybe if it is possible to reproduce that with non-company data that would be awesome!

According to what I saw here, I'd suggest you to kill kafka-backup process by kill -9 few times. I guess you may get to the state :) I really hope it's not related to eCryptfs...

Hit into this again after few hours of #88 and one OOM..

Saw this tonight on kafka-backup service shutdown before doing Azure blobstore backup:
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: [2020-05-30 19:19:24,572] INFO WorkerSinkTask{id=chrono_prod-backup-sink-0} Committing offsets synchronously using sequence number 2782: {xxx-4=OffsetAndMetadata{offset=911115, leaderEpoch=null, metadata=''}, yyy-5=OffsetAndMetadata{offset=11850053, leaderEpoch=null, metadata=''}, [...]
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: [2020-05-30 19:19:24,622] ERROR WorkerSinkTask{id=chrono_prod-backup-sink-0} Task threw an uncaught and unrecoverable exception (org.apache.kafka.connect.runtime.WorkerTask:179)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: org.apache.kafka.common.errors.WakeupException
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.maybeTriggerWakeup(ConsumerNetworkClient.java:511)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:275)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:233)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:212)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.commitOffsetsSync(ConsumerCoordinator.java:937)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(KafkaConsumer.java:1473)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(KafkaConsumer.java:1431)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.connect.runtime.WorkerSinkTask.doCommitSync(WorkerSinkTask.java:333)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.connect.runtime.WorkerSinkTask.doCommit(WorkerSinkTask.java:361)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.connect.runtime.WorkerSinkTask.commitOffsets(WorkerSinkTask.java:432)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.connect.runtime.WorkerSinkTask.closePartitions(WorkerSinkTask.java:591)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:196)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:177)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:227)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: #011at java.base/java.lang.Thread.run(Unknown Source)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: [2020-05-30 19:19:24,634] ERROR WorkerSinkTask{id=chrono_prod-backup-sink-0} Task is being killed and will not recover until manually restarted (org.apache.kafka.connect.runtime.WorkerTask:180)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: [2020-05-30 19:19:24,733] INFO Stopped BackupSinkTask (de.azapps.kafkabackup.sink.BackupSinkTask:139)
May 30 19:19:24 backupmgrp1 docker/kafka-backup-chrono_prod[16472]: [2020-05-30 19:19:24,771] INFO [Consumer clientId=connector-consumer-chrono_prod-backup-sink-0, groupId=connect-chrono_prod-backup-sink] Revoke previously assigned partitions [...]

:thinking: maybe i should try to reproduce it by letting run Kafka Backup for a few hours and producing a lot of data… need to think about how to debug that in the most meaningful manner…
I think it would help a bit if you could monitor your Kafka Backup setup. Maybe we will see something useful in the metrics :thinking:

I reproduce the same error:
[2020-07-10 11:05:21,755] ERROR WorkerSinkTask{id=backup-sink-0} Task threw an uncaught and unrecoverable exception (org.apache.kafka.connect.runtime.WorkerTask)
java.lang.NullPointerException
	at de.azapps.kafkabackup.sink.BackupSinkTask.close(BackupSinkTask.java:122)
	at org.apache.kafka.connect.runtime.WorkerSinkTask.commitOffsets(WorkerSinkTask.java:397)
	at org.apache.kafka.connect.runtime.WorkerSinkTask.closePartitions(WorkerSinkTask.java:591)
	at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:196)
	at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:177)
	at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:227)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

I am using a pod setup en k8s and Azure File Share filesystem to store the backup. I will try to add some logs at this point.

authors: andresgomezfrr itadventurer jay7x

repo: itadventurer/kafka-backup


text:
[4005] formatoRichiesta mancante

Salve,
Abbiamo notato che nella risposta di una verifica stato 4005 associata ad una richiesta che aveva specificato il parametro

<dettaglioDati>TUTTO</dettaglioDati>

risulta presente solo il campo formatoRisposta e non quello di formatoRichiesta.
Questo significa che basta controllare il valore di formatoRisposta perche anche la richiesta avrà lo stesso formato?
esempio:

<idOperazioneComune>1002SYNC1256630</idOperazioneComune>

Albana Celepija
SmartCommunity Lab
Fondazione Bruno Kessler, Trento

Buongiorno, il problema dovrebbe essere stato individuato e risolto per le future elaborazioni.
Saluti
Assistenza ANPR

authors: AlbanaCelepija mttfranci

repo: italia/anpr


text:
Annullamenti mutazioni famiglia bloccati

Ambiente di produzione, comune di Pesaro
Dobbiamo annullare due mutazioni famiglia 5001 che hanno alterato l'indirizzo di due convivenze. Si tratta delle operazioni ID ANPR 254637418 e 254667738.
Tentando di farlo da webapp veniamo fermati da "L'operazione da annullare non è l'ultima per il soggetto/i o per le famiglie movimentate dall'operazione stessa (Codice: EN077)" (Informazioni sull'operazione da fornire in caso di assistenza : data 2020-06-09 16:51:28 , idOperazioneANPR 263946815 (Codice: EN527))
Potete aiutarci a capire quali sono le operazioni bloccanti ?
Grazie

prima di eliminare l'operazione idanpr 254637418 dovrete eliminare l'operazione idanpr 261137840; prima di eliminare l'operazione idanpr 254667738 dovrete eliminare l'operazione idanpr   260063793.
Fatemi sapere.

Per il caso della 254637418 non riusciamo a risolvere : l'operazione 261137840 non la troviamo nell'elenco utilità->notifiche->monitoraggio operazioni,  per cui non sappiamo di che tipo è e di quale cittadino si tratta, non riuscendo quindi ad annullarla da webapp.
Per il caso della 254667738 invece abbiamo risolto annullando prima la 260063793.

l'operazione idanpr 261137840 è una mutazione di residenza (ws 5005) per il soggetto idanpr 42359988

Purtroppo il soggetto non è più residente a Pesaro e on è possibile annullare quella mutazione.

se vuole possiamo sentirci per cercare una soluzione alternativa.
nel caso mi scriva il suo contatto telefonico al seguente indirizzo frmariani@sogei.it

siamo in contatto telefonico per la risoluzione del problema.

authors: busaster frmariani


text:
Web SERVICE ANPR di PRODUZIONE - Impossibile caricamento stemmi comunali

COMUNE IN SUBENTRO in queste ore: effettuando l'accesso al Web Service ANPR di produzione, successivamente all'area amministrazione per caricare gli stemmi comunali compare la maschera di informazione allegata.
Necessaria URGENTE risoluzione, diversamente da applicativo Anagrafe non sarà possibile effettuare richieste di "certificati ANPR" fino a quando lo stemma di dimnsione 70x70 non sarà caricato nell'area del Web Service del Comune (di circa 12.000 abitanti).
FIORENTINI Alberto per conto COMUNE di MONTECOMPATRI (RM)

Il problema è stato risolto.


text:
Collegamento di codici fiscali diversi di una stessa persona

Buongiorno,
qualche giorno fa abbiamo avuto diversi problemi con un rifugiato che aveva due posizioni aperte presso l'Agenzia delle Entrate (una creata dalla Questura e una dall'Agenzia delle Entrate), e quindi abbiamo dovuto collegare le due posizioni; l'operazione è stata fatta solo con l'aiuto di un operatore di SOGEI (che ha contattato direttamente l'Agenzia delle Entrate).
Ci confermate che dovrebbe essere disponibile un'apposita funzione di ANPR per fare questo tipo di operazioni?
se sì, con che tempi?
Facciamo anche presente che dopo la modifica ci è stato detto che non si possono fare altre operazioni entro le successive 48 ore, e questo provoca un disservizio per la persona: è possibile ovviare a questo problema?
Cordiali saluti
Patrizia Saggini e Monia Pellizzari

Salve. Siamo in contatto con l'Agenzia delle Entrate per trovare una soluzione al problema delle posizioni duplicate che al momento è possibile soltanto se entrambi i codici fiscali sono validati.

Buongiorno,
di nuovo un problema con Agenzia Entrate relativo ai codici fiscali.
Il caso: una persona straniera  iscritta in ANPR cambia il cognome, purtroppo invece che venire allo sportello anagrafe dove possiamo variare il cognome e contestualmente confermare il nuovo CF si reca allo sportello di AE che  gli attribuisce un nuovo CF, ma non riesce a collegarlo al precedente.
Il signore viene ai nostri sportelli per la variazione anagrafica e il rilascio della nuova carta d'identità.
avviamo il procedimento di variazione ma ANPR ci blocca, e a seconda del tipo di "azione" richiesta su cf ci dà i seguenti tipi di errori:
EAM9C: Individuate due posizioni in AT non unificabili
EN230: Attenzione! Sono stati modificati i dati anagrafici del soggetto senza validazione di Agenzia Entrate
EN491:Se il codice fiscale è esistente, non è possibile richiedere una nuova attribuzione
naturalmente non riusciamo a chiudere la variazione di generalità.
allora proviamo da WA:

proviamo con utilità e notifiche, risoluzione disallineamenti con AE: mi propone le due posizioni, confermo quella di AE ma non produce effetti.
allora provo con registrazione - mutazione tutti i dati - generalità  .... salva e chiudi: EAM9C: Individuate due posizioni in AT non unificabili
ritorno su utilità e notifiche e sulla persona esiste una attività in sospeso.
-ritorno su variazione tutti i dati e l'annullo
-ritorno su risoluzione disallineamenti e la posizione con il nuovo cf attribuito da AE è scomparsa!
felice riprovo a variare i dati nel mio WS ... i risultati sono sempre quelli ...
EAM9C: Individuate due posizioni in AT non unificabili
EN230: Attenzione! Sono stati modificati i dati anagrafici del soggetto senza validazione di Agenzia Entrate
EN491:Se il codice fiscale è esistente, non è possibile richiedere una nuova attribuzione.
Che fare? io sono disperata, il cittadino no.
perchè?
perchè io non posso rilasciare la cie o il certificato di residenza
perche lui si ritrova in questa posizione rispetto all'ANAGRAFE TRIBUTARIA:
passaporto e cf nuovi
carta d'identità e cf vecchi
ovvero due identità.
Vorrei capire cosa devo fare.
Grazie
Raffaella
Spinea
0415071155
ps. tra poco ha l'appuntamento in questura per l'aggiornamento del permesso di soggiorno ...
quindi lui sarà regolarmente soggiornante in italia senza una residenza
quadrato il cerchio

authors: Raffive gcarbonin psaggini


text:
[R006] Errore corrispondenza firmatari

Salve,
stiamo provando a far firmare tramite firma autografa dei componenti dell'atto per il caso d'uso Matr_001 senza successo. A quanto pare l'errore restituito indica la mancata corrispondenza di uno o più firmatari della lista. Abbiamo ricontrollato i dati della validazione (correttamente effettuata tramite servizio R009) e i dati inviati al servizio di firma R006 e ci viene restituito:
 400003 : Non è stata trovata corrispondenza per uno o più firmatari nella lista, assicurasi di aver inserito solo i parametri forniti in validazione
Potreste indicarci se ci sono errori o se si tratta di un bug?
idOperazione R009 : 1699737
idOperazione R006: 1699775

Buongiorno stiamo verificando. Appena possibile le faremo sapere

Buongiorno.
Come indicato nel [Changelog(https://github.com/italia/ansc/blob/main/docs/Changelog.md#1152---23-10-2023) della versione 1.15.2, è necessario passare i dati del firmatario indicati in fase di validazione; si prega pertanto di apportare le modifiche al payload e risottomettere la richiesta.
Nel caso di esito positivo vi chiediamo di chiudere la issue.
Grazie.
Supporto ANSC.

Buongiorno abbiamo verificato la richiesta inviata; nello specifico per il servizio R006 di firma dichiarante, avete inviato una anagrafica non completa dei soggetti firmatari. Riporto quanto descritto nel changelog relativo alla versione 1.15.2 del 23-10-2023,
R006 firma dichiarante con lista firmatari: il servizio richiede necessariamente i dati anagrafici  con cui il soggetto è stato registrato (es. se il coniuge è stato registrato con nome, cognome, sesso e data di nascita, questi campi devono essere trasmessi anche nel servizio R006; se l'officiante è stato registrato solo con nome e cognome, il servizio R006 dovrà essere invocato tramsettendo solo nome e cognome)
Si richiede pertanto di riprovare trasmettendo tutti i dati anagrafici dei soggetti firmatari, trasmessi durante la registrazione dell'evento con il servizio R009.

Salve, abbiamo integrato i dati come da voi suggerito, adesso tutto funziona correttamente, chiudo la issue. Grazie mille!

authors: DiBellaDavide amusarra asqueglia

repo: italia/ansc


text:
Remove box shadow when using form-control class

Checklist

[x] Le modifiche sono conformi alle linee guida di design.
[x] Il codice è coerente con le indicazioni di progetto.
[ ] Le modifiche sono state verificate sui Browser supportati e per diverse risoluzioni dello schermo.
[ ] Sono stati effettuati test di accessibilità in ottemperanza a quanto descritto nell'area "Accessibilità" delle linee guida di design.
[ ] La documentazione è stata aggiornata.

Effettivamente non è proprio un caso frequente. Mi è capitato provando a mettere form-control ad una select gestita poi con bootstrap-select.

No problem. Dovrebbe esserci nella versione 1.3.4 appena pubblicata.

authors: francescozaia pdavide

repo: italia/bootstrap-italia