chore(deps): update inspektor-gadget (minor) by renovate[bot] · Pull Request #8855 · Azure/AgentBaker

renovate · 2026-07-08T04:35:29Z

This PR contains the following updates:

Package	Update	Change
ig	minor	`0.53.2-3.azl3` → `0.54.0-1.azl3`
ig	minor	`0.53.2-ubuntu24.04u3` → `0.54.1-ubuntu24.04u1`
ig	minor	`0.53.2-ubuntu22.04u3` → `0.54.1-ubuntu22.04u1`
ig	minor	`0.53.2-ubuntu20.04u3` → `0.54.1-ubuntu20.04u1`
ig-gadgets	minor	`0.53.2-1.azl3` → `0.54.0-1.azl3`
ig-gadgets	minor	`0.53.2-ubuntu20.04u1` → `0.54.0-ubuntu20.04u1`

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

calvin197

🚧 Holding until ig-gadgets 0.54.0 publishes to PMC.

This PR bumps ig → 0.54.0 in components.json, but ig-gadgets (pinned separately in vhdbuilder/packer/install-ig.sh) is still 0.53.2. The two are grouped and must share one upstream version, so the shellspec guard fails:

1) ig-gadgets pinned versions matches every ig upstream version in components.json
   When call ig_assert_gadget_versions_match_components

   The stderr should eq
     expected: ""
     got: "Expected ig and ig-gadgets to share one upstream version, found:
     0.53.2
     0.54.0"

  # spec/vhdbuilder/packer/install_ig_spec.sh:66  FAILED

Root cause: ig-gadgets 0.54.0 is not yet published to the PMC feeds (verified — ig has 0.54.0-ubuntu20.04u1, ig-gadgets tops out at 0.53.2-ubuntu20.04u1). ig simply landed upstream ahead of ig-gadgets, which is expected (gadgets is published once per upstream release, on a later cadence).

No action needed / please don't merge. Leaving this open so Renovate auto-rebases it to co-bump ig-gadgets once 0.54.0 lands in PMC — the check will then go green on its own. Do not manually bump install-ig.sh to 0.54.0 in the meantime: that package doesn't exist in the feed yet and would 404 the VHD build download.

burak-ok

🚧 Holding until ig-gadgets 0.54.0 publishes to PMC

Unfortunatly the ig-gadget release will always be 2-4 days behind

burak-ok · 2026-07-08T08:26:01Z

@calvin197 do you know why renovate didn't update this line?

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

aks-node-assistant · 2026-07-10T15:34:27Z

AgentBaker Linux gate detective

Run: 171712155
Failed job/stage/task: build / Build VHD
Detective summary: Deterministic Linux VHD component validation failure: ig was bumped to 0.54.0 while ig-gadgets remains at upstream 0.53.2, so Packer stops before image completion.

Likely cause/signature: ig (0.54.0-ubuntu24.04u1) and ig-gadgets (0.53.2-ubuntu20.04u1) must share upstream version; this matches the existing gate flakiness signature.
Confidence: High
Recommended owner/action: PR/dependency owner should update ig-gadgets to matching 0.54.0 packages across affected distros, or pin inspektor-gadget back to 0.53.2 until matching packages are available.
Strongest alternative: package feed/transient infra issue, but less likely because the log shows successful package/version resolution followed by an intentional upstream-version guard failure, and the same PR already hit this signature.

Evidence: build timeline failed Build VHD tasks; Packer log for run 171712155; downstream missing BCC/disk logs are cleanup artifacts after the primary Packer failure.
Wiki signature: inspektor-gadget-ig-ig-gadgets-upstream-mismatch

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

aks-node-assistant · 2026-07-14T01:06:30Z

AgentBaker Linux gate detective

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=172068947
Failed job/stage/task: e2e / Run AgentBaker E2E / Run AgentBaker E2E, exit code 1.

Detective summary: E2E failed with a broad gotestsum multi-scenario failure list, but the available task log does not include the leaf assertion body. Similar failures appeared across separate PR builds, so this is treated as aggregate E2E/test-harness or infra-suspect until scenario artifacts are inspected.

Likely cause / signature: e2e-gotestsum-multi-leaf-no-error-body; visible failed leaves include AzureLinuxV3 secondary NIC dual stack, DCGM exporter ubuntu2404, and LocalDNS variants.

Confidence: Low for root cause, medium for grouping.

Recommended owner/action: Node Lifecycle E2E owner should inspect full scenario artifacts/test-log JSON and split to a narrower signature if a common assertion emerges; no PR author action from this evidence alone.

Strongest alternative: A real PR-caused provisioning regression; less likely from the current evidence because the same aggregate shape appears across unrelated PRs and lacks a shared assertion body.

Evidence: ADO timeline marks Run AgentBaker E2E failed; task log shows E2E_FAILED_TESTS_RETRY_COUNT: 0, VHD build mode, and gotestsum failed-leaf summary.

Wiki signature: �2e-gotestsum-multi-leaf-no-error-body

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

Copilot

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

renovate Bot added the renovate This pull request was created by renovate label Jul 8, 2026

Copilot AI review requested due to automatic review settings July 8, 2026 04:35

renovate Bot added the renovate This pull request was created by renovate label Jul 8, 2026

renovate Bot requested a review from a team July 8, 2026 04:35

Copilot AI reviewed Jul 8, 2026

github-actions Bot added the components This pull request updates cached components on Linux or Windows VHDs label Jul 8, 2026

calvin197 requested changes Jul 8, 2026

View reviewed changes

burak-ok reviewed Jul 8, 2026

View reviewed changes

Comment thread parts/common/components.json Outdated

burak-ok Jul 8, 2026

Copy link
Copy Markdown

Contributor

Choose a reason for hiding this comment

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

@calvin197 do you know why renovate didn't update this line?

Copilot AI review requested due to automatic review settings July 8, 2026 22:11

renovate Bot force-pushed the renovate/inspektor-gadget branch from 1583354 to a7aafd0 Compare July 8, 2026 22:11

Copilot AI reviewed Jul 8, 2026

Copilot AI review requested due to automatic review settings July 8, 2026 23:46

renovate Bot force-pushed the renovate/inspektor-gadget branch from a7aafd0 to 9eff3e4 Compare July 8, 2026 23:46

Copilot AI reviewed Jul 8, 2026

Copilot AI review requested due to automatic review settings July 9, 2026 15:00

renovate Bot force-pushed the renovate/inspektor-gadget branch from 9eff3e4 to a289e58 Compare July 9, 2026 15:00

Copilot AI reviewed Jul 9, 2026

Copilot AI review requested due to automatic review settings July 9, 2026 18:57

renovate Bot force-pushed the renovate/inspektor-gadget branch from a289e58 to 8a3f0ea Compare July 9, 2026 18:57

Copilot AI reviewed Jul 9, 2026

Copilot AI review requested due to automatic review settings July 10, 2026 13:53

renovate Bot force-pushed the renovate/inspektor-gadget branch from 8a3f0ea to 6862d95 Compare July 10, 2026 13:53

Copilot AI reviewed Jul 10, 2026

Copilot AI review requested due to automatic review settings July 10, 2026 14:06

renovate Bot force-pushed the renovate/inspektor-gadget branch from 6862d95 to a18b5df Compare July 10, 2026 14:06

Copilot AI reviewed Jul 10, 2026

Copilot AI review requested due to automatic review settings July 11, 2026 04:52

renovate Bot force-pushed the renovate/inspektor-gadget branch from a18b5df to e2eb3b4 Compare July 11, 2026 04:52

renovate Bot requested a review from cameronmeissner as a code owner July 11, 2026 04:52

Copilot AI reviewed Jul 11, 2026

Copilot AI review requested due to automatic review settings July 11, 2026 12:55

renovate Bot force-pushed the renovate/inspektor-gadget branch from 0098e6e to 68d0874 Compare July 11, 2026 12:55

Copilot AI reviewed Jul 11, 2026

Copilot AI review requested due to automatic review settings July 12, 2026 20:48

renovate Bot force-pushed the renovate/inspektor-gadget branch from 68d0874 to e015670 Compare July 12, 2026 20:48

Copilot AI reviewed Jul 12, 2026

Copilot AI review requested due to automatic review settings July 13, 2026 21:38

renovate Bot force-pushed the renovate/inspektor-gadget branch from e015670 to 5e5fc92 Compare July 13, 2026 21:38

Copilot AI reviewed Jul 13, 2026

Copilot AI review requested due to automatic review settings July 13, 2026 22:06

renovate Bot force-pushed the renovate/inspektor-gadget branch from 5e5fc92 to e4e35ca Compare July 13, 2026 22:06

Copilot AI reviewed Jul 13, 2026

Copilot AI review requested due to automatic review settings July 14, 2026 18:43

renovate Bot force-pushed the renovate/inspektor-gadget branch from e4e35ca to 7165989 Compare July 14, 2026 18:43

Copilot AI reviewed Jul 14, 2026

Copilot AI review requested due to automatic review settings July 14, 2026 20:18

renovate Bot force-pushed the renovate/inspektor-gadget branch from 7165989 to 71d797a Compare July 14, 2026 20:18

Copilot AI reviewed Jul 14, 2026

Copilot AI review requested due to automatic review settings July 15, 2026 00:02

renovate Bot force-pushed the renovate/inspektor-gadget branch from 71d797a to c0f4091 Compare July 15, 2026 00:02

Copilot AI reviewed Jul 15, 2026

Copilot AI review requested due to automatic review settings July 15, 2026 01:04

renovate Bot force-pushed the renovate/inspektor-gadget branch from c0f4091 to d3db9da Compare July 15, 2026 01:04

Copilot AI reviewed Jul 15, 2026

chore(deps): update inspektor-gadget

47cc3f3

Copilot AI review requested due to automatic review settings July 15, 2026 03:14

renovate Bot force-pushed the renovate/inspektor-gadget branch from d3db9da to 47cc3f3 Compare July 15, 2026 03:14

Copilot AI reviewed Jul 15, 2026

Uh oh!

Conversation

renovate Bot commented Jul 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Configuration

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

calvin197 left a comment

Choose a reason for hiding this comment

Uh oh!

burak-ok left a comment

Choose a reason for hiding this comment

Uh oh!

burak-ok Jul 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

aks-node-assistant Bot commented Jul 10, 2026

AgentBaker Linux gate detective

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

aks-node-assistant Bot commented Jul 14, 2026

AgentBaker Linux gate detective

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

renovate Bot commented Jul 8, 2026 •

edited

Loading