action #25610
closed[sle][functional][opensuse][u][medium] postgresql96server is hard to investigate on errors / should be enabled on openSUSE
Added by okurz over 6 years ago. Updated almost 6 years ago.
0%
Description
Observation¶
openQA test in scenario sle-15-Leanos-DVD-x86_64-minimal+base@64bit fails in
postgresql96server
with a not so helpful error output. I checked manually and the substate is "exited" instead of running so I created https://bugzilla.suse.com/show_bug.cgi?id=1060639 but I think the output can be improved.
Suggestions¶
- add for openSUSE tests as well
- output the details for crosschecking and don't just be silent if the grep does not match
Further details¶
Always latest result in this scenario: latest
Updated by okurz over 6 years ago
- Assignee set to osukup
@osukup: you are the test module maintainer, do you want to do it? otherwise please unassign again
Updated by osukup over 6 years ago
it looks as product bug, on SLE12-Sp3 with almost same version no problem shown ...
maybe try port to systemctl. and use more verbose calls.
for logs suggested by rmax we need extend postfailhook ..
Updated by emiura over 6 years ago
By the comments on https://bugzilla.suse.com/show_bug.cgi?id=1060639&GoAheadAndLogIn=1, a version that fixes the "SubState=exited" issue was not released yet (tumbleweed)
Updated by emiura over 6 years ago
Seems like the package name changed as well (postgresql10)
Updated by okurz over 6 years ago
Yes. I think for the high-level openQA tests we should not carry around the version numbers of specific packages in the test module names at least. I suggest to just call the test modules like "postgresql_server.pm" and such.
Updated by emiura over 6 years ago
- Status changed from New to In Progress
After some trials and errors, I did put this code in to the test,
assert_script_run 'systemctl show -p ActiveState postgresql.service | grep ActiveState=active || systemctl status postgresql.service';
Updated by okurz about 6 years ago
- Due date set to 2018-03-27
- Target version changed from Milestone 13 to Milestone 14
Hi emiura, any progress on this? Did you create a pull request for the code? Would you like to keep this ticket or unassign?
Updated by emiura about 6 years ago
okurz wrote:
Hi emiura, any progress on this? Did you create a pull request for the code? Would you like to keep this ticket or unassign?
Hello Okurz. Yes. I did create a pull request: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4030. Is there a standard procedure when someone places a PR?
Updated by okurz about 6 years ago
I see. Well, you are doing the right thing by just mentioning the PR so people can take a look there on what's going on :) Other than this the wiki also describes a bit of process and how we commonly handle tickets. Thanks for your PR.
Updated by okurz about 6 years ago
- Blocked by action #27014: [opensuse][functional][u][easy] Add postgresql_server to openSUSE tests (was: Add postgresql96server to openSUSE tests) added
Updated by okurz about 6 years ago
- Due date changed from 2018-03-27 to 2018-04-10
- Target version changed from Milestone 14 to Milestone 15
Updated by okurz about 6 years ago
- Subject changed from [sle][functional][qam][opensuse] postgresql96server is hard to investigate on errors / should be enabled on openSUSE to [sle][functional][qam][opensuse][u] postgresql96server is hard to investigate on errors / should be enabled on openSUSE
Updated by emiura about 6 years ago
- Status changed from In Progress to Feedback
Log collecting already implemented (by someone else).
Updated by mgriessmeier about 6 years ago
- Due date changed from 2018-04-10 to 2018-04-24
Updated by mgriessmeier about 6 years ago
- Due date changed from 2018-04-24 to 2018-05-08
- Target version changed from Milestone 15 to Milestone 16
emiura wrote:
Log collecting already implemented (by someone else).
so can we close this one?
do you have a reference for this?
Updated by emiura about 6 years ago
mgriessmeier wrote:
emiura wrote:
Log collecting already implemented (by someone else).
so can we close this one?
do you have a reference for this?
Yes, I think that it can be closed.
Okurz suggested to add a post_fail_hook. Since I looked at this ticket only later, someone already implemented it on the postgresql test.
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4030
Updated by okurz about 6 years ago
Nope, can not be closed. The log collection was done with
commit b7516099 (okurz/feature/postgres, lord/feature/postgres)
Author: Oliver Kurz okurz@suse.de
Date: Thu Sep 28 16:25:33 2017 +0200
Provide more postgres logs on fail (bsc#1060639)
Verification run: http://lord.arch/tests/511
so what is missing is adding the test to openSUSE.
@emiura if you would like to do that, this would be appreciated, else feel free to unassign and we will try to do that.
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional][qam][opensuse][u] postgresql96server is hard to investigate on errors / should be enabled on openSUSE to [sle][functional][opensuse][u] postgresql96server is hard to investigate on errors / should be enabled on openSUSE
- Category changed from Enhancement to existing tests to New test
- Status changed from Feedback to Workable
ok, fine. So we should do it then: Add corresponding tests to o3
Updated by mgriessmeier almost 6 years ago
- Due date changed from 2018-05-08 to 2018-05-22
Updated by riafarov almost 6 years ago
- Subject changed from [sle][functional][opensuse][u] postgresql96server is hard to investigate on errors / should be enabled on openSUSE to [sle][functional][opensuse][u][medium] postgresql96server is hard to investigate on errors / should be enabled on openSUSE
Updated by SLindoMansilla almost 6 years ago
- Status changed from Workable to In Progress
- Assignee set to SLindoMansilla
Updated by SLindoMansilla almost 6 years ago
- Status changed from In Progress to Resolved
Blocker resolved.
Module postgresql_server enabled for openSUSE.