After deploying a RHOSP17.1 node, we cannot login using tripleo-admin

Solution In Progress - Updated -

Issue

  • After deploying a RHOSP17.1 node, we cannot login using tripleo-admin but the host pings and has the correct hostname.

  • Using rd.break selinux=0 in the kernel arguments at boot time, we gained access to the freshly deployed host and found the following error in /var/log/cloud-init-output.log:

2024-09-25 12:52:52,966 - util.py[DEBUG]: Failed to mount device: '/dev/sda2' with type: 'auto' using mount command: 'mount -o ro -t auto /dev/sda2 /run/cloud-init/tmp/tmp80u1_qpa', which caused exception: Unexpected error while running command.
Command: ['mount', '-o', 'ro', '-t', 'auto', '/dev/sda2', '/run/cloud-init/tmp/tmp80u1_qpa']
Exit code: 32
Reason: -
Stdout:
Stderr: mount: /run/cloud-init/tmp/tmp80u1_qpa: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error.

Environment

  • Red Hat OpenStack Platform 17.1 (RHOSP)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content