[ovirt-users] Problem to upgrade ovirt

Marcelo Leandro marceloltmm at gmail.com
Wed Apr 25 12:55:37 UTC 2018


Hello ,
 I do a full-backup of ovirt-engine,instaled ovirt-engine in new host ,
drop database postgres and create a new with this steps:

 1-drop database postgres;
 2- create database template1 with owner=postgres encoding='UTF-8'
   lc_collate='en_US.utf8' lc_ctype='en_US.utf8' template template0;

and after this steps I restores backup of ovirt-engine and run
engine-setup, upgrade works now.

With this steps I can obtain somethings erros in the future?

Thanks,

Marcelo Leandro

Em seg, 23 de abr de 2018 17:04, Marcelo Leandro <marceloltmm at gmail.com>
escreveu:

> Thank you for reply,
>
>
> "BZ 1515635 [RFE] Drop uuid_generate_v1() internal implementation and use
> the implementation from standard PostgreSQL uuid-ossp extension
> We have added a requirement for uuid-ossp PostgreSQL extension to be
> present in engine database. 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. "
>
>
> my database is  managed by engine-setup, so i think that is perfomed
> automatically. I know that problem in my database , but I instaled it`s
> whith engine-setup com default options.
>
> I try an new instalation in new host and restore backup and when I try
> update I had take the same error.
>
>
> Very thanks!!
>
>
>
>
>
> 2018-04-23 16:47 GMT-03:00 Alexander Wels <awels at redhat.com>:
>
>> On Monday, April 23, 2018 3:23:21 PM EDT Marcelo Leandro wrote:
>> > Can someone help me?
>> >
>> > Thanks,
>> >
>> > Marcelo Leandro
>> >
>>
>> You need postgresql 9.5, following the information here should give you
>> everything you need:
>>
>> https://www.ovirt.org/release/4.2.1/
>>
>> Also look at the information below 'What's New in 4.2.1' it has some
>> information on upgrading the uuid generation which requires some manual
>> steps.
>>
>> > 2018-04-23 8:27 GMT-03:00 Robert O'Kane <okane at khm.de>:
>> > > Hello,
>> > >
>> > > Sorry, I did not have to chance anything else. It simply worked after
>> my
>> > > SELinux solution.
>> > >
>> > > Good Luck.
>> > >
>> > > Robert O'Kane
>> > >
>> > > On 04/23/2018 01:21 PM, Marcelo Leandro wrote:
>> > >> Hello, Robert
>> > >>
>> > >> Thank you for reply, I tried this steps but not worked for me , I
>> think
>> > >> that I need change parameters in my postgresql but I don't know how
>> do
>> > >> this.
>> > >>
>> > >>
>> > >> 2018-04-22 7:45 GMT-03:00 Robert O'Kane <okane at khm.de <mailto:
>> > >>
>> > >> okane at khm.de>>:
>> > >>     Hello,
>> > >>
>> > >>     I had a similar problem with the engine update from 4.1.9 to
>> 4.2.2.
>> > >>     For me it was SELinux in Enforcing mode on the host.  You should
>> > >>
>> > >> check that
>> > >>
>> > >>     SELinux is in "Enforcing" mode and that the audit daemon is
>> > >>
>> > >> complaining
>> > >>
>> > >>     about postgres95. "audit2why -a"
>> > >>
>> > >>
>> > >>     I set the host to "Permissive", did the upgrade and it worked
>> for me.
>> > >>     But you may have to leave it in "Permissive" mode until you can
>> > >>
>> > >> update the
>> > >>
>> > >>     SELinux rules.
>> > >>
>> > >>
>> > >>     *IF* the problem is SELinux I would suggest:
>> > >>
>> > >>     1: Clean up the auditd logs (make sure all old problems are
>> > >>
>> > >> corrected).
>> > >>
>> > >>         Reset the auditd logs so the following output is "cleaner".
>> > >>         The "audit2why -a" command should show nothing. Please
>> RYFM....
>> > >>
>> > >>     2: Set SELinux to "Permissive" mode.
>> > >>
>> > >>     3: Apply the Ovirt-engine updates. Make sure everything works.
>> > >>
>> > >>     4: run "audit2why -a" and see what the warnings are
>> > >>
>> > >>       or go directly to 5
>> > >>
>> > >>     5: generate the new rules with:
>> > >>            audit2allow -a -M postgres95-selinux-ovirt
>> > >>
>> > >>     6: add the rules to the system:
>> > >>            semodule -i  postgres95-selinux-ovirt.pp
>> > >>
>> > >>     7: It should now be possible to set SELinux back to "Enforcing"
>> > >>
>> > >>
>> > >>     Good Luck,
>> > >>
>> > >>     Robert O'Kane
>> > >>
>> > >>     Am 21.04.2018 um 10:26 schrieb Marcelo Leandro:
>> > >>         Hello,
>> > >>         I have problem when i try upgrade the ovirt to 4.2,  my
>> version
>> > >>
>> > >> is 4.1.9, I
>> > >>
>> > >>         have problem when engine-setup try update the postgresql.
>> > >>         Postgres version 9.2
>> > >>
>> > >>         I had this message:
>> > >>
>> > >>         Log install:
>> > >>
>> > >>         ERROR: pg_upgrade tool failed
>> > >>         ERROR: Upgrade failed.
>> > >>
>> > >>            * See /var/lib/pgsql/upgrade_rh-
>> postgresql95-postgresql.log
>> > >>
>> > >> for details.
>> > >>
>> > >>         2018-04-21 04:53:10,766-0300 DEBUG otopi.transaction
>> > >>         transaction._prepare:66 exception during prepare phase
>> > >>
>> > >>         Traceback (most recent call last):
>> > >>             File "/usr/lib/python2.7/site-
>> packages/otopi/transaction.py",
>> > >>
>> > >> line
>> > >>
>> > >>         62, in
>> > >>         _prepare
>> > >>
>> > >>               element.prepare()
>> > >>
>> > >>             File
>> > >>
>> > >>         "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_
>> > >>
>> > >> common/postgres.py",
>> > >>
>> > >>         line 777, in prepare
>> > >>
>> > >>               raiseOnError=True,
>> > >>
>> > >>             File "/usr/lib/python2.7/site-packages/otopi/plugin.py",
>> > >>
>> > >> line 931, in
>> > >>
>> > >>         execute
>> > >>
>> > >>               command=args[0],
>> > >>
>> > >>         RuntimeError: Command
>> > >>         '/opt/rh/rh-postgresql95/root/usr/bin/postgresql-setup'
>> failed
>> > >>
>> > >> to execute
>> > >>
>> > >>         2018-04-21 04:53:10,768-0300 DEBUG otopi.context
>> > >>
>> > >> context._executeMethod:143
>> > >>
>> > >>         method exception
>> > >>
>> > >>         Traceback (most recent call last):
>> > >>             File "/usr/lib/python2.7/site-
>> packages/otopi/context.py",
>> > >>
>> > >> line 133, in
>> > >>
>> > >>         _executeMethod
>> > >>
>> > >>               method['method']()
>> > >>
>> > >>             File
>> > >>
>> > >>         "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-
>> > >>
>> > >> setup/ovirt-engine/db/dbmsupgrade.py",
>> > >>
>> > >>         line 89, in _updateDBMS
>> > >>
>> > >>               oengcommcons.ProvisioningEnv.OLD_POSTGRES_SERVICE
>> > >>
>> > >>             File "/usr/lib/python2.7/site-
>> packages/otopi/transaction.py",
>> > >>
>> > >> line 106,
>> > >>
>> > >>         in append
>> > >>
>> > >>               self._prepare(element=element)
>> > >>
>> > >>             File "/usr/lib/python2.7/site-
>> packages/otopi/transaction.py",
>> > >>
>> > >> line
>> > >>
>> > >>         62, in
>> > >>         _prepare
>> > >>
>> > >>               element.prepare()
>> > >>
>> > >>             File
>> > >>
>> > >>         "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_
>> > >>
>> > >> common/postgres.py",
>> > >>
>> > >>         line 777, in prepare
>> > >>
>> > >>               raiseOnError=True,
>> > >>
>> > >>             File "/usr/lib/python2.7/site-packages/otopi/plugin.py",
>> > >>
>> > >> line 931, in
>> > >>
>> > >>         execute
>> > >>
>> > >>               command=args[0],
>> > >>
>> > >>         RuntimeError: Command
>> > >>         '/opt/rh/rh-postgresql95/root/usr/bin/postgresql-setup'
>> failed
>> > >>
>> > >> to execute
>> > >>
>> > >>         2018-04-21 04:53:10,770-0300 ERROR otopi.context
>> > >>
>> > >> context._executeMethod:152
>> > >>
>> > >>         Failed to execute stage 'Misc configuration': Command
>> > >>         '/opt/rh/rh-postgresql95/root/usr/bin/postgresql-setup'
>> failed
>> > >>
>> > >> to execute
>> > >>
>> > >>         Log postgres:
>> > >>         Performing Consistency Checks
>> > >>         -----------------------------
>> > >>         Checking cluster versions
>>  ok
>> > >>         Checking database user is the install user
>> ok
>> > >>         Checking database connection settings
>>  ok
>> > >>         Checking for prepared transactions
>> ok
>> > >>         Checking for reg* system OID user data types
>> ok
>> > >>         Checking for contrib/isn with bigint-passing mismatch
>>  ok
>> > >>         Checking for invalid "line" user columns
>> ok
>> > >>         Creating dump of global objects
>>  ok
>> > >>         Creating dump of database schemas
>> > >>
>> > >>             engine
>> > >>             ovirt_engine_history
>> > >>             postgres
>> > >>             template1
>> > >>
>> > >>
>>  ok
>> > >>
>> > >>         encodings for database "postgres" do not match:  old
>> "SQL_ASCII",
>> > >>
>> > >> new "UTF8"
>> > >>
>> > >>         Failure, exiting
>> > >>
>> > >>
>> > >>         I know that problem not is in oVirt , but anyone help me ?
>> > >>
>> > >>
>> > >>         Thank you!
>> > >>
>> > >>
>> > >>
>> > >>         _______________________________________________
>> > >>         Users mailing list
>> > >>         Users at ovirt.org <mailto:Users at ovirt.org>
>> > >>         http://lists.ovirt.org/mailman/listinfo/users
>> > >>         <http://lists.ovirt.org/mailman/listinfo/users>
>> > >>
>> > >>     --     Systems Administrator
>> > >>     Kunsthochschule für Medien Köln
>> > >>     Peter-Welter-Platz 2
>> > >>     50676 Köln
>> > >>     _______________________________________________
>> > >>     Users mailing list
>> > >>     Users at ovirt.org <mailto:Users at ovirt.org>
>> > >>     http://lists.ovirt.org/mailman/listinfo/users
>> > >>     <http://lists.ovirt.org/mailman/listinfo/users>
>> > >
>> > > --
>> > > Robert O'Kane
>> > > Systems Administrator
>> > > Kunsthochschule für Medien Köln
>> > > Peter-Welter-Platz 2
>> > > 50676 Köln
>> > >
>> > > fon: +49(221)20189-223
>> > > fax: +49(221)20189-49223
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180425/beb341c9/attachment.html>


More information about the Users mailing list