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

[WIP] increase SafeTimeToAssumeNodeRebootedSeconds #186

Conversation

mshitrit
Copy link
Member

@mshitrit mshitrit commented Feb 1, 2024

increase SafeTimeToAssumeNodeRebootedSeconds as in some clusters it's value is lower than minimum calculated value

Copy link
Contributor

openshift-ci bot commented Feb 1, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link
Contributor

openshift-ci bot commented Feb 1, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mshitrit

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 label Feb 1, 2024
… value is lower than minimum calculated value

Signed-off-by: Michael Shitrit <[email protected]>
@mshitrit mshitrit force-pushed the increase-default-SafeTimeToAssumeNodeRebootedSeconds branch from 87739cb to 0293992 Compare February 1, 2024 14:21
@mshitrit
Copy link
Member Author

mshitrit commented Mar 3, 2024

Suggested a better approach to solve this: https://issues.redhat.com/browse/ECOPROJECT-1875

@mshitrit mshitrit closed this Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant