Repository: konflux-ci/release-service
Pull request #683: feat(RELEASE-1452): onboard sealights to release service
Author: login: jinqi7
Created: 2025-02-26T09:31:04Z | Merged: 2025-03-19T07:39:54Z

Added Sealights instrumentation task to the build process to enable tracking
 and monitoring of test coverage during builds. Adjusted build pipelines to
 create a new container image that includes the Sealights agent, making it
ready for instrumentation. Enabled e2e tests to sync with Sealights by
sending test reports for coverage tracking.Future improvements will include
test selection, optimizing test run times, and reducing cloud costs


Diff:
diff --git a/.dockerignore b/.dockerignore
index 0f046820f..87e8fdbef 100644
--- a/.dockerignore
+++ b/.dockerignore
@@ -2,3 +2,27 @@
 # Ignore build and test binaries.
 bin/
 testbin/
+
+# Development and test directories
+hack/
+integration-tests/
+# Comment it since network-policy.yaml is in this directory
+config/
+
+# Git and CI related files
+.github/
+.tekton/
+.gitignore
+.gitlint
+.sonarcloud.properties
+
+# Build and configuration files
+codecov.yml
+PROJECT
+Makefile
+LICENSE
+
+# Documentation files
+CODE_OF_CONDUCT.md
+CONTRIBUTING.md
+README.md
diff --git a/.tekton/release-service-pull-request.yaml b/.tekton/release-service-pull-request.yaml
index c5a14455e..23ff648d3 100644
--- a/.tekton/release-service-pull-request.yaml
+++ b/.tekton/release-service-pull-request.yaml
@@ -163,18 +163,49 @@ spec:
       workspaces:
       - name: basic-auth
         workspace: git-auth
+    - name: sealights-go-instrumentation
+      runAfter:
+        - clone-repository
+      taskRef:
+        params:
+        - name: name
+          value: sealights-go-oci-ta
+        - name: bundle
+          value: quay.io/konflux-ci/tekton-catalog/task-sealights-go-oci-ta:0.1@sha256:7c8fdf2873aee7b02feaa42f4868be55878d2d06dc3a93b1ceb77d1c6fa3fc22
+        - name: kind
+          value: task
+        resolver: bundles
+      params:
+        - name: SOURCE_ARTIFACT
+          value: $(tasks.clone-repository.results.SOURCE_ARTIFACT)
+        - name: component
+          value: '{{ repo_name }}'
+        - name: branch
+          value: '{{ source_branch }}'
+        - name: revision
+          value: '{{ revision }}'
+        - name: repository-url
+          value: '{{ repo_url }}'
+        - name: pull-request-number 
+          value: '{{pull_request_number}}'
+        - name: target-branch
+          value: '{{ target_branch }}'
+        - name: oci-storage
+          value: $(params.output-image).sealights.git
+        - name: disable-token-save
+          value: "true"
     - name: prefetch-dependencies
       params:
       - name: input
         value: $(params.prefetch-input)
       - name: SOURCE_ARTIFACT
-        value: $(tasks.clone-repository.results.SOURCE_ARTIFACT)
+        value: $(tasks.sealights-go-instrumentation.results.SOURCE_ARTIFACT)
       - name: ociStorage
         value: $(params.output-image).prefetch
       - name: ociArtifactExpiresAfter
         value: $(params.image-expires-after)
       runAfter:
-      - clone-repository
+      - sealights-go-instrumentation
       taskRef:
         params:
         - name: name
diff --git a/.tekton/release-service-push.yaml b/.tekton/release-service-push.yaml
index 5c82b4abf..237874de1 100644
--- a/.tekton/release-service-push.yaml
+++ b/.tekton/release-service-push.yaml
@@ -156,6 +156,31 @@ spec:
       workspaces:
       - name: basic-auth
         workspace: git-auth
+    - name: sealights-go-instrumentation
+      runAfter:
+        - clone-repository
+      taskRef:
+        params:
+        - name: name
+          value: sealights-go-oci-ta
+        - name: bundle
+          value: quay.io/konflux-ci/tekton-catalog/task-sealights-go-oci-ta:0.1@sha256:7c8fdf2873aee7b02feaa42f4868be55878d2d06dc3a93b1ceb77d1c6fa3fc22
+        - name: kind
+          value: task
+        resolver: bundles
+      params:
+        - name: SOURCE_ARTIFACT
+          value: $(tasks.clone-repository.results.SOURCE_ARTIFACT)
+        - name: component
+          value: '{{ repo_name }}'
+        - name: branch
+          value: '{{ source_branch }}'
+        - name: revision
+          value: '{{ revision }}'
+        - name: oci-storage
+          value: $(params.output-image).sealights.git
+        - name: disable-token-save
+          value: "true"
     - name: prefetch-dependencies
       params:
       - name: input
@@ -223,6 +248,48 @@ spec:
         operator: in
         values:
         - "true"
+    - name: build-sealights-container
+      params:
+      - name: IMAGE
+        value: $(params.output-image).sealights
+      - name: DOCKERFILE
+        value: $(params.dockerfile)
+      - name: CONTEXT
+        value: $(params.path-context)
+      - name: HERMETIC
+        value: $(params.hermetic)
+      - name: PREFETCH_INPUT
+        value: $(params.prefetch-input)
+      - name: IMAGE_EXPIRES_AFTER
+        value: $(params.image-expires-after)
+      - name: COMMIT_SHA
+        value: $(tasks.clone-repository.results.commit)
+      - name: BUILD_ARGS
+        value:
+        - $(params.build-args[*])
+      - name: BUILD_ARGS_FILE
+        value: $(params.build-args-file)
+      - name: SOURCE_ARTIFACT
+        value: $(tasks.sealights-go-instrumentation.results.SOURCE_ARTIFACT)
+      - name: CACHI2_ARTIFACT
+        value: $(tasks.prefetch-dependencies.results.CACHI2_ARTIFACT)
+      runAfter:
+      - sealights-go-instrumentation
+      - prefetch-dependencies
+      taskRef:
+        params:
+        - name: name
+          value: buildah-oci-ta
+        - name: bundle
+          value: quay.io/konflux-ci/tekton-catalog/task-buildah-oci-ta:0.4@sha256:63e57ac67f892a0e2990fc18db5c18ef5ad9de1db8df82c25d5813e2f84f5977
+        - name: kind
+          value: task
+        resolver: bundles
+      when:
+      - input: $(tasks.init.results.build)
+        operator: in
+        values:
+        - "true"
     - name: build-image-index
       params:
       - name: IMAGE
diff --git a/Dockerfile b/Dockerfile
index b7ab4faa9..f9c5baeb4 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,23 +1,17 @@
 # Build the manager binary
 FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1742197705 as builder
 
+USER 1001
+
 # Copy the Go Modules manifests
-COPY go.mod go.mod
-COPY go.sum go.sum
+COPY --chown=1001:0 go.mod go.mod
+COPY --chown=1001:0 go.sum go.sum
 # cache deps before building and copying source so that we don't need to re-download as much
 # and so that source changes don't invalidate our downloaded layer
 RUN go mod download
 
 # Copy the go source
-COPY main.go main.go
-COPY api/ api/
-COPY cache/ cache/
-COPY controllers/ controllers/
-COPY loader/ loader/
-COPY metadata/ metadata/
-COPY metrics/ metrics/
-COPY syncer/ syncer/
-COPY tekton/ tekton/
+COPY --chown=1001:0 . .
 
 # Build
 RUN CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -a -o manager main.go
@@ -37,6 +31,7 @@ LABEL io.k8s.description="Konflux Release Service"
 LABEL io.k8s.display-name="release-service"
 LABEL summary="Konflux Release Service"
 LABEL com.redhat.component="release-service"
+LABEL io.openshift.tags="konflux"
 
 USER 65532:65532
 
diff --git a/config/manager/network_policy.yaml b/config/manager/network_policy.yaml
index 6a4d682d5..b04e88844 100644
--- a/config/manager/network_policy.yaml
+++ b/config/manager/network_policy.yaml
@@ -26,3 +26,18 @@ spec:
           protocol: TCP
         - port: 443
           protocol: TCP
+    # Open traffic to SeaLights
+    - to:
+      - ipBlock:
+          cidr: 159.60.128.87/32
+      ports:
+        - port: 443
+          protocol: TCP
+    # Allow DNS queries so SeaLights can resolve the api url
+    - to:
+      - namespaceSelector:
+          matchLabels:
+            kubernetes.io/metadata.name: openshift-dns
+      ports:
+        - port: 5353
+          protocol: UDP
diff --git a/integration-tests/pipelines/konflux-e2e-tests-pipeline.yaml b/integration-tests/pipelines/konflux-e2e-tests-pipeline.yaml
index c461404b0..7e37d6969 100644
--- a/integration-tests/pipelines/konflux-e2e-tests-pipeline.yaml
+++ b/integration-tests/pipelines/konflux-e2e-tests-pipeline.yaml
@@ -17,6 +17,11 @@ spec:
     - name: test-name
       description: 'The name of the test corresponding to a defined Konflux integration test.'
       default: ''
+    - name: test-stage
+      default: 'release-service-e2e'
+      description: >-
+        "The name or identifier of the testing phase (e.g., "integration", "e2e") during which the results
+          are being captured. This helps distinguish the test results within Sealights for better reporting and traceability"
     - name: ocp-version
       description: 'The OpenShift version to use for the ephemeral cluster deployment.'
       type: string
@@ -45,7 +50,23 @@ spec:
       default: 'none'
       description: 'Container image built from any konflux git repo. Use this param only when you run Konflux e2e tests
         in another Konflux component repo. Will pass the component built image from the snapshot.'
+    - name: enable-sealights
+      description: "A flag to enable or disable the Sealights integration feature. When set to 'true', test results are sent to Sealights for analysis; otherwise, this feature is skipped."
+      default: "true"
   tasks:
+    - name: sealights-refs
+      taskRef:
+        resolver: git
+        params:
+          - name: url
+            value: https://github.com/konflux-ci/tekton-integration-catalog.git
+          - name: revision
+            value: main
+          - name: pathInRepo
+            value: tasks/sealights/sealights-get-refs/0.1/sealights-get-refs.yaml
+      params:
+        - name: SNAPSHOT
+          value: $(params.SNAPSHOT)
     - name: rosa-hcp-metadata
       taskRef:
         resolver: git
@@ -82,6 +103,7 @@ spec:
       runAfter:
         - rosa-hcp-metadata
         - test-metadata
+        - sealights-refs
       taskRef:
         resolver: git
         params:
@@ -142,7 +164,13 @@ spec:
         - name: ocp-login-command
           value: "$(tasks.provision-rosa.results.ocp-login-command)"
         - name: component-image
-          value: "$(tasks.test-metadata.results.container-image)"
+          value: $(tasks.sealights-refs.results.sealights-container-image)
+        - name: sealights-bsid
+          value: $(tasks.sealights-refs.results.sealights-bsid)
+        - name: test-stage
+          value: $(params.test-stage)
+        - name: enable-sealights
+          value: $(params.enable-sealights)
   finally:
     - name: deprovision-rosa-collect-artifacts
       when:


Reviews:
user: login: johnbieren
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-02-26T13:39:19Z
user: login: jinqi7
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-02-26T14:02:16Z
user: login: flacatus
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-02-26T14:20:18Z
user: login: johnbieren
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-02-26T14:36:38Z
user: login: flacatus
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-02-26T15:04:07Z
user: login: johnbieren
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-02-26T15:05:42Z
user: login: jinqi7
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-02-27T01:35:56Z
user: login: johnbieren
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-02-27T01:57:06Z
user: login: flacatus
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-02-27T09:43:20Z
user: login: jinqi7
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-02-27T10:09:33Z
user: login: jinqi7
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-03T03:16:04Z
user: login: psturc
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-04T18:44:50Z
user: login: jinqi7
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-05T01:20:59Z
user: login: psturc
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-05T08:54:22Z
user: login: flacatus
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-05T09:06:01Z
user: login: psturc
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-05T09:30:14Z
user: login: psturc
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-03-17T12:42:35Z
user: login: jinqi7
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-18T06:51:53Z
user: login: johnbieren
state: APPROVED
author_association: COLLABORATOR
submitted_at: 2025-03-18T20:01:50Z

Review comments:
diff_hunk: @@ -1,23 +1,16 @@
 # Build the manager binary
 FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1739801907 as builder
 
+USER 1001
 # Copy the Go Modules manifests
-COPY go.mod go.mod
-COPY go.sum go.sum
+COPY --chown=1001:0 go.mod go.mod
+COPY --chown=1001:0 go.sum go.sum
 # cache deps before building and copying source so that we don't need to re-download as much
 # and so that source changes don't invalidate our downloaded layer
 RUN go mod download
 
 # Copy the go source
-COPY main.go main.go
-COPY api/ api/
-COPY cache/ cache/
-COPY controllers/ controllers/
-COPY loader/ loader/
-COPY metadata/ metadata/
-COPY metrics/ metrics/
-COPY syncer/ syncer/
-COPY tekton/ tekton/
+COPY --chown=1001:0 . .
path: Dockerfile
user: login: johnbieren
body: With this change, we are now copying things into the image we don't really need like `hack/` and `integration-tests/pipelines`
created_at: 2025-02-26T13:39:19Z
author_association: COLLABORATOR
diff_hunk: @@ -1,23 +1,16 @@
 # Build the manager binary
 FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1739801907 as builder
 
+USER 1001
 # Copy the Go Modules manifests
-COPY go.mod go.mod
-COPY go.sum go.sum
+COPY --chown=1001:0 go.mod go.mod
+COPY --chown=1001:0 go.sum go.sum
 # cache deps before building and copying source so that we don't need to re-download as much
 # and so that source changes don't invalidate our downloaded layer
 RUN go mod download
 
 # Copy the go source
-COPY main.go main.go
-COPY api/ api/
-COPY cache/ cache/
-COPY controllers/ controllers/
-COPY loader/ loader/
-COPY metadata/ metadata/
-COPY metrics/ metrics/
-COPY syncer/ syncer/
-COPY tekton/ tekton/
+COPY --chown=1001:0 . .
path: Dockerfile
user: login: jinqi7
body: I  checked the other services and it's the same.  I guess it because sealight analyzes code coverage. @flacatus , can you help to answer it? 
created_at: 2025-02-26T14:02:16Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,23 +1,16 @@
 # Build the manager binary
 FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1739801907 as builder
 
+USER 1001
 # Copy the Go Modules manifests
-COPY go.mod go.mod
-COPY go.sum go.sum
+COPY --chown=1001:0 go.mod go.mod
+COPY --chown=1001:0 go.sum go.sum
 # cache deps before building and copying source so that we don't need to re-download as much
 # and so that source changes don't invalidate our downloaded layer
 RUN go mod download
 
 # Copy the go source
-COPY main.go main.go
-COPY api/ api/
-COPY cache/ cache/
-COPY controllers/ controllers/
-COPY loader/ loader/
-COPY metadata/ metadata/
-COPY metrics/ metrics/
-COPY syncer/ syncer/
-COPY tekton/ tekton/
+COPY --chown=1001:0 . .
path: Dockerfile
user: login: flacatus
body: you can use .dockerignore file to not copy them
created_at: 2025-02-26T14:20:18Z
author_association: MEMBER
diff_hunk: @@ -1,23 +1,16 @@
 # Build the manager binary
 FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1739801907 as builder
 
+USER 1001
 # Copy the Go Modules manifests
-COPY go.mod go.mod
-COPY go.sum go.sum
+COPY --chown=1001:0 go.mod go.mod
+COPY --chown=1001:0 go.sum go.sum
 # cache deps before building and copying source so that we don't need to re-download as much
 # and so that source changes don't invalidate our downloaded layer
 RUN go mod download
 
 # Copy the go source
-COPY main.go main.go
-COPY api/ api/
-COPY cache/ cache/
-COPY controllers/ controllers/
-COPY loader/ loader/
-COPY metadata/ metadata/
-COPY metrics/ metrics/
-COPY syncer/ syncer/
-COPY tekton/ tekton/
+COPY --chown=1001:0 . .
path: Dockerfile
user: login: johnbieren
body: Why? Why not just keep the multiple COPY directives like we have but add the `--chown` to each?
created_at: 2025-02-26T14:36:38Z
author_association: COLLABORATOR
diff_hunk: @@ -1,23 +1,16 @@
 # Build the manager binary
 FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1739801907 as builder
 
+USER 1001
 # Copy the Go Modules manifests
-COPY go.mod go.mod
-COPY go.sum go.sum
+COPY --chown=1001:0 go.mod go.mod
+COPY --chown=1001:0 go.sum go.sum
 # cache deps before building and copying source so that we don't need to re-download as much
 # and so that source changes don't invalidate our downloaded layer
 RUN go mod download
 
 # Copy the go source
-COPY main.go main.go
-COPY api/ api/
-COPY cache/ cache/
-COPY controllers/ controllers/
-COPY loader/ loader/
-COPY metadata/ metadata/
-COPY metrics/ metrics/
-COPY syncer/ syncer/
-COPY tekton/ tekton/
+COPY --chown=1001:0 . .
path: Dockerfile
user: login: flacatus
body: @johnbieren when Sealights do go instrumentation they create additional packages to your code and we need to copy it to the container in order to build
created_at: 2025-02-26T15:04:07Z
author_association: MEMBER
diff_hunk: @@ -1,23 +1,16 @@
 # Build the manager binary
 FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1739801907 as builder
 
+USER 1001
 # Copy the Go Modules manifests
-COPY go.mod go.mod
-COPY go.sum go.sum
+COPY --chown=1001:0 go.mod go.mod
+COPY --chown=1001:0 go.sum go.sum
 # cache deps before building and copying source so that we don't need to re-download as much
 # and so that source changes don't invalidate our downloaded layer
 RUN go mod download
 
 # Copy the go source
-COPY main.go main.go
-COPY api/ api/
-COPY cache/ cache/
-COPY controllers/ controllers/
-COPY loader/ loader/
-COPY metadata/ metadata/
-COPY metrics/ metrics/
-COPY syncer/ syncer/
-COPY tekton/ tekton/
+COPY --chown=1001:0 . .
path: Dockerfile
user: login: johnbieren
body: Ah, got it. The .dockerignore thing sounds good to me then
created_at: 2025-02-26T15:05:42Z
author_association: COLLABORATOR
diff_hunk: @@ -1,23 +1,16 @@
 # Build the manager binary
 FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1739801907 as builder
 
+USER 1001
 # Copy the Go Modules manifests
-COPY go.mod go.mod
-COPY go.sum go.sum
+COPY --chown=1001:0 go.mod go.mod
+COPY --chown=1001:0 go.sum go.sum
 # cache deps before building and copying source so that we don't need to re-download as much
 # and so that source changes don't invalidate our downloaded layer
 RUN go mod download
 
 # Copy the go source
-COPY main.go main.go
-COPY api/ api/
-COPY cache/ cache/
-COPY controllers/ controllers/
-COPY loader/ loader/
-COPY metadata/ metadata/
-COPY metrics/ metrics/
-COPY syncer/ syncer/
-COPY tekton/ tekton/
+COPY --chown=1001:0 . .
path: Dockerfile
user: login: jinqi7
body: Do we need `config\` included in .dockerignore file? And I saw only `release-in-cluster-local` Degraded during konflux deployment in the PR's test. Not sure what may cause it?
created_at: 2025-02-27T01:35:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,23 +1,16 @@
 # Build the manager binary
 FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1739801907 as builder
 
+USER 1001
 # Copy the Go Modules manifests
-COPY go.mod go.mod
-COPY go.sum go.sum
+COPY --chown=1001:0 go.mod go.mod
+COPY --chown=1001:0 go.sum go.sum
 # cache deps before building and copying source so that we don't need to re-download as much
 # and so that source changes don't invalidate our downloaded layer
 RUN go mod download
 
 # Copy the go source
-COPY main.go main.go
-COPY api/ api/
-COPY cache/ cache/
-COPY controllers/ controllers/
-COPY loader/ loader/
-COPY metadata/ metadata/
-COPY metrics/ metrics/
-COPY syncer/ syncer/
-COPY tekton/ tekton/
+COPY --chown=1001:0 . .
path: Dockerfile
user: login: johnbieren
body: I mean anything that is not currently in a COPY directive but exists in the root of the repo I'd think should be added to the ignore
created_at: 2025-02-27T01:57:06Z
author_association: COLLABORATOR
diff_hunk: @@ -45,7 +50,23 @@ spec:
       default: 'none'
       description: 'Container image built from any konflux git repo. Use this param only when you run Konflux e2e tests
         in another Konflux component repo. Will pass the component built image from the snapshot.'
+    - name: enable-sealights
+      description: "A flag to enable or disable the Sealights integration feature. When set to 'true', test results are sent to Sealights for analysis; otherwise, this feature is skipped."
+      default: "true"
   tasks:
+    - name: sealights-refs
path: integration-tests/pipelines/konflux-e2e-tests-pipeline.yaml
user: login: flacatus
body: for some reason I dont see this task creating in ur pipelines
created_at: 2025-02-27T09:43:19Z
author_association: MEMBER
diff_hunk: @@ -45,7 +50,23 @@ spec:
       default: 'none'
       description: 'Container image built from any konflux git repo. Use this param only when you run Konflux e2e tests
         in another Konflux component repo. Will pass the component built image from the snapshot.'
+    - name: enable-sealights
+      description: "A flag to enable or disable the Sealights integration feature. When set to 'true', test results are sent to Sealights for analysis; otherwise, this feature is skipped."
+      default: "true"
   tasks:
+    - name: sealights-refs
path: integration-tests/pipelines/konflux-e2e-tests-pipeline.yaml
user: login: jinqi7
body: Because we haven't merge this PR yet and "main" branch is being used for the pipeline in the IntegrationTestScenario CR. 
created_at: 2025-02-27T10:09:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,23 +1,16 @@
 # Build the manager binary
 FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1739801907 as builder
 
+USER 1001
 # Copy the Go Modules manifests
-COPY go.mod go.mod
-COPY go.sum go.sum
+COPY --chown=1001:0 go.mod go.mod
+COPY --chown=1001:0 go.sum go.sum
 # cache deps before building and copying source so that we don't need to re-download as much
 # and so that source changes don't invalidate our downloaded layer
 RUN go mod download
 
 # Copy the go source
-COPY main.go main.go
-COPY api/ api/
-COPY cache/ cache/
-COPY controllers/ controllers/
-COPY loader/ loader/
-COPY metadata/ metadata/
-COPY metrics/ metrics/
-COPY syncer/ syncer/
-COPY tekton/ tekton/
+COPY --chown=1001:0 . .
path: Dockerfile
user: login: jinqi7
body: But the network_policy.yaml file is under config/manager dir.  If `config/` is in .dockerignore, how the change of network_policy.yaml affect the operator deployment?   
created_at: 2025-03-03T03:16:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -156,18 +156,41 @@ spec:
       workspaces:
       - name: basic-auth
         workspace: git-auth
+    - name: sealights-go-instrumentation
+      runAfter:
+        - clone-repository
+      taskRef:
+        params:
+        - name: name
+          value: sealights-go-oci-ta
+        - name: bundle
+          value: quay.io/konflux-ci/tekton-catalog/task-sealights-go-oci-ta:0.1@sha256:5c31f32ea625b3a7419d7a6994bfa2cce477d3050c0c145dc14a47302feb253e
+        - name: kind
+          value: task
+        resolver: bundles
+      params:
+        - name: SOURCE_ARTIFACT
+          value: $(tasks.clone-repository.results.SOURCE_ARTIFACT)
+        - name: component
+          value: '{{ repo_name }}'
+        - name: branch
+          value: '{{ source_branch }}'
+        - name: revision
+          value: '{{ revision }}'
+        - name: oci-storage
+          value: $(params.output-image).sealights.git
     - name: prefetch-dependencies
       params:
       - name: input
         value: $(params.prefetch-input)
       - name: SOURCE_ARTIFACT
-        value: $(tasks.clone-repository.results.SOURCE_ARTIFACT)
+        value: $(tasks.sealights-go-instrumentation.results.SOURCE_ARTIFACT)
path: .tekton/release-service-push.yaml
user: login: psturc
body: I think for **push** pipeline, we should keep the source artifact as is. Otherwise the `build-container` Task (below) would build a pristine image with Sealights instrumentation files in it.
created_at: 2025-03-04T18:44:49Z
author_association: MEMBER
diff_hunk: @@ -156,18 +156,41 @@ spec:
       workspaces:
       - name: basic-auth
         workspace: git-auth
+    - name: sealights-go-instrumentation
+      runAfter:
+        - clone-repository
+      taskRef:
+        params:
+        - name: name
+          value: sealights-go-oci-ta
+        - name: bundle
+          value: quay.io/konflux-ci/tekton-catalog/task-sealights-go-oci-ta:0.1@sha256:5c31f32ea625b3a7419d7a6994bfa2cce477d3050c0c145dc14a47302feb253e
+        - name: kind
+          value: task
+        resolver: bundles
+      params:
+        - name: SOURCE_ARTIFACT
+          value: $(tasks.clone-repository.results.SOURCE_ARTIFACT)
+        - name: component
+          value: '{{ repo_name }}'
+        - name: branch
+          value: '{{ source_branch }}'
+        - name: revision
+          value: '{{ revision }}'
+        - name: oci-storage
+          value: $(params.output-image).sealights.git
     - name: prefetch-dependencies
       params:
       - name: input
         value: $(params.prefetch-input)
       - name: SOURCE_ARTIFACT
-        value: $(tasks.clone-repository.results.SOURCE_ARTIFACT)
+        value: $(tasks.sealights-go-instrumentation.results.SOURCE_ARTIFACT)
path: .tekton/release-service-push.yaml
user: login: jinqi7
body: Right. Updated!  Thanks
created_at: 2025-03-05T01:20:59Z
author_association: CONTRIBUTOR
diff_hunk: @@ -223,6 +246,48 @@ spec:
         operator: in
         values:
         - "true"
+    - name: build-sealights-container
+      params:
+      - name: IMAGE
+        value: $(params.output-image).sealights
+      - name: DOCKERFILE
+        value: $(params.dockerfile)
+      - name: CONTEXT
+        value: $(params.path-context)
+      - name: HERMETIC
+        value: $(params.hermetic)
+      - name: PREFETCH_INPUT
+        value: $(params.prefetch-input)
+      - name: IMAGE_EXPIRES_AFTER
+        value: $(params.image-expires-after)
+      - name: COMMIT_SHA
+        value: $(tasks.clone-repository.results.commit)
+      - name: BUILD_ARGS
+        value:
+        - $(params.build-args[*])
+      - name: BUILD_ARGS_FILE
+        value: $(params.build-args-file)
+      - name: SOURCE_ARTIFACT
+        value: $(tasks.sealights-go-instrumentation.results.SOURCE_ARTIFACT)
+      - name: CACHI2_ARTIFACT
+        value: $(tasks.prefetch-dependencies.results.CACHI2_ARTIFACT)
+      runAfter:
+      - sealights-go-instrumentation
+      - prefetch-dependencies
path: .tekton/release-service-push.yaml
user: login: psturc
body: I think this Task now doesn't depend on `prefetch-dependencies` Task in "push" PipelineRun
created_at: 2025-03-05T08:54:21Z
author_association: MEMBER
diff_hunk: @@ -223,6 +246,48 @@ spec:
         operator: in
         values:
         - "true"
+    - name: build-sealights-container
+      params:
+      - name: IMAGE
+        value: $(params.output-image).sealights
+      - name: DOCKERFILE
+        value: $(params.dockerfile)
+      - name: CONTEXT
+        value: $(params.path-context)
+      - name: HERMETIC
+        value: $(params.hermetic)
+      - name: PREFETCH_INPUT
+        value: $(params.prefetch-input)
+      - name: IMAGE_EXPIRES_AFTER
+        value: $(params.image-expires-after)
+      - name: COMMIT_SHA
+        value: $(tasks.clone-repository.results.commit)
+      - name: BUILD_ARGS
+        value:
+        - $(params.build-args[*])
+      - name: BUILD_ARGS_FILE
+        value: $(params.build-args-file)
+      - name: SOURCE_ARTIFACT
+        value: $(tasks.sealights-go-instrumentation.results.SOURCE_ARTIFACT)
+      - name: CACHI2_ARTIFACT
+        value: $(tasks.prefetch-dependencies.results.CACHI2_ARTIFACT)
+      runAfter:
+      - sealights-go-instrumentation
+      - prefetch-dependencies
path: .tekton/release-service-push.yaml
user: login: flacatus
body: Should depends on preferch-dependencies due that is using a result from there tasks.prefetch-dependencies.results.CACHI2_ARTIFACT
created_at: 2025-03-05T09:06:00Z
author_association: MEMBER
diff_hunk: @@ -223,6 +246,48 @@ spec:
         operator: in
         values:
         - "true"
+    - name: build-sealights-container
+      params:
+      - name: IMAGE
+        value: $(params.output-image).sealights
+      - name: DOCKERFILE
+        value: $(params.dockerfile)
+      - name: CONTEXT
+        value: $(params.path-context)
+      - name: HERMETIC
+        value: $(params.hermetic)
+      - name: PREFETCH_INPUT
+        value: $(params.prefetch-input)
+      - name: IMAGE_EXPIRES_AFTER
+        value: $(params.image-expires-after)
+      - name: COMMIT_SHA
+        value: $(tasks.clone-repository.results.commit)
+      - name: BUILD_ARGS
+        value:
+        - $(params.build-args[*])
+      - name: BUILD_ARGS_FILE
+        value: $(params.build-args-file)
+      - name: SOURCE_ARTIFACT
+        value: $(tasks.sealights-go-instrumentation.results.SOURCE_ARTIFACT)
+      - name: CACHI2_ARTIFACT
+        value: $(tasks.prefetch-dependencies.results.CACHI2_ARTIFACT)
+      runAfter:
+      - sealights-go-instrumentation
+      - prefetch-dependencies
path: .tekton/release-service-push.yaml
user: login: psturc
body: Ah ok you're right.

Looking at the logs, it seems like we don't need the `prefetch-dependencies` Task though:
```
step-prefetch-dependencies :-
No prefetch will be performed because no input was provided for cachi2 fetch-deps
```

But I guess it's ok to keep it.
created_at: 2025-03-05T09:30:14Z
author_association: MEMBER
diff_hunk: @@ -163,18 +163,47 @@ spec:
       workspaces:
       - name: basic-auth
         workspace: git-auth
+    - name: sealights-go-instrumentation
+      runAfter:
+        - clone-repository
+      taskRef:
+        params:
+        - name: name
+          value: sealights-go-oci-ta
+        - name: bundle
+          value: quay.io/konflux-ci/tekton-catalog/task-sealights-go-oci-ta:0.1@sha256:5c31f32ea625b3a7419d7a6994bfa2cce477d3050c0c145dc14a47302feb253e
+        - name: kind
+          value: task
+        resolver: bundles
+      params:
+        - name: SOURCE_ARTIFACT
+          value: $(tasks.clone-repository.results.SOURCE_ARTIFACT)
+        - name: component
+          value: '{{ repo_name }}'
+        - name: branch
+          value: '{{ source_branch }}'
+        - name: revision
+          value: '{{ revision }}'
+        - name: repository-url
+          value: '{{ repo_url }}'
+        - name: pull-request-number 
+          value: '{{pull_request_number}}'
+        - name: target-branch
+          value: '{{ target_branch }}'
+        - name: oci-storage
+          value: $(params.output-image).sealights.git
path: .tekton/release-service-pull-request.yaml
user: login: psturc
body: Hi @jinqi7 could you please update the image sha and add `disable-token-save` parameter here similarly like [here](https://github.com/konflux-ci/image-controller/pull/188/files#diff-d05874b2e54b1e8bdd95161807da489eaaad9102d9c38927f0f0fff65ab679fdR178-R200) in on-pr pipeline and in push pipelinerun manifest as well (it's needed for [this task](https://issues.redhat.com/browse/KFLUXDP-180))?
created_at: 2025-03-17T12:42:35Z
author_association: MEMBER
diff_hunk: @@ -163,18 +163,47 @@ spec:
       workspaces:
       - name: basic-auth
         workspace: git-auth
+    - name: sealights-go-instrumentation
+      runAfter:
+        - clone-repository
+      taskRef:
+        params:
+        - name: name
+          value: sealights-go-oci-ta
+        - name: bundle
+          value: quay.io/konflux-ci/tekton-catalog/task-sealights-go-oci-ta:0.1@sha256:5c31f32ea625b3a7419d7a6994bfa2cce477d3050c0c145dc14a47302feb253e
+        - name: kind
+          value: task
+        resolver: bundles
+      params:
+        - name: SOURCE_ARTIFACT
+          value: $(tasks.clone-repository.results.SOURCE_ARTIFACT)
+        - name: component
+          value: '{{ repo_name }}'
+        - name: branch
+          value: '{{ source_branch }}'
+        - name: revision
+          value: '{{ revision }}'
+        - name: repository-url
+          value: '{{ repo_url }}'
+        - name: pull-request-number 
+          value: '{{pull_request_number}}'
+        - name: target-branch
+          value: '{{ target_branch }}'
+        - name: oci-storage
+          value: $(params.output-image).sealights.git
path: .tekton/release-service-pull-request.yaml
user: login: jinqi7
body: Updated, thanks
created_at: 2025-03-18T06:51:53Z
author_association: CONTRIBUTOR

PR comments:
user: login: openshift-ci[bot]
created_at: 2025-02-26T09:31:08Z
body: Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with `/test all`
author_association: NONE
user: login: codecov[bot]
created_at: 2025-02-26T09:35:00Z
body: ## [Codecov](https://app.codecov.io/gh/konflux-ci/release-service/pull/683?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=konflux-ci) Report
All modified and coverable lines are covered by tests :white_check_mark:
> Project coverage is 77.71%. Comparing base [(`f1cc9bd`)](https://app.codecov.io/gh/konflux-ci/release-service/commit/f1cc9bd9251546a9a1e612cc77669fc4af67709f?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=konflux-ci) to head [(`fe5382b`)](https://app.codecov.io/gh/konflux-ci/release-service/commit/fe5382b183861288aff75e239df7cd1b319d0029?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=konflux-ci).
> Report is 54 commits behind head on main.

<details><summary>Additional details and impacted files</summary>


```diff
@@            Coverage Diff             @@
##             main     #683      +/-   ##
==========================================
- Coverage   79.23%   77.71%   -1.53%     
==========================================
  Files          28       28              
  Lines        2283     2849     +566     
==========================================
+ Hits         1809     2214     +405     
- Misses        389      532     +143     
- Partials       85      103      +18     
```

</details>

[:umbrella: View full report in Codecov by Sentry](https://app.codecov.io/gh/konflux-ci/release-service/pull/683?dropdown=coverage&src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=konflux-ci).   
:loudspeaker: Have feedback on the report? [Share it here](https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=konflux-ci).

<details><summary>🚀 New features to boost your workflow: </summary>

- ❄ [Test Analytics](https://docs.codecov.com/docs/test-analytics): Detect flaky tests, report on failures, and find test suite problems.
</details>
author_association: NONE
user: login: jinqi7
created_at: 2025-02-26T09:51:23Z
body: /test
author_association: CONTRIBUTOR
user: login: openshift-ci[bot]
created_at: 2025-02-26T09:51:26Z
body: @jinqi7: The `/test` command needs one or more targets.
The following commands are available to trigger required jobs:
```
/test images
```

The following commands are available to trigger optional jobs:
```
/test release-service-e2e
```

Use `/test all` to run the following jobs that were automatically triggered:
```
pull-ci-konflux-ci-release-service-main-images
```



<details>

In response to [this](https://github.com/konflux-ci/release-service/pull/683#issuecomment-2684460392):

>/test


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: jinqi7
created_at: 2025-02-26T12:55:34Z
body: /retest
author_association: CONTRIBUTOR
user: login: mmalina
created_at: 2025-02-26T14:35:17Z
body: @jinqi7 could you add some more description? What is sealights? Would be nice to have more details without having to go to Jira.
author_association: COLLABORATOR
user: login: flacatus
created_at: 2025-02-27T00:17:13Z
body: /retest
author_association: MEMBER
user: login: jinqi7
created_at: 2025-02-27T03:33:39Z
body: /retest
author_association: CONTRIBUTOR
user: login: jinqi7
created_at: 2025-02-27T10:22:45Z
body: /retest
author_association: CONTRIBUTOR
user: login: flacatus
created_at: 2025-02-27T13:11:08Z
body: /retest
author_association: MEMBER
user: login: flacatus
created_at: 2025-02-27T15:10:32Z
body: @johnbieren @jinqi7 Can this network policy https://github.com/konflux-ci/release-service/blob/main/config/manager/network_policy.yaml to block traffic to redhat.sealights.co?
author_association: MEMBER
user: login: johnbieren
created_at: 2025-02-27T15:29:26Z
body: > @johnbieren @jinqi7 Can this network policy https://github.com/konflux-ci/release-service/blob/main/config/manager/network_policy.yaml to block traffic to redhat.sealights.co?

I have no idea, I didn't work on that. @happybhati ?
author_association: COLLABORATOR
user: login: happybhati
created_at: 2025-02-27T16:32:23Z
body: > @johnbieren @jinqi7 Can this network policy https://github.com/konflux-ci/release-service/blob/main/config/manager/network_policy.yaml to block traffic to redhat.sealights.co?

@flacatus We have Egress Network Policy to block all outgoing(Egress) traffic
from release service pod(controller-manager)

- The "spec.podSelector" contains the name of a pod on which we want to apply network policy

- "spec.egress" have Whitelist rules to allow the necessary traffic to certain pods and namespaces.
author_association: COLLABORATOR
user: login: happybhati
created_at: 2025-02-27T16:46:32Z
body: If you need the agents to reach an external SeaLights server, you’d have to update the egress section to include an ipBlock or namespaceSelector that covers the external endpoint’s IP range and port. For example:

```
- to:
  - ipBlock:
      cidr: <SeaLights-server-IP-range>  # e.g., 203.0.113.0/24
  ports:
    - port: 443  # Or whatever port SeaLights uses
      protocol: TCP
```
Without such an addition, the agents are stuck inside the cluster’s restricted network boundaries.
author_association: COLLABORATOR
user: login: flacatus
created_at: 2025-02-27T18:24:53Z
body: Can we disable this network policy for development? @johnbieren @happybhati 
author_association: MEMBER
user: login: happybhati
created_at: 2025-02-27T18:51:12Z
body: I am not sure about disabling,
it was a prod sec requirement for the threat model of release service to have an egress network policy in place.


![Screenshot 2025-02-27 at 1 48 29 PM](https://github.com/user-attachments/assets/7d35c66e-5d2c-4e41-8178-aaadcf9d8ce3)

author_association: COLLABORATOR
user: login: jinqi7
created_at: 2025-02-28T08:14:39Z
body: I did several tests  with adding below IP range and port ( 6443/443 and 443/80).  It didn't work.   But it really works with disabling net work policy.  
 ```
- to:
      - ipBlock:
          cidr: 159.60.128.0/24  # CIDR of Sealight server Endpoint.
      ports:
        - port: 6443
          protocol: TCP
        - port: 443
          protocol: TCP
```


author_association: CONTRIBUTOR
user: login: jinqi7
created_at: 2025-02-28T12:04:37Z
body: /retest
author_association: CONTRIBUTOR
user: login: jinqi7
created_at: 2025-03-05T06:49:14Z
body: /retest
author_association: CONTRIBUTOR
user: login: jinqi7
created_at: 2025-03-09T13:59:57Z
body: /retest
author_association: CONTRIBUTOR
user: login: jinqi7
created_at: 2025-03-10T03:48:53Z
body: /retest
author_association: CONTRIBUTOR
user: login: jinqi7
created_at: 2025-03-10T04:46:32Z
body: /retest
author_association: CONTRIBUTOR
user: login: jinqi7
created_at: 2025-03-10T23:34:47Z
body: /retest
author_association: CONTRIBUTOR
user: login: jinqi7
created_at: 2025-03-12T01:40:11Z
body: /retest
author_association: CONTRIBUTOR
user: login: psturc
created_at: 2025-03-12T05:25:10Z
body: FYI note that the error reported by the test analyzer is misleading due to [this bug](https://issues.redhat.com/browse/KFLUXDP-199)

In fact the test failed on release service and integration argo apps being degraded:
```
Waiting 10 seconds for application sync
integration-in-cluster-local                       Synced      Degraded
release-in-cluster-local                           OutOfSync   Degraded
```
author_association: MEMBER
user: login: psturc
created_at: 2025-03-12T07:55:53Z
body: @jinqi7 

1. integration-service pod is failing on
```
{"level":"error","ts":"2025-03-12T07:44:01Z","logger":"setup","caller":"cmd/main.go:117","msg":"unable to setup controllers","error":"no matches for kind \"ReleasePlan\" in version \"appstudio.redhat.com/v1alpha1\"","stacktrace":"main.main\n\t/opt/app-root/src/cmd/main.go:117\nruntime.main\n\t/usr/lib/golang/src/runtime/proc.go:271"}
```

2. release-service pod is failing on
```
2025-03-12T07:48:56.308Z ERROR setup unable to start manager {"error": "failed to determine if *v1alpha1.ReleasePlan is namespaced: failed to get restmapping: no matches for kind \"ReleasePlan\" in version \"appstudio.redhat.com/v1alpha1\""}
main.main
/opt/app-root/src/main.go:181
runtime.main
/usr/lib/golang/src/runtime/proc.go:271
```

would it rather make more sense to test the deployment on some long-running cluster than requesting a new rosa cluster for each attempt?
author_association: MEMBER
user: login: jinqi7
created_at: 2025-03-12T10:30:50Z
body: > @jinqi7
> 
>     1. integration-service pod is failing on
> 
> 
> ```
> {"level":"error","ts":"2025-03-12T07:44:01Z","logger":"setup","caller":"cmd/main.go:117","msg":"unable to setup controllers","error":"no matches for kind \"ReleasePlan\" in version \"appstudio.redhat.com/v1alpha1\"","stacktrace":"main.main\n\t/opt/app-root/src/cmd/main.go:117\nruntime.main\n\t/usr/lib/golang/src/runtime/proc.go:271"}
> ```
> 
>     2. release-service pod is failing on
> 
> 
> ```
> 2025-03-12T07:48:56.308Z ERROR setup unable to start manager {"error": "failed to determine if *v1alpha1.ReleasePlan is namespaced: failed to get restmapping: no matches for kind \"ReleasePlan\" in version \"appstudio.redhat.com/v1alpha1\""}
> main.main
> /opt/app-root/src/main.go:181
> runtime.main
> /usr/lib/golang/src/runtime/proc.go:271
> ```
> 
> would it rather make more sense to test the deployment on some long-running cluster than requesting a new rosa cluster for each attempt?

The error message you pasted happened in other PRs ( https://github.com/konflux-ci/release-service/pull/684) also, even in other repo. I tried to deploy konflux in a cluster I requested and it can be deployed successfully. 
author_association: CONTRIBUTOR
user: login: psturc
created_at: 2025-03-12T11:09:07Z
body: > > @jinqi7
> > ```
> > 1. integration-service pod is failing on
> > ```
> > 
> > 
> >     
> >       
> >     
> > 
> >       
> >     
> > 
> >     
> >   
> > ```
> > {"level":"error","ts":"2025-03-12T07:44:01Z","logger":"setup","caller":"cmd/main.go:117","msg":"unable to setup controllers","error":"no matches for kind \"ReleasePlan\" in version \"appstudio.redhat.com/v1alpha1\"","stacktrace":"main.main\n\t/opt/app-root/src/cmd/main.go:117\nruntime.main\n\t/usr/lib/golang/src/runtime/proc.go:271"}
> > ```
> > 
> > 
> >     
> >       
> >     
> > 
> >       
> >     
> > 
> >     
> >   
> > ```
> > 2. release-service pod is failing on
> > ```
> > 
> > 
> >     
> >       
> >     
> > 
> >       
> >     
> > 
> >     
> >   
> > ```
> > 2025-03-12T07:48:56.308Z ERROR setup unable to start manager {"error": "failed to determine if *v1alpha1.ReleasePlan is namespaced: failed to get restmapping: no matches for kind \"ReleasePlan\" in version \"appstudio.redhat.com/v1alpha1\""}
> > main.main
> > /opt/app-root/src/main.go:181
> > runtime.main
> > /usr/lib/golang/src/runtime/proc.go:271
> > ```
> > 
> > 
> >     
> >       
> >     
> > 
> >       
> >     
> > 
> >     
> >   
> > would it rather make more sense to test the deployment on some long-running cluster than requesting a new rosa cluster for each attempt?
> 
> The error message you pasted happened in other PRs ( #684) also, even in other repo. I tried to deploy konflux in a cluster I requested and it can be deployed successfully.

That is pretty strange I see that it failed also on openshift-ci cluster and I can see in [the gather-extra script output](https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/konflux-ci_release-service/684/pull-ci-konflux-ci-release-service-main-release-service-e2e/1899125267964628992/artifacts/release-service-e2e/redhat-appstudio-gather/build-log.txt) that the ReleasePlan CRD is indeed missing
```
error: the server doesn't have a resource type "releaseplans"
```
author_association: MEMBER
user: login: jinqi7
created_at: 2025-03-13T10:46:33Z
body: /retest
author_association: CONTRIBUTOR
user: login: jinqi7
created_at: 2025-03-13T11:04:22Z
body: /retest
author_association: CONTRIBUTOR
user: login: konflux-ci-qe-bot
created_at: 2025-03-13T13:15:44Z
body: @jinqi7: The following test has Failed, say **/retest** to rerun failed tests.

| PipelineRun Name | Status | Rerun command | Build Log | Test Log |
|------------------|--------|---------------|-----------|----------|
| `konflux-e2e-tests-8cm8h`    | **Failed** | `/retest` | [View Pipeline Log](https://console.redhat.com/application-pipeline/ns/rhtap-release-2-tenant/pipelinerun/release-service-on-pull-request-4b5mx) | [View Test Logs](https://console.redhat.com/application-pipeline/ns/rhtap-release-2-tenant/pipelinerun/konflux-e2e-tests-8cm8h) |

### Inspecting Test Artifacts
To inspect your test artifacts, follow these steps:
1. Install **ORAS** (see the [ORAS installation guide](https://oras.land/docs/installation)).
2. Download artifacts with the following commands:

```sh
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/release-service:konflux-e2e-tests-8cm8h
```
### Test results analysis
:rotating_light: **Failed to provision a cluster, see the log for more details**: 

 <details><summary>Click to view logs</summary><br>
<pre>INFO: Log in to your Red Hat account...
INFO: Configure AWS Credentials...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
INFO: Logged in as 'konflux-ci-418295695583' on 'https://api.openshift.com'
INFO: Create ROSA with HCP cluster...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
time=2025-03-13T09:54:48Z level=info msg=Ignored check for policy key 'sts_hcp_ec2_registry_permission_policy' (zero egress feature toggle is not enabled)
INFO: Creating cluster 'kx-bcd58379e3'
INFO: To view a list of clusters and their status, run 'rosa list clusters'
INFO: Cluster 'kx-bcd58379e3' has been created.
INFO: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information.

Name:                       kx-bcd58379e3
Domain Prefix:              kx-bcd58379e3
Display Name:               kx-bcd58379e3
ID:                         2hg5qruip2657fpqgujr82ru0668sm4s
External ID:                81e704df-b5d6-41c8-b593-96906297c42f
Control Plane:              ROSA Service Hosted
OpenShift Version:          4.15.46
Channel Group:              stable
DNS:                        Not ready
AWS Account:                418295695583
AWS Billing Account:        418295695583
API URL:                    
Console URL:                
Region:                     us-east-1
Availability:
 - Control Plane:           MultiAZ
 - Data Plane:              SingleAZ

Nodes:
 - Compute (desired):       3
 - Compute (current):       0
Network:
 - Type:                    OVNKubernetes
 - Service CIDR:            172.30.0.0/16
 - Machine CIDR:            10.0.0.0/16
 - Pod CIDR:                10.128.0.0/14
 - Host Prefix:             /23
 - Subnets:                 subnet-05b9daa0609597f68, subnet-04cf6376374bf9e09
EC2 Metadata Http Tokens:   optional
Role (STS) ARN:             arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Installer-Role
Support Role ARN:           arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Support-Role
Instance IAM Roles:
 - Worker:                  arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Worker-Role
Operator IAM Roles:
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cloud-network-config-controller-cloud-credent
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kube-controller-manager
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-capa-controller-manager
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-control-plane-operator
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kms-provider
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-image-registry-installer-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-ingress-operator-cloud-credentials
Managed Policies:           Yes
State:                      waiting (Waiting for user action)
Private:                    No
Delete Protection:          Disabled
Created:                    Mar 13 2025 09:55:00 UTC
User Workload Monitoring:   Enabled
Details Page:               https://console.redhat.com/openshift/details/s/2uG0ejrsZxAguHPwNXF2lnYL9HO
OIDC Endpoint URL:          https://oidc.op1.openshiftapps.com/2du11g36ejmoo4624pofphlrgf4r9tf3 (Managed)
Etcd Encryption:            Disabled
Audit Log Forwarding:       Disabled
External Authentication:    Disabled
Zero Egress:                Disabled


INFO: Preparing to create operator roles.
INFO: Operator Roles already exists
INFO: Preparing to create OIDC Provider.
INFO: OIDC provider already exists
INFO: To determine when your cluster is Ready, run 'rosa describe cluster -c kx-bcd58379e3'.
INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-bcd58379e3 --watch'.
INFO: Track the progress of the cluster creation...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
[0;33mW:[m Region flag will be removed from this command in future versions
INFO: Cluster 'kx-bcd58379e3' is in waiting state waiting for installation to begin. Logs will show up within 5 minutes
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-bcd58379e3 Version 
2025-03-13 10:00:37 +0000 UTC hostedclusters kx-bcd58379e3 ValidAWSIdentityProvider StatusUnknown
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Condition not found in the CVO.
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Condition not found in the CVO.
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Condition not found in the CVO.
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Waiting for hosted control plane to be healthy
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Condition not found in the CVO.
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Condition not found in the CVO.
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Ignition server deployment not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Configuration passes validation
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 HostedCluster is supported by operator configuration
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Release image is valid
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Reconciliation active on resource
2025-03-13 10:00:44 +0000 UTC hostedclusters kx-bcd58379e3 HostedCluster is at expected version
2025-03-13 10:00:47 +0000 UTC hostedclusters kx-bcd58379e3 Required platform credentials are found
2025-03-13 10:00:47 +0000 UTC hostedclusters kx-bcd58379e3 failed to get referenced secret ocm-production-2hg5qruip2657fpqgujr82ru0668sm4s/cluster-api-cert: Secret "cluster-api-cert" not found
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-bcd58379e3 Version 
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Condition not found in the CVO.
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Condition not found in the CVO.
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Condition not found in the CVO.
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Condition not found in the CVO.
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Reconciliation active on resource
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Condition not found in the CVO.
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Ignition server deployment not found
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Configuration passes validation
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 HostedCluster is supported by operator configuration
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Waiting for hosted control plane to be healthy
2025-03-13 10:00:41 +0000 UTC hostedclusters kx-bcd58379e3 Release image is valid
2025-03-13 10:00:44 +0000 UTC hostedclusters kx-bcd58379e3 HostedCluster is at expected version
2025-03-13 10:00:47 +0000 UTC hostedclusters kx-bcd58379e3 Required platform credentials are found
2025-03-13 10:02:25 +0000 UTC hostedclusters kx-bcd58379e3 Reconciliation completed successfully
2025-03-13 10:02:25 +0000 UTC hostedclusters kx-bcd58379e3 OIDC configuration is valid
2025-03-13 10:02:26 +0000 UTC hostedclusters kx-bcd58379e3 WebIdentityErr
2025-03-13 10:02:28 +0000 UTC hostedclusters kx-bcd58379e3 All is well
2025-03-13 10:02:28 +0000 UTC hostedclusters kx-bcd58379e3 lookup api.kx-bcd58379e3.vq1e.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-03-13 10:02:28 +0000 UTC hostedclusters kx-bcd58379e3 capi-provider deployment has 1 unavailable replicas
2025-03-13 10:02:28 +0000 UTC hostedclusters kx-bcd58379e3 Configuration passes validation
2025-03-13 10:02:28 +0000 UTC hostedclusters kx-bcd58379e3 AWS KMS is not configured
2025-03-13 10:02:28 +0000 UTC hostedclusters kx-bcd58379e3 Waiting for etcd to reach quorum
2025-03-13 10:02:28 +0000 UTC hostedclusters kx-bcd58379e3 Kube APIServer deployment not found
2025-03-13 10:02:36 +0000 UTC hostedclusters kx-bcd58379e3 All is well
2025-03-13 10:03:24 +0000 UTC hostedclusters kx-bcd58379e3 EtcdAvailable QuorumAvailable
2025-03-13 10:04:25 +0000 UTC hostedclusters kx-bcd58379e3 Kube APIServer deployment is available
2025-03-13 10:04:26 +0000 UTC hostedclusters kx-bcd58379e3 All is well
2025-03-13 10:04:51 +0000 UTC hostedclusters kx-bcd58379e3 All is well
2025-03-13 10:04:51 +0000 UTC hostedclusters kx-bcd58379e3 [catalog-operator deployment has 1 unavailable replicas, certified-operators-catalog deployment has 1 unavailable replicas, cloud-credential-operator deployment has 1 unavailable replicas, cluster-network-operator deployment has 1 unavailable replicas, cluster-storage-operator deployment has 1 unavailable replicas, cluster-version-operator deployment has 1 unavailable replicas, community-operators-catalog deployment has 1 unavailable replicas, csi-snapshot-controller-operator deployment has 1 unavailable replicas, dns-operator deployment has 1 unavailable replicas, hosted-cluster-config-operator deployment has 1 unavailable replicas, ingress-operator deployment has 1 unavailable replicas, machine-approver deployment has 1 unavailable replicas, oauth-openshift deployment has 2 unavailable replicas, olm-operator deployment has 1 unavailable replicas, packageserver deployment has 3 unavailable replicas, redhat-marketplace-catalog deployment has 1 unavailable replicas, redhat-operators-catalog deployment has 1 unavailable replicas, router deployment has 2 unavailable replicas]
2025-03-13 10:05:04 +0000 UTC hostedclusters kx-bcd58379e3 ClusterVersionSucceeding FromClusterVersion
2025-03-13 10:05:04 +0000 UTC hostedclusters kx-bcd58379e3 ClusterVersionAvailable FromClusterVersion
2025-03-13 10:05:04 +0000 UTC hostedclusters kx-bcd58379e3 Condition not found in the CVO.
2025-03-13 10:05:04 +0000 UTC hostedclusters kx-bcd58379e3 Working towards 4.15.46: 27 of 606 done (4% complete)
2025-03-13 10:05:04 +0000 UTC hostedclusters kx-bcd58379e3 Payload loaded version="4.15.46" image="quay.io/openshift-release-dev/ocp-release@sha256:faf497f83a93980929dd2e0afd88352d578989778646604f7657be70a21550d3" architecture="Multi"
2025-03-13 10:05:12 +0000 UTC hostedclusters kx-bcd58379e3 Kubernetes 1.29 and therefore OpenShift 4.16 remove several APIs which require admin consideration. Please see the knowledge article https://access.redhat.com/articles/7031404 for details and instructions.
2025-03-13 10:05:42 +0000 UTC hostedclusters kx-bcd58379e3 Cluster operators console, dns, ingress, insights, kube-storage-version-migrator, monitoring, node-tuning, openshift-samples, service-ca, storage are not available
2025-03-13 10:05:43 +0000 UTC hostedclusters kx-bcd58379e3 The hosted control plane is available
INFO: Cluster 'kx-bcd58379e3' is now ready
INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
INFO: Storing login command...
INFO: Check if it's able to login to OCP cluster...
Retried 1 times...
Retried 2 times...
INFO: Check if apiserver is ready...
Waiting for cluster operators to be accessible for 2m...
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      6m24s   
dns                                        4.15.46   False       True          True       6m25s   DNS "default" is unavailable.
image-registry                                       False       True          True       5m44s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       5m45s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                   4.15.46   True        False         False      15s     
kube-apiserver                             4.15.46   True        False         False      6m13s   
kube-controller-manager                    4.15.46   True        False         False      6m13s   
kube-scheduler                             4.15.46   True        False         False      6m13s   
kube-storage-version-migrator              4.15.46   True        False         False      7s      
monitoring                                                                                        
network                                    4.15.46   True        True          False      5m59s   DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 3 nodes)...
node-tuning                                4.15.46   True        False         False      50s     
openshift-apiserver                        4.15.46   True        False         False      6m13s   
openshift-controller-manager               4.15.46   True        False         False      6m13s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      6m16s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      6m9s    
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      6m13s   
service-ca                                 4.15.46   True        False         False      19s     
storage                                    4.15.46   True        False         False      44s     
cluster operators to be accessible finished!
[INFO] Cluster operators are accessible.
Waiting for cluster to be reported as healthy for 60m...
Unable to connect to the server: dial tcp: lookup api.kx-bcd58379e3.vq1e.p3.openshiftapps.com on 172.30.0.10:53: no such host
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        True          False      17s     SyncLoopRefreshProgressing: Working toward version 4.15.46, 1 replicas available
csi-snapshot-controller                    4.15.46   True        False         False      7m25s   
dns                                        4.15.46   True        False         False      17s     
image-registry                             4.15.46   True        False         False      17s     
ingress                                    4.15.46   True        False         True       17s     The "default" ingress controller reports Degraded=True: DegradedConditions: One or more other status conditions indicate a degraded state: CanaryChecksSucceeding=Unknown (CanaryRouteNotAdmitted: Canary route is not admitted by the default ingress controller)
insights                                   4.15.46   True        False         False      76s     
kube-apiserver                             4.15.46   True        False         False      7m14s   
kube-controller-manager                    4.15.46   True        False         False      7m14s   
kube-scheduler                             4.15.46   True        False         False      7m14s   
kube-storage-version-migrator              4.15.46   True        False         False      68s     
monitoring                                           Unknown     True          Unknown    46s     Rolling out the stack.
network                                    4.15.46   True        True          False      7m      DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)
node-tuning                                4.15.46   True        False         False      111s    
openshift-apiserver                        4.15.46   True        False         False      7m14s   
openshift-controller-manager               4.15.46   True        False         False      7m14s   
openshift-samples                          4.15.46   True        False         False      13s     
operator-lifecycle-manager                 4.15.46   True        False         False      7m17s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      7m10s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      7m14s   
service-ca                                 4.15.46   True        False         False      80s     
storage                                    4.15.46   True        False         False      105s    
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      77s     
csi-snapshot-controller                    4.15.46   True        False         False      8m25s   
dns                                        4.15.46   True        False         False      77s     
image-registry                             4.15.46   True        False         False      77s     
ingress                                    4.15.46   True        False         False      77s     
insights                                   4.15.46   True        False         False      2m16s   
kube-apiserver                             4.15.46   True        False         False      8m14s   
kube-controller-manager                    4.15.46   True        False         False      8m14s   
kube-scheduler                             4.15.46   True        False         False      8m14s   
kube-storage-version-migrator              4.15.46   True        False         False      2m8s    
monitoring                                           Unknown     True          Unknown    106s    Rolling out the stack.
network                                    4.15.46   True        False         False      8m      
node-tuning                                4.15.46   True        False         False      2m51s   
openshift-apiserver                        4.15.46   True        False         False      8m14s   
openshift-controller-manager               4.15.46   True        False         False      8m14s   
openshift-samples                          4.15.46   True        False         False      73s     
operator-lifecycle-manager                 4.15.46   True        False         False      8m17s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      8m10s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      8m14s   
service-ca                                 4.15.46   True        False         False      2m20s   
storage                                    4.15.46   True        False         False      2m45s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      2m18s   
csi-snapshot-controller                    4.15.46   True        False         False      9m26s   
dns                                        4.15.46   True        False         False      2m18s   
image-registry                             4.15.46   True        False         False      2m18s   
ingress                                    4.15.46   True        False         False      2m18s   
insights                                   4.15.46   True        False         False      3m17s   
kube-apiserver                             4.15.46   True        False         False      9m15s   
kube-controller-manager                    4.15.46   True        False         False      9m15s   
kube-scheduler                             4.15.46   True        False         False      9m15s   
kube-storage-version-migrator              4.15.46   True        False         False      3m9s    
monitoring                                 4.15.46   True        False         False      2s      
network                                    4.15.46   True        False         False      9m1s    
node-tuning                                4.15.46   True        False         False      3m52s   
openshift-apiserver                        4.15.46   True        False         False      9m15s   
openshift-controller-manager               4.15.46   True        False         False      9m15s   
openshift-samples                          4.15.46   True        False         False      2m14s   
operator-lifecycle-manager                 4.15.46   True        False         False      9m18s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      9m11s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      9m15s   
service-ca                                 4.15.46   True        False         False      3m21s   
storage                                    4.15.46   True        False         False      3m46s   
Waiting for cluster to be reported as healthy... Trying again in 60s
healthy
cluster to be reported as healthy finished!
</pre></details>

---
author_association: NONE
user: login: konflux-ci-qe-bot
created_at: 2025-03-13T14:35:44Z
body: @jinqi7: The following test has Failed, say **/retest** to rerun failed tests.

| PipelineRun Name | Status | Rerun command | Build Log | Test Log |
|------------------|--------|---------------|-----------|----------|
| `konflux-e2e-tests-9bg4n`    | **Failed** | `/retest` | [View Pipeline Log](https://console.redhat.com/application-pipeline/ns/rhtap-release-2-tenant/pipelinerun/release-service-on-pull-request-fb6rz) | [View Test Logs](https://console.redhat.com/application-pipeline/ns/rhtap-release-2-tenant/pipelinerun/konflux-e2e-tests-9bg4n) |

### Inspecting Test Artifacts
To inspect your test artifacts, follow these steps:
1. Install **ORAS** (see the [ORAS installation guide](https://oras.land/docs/installation)).
2. Download artifacts with the following commands:

```sh
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/release-service:konflux-e2e-tests-9bg4n
```
### Test results analysis
:rotating_light: **Failed to provision a cluster, see the log for more details**: 

 <details><summary>Click to view logs</summary><br>
<pre>INFO: Log in to your Red Hat account...
INFO: Configure AWS Credentials...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
INFO: Logged in as 'konflux-ci-418295695583' on 'https://api.openshift.com'
INFO: Create ROSA with HCP cluster...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
time=2025-03-13T11:11:28Z level=info msg=Ignored check for policy key 'sts_hcp_ec2_registry_permission_policy' (zero egress feature toggle is not enabled)
INFO: Creating cluster 'kx-54f6d06dfb'
INFO: To view a list of clusters and their status, run 'rosa list clusters'
INFO: Cluster 'kx-54f6d06dfb' has been created.
INFO: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information.

Name:                       kx-54f6d06dfb
Domain Prefix:              kx-54f6d06dfb
Display Name:               kx-54f6d06dfb
ID:                         2hg6upsrud4ijmjc7plenv1ou5hi0cmv
External ID:                0e96528a-163c-4c10-9680-2133bf220d18
Control Plane:              ROSA Service Hosted
OpenShift Version:          4.15.46
Channel Group:              stable
DNS:                        Not ready
AWS Account:                418295695583
AWS Billing Account:        418295695583
API URL:                    
Console URL:                
Region:                     us-east-1
Availability:
 - Control Plane:           MultiAZ
 - Data Plane:              SingleAZ

Nodes:
 - Compute (desired):       3
 - Compute (current):       0
Network:
 - Type:                    OVNKubernetes
 - Service CIDR:            172.30.0.0/16
 - Machine CIDR:            10.0.0.0/16
 - Pod CIDR:                10.128.0.0/14
 - Host Prefix:             /23
 - Subnets:                 subnet-05b9daa0609597f68, subnet-04cf6376374bf9e09
EC2 Metadata Http Tokens:   optional
Role (STS) ARN:             arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Installer-Role
Support Role ARN:           arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Support-Role
Instance IAM Roles:
 - Worker:                  arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Worker-Role
Operator IAM Roles:
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kube-controller-manager
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-capa-controller-manager
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-control-plane-operator
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kms-provider
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-image-registry-installer-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-ingress-operator-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cloud-network-config-controller-cloud-credent
Managed Policies:           Yes
State:                      waiting (Waiting for user action)
Private:                    No
Delete Protection:          Disabled
Created:                    Mar 13 2025 11:11:41 UTC
User Workload Monitoring:   Enabled
Details Page:               https://console.redhat.com/openshift/details/s/2uG9yz0rkx0RyHlqDF7KkrkgjUy
OIDC Endpoint URL:          https://oidc.op1.openshiftapps.com/2du11g36ejmoo4624pofphlrgf4r9tf3 (Managed)
Etcd Encryption:            Disabled
Audit Log Forwarding:       Disabled
External Authentication:    Disabled
Zero Egress:                Disabled


INFO: Preparing to create operator roles.
INFO: Operator Roles already exists
INFO: Preparing to create OIDC Provider.
INFO: OIDC provider already exists
INFO: To determine when your cluster is Ready, run 'rosa describe cluster -c kx-54f6d06dfb'.
INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-54f6d06dfb --watch'.
INFO: Track the progress of the cluster creation...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
[0;33mW:[m Region flag will be removed from this command in future versions
INFO: Cluster 'kx-54f6d06dfb' is in waiting state waiting for installation to begin. Logs will show up within 5 minutes
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-54f6d06dfb Version 
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Condition not found in the CVO.
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb The hosted control plane is not found
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Condition not found in the CVO.
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb The hosted control plane is not found
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb The hosted control plane is not found
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb The hosted control plane is not found
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb The hosted control plane is not found
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb The hosted control plane is not found
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Condition not found in the CVO.
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Waiting for hosted control plane to be healthy
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Condition not found in the CVO.
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb The hosted control plane is not found
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Condition not found in the CVO.
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Ignition server deployment not found
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Configuration passes validation
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb HostedCluster is supported by operator configuration
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Reconciliation active on resource
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb ValidAWSIdentityProvider StatusUnknown
2025-03-13 11:16:50 +0000 UTC hostedclusters kx-54f6d06dfb Release image is valid
2025-03-13 11:16:52 +0000 UTC hostedclusters kx-54f6d06dfb HostedCluster is at expected version
2025-03-13 11:16:53 +0000 UTC hostedclusters kx-54f6d06dfb Required platform credentials are found
2025-03-13 11:16:53 +0000 UTC hostedclusters kx-54f6d06dfb failed to get referenced secret ocm-production-2hg6upsrud4ijmjc7plenv1ou5hi0cmv/cluster-api-cert: Secret "cluster-api-cert" not found
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-54f6d06dfb Version 
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Condition not found in the CVO.
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Reconciliation active on resource
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb router load balancer is not provisioned; 1s since creation.; private-router load balancer is not provisioned; 1s since creation.; router load balancer is not provisioned; 1s since creation.
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb HostedCluster is supported by operator configuration
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Configuration passes validation
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Ignition server deployment not found
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Condition not found in the CVO.
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Condition not found in the CVO.
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Condition not found in the CVO.
2025-03-13 11:16:33 +0000 UTC hostedclusters kx-54f6d06dfb Condition not found in the CVO.
2025-03-13 11:16:50 +0000 UTC hostedclusters kx-54f6d06dfb Release image is valid
2025-03-13 11:16:52 +0000 UTC hostedclusters kx-54f6d06dfb HostedCluster is at expected version
2025-03-13 11:16:53 +0000 UTC hostedclusters kx-54f6d06dfb Required platform credentials are found
2025-03-13 11:18:16 +0000 UTC hostedclusters kx-54f6d06dfb OIDC configuration is valid
2025-03-13 11:18:16 +0000 UTC hostedclusters kx-54f6d06dfb Reconciliation completed successfully
2025-03-13 11:18:27 +0000 UTC hostedclusters kx-54f6d06dfb WebIdentityErr
2025-03-13 11:18:30 +0000 UTC hostedclusters kx-54f6d06dfb EtcdAvailable StatefulSetNotFound
2025-03-13 11:18:30 +0000 UTC hostedclusters kx-54f6d06dfb router load balancer is not provisioned; 1s since creation.; private-router load balancer is not provisioned; 1s since creation.; router load balancer is not provisioned; 1s since creation.
2025-03-13 11:18:30 +0000 UTC hostedclusters kx-54f6d06dfb Kube APIServer deployment not found
2025-03-13 11:18:30 +0000 UTC hostedclusters kx-54f6d06dfb AWS KMS is not configured
2025-03-13 11:18:30 +0000 UTC hostedclusters kx-54f6d06dfb All is well
2025-03-13 11:18:30 +0000 UTC hostedclusters kx-54f6d06dfb capi-provider deployment has 1 unavailable replicas
2025-03-13 11:18:30 +0000 UTC hostedclusters kx-54f6d06dfb Configuration passes validation
2025-03-13 11:18:30 +0000 UTC hostedclusters kx-54f6d06dfb lookup api.kx-54f6d06dfb.b2gt.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-03-13 11:18:38 +0000 UTC hostedclusters kx-54f6d06dfb All is well
2025-03-13 11:19:37 +0000 UTC hostedclusters kx-54f6d06dfb EtcdAvailable QuorumAvailable
2025-03-13 11:20:45 +0000 UTC hostedclusters kx-54f6d06dfb Kube APIServer deployment is available
2025-03-13 11:20:47 +0000 UTC hostedclusters kx-54f6d06dfb All is well
2025-03-13 11:21:16 +0000 UTC hostedclusters kx-54f6d06dfb The hosted cluster is not degraded
2025-03-13 11:21:21 +0000 UTC hostedclusters kx-54f6d06dfb All is well
2025-03-13 11:21:21 +0000 UTC hostedclusters kx-54f6d06dfb [capi-provider deployment has 1 unavailable replicas, catalog-operator deployment has 1 unavailable replicas, certified-operators-catalog deployment has 2 unavailable replicas, cloud-credential-operator deployment has 1 unavailable replicas, cluster-network-operator deployment has 1 unavailable replicas, cluster-storage-operator deployment has 1 unavailable replicas, cluster-version-operator deployment has 1 unavailable replicas, community-operators-catalog deployment has 2 unavailable replicas, csi-snapshot-controller-operator deployment has 1 unavailable replicas, dns-operator deployment has 1 unavailable replicas, hosted-cluster-config-operator deployment has 1 unavailable replicas, ignition-server deployment has 3 unavailable replicas, ingress-operator deployment has 1 unavailable replicas, olm-operator deployment has 1 unavailable replicas, openshift-controller-manager deployment has 1 unavailable replicas, openshift-oauth-apiserver deployment has 1 unavailable replicas, openshift-route-controller-manager deployment has 1 unavailable replicas, packageserver deployment has 3 unavailable replicas, redhat-marketplace-catalog deployment has 2 unavailable replicas, redhat-operators-catalog deployment has 2 unavailable replicas, router deployment has 1 unavailable replicas]
2025-03-13 11:21:43 +0000 UTC hostedclusters kx-54f6d06dfb The hosted control plane is available
INFO: Cluster 'kx-54f6d06dfb' is now ready
INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
INFO: Storing login command...
INFO: Check if it's able to login to OCP cluster...
Retried 1 times...
Retried 2 times...
INFO: Check if apiserver is ready...
Waiting for cluster operators to be accessible for 2m...
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      3m3s    
dns                                        4.15.46   False       False         True       3m8s    DNS "default" is unavailable.
image-registry                                       False       True          True       2m39s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       2m17s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      3m3s    
kube-controller-manager                    4.15.46   True        False         False      3m3s    
kube-scheduler                             4.15.46   True        False         False      3m3s    
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      2m35s   DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready...
node-tuning                                          False       True          False      2m52s   DaemonSet "tuned" has no available Pod(s)
openshift-apiserver                        4.15.46   True        False         False      3m3s    
openshift-controller-manager               4.15.46   True        False         False      3m3s    
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      3m5s    
operator-lifecycle-manager-catalog         4.15.46   True        False         False      3m5s    
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      3m3s    
service-ca                                                                                        
storage                                    4.15.46   False       False         False      3m2s    AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service
cluster operators to be accessible finished!
[INFO] Cluster operators are accessible.
Waiting for cluster to be reported as healthy for 60m...
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      3m3s    
dns                                        4.15.46   False       False         True       3m8s    DNS "default" is unavailable.
image-registry                                       False       True          True       2m39s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       2m17s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      3m3s    
kube-controller-manager                    4.15.46   True        False         False      3m3s    
kube-scheduler                             4.15.46   True        False         False      3m3s    
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      2m35s   DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready...
node-tuning                                          False       True          False      2m52s   DaemonSet "tuned" has no available Pod(s)
openshift-apiserver                        4.15.46   True        False         False      3m3s    
openshift-controller-manager               4.15.46   True        False         False      3m3s    
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      3m5s    
operator-lifecycle-manager-catalog         4.15.46   True        False         False      3m5s    
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      3m3s    
service-ca                                                                                        
storage                                    4.15.46   False       False         False      3m2s    AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      4m3s    
dns                                        4.15.46   False       False         True       4m8s    DNS "default" is unavailable.
image-registry                                       False       True          True       3m39s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       3m17s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      4m3s    
kube-controller-manager                    4.15.46   True        False         False      4m3s    
kube-scheduler                             4.15.46   True        False         False      4m3s    
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      3m35s   DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)...
node-tuning                                4.15.46   True        True          False      16s     Waiting for 3/3 Profiles to be applied
openshift-apiserver                        4.15.46   True        False         False      4m3s    
openshift-controller-manager               4.15.46   True        False         False      4m3s    
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      4m5s    
operator-lifecycle-manager-catalog         4.15.46   True        False         False      4m5s    
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      4m3s    
service-ca                                                                                        
storage                                    4.15.46   True        True          False      1s      AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      5m4s    
dns                                        4.15.46   False       True          True       5m9s    DNS "default" is unavailable.
image-registry                                       False       True          True       4m40s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       4m18s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                   4.15.46   True        False         False      39s     
kube-apiserver                             4.15.46   True        False         False      5m4s    
kube-controller-manager                    4.15.46   True        False         False      5m4s    
kube-scheduler                             4.15.46   True        False         False      5m4s    
kube-storage-version-migrator              4.15.46   True        False         False      33s     
monitoring                                           Unknown     True          Unknown    8s      Rolling out the stack.
network                                    4.15.46   True        True          False      4m36s   DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)...
node-tuning                                4.15.46   True        False         False      77s     
openshift-apiserver                        4.15.46   True        False         False      5m4s    
openshift-controller-manager               4.15.46   True        False         False      5m4s    
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      5m6s    
operator-lifecycle-manager-catalog         4.15.46   True        False         False      5m6s    
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      5m4s    
service-ca                                 4.15.46   True        False         False      37s     
storage                                    4.15.46   True        False         False      62s     
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      18s     
csi-snapshot-controller                    4.15.46   True        False         False      6m4s    
dns                                        4.15.46   True        False         False      30s     
image-registry                             4.15.46   True        False         False      31s     
ingress                                    4.15.46   True        False         False      30s     
insights                                   4.15.46   True        False         False      99s     
kube-apiserver                             4.15.46   True        False         False      6m4s    
kube-controller-manager                    4.15.46   True        False         False      6m4s    
kube-scheduler                             4.15.46   True        False         False      6m4s    
kube-storage-version-migrator              4.15.46   True        False         False      93s     
monitoring                                           Unknown     True          Unknown    68s     Rolling out the stack.
network                                    4.15.46   True        False         False      5m36s   
node-tuning                                4.15.46   True        False         False      2m17s   
openshift-apiserver                        4.15.46   True        False         False      6m4s    
openshift-controller-manager               4.15.46   True        False         False      6m4s    
openshift-samples                          4.15.46   True        False         False      30s     
operator-lifecycle-manager                 4.15.46   True        False         False      6m6s    
operator-lifecycle-manager-catalog         4.15.46   True        False         False      6m6s    
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      6m4s    
service-ca                                 4.15.46   True        False         False      97s     
storage                                    4.15.46   True        False         False      2m2s    
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      78s     
csi-snapshot-controller                    4.15.46   True        False         False      7m4s    
dns                                        4.15.46   True        False         False      90s     
image-registry                             4.15.46   True        False         False      91s     
ingress                                    4.15.46   True        False         False      90s     
insights                                   4.15.46   True        False         False      2m39s   
kube-apiserver                             4.15.46   True        False         False      7m4s    
kube-controller-manager                    4.15.46   True        False         False      7m4s    
kube-scheduler                             4.15.46   True        False         False      7m4s    
kube-storage-version-migrator              4.15.46   True        False         False      2m33s   
monitoring                                           Unknown     True          Unknown    2m8s    Rolling out the stack.
network                                    4.15.46   True        False         False      6m36s   
node-tuning                                4.15.46   True        False         False      3m17s   
openshift-apiserver                        4.15.46   True        False         False      7m4s    
openshift-controller-manager               4.15.46   True        False         False      7m4s    
openshift-samples                          4.15.46   True        False         False      90s     
operator-lifecycle-manager                 4.15.46   True        False         False      7m6s    
operator-lifecycle-manager-catalog         4.15.46   True        False         False      7m6s    
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      7m4s    
service-ca                                 4.15.46   True        False         False      2m37s   
storage                                    4.15.46   True        False         False      3m2s    
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      2m18s   
csi-snapshot-controller                    4.15.46   True        False         False      8m4s    
dns                                        4.15.46   True        False         False      2m30s   
image-registry                             4.15.46   True        False         False      2m31s   
ingress                                    4.15.46   True        False         False      2m30s   
insights                                   4.15.46   True        False         False      3m39s   
kube-apiserver                             4.15.46   True        False         False      8m4s    
kube-controller-manager                    4.15.46   True        False         False      8m4s    
kube-scheduler                             4.15.46   True        False         False      8m4s    
kube-storage-version-migrator              4.15.46   True        False         False      3m33s   
monitoring                                 4.15.46   True        False         False      11s     
network                                    4.15.46   True        False         False      7m36s   
node-tuning                                4.15.46   True        False         False      4m17s   
openshift-apiserver                        4.15.46   True        False         False      8m4s    
openshift-controller-manager               4.15.46   True        False         False      8m4s    
openshift-samples                          4.15.46   True        False         False      2m30s   
operator-lifecycle-manager                 4.15.46   True        False         False      8m6s    
operator-lifecycle-manager-catalog         4.15.46   True        False         False      8m6s    
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      8m4s    
service-ca                                 4.15.46   True        False         False      3m37s   
storage                                    4.15.46   True        False         False      4m2s    
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      3m19s   
csi-snapshot-controller                    4.15.46   True        False         False      9m5s    
dns                                        4.15.46   True        False         False      3m31s   
image-registry                             4.15.46   True        False         False      3m32s   
ingress                                    4.15.46   True        False         False      3m31s   
insights                                   4.15.46   True        False         False      4m40s   
kube-apiserver                             4.15.46   True        False         False      9m5s    
kube-controller-manager                    4.15.46   True        False         False      9m5s    
kube-scheduler                             4.15.46   True        False         False      9m5s    
kube-storage-version-migrator              4.15.46   True        False         False      4m34s   
monitoring                                 4.15.46   True        False         False      72s     
network                                    4.15.46   True        False         False      8m37s   
node-tuning                                4.15.46   True        False         False      5m18s   
openshift-apiserver                        4.15.46   True        False         False      9m5s    
openshift-controller-manager               4.15.46   True        False         False      9m5s    
openshift-samples                          4.15.46   True        False         False      3m31s   
operator-lifecycle-manager                 4.15.46   True        False         False      9m7s    
operator-lifecycle-manager-catalog         4.15.46   True        False         False      9m7s    
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      9m5s    
service-ca                                 4.15.46   True        False         False      4m38s   
storage                                    4.15.46   True        False         False      5m3s    
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      4m19s   
csi-snapshot-controller                    4.15.46   True        False         False      10m     
dns                                        4.15.46   True        False         False      4m31s   
image-registry                             4.15.46   True        False         False      4m32s   
ingress                                    4.15.46   True        False         False      4m31s   
insights                                   4.15.46   True        False         False      5m40s   
kube-apiserver                             4.15.46   True        False         False      10m     
kube-controller-manager                    4.15.46   True        False         False      10m     
kube-scheduler                             4.15.46   True        False         False      10m     
kube-storage-version-migrator              4.15.46   True        False         False      5m34s   
monitoring                                 4.15.46   True        False         False      2m12s   
network                                    4.15.46   True        False         False      9m37s   
node-tuning                                4.15.46   True        False         False      6m18s   
openshift-apiserver                        4.15.46   True        False         False      10m     
openshift-controller-manager               4.15.46   True        False         False      10m     
openshift-samples                          4.15.46   True        False         False      4m31s   
operator-lifecycle-manager                 4.15.46   True        False         False      10m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      10m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      10m     
service-ca                                 4.15.46   True        False         False      5m38s   
storage                                    4.15.46   True        False         False      6m3s    
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      5m19s   
csi-snapshot-controller                    4.15.46   True        False         False      11m     
dns                                        4.15.46   True        False         False      5m31s   
image-registry                             4.15.46   True        False         False      5m32s   
ingress                                    4.15.46   True        False         False      5m31s   
insights                                   4.15.46   True        False         False      6m40s   
kube-apiserver                             4.15.46   True        False         False      11m     
kube-controller-manager                    4.15.46   True        False         False      11m     
kube-scheduler                             4.15.46   True        False         False      11m     
kube-storage-version-migrator              4.15.46   True        False         False      6m34s   
monitoring                                 4.15.46   True        False         False      3m12s   
network                                    4.15.46   True        False         False      10m     
node-tuning                                4.15.46   True        False         False      7m18s   
openshift-apiserver                        4.15.46   True        False         False      11m     
openshift-controller-manager               4.15.46   True        False         False      11m     
openshift-samples                          4.15.46   True        False         False      5m31s   
operator-lifecycle-manager                 4.15.46   True        False         False      11m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      11m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      11m     
service-ca                                 4.15.46   True        False         False      6m38s   
storage                                    4.15.46   True        False         False      7m3s    
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      6m19s   
csi-snapshot-controller                    4.15.46   True        False         False      12m     
dns                                        4.15.46   True        False         False      6m31s   
image-registry                             4.15.46   True        False         False      6m32s   
ingress                                    4.15.46   True        False         False      6m31s   
insights                                   4.15.46   True        False         False      7m40s   
kube-apiserver                             4.15.46   True        False         False      12m     
kube-controller-manager                    4.15.46   True        False         False      12m     
kube-scheduler                             4.15.46   True        False         False      12m     
kube-storage-version-migrator              4.15.46   True        False         False      7m34s   
monitoring                                 4.15.46   True        False         False      4m12s   
network                                    4.15.46   True        False         False      11m     
node-tuning                                4.15.46   True        False         False      8m18s   
openshift-apiserver                        4.15.46   True        False         False      12m     
openshift-controller-manager               4.15.46   True        False         False      12m     
openshift-samples                          4.15.46   True        False         False      6m31s   
operator-lifecycle-manager                 4.15.46   True        False         False      12m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      12m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      12m     
service-ca                                 4.15.46   True        False         False      7m38s   
storage                                    4.15.46   True        False         False      8m3s    
Waiting for cluster to be reported as healthy... Trying again in 60s
healthy
cluster to be reported as healthy finished!
</pre></details>

---
author_association: NONE
user: login: konflux-ci-qe-bot
created_at: 2025-03-14T04:01:12Z
body: @jinqi7: The following test has Failed, say **/retest** to rerun failed tests.

| PipelineRun Name | Status | Rerun command | Build Log | Test Log |
|------------------|--------|---------------|-----------|----------|
| `konflux-e2e-tests-fr2j6`    | **Failed** | `/retest` | [View Pipeline Log](https://console.redhat.com/application-pipeline/ns/rhtap-release-2-tenant/pipelinerun/release-service-on-pull-request-rrbzg) | [View Test Logs](https://console.redhat.com/application-pipeline/ns/rhtap-release-2-tenant/pipelinerun/konflux-e2e-tests-fr2j6) |

### Inspecting Test Artifacts
To inspect your test artifacts, follow these steps:
1. Install **ORAS** (see the [ORAS installation guide](https://oras.land/docs/installation)).
2. Download artifacts with the following commands:

```sh
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/release-service:konflux-e2e-tests-fr2j6
```
### Test results analysis
:rotating_light: **Failed to provision a cluster, see the log for more details**: 

 <details><summary>Click to view logs</summary><br>
<pre>INFO: Log in to your Red Hat account...
INFO: Configure AWS Credentials...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
INFO: Logged in as 'konflux-ci-418295695583' on 'https://api.openshift.com'
INFO: Create ROSA with HCP cluster...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
time=2025-03-14T00:33:02Z level=info msg=Ignored check for policy key 'sts_hcp_ec2_registry_permission_policy' (zero egress feature toggle is not enabled)
INFO: Creating cluster 'kx-f8f8344eab'
INFO: To view a list of clusters and their status, run 'rosa list clusters'
INFO: Cluster 'kx-f8f8344eab' has been created.
INFO: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information.

Name:                       kx-f8f8344eab
Domain Prefix:              kx-f8f8344eab
Display Name:               kx-f8f8344eab
ID:                         2hgimh5lv7o4t4red23cul3agt9trqog
External ID:                e4be0d73-b4c1-4131-9e7c-0c50c14cf851
Control Plane:              ROSA Service Hosted
OpenShift Version:          4.15.46
Channel Group:              stable
DNS:                        Not ready
AWS Account:                418295695583
AWS Billing Account:        418295695583
API URL:                    
Console URL:                
Region:                     us-east-1
Availability:
 - Control Plane:           MultiAZ
 - Data Plane:              SingleAZ

Nodes:
 - Compute (desired):       3
 - Compute (current):       0
Network:
 - Type:                    OVNKubernetes
 - Service CIDR:            172.30.0.0/16
 - Machine CIDR:            10.0.0.0/16
 - Pod CIDR:                10.128.0.0/14
 - Host Prefix:             /23
 - Subnets:                 subnet-05b9daa0609597f68, subnet-04cf6376374bf9e09
EC2 Metadata Http Tokens:   optional
Role (STS) ARN:             arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Installer-Role
Support Role ARN:           arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Support-Role
Instance IAM Roles:
 - Worker:                  arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Worker-Role
Operator IAM Roles:
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cloud-network-config-controller-cloud-credent
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kube-controller-manager
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-capa-controller-manager
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-control-plane-operator
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kms-provider
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-image-registry-installer-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-ingress-operator-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials
Managed Policies:           Yes
State:                      waiting (Waiting for user action)
Private:                    No
Delete Protection:          Disabled
Created:                    Mar 14 2025 00:33:12 UTC
User Workload Monitoring:   Enabled
Details Page:               https://console.redhat.com/openshift/details/s/2uHjSR7JziFEH3uY4I3EKT0VN8a
OIDC Endpoint URL:          https://oidc.op1.openshiftapps.com/2du11g36ejmoo4624pofphlrgf4r9tf3 (Managed)
Etcd Encryption:            Disabled
Audit Log Forwarding:       Disabled
External Authentication:    Disabled
Zero Egress:                Disabled


INFO: Preparing to create operator roles.
INFO: Operator Roles already exists
INFO: Preparing to create OIDC Provider.
INFO: OIDC provider already exists
INFO: To determine when your cluster is Ready, run 'rosa describe cluster -c kx-f8f8344eab'.
INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-f8f8344eab --watch'.
INFO: Track the progress of the cluster creation...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
[0;33mW:[m Region flag will be removed from this command in future versions
INFO: Cluster 'kx-f8f8344eab' is in waiting state waiting for installation to begin. Logs will show up within 5 minutes
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-f8f8344eab Version 
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab The hosted control plane is not found
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab The hosted control plane is not found
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab The hosted control plane is not found
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab The hosted control plane is not found
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab The hosted control plane is not found
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab The hosted control plane is not found
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Waiting for hosted control plane to be healthy
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab The hosted control plane is not found
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Ignition server deployment not found
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Configuration passes validation
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab HostedCluster is supported by operator configuration
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Reconciliation active on resource
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab ValidAWSIdentityProvider StatusUnknown
2025-03-14 00:37:03 +0000 UTC hostedclusters kx-f8f8344eab Release image is valid
2025-03-14 00:37:04 +0000 UTC hostedclusters kx-f8f8344eab HostedCluster is at expected version
2025-03-14 00:37:14 +0000 UTC hostedclusters kx-f8f8344eab Required platform credentials are found
2025-03-14 00:37:14 +0000 UTC hostedclusters kx-f8f8344eab failed to get referenced secret ocm-production-2hgimh5lv7o4t4red23cul3agt9trqog/cluster-api-cert: Secret "cluster-api-cert" not found
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-f8f8344eab Version 
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Reconciliation active on resource
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Waiting for hosted control plane kubeconfig to be created
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab HostedCluster is supported by operator configuration
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Configuration passes validation
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Ignition server deployment not found
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:03 +0000 UTC hostedclusters kx-f8f8344eab Release image is valid
2025-03-14 00:37:04 +0000 UTC hostedclusters kx-f8f8344eab HostedCluster is at expected version
2025-03-14 00:37:14 +0000 UTC hostedclusters kx-f8f8344eab Required platform credentials are found
2025-03-14 00:38:39 +0000 UTC hostedclusters kx-f8f8344eab OIDC configuration is valid
2025-03-14 00:38:39 +0000 UTC hostedclusters kx-f8f8344eab Reconciliation completed successfully
2025-03-14 00:38:48 +0000 UTC hostedclusters kx-f8f8344eab WebIdentityErr
2025-03-14 00:38:50 +0000 UTC hostedclusters kx-f8f8344eab EtcdAvailable StatefulSetNotFound
2025-03-14 00:38:50 +0000 UTC hostedclusters kx-f8f8344eab Kube APIServer deployment not found
2025-03-14 00:38:50 +0000 UTC hostedclusters kx-f8f8344eab AWS KMS is not configured
2025-03-14 00:38:50 +0000 UTC hostedclusters kx-f8f8344eab All is well
2025-03-14 00:38:50 +0000 UTC hostedclusters kx-f8f8344eab capi-provider deployment has 1 unavailable replicas
2025-03-14 00:38:50 +0000 UTC hostedclusters kx-f8f8344eab Configuration passes validation
2025-03-14 00:38:50 +0000 UTC hostedclusters kx-f8f8344eab lookup api.kx-f8f8344eab.tsu1.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-03-14 00:38:57 +0000 UTC hostedclusters kx-f8f8344eab All is well
2025-03-14 00:39:46 +0000 UTC hostedclusters kx-f8f8344eab EtcdAvailable QuorumAvailable
2025-03-14 00:40:47 +0000 UTC hostedclusters kx-f8f8344eab Kube APIServer deployment is available
2025-03-14 00:40:49 +0000 UTC hostedclusters kx-f8f8344eab All is well
2025-03-14 00:41:18 +0000 UTC hostedclusters kx-f8f8344eab The hosted cluster is not degraded
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-f8f8344eab Version 
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Reconciliation active on resource
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab HostedCluster is supported by operator configuration
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Configuration passes validation
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Ignition server deployment is not yet available
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:00 +0000 UTC hostedclusters kx-f8f8344eab Condition not found in the CVO.
2025-03-14 00:37:03 +0000 UTC hostedclusters kx-f8f8344eab Release image is valid
2025-03-14 00:37:04 +0000 UTC hostedclusters kx-f8f8344eab HostedCluster is at expected version
2025-03-14 00:37:14 +0000 UTC hostedclusters kx-f8f8344eab Required platform credentials are found
2025-03-14 00:38:39 +0000 UTC hostedclusters kx-f8f8344eab OIDC configuration is valid
2025-03-14 00:38:39 +0000 UTC hostedclusters kx-f8f8344eab Reconciliation completed successfully
2025-03-14 00:38:50 +0000 UTC hostedclusters kx-f8f8344eab AWS KMS is not configured
2025-03-14 00:38:50 +0000 UTC hostedclusters kx-f8f8344eab All is well
2025-03-14 00:38:50 +0000 UTC hostedclusters kx-f8f8344eab Configuration passes validation
2025-03-14 00:38:50 +0000 UTC hostedclusters kx-f8f8344eab lookup api.kx-f8f8344eab.tsu1.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-03-14 00:38:57 +0000 UTC hostedclusters kx-f8f8344eab All is well
2025-03-14 00:39:46 +0000 UTC hostedclusters kx-f8f8344eab EtcdAvailable QuorumAvailable
2025-03-14 00:40:47 +0000 UTC hostedclusters kx-f8f8344eab Kube APIServer deployment is available
2025-03-14 00:40:49 +0000 UTC hostedclusters kx-f8f8344eab All is well
2025-03-14 00:41:24 +0000 UTC hostedclusters kx-f8f8344eab All is well
2025-03-14 00:41:24 +0000 UTC hostedclusters kx-f8f8344eab [catalog-operator deployment has 1 unavailable replicas, certified-operators-catalog deployment has 2 unavailable replicas, cloud-credential-operator deployment has 1 unavailable replicas, cluster-network-operator deployment has 1 unavailable replicas, cluster-storage-operator deployment has 1 unavailable replicas, cluster-version-operator deployment has 1 unavailable replicas, community-operators-catalog deployment has 2 unavailable replicas, csi-snapshot-controller-operator deployment has 1 unavailable replicas, dns-operator deployment has 1 unavailable replicas, hosted-cluster-config-operator deployment has 1 unavailable replicas, ignition-server deployment has 3 unavailable replicas, ingress-operator deployment has 1 unavailable replicas, olm-operator deployment has 1 unavailable replicas, packageserver deployment has 3 unavailable replicas, redhat-marketplace-catalog deployment has 2 unavailable replicas, redhat-operators-catalog deployment has 2 unavailable replicas, router deployment has 1 unavailable replicas]
2025-03-14 00:41:48 +0000 UTC hostedclusters kx-f8f8344eab The hosted control plane is available
INFO: Cluster 'kx-f8f8344eab' is now ready
INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
INFO: Storing login command...
INFO: Check if it's able to login to OCP cluster...
Retried 1 times...
INFO: Check if apiserver is ready...
Waiting for cluster operators to be accessible for 2m...
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      2m34s   
dns                                        4.15.46   False       False         True       2m38s   DNS "default" is unavailable.
image-registry                                       False       True          True       107s    Available: The deployment does not have available replicas...
ingress                                              False       True          True       2m14s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      2m29s   
kube-controller-manager                    4.15.46   True        False         False      2m29s   
kube-scheduler                             4.15.46   True        False         False      2m29s   
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      2m9s    Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning                                          False       True          False      2m15s   DaemonSet "tuned" has no available Pod(s)
openshift-apiserver                        4.15.46   True        False         False      2m29s   
openshift-controller-manager               4.15.46   True        False         False      2m29s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      2m34s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      2m30s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      2m29s   
service-ca                                                                                        
storage                                    4.15.46   False       False         False      2m28s   AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service
cluster operators to be accessible finished!
[INFO] Cluster operators are accessible.
Waiting for cluster to be reported as healthy for 60m...
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      2m34s   
dns                                        4.15.46   False       False         True       2m38s   DNS "default" is unavailable.
image-registry                                       False       True          True       107s    Available: The deployment does not have available replicas...
ingress                                              False       True          True       2m14s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      2m29s   
kube-controller-manager                    4.15.46   True        False         False      2m29s   
kube-scheduler                             4.15.46   True        False         False      2m29s   
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      2m9s    Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning                                          False       True          False      2m15s   DaemonSet "tuned" has no available Pod(s)
openshift-apiserver                        4.15.46   True        False         False      2m29s   
openshift-controller-manager               4.15.46   True        False         False      2m29s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      2m34s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      2m30s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      2m29s   
service-ca                                                                                        
storage                                    4.15.46   False       False         False      2m28s   AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      3m35s   
dns                                        4.15.46   False       False         True       3m39s   DNS "default" is unavailable.
image-registry                                       False       True          True       2m48s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       3m15s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      3m30s   
kube-controller-manager                    4.15.46   True        False         False      3m30s   
kube-scheduler                             4.15.46   True        False         False      3m30s   
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      3m10s   Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning                                          False       True          False      3m16s   DaemonSet "tuned" has no available Pod(s)
openshift-apiserver                        4.15.46   True        False         False      3m30s   
openshift-controller-manager               4.15.46   True        False         False      3m30s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      3m35s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      3m31s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      3m30s   
service-ca                                                                                        
storage                                    4.15.46   False       False         False      3m29s   AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   False       True          False      47s     CSISnapshotControllerAvailable: Waiting for Deployment
dns                                        4.15.46   False       False         True       4m39s   DNS "default" is unavailable.
image-registry                                       False       True          True       3m48s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       4m15s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      4m30s   
kube-controller-manager                    4.15.46   True        False         False      4m30s   
kube-scheduler                             4.15.46   True        False         False      4m30s   
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      4m10s   DaemonSet "/openshift-network-diagnostics/network-check-target" is not available (awaiting 2 nodes)...
node-tuning                                4.15.46   True        True          False      4s      Waiting for 2/3 Profiles to be applied
openshift-apiserver                        4.15.46   True        False         False      4m30s   
openshift-controller-manager               4.15.46   True        False         False      4m30s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      4m35s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      4m31s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      4m30s   
service-ca                                                                                        
storage                                    4.15.46   False       True          False      4m29s   AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverControllerServiceControllerAvailable: Waiting for Deployment
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   Unknown     False         False      5s      
csi-snapshot-controller                    4.15.46   False       True          False      107s    CSISnapshotControllerAvailable: Waiting for Deployment
dns                                        4.15.46   False       True          True       5m39s   DNS "default" is unavailable.
image-registry                                       False       True          True       4m48s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       5m15s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                   4.15.46   True        False         False      43s     
kube-apiserver                             4.15.46   True        False         False      5m30s   
kube-controller-manager                    4.15.46   True        False         False      5m30s   
kube-scheduler                             4.15.46   True        False         False      5m30s   
kube-storage-version-migrator              4.15.46   True        False         False      38s     
monitoring                                           Unknown     True          Unknown    9s      Rolling out the stack.
network                                    4.15.46   True        True          False      5m10s   DaemonSet "/openshift-multus/network-metrics-daemon" is waiting for other operators to become ready...
node-tuning                                4.15.46   True        False         False      64s     
openshift-apiserver                        4.15.46   True        False         False      5m30s   
openshift-controller-manager               4.15.46   True        False         False      5m30s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      5m35s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      5m31s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      5m30s   
service-ca                                 4.15.46   True        False         False      39s     
storage                                    4.15.46   False       True          False      5m29s   AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverControllerServiceControllerAvailable: Waiting for Deployment
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        True          False      22s     SyncLoopRefreshProgressing: Working toward version 4.15.46, 1 replicas available
csi-snapshot-controller                    4.15.46   False       True          False      2m48s   CSISnapshotControllerAvailable: Waiting for Deployment
dns                                        4.15.46   True        False         False      48s     
image-registry                             4.15.46   True        True          False      42s     Progressing: The deployment has not completed...
ingress                                    4.15.46   True        False         True       27s     The "default" ingress controller reports Degraded=True: DegradedConditions: One or more other status conditions indicate a degraded state: CanaryChecksSucceeding=Unknown (CanaryRouteNotAdmitted: Canary route is not admitted by the default ingress controller)
insights                                   4.15.46   True        False         False      104s    
kube-apiserver                             4.15.46   True        False         False      6m31s   
kube-controller-manager                    4.15.46   True        False         False      6m31s   
kube-scheduler                             4.15.46   True        False         False      6m31s   
kube-storage-version-migrator              4.15.46   True        False         False      99s     
monitoring                                           Unknown     True          Unknown    70s     Rolling out the stack.
network                                    4.15.46   True        False         False      6m11s   
node-tuning                                4.15.46   True        False         False      2m5s    
openshift-apiserver                        4.15.46   True        False         False      6m31s   
openshift-controller-manager               4.15.46   True        False         False      6m31s   
openshift-samples                          4.15.46   True        False         False      36s     
operator-lifecycle-manager                 4.15.46   True        False         False      6m36s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      6m32s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      6m31s   
service-ca                                 4.15.46   True        False         False      100s    
storage                                    4.15.46   False       True          False      6m30s   AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverControllerServiceControllerAvailable: Waiting for Deployment
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      82s     
csi-snapshot-controller                    4.15.46   True        False         False      12s     
dns                                        4.15.46   True        True          False      108s    DNS "default" reports Progressing=True: "Have 2 available DNS pods, want 3."
image-registry                             4.15.46   True        False         False      102s    
ingress                                    4.15.46   True        False         False      87s     
insights                                   4.15.46   True        False         False      2m44s   
kube-apiserver                             4.15.46   True        False         False      7m31s   
kube-controller-manager                    4.15.46   True        False         False      7m31s   
kube-scheduler                             4.15.46   True        False         False      7m31s   
kube-storage-version-migrator              4.15.46   True        False         False      2m39s   
monitoring                                           Unknown     True          Unknown    2m10s   Rolling out the stack.
network                                    4.15.46   True        False         False      7m11s   
node-tuning                                4.15.46   True        False         False      3m5s    
openshift-apiserver                        4.15.46   True        False         False      7m31s   
openshift-controller-manager               4.15.46   True        False         False      7m31s   
openshift-samples                          4.15.46   True        False         False      96s     
operator-lifecycle-manager                 4.15.46   True        False         False      7m36s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      7m32s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      7m31s   
service-ca                                 4.15.46   True        False         False      2m40s   
storage                                    4.15.46   True        False         False      17s     
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      2m22s   
csi-snapshot-controller                    4.15.46   True        False         False      72s     
dns                                        4.15.46   True        False         False      2m48s   
image-registry                             4.15.46   True        False         False      2m42s   
ingress                                    4.15.46   True        False         False      2m27s   
insights                                   4.15.46   True        False         False      3m44s   
kube-apiserver                             4.15.46   True        False         False      8m31s   
kube-controller-manager                    4.15.46   True        False         False      8m31s   
kube-scheduler                             4.15.46   True        False         False      8m31s   
kube-storage-version-migrator              4.15.46   True        False         False      3m39s   
monitoring                                           Unknown     True          Unknown    3m10s   Rolling out the stack.
network                                    4.15.46   True        False         False      8m11s   
node-tuning                                4.15.46   True        False         False      4m5s    
openshift-apiserver                        4.15.46   True        False         False      8m31s   
openshift-controller-manager               4.15.46   True        False         False      8m31s   
openshift-samples                          4.15.46   True        False         False      2m36s   
operator-lifecycle-manager                 4.15.46   True        False         False      8m36s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      8m32s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      8m31s   
service-ca                                 4.15.46   True        False         False      3m40s   
storage                                    4.15.46   True        False         False      77s     
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      3m22s   
csi-snapshot-controller                    4.15.46   True        False         False      2m12s   
dns                                        4.15.46   True        False         False      3m48s   
image-registry                             4.15.46   True        False         False      3m42s   
ingress                                    4.15.46   True        False         False      3m27s   
insights                                   4.15.46   True        False         False      4m44s   
kube-apiserver                             4.15.46   True        False         False      9m31s   
kube-controller-manager                    4.15.46   True        False         False      9m31s   
kube-scheduler                             4.15.46   True        False         False      9m31s   
kube-storage-version-migrator              4.15.46   True        False         False      4m39s   
monitoring                                           Unknown     True          Unknown    4m10s   Rolling out the stack.
network                                    4.15.46   True        False         False      9m11s   
node-tuning                                4.15.46   True        False         False      5m5s    
openshift-apiserver                        4.15.46   True        False         False      9m31s   
openshift-controller-manager               4.15.46   True        False         False      9m31s   
openshift-samples                          4.15.46   True        False         False      3m36s   
operator-lifecycle-manager                 4.15.46   True        False         False      9m36s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      9m32s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      9m31s   
service-ca                                 4.15.46   True        False         False      4m40s   
storage                                    4.15.46   True        False         False      2m17s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        True          False      4m23s   SyncLoopRefreshProgressing: Working toward version 4.15.46, 1 replicas available
csi-snapshot-controller                    4.15.46   True        False         False      3m13s   
dns                                        4.15.46   True        False         False      4m49s   
image-registry                             4.15.46   True        False         False      4m43s   
ingress                                    4.15.46   True        False         False      4m28s   
insights                                   4.15.46   True        False         False      5m45s   
kube-apiserver                             4.15.46   True        False         False      10m     
kube-controller-manager                    4.15.46   True        False         False      10m     
kube-scheduler                             4.15.46   True        False         False      10m     
kube-storage-version-migrator              4.15.46   True        False         False      5m40s   
monitoring                                 4.15.46   True        False         False      34s     
network                                    4.15.46   True        False         False      10m     
node-tuning                                4.15.46   True        False         False      6m6s    
openshift-apiserver                        4.15.46   True        False         False      10m     
openshift-controller-manager               4.15.46   True        False         False      10m     
openshift-samples                          4.15.46   True        False         False      4m37s   
operator-lifecycle-manager                 4.15.46   True        False         False      10m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      10m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      10m     
service-ca                                 4.15.46   True        False         False      5m41s   
storage                                    4.15.46   True        False         False      3m18s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      5m23s   
csi-snapshot-controller                    4.15.46   True        False         False      4m13s   
dns                                        4.15.46   True        False         False      5m49s   
image-registry                             4.15.46   True        False         False      5m43s   
ingress                                    4.15.46   True        False         False      5m28s   
insights                                   4.15.46   True        False         False      6m45s   
kube-apiserver                             4.15.46   True        False         False      11m     
kube-controller-manager                    4.15.46   True        False         False      11m     
kube-scheduler                             4.15.46   True        False         False      11m     
kube-storage-version-migrator              4.15.46   True        False         False      6m40s   
monitoring                                 4.15.46   True        False         False      94s     
network                                    4.15.46   True        False         False      11m     
node-tuning                                4.15.46   True        False         False      7m6s    
openshift-apiserver                        4.15.46   True        False         False      11m     
openshift-controller-manager               4.15.46   True        False         False      11m     
openshift-samples                          4.15.46   True        False         False      5m37s   
operator-lifecycle-manager                 4.15.46   True        False         False      11m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      11m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      11m     
service-ca                                 4.15.46   True        False         False      6m41s   
storage                                    4.15.46   True        False         False      4m18s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      6m23s   
csi-snapshot-controller                    4.15.46   True        False         False      5m13s   
dns                                        4.15.46   True        False         False      6m49s   
image-registry                             4.15.46   True        False         False      6m43s   
ingress                                    4.15.46   True        False         False      6m28s   
insights                                   4.15.46   True        False         False      7m45s   
kube-apiserver                             4.15.46   True        False         False      12m     
kube-controller-manager                    4.15.46   True        False         False      12m     
kube-scheduler                             4.15.46   True        False         False      12m     
kube-storage-version-migrator              4.15.46   True        False         False      7m40s   
monitoring                                 4.15.46   True        False         False      2m34s   
network                                    4.15.46   True        False         False      12m     
node-tuning                                4.15.46   True        False         False      8m6s    
openshift-apiserver                        4.15.46   True        False         False      12m     
openshift-controller-manager               4.15.46   True        False         False      12m     
openshift-samples                          4.15.46   True        False         False      6m37s   
operator-lifecycle-manager                 4.15.46   True        False         False      12m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      12m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      12m     
service-ca                                 4.15.46   True        False         False      7m41s   
storage                                    4.15.46   True        False         False      5m18s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      7m23s   
csi-snapshot-controller                    4.15.46   True        False         False      6m13s   
dns                                        4.15.46   True        False         False      7m49s   
image-registry                             4.15.46   True        False         False      7m43s   
ingress                                    4.15.46   True        False         False      7m28s   
insights                                   4.15.46   True        False         False      8m45s   
kube-apiserver                             4.15.46   True        False         False      13m     
kube-controller-manager                    4.15.46   True        False         False      13m     
kube-scheduler                             4.15.46   True        False         False      13m     
kube-storage-version-migrator              4.15.46   True        False         False      8m40s   
monitoring                                 4.15.46   True        False         False      3m34s   
network                                    4.15.46   True        False         False      13m     
node-tuning                                4.15.46   True        False         False      9m6s    
openshift-apiserver                        4.15.46   True        False         False      13m     
openshift-controller-manager               4.15.46   True        False         False      13m     
openshift-samples                          4.15.46   True        False         False      7m37s   
operator-lifecycle-manager                 4.15.46   True        False         False      13m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      13m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      13m     
service-ca                                 4.15.46   True        False         False      8m41s   
storage                                    4.15.46   True        False         False      6m18s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      8m24s   
csi-snapshot-controller                    4.15.46   True        False         False      7m14s   
dns                                        4.15.46   True        False         False      8m50s   
image-registry                             4.15.46   True        False         False      8m44s   
ingress                                    4.15.46   True        False         False      8m29s   
insights                                   4.15.46   True        False         False      9m46s   
kube-apiserver                             4.15.46   True        False         False      14m     
kube-controller-manager                    4.15.46   True        False         False      14m     
kube-scheduler                             4.15.46   True        False         False      14m     
kube-storage-version-migrator              4.15.46   True        False         False      9m41s   
monitoring                                 4.15.46   True        False         False      4m35s   
network                                    4.15.46   True        False         False      14m     
node-tuning                                4.15.46   True        False         False      10m     
openshift-apiserver                        4.15.46   True        False         False      14m     
openshift-controller-manager               4.15.46   True        False         False      14m     
openshift-samples                          4.15.46   True        False         False      8m38s   
operator-lifecycle-manager                 4.15.46   True        False         False      14m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      14m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      14m     
service-ca                                 4.15.46   True        False         False      9m42s   
storage                                    4.15.46   True        False         False      7m19s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      9m24s   
csi-snapshot-controller                    4.15.46   True        False         False      8m14s   
dns                                        4.15.46   True        False         False      9m50s   
image-registry                             4.15.46   True        False         False      9m44s   
ingress                                    4.15.46   True        False         False      9m29s   
insights                                   4.15.46   True        False         False      10m     
kube-apiserver                             4.15.46   True        False         False      15m     
kube-controller-manager                    4.15.46   True        False         False      15m     
kube-scheduler                             4.15.46   True        False         False      15m     
kube-storage-version-migrator              4.15.46   True        False         False      10m     
monitoring                                 4.15.46   True        False         False      5m35s   
network                                    4.15.46   True        False         False      15m     
node-tuning                                4.15.46   True        False         False      11m     
openshift-apiserver                        4.15.46   True        False         False      15m     
openshift-controller-manager               4.15.46   True        False         False      15m     
openshift-samples                          4.15.46   True        False         False      9m38s   
operator-lifecycle-manager                 4.15.46   True        False         False      15m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      15m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      15m     
service-ca                                 4.15.46   True        False         False      10m     
storage                                    4.15.46   True        False         False      8m19s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      10m     
csi-snapshot-controller                    4.15.46   True        False         False      9m14s   
dns                                        4.15.46   True        False         False      10m     
image-registry                             4.15.46   True        False         False      10m     
ingress                                    4.15.46   True        False         False      10m     
insights                                   4.15.46   True        False         False      11m     
kube-apiserver                             4.15.46   True        False         False      16m     
kube-controller-manager                    4.15.46   True        False         False      16m     
kube-scheduler                             4.15.46   True        False         False      16m     
kube-storage-version-migrator              4.15.46   True        False         False      11m     
monitoring                                 4.15.46   True        False         False      6m35s   
network                                    4.15.46   True        False         False      16m     
node-tuning                                4.15.46   True        False         False      12m     
openshift-apiserver                        4.15.46   True        False         False      16m     
openshift-controller-manager               4.15.46   True        False         False      16m     
openshift-samples                          4.15.46   True        False         False      10m     
operator-lifecycle-manager                 4.15.46   True        False         False      16m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      16m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      16m     
service-ca                                 4.15.46   True        False         False      11m     
storage                                    4.15.46   True        False         False      9m19s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      11m     
csi-snapshot-controller                    4.15.46   True        False         False      10m     
dns                                        4.15.46   True        False         False      11m     
image-registry                             4.15.46   True        False         False      11m     
ingress                                    4.15.46   True        False         False      11m     
insights                                   4.15.46   True        False         False      12m     
kube-apiserver                             4.15.46   True        False         False      17m     
kube-controller-manager                    4.15.46   True        False         False      17m     
kube-scheduler                             4.15.46   True        False         False      17m     
kube-storage-version-migrator              4.15.46   True        False         False      12m     
monitoring                                 4.15.46   True        False         False      7m36s   
network                                    4.15.46   True        False         False      17m     
node-tuning                                4.15.46   True        False         False      13m     
openshift-apiserver                        4.15.46   True        False         False      17m     
openshift-controller-manager               4.15.46   True        False         False      17m     
openshift-samples                          4.15.46   True        False         False      11m     
operator-lifecycle-manager                 4.15.46   True        False         False      17m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      17m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      17m     
service-ca                                 4.15.46   True        False         False      12m     
storage                                    4.15.46   True        False         False      10m     
Waiting for cluster to be reported as healthy... Trying again in 60s
healthy
cluster to be reported as healthy finished!
</pre></details>

---
author_association: NONE
user: login: konflux-ci-qe-bot
created_at: 2025-03-14T04:55:34Z
body: @jinqi7: The following test has Failed, say **/retest** to rerun failed tests.

| PipelineRun Name | Status | Rerun command | Build Log | Test Log |
|------------------|--------|---------------|-----------|----------|
| `konflux-e2e-tests-5rvsg`    | **Failed** | `/retest` | [View Pipeline Log](https://console.redhat.com/application-pipeline/ns/rhtap-release-2-tenant/pipelinerun/release-service-on-pull-request-dbx4c) | [View Test Logs](https://console.redhat.com/application-pipeline/ns/rhtap-release-2-tenant/pipelinerun/konflux-e2e-tests-5rvsg) |

### Inspecting Test Artifacts
To inspect your test artifacts, follow these steps:
1. Install **ORAS** (see the [ORAS installation guide](https://oras.land/docs/installation)).
2. Download artifacts with the following commands:

```sh
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/release-service:konflux-e2e-tests-5rvsg
```
### Test results analysis
:rotating_light: **Failed to provision a cluster, see the log for more details**: 

 <details><summary>Click to view logs</summary><br>
<pre>INFO: Log in to your Red Hat account...
INFO: Configure AWS Credentials...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
INFO: Logged in as 'konflux-ci-418295695583' on 'https://api.openshift.com'
INFO: Create ROSA with HCP cluster...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
time=2025-03-14T01:33:02Z level=info msg=Ignored check for policy key 'sts_hcp_ec2_registry_permission_policy' (zero egress feature toggle is not enabled)
INFO: Creating cluster 'kx-1608e4edd9'
INFO: To view a list of clusters and their status, run 'rosa list clusters'
INFO: Cluster 'kx-1608e4edd9' has been created.
INFO: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information.

Name:                       kx-1608e4edd9
Domain Prefix:              kx-1608e4edd9
Display Name:               kx-1608e4edd9
ID:                         2hgjim2jcrk5b473feb5ki5mvv9aprrl
External ID:                068efd7c-79f6-46fa-a18d-94ccb6de9410
Control Plane:              ROSA Service Hosted
OpenShift Version:          4.15.46
Channel Group:              stable
DNS:                        Not ready
AWS Account:                418295695583
AWS Billing Account:        418295695583
API URL:                    
Console URL:                
Region:                     us-east-1
Availability:
 - Control Plane:           MultiAZ
 - Data Plane:              SingleAZ

Nodes:
 - Compute (desired):       3
 - Compute (current):       0
Network:
 - Type:                    OVNKubernetes
 - Service CIDR:            172.30.0.0/16
 - Machine CIDR:            10.0.0.0/16
 - Pod CIDR:                10.128.0.0/14
 - Host Prefix:             /23
 - Subnets:                 subnet-05b9daa0609597f68, subnet-04cf6376374bf9e09
EC2 Metadata Http Tokens:   optional
Role (STS) ARN:             arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Installer-Role
Support Role ARN:           arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Support-Role
Instance IAM Roles:
 - Worker:                  arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Worker-Role
Operator IAM Roles:
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cloud-network-config-controller-cloud-credent
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-image-registry-installer-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-ingress-operator-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kube-controller-manager
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-capa-controller-manager
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-control-plane-operator
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kms-provider
Managed Policies:           Yes
State:                      waiting (Waiting for user action)
Private:                    No
Delete Protection:          Disabled
Created:                    Mar 14 2025 01:33:19 UTC
User Workload Monitoring:   Enabled
Details Page:               https://console.redhat.com/openshift/details/s/2uHqlfLuXLCJHiyRJ4Xuhy8lx1k
OIDC Endpoint URL:          https://oidc.op1.openshiftapps.com/2du11g36ejmoo4624pofphlrgf4r9tf3 (Managed)
Etcd Encryption:            Disabled
Audit Log Forwarding:       Disabled
External Authentication:    Disabled
Zero Egress:                Disabled


INFO: Preparing to create operator roles.
INFO: Operator Roles already exists
INFO: Preparing to create OIDC Provider.
INFO: OIDC provider already exists
INFO: To determine when your cluster is Ready, run 'rosa describe cluster -c kx-1608e4edd9'.
INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-1608e4edd9 --watch'.
INFO: Track the progress of the cluster creation...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
[0;33mW:[m Region flag will be removed from this command in future versions
INFO: Cluster 'kx-1608e4edd9' is in waiting state waiting for installation to begin. Logs will show up within 5 minutes
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-1608e4edd9 Version 
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 The hosted control plane is not found
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 The hosted control plane is not found
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 The hosted control plane is not found
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 The hosted control plane is not found
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 The hosted control plane is not found
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 The hosted control plane is not found
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Waiting for hosted control plane to be healthy
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 The hosted control plane is not found
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Ignition server deployment not found
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Configuration passes validation
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 HostedCluster is supported by operator configuration
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Reconciliation active on resource
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 ValidAWSIdentityProvider StatusUnknown
2025-03-14 01:37:47 +0000 UTC hostedclusters kx-1608e4edd9 Release image is valid
2025-03-14 01:37:48 +0000 UTC hostedclusters kx-1608e4edd9 HostedCluster is at expected version
2025-03-14 01:37:49 +0000 UTC hostedclusters kx-1608e4edd9 Required platform credentials are found
2025-03-14 01:37:50 +0000 UTC hostedclusters kx-1608e4edd9 failed to get referenced secret ocm-production-2hgjim2jcrk5b473feb5ki5mvv9aprrl/cluster-api-cert: Secret "cluster-api-cert" not found
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-1608e4edd9 Version 
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Reconciliation active on resource
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 router load balancer is not provisioned; 3s since creation.; router load balancer is not provisioned; 3s since creation.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 HostedCluster is supported by operator configuration
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Configuration passes validation
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Ignition server deployment not found
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:47 +0000 UTC hostedclusters kx-1608e4edd9 Release image is valid
2025-03-14 01:37:48 +0000 UTC hostedclusters kx-1608e4edd9 HostedCluster is at expected version
2025-03-14 01:37:49 +0000 UTC hostedclusters kx-1608e4edd9 Required platform credentials are found
2025-03-14 01:39:20 +0000 UTC hostedclusters kx-1608e4edd9 OIDC configuration is valid
2025-03-14 01:39:20 +0000 UTC hostedclusters kx-1608e4edd9 Reconciliation completed successfully
2025-03-14 01:39:28 +0000 UTC hostedclusters kx-1608e4edd9 WebIdentityErr
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 EtcdAvailable StatefulSetNotFound
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 router load balancer is not provisioned; 3s since creation.; router load balancer is not provisioned; 3s since creation.
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 Kube APIServer deployment not found
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 AWS KMS is not configured
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 All is well
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 capi-provider deployment has 1 unavailable replicas
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 Configuration passes validation
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 lookup api.kx-1608e4edd9.e3dw.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-03-14 01:39:38 +0000 UTC hostedclusters kx-1608e4edd9 All is well
2025-03-14 01:40:32 +0000 UTC hostedclusters kx-1608e4edd9 EtcdAvailable QuorumAvailable
2025-03-14 01:41:33 +0000 UTC hostedclusters kx-1608e4edd9 Kube APIServer deployment is available
2025-03-14 01:41:39 +0000 UTC hostedclusters kx-1608e4edd9 All is well
2025-03-14 01:42:04 +0000 UTC hostedclusters kx-1608e4edd9 The hosted cluster is not degraded
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-1608e4edd9 Version 
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Reconciliation active on resource
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Get "https://a0c02bed5ef9143de9de49ed3feeae32-36713eebdca9970e.elb.us-east-1.amazonaws.com:443/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 HostedCluster is supported by operator configuration
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Configuration passes validation
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Ignition server deployment is not yet available
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:47 +0000 UTC hostedclusters kx-1608e4edd9 Release image is valid
2025-03-14 01:37:48 +0000 UTC hostedclusters kx-1608e4edd9 HostedCluster is at expected version
2025-03-14 01:37:49 +0000 UTC hostedclusters kx-1608e4edd9 Required platform credentials are found
2025-03-14 01:39:20 +0000 UTC hostedclusters kx-1608e4edd9 OIDC configuration is valid
2025-03-14 01:39:20 +0000 UTC hostedclusters kx-1608e4edd9 Reconciliation completed successfully
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 lookup api.kx-1608e4edd9.e3dw.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 Configuration passes validation
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 All is well
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 AWS KMS is not configured
2025-03-14 01:39:38 +0000 UTC hostedclusters kx-1608e4edd9 All is well
2025-03-14 01:40:32 +0000 UTC hostedclusters kx-1608e4edd9 EtcdAvailable QuorumAvailable
2025-03-14 01:41:33 +0000 UTC hostedclusters kx-1608e4edd9 Kube APIServer deployment is available
2025-03-14 01:41:39 +0000 UTC hostedclusters kx-1608e4edd9 All is well
2025-03-14 01:42:10 +0000 UTC hostedclusters kx-1608e4edd9 All is well
2025-03-14 01:42:10 +0000 UTC hostedclusters kx-1608e4edd9 [aws-cloud-controller-manager deployment has 1 unavailable replicas, catalog-operator deployment has 1 unavailable replicas, certified-operators-catalog deployment has 1 unavailable replicas, cloud-credential-operator deployment has 1 unavailable replicas, cluster-image-registry-operator deployment has 1 unavailable replicas, cluster-network-operator deployment has 1 unavailable replicas, cluster-node-tuning-operator deployment has 1 unavailable replicas, cluster-policy-controller deployment has 3 unavailable replicas, cluster-storage-operator deployment has 1 unavailable replicas, cluster-version-operator deployment has 1 unavailable replicas, community-operators-catalog deployment has 1 unavailable replicas, csi-snapshot-controller-operator deployment has 1 unavailable replicas, dns-operator deployment has 1 unavailable replicas, hosted-cluster-config-operator deployment has 1 unavailable replicas, ingress-operator deployment has 1 unavailable replicas, konnectivity-agent deployment has 1 unavailable replicas, machine-approver deployment has 1 unavailable replicas, oauth-openshift deployment has 2 unavailable replicas, olm-operator deployment has 1 unavailable replicas, openshift-controller-manager deployment has 3 unavailable replicas, openshift-oauth-apiserver deployment has 3 unavailable replicas, openshift-route-controller-manager deployment has 3 unavailable replicas, packageserver deployment has 3 unavailable replicas, redhat-marketplace-catalog deployment has 1 unavailable replicas, redhat-operators-catalog deployment has 1 unavailable replicas, router deployment has 1 unavailable replicas]
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-1608e4edd9 Version 
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Reconciliation active on resource
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 HostedCluster is supported by operator configuration
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Configuration passes validation
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Ignition server deployment is not yet available
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:40 +0000 UTC hostedclusters kx-1608e4edd9 Condition not found in the CVO.
2025-03-14 01:37:47 +0000 UTC hostedclusters kx-1608e4edd9 Release image is valid
2025-03-14 01:37:48 +0000 UTC hostedclusters kx-1608e4edd9 HostedCluster is at expected version
2025-03-14 01:37:49 +0000 UTC hostedclusters kx-1608e4edd9 Required platform credentials are found
2025-03-14 01:39:20 +0000 UTC hostedclusters kx-1608e4edd9 OIDC configuration is valid
2025-03-14 01:39:20 +0000 UTC hostedclusters kx-1608e4edd9 Reconciliation completed successfully
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 AWS KMS is not configured
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 All is well
2025-03-14 01:39:30 +0000 UTC hostedclusters kx-1608e4edd9 Configuration passes validation
2025-03-14 01:39:38 +0000 UTC hostedclusters kx-1608e4edd9 All is well
2025-03-14 01:40:32 +0000 UTC hostedclusters kx-1608e4edd9 EtcdAvailable QuorumAvailable
2025-03-14 01:41:33 +0000 UTC hostedclusters kx-1608e4edd9 Kube APIServer deployment is available
2025-03-14 01:41:39 +0000 UTC hostedclusters kx-1608e4edd9 All is well
2025-03-14 01:42:10 +0000 UTC hostedclusters kx-1608e4edd9 All is well
2025-03-14 01:42:10 +0000 UTC hostedclusters kx-1608e4edd9 [catalog-operator deployment has 1 unavailable replicas, certified-operators-catalog deployment has 2 unavailable replicas, cloud-credential-operator deployment has 1 unavailable replicas, cluster-network-operator deployment has 1 unavailable replicas, cluster-storage-operator deployment has 1 unavailable replicas, community-operators-catalog deployment has 2 unavailable replicas, csi-snapshot-controller-operator deployment has 1 unavailable replicas, dns-operator deployment has 1 unavailable replicas, hosted-cluster-config-operator deployment has 1 unavailable replicas, ignition-server deployment has 3 unavailable replicas, ingress-operator deployment has 1 unavailable replicas, olm-operator deployment has 1 unavailable replicas, packageserver deployment has 3 unavailable replicas, redhat-marketplace-catalog deployment has 2 unavailable replicas, redhat-operators-catalog deployment has 2 unavailable replicas, router deployment has 1 unavailable replicas]
2025-03-14 01:42:43 +0000 UTC hostedclusters kx-1608e4edd9 The hosted control plane is available
INFO: Cluster 'kx-1608e4edd9' is now ready
INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
INFO: Storing login command...
INFO: Check if it's able to login to OCP cluster...
Retried 1 times...
INFO: Check if apiserver is ready...
.....Waiting for cluster operators to be accessible for 2m...
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      3m16s   
dns                                        4.15.46   False       False         True       3m16s   DNS "default" is unavailable.
image-registry                                       False       True          True       2m40s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       2m44s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      3m12s   
kube-controller-manager                    4.15.46   True        False         False      3m12s   
kube-scheduler                             4.15.46   True        False         False      3m12s   
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      2m47s   Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning                                          False       True          False      3m20s   DaemonSet "tuned" has no available Pod(s)
openshift-apiserver                        4.15.46   True        False         False      3m12s   
openshift-controller-manager               4.15.46   True        False         False      3m12s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      3m15s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      3m15s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      3m12s   
service-ca                                                                                        
storage                                    4.15.46   False       False         False      3m11s   AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service
cluster operators to be accessible finished!
[INFO] Cluster operators are accessible.
Waiting for cluster to be reported as healthy for 60m...
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      3m17s   
dns                                        4.15.46   False       False         True       3m17s   DNS "default" is unavailable.
image-registry                                       False       True          True       2m41s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       2m45s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      3m13s   
kube-controller-manager                    4.15.46   True        False         False      3m13s   
kube-scheduler                             4.15.46   True        False         False      3m13s   
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      2m48s   Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning                                          False       True          False      3m21s   DaemonSet "tuned" has no available Pod(s)
openshift-apiserver                        4.15.46   True        False         False      3m13s   
openshift-controller-manager               4.15.46   True        False         False      3m13s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      3m16s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      3m16s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      3m13s   
service-ca                                                                                        
storage                                    4.15.46   False       False         False      3m12s   AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service
Waiting for cluster to be reported as healthy... Trying again in 60s
Unable to connect to the server: dial tcp: lookup api.kx-1608e4edd9.e3dw.p3.openshiftapps.com on 172.30.0.10:53: no such host
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      5m17s   
dns                                        4.15.46   False       False         True       5m17s   DNS "default" is unavailable.
image-registry                                       False       True          True       4m41s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       4m45s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      5m13s   
kube-controller-manager                    4.15.46   True        False         False      5m13s   
kube-scheduler                             4.15.46   True        False         False      5m13s   
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      4m48s   DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes)...
node-tuning                                4.15.46   True        False         False      12s     
openshift-apiserver                        4.15.46   True        False         False      5m13s   
openshift-controller-manager               4.15.46   True        False         False      5m13s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      5m16s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      5m16s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      5m13s   
service-ca                                                                                        
storage                                    4.15.46   True        False         False      12s     
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   False       True          False      18s     DeploymentAvailable: 0 replicas available for console deployment
csi-snapshot-controller                    4.15.46   True        False         False      6m17s   
dns                                        4.15.46   True        False         False      11s     
image-registry                                       False       True          True       5m41s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       5m45s   The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                   4.15.46   True        False         False      56s     
kube-apiserver                             4.15.46   True        False         False      6m13s   
kube-controller-manager                    4.15.46   True        False         False      6m13s   
kube-scheduler                             4.15.46   True        False         False      6m13s   
kube-storage-version-migrator              4.15.46   True        False         False      50s     
monitoring                                           Unknown     True          Unknown    29s     Rolling out the stack.
network                                    4.15.46   True        True          False      5m48s   DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes)
node-tuning                                4.15.46   True        False         False      72s     
openshift-apiserver                        4.15.46   True        False         False      6m13s   
openshift-controller-manager               4.15.46   True        False         False      6m13s   
openshift-samples                                    False       False         False      4s      SampleUpsertsPending
operator-lifecycle-manager                 4.15.46   True        False         False      6m16s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      6m16s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      6m13s   
service-ca                                 4.15.46   True        False         False      54s     
storage                                    4.15.46   True        False         False      72s     
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        True          False      48s     SyncLoopRefreshProgressing: Working toward version 4.15.46, 1 replicas available
csi-snapshot-controller                    4.15.46   True        False         False      7m18s   
dns                                        4.15.46   True        True          False      72s     DNS "default" reports Progressing=True: "Have 1 available node-resolver pods, want 2."
image-registry                                       True        True          False      48s     Progressing: The deployment has not completed...
ingress                                    4.15.46   True        True          False      48s     ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 old replica(s) are pending termination......
insights                                   4.15.46   True        False         False      117s    
kube-apiserver                             4.15.46   True        False         False      7m14s   
kube-controller-manager                    4.15.46   True        False         False      7m14s   
kube-scheduler                             4.15.46   True        False         False      7m14s   
kube-storage-version-migrator              4.15.46   True        False         False      111s    
monitoring                                           Unknown     True          Unknown    90s     Rolling out the stack.
network                                    4.15.46   True        True          False      6m49s   DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)...
node-tuning                                4.15.46   True        True          False      22s     Waiting for 1/2 Profiles to be applied
openshift-apiserver                        4.15.46   True        False         False      7m14s   
openshift-controller-manager               4.15.46   True        False         False      7m14s   
openshift-samples                          4.15.46   True        False         False      55s     
operator-lifecycle-manager                 4.15.46   True        False         False      7m17s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      7m17s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      7m14s   
service-ca                                 4.15.46   True        False         False      115s    
storage                                    4.15.46   True        True          False      2m13s   AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      108s    
csi-snapshot-controller                    4.15.46   True        False         False      8m18s   
dns                                        4.15.46   True        False         False      2m12s   
image-registry                             4.15.46   True        True          False      108s    Progressing: The deployment has not completed...
ingress                                    4.15.46   True        False         False      108s    
insights                                   4.15.46   True        False         False      2m57s   
kube-apiserver                             4.15.46   True        False         False      8m14s   
kube-controller-manager                    4.15.46   True        False         False      8m14s   
kube-scheduler                             4.15.46   True        False         False      8m14s   
kube-storage-version-migrator              4.15.46   True        False         False      2m51s   
monitoring                                           Unknown     True          Unknown    2m30s   Rolling out the stack.
network                                    4.15.46   True        True          False      7m49s   DaemonSet "/openshift-network-diagnostics/network-check-target" is not available (awaiting 1 nodes)
node-tuning                                4.15.46   True        False         False      82s     
openshift-apiserver                        4.15.46   True        False         False      8m14s   
openshift-controller-manager               4.15.46   True        False         False      8m14s   
openshift-samples                          4.15.46   True        False         False      115s    
operator-lifecycle-manager                 4.15.46   True        False         False      8m17s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      8m17s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      8m14s   
service-ca                                 4.15.46   True        False         False      2m55s   
storage                                    4.15.46   True        False         False      3m13s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      2m48s   
csi-snapshot-controller                    4.15.46   True        False         False      9m18s   
dns                                        4.15.46   True        False         False      3m12s   
image-registry                             4.15.46   True        False         False      2m48s   
ingress                                    4.15.46   True        False         False      2m48s   
insights                                   4.15.46   True        False         False      3m57s   
kube-apiserver                             4.15.46   True        False         False      9m14s   
kube-controller-manager                    4.15.46   True        False         False      9m14s   
kube-scheduler                             4.15.46   True        False         False      9m14s   
kube-storage-version-migrator              4.15.46   True        False         False      3m51s   
monitoring                                           Unknown     True          Unknown    3m30s   Rolling out the stack.
network                                    4.15.46   True        False         False      8m49s   
node-tuning                                4.15.46   True        False         False      2m22s   
openshift-apiserver                        4.15.46   True        False         False      9m14s   
openshift-controller-manager               4.15.46   True        False         False      9m14s   
openshift-samples                          4.15.46   True        False         False      2m55s   
operator-lifecycle-manager                 4.15.46   True        False         False      9m17s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      9m17s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      9m14s   
service-ca                                 4.15.46   True        False         False      3m55s   
storage                                    4.15.46   True        False         False      4m13s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      3m48s   
csi-snapshot-controller                    4.15.46   True        False         False      10m     
dns                                        4.15.46   True        False         False      4m12s   
image-registry                             4.15.46   True        False         False      3m48s   
ingress                                    4.15.46   True        False         False      3m48s   
insights                                   4.15.46   True        False         False      4m57s   
kube-apiserver                             4.15.46   True        False         False      10m     
kube-controller-manager                    4.15.46   True        False         False      10m     
kube-scheduler                             4.15.46   True        False         False      10m     
kube-storage-version-migrator              4.15.46   True        False         False      4m51s   
monitoring                                 4.15.46   True        False         False      19s     
network                                    4.15.46   True        False         False      9m49s   
node-tuning                                4.15.46   True        False         False      3m22s   
openshift-apiserver                        4.15.46   True        False         False      10m     
openshift-controller-manager               4.15.46   True        False         False      10m     
openshift-samples                          4.15.46   True        False         False      3m55s   
operator-lifecycle-manager                 4.15.46   True        False         False      10m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      10m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      10m     
service-ca                                 4.15.46   True        False         False      4m55s   
storage                                    4.15.46   True        False         False      5m13s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      4m48s   
csi-snapshot-controller                    4.15.46   True        False         False      11m     
dns                                        4.15.46   True        False         False      5m12s   
image-registry                             4.15.46   True        False         False      4m48s   
ingress                                    4.15.46   True        False         False      4m48s   
insights                                   4.15.46   True        False         False      5m57s   
kube-apiserver                             4.15.46   True        False         False      11m     
kube-controller-manager                    4.15.46   True        False         False      11m     
kube-scheduler                             4.15.46   True        False         False      11m     
kube-storage-version-migrator              4.15.46   True        False         False      5m51s   
monitoring                                 4.15.46   True        False         False      79s     
network                                    4.15.46   True        False         False      10m     
node-tuning                                4.15.46   True        False         False      4m22s   
openshift-apiserver                        4.15.46   True        False         False      11m     
openshift-controller-manager               4.15.46   True        False         False      11m     
openshift-samples                          4.15.46   True        False         False      4m55s   
operator-lifecycle-manager                 4.15.46   True        False         False      11m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      11m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      11m     
service-ca                                 4.15.46   True        False         False      5m55s   
storage                                    4.15.46   True        False         False      6m13s   
Waiting for cluster to be reported as healthy... Trying again in 60s
healthy
cluster to be reported as healthy finished!
</pre></details>

---
author_association: NONE
user: login: konflux-ci-qe-bot
created_at: 2025-03-14T05:51:12Z
body: @jinqi7: The following test has Failed, say **/retest** to rerun failed tests.

| PipelineRun Name | Status | Rerun command | Build Log | Test Log |
|------------------|--------|---------------|-----------|----------|
| `konflux-e2e-tests-djjg4`    | **Failed** | `/retest` | [View Pipeline Log](https://console.redhat.com/application-pipeline/ns/rhtap-release-2-tenant/pipelinerun/release-service-on-pull-request-rxsr6) | [View Test Logs](https://console.redhat.com/application-pipeline/ns/rhtap-release-2-tenant/pipelinerun/konflux-e2e-tests-djjg4) |

### Inspecting Test Artifacts
To inspect your test artifacts, follow these steps:
1. Install **ORAS** (see the [ORAS installation guide](https://oras.land/docs/installation)).
2. Download artifacts with the following commands:

```sh
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/release-service:konflux-e2e-tests-djjg4
```
### Test results analysis
:rotating_light: **Failed to provision a cluster, see the log for more details**: 

 <details><summary>Click to view logs</summary><br>
<pre>INFO: Log in to your Red Hat account...
INFO: Configure AWS Credentials...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
INFO: Logged in as 'konflux-ci-418295695583' on 'https://api.openshift.com'
INFO: Create ROSA with HCP cluster...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
time=2025-03-14T02:25:23Z level=info msg=Ignored check for policy key 'sts_hcp_ec2_registry_permission_policy' (zero egress feature toggle is not enabled)
INFO: Creating cluster 'kx-2c90ee9b90'
INFO: To view a list of clusters and their status, run 'rosa list clusters'
INFO: Cluster 'kx-2c90ee9b90' has been created.
INFO: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information.

Name:                       kx-2c90ee9b90
Domain Prefix:              kx-2c90ee9b90
Display Name:               kx-2c90ee9b90
ID:                         2hgkb780p7l0kmtvt4apctamm011off4
External ID:                9d347c74-316c-4547-b2f9-2bcb7cfc0137
Control Plane:              ROSA Service Hosted
OpenShift Version:          4.15.46
Channel Group:              stable
DNS:                        Not ready
AWS Account:                418295695583
AWS Billing Account:        418295695583
API URL:                    
Console URL:                
Region:                     us-east-1
Availability:
 - Control Plane:           MultiAZ
 - Data Plane:              SingleAZ

Nodes:
 - Compute (desired):       3
 - Compute (current):       0
Network:
 - Type:                    OVNKubernetes
 - Service CIDR:            172.30.0.0/16
 - Machine CIDR:            10.0.0.0/16
 - Pod CIDR:                10.128.0.0/14
 - Host Prefix:             /23
 - Subnets:                 subnet-05b9daa0609597f68, subnet-04cf6376374bf9e09
EC2 Metadata Http Tokens:   optional
Role (STS) ARN:             arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Installer-Role
Support Role ARN:           arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Support-Role
Instance IAM Roles:
 - Worker:                  arn:aws:iam::418295695583:role/ManagedOpenShift-HCP-ROSA-Worker-Role
Operator IAM Roles:
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-image-registry-installer-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-ingress-operator-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cluster-csi-drivers-ebs-cloud-credentials
 - arn:aws:iam::418295695583:role/rosa-hcp-openshift-cloud-network-config-controller-cloud-credent
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kms-provider
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kube-controller-manager
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-capa-controller-manager
 - arn:aws:iam::418295695583:role/rosa-hcp-kube-system-control-plane-operator
Managed Policies:           Yes
State:                      waiting (Waiting for user action)
Private:                    No
Delete Protection:          Disabled
Created:                    Mar 14 2025 02:25:38 UTC
User Workload Monitoring:   Enabled
Details Page:               https://console.redhat.com/openshift/details/s/2uHx81DmkAUhtQ6iSUCIYfc8inz
OIDC Endpoint URL:          https://oidc.op1.openshiftapps.com/2du11g36ejmoo4624pofphlrgf4r9tf3 (Managed)
Etcd Encryption:            Disabled
Audit Log Forwarding:       Disabled
External Authentication:    Disabled
Zero Egress:                Disabled


INFO: Preparing to create operator roles.
INFO: Operator Roles already exists
INFO: Preparing to create OIDC Provider.
INFO: OIDC provider already exists
INFO: To determine when your cluster is Ready, run 'rosa describe cluster -c kx-2c90ee9b90'.
INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-2c90ee9b90 --watch'.
INFO: Track the progress of the cluster creation...
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
[0;33mW:[m Region flag will be removed from this command in future versions
INFO: Cluster 'kx-2c90ee9b90' is in waiting state waiting for installation to begin. Logs will show up within 5 minutes
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-2c90ee9b90 Version 
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 The hosted control plane is not found
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 The hosted control plane is not found
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 The hosted control plane is not found
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 The hosted control plane is not found
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 The hosted control plane is not found
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 The hosted control plane is not found
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Waiting for hosted control plane to be healthy
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 The hosted control plane is not found
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Ignition server deployment not found
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Configuration passes validation
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 HostedCluster is supported by operator configuration
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Reconciliation active on resource
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 ValidAWSIdentityProvider StatusUnknown
2025-03-14 02:31:13 +0000 UTC hostedclusters kx-2c90ee9b90 Release image is valid
2025-03-14 02:31:14 +0000 UTC hostedclusters kx-2c90ee9b90 HostedCluster is at expected version
2025-03-14 02:31:15 +0000 UTC hostedclusters kx-2c90ee9b90 Required platform credentials are found
2025-03-14 02:31:15 +0000 UTC hostedclusters kx-2c90ee9b90 failed to get referenced secret ocm-production-2hgkb780p7l0kmtvt4apctamm011off4/cluster-api-cert: Secret "cluster-api-cert" not found
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-2c90ee9b90 Version 
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Reconciliation active on resource
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\\n\\tstatus code: 400, request id: 1260bdde-496d-4f02-b35e-b3ff36fdcfb7\""; private-router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\\n\\tstatus code: 400, request id: dc6aa8aa-0bf6-47d3-a5c0-5b06a944d633\""; router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\\n\\tstatus code: 400, request id: 1260bdde-496d-4f02-b35e-b3ff36fdcfb7\""
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 HostedCluster is supported by operator configuration
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Configuration passes validation
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Ignition server deployment not found
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:13 +0000 UTC hostedclusters kx-2c90ee9b90 Release image is valid
2025-03-14 02:31:14 +0000 UTC hostedclusters kx-2c90ee9b90 HostedCluster is at expected version
2025-03-14 02:31:15 +0000 UTC hostedclusters kx-2c90ee9b90 Required platform credentials are found
2025-03-14 02:34:06 +0000 UTC hostedclusters kx-2c90ee9b90 OIDC configuration is valid
2025-03-14 02:34:06 +0000 UTC hostedclusters kx-2c90ee9b90 Reconciliation completed successfully
2025-03-14 02:34:07 +0000 UTC hostedclusters kx-2c90ee9b90 WebIdentityErr
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 EtcdAvailable StatefulSetNotFound
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\\n\\tstatus code: 400, request id: 1260bdde-496d-4f02-b35e-b3ff36fdcfb7\""; private-router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\\n\\tstatus code: 400, request id: dc6aa8aa-0bf6-47d3-a5c0-5b06a944d633\""; router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error creating listener: "error trying to register targets in target group: \"InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\\n\\tstatus code: 400, request id: 1260bdde-496d-4f02-b35e-b3ff36fdcfb7\""
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 Kube APIServer deployment not found
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 AWS KMS is not configured
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 All is well
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 capi-provider deployment has 1 unavailable replicas
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 Configuration passes validation
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 lookup api.kx-2c90ee9b90.6wae.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-03-14 02:34:26 +0000 UTC hostedclusters kx-2c90ee9b90 failed to get controlPlaneOperatorImageLabels: failed to look up image metadata for quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c8007f9e26ff743d5c829758f09ce0b4b4806660ae44e2a936f29ac9ab32d690: failed to create repository client for https://quay.io: endpoint "https://quay.io" does not support v2 API (got 502 Bad Gateway)
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-2c90ee9b90 Version 
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Reconciliation active on resource
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\n\tstatus code: 400, request id: a0fcf393-25f6-4215-95c0-00be74b813aa"; private-router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\n\tstatus code: 400, request id: e7f7e809-d3c3-40ae-a18b-9237c1263825"; router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\n\tstatus code: 400, request id: a0fcf393-25f6-4215-95c0-00be74b813aa"
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 HostedCluster is supported by operator configuration
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Configuration passes validation
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Ignition server deployment not found
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:10 +0000 UTC hostedclusters kx-2c90ee9b90 Condition not found in the CVO.
2025-03-14 02:31:13 +0000 UTC hostedclusters kx-2c90ee9b90 Release image is valid
2025-03-14 02:31:14 +0000 UTC hostedclusters kx-2c90ee9b90 HostedCluster is at expected version
2025-03-14 02:31:15 +0000 UTC hostedclusters kx-2c90ee9b90 Required platform credentials are found
2025-03-14 02:34:06 +0000 UTC hostedclusters kx-2c90ee9b90 OIDC configuration is valid
2025-03-14 02:34:07 +0000 UTC hostedclusters kx-2c90ee9b90 WebIdentityErr
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 EtcdAvailable StatefulSetNotFound
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 Kube APIServer deployment not found
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\n\tstatus code: 400, request id: a0fcf393-25f6-4215-95c0-00be74b813aa"; private-router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\n\tstatus code: 400, request id: e7f7e809-d3c3-40ae-a18b-9237c1263825"; router load balancer is not provisioned: Error syncing load balancer: failed to ensure load balancer: error trying to register targets in target group: "InvalidTarget: The following targets are not in a running state and cannot be registered: 'i-0bae7a4ae48844f02'\n\tstatus code: 400, request id: a0fcf393-25f6-4215-95c0-00be74b813aa"
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 All is well
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 AWS KMS is not configured
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 Configuration passes validation
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 capi-provider deployment has 1 unavailable replicas
2025-03-14 02:34:08 +0000 UTC hostedclusters kx-2c90ee9b90 lookup api.kx-2c90ee9b90.6wae.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-03-14 02:34:40 +0000 UTC hostedclusters kx-2c90ee9b90 Reconciliation completed successfully
2025-03-14 02:35:32 +0000 UTC hostedclusters kx-2c90ee9b90 All is well
2025-03-14 02:36:18 +0000 UTC hostedclusters kx-2c90ee9b90 EtcdAvailable QuorumAvailable
2025-03-14 02:37:30 +0000 UTC hostedclusters kx-2c90ee9b90 Kube APIServer deployment is available
2025-03-14 02:37:37 +0000 UTC hostedclusters kx-2c90ee9b90 All is well
2025-03-14 02:37:56 +0000 UTC hostedclusters kx-2c90ee9b90 All is well
2025-03-14 02:38:13 +0000 UTC hostedclusters kx-2c90ee9b90 The hosted control plane is available
INFO: Cluster 'kx-2c90ee9b90' is now ready
INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster
WARN: The current version (1.2.50) is not up to date with latest rosa cli released version (1.2.51).
WARN: It is recommended that you update to the latest version.
INFO: Storing login command...
INFO: Check if it's able to login to OCP cluster...
Retried 1 times...
Retried 2 times...
INFO: Check if apiserver is ready...
Waiting for cluster operators to be accessible for 2m...
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      3m16s   
dns                                        4.15.46   False       False         True       3m27s   DNS "default" is unavailable.
image-registry                                       False       True          True       2m58s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       3m7s    The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      3m27s   
kube-controller-manager                    4.15.46   True        False         False      3m27s   
kube-scheduler                             4.15.46   True        False         False      3m27s   
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      3m3s    Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning                                          False       True          False      3m11s   DaemonSet "tuned" has no available Pod(s)
openshift-apiserver                        4.15.46   True        False         False      3m27s   
openshift-controller-manager               4.15.46   True        False         False      3m27s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      3m27s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      3m29s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      3m27s   
service-ca                                                                                        
storage                                    4.15.46   False       False         False      3m25s   AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service
cluster operators to be accessible finished!
[INFO] Cluster operators are accessible.
Waiting for cluster to be reported as healthy for 60m...
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      3m17s   
dns                                        4.15.46   False       False         True       3m28s   DNS "default" is unavailable.
image-registry                                       False       True          True       2m59s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       3m8s    The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      3m28s   
kube-controller-manager                    4.15.46   True        False         False      3m28s   
kube-scheduler                             4.15.46   True        False         False      3m28s   
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      3m4s    Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning                                          False       True          False      3m12s   DaemonSet "tuned" has no available Pod(s)
openshift-apiserver                        4.15.46   True        False         False      3m28s   
openshift-controller-manager               4.15.46   True        False         False      3m28s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      3m28s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      3m30s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      3m28s   
service-ca                                                                                        
storage                                    4.15.46   False       False         False      3m26s   AWSEBSCSIDriverOperatorCRAvailable: AWSEBSDriverNodeServiceControllerAvailable: Waiting for the DaemonSet to deploy the CSI Node Service
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      4m17s   
dns                                        4.15.46   False       False         True       4m28s   DNS "default" is unavailable.
image-registry                                       False       True          True       3m59s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       4m8s    The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                                                                          
kube-apiserver                             4.15.46   True        False         False      4m28s   
kube-controller-manager                    4.15.46   True        False         False      4m28s   
kube-scheduler                             4.15.46   True        False         False      4m28s   
kube-storage-version-migrator                                                                     
monitoring                                                                                        
network                                    4.15.46   True        True          False      4m4s    DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 2 nodes)...
node-tuning                                4.15.46   True        True          False      25s     Waiting for 2/2 Profiles to be applied
openshift-apiserver                        4.15.46   True        False         False      4m28s   
openshift-controller-manager               4.15.46   True        False         False      4m28s   
openshift-samples                                                                                 
operator-lifecycle-manager                 4.15.46   True        False         False      4m28s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      4m30s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      4m28s   
service-ca                                                                                        
storage                                    4.15.46   True        True          False      12s     AWSEBSCSIDriverOperatorCRProgressing: AWSEBSDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                                                                           
csi-snapshot-controller                    4.15.46   True        False         False      5m17s   
dns                                        4.15.46   False       True          True       5m28s   DNS "default" is unavailable.
image-registry                                       False       True          True       4m59s   Available: The deployment does not have available replicas...
ingress                                              False       True          True       5m8s    The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
insights                                   4.15.46   True        False         False      51s     
kube-apiserver                             4.15.46   True        False         False      5m28s   
kube-controller-manager                    4.15.46   True        False         False      5m28s   
kube-scheduler                             4.15.46   True        False         False      5m28s   
kube-storage-version-migrator              4.15.46   True        False         False      36s     
monitoring                                                                                        
network                                    4.15.46   True        True          False      5m4s    DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 2 nodes)...
node-tuning                                4.15.46   True        False         False      85s     
openshift-apiserver                        4.15.46   True        False         False      5m28s   
openshift-controller-manager               4.15.46   True        False         False      5m28s   
openshift-samples                                    False       False         False      1s      SampleUpsertsPending
operator-lifecycle-manager                 4.15.46   True        False         False      5m28s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      5m30s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      5m28s   
service-ca                                 4.15.46   True        False         False      49s     
storage                                    4.15.46   True        False         False      72s     
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      45s     
csi-snapshot-controller                    4.15.46   True        False         False      6m17s   
dns                                        4.15.46   True        False         False      60s     
image-registry                             4.15.46   True        True          False      34s     Progressing: The deployment has not completed...
ingress                                    4.15.46   True        True          False      23s     ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available......
insights                                   4.15.46   True        False         False      111s    
kube-apiserver                             4.15.46   True        False         False      6m28s   
kube-controller-manager                    4.15.46   True        False         False      6m28s   
kube-scheduler                             4.15.46   True        False         False      6m28s   
kube-storage-version-migrator              4.15.46   True        False         False      96s     
monitoring                                           Unknown     True          Unknown    51s     Rolling out the stack.
network                                    4.15.46   True        True          False      6m4s    DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes)...
node-tuning                                4.15.46   True        False         False      58s     
openshift-apiserver                        4.15.46   True        False         False      6m28s   
openshift-controller-manager               4.15.46   True        False         False      6m28s   
openshift-samples                          4.15.46   True        False         False      51s     
operator-lifecycle-manager                 4.15.46   True        False         False      6m28s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      6m30s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      6m28s   
service-ca                                 4.15.46   True        False         False      109s    
storage                                    4.15.46   True        False         False      2m12s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      106s    
csi-snapshot-controller                    4.15.46   True        False         False      7m18s   
dns                                        4.15.46   True        False         False      2m1s    
image-registry                             4.15.46   True        False         False      95s     
ingress                                    4.15.46   True        False         False      84s     
insights                                   4.15.46   True        False         False      2m52s   
kube-apiserver                             4.15.46   True        False         False      7m29s   
kube-controller-manager                    4.15.46   True        False         False      7m29s   
kube-scheduler                             4.15.46   True        False         False      7m29s   
kube-storage-version-migrator              4.15.46   True        False         False      2m37s   
monitoring                                 4.15.46   True        False         False      11s     
network                                    4.15.46   True        False         False      7m5s    
node-tuning                                4.15.46   True        False         False      119s    
openshift-apiserver                        4.15.46   True        False         False      7m29s   
openshift-controller-manager               4.15.46   True        False         False      7m29s   
openshift-samples                          4.15.46   True        False         False      112s    
operator-lifecycle-manager                 4.15.46   True        False         False      7m29s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      7m31s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      7m29s   
service-ca                                 4.15.46   True        False         False      2m50s   
storage                                    4.15.46   True        False         False      3m13s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      2m46s   
csi-snapshot-controller                    4.15.46   True        False         False      8m18s   
dns                                        4.15.46   True        False         False      3m1s    
image-registry                             4.15.46   True        False         False      2m35s   
ingress                                    4.15.46   True        False         False      2m24s   
insights                                   4.15.46   True        False         False      3m52s   
kube-apiserver                             4.15.46   True        False         False      8m29s   
kube-controller-manager                    4.15.46   True        False         False      8m29s   
kube-scheduler                             4.15.46   True        False         False      8m29s   
kube-storage-version-migrator              4.15.46   True        False         False      3m37s   
monitoring                                 4.15.46   True        False         False      71s     
network                                    4.15.46   True        False         False      8m5s    
node-tuning                                4.15.46   True        False         False      2m59s   
openshift-apiserver                        4.15.46   True        False         False      8m29s   
openshift-controller-manager               4.15.46   True        False         False      8m29s   
openshift-samples                          4.15.46   True        False         False      2m52s   
operator-lifecycle-manager                 4.15.46   True        False         False      8m29s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      8m31s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      8m29s   
service-ca                                 4.15.46   True        False         False      3m50s   
storage                                    4.15.46   True        False         False      4m13s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      3m46s   
csi-snapshot-controller                    4.15.46   True        False         False      9m18s   
dns                                        4.15.46   True        False         False      4m1s    
image-registry                             4.15.46   True        False         False      3m35s   
ingress                                    4.15.46   True        False         False      3m24s   
insights                                   4.15.46   True        False         False      4m52s   
kube-apiserver                             4.15.46   True        False         False      9m29s   
kube-controller-manager                    4.15.46   True        False         False      9m29s   
kube-scheduler                             4.15.46   True        False         False      9m29s   
kube-storage-version-migrator              4.15.46   True        False         False      4m37s   
monitoring                                 4.15.46   True        False         False      2m11s   
network                                    4.15.46   True        False         False      9m5s    
node-tuning                                4.15.46   True        False         False      3m59s   
openshift-apiserver                        4.15.46   True        False         False      9m29s   
openshift-controller-manager               4.15.46   True        False         False      9m29s   
openshift-samples                          4.15.46   True        False         False      3m52s   
operator-lifecycle-manager                 4.15.46   True        False         False      9m29s   
operator-lifecycle-manager-catalog         4.15.46   True        False         False      9m31s   
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      9m29s   
service-ca                                 4.15.46   True        False         False      4m50s   
storage                                    4.15.46   True        False         False      5m13s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      4m46s   
csi-snapshot-controller                    4.15.46   True        False         False      10m     
dns                                        4.15.46   True        False         False      5m1s    
image-registry                             4.15.46   True        False         False      4m35s   
ingress                                    4.15.46   True        False         False      4m24s   
insights                                   4.15.46   True        False         False      5m52s   
kube-apiserver                             4.15.46   True        False         False      10m     
kube-controller-manager                    4.15.46   True        False         False      10m     
kube-scheduler                             4.15.46   True        False         False      10m     
kube-storage-version-migrator              4.15.46   True        False         False      5m37s   
monitoring                                 4.15.46   True        False         False      3m11s   
network                                    4.15.46   True        False         False      10m     
node-tuning                                4.15.46   True        False         False      4m59s   
openshift-apiserver                        4.15.46   True        False         False      10m     
openshift-controller-manager               4.15.46   True        False         False      10m     
openshift-samples                          4.15.46   True        False         False      4m52s   
operator-lifecycle-manager                 4.15.46   True        False         False      10m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      10m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      10m     
service-ca                                 4.15.46   True        False         False      5m50s   
storage                                    4.15.46   True        False         False      6m13s   
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME                                       VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
console                                    4.15.46   True        False         False      5m47s   
csi-snapshot-controller                    4.15.46   True        False         False      11m     
dns                                        4.15.46   True        False         False      6m2s    
image-registry                             4.15.46   True        False         False      5m36s   
ingress                                    4.15.46   True        False         False      5m25s   
insights                                   4.15.46   True        False         False      6m53s   
kube-apiserver                             4.15.46   True        False         False      11m     
kube-controller-manager                    4.15.46   True        False         False      11m     
kube-scheduler                             4.15.46   True        False         False      11m     
kube-storage-version-migrator              4.15.46   True        False         False      6m38s   
monitoring                                 4.15.46   True        False         False      4m12s   
network                                    4.15.46   True        False         False      11m     
node-tuning                                4.15.46   True        False         False      6m      
openshift-apiserver                        4.15.46   True        False         False      11m     
openshift-controller-manager               4.15.46   True        False         False      11m     
openshift-samples                          4.15.46   True        False         False      5m53s   
operator-lifecycle-manager                 4.15.46   True        False         False      11m     
operator-lifecycle-manager-catalog         4.15.46   True        False         False      11m     
operator-lifecycle-manager-packageserver   4.15.46   True        False         False      11m     
service-ca                                 4.15.46   True        False         False      6m51s   
storage                                    4.15.46   True        False         False      7m14s   
Waiting for cluster to be reported as healthy... Trying again in 60s
healthy
cluster to be reported as healthy finished!
</pre></details>

---
author_association: NONE
user: login: jinqi7
created_at: 2025-03-18T02:24:44Z
body: /retest
author_association: CONTRIBUTOR
user: login: jinqi7
created_at: 2025-03-18T02:25:53Z
body: /retest
author_association: CONTRIBUTOR
user: login: flacatus
created_at: 2025-03-18T18:09:38Z
body: @psturc @davidmogar @johnbieren Can we merge this one?

LGTM
author_association: MEMBER
user: login: openshift-ci[bot]
created_at: 2025-03-19T00:27:48Z
body: New changes are detected. LGTM label has been removed.
author_association: NONE