On Mon, Jun 22, 2020 at 4:55 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Mon, Jun 22, 2020 at 9:12 AM Yedidyah Bar David <didi@redhat.com> wrote:
I agree. Would you like to open a bug about this? It's not always easy to know the root cause for the failure, nor to pass it through the various components until it can reach the end-user.
Sure. Happy to. Against which bugzilla component?
Perhaps first have a look at: https://bugzilla.redhat.com/show_bug.cgi?id=1816002 and decide if to add a comment there, or create new bug (same product/component).
Not sure it must abort. In principle, you could have supplied custom ansible code to be ran inside the appliance, to add the items yourself to /etc/hosts, or in theory it can also happen that you configured stuff so that the host fails DNS resolution but the engine VM does not.
It also asked you:
2020-06-21 10:49:18,562-0400 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND Add lines for the appliance itself and for this host to /etc/hosts on the engine VM? 2020-06-21 10:49:18,562-0400 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND Note: ensuring that this host could resolve the engine VM hostname is still up to you 2020-06-21 10:49:18,563-0400 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND (Yes, No)[No]
And you accepted the default 'No'.
Perhaps we should change the default to Yes.
I must have missed it. In this case: A. It is essentially PBKAC. B. I believe that given the fact the problem was actually detected by the installer early on, I believe the installer should enforce having either hosts entry or working DNS setup. (Or at least show a big red flashing message saying: "Look, are you sure you want to set up a broken hosted engine VM and that cannot possibly resolve the host address and will uncertainly fail miserably once we try and deploy the hosted engine?")
I agree this makes sense, although as I said, it's not fully certain to fail. The code emitting this warning is general - it's used both here and in engine-setup. I agree that here (in hosted-engine) it's more important.
Of course - Yes is also a risk - a user not noticing it, then later on changing the DNS, and not understanding why it "does not work"...
Indeed.
In theory, you can examine the ansible code, and see what (not very many) next steps it should have done if it didn't fail there, and do that yourself (or decide that they are not important). In practice, I'd personally deploy again cleanly, unless this is for a quick test or something.
Best regards, --
I'll simply clean up and redeploy. Hopefully after suffering a long string of PBKAC and DNS related failures, I'll finally have a working setup :)
Good luck!
And again, many thanks for taking the time to assist me. I appreciate it!
Best regards, -- Didi