OCPBUGS-672: Catalog Pod Startup Probe Timeout

[dtfranz]

Description of the change:

Updates the Startup Probe timeoutSeconds for catalog pods to be consistent with the timeouts in the readiness and liveness probes as the default of 1s can be too low in some cases. Also adjusted the failure threshold in order to maintain the ~150s startup time failure as originally designed (timeout of 5s + period of 10s = 15s per attempt * 10 failures = 150s).

Motivation for the change:

OCPBUGS-672

[openshift-ci-robot]

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

• expected the bug to target the "4.13.0" version, but no target version was set

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:

Description of the change:

Updates the Startup Probe timeoutSeconds for catalog pods to be consistent with the timeouts in the readiness and liveness probes as the default of 1s can be too low in some cases. Also adjusted the failure threshold in order to maintain the ~150s startup time failure as originally designed (timeout of 5s + period of 10s = 15s per attempt * 10 failures = 150s).

Motivation for the change:

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]

/jira refresh

[openshift-ci-robot]

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

• expected the bug to target the "4.13.0" version, but it targets "4.13" 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.

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.

[dtfranz]

/jira refresh

[openshift-ci-robot]

@dtfranz: This pull request references Jira Issue OCPBUGS-672, which is valid. The bug has been moved to the POST state.

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 ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

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.

[dtfranz]

/hold

[tmshort]

/lgtm

[dtfranz]

/remove-hold

[ankitathomas]

/lgtm

[tmshort]

/lgtm

[dinhxuanvu]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ankitathomas, dinhxuanvu, dtfranz, tmshort

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:

• OWNERS [dinhxuanvu]

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

[openshift-ci-robot]

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

• operator-framework/operator-lifecycle-manager#2919

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

In response to this:

Description of the change:

Updates the Startup Probe timeoutSeconds for catalog pods to be consistent with the timeouts in the readiness and liveness probes as the default of 1s can be too low in some cases. Also adjusted the failure threshold in order to maintain the ~150s startup time failure as originally designed (timeout of 5s + period of 10s = 15s per attempt * 10 failures = 150s).

Motivation for the change:

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]

/cherry-pick release-4.12

[openshift-cherrypick-robot]

@dtfranz: cannot checkout release-4.12: error checking out release-4.12: exit status 1. output: error: pathspec 'release-4.12' did not match any file(s) known to git

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.