Loading...

XML

Word

Printable

Target Backport Versions:
None
Target Version:

4.21.0
Release Blocker:
None
Sprint:
ShiftStack Sprint 256, ShiftStack Sprint 280, ShiftStack Sprint 281, Bug Delivery Tracker
sprint_count:
4

Release Note Status:
Done
Release Note Type:
Bug Fix
Release Note Text:

Hide
Before this update, the bootstrap logs could not be collected as the ssh connection was dropped because a security-group rule for the bootstrap machine was missing. With this release, an additional security-group is added to the bootstrap machine to enable ssh connection and to enable log collection. (link:https://issues.redhat.com/browse/OCPBUGS-34950[~~OCPBUGS-34950~~])

Show
Before this update, the bootstrap logs could not be collected as the ssh connection was dropped because a security-group rule for the bootstrap machine was missing. With this release, an additional security-group is added to the bootstrap machine to enable ssh connection and to enable log collection. (link: https://issues.redhat.com/browse/OCPBUGS-34950 [ OCPBUGS-34950 ])

Description of problem: With CAPI-based installer, we're not able to download the bootstrap logs when anything goes wrong during bootstrap.

Looking at a failed job, we can see from the logs:

Failed to gather bootstrap logs: failed to connect to the bootstrap machine: dial tcp 10.0.2.116:22: connect: connection timed out

I see two issues:

the IP is from the machine subnet, and the node where the installer runs don't have access to it. We need to connect to the bootstrap VM via a floating IP.
we don't open SSH in security groups, which would prevent pulling the logs.

Not having bootstrap logs makes it nearly impossible to debug any bootstrapping issue.

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

How reproducible:

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

Expected results:

Additional info:

links to