check early if nodes have a hostname of localhost and error

[dustymabe]

Version

openshift-install unreleased-master-2503-g0f0142e7261349b93c3dd3dd02a9ce164dfd2d4f-dirty
built from commit 0f0142e7261349b93c3dd3dd02a9ce164dfd2d4f
release image quay.io/openshift/okd@sha256:057e2eead0443a60877fc9b579770e6464eb7fa8d92855f5c2f09ef7340d60db

Platform:

baremetal

• UPI (semi-manual installation on customised infrastructure)

What happened?

Basically a lot of chasing random error messages on the internet to find out later my nodes didn't have hostnames set. They were all set to localhost because of this bug.

I'd like to know if we can somehow add a rudimentary error check somewhere early on in the bootstrap/install process and bubble up a nice error message to the user that says "your hostnames are set to localhost, which is probably the root of your issues". It's been a while since I installed openshift and it took me a while to dig in and find the root of my problems. This could definitely bite a new user hard. Can we improve?

[wking]

I don't see this as install-specific, and would rather address it with rhbz#1817774 or similar. We'd still want to follow that up with installer-side code to gather alerts and log them from the log bundle (#2569).

[darkmuggle]

This might be addressed with openshift/machine-config-operator#1813

[dustymabe]

I guess what I'm looking for is somehow getting a message back up the user that says: "hey, this system isn't going to work, or probably isn't going to work because your hostnames are set to localhost".

Anything that makes that happen would be a win!

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.