Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-06 Thread Simone Tiraboschi 
On Wed, Sep 6, 2017 at 10:35 AM, Barak Korren  wrote:

> On 6 September 2017 at 11:11, Simone Tiraboschi 
> wrote:
> >
> > if you have both yesterday patches it was going to fail due to the lack
> of
> > rh-postgresql95-postgresql-server
> >
> > https://gerrit.ovirt.org/#/c/81478/ should be enough to require
> > rh-postgresql95-postgresql-server by itself,
> > so if DWH is part of the upgrade test, I hope it will pass.
>
> It passed:
> http://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-
> master_change-queue-tester/detail/ovirt-master_change-
> queue-tester/2347/pipeline


Thanks, nice to hear!


>
>
> Currently uploading updated packages to 'tested'.
>
>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-06 Thread Barak Korren 
On 6 September 2017 at 11:11, Simone Tiraboschi  wrote:
>
> if you have both yesterday patches it was going to fail due to the lack of
> rh-postgresql95-postgresql-server
>
> https://gerrit.ovirt.org/#/c/81478/ should be enough to require
> rh-postgresql95-postgresql-server by itself,
> so if DWH is part of the upgrade test, I hope it will pass.

It passed:
http://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-master_change-queue-tester/detail/ovirt-master_change-queue-tester/2347/pipeline

Currently uploading updated packages to 'tested'.


-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-06 Thread Simone Tiraboschi 
On Wed, Sep 6, 2017 at 10:03 AM, Barak Korren  wrote:

> On 6 September 2017 at 10:58, Simone Tiraboschi 
> wrote:
> >
> >
> > We already found an rpm dependency issue on upgrade so now I'd say:
> > https://gerrit.ovirt.org/81478 and https://gerrit.ovirt.org/81476
> (still to
> > be merged) in order to solve also that issue.
> >
> Hmm... I thought the upgrade issue was what we were discussing.
>
> I triggered a CQ run with the latest merged engine and dwh patches. If
> I understand correctly it is doomed to fail as well?
>

Yes, two distinct issue:

if you don't test the two previous patch at the same time it's going to
fail with

engine-setup --config-append=/tmp/answer-file-post --accept-defaults
returned with 2
output:
 ***L:ERROR Internal error: type object 'DBEnvKeysConst' has no attribute
'NEED_DBMSUPGRADE'

if you have both yesterday patches it was going to fail due to the lack
of rh-postgresql95-postgresql-server

https://gerrit.ovirt.org/#/c/81478/ should be enough to require
rh-postgresql95-postgresql-server
by itself,
so if DWH is part of the upgrade test, I hope it will pass.

Thanks!




>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-06 Thread Barak Korren 
On 6 September 2017 at 10:58, Simone Tiraboschi  wrote:
>
>
> We already found an rpm dependency issue on upgrade so now I'd say:
> https://gerrit.ovirt.org/81478 and https://gerrit.ovirt.org/81476 (still to
> be merged) in order to solve also that issue.
>
Hmm... I thought the upgrade issue was what we were discussing.

I triggered a CQ run with the latest merged engine and dwh patches. If
I understand correctly it is doomed to fail as well?

-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-06 Thread Simone Tiraboschi 
On Wed, Sep 6, 2017 at 9:48 AM, Barak Korren  wrote:

> On 6 September 2017 at 10:42, Simone Tiraboschi 
> wrote:
> >
> >
> > On Wed, Sep 6, 2017 at 9:34 AM, Barak Korren  wrote:
> >>
> >> On 5 September 2017 at 17:59, Simone Tiraboschi 
> >> wrote:
> >> >
> >> >
> >> > On Tue, Sep 5, 2017 at 2:00 PM, Dan Kenigsberg 
> >> > wrote:
> >> >>
> >> >> I believe that this issue is being tackled by
> >> >> https://gerrit.ovirt.org/#/c/81444/
> >> >
> >> >
> >> > No, the issue is on DWH setup side but we merged the related patches
> >> > there
> >> > almost together.
> >> > Not sure why OST is consuming an older DWH rpm.
> >>
> >> OST only uses packages that passed OST before + packages you explicitly
> >> add.
> >> The newer DWH setup package probably did not pass OST yet from one
> >> reason or another.
> >
> >
> > OK, in order to start consuming postgres 9.5 from SCL I had to introduce
> a
> > patch on ovirt-engine project and another on dwh project and I don't
> think
> > that we can successfully run the test suite with just one of the two.
> >
> > Should we simply wait or we have to manually run OST with a list of
> packages
> > from the two projects in order to have it flagging them as OK?
>
> Since we don`t have change dependency syntax yet, we need to trick the
> change queue into testing them together. The way to do that is to wait
> until it is busy testing something else and then send both changes
> together.
> We also need to make sure there are not other issues that will make it
> fail. We can verify that by using the manual job with both changes.
> Which are the two relevant changes?
>

We already found an rpm dependency issue on upgrade so now I'd say:
https://gerrit.ovirt.org/81478 and https://gerrit.ovirt.org/81476 (still to
be merged) in order to solve also that issue.


>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-06 Thread Barak Korren 
On 6 September 2017 at 10:42, Simone Tiraboschi  wrote:
>
>
> On Wed, Sep 6, 2017 at 9:34 AM, Barak Korren  wrote:
>>
>> On 5 September 2017 at 17:59, Simone Tiraboschi 
>> wrote:
>> >
>> >
>> > On Tue, Sep 5, 2017 at 2:00 PM, Dan Kenigsberg 
>> > wrote:
>> >>
>> >> I believe that this issue is being tackled by
>> >> https://gerrit.ovirt.org/#/c/81444/
>> >
>> >
>> > No, the issue is on DWH setup side but we merged the related patches
>> > there
>> > almost together.
>> > Not sure why OST is consuming an older DWH rpm.
>>
>> OST only uses packages that passed OST before + packages you explicitly
>> add.
>> The newer DWH setup package probably did not pass OST yet from one
>> reason or another.
>
>
> OK, in order to start consuming postgres 9.5 from SCL I had to introduce a
> patch on ovirt-engine project and another on dwh project and I don't think
> that we can successfully run the test suite with just one of the two.
>
> Should we simply wait or we have to manually run OST with a list of packages
> from the two projects in order to have it flagging them as OK?

Since we don`t have change dependency syntax yet, we need to trick the
change queue into testing them together. The way to do that is to wait
until it is busy testing something else and then send both changes
together.
We also need to make sure there are not other issues that will make it
fail. We can verify that by using the manual job with both changes.
Which are the two relevant changes?

-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-06 Thread Simone Tiraboschi 
On Wed, Sep 6, 2017 at 9:34 AM, Barak Korren  wrote:

> On 5 September 2017 at 17:59, Simone Tiraboschi 
> wrote:
> >
> >
> > On Tue, Sep 5, 2017 at 2:00 PM, Dan Kenigsberg 
> wrote:
> >>
> >> I believe that this issue is being tackled by
> >> https://gerrit.ovirt.org/#/c/81444/
> >
> >
> > No, the issue is on DWH setup side but we merged the related patches
> there
> > almost together.
> > Not sure why OST is consuming an older DWH rpm.
>
> OST only uses packages that passed OST before + packages you explicitly
> add.
> The newer DWH setup package probably did not pass OST yet from one
> reason or another.
>

OK, in order to start consuming postgres 9.5 from SCL I had to introduce a
patch on ovirt-engine project and another on dwh project and I don't think
that we can successfully run the test suite with just one of the two.

Should we simply wait or we have to manually run OST with a list of
packages from the two projects in order to have it flagging them as OK?


>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-05 Thread Eyal Edri 
On Tue, Sep 5, 2017 at 8:11 PM, Simone Tiraboschi 
wrote:

>
>
> On Tue, Sep 5, 2017 at 6:37 PM, Simone Tiraboschi 
> wrote:
>
>>
>>
>> On Tue, Sep 5, 2017 at 3:54 PM, Evgheni Dereveanchin > > wrote:
>>
>>> Test failed: [ upgrade_engine ]
>>>
>>> Link to suspected patches:
>>> https://gerrit.ovirt.org/#/c/78307/46/
>>>
>>> Link to Job:
>>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2301/
>>> * this is failing since around job run 2291 but was masked by other
>>> errors
>>>
>>> Link to logs:
>>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-teste
>>> r/2301/artifact/exported-artifacts/upgrade-from-release-suit
>>> -master-el7/test_logs/upgrade-from-release-suite-master/
>>> post-001_upgrade_engine.py/lago-upgrade-from-release-suit
>>> e-master-engine/_var_log/ovirt-engine/setup/ovirt-engine-
>>> setup-20170905092844-6p7cux.log
>>>
>>> Error snippet from log:
>>>
>>> 
>>>
>>> 2017-09-05 09:28:45,444-0400 DEBUG 
>>> otopi.ovirt_engine_setup.engine_common.database
>>> database.execute:229 Creating own connection
>>> 2017-09-05 09:28:45,448-0400 DEBUG 
>>> otopi.ovirt_engine_setup.engine_common.database
>>> database.execute:274 Result: [{'count': 153L}]
>>> 2017-09-05 09:28:45,448-0400 DEBUG 
>>> otopi.ovirt_engine_setup.engine_common.database
>>> database.execute:224 Database: 'None', Statement: 'SHOW server_version',
>>> args: {}
>>> 2017-09-05 09:28:45,448-0400 DEBUG 
>>> otopi.ovirt_engine_setup.engine_common.database
>>> database.execute:229 Creating own connection
>>> 2017-09-05 09:28:45,452-0400 DEBUG 
>>> otopi.ovirt_engine_setup.engine_common.database
>>> database.execute:274 Result: [{'server_version': '9.2.18'}]
>>> 2017-09-05 09:28:45,452-0400 DEBUG 
>>> otopi.ovirt_engine_setup.engine_common.database
>>> database.checkServerVersion:449 PostgreSQL server version: 9.2.18
>>> 2017-09-05 09:28:45,453-0400 DEBUG 
>>> otopi.plugins.ovirt_engine_common.ovirt_engine.db.connection
>>> connection._setup:146 Existing credential use failed
>>> Traceback (most recent call last):
>>>   File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-c
>>> ommon/ovirt-engine/db/connection.py", line 141, in _setup
>>> ] = dbovirtutils.checkDBMSUpgrade()
>>>   File 
>>> "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py",
>>> line 490, in checkDBMSUpgrade
>>> self.checkClientVersion()
>>>   File 
>>> "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py",
>>> line 457, in checkClientVersion
>>> self.command.get('psql'),
>>>   File "/usr/lib/python2.7/site-packages/otopi/command.py", line 74, in
>>> get
>>> command=command
>>> RuntimeError: Command 'psql' is required but missing
>>> 2017-09-05 09:28:45,454-0400 DEBUG otopi.context
>>> context._executeMethod:142 method exception
>>> Traceback (most recent call last):
>>>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132,
>>> in _executeMethod
>>> method['method']()
>>>   File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-c
>>> ommon/ovirt-engine/db/connection.py", line 162, in _setup
>>> raise RuntimeError(msg)
>>> RuntimeError: Cannot connect to Engine database using existing
>>> credentials: engine@localhost:5432
>>> 2017-09-05 09:28:45,455-0400 ERROR otopi.context
>>> context._executeMethod:151 Failed to execute stage 'Environment setup':
>>> Cannot connect to Engine database using existing credentials:
>>> engine@localhost:5432
>>>
>>>
>> It seams that for some strange reasons the test upgrade job is not
>> installing rh-postgresql95-postgresql which should be instead required
>> as for my modification the spec file:
>> https://gerrit.ovirt.org/#/c/78307/46/ovirt-engine.spec.in@274
>>
>>
> OK, understood.
> The dependency on the postgres 9.5 client from scl was just on
> ovirt-engine and not on ovirt-engine-setup-plugin-ovirt-engine-common as
> it should be.
>
> OST upgrade test is correctly running
>   yum -y update ovirt-*setup*
> updating just engine-setup from a local repo.
>
> While I tested it instead I was updating all the rpms from my local build
> without building a local repo, that's why I didn't realized it, sorry!
>
>
> https://gerrit.ovirt.org/#/c/81476/ should address it.
>
>
>
>
>>
>> Not sure if it's just a repo sync issue or something similar:
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-teste
>> r/2301/artifact/exported-artifacts/upgrade-from-prevrelease-
>> suit-master-el7/lago_logs/lago.log
>> And, by the way, the job is also testing 4.0.6.3 -> 4.2.0-0.0 and not
>> 4.1 -> 4.2 as it should be (not sure why it's working).
>>
>>
> This is still an issue, not sure  why our code doesn't detect it.
>

I think we are testing both:
  upgrade from prev-release is testing 4.0->4.2 ( so 2 versions back )
  upgrade from release is testing 4.1->4.2 ( 1 version back )

If we shouldn't test upgrade from 4.0->4.2, or don't support it, then we
should drop

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-05 Thread Simone Tiraboschi 
On Tue, Sep 5, 2017 at 3:54 PM, Evgheni Dereveanchin 
wrote:

> Test failed: [ upgrade_engine ]
>
> Link to suspected patches:
> https://gerrit.ovirt.org/#/c/78307/46/
>
> Link to Job:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2301/
> * this is failing since around job run 2291 but was masked by other errors
>
> Link to logs:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-
> tester/2301/artifact/exported-artifacts/upgrade-from-
> release-suit-master-el7/test_logs/upgrade-from-release-
> suite-master/post-001_upgrade_engine.py/lago-upgrade-from-
> release-suite-master-engine/_var_log/ovirt-engine/setup/
> ovirt-engine-setup-20170905092844-6p7cux.log
>
> Error snippet from log:
>
> 
>
> 2017-09-05 09:28:45,444-0400 DEBUG 
> otopi.ovirt_engine_setup.engine_common.database
> database.execute:229 Creating own connection
> 2017-09-05 09:28:45,448-0400 DEBUG 
> otopi.ovirt_engine_setup.engine_common.database
> database.execute:274 Result: [{'count': 153L}]
> 2017-09-05 09:28:45,448-0400 DEBUG 
> otopi.ovirt_engine_setup.engine_common.database
> database.execute:224 Database: 'None', Statement: 'SHOW server_version',
> args: {}
> 2017-09-05 09:28:45,448-0400 DEBUG 
> otopi.ovirt_engine_setup.engine_common.database
> database.execute:229 Creating own connection
> 2017-09-05 09:28:45,452-0400 DEBUG 
> otopi.ovirt_engine_setup.engine_common.database
> database.execute:274 Result: [{'server_version': '9.2.18'}]
> 2017-09-05 09:28:45,452-0400 DEBUG 
> otopi.ovirt_engine_setup.engine_common.database
> database.checkServerVersion:449 PostgreSQL server version: 9.2.18
> 2017-09-05 09:28:45,453-0400 DEBUG otopi.plugins.ovirt_engine_
> common.ovirt_engine.db.connection connection._setup:146 Existing
> credential use failed
> Traceback (most recent call last):
>   File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-
> engine-common/ovirt-engine/db/connection.py", line 141, in _setup
> ] = dbovirtutils.checkDBMSUpgrade()
>   File 
> "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py",
> line 490, in checkDBMSUpgrade
> self.checkClientVersion()
>   File 
> "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py",
> line 457, in checkClientVersion
> self.command.get('psql'),
>   File "/usr/lib/python2.7/site-packages/otopi/command.py", line 74, in
> get
> command=command
> RuntimeError: Command 'psql' is required but missing
> 2017-09-05 09:28:45,454-0400 DEBUG otopi.context
> context._executeMethod:142 method exception
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in
> _executeMethod
> method['method']()
>   File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-
> engine-common/ovirt-engine/db/connection.py", line 162, in _setup
> raise RuntimeError(msg)
> RuntimeError: Cannot connect to Engine database using existing
> credentials: engine@localhost:5432
> 2017-09-05 09:28:45,455-0400 ERROR otopi.context
> context._executeMethod:151 Failed to execute stage 'Environment setup':
> Cannot connect to Engine database using existing credentials:
> engine@localhost:5432
>
>
It seams that for some strange reasons the test upgrade job is not
installing rh-postgresql95-postgresql which should be instead required as
for my modification the spec file:
https://gerrit.ovirt.org/#/c/78307/46/ovirt-engine.spec.in@274


Not sure if it's just a repo sync issue or something similar:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2301/artifact/exported-artifacts/upgrade-from-prevrelease-suit-master-el7/lago_logs/lago.log
And, by the way, the job is also testing 4.0.6.3 -> 4.2.0-0.0 and not 4.1
-> 4.2 as it should be (not sure why it's working).

Relevant log section:

Resolving Dependencies
--> Running transaction check
---> Package ovirt-engine-dwh-setup.noarch 0:4.0.6-1.el7.centos will be updated
---> Package ovirt-engine-dwh-setup.noarch
0:4.2.1-0.0.master.20170903090219.el7.centos will be an update
---> Package ovirt-engine-extension-aaa-ldap-setup.noarch
0:1.2.2-1.el7 will be updated
---> Package ovirt-engine-extension-aaa-ldap-setup.noarch
0:1.3.5-0.0.master.git7230cd9.el7.centos will be an update
--> Processing Dependency: ovirt-engine-extension-aaa-ldap =
1.3.5-0.0.master.git7230cd9.el7.centos for package:
ovirt-engine-extension-aaa-ldap-setup-1.3.5-0.0.master.git7230cd9.el7.centos.noarch
---> Package ovirt-engine-setup.noarch 0:4.0.6.3-1.el7.centos will be updated
---> Package ovirt-engine-setup.noarch
0:4.2.0-0.0.master.20170905115642.git4a0716e.el7.centos will be an
update
---> Package ovirt-engine-setup-base.noarch 0:4.0.6.3-1.el7.centos
will be updated
---> Package ovirt-engine-setup-base.noarch
0:4.2.0-0.0.master.20170905115642.git4a0716e.el7.centos will be an
update
--> Processing Dependency: ovirt-engine-lib >=
4.2.0-0.0.master.20170905115642.git4a0716e.el7.centos for package:

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-05 Thread Simone Tiraboschi 
On Tue, Sep 5, 2017 at 2:00 PM, Dan Kenigsberg  wrote:

> I believe that this issue is being tackled by
> https://gerrit.ovirt.org/#/c/81444/


No, the issue is on DWH setup side but we merged the related patches there
almost together.
Not sure why OST is consuming an older DWH rpm.


>
>
> On Tue, Sep 5, 2017 at 2:55 PM, Yaniv Kaul  wrote:
> > + Simone.
> > Y.
> >
> > On Tue, Sep 5, 2017 at 2:14 PM, Evgheni Dereveanchin <
> edere...@redhat.com>
> > wrote:
> >>
> >> Test failed: [ upgrade_engine ]
> >>
> >> Link to suspected patches:
> >> https://gerrit.ovirt.org/#/c/81205/9
> >>
> >> Link to Job:
> >> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2289/
> >>
> >> Link to all logs:
> >>
> >> http://jenkins.ovirt.org/job/ovirt-master_change-queue-
> tester/2289/artifact/exported-artifacts/upgrade-from-
> prevrelease-suit-master-el7/test_logs/upgrade-from-
> prevrelease-suite-master/post-001_upgrade_engine.py/lago_logs/lago.log
> >>
> >> Error snippet from log:
> >>
> >> 
> >>
> >> engine-setup --config-append=/tmp/answer-file-post --accept-defaults
> >> returned with 2
> >> output:
> >>  ***L:ERROR Internal error: type object 'DBEnvKeysConst' has no
> attribute
> >> 'NEED_DBMSUPGRADE'
> >>
> >> 
> >>
> >> ___
> >> Devel mailing list
> >> Devel@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/devel
> >
> >
> >
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-05 Thread Evgheni Dereveanchin 
Test failed: [ upgrade_engine ]

Link to suspected patches:
https://gerrit.ovirt.org/#/c/78307/46/

Link to Job:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2301/
* this is failing since around job run 2291 but was masked by other errors

Link to logs:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2301/artifact/exported-artifacts/upgrade-from-release-suit-master-el7/test_logs/upgrade-from-release-suite-master/post-001_upgrade_engine.py/lago-upgrade-from-release-suite-master-engine/_var_log/ovirt-engine/setup/ovirt-engine-setup-20170905092844-6p7cux.log

Error snippet from log:



2017-09-05 09:28:45,444-0400 DEBUG
otopi.ovirt_engine_setup.engine_common.database database.execute:229
Creating own connection
2017-09-05 09:28:45,448-0400 DEBUG
otopi.ovirt_engine_setup.engine_common.database database.execute:274
Result: [{'count': 153L}]
2017-09-05 09:28:45,448-0400 DEBUG
otopi.ovirt_engine_setup.engine_common.database database.execute:224
Database: 'None', Statement: 'SHOW server_version', args: {}
2017-09-05 09:28:45,448-0400 DEBUG
otopi.ovirt_engine_setup.engine_common.database database.execute:229
Creating own connection
2017-09-05 09:28:45,452-0400 DEBUG
otopi.ovirt_engine_setup.engine_common.database database.execute:274
Result: [{'server_version': '9.2.18'}]
2017-09-05 09:28:45,452-0400 DEBUG
otopi.ovirt_engine_setup.engine_common.database
database.checkServerVersion:449 PostgreSQL server version: 9.2.18
2017-09-05 09:28:45,453-0400 DEBUG
otopi.plugins.ovirt_engine_common.ovirt_engine.db.connection
connection._setup:146 Existing credential use failed
Traceback (most recent call last):
  File
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/ovirt-engine/db/connection.py",
line 141, in _setup
] = dbovirtutils.checkDBMSUpgrade()
  File
"/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py",
line 490, in checkDBMSUpgrade
self.checkClientVersion()
  File
"/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py",
line 457, in checkClientVersion
self.command.get('psql'),
  File "/usr/lib/python2.7/site-packages/otopi/command.py", line 74, in get
command=command
RuntimeError: Command 'psql' is required but missing
2017-09-05 09:28:45,454-0400 DEBUG otopi.context context._executeMethod:142
method exception
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in
_executeMethod
method['method']()
  File
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/ovirt-engine/db/connection.py",
line 162, in _setup
raise RuntimeError(msg)
RuntimeError: Cannot connect to Engine database using existing credentials:
engine@localhost:5432
2017-09-05 09:28:45,455-0400 ERROR otopi.context context._executeMethod:151
Failed to execute stage 'Environment setup': Cannot connect to Engine
database using existing credentials: engine@localhost:5432




-- 
Regards,
Evgheni Dereveanchin
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-05 Thread Dan Kenigsberg 
I believe that this issue is being tackled by
https://gerrit.ovirt.org/#/c/81444/

On Tue, Sep 5, 2017 at 2:55 PM, Yaniv Kaul  wrote:
> + Simone.
> Y.
>
> On Tue, Sep 5, 2017 at 2:14 PM, Evgheni Dereveanchin 
> wrote:
>>
>> Test failed: [ upgrade_engine ]
>>
>> Link to suspected patches:
>> https://gerrit.ovirt.org/#/c/81205/9
>>
>> Link to Job:
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2289/
>>
>> Link to all logs:
>>
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2289/artifact/exported-artifacts/upgrade-from-prevrelease-suit-master-el7/test_logs/upgrade-from-prevrelease-suite-master/post-001_upgrade_engine.py/lago_logs/lago.log
>>
>> Error snippet from log:
>>
>> 
>>
>> engine-setup --config-append=/tmp/answer-file-post --accept-defaults
>> returned with 2
>> output:
>>  ***L:ERROR Internal error: type object 'DBEnvKeysConst' has no attribute
>> 'NEED_DBMSUPGRADE'
>>
>> 
>>
>> ___
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-05 Thread Yaniv Kaul 
+ Simone.
Y.

On Tue, Sep 5, 2017 at 2:14 PM, Evgheni Dereveanchin 
wrote:

> Test failed: [ upgrade_engine ]
>
> Link to suspected patches:
> https://gerrit.ovirt.org/#/c/81205/9
>
> Link to Job:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2289/
>
> Link to all logs:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-
> tester/2289/artifact/exported-artifacts/upgrade-from-
> prevrelease-suit-master-el7/test_logs/upgrade-from-
> prevrelease-suite-master/post-001_upgrade_engine.py/lago_logs/lago.log
>
> Error snippet from log:
>
> 
>
> engine-setup --config-append=/tmp/answer-file-post --accept-defaults
> returned with 2
> output:
>  ***L:ERROR Internal error: type object 'DBEnvKeysConst' has no attribute
> 'NEED_DBMSUPGRADE'
>
> 
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]

2017-09-05 Thread Evgheni Dereveanchin 
Test failed: [ upgrade_engine ]

Link to suspected patches:
https://gerrit.ovirt.org/#/c/81205/9

Link to Job:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2289/

Link to all logs:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2289/artifact/exported-artifacts/upgrade-from-prevrelease-suit-master-el7/test_logs/upgrade-from-prevrelease-suite-master/post-001_upgrade_engine.py/lago_logs/lago.log

Error snippet from log:



engine-setup --config-append=/tmp/answer-file-post --accept-defaults
returned with 2
output:
 ***L:ERROR Internal error: type object 'DBEnvKeysConst' has no attribute
'NEED_DBMSUPGRADE'


___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel