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

Reconcile Configuration first when using named Revisions #5547

Merged
merged 2 commits into from
Sep 16, 2019

Conversation

dgerd
Copy link

@dgerd dgerd commented Sep 15, 2019

This change fixes a problem where RouteReady will periodically go from
Unknown to False and then to True when reconciling a Service that uses
the "BYO Revision Name" functionality. If the Route reconciles before a
Revision has been created it will report a False status and cause
clients watching the status to report failure. Since Revision names can
only be referenced before they created when a user brings their own name
this change serializes the Configuration reconciliation to occur and
stabilize before doing the Route reconciliation.

Fixes #4173

This change fixes a problem where RouteReady will periodically go from
Unknown to False and then to True when reconciling a Service that uses
the "BYO Revision Name" functionality. If the Route reconciles before a
Revision has been created it will report a False status and cause
clients watching the status to report failure. Since Revision names can
only be referenced before they created when a user brings their own name
this change serializes the Configuration reconciliation to occur and
stabilize before doing the Route reconciliation.

Fixes knative#4173
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Sep 15, 2019
@knative-prow-robot knative-prow-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 15, 2019
Copy link
Contributor

@knative-prow-robot knative-prow-robot left a comment

Choose a reason for hiding this comment

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

@dgerd: 0 warnings.

In response to this:

This change fixes a problem where RouteReady will periodically go from
Unknown to False and then to True when reconciling a Service that uses
the "BYO Revision Name" functionality. If the Route reconciles before a
Revision has been created it will report a False status and cause
clients watching the status to report failure. Since Revision names can
only be referenced before they created when a user brings their own name
this change serializes the Configuration reconciliation to occur and
stabilize before doing the Route reconciliation.

Fixes #4173

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.

@knative-prow-robot knative-prow-robot added area/API API objects and controllers area/test-and-release It flags unit/e2e/conformance/perf test issues for product features labels Sep 15, 2019
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgerd

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 Sep 15, 2019
@knative-metrics-robot
Copy link

The following is the coverage report on pkg/.
Say /test pull-knative-serving-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/reconciler/service/service.go 88.4% 88.6% 0.1

@dgerd
Copy link
Author

dgerd commented Sep 16, 2019

/assign @vagababov

Copy link
Contributor

@vagababov vagababov left a comment

Choose a reason for hiding this comment

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

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 16, 2019
@knative-prow-robot knative-prow-robot merged commit 2680f82 into knative:master Sep 16, 2019
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/API API objects and controllers area/test-and-release It flags unit/e2e/conformance/perf test issues for product features cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. 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.

Does BYO revision name result in spurious deployment errors?
5 participants