openSUSE Project Management Tool

2021-09-24

03:37 openQA Project action #98664: Hiding test data

okurz wrote:
> > However, the value of LTSS_PRODUCTS_CODES is quite lengthy string. It looks wired and ugly. That is...

2021-09-17

05:23 openQA Project action #98664: Hiding test data

The simplest workaround I have thought of is to create one single VAR, like:
LTSS_PRODUCTS_CODES="15.1,INTERNAL-USE-...

2021-09-16

06:51 openQA Project action #98664: Hiding test data

Hello,
Let me clearly it a bit more.
I have a test data, a hash which have some scc code for internal test:
$l...

2021-09-15

09:44 openQA Project action #98664 (Resolved): Hiding test data

The virtualization test sometimes need to create several guest VMs in a openQA job. They have different sles versions...

2021-07-19

05:56 openQA Tests action #89479: [qe-core] test fails in sssd - Fix sssd testing with openldap, remove use of python-pam

The failed sssd test was already removed off job schedule a while ago. The two new sssd functional tests take it's pl...

2021-06-11

09:43 openQA Tests action #89479: [qe-core] test fails in sssd - Fix sssd testing with openldap, remove use of python-pam

Can we close this ticket?

2021-06-03

06:02 openQA Tests action #89479: [qe-core] test fails in sssd - Fix sssd testing with openldap, remove use of python-pam

Opensuse TW aarch: https://openqa.opensuse.org/tests/1765683

2021-06-02

03:44 openQA Tests action #89479: [qe-core] test fails in sssd - Fix sssd testing with openldap, remove use of python-pam

Will openldap be removed off sle15sp4?
If openldap remain in sle15sp4 we can run both openldap_sssd and 389_ds sss...

2021-06-01

08:04 openQA Tests action #89479: [qe-core] test fails in sssd - Fix sssd testing with openldap, remove use of python-pam

sssd tests are already running in OSD.
12sp5 : https://openqa.suse.de/tests/overview?distri=sle&version=12-SP5&build...

2021-05-27

09:47 openQA Tests action #89479: [qe-core] test fails in sssd - Fix sssd testing with openldap, remove use of python-pam

coolgw wrote:
> Before close this ticket.
> I have some questions on the requirement of this ticket since we will ...