Skip to content

chore: bump platform-api and hyperfleet-operator images to c882180 - #749

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift-online:mainfrom
redhat-chai-bot:bump-images-c882180
Aug 13, 2026
Merged

chore: bump platform-api and hyperfleet-operator images to c882180#749
openshift-merge-bot[bot] merged 1 commit into
openshift-online:mainfrom
redhat-chai-bot:bump-images-c882180

Conversation

@redhat-chai-bot

@redhat-chai-bot redhat-chai-bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Bump platform-api and hyperfleet-operator image references to the latest rosa-hyperfleet-api main commit (c882180ff9a18fd79f8974cd5a026df0a6cb6b5a).

This picks up changes from rosa-hyperfleet-api including:

  • PR #331 — typed error codes (RATE-LIMIT-001, etc.)
  • Several Konflux/mintmaker dependency bumps

Why

The Aug 13 nightly CI runs (ephemeral + integration) both fail on should return correct 429 response body and Retry-After header because the e2e test binary is built from latest main (which includes PR #331's updated assertions expecting RATE-LIMIT-001), but the deployed platform-api image still predates PR #331 and returns the old format.

Bumping the image references resolves the mismatch.

Changes

  • argocd/config/regional-cluster/platform-api/values.yaml — image tag
  • argocd/config/regional-cluster/hyperfleet/values.yaml — image tag + targetRevision

All updated from f7ec7d5...c882180....


AI-generated. Review for accuracy.

@typeid requested in Slack thread

Summary by CodeRabbit

  • Chores
    • Updated the HyperFleet operator to a newer release.
    • Updated the platform API service to a newer release.
    • These updates include the latest available fixes, improvements, and operational enhancements from both service builds.
    • No user-facing configuration or workflow changes are expected; the updates provide refreshed service components while maintaining existing functionality.

@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c814178a-c8d7-4eab-93ec-88afaead875b

📥 Commits

Reviewing files that changed from the base of the PR and between 92920e8 and e0a15cc.

📒 Files selected for processing (1)
  • argocd/config/regional-cluster/hyperfleet/values.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • argocd/config/regional-cluster/hyperfleet/values.yaml

📝 Walkthrough

Walkthrough

The regional cluster configuration updates the HyperFleet Argo CD source revision and operator image tag to f58b3a369751e0944721fe626a4ee8176d4ed91c. It updates the platform-api image tag to c882180ff9a18fd79f8974cd5a026df0a6cb6b5a.

Changes

Regional cluster deployment revisions

Layer / File(s) Summary
Update deployment revisions
argocd/config/regional-cluster/hyperfleet/values.yaml, argocd/config/regional-cluster/platform-api/values.yaml
The HyperFleet Argo CD source revision and operator image tag now use f58b3a369751e0944721fe626a4ee8176d4ed91c. The platform-api image tag now uses c882180ff9a18fd79f8974cd5a026df0a6cb6b5a.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Mergeability Score: ⚪ Minimal · up to e0a15

This PR updates two image references to align deployed components with the corresponding API changes; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the two updated images and the target revision, matching the pull request objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@typeid

typeid commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

/retest-required

@typeid

typeid commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

/test on-demand-e2e
/lgtm
/approve

@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 13, 2026
@redhat-chai-bot

Copy link
Copy Markdown
Contributor Author

The on-demand-e2e failure is unrelated to this PR (3-line SHA bump in ArgoCD values YAML).

Failing tests:

  • e2e-zoa: should dispatch get_nodes and complete successfully (full wait) — timed out after 300s, ZOA execution stuck in pending state
  • e2e-cli: should be able to wait for the hcp cluster to be ready — timed out after 30s, cluster response missing status object

Passing suites:

  • e2e-api: 12/12 passed (including the rate-limit error code test this PR fixes)
  • e2e-platform-monitoring: passed

Both failures are environment/infrastructure timeouts unrelated to image tag changes.

/retest-required


AI-generated. Review for accuracy.

@redhat-chai-bot

Copy link
Copy Markdown
Contributor Author

Second run, same two environment flakes — both unrelated to this PR:

  • e2e-zoa get_nodes execution stuck in pending (300s timeout) — zoa_test.go:224
  • e2e-cli cluster response missing status object (30s timeout) — cluster_test.go:496

Passing suites (unchanged): e2e-api 12/12 ✅, e2e-platform-monitoring 13/13 ✅

These two tests are flaking consistently in the on-demand environment. Retesting.

/retest-required


AI-generated. Review for accuracy.

@redhat-chai-bot

Copy link
Copy Markdown
Contributor Author

Third consecutive on-demand-e2e failure — same two environment issues, not flakes.

Suite Result Notes
e2e-api ✅ 12/12 Rate-limit test passes (validates this PR's fix)
e2e-platform-monitoring Clean
e2e-zoa ❌ 10/11 get_nodes execution stuck in pending — 300s timeout (zoa_test.go:224)
e2e-cli ❌ 8/9 cluster response missing status object — 30s timeout (cluster_test.go:496)

These two tests have failed identically across all 3 runs. The ZOA execution environment appears unable to transition executions out of pending state, and the CLI test environment isn't returning cluster status objects. Both are pre-existing on-demand environment issues unrelated to this 3-line SHA bump.

Not retesting again — the pattern is established. This PR may need /override on-demand-e2e or the on-demand environment needs investigation.


AI-generated. Review for accuracy.

platform-api: f7ec7d5 → c882180 (picks up PR openshift-online#331 typed error codes)
hyperfleet-operator: f7ec7d5 → f58b3a3 (latest available Konflux-built image)

The two components use separate Konflux pipelines with different path
triggers, so their latest built images may reference different commits.
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 13, 2026

@typeid typeid left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

/lgtm
/approve
/test on-demand-e2e

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 13, 2026
@openshift-ci

openshift-ci Bot commented Aug 13, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: typeid

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

@redhat-chai-bot

Copy link
Copy Markdown
Contributor Author

Updated: the hyperfleet-operator image tag has been corrected.

Root cause of CI failures: the hyperfleet-operator image didn't exist at c882180 — the operator's Konflux pipeline only triggers on operator-path changes, and that commit only touched API code. The operator pods were stuck in ImagePullBackOff, which cascaded into both the ZOA and CLI test failures.

Fix: hyperfleet-operator targetRevision and tag changed from c882180f58b3a3 (latest available Konflux-built operator image, verified with skopeo). Platform-api remains at c882180 (verified exists).

Verification:

Image Tag Status
platform-api c882180 ✅ exists
hyperfleet-operator c882180 manifest unknown
hyperfleet-operator f58b3a3 ✅ exists

This commit was amended and force-pushed — will need re-approval.


AI-generated. Review for accuracy.

@typeid

typeid commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

/test on-demand-e2e

@coderabbitai coderabbitai Bot mentioned this pull request Aug 13, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit d940eed into openshift-online:main Aug 13, 2026
9 checks passed
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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants