Loading...

XML

Word

Printable

Type: Bug
Resolution: Duplicate
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.14.0
Component/s: Installer / Assisted installer
Labels:

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
Important
Regression:
Yes

Target Backport Versions:
None
Target Version:
None
Release Blocker:
Rejected
Sprint:
AI-34, AI-35
sprint_count:
2

Internal Whiteboard:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

Installation of 4.14.0-rc.0 on a multi-node cluster managedcluster via ZTP workflow fails with error:

"Host failed to install because its installation stage Waiting for bootkube took longer than expected "

Version-Release number of selected component (if applicable):

4.14

How reproducible:

Always

Steps to Reproduce:

1. Hub cluster running OCP 4.13.11 with ACM 2.8, TALM 4.14, GitOps operator
2. Target managed cluster is a 5-node standard cluster on baremetal. 
3. Trigger spoke cluster installation via ZTP workflow

Example job: https://ci-jenkins-csb-kniqe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-far-edge-vran-deployment/5945/

Actual results:

spoke cluster installation fails with error: Host failed to install because its installation stage Waiting for bootkube took longer than expected

Expected results:

spoke cluster installation should succeed.

Additional info:

OCP installations of 4.14 nightly prior to 4.14.0-rc.0 have bee successful on this cluster.

Assignee:: Daniel Erez

Reporter:: Joshua Clark

Need Info From:: None

Contributors:: None

QA Contact:: Joshua Clark

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 14 Start watching this issue

Created:: 2023/09/12 2:07 AM

Updated:: 2025/07/25 5:30 PM

Resolved:: 2023/10/16 5:54 PM