Skip to content

OCPBUGS-74076: Fix: Enable boot diagnostics for Azure Stack Hub VMs#182

Open
gpei wants to merge 1 commit intoopenshift:mainfrom
gpei:add_ash_diagnostics
Open

OCPBUGS-74076: Fix: Enable boot diagnostics for Azure Stack Hub VMs#182
gpei wants to merge 1 commit intoopenshift:mainfrom
gpei:add_ash_diagnostics

Conversation

@gpei
Copy link

@gpei gpei commented Jan 25, 2026

The deriveVirtualMachineParametersStackHub function was missing the DiagnosticsProfile field assignment, causing boot diagnostics to not be applied to Azure Stack Hub VMs even when correctly specified in the Machine configuration.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 25, 2026
@openshift-ci-robot
Copy link

@gpei: This pull request references Jira Issue OCPBUGS-74076, which is invalid:

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

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

Details

In response to this:

The deriveVirtualMachineParametersStackHub function was missing the DiagnosticsProfile field assignment, causing boot diagnostics to not be applied to Azure Stack Hub VMs even when correctly specified in the Machine configuration.

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 bot requested review from RadekManak and mdbooth January 25, 2026 11:31
@gpei
Copy link
Author

gpei commented Jan 25, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 25, 2026
@openshift-ci-robot
Copy link

@gpei: This pull request references Jira Issue OCPBUGS-74076, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

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.

@openshift-ci openshift-ci bot requested a review from sunzhaohua2 January 25, 2026 11:32
@gpei
Copy link
Author

gpei commented Jan 25, 2026

/payload-job-with-prs periodic-ci-openshift-verification-tests-main-installation-nightly-4.22-azure-stack-ipi-boot-diagnostics-usermanaged-f28 openshift/installer#10224

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 25, 2026

@gpei: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-verification-tests-main-installation-nightly-4.22-azure-stack-ipi-boot-diagnostics-usermanaged-f28

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7aeec980-f9e2-11f0-8f5e-f212ccafe468-0

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 25, 2026

@gpei: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@gpei
Copy link
Author

gpei commented Jan 27, 2026

/payload-job-with-prs periodic-ci-openshift-verification-tests-main-installation-nightly-4.22-azure-stack-ipi-boot-diagnostics-usermanaged-f28 openshift/installer#10224

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

@gpei: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-verification-tests-main-installation-nightly-4.22-azure-stack-ipi-boot-diagnostics-usermanaged-f28

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5deb7650-fb16-11f0-89d1-164b85f8b486-0

@sunzhaohua2
Copy link
Contributor

sunzhaohua2 commented Jan 27, 2026

@gpei For storageAccountType: CustomerManaged, it work as expected.

          diagnostics:
            boot:
              customerManaged:
                storageAccountURI: https://imageregistryzhsuna9wjrk.blob.mtcazs.wwtatc.com/
              storageAccountType: CustomerManaged
# az vm show --name zhsun-ashfix-cjhqf-worker-mtcazs2-b8v6g -g zhsun-ashfix-cjhqf-rg --query 'diagnosticsProfile.bootDiagnostics'
{
 "enabled": true,
 "storageUri": "https://imageregistryzhsuna9wjrk.blob.mtcazs.wwtatc.com/"
}

For storageAccountType: AzureManaged machine creation failed with incorrect message, ASH does not support AzureManaged boot diagnostics storage. I created a bug https://issues.redhat.com/browse/OCPBUGS-74573

          diagnostics:
            boot:
              storageAccountType: AzureManaged
        RESPONSE 400: 400 Bad Request
        ERROR CODE: InvalidParameter
        --------------------------------------------------------------------------------
        {
          "error": {
            "code": "InvalidParameter",
            "message": "Required parameter 'bootDiagnostics.storageAccountUri' is missing (null).",
            "target": "bootDiagnostics.storageAccountUri"
          }
        }

@gpei
Copy link
Author

gpei commented Jan 27, 2026

/payload-job-with-prs periodic-ci-openshift-verification-tests-main-installation-nightly-4.22-azure-stack-ipi-boot-diagnostics-usermanaged-f28 openshift/installer#10224

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

@gpei: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-verification-tests-main-installation-nightly-4.22-azure-stack-ipi-boot-diagnostics-usermanaged-f28

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ad7b9fc0-fb24-11f0-91b5-be2c7e67fc22-0

@gpei
Copy link
Author

gpei commented Jan 27, 2026

/payload-job-with-prs periodic-ci-openshift-verification-tests-main-installation-nightly-4.22-azure-stack-ipi-boot-diagnostics-disabled-f28 openshift/installer#10224

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

@gpei: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-verification-tests-main-installation-nightly-4.22-azure-stack-ipi-boot-diagnostics-disabled-f28

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0b6fd0a0-fb53-11f0-9560-fddbdd6f5af8-0

Copy link
Member

@damdo damdo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 4, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 4, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 4, 2026
@damdo
Copy link
Member

damdo commented Feb 4, 2026

/hold

Until we decide what to do with: https://issues.redhat.com/browse/OCPBUGS-74573

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 4, 2026
@damdo
Copy link
Member

damdo commented Feb 4, 2026

^ cc. @gpei

@gpei
Copy link
Author

gpei commented Feb 5, 2026

@damdo Thanks for the review and reminding.
Regarding the validation of the diagnostics profile configuration, it should be added in https://github.com/openshift/machine-api-provider-azure/blob/main/pkg/cloud/azure/actuators/machine/reconciler.go#L912, right?
If so, I'd prefer to merge the current PR first, since it fixes the two supported boot-diagnostics strategies on ASH: UserManaged and Disabled. For the AzureManaged type, which is not supported for ASH, I think the validation can be added in a separate PR, specifically for OCPBUGS-74573.
I should have time to work on this during next week's Shift week. WDYT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants