Project

General

Profile

Actions

action #73423

closed

[qe-core][functional] test fails in vsftpd - Investigate why test suite is failing

Added by szarate over 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-10-15
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

Fails on all backends: https://openqa.suse.de/tests/overview?arch=&machine=&modules=vsftpd&distri=sle&version=15-SP3&build=57.4&groupid=110

openQA test in scenario sle-15-SP3-Online-x86_64-extra_tests_textmode@svirt-xen-pv fails in
vsftpd

Test suite description

Maintainer: asmorodskyi,okurz,dheidler. Mainly console extratest

Reproducible

Fails since (at least) Build 43.1

Expected result

Last good: 36.5 (or more recent)

Further details

Always latest result in this scenario: latest


Files

Actions #1

Updated by szarate over 3 years ago

  • Status changed from New to Feedback
  • Assignee set to szarate
  • Priority changed from Urgent to Normal

Didn't seem to happen anymore on last build, to monitor just in case it happens again.

Actions #2

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from [functional][u] test fails in vsftpd - Investigate why test suite is failing to [qe-core][functional] test fails in vsftpd - Investigate why test suite is failing
Actions #3

Updated by dzedro over 3 years ago

There is something wrong with vsftpd or something with configuration which does work on previous versions.
I would open bug or ask maintainer about the error.

Actions #5

Updated by okurz over 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode
https://openqa.suse.de/tests/5066305

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #6

Updated by SLindoMansilla over 3 years ago

  • Assignee changed from szarate to SLindoMansilla

As agreed in the daily, taking over investigation and bug report

Actions #7

Updated by okurz over 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode
https://openqa.suse.de/tests/5162919

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #8

Updated by okurz about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode
https://openqa.suse.de/tests/5212016

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #9

Updated by okurz about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode
https://openqa.suse.de/tests/5247626

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #10

Updated by okurz about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode
https://openqa.suse.de/tests/5338159

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #11

Updated by SLindoMansilla about 3 years ago

  • Status changed from Feedback to In Progress
Actions #12

Updated by SLindoMansilla about 3 years ago

Failure identified as product bug.

ftp client shows ls: Fatal error: 500 OOPS: not a normal exit in vsf_sysutil_wait_get_exitcode

journalctl shows

Jan 27 16:41:56 susetest systemd[1]: Started Process Core Dump (PID 8041/UID 0).
Jan 27 16:41:56 susetest systemd-coredump[8042]: Process 8040 (vsftpd) of user 1002 dumped core.

                                                 Stack trace of thread 8040:
                                                 #0  0x00007f79d1bf1887 getdents64 (libc.so.6 + 0xc7887)
                                                 #1  0x00007f79d1bf1935 readdir (libc.so.6 + 0xc7935)
                                                 #2  0x0000560e8c3907c9 n/a (vsftpd + 0x167c9)
                                                 #3  0x0000560e8c3899a1 n/a (vsftpd + 0xf9a1)
                                                 #4  0x0000560e8c386d0b n/a (vsftpd + 0xcd0b)
                                                 #5  0x0000560e8c385698 n/a (vsftpd + 0xb698)
                                                 #6  0x0000560e8c3820ad n/a (vsftpd + 0x80ad)
                                                 #7  0x0000560e8c384094 n/a (vsftpd + 0xa094)
                                                 #8  0x0000560e8c38b0dc n/a (vsftpd + 0x110dc)
                                                 #9  0x0000560e8c38b4ed n/a (vsftpd + 0x114ed)
                                                 #10 0x0000560e8c37fee6 n/a (vsftpd + 0x5ee6)
                                                 #11 0x00007f79d1b4f34d __libc_start_main (libc.so.6 + 0x2534d)
                                                 #12 0x0000560e8c3801ea n/a (vsftpd + 0x61ea)
Jan 27 16:41:56 susetest systemd[1]: systemd-coredump@50-8041-0.service: Succeeded.

Apart from that, there is a test bug in client/bin/04_NOSSL_listdirs_valid_users.sh from data/qam/vsftpd/vsftpd.tar.gz which causes false negatives.

- diff /tmp/sshoutput /tmp/sshoutput
+ diff /tmp/ftpoutput /tmp/sshoutput
Actions #15

Updated by SLindoMansilla about 3 years ago

Test suite comes from old SLEnkins: https://gitlab.suse.de/SLEnkins/tests-vsftpd

slenkins had to use 3 nodes.
When tests-vsftpd was integrated in openQA, the control node was droped and was executed in form of Multi-Machine test.
Later the MM was dropped and vsftpd was just client/server single test.

Actions #16

Updated by SLindoMansilla about 3 years ago

  • Status changed from In Progress to Resolved
Actions #17

Updated by szarate about 3 years ago

FYI: sudo tar --preserve-permissions --same-owner -xzvf /home/sergio/github/os-autoinst_os-autoinst-distri-opensuse/data/qam/vsftpd.tar.gz

Actions #18

Updated by okurz about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode@svirt-xen-hvm
https://openqa.suse.de/tests/5476713

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #19

Updated by okurz about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode@svirt-xen-pv
https://openqa.suse.de/tests/5662190

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #20

Updated by okurz about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode@svirt-xen-pv
https://openqa.suse.de/tests/5662190

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #21

Updated by openqa_review about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode@svirt-xen-pv
https://openqa.suse.de/tests/5670543

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #22

Updated by okurz almost 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_textmode@svirt-xen-pv
https://openqa.suse.de/tests/5784080

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions

Also available in: Atom PDF