Skip to content

Conversation

pmtk
Copy link
Member

@pmtk pmtk commented Jan 20, 2025

No description provided.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 20, 2025

@pmtk: This pull request references USHIFT-4288 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 20, 2025
@openshift-ci openshift-ci bot requested review from agullon and copejon January 20, 2025 13:19
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 20, 2025

Then, executes `microshift healthcheck` command with following options:
- `-v=2` to increase verbosity of the output
- `--timeout="${WAIT_TIMEOUT_SECS}s"` to override default 300s timeout value
Copy link
Contributor

Choose a reason for hiding this comment

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

Is 300s the default in the code, or 600?

Copy link
Member Author

Choose a reason for hiding this comment

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

It's 300s:

cmd.Flags().DurationVar(&timeout, "timeout", 300*time.Second, "The maximum duration of each stage of the healthcheck.")

Co-authored-by: Gregory Giguashvili <[email protected]>
Copy link
Contributor

openshift-ci bot commented Jan 21, 2025

@pmtk: 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-sigs/prow repository. I understand the commands that are listed here.

@ggiguash
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 21, 2025
Copy link
Contributor

openshift-ci bot commented Jan 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

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-merge-bot openshift-merge-bot bot merged commit 602fc5e into openshift:main Jan 21, 2025
5 checks passed
@pmtk pmtk deleted the healthcheck-docs branch January 21, 2025 15:08
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. 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.

3 participants