Re: [ovirt-users] oVirt Engine 4.2 -> 4.2.1 Upgrade
On Wed, Mar 14, 2018 at 6:56 PM, Andrei Verovski <andreil1(a)starlett.lv> wrote:
Hi !
After oVirt Engine 4.2 -> 4.2.1 Upgrade do I need to run these commands as described
in this article
https://www.ovirt.org/release/4.2.1/
Please note that the start of this section says:
"For databases managed by engine-setup this is performed
automatically, but non-managed databases (usually remote databases)
this needs to be done manually by administrators."
Is your database remote or managed manually, or local and managed by
engine-setup? If latter, it's enough to run 'engine-setup'.
su - postgres -c "scl enable rh-postgresql95 – psql -d engine"
postgres=# DROP FUNCTION IF EXISTS uuid_generate_v1();
postgres=# CREATE EXTENSION "uuid-ossp”;
Sorry, this is a bug in the documentation. The commands should be:
su - postgres -c "scl enable rh-postgresql95 -- psql -d engine"
postgres=# DROP FUNCTION IF EXISTS uuid_generate_v1();
postgres=# CREATE EXTENSION "uuid-ossp";
BTW, this yelds error:
[root@node00 ~]# su - postgres -c "scl enable rh-postgresql95 – psql -d
engine"
Unable to open /etc/scl/conf/–!
Indeed.
The reason that this bug happened is that the release notes are (partially)
auto-generated, where this part is taken from the doc-text of the linked bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1515635
The text there is ok.
We should somehow make the resultant markdown mark such doc text as
pre-formatted,
to prevent it from replacing '--' with '–'. Adding Sandro for this.
Thanks for the report!
node00 is a dedicated PC with CentOS and oVirt Host Engine.
Sounds to me like you are in the "this will happen automatically" case.
Best regards,
--
Didi