Skip to content
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

fix(deps): update module github.com/bradleyfalzon/ghinstallation/v2 to v2.14.0 #416

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
github.com/bradleyfalzon/ghinstallation/v2 require minor v2.11.0 -> v2.14.0

Release Notes

bradleyfalzon/ghinstallation (github.com/bradleyfalzon/ghinstallation/v2)

v2.14.0

Compare Source

What's Changed

Full Changelog: bradleyfalzon/ghinstallation@v2.13.0...v2.14.0

v2.13.0

Compare Source

What's Changed

New Contributors

Full Changelog: bradleyfalzon/ghinstallation@v2.12.0...v2.13.0

v2.12.0

Compare Source

What's Changed

New Contributors

Full Changelog: bradleyfalzon/ghinstallation@v2.11.0...v2.12.0


Configuration

📅 Schedule: Branch creation - "after 5am on sunday" (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).

…o v2.14.0

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

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 1 additional dependency was updated

Details:

Package Change
github.com/golang-jwt/jwt/v4 v4.5.0 -> v4.5.1

@red-hat-konflux red-hat-konflux bot requested a review from a team as a code owner March 2, 2025 17:56
@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-build-service-k4h9v 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/build-service:konflux-e2e-build-service-k4h9v

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...
INFO: Logged in as 'konflux-ci-418295695583' on 'https://api.openshift.com'
INFO: Create ROSA with HCP cluster...
time=2025-03-02T18:04:22Z 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-cd2672e907'
INFO: To view a list of clusters and their status, run 'rosa list clusters'
INFO: Cluster 'kx-cd2672e907' 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-cd2672e907
Domain Prefix: kx-cd2672e907
Display Name: kx-cd2672e907
ID: 2h94vauc64lhlelbt51umqq2sik123l7
External ID: 2c9d4fde-f167-4aef-8fe5-e4eaa5faebd9
Control Plane: ROSA Service Hosted
OpenShift Version: 4.15.45
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 2 2025 18:04:32 UTC
    User Workload Monitoring: Enabled
    Details Page: https://console.redhat.com/openshift/details/s/2tltpbVvRTbqRutzQsC4MaIVAxm
    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-cd2672e907'.
INFO: To watch your cluster installation logs, run 'rosa logs install -c kx-cd2672e907 --watch'.
INFO: Track the progress of the cluster creation...
�[0;33mW:�[m Region flag will be removed from this command in future versions
INFO: Cluster 'kx-cd2672e907' 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-cd2672e907 Version
2025-03-02 18:09:48 +0000 UTC hostedclusters kx-cd2672e907 ValidAWSIdentityProvider StatusUnknown
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 The hosted control plane is not found
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 The hosted control plane is not found
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 The hosted control plane is not found
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 The hosted control plane is not found
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 The hosted control plane is not found
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Waiting for hosted control plane to be healthy
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 The hosted control plane is not found
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Ignition server deployment not found
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Configuration passes validation
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 HostedCluster is supported by operator configuration
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Release image is valid
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 The hosted control plane is not found
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Reconciliation active on resource
2025-03-02 18:09:51 +0000 UTC hostedclusters kx-cd2672e907 HostedCluster is at expected version
2025-03-02 18:09:52 +0000 UTC hostedclusters kx-cd2672e907 Required platform credentials are found
2025-03-02 18:09:52 +0000 UTC hostedclusters kx-cd2672e907 failed to get referenced secret ocm-production-2h94vauc64lhlelbt51umqq2sik123l7/cluster-api-cert: Secret "cluster-api-cert" not found
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-cd2672e907 Version
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Release image is valid
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Ignition server deployment not found
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 router load balancer is not provisioned; 0s since creation.; private-router load balancer is not provisioned; 0s since creation.; router load balancer is not provisioned; 0s since creation.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 HostedCluster is supported by operator configuration
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Reconciliation active on resource
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Configuration passes validation
2025-03-02 18:09:51 +0000 UTC hostedclusters kx-cd2672e907 HostedCluster is at expected version
2025-03-02 18:09:52 +0000 UTC hostedclusters kx-cd2672e907 Required platform credentials are found
2025-03-02 18:11:26 +0000 UTC hostedclusters kx-cd2672e907 OIDC configuration is valid
2025-03-02 18:11:26 +0000 UTC hostedclusters kx-cd2672e907 Reconciliation completed successfully
2025-03-02 18:11:27 +0000 UTC hostedclusters kx-cd2672e907 WebIdentityErr
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 All is well
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 lookup api.kx-cd2672e907.2y7t.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 capi-provider deployment has 1 unavailable replicas
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 Configuration passes validation
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 AWS KMS is not configured
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 EtcdAvailable StatefulSetNotFound
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 Kube APIServer deployment not found
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 router load balancer is not provisioned; 0s since creation.; private-router load balancer is not provisioned; 0s since creation.; router load balancer is not provisioned; 0s since creation.
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-cd2672e907 Version
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Release image is valid
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Ignition server deployment not found
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Waiting for hosted control plane kubeconfig to be created
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 HostedCluster is supported by operator configuration
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Condition not found in the CVO.
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Reconciliation active on resource
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Configuration passes validation
2025-03-02 18:09:51 +0000 UTC hostedclusters kx-cd2672e907 HostedCluster is at expected version
2025-03-02 18:09:52 +0000 UTC hostedclusters kx-cd2672e907 Required platform credentials are found
2025-03-02 18:11:26 +0000 UTC hostedclusters kx-cd2672e907 OIDC configuration is valid
2025-03-02 18:11:26 +0000 UTC hostedclusters kx-cd2672e907 Reconciliation completed successfully
2025-03-02 18:11:27 +0000 UTC hostedclusters kx-cd2672e907 WebIdentityErr
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 All is well
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 lookup api.kx-cd2672e907.2y7t.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 capi-provider deployment has 1 unavailable replicas
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 Configuration passes validation
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 AWS KMS is not configured
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 EtcdAvailable StatefulSetNotFound
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 Kube APIServer deployment not found
2025-03-02 18:11:36 +0000 UTC hostedclusters kx-cd2672e907 All is well
2025-03-02 18:12:20 +0000 UTC hostedclusters kx-cd2672e907 EtcdAvailable QuorumAvailable
2025-03-02 18:13:32 +0000 UTC hostedclusters kx-cd2672e907 Kube APIServer deployment is available
2025-03-02 18:13:38 +0000 UTC hostedclusters kx-cd2672e907 All is well
2025-03-02 18:13:53 +0000 UTC hostedclusters kx-cd2672e907 The hosted cluster is not degraded
0001-01-01 00:00:00 +0000 UTC hostedclusters kx-cd2672e907 Version
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Ignition server deployment is not yet available
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Reconciliation active on resource
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Get "https://abadcc772cef841669fcdc540b04e4a8-673be6ed8f214253.elb.us-east-1.amazonaws.com:443/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Release image is valid
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 HostedCluster is supported by operator configuration
2025-03-02 18:09:49 +0000 UTC hostedclusters kx-cd2672e907 Configuration passes validation
2025-03-02 18:09:51 +0000 UTC hostedclusters kx-cd2672e907 HostedCluster is at expected version
2025-03-02 18:09:52 +0000 UTC hostedclusters kx-cd2672e907 Required platform credentials are found
2025-03-02 18:11:26 +0000 UTC hostedclusters kx-cd2672e907 Reconciliation completed successfully
2025-03-02 18:11:26 +0000 UTC hostedclusters kx-cd2672e907 OIDC configuration is valid
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 Configuration passes validation
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 AWS KMS is not configured
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 All is well
2025-03-02 18:11:28 +0000 UTC hostedclusters kx-cd2672e907 lookup api.kx-cd2672e907.2y7t.p3.openshiftapps.com on 172.30.0.10:53: no such host
2025-03-02 18:11:36 +0000 UTC hostedclusters kx-cd2672e907 All is well
2025-03-02 18:12:20 +0000 UTC hostedclusters kx-cd2672e907 EtcdAvailable QuorumAvailable
2025-03-02 18:13:32 +0000 UTC hostedclusters kx-cd2672e907 Kube APIServer deployment is available
2025-03-02 18:13:38 +0000 UTC hostedclusters kx-cd2672e907 All is well
2025-03-02 18:13:59 +0000 UTC hostedclusters kx-cd2672e907 All is well
2025-03-02 18:13:59 +0000 UTC hostedclusters kx-cd2672e907 [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]
2025-03-02 18:14:11 +0000 UTC hostedclusters kx-cd2672e907 ClusterVersionSucceeding FromClusterVersion
2025-03-02 18:14:11 +0000 UTC hostedclusters kx-cd2672e907 ClusterVersionAvailable FromClusterVersion
2025-03-02 18:14:11 +0000 UTC hostedclusters kx-cd2672e907 Working towards 4.15.45: 284 of 606 done (46% complete)
2025-03-02 18:14:11 +0000 UTC hostedclusters kx-cd2672e907 Payload loaded version="4.15.45" image="quay.io/openshift-release-dev/ocp-release@sha256:e645f0b6c90d201d79aa4b768f3a36dc38457329b858ca7054de721cb357ea0b" architecture="Multi"
2025-03-02 18:14:18 +0000 UTC hostedclusters kx-cd2672e907 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-02 18:14:25 +0000 UTC hostedclusters kx-cd2672e907 The hosted control plane is available
INFO: Cluster 'kx-cd2672e907' is now ready
INFO: ROSA with HCP cluster is ready, create a cluster admin account for accessing the cluster
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.45 True False False 3m24s
dns 4.15.45 False False True 3m27s DNS "default" is unavailable.
image-registry False True True 2m43s Available: The deployment does not have available replicas...
ingress False True True 2m59s 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.45 True False False 3m17s
kube-controller-manager 4.15.45 True False False 3m17s
kube-scheduler 4.15.45 True False False 3m17s
kube-storage-version-migrator
monitoring
network 4.15.45 True True False 3m2s Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning False True False 3m13s DaemonSet "tuned" has no available Pod(s)
openshift-apiserver 4.15.45 True False False 3m17s
openshift-controller-manager 4.15.45 True False False 3m17s
openshift-samples
operator-lifecycle-manager 4.15.45 True False False 3m19s
operator-lifecycle-manager-catalog 4.15.45 True False False 3m20s
operator-lifecycle-manager-packageserver 4.15.45 True False False 3m17s
service-ca
storage 4.15.45 False False False 3m16s 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.45 True False False 3m25s
dns 4.15.45 False False True 3m28s DNS "default" is unavailable.
image-registry False True True 2m44s Available: The deployment does not have available replicas...
ingress False True True 3m 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.45 True False False 3m18s
kube-controller-manager 4.15.45 True False False 3m18s
kube-scheduler 4.15.45 True False False 3m18s
kube-storage-version-migrator
monitoring
network 4.15.45 True True False 3m3s Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning False True False 3m14s DaemonSet "tuned" has no available Pod(s)
openshift-apiserver 4.15.45 True False False 3m18s
openshift-controller-manager 4.15.45 True False False 3m18s
openshift-samples
operator-lifecycle-manager 4.15.45 True False False 3m20s
operator-lifecycle-manager-catalog 4.15.45 True False False 3m21s
operator-lifecycle-manager-packageserver 4.15.45 True False False 3m18s
service-ca
storage 4.15.45 False False False 3m17s 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.45 True False False 4m25s
dns 4.15.45 False False True 4m28s DNS "default" is unavailable.
image-registry False True True 3m44s Available: The deployment does not have available replicas...
ingress False True True 4m 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.45 True False False 4m18s
kube-controller-manager 4.15.45 True False False 4m18s
kube-scheduler 4.15.45 True False False 4m18s
kube-storage-version-migrator
monitoring
network 4.15.45 True True False 4m3s Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning False True False 4m14s DaemonSet "tuned" has no available Pod(s)
openshift-apiserver 4.15.45 True False False 4m18s
openshift-controller-manager 4.15.45 True False False 4m18s
openshift-samples
operator-lifecycle-manager 4.15.45 True False False 4m20s
operator-lifecycle-manager-catalog 4.15.45 True False False 4m21s
operator-lifecycle-manager-packageserver 4.15.45 True False False 4m18s
service-ca
storage 4.15.45 False False False 4m17s 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.45 True False False 5m25s
dns 4.15.45 False False True 5m28s DNS "default" is unavailable.
image-registry False True True 4m44s Available: The deployment does not have available replicas...
ingress False True True 5m 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.45 True False False 5m18s
kube-controller-manager 4.15.45 True False False 5m18s
kube-scheduler 4.15.45 True False False 5m18s
kube-storage-version-migrator
monitoring
network 4.15.45 True True False 5m3s Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
node-tuning False True False 5m14s DaemonSet "tuned" has no available Pod(s)
openshift-apiserver 4.15.45 True False False 5m18s
openshift-controller-manager 4.15.45 True False False 5m18s
openshift-samples
operator-lifecycle-manager 4.15.45 True False False 5m20s
operator-lifecycle-manager-catalog 4.15.45 True False False 5m21s
operator-lifecycle-manager-packageserver 4.15.45 True False False 5m18s
service-ca
storage 4.15.45 False False False 5m17s 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.45 True False False 6m26s
dns 4.15.45 False False True 6m29s DNS "default" is unavailable.
image-registry False True True 5m45s Available: The deployment does not have available replicas...
ingress False True True 6m1s 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.45 True False False 6m19s
kube-controller-manager 4.15.45 True False False 6m19s
kube-scheduler 4.15.45 True False False 6m19s
kube-storage-version-migrator
monitoring
network 4.15.45 True True False 6m4s DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)...
node-tuning 4.15.45 True True False 7s Waiting for 1/1 Profiles to be applied
openshift-apiserver 4.15.45 True False False 6m19s
openshift-controller-manager 4.15.45 True False False 6m19s
openshift-samples
operator-lifecycle-manager 4.15.45 True False False 6m21s
operator-lifecycle-manager-catalog 4.15.45 True False False 6m22s
operator-lifecycle-manager-packageserver 4.15.45 True False False 6m19s
service-ca
storage 4.15.45 True False False 4s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 False True False 15s DeploymentAvailable: 0 replicas available for console deployment
csi-snapshot-controller 4.15.45 True False False 7m26s
dns 4.15.45 True False False 7s
image-registry False True True 6m45s Available: The deployment does not have available replicas...
ingress False True True 7m1s 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.45 True False False 51s
kube-apiserver 4.15.45 True False False 7m19s
kube-controller-manager 4.15.45 True False False 7m19s
kube-scheduler 4.15.45 True False False 7m19s
kube-storage-version-migrator 4.15.45 True False False 47s
monitoring Unknown True Unknown 21s Rolling out the stack.
network 4.15.45 True False False 7m4s
node-tuning 4.15.45 True False False 67s
openshift-apiserver 4.15.45 True False False 7m19s
openshift-controller-manager 4.15.45 True False False 7m19s
openshift-samples 4.15.45 True False False 3s
operator-lifecycle-manager 4.15.45 True False False 7m21s
operator-lifecycle-manager-catalog 4.15.45 True False False 7m22s
operator-lifecycle-manager-packageserver 4.15.45 True False False 7m19s
service-ca 4.15.45 True False False 48s
storage 4.15.45 True False False 64s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 48s
csi-snapshot-controller 4.15.45 True False False 8m26s
dns 4.15.45 True False False 67s
image-registry True True False 48s Progressing: The deployment has not completed...
ingress 4.15.45 True True True 48s 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.45 True False False 111s
kube-apiserver 4.15.45 True False False 8m19s
kube-controller-manager 4.15.45 True False False 8m19s
kube-scheduler 4.15.45 True False False 8m19s
kube-storage-version-migrator 4.15.45 True False False 107s
monitoring Unknown True Unknown 81s Rolling out the stack.
network 4.15.45 True False False 8m4s
node-tuning 4.15.45 True False False 2m7s
openshift-apiserver 4.15.45 True False False 8m19s
openshift-controller-manager 4.15.45 True False False 8m19s
openshift-samples 4.15.45 True False False 63s
operator-lifecycle-manager 4.15.45 True False False 8m21s
operator-lifecycle-manager-catalog 4.15.45 True False False 8m22s
operator-lifecycle-manager-packageserver 4.15.45 True False False 8m19s
service-ca 4.15.45 True False False 108s
storage 4.15.45 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.45 True False False 108s
csi-snapshot-controller 4.15.45 True False False 9m26s
dns 4.15.45 True False False 2m7s
image-registry True True True 108s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 108s 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.45 True False False 2m51s
kube-apiserver 4.15.45 True False False 9m19s
kube-controller-manager 4.15.45 True False False 9m19s
kube-scheduler 4.15.45 True False False 9m19s
kube-storage-version-migrator 4.15.45 True False False 2m47s
monitoring Unknown True Unknown 2m21s Rolling out the stack.
network 4.15.45 True False False 9m4s
node-tuning 4.15.45 True False False 3m7s
openshift-apiserver 4.15.45 True False False 9m19s
openshift-controller-manager 4.15.45 True False False 9m19s
openshift-samples 4.15.45 True False False 2m3s
operator-lifecycle-manager 4.15.45 True False False 9m21s
operator-lifecycle-manager-catalog 4.15.45 True False False 9m22s
operator-lifecycle-manager-packageserver 4.15.45 True False False 9m19s
service-ca 4.15.45 True False False 2m48s
storage 4.15.45 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.45 True False False 2m49s
csi-snapshot-controller 4.15.45 True False False 10m
dns 4.15.45 True False False 3m8s
image-registry True True True 2m49s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 2m49s 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.45 True False False 3m52s
kube-apiserver 4.15.45 True False False 10m
kube-controller-manager 4.15.45 True False False 10m
kube-scheduler 4.15.45 True False False 10m
kube-storage-version-migrator 4.15.45 True False False 3m48s
monitoring Unknown True Unknown 3m22s Rolling out the stack.
network 4.15.45 True False False 10m
node-tuning 4.15.45 True False False 4m8s
openshift-apiserver 4.15.45 True False False 10m
openshift-controller-manager 4.15.45 True False False 10m
openshift-samples 4.15.45 True False False 3m4s
operator-lifecycle-manager 4.15.45 True False False 10m
operator-lifecycle-manager-catalog 4.15.45 True False False 10m
operator-lifecycle-manager-packageserver 4.15.45 True False False 10m
service-ca 4.15.45 True False False 3m49s
storage 4.15.45 True False False 4m5s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 3m49s
csi-snapshot-controller 4.15.45 True False False 11m
dns 4.15.45 True False False 4m8s
image-registry True True True 3m49s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 3m49s 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.45 True False False 4m52s
kube-apiserver 4.15.45 True False False 11m
kube-controller-manager 4.15.45 True False False 11m
kube-scheduler 4.15.45 True False False 11m
kube-storage-version-migrator 4.15.45 True False False 4m48s
monitoring Unknown True Unknown 4m22s Rolling out the stack.
network 4.15.45 True False False 11m
node-tuning 4.15.45 True False False 5m8s
openshift-apiserver 4.15.45 True False False 11m
openshift-controller-manager 4.15.45 True False False 11m
openshift-samples 4.15.45 True False False 4m4s
operator-lifecycle-manager 4.15.45 True False False 11m
operator-lifecycle-manager-catalog 4.15.45 True False False 11m
operator-lifecycle-manager-packageserver 4.15.45 True False False 11m
service-ca 4.15.45 True False False 4m49s
storage 4.15.45 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.45 True False False 4m49s
csi-snapshot-controller 4.15.45 True False False 12m
dns 4.15.45 True False False 5m8s
image-registry True True True 4m49s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 4m49s 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.45 True False False 5m52s
kube-apiserver 4.15.45 True False False 12m
kube-controller-manager 4.15.45 True False False 12m
kube-scheduler 4.15.45 True False False 12m
kube-storage-version-migrator 4.15.45 True False False 5m48s
monitoring Unknown True Unknown 5m22s Rolling out the stack.
network 4.15.45 True False False 12m
node-tuning 4.15.45 True False False 6m8s
openshift-apiserver 4.15.45 True False False 12m
openshift-controller-manager 4.15.45 True False False 12m
openshift-samples 4.15.45 True False False 5m4s
operator-lifecycle-manager 4.15.45 True False False 12m
operator-lifecycle-manager-catalog 4.15.45 True False False 12m
operator-lifecycle-manager-packageserver 4.15.45 True False False 12m
service-ca 4.15.45 True False False 5m49s
storage 4.15.45 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.45 True False False 5m49s
csi-snapshot-controller 4.15.45 True False False 13m
dns 4.15.45 True False False 6m8s
image-registry True True True 5m49s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 5m49s 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.45 True False False 6m52s
kube-apiserver 4.15.45 True False False 13m
kube-controller-manager 4.15.45 True False False 13m
kube-scheduler 4.15.45 True False False 13m
kube-storage-version-migrator 4.15.45 True False False 6m48s
monitoring Unknown True Unknown 6m22s Rolling out the stack.
network 4.15.45 True False False 13m
node-tuning 4.15.45 True False False 7m8s
openshift-apiserver 4.15.45 True False False 13m
openshift-controller-manager 4.15.45 True False False 13m
openshift-samples 4.15.45 True False False 6m4s
operator-lifecycle-manager 4.15.45 True False False 13m
operator-lifecycle-manager-catalog 4.15.45 True False False 13m
operator-lifecycle-manager-packageserver 4.15.45 True False False 13m
service-ca 4.15.45 True False False 6m49s
storage 4.15.45 True False False 7m5s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 6m50s
csi-snapshot-controller 4.15.45 True False False 14m
dns 4.15.45 True False False 7m9s
image-registry True True True 6m50s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 6m50s 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.45 True False False 7m53s
kube-apiserver 4.15.45 True False False 14m
kube-controller-manager 4.15.45 True False False 14m
kube-scheduler 4.15.45 True False False 14m
kube-storage-version-migrator 4.15.45 True False False 7m49s
monitoring Unknown True Unknown 7m23s Rolling out the stack.
network 4.15.45 True False False 14m
node-tuning 4.15.45 True False False 8m9s
openshift-apiserver 4.15.45 True False False 14m
openshift-controller-manager 4.15.45 True False False 14m
openshift-samples 4.15.45 True False False 7m5s
operator-lifecycle-manager 4.15.45 True False False 14m
operator-lifecycle-manager-catalog 4.15.45 True False False 14m
operator-lifecycle-manager-packageserver 4.15.45 True False False 14m
service-ca 4.15.45 True False False 7m50s
storage 4.15.45 True False False 8m6s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 7m50s
csi-snapshot-controller 4.15.45 True False False 15m
dns 4.15.45 True False False 8m9s
image-registry True True True 7m50s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 7m50s 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.45 True False False 8m53s
kube-apiserver 4.15.45 True False False 15m
kube-controller-manager 4.15.45 True False False 15m
kube-scheduler 4.15.45 True False False 15m
kube-storage-version-migrator 4.15.45 True False False 8m49s
monitoring Unknown True Unknown 8m23s Rolling out the stack.
network 4.15.45 True False False 15m
node-tuning 4.15.45 True False False 9m9s
openshift-apiserver 4.15.45 True False False 15m
openshift-controller-manager 4.15.45 True False False 15m
openshift-samples 4.15.45 True False False 8m5s
operator-lifecycle-manager 4.15.45 True False False 15m
operator-lifecycle-manager-catalog 4.15.45 True False False 15m
operator-lifecycle-manager-packageserver 4.15.45 True False False 15m
service-ca 4.15.45 True False False 8m50s
storage 4.15.45 True False False 9m6s
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 8m50s
csi-snapshot-controller 4.15.45 True False False 16m
dns 4.15.45 True False False 9m9s
image-registry True True True 8m50s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 8m50s 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.45 True False False 9m53s
kube-apiserver 4.15.45 True False False 16m
kube-controller-manager 4.15.45 True False False 16m
kube-scheduler 4.15.45 True False False 16m
kube-storage-version-migrator 4.15.45 True False False 9m49s
monitoring Unknown True Unknown 9m23s Rolling out the stack.
network 4.15.45 True False False 16m
node-tuning 4.15.45 True False False 10m
openshift-apiserver 4.15.45 True False False 16m
openshift-controller-manager 4.15.45 True False False 16m
openshift-samples 4.15.45 True False False 9m5s
operator-lifecycle-manager 4.15.45 True False False 16m
operator-lifecycle-manager-catalog 4.15.45 True False False 16m
operator-lifecycle-manager-packageserver 4.15.45 True False False 16m
service-ca 4.15.45 True False False 9m50s
storage 4.15.45 True False False 10m
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 9m51s
csi-snapshot-controller 4.15.45 True False False 17m
dns 4.15.45 True False False 10m
image-registry True True True 9m51s Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 9m51s 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.45 True False False 10m
kube-apiserver 4.15.45 True False False 17m
kube-controller-manager 4.15.45 True False False 17m
kube-scheduler 4.15.45 True False False 17m
kube-storage-version-migrator 4.15.45 True False False 10m
monitoring Unknown True Unknown 10m Rolling out the stack.
network 4.15.45 True False False 17m
node-tuning 4.15.45 True False False 11m
openshift-apiserver 4.15.45 True False False 17m
openshift-controller-manager 4.15.45 True False False 17m
openshift-samples 4.15.45 True False False 10m
operator-lifecycle-manager 4.15.45 True False False 17m
operator-lifecycle-manager-catalog 4.15.45 True False False 17m
operator-lifecycle-manager-packageserver 4.15.45 True False False 17m
service-ca 4.15.45 True False False 10m
storage 4.15.45 True False False 11m
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 10m
csi-snapshot-controller 4.15.45 True False False 18m
dns 4.15.45 True False False 11m
image-registry True True True 10m Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 10m 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.45 True False False 11m
kube-apiserver 4.15.45 True False False 18m
kube-controller-manager 4.15.45 True False False 18m
kube-scheduler 4.15.45 True False False 18m
kube-storage-version-migrator 4.15.45 True False False 11m
monitoring Unknown True Unknown 11m Rolling out the stack.
network 4.15.45 True True False 18m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes)...
node-tuning 4.15.45 True True False 47s Waiting for 1/2 Profiles to be applied
openshift-apiserver 4.15.45 True False False 18m
openshift-controller-manager 4.15.45 True False False 18m
openshift-samples 4.15.45 True False False 11m
operator-lifecycle-manager 4.15.45 True False False 18m
operator-lifecycle-manager-catalog 4.15.45 True False False 18m
operator-lifecycle-manager-packageserver 4.15.45 True False False 18m
service-ca 4.15.45 True False False 11m
storage 4.15.45 True True False 12m 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.45 True False False 11m
csi-snapshot-controller 4.15.45 True False False 19m
dns 4.15.45 True False False 12m
image-registry True True True 11m Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 11m 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.45 True False False 12m
kube-apiserver 4.15.45 True False False 19m
kube-controller-manager 4.15.45 True False False 19m
kube-scheduler 4.15.45 True False False 19m
kube-storage-version-migrator 4.15.45 True False False 12m
monitoring Unknown True Unknown 12m Rolling out the stack.
network 4.15.45 True True False 19m DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 1 nodes)...
node-tuning 4.15.45 True True False 48s Waiting for 2/3 Profiles to be applied
openshift-apiserver 4.15.45 True False False 19m
openshift-controller-manager 4.15.45 True False False 19m
openshift-samples 4.15.45 True False False 12m
operator-lifecycle-manager 4.15.45 True False False 19m
operator-lifecycle-manager-catalog 4.15.45 True False False 19m
operator-lifecycle-manager-packageserver 4.15.45 True False False 19m
service-ca 4.15.45 True False False 12m
storage 4.15.45 True False False 13m
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 12m
csi-snapshot-controller 4.15.45 True False False 20m
dns 4.15.45 True True False 13m DNS "default" reports Progressing=True: "Have 2 available DNS pods, want 3."
image-registry True True True 12m Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-77b5cc8897" has timed out progressing.
ingress 4.15.45 True True False 12m 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.45 True False False 13m
kube-apiserver 4.15.45 True False False 20m
kube-controller-manager 4.15.45 True False False 20m
kube-scheduler 4.15.45 True False False 20m
kube-storage-version-migrator 4.15.45 True False False 13m
monitoring Unknown True Unknown 13m Rolling out the stack.
network 4.15.45 True True False 20m DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes)...
node-tuning 4.15.45 True False False 109s
openshift-apiserver 4.15.45 True False False 20m
openshift-controller-manager 4.15.45 True False False 20m
openshift-samples 4.15.45 True False False 13m
operator-lifecycle-manager 4.15.45 True False False 20m
operator-lifecycle-manager-catalog 4.15.45 True False False 20m
operator-lifecycle-manager-packageserver 4.15.45 True False False 20m
service-ca 4.15.45 True False False 13m
storage 4.15.45 True False False 14m
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 13m
csi-snapshot-controller 4.15.45 True False False 21m
dns 4.15.45 True False False 14m
image-registry 4.15.45 True False False 13m
ingress 4.15.45 True False False 13m
insights 4.15.45 True False False 14m
kube-apiserver 4.15.45 True False False 21m
kube-controller-manager 4.15.45 True False False 21m
kube-scheduler 4.15.45 True False False 21m
kube-storage-version-migrator 4.15.45 True False False 14m
monitoring Unknown True Unknown 14m Rolling out the stack.
network 4.15.45 True False False 21m
node-tuning 4.15.45 True False False 2m49s
openshift-apiserver 4.15.45 True False False 21m
openshift-controller-manager 4.15.45 True False False 21m
openshift-samples 4.15.45 True False False 14m
operator-lifecycle-manager 4.15.45 True False False 21m
operator-lifecycle-manager-catalog 4.15.45 True False False 21m
operator-lifecycle-manager-packageserver 4.15.45 True False False 21m
service-ca 4.15.45 True False False 14m
storage 4.15.45 True False False 15m
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 14m
csi-snapshot-controller 4.15.45 True False False 22m
dns 4.15.45 True False False 15m
image-registry 4.15.45 True False False 14m
ingress 4.15.45 True False False 14m
insights 4.15.45 True False False 15m
kube-apiserver 4.15.45 True False False 22m
kube-controller-manager 4.15.45 True False False 22m
kube-scheduler 4.15.45 True False False 22m
kube-storage-version-migrator 4.15.45 True False False 15m
monitoring 4.15.45 True False False 8s
network 4.15.45 True False False 22m
node-tuning 4.15.45 True False False 3m49s
openshift-apiserver 4.15.45 True False False 22m
openshift-controller-manager 4.15.45 True False False 22m
openshift-samples 4.15.45 True False False 15m
operator-lifecycle-manager 4.15.45 True False False 22m
operator-lifecycle-manager-catalog 4.15.45 True False False 22m
operator-lifecycle-manager-packageserver 4.15.45 True False False 22m
service-ca 4.15.45 True False False 15m
storage 4.15.45 True False False 16m
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 15m
csi-snapshot-controller 4.15.45 True False False 23m
dns 4.15.45 True False False 16m
image-registry 4.15.45 True False False 15m
ingress 4.15.45 True False False 15m
insights 4.15.45 True False False 16m
kube-apiserver 4.15.45 True False False 23m
kube-controller-manager 4.15.45 True False False 23m
kube-scheduler 4.15.45 True False False 23m
kube-storage-version-migrator 4.15.45 True False False 16m
monitoring 4.15.45 True False False 68s
network 4.15.45 True False False 23m
node-tuning 4.15.45 True False False 4m49s
openshift-apiserver 4.15.45 True False False 23m
openshift-controller-manager 4.15.45 True False False 23m
openshift-samples 4.15.45 True False False 16m
operator-lifecycle-manager 4.15.45 True False False 23m
operator-lifecycle-manager-catalog 4.15.45 True False False 23m
operator-lifecycle-manager-packageserver 4.15.45 True False False 23m
service-ca 4.15.45 True False False 16m
storage 4.15.45 True False False 17m
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 16m
csi-snapshot-controller 4.15.45 True False False 24m
dns 4.15.45 True False False 17m
image-registry 4.15.45 True False False 16m
ingress 4.15.45 True False False 16m
insights 4.15.45 True False False 17m
kube-apiserver 4.15.45 True False False 24m
kube-controller-manager 4.15.45 True False False 24m
kube-scheduler 4.15.45 True False False 24m
kube-storage-version-migrator 4.15.45 True False False 17m
monitoring 4.15.45 True False False 2m9s
network 4.15.45 True False False 24m
node-tuning 4.15.45 True False False 5m50s
openshift-apiserver 4.15.45 True False False 24m
openshift-controller-manager 4.15.45 True False False 24m
openshift-samples 4.15.45 True False False 17m
operator-lifecycle-manager 4.15.45 True False False 24m
operator-lifecycle-manager-catalog 4.15.45 True False False 24m
operator-lifecycle-manager-packageserver 4.15.45 True False False 24m
service-ca 4.15.45 True False False 17m
storage 4.15.45 True False False 18m
Waiting for cluster to be reported as healthy... Trying again in 60s
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
console 4.15.45 True False False 17m
csi-snapshot-controller 4.15.45 True False False 25m
dns 4.15.45 True False False 18m
image-registry 4.15.45 True False False 17m
ingress 4.15.45 True False False 17m
insights 4.15.45 True False False 18m
kube-apiserver 4.15.45 True False False 25m
kube-controller-manager 4.15.45 True False False 25m
kube-scheduler 4.15.45 True False False 25m
kube-storage-version-migrator 4.15.45 True False False 18m
monitoring 4.15.45 True False False 3m9s
network 4.15.45 True False False 25m
node-tuning 4.15.45 True False False 6m50s
openshift-apiserver 4.15.45 True False False 25m
openshift-controller-manager 4.15.45 True False False 25m
openshift-samples 4.15.45 True False False 18m
operator-lifecycle-manager 4.15.45 True False False 25m
operator-lifecycle-manager-catalog 4.15.45 True False False 25m
operator-lifecycle-manager-packageserver 4.15.45 True False False 25m
service-ca 4.15.45 True False False 18m
storage 4.15.45 True False False 19m
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant