[ovirt-users] Re: Self-hosted engine deploy failed
On Tue, Aug 23, 2022 at 8:01 PM Henry Wong <dewongway(a)gmail.com> wrote:
Yes, I used cockpit to deploy the hosted-engine as I wasn't aware it's been
deprecated.
Sorry for that.
If you believe this issue is specific to the cockpit deployment
method only,
Can't be certain, obviously, but it does look so - and for the CLI,
unlike cockpit, we have automated testing, so at least for the common
case we are likely to find bugs before actual users do.
is there a need to open a bug since it should/will be removed from
cockpit in the future, correct?
If enough people want cockpit back, and enough of these people want to
invest the time in maintaining it, it can live on...
I didn't try cockpit myself recently, and frankly, hardly ever did
overall - other than when trying to fix bugs in it. I personally find
the CLI much better, main reason being that you can run it inside tmux
and get back to it if the network went down in the middle. We had a
bug asking to be able to return back to a running cockpit HE deploy,
but eventually gave up on it - required too much work.
Just need to update the documentation to point that out?
I guess so, yes. Would you like to create a documentation bug/issue
for this? Or send a patch? How to do this: Start with the page you
followed when deciding to deploy - the point in which you'd expect
such a note - then scroll down to the bottom press either 'Report an
issue with this page' or 'Edit this page'. Thanks.
To be honest, 4.5 has been a headache for me. I have been on 4.4 for over a year and
never had so many issues. This all started from the upgrade of 4.4. to 4.5, which caused
the engine failed to start,
Was this resolved? Did you report a bug?
and later found out was related to the postgresql version
incompatibility issue.
PG itself? Or postgresql-jdbc? We had problems around that during 4.4
time - I think in 4.5 they are all resolved.
But it was already too late as I decided to do a fresh install and
thought it would be much cleaner and faster. In any way I have it back and it's on
4.5 but it will make me think twice next time before going for an update.
If this is a production setup, I definitely recommend trying an update
on a test env beforehand. Not only for oVirt, BTW...
Good luck and best regards,
--
Didi