Skip to content

feat: use custom cloud init status reporting - #9022

Draft
lilypan26 wants to merge 5 commits into
mainfrom
lily/custom-cloud-init-reporting
Draft

feat: use custom cloud init status reporting#9022
lilypan26 wants to merge 5 commits into
mainfrom
lily/custom-cloud-init-reporting

Conversation

@lilypan26

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

awesomenix and others added 3 commits July 23, 2026 13:24
…ript

   Bake experimental_skip_ready_report into VHD via cloud.cfg.d to skip
   cloud-init's built-in health ready report to Azure fabric. Add a
   standalone Python script (report_ready.py) that can be invoked from
   CSE to report ready at the appropriate time during node provisioning.

   Depends on canonical/cloud-init#6771.

   Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Supersede the single-file DataSourceAzure.py vendoring hack with the
actual patched cloud-init Jammy .deb built from
https://github.com/peytonr18/cloud-init/tree/probertson/jammy-runtime-ds-options-skip-ready
(base version 26.1-0ubuntu1~22.04.1), which carries both the
experimental_skip_ready_report patch (canonical/cloud-init#6771) and a
second patch allowing datasource options to be overridden at runtime
via custom data.

Installing the full package via dpkg instead of overwriting a single
module keeps cloud-init's schema, tests, and packaging metadata
consistent, and avoids the risk of the vendored file drifting from the
rest of the installed package.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 9e623d45-e026-4e5c-b9e2-3107c1d96592
@lilypan26 lilypan26 changed the title Lily/custom cloud init reporting feat: use custom cloud init status reporting Jul 23, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Windows Unit Test Results

  3 files   12 suites   54s ⏱️
389 tests 389 ✅ 0 💤 0 ❌
392 runs  392 ✅ 0 💤 0 ❌

Results for commit 7436e77.

@lilypan26
lilypan26 force-pushed the lily/custom-cloud-init-reporting branch from 7436e77 to a5ac516 Compare July 31, 2026 16:36
@aks-node-assistant

Copy link
Copy Markdown
Contributor

AgentBaker Linux Gate Detective

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=174679898
Failed job/stage/task: e2e / Run AgentBaker E2E / Run AgentBaker E2E
TL;DR: Test_Ubuntu2204 failed in CSE provisioning: vmssCSE returned VMExtensionProvisioningError with CSE ExitCode 161 while running installSecureTLSBootstrapClient, reporting secure TLS bootstrapping enabled without a custom client download URL.
Likely cause/signature: PR-change-caused CSE/provisioning regression; stable wiki signature linux-vhd-prgate-cse-secure-tls-bootstrap-no-client-url.
Confidence: High for failure mode, medium-high for PR-change-caused attribution.
Owner/action: PR author/Node Lifecycle should validate secure TLS bootstrap client URL/config propagation for the Ubuntu2204 E2E path and remove/avoid the temp forced E2E failure before rerunning through normal policy.
Strongest alternative: infrastructure/agent flake, but less likely because the same Test_Ubuntu2204 vmssCSE ExitCode 161 repeated in build 174680846 on the same branch and the PR changes CSE/cloud-init/Packer paths.
Evidence: timeline failed task log 612; failed test result run 555715746; PR #9022 changed parts/linux/cloud-init/artifacts/cse_install.sh, cse_start.sh, report_ready.py, and Packer/cloud-init files; adjacent manual branch build 174680846 reproduced the same signature.
Wiki:
https://dev.azure.com/msazure/CloudNativeCompute/_wiki/wikis/=%2FAKS%2FSIGs%20and%20Teams%2FAKS%20Components%2FSIG%3A%20Node%20Lifecycle%2FAI%20Agent%20Knowledge%2FAgentBaker%20Gate%20PR%20Pipeline%20Flakiness%2FNoisy%20Active%20Items

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants