Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adding istion annotation (#3534) #3557

Merged
merged 5 commits into from
Jul 12, 2020
Merged

adding istion annotation (#3534) #3557

merged 5 commits into from
Jul 12, 2020

Conversation

vayyappaneni
Copy link
Contributor

@vayyappaneni vayyappaneni commented Jul 9, 2020

Fixes #3532
backport #3534
backport #3542
backport #3543
backport #3539

Proposed Changes

  • Fixing issue where jobs do not complete on istio enabled cluster

Release Note

Fixes issue where migration jobs would fail on Istio cluster with auto-inject enabled

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Jul 9, 2020
@knative-prow-robot knative-prow-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jul 9, 2020
@knative-prow-robot knative-prow-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jul 9, 2020
@knative-prow-robot
Copy link
Contributor

Hi @vayyappaneni. Thanks for your PR.

I'm waiting for a knative 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.

@vayyappaneni
Copy link
Contributor Author

/assign @markusthoemmes

@AceHack
Copy link
Contributor

AceHack commented Jul 9, 2020

/ok-to-test

@knative-prow-robot knative-prow-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 9, 2020
@vayyappaneni
Copy link
Contributor Author

/test pull-knative-eventing-upgrade-tests

1 similar comment
@AceHack
Copy link
Contributor

AceHack commented Jul 9, 2020

/test pull-knative-eventing-upgrade-tests

@AceHack
Copy link
Contributor

AceHack commented Jul 9, 2020

/test pull-knative-eventing-integration-tests

@AceHack
Copy link
Contributor

AceHack commented Jul 9, 2020

/test pull-knative-eventing-upgrade-tests

1 similar comment
@AceHack
Copy link
Contributor

AceHack commented Jul 9, 2020

/test pull-knative-eventing-upgrade-tests

@pierDipi
Copy link
Member

You might want to backport this one first: #3543.

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@knative-prow-robot knative-prow-robot added the area/test-and-release Test infrastructure, tests or release label Jul 10, 2020
@googlebot googlebot added cla: no Indicates the PR's author has not signed the CLA. and removed cla: yes Indicates the PR's author has signed the CLA. labels Jul 10, 2020
@vayyappaneni
Copy link
Contributor Author

vayyappaneni commented Jul 10, 2020

@googlebot I fixed it.

@vayyappaneni
Copy link
Contributor Author

@markusthoemmes @pierDipi @vaikas
I did sign the CLA fews days ago. I am not sure what happen here it is complaining about of CLA . This is what google bot said: #3557 (comment)

@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: yes Indicates the PR's author has signed the CLA. and removed cla: no Indicates the PR's author has not signed the CLA. labels Jul 10, 2020
@AceHack
Copy link
Contributor

AceHack commented Jul 10, 2020

This is weird, cherry-picking @vaikas commit cause the CLA to go out of wack. We are gonna just manually make the fix to backport instead of cherry-picking.

Copy link
Member

@mattmoor mattmoor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Produced via:
gofmt -s -w $(find -path './vendor' -prune -o -path './third_party' -prune -o -name '*.pb.go' -prune -o -type f -name '*.go' -print)
goimports -w $(find -name '*.go' | grep -v vendor | grep -v third_party | grep -v .pb.go | grep -v wire_gen.go)

Co-authored-by: Matt Moore <mattmoor@vmware.com>
@vaikas
Copy link
Contributor

vaikas commented Jul 10, 2020

I guess I'm little confused what we're backporting here? Shouldn't it just be a rebase? I'm mosdef not a git expert, but something seems wrong here.

@vaikas
Copy link
Contributor

vaikas commented Jul 10, 2020

lol, I see, you're porting them to .16.1 release :) LOL sorry about the noise...

@AceHack
Copy link
Contributor

AceHack commented Jul 10, 2020

@vaikas do you know why the CLA got invalidated when we cherry-picked your commit?

@vayyappaneni
Copy link
Contributor Author

/retest

@AceHack
Copy link
Contributor

AceHack commented Jul 10, 2020

/test pull-knative-eventing-upgrade-tests

@vaikas
Copy link
Contributor

vaikas commented Jul 10, 2020

@AceHack no idea, in the past I've seen the emails go out of whack when things get cherrypicked, but no idea.

@vaikas
Copy link
Contributor

vaikas commented Jul 10, 2020

Oh snap, looks like this needs to be cherrypicked also:
#3539

The errors are exactly what we saw in the main branch.

* try to dump some state

* use client wait or fail

* create broker directly
@knative-prow-robot knative-prow-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 10, 2020
@vayyappaneni
Copy link
Contributor Author

/retest

@AceHack
Copy link
Contributor

AceHack commented Jul 10, 2020

@vaikas it seems cherry-picking your PR directly into 16 branch caused unit test issues. Can you offer any advice or do you know if there are other things we should cherry pick.

@AceHack
Copy link
Contributor

AceHack commented Jul 10, 2020

/retest

@vaikas
Copy link
Contributor

vaikas commented Jul 10, 2020

Looks like backporting it missed some bits?
https://github.com/knative/eventing/pull/3539/files#diff-9ec464ac1ed01

vs.
https://github.com/knative/eventing/pull/3557/files#diff-9ec464ac1ed0145dae8da5a443e0a903L22

test/upgrade/prober/configuration.go:22:2: imported and not used: "knative.dev/eventing/pkg/reconciler/sugar"

@knative-test-reporter-robot

The following jobs failed:

Test name Triggers Retries
pull-knative-eventing-upgrade-tests 0/3

Failed non-flaky tests preventing automatic retry of pull-knative-eventing-upgrade-tests:

test/upgrade.[build failed]

@AceHack
Copy link
Contributor

AceHack commented Jul 11, 2020

@markusthoemmes @vaikas It's finally working, thanks for all the help. Can we get it merged? Thanks again.

@vaikas
Copy link
Contributor

vaikas commented Jul 12, 2020

/lgtm
/approve

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 12, 2020
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vaikas, vayyappaneni

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:

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

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 12, 2020
@knative-prow-robot knative-prow-robot merged commit acdd118 into knative:release-0.16 Jul 12, 2020
@vayyappaneni vayyappaneni deleted the istiofix-0.16 branch July 12, 2020 04:09
matzew pushed a commit to matzew/eventing that referenced this pull request Sep 30, 2020
* adding istion annotation (knative#3534)

* backporting knative#3543

* Update test/lib/duck/resource_inspectors.go

Co-authored-by: Matt Moore <mattmoor@vmware.com>

* Use the standard resource creation libs for upgrade tests. (knative#3539)

* try to dump some state

* use client wait or fail

* create broker directly

* removed the unused import

Co-authored-by: Matt Moore <mattmoor@vmware.com>
matzew pushed a commit to matzew/eventing that referenced this pull request Oct 1, 2020
* adding istion annotation (knative#3534)

* backporting knative#3543

* Update test/lib/duck/resource_inspectors.go

Co-authored-by: Matt Moore <mattmoor@vmware.com>

* Use the standard resource creation libs for upgrade tests. (knative#3539)

* try to dump some state

* use client wait or fail

* create broker directly

* removed the unused import

Co-authored-by: Matt Moore <mattmoor@vmware.com>
openshift-merge-robot pushed a commit to openshift/knative-eventing that referenced this pull request Oct 7, 2020
* adding istion annotation (knative#3534) (knative#3557)

* adding istion annotation (knative#3534)

* backporting knative#3543

* Update test/lib/duck/resource_inspectors.go

Co-authored-by: Matt Moore <mattmoor@vmware.com>

* Use the standard resource creation libs for upgrade tests. (knative#3539)

* try to dump some state

* use client wait or fail

* create broker directly

* removed the unused import

Co-authored-by: Matt Moore <mattmoor@vmware.com>

* cp 3897 (knative#3902)

* cp 3897

* backport 3719

* x bit

* apiserversource v1beta1->v1alpha2

* install broker / sugar

* backport 3945 to .16 (knative#3948)

Co-authored-by: VijayaSenaReddy Ayyappaneni <48216363+vayyappaneni@users.noreply.github.com>
Co-authored-by: Matt Moore <mattmoor@vmware.com>
Co-authored-by: Ville Aikas <11279988+vaikas@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/test-and-release Test infrastructure, tests or release cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants