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

ERROR Attempted to gather ClusterOperator status after installation failure #7899

Open
springfred opened this issue Jan 11, 2024 · 2 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@springfred
Copy link

Version

$ openshift-install version
openshift-install 4.11.56
built from commit 080693d2736ac301bfebf09f83da79cc4cf902d8
release image quay.io/openshift-release-dev/ocp-release@sha256:6fcfee1b6d7e4d2f9c0e05ec2b0ad159809ea93736ac0acdc710df0584510892
release architecture amd64

Platform:

vsphere

IPI

What happened?

DEBUG Unable to connect to the server: dial tcp 192.168.0.9:6443: connect: no route to host 
DEBUG Unable to connect to the server: dial tcp 192.168.0.9:6443: connect: no route to host 
DEBUG Gather remote logs                           
DEBUG No masters found!                            
DEBUG Log bundle written to /var/home/core/log-bundle-20240111191454.tar.gz 
WARNING Unable to stat /opt/openshift/packages/okd-offline/4.11.56/okd/serial-log-bundle-20240111191454.tar.gz, skipping 
ERROR Attempted to gather ClusterOperator status after installation failure: listing ClusterOperator objects: Get "https://api.openshift4.poc.com:6443/apis/config.openshift.io/v1/clusteroperators": dial tcp 192.168.0.9:6443: connect: no route to host 
ERROR Bootstrap failed to complete: Get "https://api.openshift4.poc.com:6443/version": dial tcp 192.168.0.9:6443: connect: no route to host 
ERROR Failed waiting for Kubernetes API. This error usually happens when there is a problem on the bootstrap host that prevents creating a temporary control plane. 
INFO Bootstrap gather logs captured here "/opt/openshift/packages/okd-offline/4.11.56/okd/log-bundle-20240111191454.tar.gz" 

What you expected to happen?

Enter text here.

How to reproduce it (as minimally and precisely as possible)?

$ openshift-install create install-config --dir=okd
$ cat okd/install-config.yaml
apiVersion: v1
baseDomain: poc.com
compute:
- architecture: amd64
  hyperthreading: Enabled
  name: worker
  platform: {}
  replicas: 3
controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  platform: {}
  replicas: 3
metadata:
  creationTimestamp: null
  name: openshift4
networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  machineNetwork:
  - cidr: 10.0.0.0/16
  networkType: OpenShiftSDN
  serviceNetwork:
  - 172.30.0.0/16
platform:
  vsphere:
    apiVIP: 192.168.0.9
    cluster: vcluster
    datacenter: Datacenter
    defaultDatastore: datastore1
    ingressVIP: 192.168.0.10
    network: XXX
    password: XXX
    username: administrator@vsphere.local
    vCenter: vcenter.poc.com
publish: External
pullSecret: 'XXXX'
sshKey: |
  XXXXX

$ openshift-install create cluster --dir=okd --log-level=debug

openshift_install.log

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 12, 2024
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

2 participants