DFBUGS-1356:[release-4.18] controllers: add a info explicitly stating no user action

[leelavg]

it was observed that users is mistaking the log message and trying to speed up the operation by manually annotating the storagecluster with provider mode annotation even in non provider modes.

[openshift-ci-robot]

@leelavg: This pull request references [Jira Issue DFBUGS-1356](https://issues.redhat.com//browse/DFBUGS-1356), which is invalid:

• expected the bug to target the "odf-4.18.10" 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.

Details

In response to this:

it was observed that users is mistaking the log message and trying to speed up the operation by manually annotating the storagecluster with provider mode annotation even in non provider modes.

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.

[leelavg]

/cherrypick release-4.17
via DFBUGS-4042

[openshift-cherrypick-robot]

@leelavg: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

Details

In response to this:

/cherrypick release-4.17
via DFBUGS-4042

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.

[leelavg]

/cherrypick release-4.16
via DFBUGS-4043

[openshift-cherrypick-robot]

@leelavg: once the present PR merges, I will cherry-pick it on top of release-4.16 in a new PR and assign it to you.

Details

In response to this:

/cherrypick release-4.16
via DFBUGS-4043

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.

[leelavg]

w/ fix

on local cluster

Waiting for 90 sec before checking to allow operator to run
StorageCluster CR does not exist
Waiting on deployment mode verification, no user action needed.
Waiting on deployment mode verification, no user action needed.
[...]

Above will end w/ Condition met to allow operator to run if configured in provider mode or odf-op will scale us down

on remote cluster

Waiting for 90 sec before checking to allow operator to run
Condition met to allow operator to run

[nb-ohad]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leelavg, nb-ohad

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [leelavg,nb-ohad]

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

[leelavg]

/jira refresh

[openshift-ci-robot]

@leelavg: This pull request references [Jira Issue DFBUGS-1356](https://issues.redhat.com//browse/DFBUGS-1356), which is invalid:

• expected the bug to target either version "odf-4.18.13." or "openshift-odf-4.18.13.", but it targets "odf-4.18.15" 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.

Details

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.

[leelavg]

/jira refresh

[openshift-ci-robot]

@leelavg: This pull request references [Jira Issue DFBUGS-1356](https://issues.redhat.com//browse/DFBUGS-1356), which is invalid:

• expected the bug to target either version "odf-4.18.13." or "openshift-odf-4.18.13.", but it targets "odf-4.18.15" 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.

Details

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.

[leelavg]

/jira refresh

[openshift-ci-robot]

@leelavg: This pull request references [Jira Issue DFBUGS-1356](https://issues.redhat.com//browse/DFBUGS-1356), which is invalid:

• expected the bug to target either version "odf-4.18.14." or "openshift-odf-4.18.14.", but it targets "odf-4.18.15" 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.

Details

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.

[leelavg]

/jira refresh

[openshift-ci-robot]

@leelavg: This pull request references [Jira Issue DFBUGS-1356](https://issues.redhat.com//browse/DFBUGS-1356), which is invalid:

• expected the bug to target either version "odf-4.18.14." or "openshift-odf-4.18.14.", but it targets "odf-4.18.15" 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.

Details

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.