Skip to content

chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v9.5-1744294473 #1098

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

red-hat-konflux[bot]
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/ubi9/go-toolset stage patch 9.5-1744194661 -> 9.5-1744294473

Configuration

📅 Schedule: Branch creation - "before 5am" (UTC), Automerge - At any time (no schedule defined).

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

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

To execute skipped test pipelines write comment /ok-to-test.

This PR has been generated by MintMaker (powered by Renovate Bot).

… tag to v9.5-1744294473

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
Copy link

openshift-ci bot commented Apr 11, 2025

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a konflux-ci member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@konflux-ci-qe-bot
Copy link

@red-hat-konflux[bot]: The following test has Failed, say /retest to rerun failed tests.

PipelineRun Name Status Rerun command Build Log Test Log
konflux-e2e-vpv7z Failed /retest View Pipeline Log View Test Logs

Inspecting Test Artifacts

To inspect your test artifacts, follow these steps:

  1. Install ORAS (see the ORAS installation guide).
  2. Download artifacts with the following commands:
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/integration-service:konflux-e2e-vpv7z

Test results analysis

🚨 Failed to provision a cluster, see the log for more details:

Click to view logs
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.52).
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.52).
WARN: It is recommended that you update to the latest version.
time=2025-04-11T01:55:08Z 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-a28b7c1fa3'
INFO: To view a list of clusters and their status, run 'rosa list clusters'
INFO: Cluster 'kx-a28b7c1fa3' 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-a28b7c1fa3
Domain Prefix: kx-a28b7c1fa3
Display Name: kx-a28b7c1fa3
ID: 2i32h15268s4q674rngkk3arco7287uk
External ID: 567eb215-9c36-4ad2-83d6-49e98d7c68ca
Control Plane: ROSA Service Hosted
OpenShift Version: 4.15.48
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: MultiAZ

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-001fc23497e4a3aeb, subnet-00ffba09365a434bc, subnet-074cbf0329958194a, subnet-0689cd077699b690a, subnet-0f9f09e46f74cde64, subnet-033f48892ddbaa09d
    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-kms-provider
  • arn:aws:iam::418295695583:role/rosa-hcp-kube-system-kube-controller-manager
  • 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-openshift-image-registry-installer-cloud-credentials
  • 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: Apr 11 2025 01:55:23 UTC
    User Workload Monitoring: Enabled
    Details Page: https://console.redhat.com/openshift/details/s/2vYyuOC9QBFL8U4SWGX6qx5NtOX
    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-a28b7c1fa3'.
INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-a28b7c1fa3 --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.52).
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-a28b7c1fa3' 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-a28b7c1fa3 Version
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 Condition not found in the CVO.
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 The hosted control plane is not found
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 Condition not found in the CVO.
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 The hosted control plane is not found
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 The hosted control plane is not found
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 The hosted control plane is not found
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 The hosted control plane is not found
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 Condition not found in the CVO.
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 Ignition server deployment not found
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 Waiting for hosted control plane to be healthy
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 Condition not found in the CVO.
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 The hosted control plane is not found
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 Condition not found in the CVO.
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 Configuration passes validation
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 HostedCluster is supported by operator configuration
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 failed to get pull secret: Secret "kx-a28b7c1fa3-pull" not found
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 ValidAWSIdentityProvider StatusUnknown
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 Reconciliation active on resource
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 failed to get pull secret: Secret "kx-a28b7c1fa3-pull" not found
2025-04-11 02:00:25 +0000 UTC hostedclusters kx-a28b7c1fa3 The hosted control plane is not found
2025-04-11 02:00:26 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist
2025-04-11 02:00:26 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist
2025-04-11 02:00:26 +0000 UTC certificates cluster-api-cert Issuing certificate as Secret does not exist
2025-04-11 02:00:34 +0000 UTC hostedclusters kx-a28b7c1fa3 Release image is valid
2025-04-11 02:00:36 +0000 UTC hostedclusters kx-a28b7c1fa3 HostedCluster is at expected version
2025-04-11 02:00:38 +0000 UTC hostedclusters kx-a28b7c1fa3 failed to get referenced secret ocm-production-2i32h15268s4q674rngkk3arco7287uk/cluster-api-cert: Secret "cluster-api-cert" not found
2025-04-11 02:00:38 +0000 UTC hostedclusters kx-a28b7c1fa3 Required platform credentials are found
2025-04-11 02:00:38 +0000 UTC hostedclusters kx-a28b7c1fa3 failed to get referenced secret ocm-production-2i32h15268s4q674rngkk3arco7287uk/cluster-api-cert: Secret "cluster-api-cert" not found
2025-04-11 02:01:58 +0000 UTC certificates cluster-api-cert Certificate is up to date and has not expired
2025-04-11 02:02:16 +0000 UTC hostedclusters kx-a28b7c1fa3 OIDC configuration is valid
2025-04-11 02:02:16 +0000 UTC hostedclusters kx-a28b7c1fa3 Reconciliation completed successfully
2025-04-11 02:02:19 +0000 UTC hostedclusters kx-a28b7c1fa3 EtcdAvailable StatefulSetNotFound
2025-04-11 02:02:19 +0000 UTC hostedclusters kx-a28b7c1fa3 router load balancer is not provisioned; 9s since creation.
2025-04-11 02:02:19 +0000 UTC hostedclusters kx-a28b7c1fa3 AWS KMS is not configured
2025-04-11 02:02:19 +0000 UTC hostedclusters kx-a28b7c1fa3 Kube APIServer deployment not found
2025-04-11 02:02:19 +0000 UTC hostedclusters kx-a28b7c1fa3 capi-provider deployment has 1 unavailable replicas
2025-04-11 02:02:19 +0000 UTC hostedclusters kx-a28b7c1fa3 All is well
2025-04-11 02:02:19 +0000 UTC hostedclusters kx-a28b7c1fa3 Configuration passes validation
2025-04-11 02:02:19 +0000 UTC hostedclusters kx-a28b7c1fa3 lookup api.kx-a28b7c1fa3.6urt.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-04-11 02:02:47 +0000 UTC hostedclusters kx-a28b7c1fa3 WebIdentityErr
2025-04-11 02:03:22 +0000 UTC hostedclusters kx-a28b7c1fa3 EtcdAvailable QuorumAvailable
2025-04-11 02:04:25 +0000 UTC hostedclusters kx-a28b7c1fa3 Kube APIServer deployment is available
2025-04-11 02:04:48 +0000 UTC hostedclusters kx-a28b7c1fa3 All is well
2025-04-11 02:05:12 +0000 UTC hostedclusters kx-a28b7c1fa3 All is well
2025-04-11 02:05:27 +0000 UTC hostedclusters kx-a28b7c1fa3 ClusterVersionAvailable FromClusterVersion
2025-04-11 02:05:27 +0000 UTC hostedclusters kx-a28b7c1fa3 ClusterVersionSucceeding FromClusterVersion
2025-04-11 02:05:27 +0000 UTC hostedclusters kx-a28b7c1fa3 Working towards 4.15.48: 518 of 606 done (85% complete)
2025-04-11 02:05:27 +0000 UTC hostedclusters kx-a28b7c1fa3 Payload loaded version="4.15.48" image="quay.io/openshift-release-dev/ocp-release@sha256:8354a185d9bebfcd3d640a57c8c06d8f6135ace8d02070dff02a6f8bd6c7e5fc" architecture="Multi"
2025-04-11 02:05:31 +0000 UTC hostedclusters kx-a28b7c1fa3 The hosted control plane is available
INFO: Cluster 'kx-a28b7c1fa3' 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.52).
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.48 True False False 3m36s
dns 4.15.48 False False True 3m36s DNS "default" is unavailable.
image-registry False True True 2m35s Available: The deployment does not have available replicas...
ingress False True True 2m52s 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.48 True False False 3m25s
kube-controller-manager 4.15.48 True False False 3m25s
kube-scheduler 4.15.48 True False False 3m25s
kube-storage-version-migrator
monitoring
network 4.15.48 True True False 3m10s Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning False True False 3m9s DaemonSet "tuned" has no available Pod(s)
openshift-apiserver 4.15.48 True False False 3m25s
openshift-controller-manager 4.15.48 True False False 3m25s
openshift-samples
operator-lifecycle-manager 4.15.48 True False False 3m27s
operator-lifecycle-manager-catalog 4.15.48 True False False 3m22s
operator-lifecycle-manager-packageserver 4.15.48 True False False 3m25s
service-ca
storage 4.15.48 False False False 3m24s 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.48 True False False 3m37s
dns 4.15.48 False False True 3m37s DNS "default" is unavailable.
image-registry False True True 2m36s Available: The deployment does not have available replicas...
ingress False True True 2m53s 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.48 True False False 3m26s
kube-controller-manager 4.15.48 True False False 3m26s
kube-scheduler 4.15.48 True False False 3m26s
kube-storage-version-migrator
monitoring
network 4.15.48 True True False 3m11s Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning False True False 3m10s DaemonSet "tuned" has no available Pod(s)
openshift-apiserver 4.15.48 True False False 3m26s
openshift-controller-manager 4.15.48 True False False 3m26s
openshift-samples
operator-lifecycle-manager 4.15.48 True False False 3m28s
operator-lifecycle-manager-catalog 4.15.48 True False False 3m23s
operator-lifecycle-manager-packageserver 4.15.48 True False False 3m26s
service-ca
storage 4.15.48 False False False 3m25s 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.48 True False False 4m37s
dns 4.15.48 False False True 4m37s DNS "default" is unavailable.
image-registry False True True 3m36s Available: The deployment does not have available replicas...
ingress False True True 3m53s 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.48 True False False 4m26s
kube-controller-manager 4.15.48 True False False 4m26s
kube-scheduler 4.15.48 True False False 4m26s
kube-storage-version-migrator
monitoring
network 4.15.48 True True False 4m11s Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning False True False 4m10s DaemonSet "tuned" has no available Pod(s)
openshift-apiserver 4.15.48 True False False 4m26s
openshift-controller-manager 4.15.48 True False False 4m26s
openshift-samples
operator-lifecycle-manager 4.15.48 True False False 4m28s
operator-lifecycle-manager-catalog 4.15.48 True False False 4m23s
operator-lifecycle-manager-packageserver 4.15.48 True False False 4m26s
service-ca
storage 4.15.48 False False False 4m25s 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.48 True False False 5m37s
dns 4.15.48 False False True 5m37s DNS "default" is unavailable.
image-registry False True True 4m36s Available: The deployment does not have available replicas...
ingress False True True 4m53s 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.48 True False False 5m26s
kube-controller-manager 4.15.48 True False False 5m26s
kube-scheduler 4.15.48 True False False 5m26s
kube-storage-version-migrator
monitoring
network 4.15.48 True True False 5m11s Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning False True False 5m10s DaemonSet "tuned" has no available Pod(s)
openshift-apiserver 4.15.48 True False False 5m26s
openshift-controller-manager 4.15.48 True False False 5m26s
openshift-samples
operator-lifecycle-manager 4.15.48 True False False 5m28s
operator-lifecycle-manager-catalog 4.15.48 True False False 5m23s
operator-lifecycle-manager-packageserver 4.15.48 True False False 5m26s
service-ca
storage 4.15.48 False False False 5m25s 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.48 True False False 6m38s
dns 4.15.48 False False True 6m38s DNS "default" is unavailable.
image-registry False True True 5m37s Available: The deployment does not have available replicas...
ingress False True True 5m54s 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.48 True False False 6m27s
kube-controller-manager 4.15.48 True False False 6m27s
kube-scheduler 4.15.48 True False False 6m27s
kube-storage-version-migrator
monitoring
network 4.15.48 True True False 6m12s Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning False True False 6m11s DaemonSet "tuned" has no available Pod(s)
openshift-apiserver 4.15.48 True False False 6m27s
openshift-controller-manager 4.15.48 True False False 6m27s
openshift-samples
operator-lifecycle-manager 4.15.48 True False False 6m29s
operator-lifecycle-manager-catalog 4.15.48 True False False 6m24s
operator-lifecycle-manager-packageserver 4.15.48 True False False 6m27s
service-ca
storage 4.15.48 False False False 6m26s 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.48 True False False 7m38s
dns 4.15.48 False False True 7m38s DNS "default" is unavailable.
image-registry False True True 6m37s Available: The deployment does not have available replicas...
ingress False True True 6m54s 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.48 True False False 7m27s
kube-controller-manager 4.15.48 True False False 7m27s
kube-scheduler 4.15.48 True False False 7m27s
kube-storage-version-migrator
monitoring
network 4.15.48 True True False 7m12s DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)...
node-tuning 4.15.48 True True False 25s Waiting for 1/1 Profiles to be applied
openshift-apiserver 4.15.48 True False False 7m27s
openshift-controller-manager 4.15.48 True False False 7m27s
openshift-samples
operator-lifecycle-manager 4.15.48 True False False 7m29s
operator-lifecycle-manager-catalog 4.15.48 True False False 7m24s
operator-lifecycle-manager-packageserver 4.15.48 True False False 7m27s
service-ca
storage 4.15.48 True False False 3s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.48 True True False 2s SyncLoopRefreshProgressing: Working toward version 4.15.48, 1 replicas available
csi-snapshot-controller 4.15.48 True False False 8m38s
dns 4.15.48 True True False 5s DNS "default" reports Progressing=True: "Have 2 available node-resolver pods, want 3."
image-registry False True True 7m37s Available: The deployment does not have available replicas...
ingress False True True 7m54s 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.48 True False False 38s
kube-apiserver 4.15.48 True False False 8m27s
kube-controller-manager 4.15.48 True False False 8m27s
kube-scheduler 4.15.48 True False False 8m27s
kube-storage-version-migrator 4.15.48 True False False 26s
monitoring Unknown True Unknown 12s Rolling out the stack.
network 4.15.48 True True False 8m12s DaemonSet "/openshift-multus/multus" is not available (awaiting 2 nodes)...
node-tuning 4.15.48 True True False 14s Waiting for 2/3 Profiles to be applied
openshift-apiserver 4.15.48 True False False 8m27s
openshift-controller-manager 4.15.48 True False False 8m27s
openshift-samples False False False 3s SampleUpsertsPending
operator-lifecycle-manager 4.15.48 True False False 8m29s
operator-lifecycle-manager-catalog 4.15.48 True False False 8m24s
operator-lifecycle-manager-packageserver 4.15.48 True False False 8m27s
service-ca 4.15.48 True False False 37s
storage 4.15.48 True True False 63s 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.48 True True False 63s SyncLoopRefreshProgressing: Working toward version 4.15.48, 1 replicas available
csi-snapshot-controller 4.15.48 True False False 9m39s
dns 4.15.48 True True False 66s DNS "default" reports Progressing=True: "Have 2 available DNS pods, want 3."
image-registry 4.15.48 True False False 36s
ingress 4.15.48 True False False 37s
insights 4.15.48 True False False 99s
kube-apiserver 4.15.48 True False False 9m28s
kube-controller-manager 4.15.48 True False False 9m28s
kube-scheduler 4.15.48 True False False 9m28s
kube-storage-version-migrator 4.15.48 True False False 87s
monitoring Unknown True Unknown 73s Rolling out the stack.
network 4.15.48 True True False 9m13s DaemonSet "/openshift-network-diagnostics/network-check-target" is not available (awaiting 2 nodes)
node-tuning 4.15.48 True False False 75s
openshift-apiserver 4.15.48 True False False 9m28s
openshift-controller-manager 4.15.48 True False False 9m28s
openshift-samples 4.15.48 True False False 54s
operator-lifecycle-manager 4.15.48 True False False 9m30s
operator-lifecycle-manager-catalog 4.15.48 True False False 9m25s
operator-lifecycle-manager-packageserver 4.15.48 True False False 9m28s
service-ca 4.15.48 True False False 98s
storage 4.15.48 True False False 2m4s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.48 True False False 2m3s
csi-snapshot-controller 4.15.48 True False False 10m
dns 4.15.48 True False False 2m6s
image-registry 4.15.48 True False False 96s
ingress 4.15.48 True False False 97s
insights 4.15.48 True False False 2m39s
kube-apiserver 4.15.48 True False False 10m
kube-controller-manager 4.15.48 True False False 10m
kube-scheduler 4.15.48 True False False 10m
kube-storage-version-migrator 4.15.48 True False False 2m27s
monitoring Unknown True Unknown 2m13s Rolling out the stack.
network 4.15.48 True False False 10m
node-tuning 4.15.48 True False False 2m15s
openshift-apiserver 4.15.48 True False False 10m
openshift-controller-manager 4.15.48 True False False 10m
openshift-samples 4.15.48 True False False 114s
operator-lifecycle-manager 4.15.48 True False False 10m
operator-lifecycle-manager-catalog 4.15.48 True False False 10m
operator-lifecycle-manager-packageserver 4.15.48 True False False 10m
service-ca 4.15.48 True False False 2m38s
storage 4.15.48 True False False 3m4s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.48 True False False 3m3s
csi-snapshot-controller 4.15.48 True False False 11m
dns 4.15.48 True False False 3m6s
image-registry 4.15.48 True False False 2m36s
ingress 4.15.48 True False False 2m37s
insights 4.15.48 True False False 3m39s
kube-apiserver 4.15.48 True False False 11m
kube-controller-manager 4.15.48 True False False 11m
kube-scheduler 4.15.48 True False False 11m
kube-storage-version-migrator 4.15.48 True False False 3m27s
monitoring Unknown True Unknown 3m13s Rolling out the stack.
network 4.15.48 True False False 11m
node-tuning 4.15.48 True False False 3m15s
openshift-apiserver 4.15.48 True False False 11m
openshift-controller-manager 4.15.48 True False False 11m
openshift-samples 4.15.48 True False False 2m54s
operator-lifecycle-manager 4.15.48 True False False 11m
operator-lifecycle-manager-catalog 4.15.48 True False False 11m
operator-lifecycle-manager-packageserver 4.15.48 True False False 11m
service-ca 4.15.48 True False False 3m38s
storage 4.15.48 True False False 4m4s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.48 True False False 4m4s
csi-snapshot-controller 4.15.48 True False False 12m
dns 4.15.48 True False False 4m7s
image-registry 4.15.48 True False False 3m37s
ingress 4.15.48 True False False 3m38s
insights 4.15.48 True False False 4m40s
kube-apiserver 4.15.48 True False False 12m
kube-controller-manager 4.15.48 True False False 12m
kube-scheduler 4.15.48 True False False 12m
kube-storage-version-migrator 4.15.48 True False False 4m28s
monitoring 4.15.48 True False False 61s
network 4.15.48 True False False 12m
node-tuning 4.15.48 True False False 4m16s
openshift-apiserver 4.15.48 True False False 12m
openshift-controller-manager 4.15.48 True False False 12m
openshift-samples 4.15.48 True False False 3m55s
operator-lifecycle-manager 4.15.48 True False False 12m
operator-lifecycle-manager-catalog 4.15.48 True False False 12m
operator-lifecycle-manager-packageserver 4.15.48 True False False 12m
service-ca 4.15.48 True False False 4m39s
storage 4.15.48 True False False 5m5s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.48 True False False 5m4s
csi-snapshot-controller 4.15.48 True False False 13m
dns 4.15.48 True False False 5m7s
image-registry 4.15.48 True False False 4m37s
ingress 4.15.48 True False False 4m38s
insights 4.15.48 True False False 5m40s
kube-apiserver 4.15.48 True False False 13m
kube-controller-manager 4.15.48 True False False 13m
kube-scheduler 4.15.48 True False False 13m
kube-storage-version-migrator 4.15.48 True False False 5m28s
monitoring 4.15.48 True False False 2m1s
network 4.15.48 True False False 13m
node-tuning 4.15.48 True False False 5m16s
openshift-apiserver 4.15.48 True False False 13m
openshift-controller-manager 4.15.48 True False False 13m
openshift-samples 4.15.48 True False False 4m55s
operator-lifecycle-manager 4.15.48 True False False 13m
operator-lifecycle-manager-catalog 4.15.48 True False False 13m
operator-lifecycle-manager-packageserver 4.15.48 True False False 13m
service-ca 4.15.48 True False False 5m39s
storage 4.15.48 True False False 6m5s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.48 True False False 6m4s
csi-snapshot-controller 4.15.48 True False False 14m
dns 4.15.48 True False False 6m7s
image-registry 4.15.48 True False False 5m37s
ingress 4.15.48 True False False 5m38s
insights 4.15.48 True False False 6m40s
kube-apiserver 4.15.48 True False False 14m
kube-controller-manager 4.15.48 True False False 14m
kube-scheduler 4.15.48 True False False 14m
kube-storage-version-migrator 4.15.48 True False False 6m28s
monitoring 4.15.48 True False False 3m1s
network 4.15.48 True False False 14m
node-tuning 4.15.48 True False False 6m16s
openshift-apiserver 4.15.48 True False False 14m
openshift-controller-manager 4.15.48 True False False 14m
openshift-samples 4.15.48 True False False 5m55s
operator-lifecycle-manager 4.15.48 True False False 14m
operator-lifecycle-manager-catalog 4.15.48 True False False 14m
operator-lifecycle-manager-packageserver 4.15.48 True False False 14m
service-ca 4.15.48 True False False 6m39s
storage 4.15.48 True False False 7m5s
Waiting for cluster to be reported as healthy... Trying again in 60s
healthy
cluster to be reported as healthy finished!


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

Successfully merging this pull request may close these issues.

1 participant