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

Fix status reconcilation for Knative service #1170

Merged
merged 1 commit into from
Aug 6, 2021

Conversation

savitaashture
Copy link
Contributor

@savitaashture savitaashture commented Aug 2, 2021

Issue:

When we create custom object the READY status of EL always shows false

RootCause:

Polling of Knative service are not done properly and because of that only initial status are set to EL status here

Changes

Added a condition check to set the status to EL when Knative service READY state is True

/cc @dibyom

Effected versions:

Triggers v0.15.0 and v0.15.0-rc1

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Release Notes

NONE

@tekton-robot tekton-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Aug 2, 2021
@tekton-robot tekton-robot requested a review from dibyom August 2, 2021 15:18
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Aug 2, 2021
@tekton-robot
Copy link

The following is the coverage report on the affected files.
Say /test pull-tekton-triggers-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/reconciler/eventlistener/eventlistener.go 78.6% 77.7% -0.9

@dibyom
Copy link
Member

dibyom commented Aug 3, 2021

Oh interesting.
Code looks good. Two questions:

  1. Do we need a patch release for this?
  2. Could we add a test for this behavior?

@savitaashture
Copy link
Contributor Author

Oh interesting.
Code looks good. Two questions:

  1. Do we need a patch release for this?

Yes

  1. Could we add a test for this behavior?

For Knative service we are using withPod ducktype and that doesn't have status field to set some dummy value

Lets cover e2e test as part of this issue #1089 so that in future these kind of issues won't miss

@dibyom
Copy link
Member

dibyom commented Aug 6, 2021

/approve
/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 6, 2021
@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 6, 2021
@tekton-robot tekton-robot merged commit 5976c3f into tektoncd:main Aug 6, 2021
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. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants