[release-4.18] OCPBUGS-46032: Update the storage.conf configuration file template

[openshift-cherrypick-robot]

This is an automated cherry-pick of #4681

/assign kwilczynski

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-44995 has been cloned as Jira Issue OCPBUGS-46339. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-46339: Update the storage.conf configuration file template

In response to this:

This is an automated cherry-pick of #4681

/assign kwilczynski

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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-46339, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-44995 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-44995 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
• bug has dependents

Requesting review from QA contact:
/cc @cpmeadors

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

In response to this:

This is an automated cherry-pick of #4681

/assign kwilczynski

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.

[kwilczynski]

/retitle [release-4.18] OCPBUGS-4633: Update the storage.conf configuration file template

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-4633, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.12.z" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-4518 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Done) instead
• expected dependent Jira Issue OCPBUGS-4518 to target a version in 4.19.0, but it targets "4.13.0" 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:

This is an automated cherry-pick of #4681

/assign kwilczynski

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.

[kwilczynski]

/jira refresh

[openshift-ci-robot]

@kwilczynski: This pull request references Jira Issue OCPBUGS-4633, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.12.z" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-4518 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Done) instead
• expected dependent Jira Issue OCPBUGS-4518 to target a version in 4.19.0, but it targets "4.13.0" 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 openshift-eng/jira-lifecycle-plugin repository.

[kwilczynski]

/retitle [release-4.18] OCPBUGS-46032: Update the storage.conf configuration file template

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-46032, which is invalid:

• expected the bug to target only the "4.18.0" version, but multiple target versions were set
• expected Jira Issue OCPBUGS-46032 to depend on a bug targeting a version in 4.19.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

This is an automated cherry-pick of #4681

/assign kwilczynski

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.

[kwilczynski]

/jira refresh

[openshift-ci-robot]

@kwilczynski: This pull request references Jira Issue OCPBUGS-46032, which is invalid:

• expected Jira Issue OCPBUGS-46032 to depend on a bug targeting a version in 4.19.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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

[kwilczynski]

/jira refresh

[openshift-ci-robot]

@kwilczynski: This pull request references Jira Issue OCPBUGS-46032, which is invalid:

• expected Jira Issue OCPBUGS-46032 to depend on a bug targeting a version in 4.19.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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

[kwilczynski]

/retest

[kwilczynski]

/retest

[kwilczynski]

/cc @openshift/cri-o-maintainers
/cc @haircommander
/cc @saschagrunert
/cc @sohankunkerkar

[openshift-ci]

@kwilczynski: GitHub didn't allow me to request PR reviews from the following users: openshift/cri-o-maintainers.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @openshift/cri-o-maintainers
/cc @haircommander
/cc @saschagrunert
/cc @sohankunkerkar

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.

[sohankunkerkar]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, sohankunkerkar
Once this PR has been reviewed and has the lgtm label, please assign yuqi-zhang for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[kwilczynski]

/retest

[openshift-ci]

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-azure-ovn-upgrade-out-of-change	36e34c5	link	false	/test e2e-azure-ovn-upgrade-out-of-change

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.