action #27457
closed
coordination #27074: [sle][functional][epic][sle15][opensuse][y] Update yast2 ui (gui & ncurses) tests for SLE15 and Leap 15
[sle][functional][sle15][bsc#1072808][y][yast][medium] yast2 samba-server - create new workflow because of product change
Added by zluo about 7 years ago.
Updated over 6 years ago.
Category:
Bugs in existing tests
Description
Motivation¶
from sle 15 we have samba server which doesn't provide server role page anymore.
So this change is quite big and it requires a new workflow for samba-server.
We still need to keep current workflow to make sure that tests for sle 12 and current TW are not going to fail.
Blocked by bsc#1072808 although I feel we could still move forward and adjust the current test workflow.
Suggestions¶
- Target version set to Milestone 12
- Subject changed from [sle][functional][sle15] yast2 samba-server - create new workflow because of product change to [sle][functional][sle15][bsc#1072808] yast2 samba-server - create new workflow because of product change
- Status changed from New to Blocked
- Assignee set to okurz
- Target version changed from Milestone 12 to Milestone 14
- Due date set to 2018-03-13
No movement in bug since 2017-12, asked back.
- Description updated (diff)
- Due date deleted (
2018-03-13)
- Target version changed from Milestone 14 to Milestone 15
- Subject changed from [sle][functional][sle15][bsc#1072808] yast2 samba-server - create new workflow because of product change to [sle][functional][medium][sle15][bsc#1072808][y][yast] yast2 samba-server - create new workflow because of product change
- Description updated (diff)
- Due date set to 2018-04-10
- Category changed from Enhancement to existing tests to Bugs in existing tests
- Status changed from Blocked to Workable
- Assignee deleted (
okurz)
- Status changed from Workable to Blocked
- Assignee set to okurz
- Has duplicate action #30064: [sle][functional][blocked][bsc#1072808]test fails in yast2_samba added
- Status changed from Blocked to Workable
- Assignee deleted (
okurz)
- Priority changed from Normal to High
@riafarov I think you misunderstood my last change in #27457#note-5 . I mentioned the bug and we can continue with the necessary test adaption now even though the bug is/was open. But to make that more clear I did set the bug to RESOLVED FIXED. We can now adapt the test accordingly.
- Parent task set to #27074
- Subject changed from [sle][functional][medium][sle15][bsc#1072808][y][yast] yast2 samba-server - create new workflow because of product change to [sle][functional][medium][sle15][bsc#1072808][y][yast][medium] yast2 samba-server - create new workflow because of product change
- Has duplicate action #34009: Failure in yast2_samba: yast2 auth-server no longer exists added
- Status changed from Workable to In Progress
- Subject changed from [sle][functional][medium][sle15][bsc#1072808][y][yast][medium] yast2 samba-server - create new workflow because of product change to [sle][functional][sle15][bsc#1072808][y][yast][medium] yast2 samba-server - create new workflow because of product change
- Due date changed from 2018-04-10 to 2018-04-24
- Status changed from In Progress to Feedback
- Due date changed from 2018-04-24 to 2018-05-08
- Target version changed from Milestone 15 to Milestone 16
- Status changed from Feedback to In Progress
Please regard this with high priority as is marked in the ticket priority field. I assume either the work is actually in progress or you are waiting for something where we could help with. OR can we actually merge the PR as is and see an improvement in tests on production already?
I am waiting for Zsolt's response on my last mail. There is still a problem to load properly pcks12 certificate store on my side. He has already confirmed that steps to create CA & server key/certificate are correct and are working for him. I have sent him my files to check, whether he has the same problem to setup ldap as I do.
- Due date changed from 2018-05-08 to 2018-05-22
Martin, is it blocked? How can we proceed here?
Not blocked, just working on the PR.
Currently I am done with the PR atm.
PR merged, tests retriggered, waiting for execution:
But subsequent test module yast2_hostname failed because of the change in the domain name, created needle and retriggered:
- tw, obsoleted by new TW build, new job tw
- leap15 -> ok
- Status changed from In Progress to Resolved
Also available in: Atom
PDF