OCPBUGS-34227: fix: increase vgmanager startup timeout to 10 mins to cover long running volume group initialization

[jakobmoellerdev]

This is done as a workaround until we have a better fix available
Since im unable to stabilize #658 right now and I have to do more debugging there this should provide a valid workaround that can sit until release if no better option is found.

[openshift-ci-robot]

@jakobmoellerdev: This pull request references Jira Issue OCPBUGS-34227, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.17.0) matches configured target version for branch (4.17.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @radeore

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

In response to this:

This is done as a workaround until we have a better fix available
Since im unable to stabilize #658 right now and I have to do more debugging there this should provide a valid workaround that can sit until release if no better option is found.

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jakobmoellerdev

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 [jakobmoellerdev]

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

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.95%. Comparing base (7ff35c9) to head (81ff540).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #668      +/-   ##
==========================================
+ Coverage   57.76%   57.95%   +0.18%     
==========================================
  Files          53       53              
  Lines        4215     4215              
==========================================
+ Hits         2435     2443       +8     
+ Misses       1534     1531       -3     
+ Partials      246      241       -5     

Files	Coverage Δ
...rollers/lvmcluster/resource/vgmanager_daemonset.go	97.20% <100.00%> (ø)

... and 4 files with indirect coverage changes

[jakobmoellerdev]

/test e2e-aws

[openshift-ci-robot]

@jakobmoellerdev: This pull request references Jira Issue OCPBUGS-34227. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to this:

This is done as a workaround until we have a better fix available
Since im unable to stabilize #658 right now and I have to do more debugging there this should provide a valid workaround that can sit until release if no better option is found.

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]

@jakobmoellerdev: This pull request references Jira Issue OCPBUGS-34227, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.17.0) matches configured target version for branch (4.17.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @radeore

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

In response to this:

This is done as a workaround until we have a better fix available
Since im unable to stabilize #658 right now and I have to do more debugging there this should provide a valid workaround that can sit until release if no better option is found.

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.

[suleymanakbas91]

/retest
/lgtm

[openshift-ci]

@jakobmoellerdev: 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.

[openshift-ci-robot]

@jakobmoellerdev: Jira Issue OCPBUGS-34227: Some pull requests linked via external trackers have merged:

• openshift/lvm-operator#633
• openshift/lvm-operator#643

The following pull requests linked via external trackers have not merged:

• openshift/lvm-operator#658 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to this:

This is done as a workaround until we have a better fix available
Since im unable to stabilize #658 right now and I have to do more debugging there this should provide a valid workaround that can sit until release if no better option is found.

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.