Skip to content

OCPBUGS-672: Catalog Pod Startup Probe Timeout #446

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

Merged

Conversation

dtfranz
Copy link
Contributor

@dtfranz dtfranz commented Feb 15, 2023

Updates the Startup Probe timeoutSeconds for catalog pods to be consistent with the timeouts in the readiness and liveness probes. Also adjusted the failure threshold in order to maintain the ~150s startup time failure as originally designed.

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 401bfff4df20c97bef08db2dc9fc75bc1879be7a

OCPBUGS-672

Updates the Startup Probe timeoutSeconds for catalog pods to be consistent with the timeouts in the readiness and liveness probes. Also adjusted the failure threshold in order to maintain the ~150s startup time failure as originally designed.

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 401bfff4df20c97bef08db2dc9fc75bc1879be7a

Signed-off-by: dtfranz <[email protected]>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 15, 2023
@openshift-ci-robot
Copy link

@dtfranz: This pull request references Jira Issue OCPBUGS-672, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Updates the Startup Probe timeoutSeconds for catalog pods to be consistent with the timeouts in the readiness and liveness probes. Also adjusted the failure threshold in order to maintain the ~150s startup time failure as originally designed.

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 401bfff4df20c97bef08db2dc9fc75bc1879be7a

OCPBUGS-672

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.

@openshift-ci openshift-ci bot requested review from anik120 and benluddy February 15, 2023 01:20
@bandrade
Copy link
Contributor

/lgtm

Timeout was added as expected

oc exec catalog-operator-7c9f79f889-xskvj -n openshift-operator-lifecycle-manager -- olm --version

OLM version: 0.19.0
git commit: f1d5d0b49182e221e7f914f53e5ed2ca07fc59da

oc get pods redhat-operators-xvl8m -o yaml -n openshift-marketplace

spec:
  containers:
  - image: registry.redhat.io/redhat/redhat-operator-index:v4.12
    imagePullPolicy: Always
    livenessProbe:
      exec:
        command:
        - grpc_health_probe
        - -addr=:50051
      failureThreshold: 3
      initialDelaySeconds: 10
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 5
    name: registry-server
    ports:
    - containerPort: 50051
      name: grpc
      protocol: TCP
    readinessProbe:
      exec:
        command:
        - grpc_health_probe
        - -addr=:50051

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 15, 2023
@dtfranz
Copy link
Contributor Author

dtfranz commented Feb 15, 2023

/lgtm

Timeout was added as expected

oc exec catalog-operator-7c9f79f889-xskvj -n openshift-operator-lifecycle-manager -- olm --version

OLM version: 0.19.0
git commit: f1d5d0b49182e221e7f914f53e5ed2ca07fc59da

oc get pods redhat-operators-xvl8m -o yaml -n openshift-marketplace

spec:
  containers:
  - image: registry.redhat.io/redhat/redhat-operator-index:v4.12
    imagePullPolicy: Always
    livenessProbe:
      exec:
        command:
        - grpc_health_probe
        - -addr=:50051
      failureThreshold: 3
      initialDelaySeconds: 10
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 5
    name: registry-server
    ports:
    - containerPort: 50051
      name: grpc
      protocol: TCP
    readinessProbe:
      exec:
        command:
        - grpc_health_probe
        - -addr=:50051

Hey @bandrade , thank you for taking a look at this! I didn't see the startupProbe in the yaml you posted, could you please also verify that the timeoutSeconds in the startupProbe is set to 5 as well?

@dtfranz
Copy link
Contributor Author

dtfranz commented Feb 15, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 15, 2023
@openshift-ci-robot
Copy link

@dtfranz: This pull request references Jira Issue OCPBUGS-672, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.0) matches configured target version for branch (4.13.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

/jira refresh

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.

@awgreene
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 15, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awgreene, dtfranz

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 15, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD bae42cd and 2 for PR HEAD 8c0d84e in total

@dtfranz
Copy link
Contributor Author

dtfranz commented Feb 16, 2023

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2023

@dtfranz: all tests passed!

Full PR test history. Your PR 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.

@openshift-merge-robot openshift-merge-robot merged commit 0265569 into openshift:master Feb 16, 2023
@openshift-ci-robot
Copy link

@dtfranz: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-672 has been moved to the MODIFIED state.

In response to this:

Updates the Startup Probe timeoutSeconds for catalog pods to be consistent with the timeouts in the readiness and liveness probes. Also adjusted the failure threshold in order to maintain the ~150s startup time failure as originally designed.

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 401bfff4df20c97bef08db2dc9fc75bc1879be7a

OCPBUGS-672

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.

@dtfranz
Copy link
Contributor Author

dtfranz commented Feb 16, 2023

/cherry-pick release-4.12

@openshift-cherrypick-robot

@dtfranz: new pull request created: #450

In response to this:

/cherry-pick release-4.12

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.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants