Project

General

Profile

action #57215

[functional][u] test fails in sssd - Failed to start SSSD

Added by SLindoMansilla almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 28
Start date:
2019-09-23
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

../junit.sh failure -T 'Failed to start SSSD'

No logs. We need to investigate if this is a product bug.

Acceptance criteria

  • AC1: The module sssd uploads logs on failure.
  • AC2: The modules passes or soft-fail in a product bug.

Suggestions

For manual debugging, use root-console instead of serial console, then use developer mode to manually reproduce the issue and get logs.

Reproducible

  • In scenario sle-12-SP5-Server-DVD-aarch64-extra_tests_in_textmode@aarch64
  • Fails since Build 0322
  • Current occurrence: 0330

Expected result

Last good: 0319

Further details

Always latest result:


Related issues

Related to openQA Tests - action #58196: [functional][u] test fails in sssd: 'zypper -n in psmisc' failed with code 106 (ZYPPER_EXIT_INF_REPOS_SKIPPED)Rejected2019-10-15

Related to openQA Tests - action #55115: [qe-core][functional] test fails in sssd - Test fails switching to serial terminalResolved2019-08-05

Related to openQA Tests - action #13168: [qe-core][opensuse][sle][functional] Sudo and LDAP/SSSD for sudoersWorkable5000-01-01

Related to openQA Tests - action #57290: [qe-core][functional] Move module specific test modules from extra_tests_* scenarios to its respective scenarioResolved2019-09-19

History

#1 Updated by SLindoMansilla almost 3 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Target version set to Milestone 28
  • Estimated time set to 42.00 h

#2 Updated by okurz over 2 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_package_hub
https://openqa.suse.de/tests/3453775

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

#3 Updated by maritawerner over 2 years ago

What is the status here? We are almost at GMC? Can we get that fixed?

#4 Updated by SLindoMansilla over 2 years ago

  • Related to action #58196: [functional][u] test fails in sssd: 'zypper -n in psmisc' failed with code 106 (ZYPPER_EXIT_INF_REPOS_SKIPPED) added

#5 Updated by SLindoMansilla over 2 years ago

  • Related to action #55115: [qe-core][functional] test fails in sssd - Test fails switching to serial terminal added

#6 Updated by SLindoMansilla over 2 years ago

  • Related to action #13168: [qe-core][opensuse][sle][functional] Sudo and LDAP/SSSD for sudoers added

#7 Updated by SLindoMansilla over 2 years ago

The module maintainer will not continue maintaining. We need to learn how it works and find someone who can be the maintainer.

#8 Updated by SLindoMansilla over 2 years ago

  • Priority changed from High to Urgent

#9 Updated by SLindoMansilla over 2 years ago

  • Related to action #57290: [qe-core][functional] Move module specific test modules from extra_tests_* scenarios to its respective scenario added

#10 Updated by SLindoMansilla over 2 years ago

  • Description updated (diff)

New test suite dedicated for packages coming from package-hub module: extra_tests_package_hub

#11 Updated by okurz over 2 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_package_hub
https://openqa.suse.de/tests/3507946

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

#12 Updated by szarate over 2 years ago

  • Assignee set to szarate

#13 Updated by szarate over 2 years ago

  • Status changed from Workable to Resolved

#14 Updated by SLindoMansilla over 2 years ago

  • Priority changed from Urgent to High

#15 Updated by okurz over 2 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_in_textmode
https://openqa.suse.de/tests/3576653

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

Also available in: Atom PDF