search

redhat-performance / JetSki

Deployment Automation for OpenShift on Baremetal in Red Hat's Shared Labs
Apache License 2.0
21 stars 29 forks source link

[Issue] Provisioner Node Upgrade to CoreOS post deployment and reboot #306

Closed pradiptapks closed 2 months ago

pradiptapks commented 6 months ago

Upon upgrading the provisioner node from RHEL-8.4 to RHEL-8.6 in the scale lab, we encountered an issue where the hosts were inaccessible with the existing credentials, and it was observed that the host OS had been upgraded to CoreOS.

Steps Taken:

  1. Utilizing Jetski and the provisioner host (initially installed with RHEL8.4), we deployed the OCP4.14 cluster with baremetal nodes.
  2. Post-deployment, access to the provisioner host was successful using both root and kni user credentials.
  3. Subsequently, we upgraded the repositories from RHEL 8.4 to 8.6 and performed the host upgrade on the provisioner host.
  4. Following a clean reboot, it was noted that the host was no longer accessible, displaying CoreOS on the hardware console.

We seek clarification on whether this behaviour is expected with Jetski. If so, careful planning will be necessary for the deployment of RHOSP-18.0 next-gen.

image

github-actions[bot] commented 3 months ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days