[ OST Failure Report ] [ oVirt master ] [ 2017-09-05 ] [upgrade_engine]
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/... Error snippet from log: <error> 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' </error>
+ Simone. Y. On Tue, Sep 5, 2017 at 2:14 PM, Evgheni Dereveanchin <ederevea@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:
<error>
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'
</error>
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
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 <ykaul@redhat.com> wrote:
+ Simone. Y.
On Tue, Sep 5, 2017 at 2:14 PM, Evgheni Dereveanchin <ederevea@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/...
Error snippet from log:
<error>
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'
</error>
_______________________________________________ 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
On Tue, Sep 5, 2017 at 2:00 PM, Dan Kenigsberg <danken@redhat.com> 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.
+ Simone. Y.
On Tue, Sep 5, 2017 at 2:14 PM, Evgheni Dereveanchin < ederevea@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:
tester/2289/artifact/exported-artifacts/upgrade-from-
On Tue, Sep 5, 2017 at 2:55 PM, Yaniv Kaul <ykaul@redhat.com> wrote: prevrelease-suit-master-el7/test_logs/upgrade-from- prevrelease-suite-master/post-001_upgrade_engine.py/lago_logs/lago.log
Error snippet from log:
<error>
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'
</error>
_______________________________________________ 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
On 5 September 2017 at 17:59, Simone Tiraboschi <stirabos@redhat.com> wrote:
On Tue, Sep 5, 2017 at 2:00 PM, Dan Kenigsberg <danken@redhat.com> 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. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
On Wed, Sep 6, 2017 at 9:34 AM, Barak Korren <bkorren@redhat.com> wrote:
On 5 September 2017 at 17:59, Simone Tiraboschi <stirabos@redhat.com> wrote:
On Tue, Sep 5, 2017 at 2:00 PM, Dan Kenigsberg <danken@redhat.com>
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
wrote: 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
On 6 September 2017 at 10:42, Simone Tiraboschi <stirabos@redhat.com> wrote:
On Wed, Sep 6, 2017 at 9:34 AM, Barak Korren <bkorren@redhat.com> wrote:
On 5 September 2017 at 17:59, Simone Tiraboschi <stirabos@redhat.com> wrote:
On Tue, Sep 5, 2017 at 2:00 PM, Dan Kenigsberg <danken@redhat.com> 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
On Wed, Sep 6, 2017 at 9:48 AM, Barak Korren <bkorren@redhat.com> wrote:
On 6 September 2017 at 10:42, Simone Tiraboschi <stirabos@redhat.com> wrote:
On Wed, Sep 6, 2017 at 9:34 AM, Barak Korren <bkorren@redhat.com> wrote:
On 5 September 2017 at 17:59, Simone Tiraboschi <stirabos@redhat.com> wrote:
On Tue, Sep 5, 2017 at 2:00 PM, Dan Kenigsberg <danken@redhat.com> 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
patch on ovirt-engine project and another on dwh project and I don't
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
a think 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
On 6 September 2017 at 10:58, Simone Tiraboschi <stirabos@redhat.com> 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
On Wed, Sep 6, 2017 at 10:03 AM, Barak Korren <bkorren@redhat.com> wrote:
On 6 September 2017 at 10:58, Simone Tiraboschi <stirabos@redhat.com> 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
On 6 September 2017 at 11:11, Simone Tiraboschi <stirabos@redhat.com> 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-queu... Currently uploading updated packages to 'tested'. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
On Wed, Sep 6, 2017 at 10:35 AM, Barak Korren <bkorren@redhat.com> wrote:
On 6 September 2017 at 11:11, Simone Tiraboschi <stirabos@redhat.com> 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
participants (5)
-
Barak Korren -
Dan Kenigsberg -
Evgheni Dereveanchin -
Simone Tiraboschi -
Yaniv Kaul