integration-service update by rh-tap-build-team[bot] · Pull Request #11330 · redhat-appstudio/infra-deployments

rh-tap-build-team · 2026-04-16T14:37:23Z

Included PRs:

feat(stoneintg-1521): snapshot controller supports ComponentGroups konflux-ci/integration-service#1515

openshift-ci · 2026-04-16T14:37:31Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rh-tap-build-team[bot]
Once this PR has been reviewed and has the lgtm label, please assign josh-everett for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

components/integration/OWNERS

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

qodo-code-review · 2026-04-16T14:38:06Z

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: label
Failed stage: Checkout PR merge ref [❌]
Failed test name: ""
Failure summary: The action failed during the PR merge ref checkout step because Git could not fetch the expected pull request merge reference. - The workflow ran `git fetch origin pull/11216/merge:pr-merge` and then attempted `git checkout pr-merge`. - Git returned `fatal: couldn't find remote ref pull/11216/merge`, meaning the remote (`origin`) does not have the `pull/11216/merge` ref available (e.g., the PR ref doesn't exist in this repo/remote context, the PR number is wrong, or the workflow is running against a remote that doesn't expose GitHub PR refs). - This caused the step to exit with code `128`, failing the action.
Relevant error logs: 1: ##[group]Runner Image Provisioner 2: Hosted Compute Agent ... 98: * [new branch] application-service -> origin/application-service 99: * [new branch] build-service -> origin/build-service 100: * [new branch] c8x-d160-stg -> origin/c8x-d160-stg 101: * [new branch] caching -> origin/caching 102: * [new branch] caching.git -> origin/caching.git 103: * [new branch] deploy-cardinality -> origin/deploy-cardinality 104: * [new branch] deploy-changes -> origin/deploy-changes 105: * [new branch] deploy-new-metrics -> origin/deploy-new-metrics 106: * [new branch] deploy-prometheus -> origin/deploy-prometheus 107: * [new branch] deploy-to-prod -> origin/deploy-to-prod 108: * [new branch] disable-alerting-on-pentest-cluster -> origin/disable-alerting-on-pentest-cluster 109: * [new branch] disable-weekend-runs-stone-prod-p02 -> origin/disable-weekend-runs-stone-prod-p02 110: * [new branch] drop-user-advisor-banner -> origin/drop-user-advisor-banner 111: * [new branch] drop_metric -> origin/drop_metric 112: * [new branch] external-secrets-operator -> origin/external-secrets-operator 113: * [new branch] fix-big-dashboards-error -> origin/fix-big-dashboards-error 114: * [new branch] fix-syncloop -> origin/fix-syncloop ... 279: GOVCS='' 280: GOVERSION='go1.24.5' 281: GOWORK='' 282: PKG_CONFIG='pkg-config' 283: ##[endgroup] 284: ##[group]Run go build -o bin/env-detector ./cmd/env-detector 285: �[36;1mgo build -o bin/env-detector ./cmd/env-detector�[0m 286: shell: /usr/bin/bash -e {0} 287: ##[endgroup] 288: ##[group]Run git fetch origin pull/11216/merge:pr-merge 289: �[36;1mgit fetch origin pull/11216/merge:pr-merge�[0m 290: �[36;1mgit checkout pr-merge�[0m 291: shell: /usr/bin/bash -e {0} 292: ##[endgroup] 293: fatal: couldn't find remote ref pull/11216/merge 294: ##[error]Process completed with exit code 128. 295: ##[group]Run actions/upload-artifact@v4

github-actions · 2026-04-16T14:38:14Z

Kustomize Render Diff

Comparing bd9a404d6 → feedadb4e

Component	Environment	Changes
`components/integration/development`	development	+2 -2
`components/integration/staging/base`	staging	+2 -2
`components/integration/staging/stone-stage-p01`	staging	+2 -2

Total: 3 components, +6 -6 lines

📋 Full diff available in the workflow summary and as a downloadable artifact.

konflux-ci-qe-bot · 2026-04-16T16:49:16Z

🤖 Pipeline Failure Analysis

Category: Test

The pipeline failed because an End-to-End test timed out while waiting for a Release Custom Resource (CR) to be created or become discoverable, indicating a functional issue within the Konflux demo application or the Release Service.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step failed because the E2E test "Maven project - Default build when Integration Test PipelineRun completes successfully should trigger creation of Release CR" timed out after 240 seconds. The test was unable to find the expected Release Custom Resource (CR) associated with a specific snapshot in the konflux-wjoi namespace.

Contributing Factors

The root cause is a functional failure in either the Konflux demo application, which is responsible for triggering the Release CR creation, or the Release Service itself, which should have created and exposed the CR. The preceding Integration Test PipelineRun completed successfully, suggesting the issue is isolated to the post-integration-test release processing. No significant errors were found in the provided diagnostic logs from other services, which otherwise could indicate an infrastructure problem.

Impact

The inability to locate the Release CR directly prevented the E2E test from completing its validation, causing it to fail and subsequently blocking the entire appstudio-e2e-tests pipeline step.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: test
Root Cause: The root cause is a functional failure in the Konflux demo application or the Release Service, which prevented the expected Release Custom Resource (CR) from being created or becoming discoverable after an Integration Test PipelineRun completed, leading to the E2E test timing out.

Logs: