Skip to content

Error on unknown hostname - #551

Open
frelon wants to merge 1 commit into
SUSE:mainfrom
frelon:unknown-hostname-error
Open

Error on unknown hostname#551
frelon wants to merge 1 commit into
SUSE:mainfrom
frelon:unknown-hostname-error

Conversation

@frelon

@frelon frelon commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

During kubernetes provisioning the current behavior is to assume a node
is a 'server' and if found in the list of nodes we set it to the found
node-type.

In this commit we abort with an error if the node is not found for
multi-node clusters.

Signed-off-by: Fredrik Lönnegren fredrik.lonnegren@suse.com

During kubernetes provisioning the current behavior is to assume a node
is a 'server' and if found in the list of nodes we set it to the found
node-type.

In this commit we abort with an error if the node is not found for
multi-node clusters.

Signed-off-by: Fredrik Lönnegren <fredrik.lonnegren@suse.com>
@frelon
frelon requested a review from a team as a code owner August 5, 2026 11:40
@dharmit

dharmit commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

EDIT: This is probably a me problem. I'm facing this with main branch as well. Running openssl passwd -6 as mentioned in the code comment in butane.yaml and using the hash it provided also doesn't let me login to the VM. Weird.

I don't know if it's just me, but a multi-node or single-node image built using this PR is not letting me login with root-linux credentials that we have configured in butane.yaml for these examples.

I do make a change before building the image for both example types which is rebase against main to have changes from #549 pulled in so that customize doesn't fail with LCM requirement. But I don't suppose that should lead to such a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants