DFBUGS-2370: [release-4.18] Fix storageid generation

[umangachapagain]

There can be cases where Ceph FSID is not yet initialized or missing from the server response. In such cases, it is better to error out early than to proceed with incorrect state.

We also reconcile all blue secrets irrespective of the changes to ensure that we do not miss out on any updates. Additionally, we watch CephCluster for FSID changes.

Backport of #323

[openshift-ci-robot]

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

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

In response to this:

There can be cases where Ceph FSID is not yet initialized or missing from the server response. In such cases, it is better to error out early than to proceed with incorrect state.

We also reconcile all blue secrets irrespective of the changes to ensure that we do not miss out on any updates. Additionally, we watch CephCluster for FSID changes.

Backport of #323

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.

[umangachapagain]

/jira refresh

[openshift-ci-robot]

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

3 validation(s) were run on this bug

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

Requesting review from QA contact:
/cc @keesturam

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.

[openshift-ci]

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: keesturam.

Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

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

3 validation(s) were run on this bug

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

Requesting review from QA contact:
/cc @keesturam

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.

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.

[vbnrh]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: umangachapagain, vbnrh

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 [umangachapagain,vbnrh]

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

[openshift-ci-robot]

@umangachapagain: [Jira Issue DFBUGS-2370](https://issues.redhat.com//browse/DFBUGS-2370): All pull requests linked via external trackers have merged:

• red-hat-storage/odf-multicluster-orchestrator#322

[Jira Issue DFBUGS-2370](https://issues.redhat.com//browse/DFBUGS-2370) has been moved to the MODIFIED state.

In response to this:

There can be cases where Ceph FSID is not yet initialized or missing from the server response. In such cases, it is better to error out early than to proceed with incorrect state.

We also reconcile all blue secrets irrespective of the changes to ensure that we do not miss out on any updates. Additionally, we watch CephCluster for FSID changes.

Backport of #323

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.