[release-4.20] OCPBUGS-65763: continue to update 02_storage.json using new property storageAccountId

[openshift-cherrypick-robot]

This is an automated cherry-pick of #10089

/assign jinyunma

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jhixson74 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:

• upi/azure/OWNERS

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]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-65661 has been cloned as Jira Issue OCPBUGS-65763. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-65763: continue to update 02_storage.json using new property storageAccountId

In response to this:

This is an automated cherry-pick of #10089

/assign jinyunma

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-65763, which is invalid:

• 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-65661 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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 #10089

/assign jinyunma

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.

[jinyunma]

Installation in job e2e-azure-ovn-upi succeeded, although few e2e test cases failed, this should be unrelated with PR.

/verified by jima

[openshift-ci-robot]

@jinyunma: This PR has been marked as verified by jima.

In response to this:

Installation in job e2e-azure-ovn-upi succeeded, although few e2e test cases failed, this should be unrelated with PR.

/verified by jima

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-cherrypick-robot: The following tests 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-azurestack-upi	5ecafa4	link	false	/test e2e-azurestack-upi
ci/prow/e2e-azure-ovn-shared-vpc	5ecafa4	link	false	/test e2e-azure-ovn-shared-vpc
ci/prow/e2e-azurestack	5ecafa4	link	false	/test e2e-azurestack
ci/prow/e2e-azure-ovn-upi	5ecafa4	link	false	/test e2e-azure-ovn-upi

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.