action #12874
closed
coordination #9486: [sle][opensuse][functional][epic][y]Network Installations
[tools][sle][functional][u] Extend Installation over smb functionality for openSUSE and add samba server setup to salt recipes
Added by okurz over 8 years ago.
Updated about 6 years ago.
Target version:
SUSE QA (private) - Milestone 18
Description
motivation¶
we have manual tests to cover smb but we should be able to automate this when we distribute assets over SMB
ideas¶
- Project changed from openQA Project (public) to openQA Tests (public)
- Category changed from 168 to Infrastructure
- Status changed from New to In Progress
- Assignee set to mgriessmeier
- Parent task set to #9486
@mgriessmeier: you tried saltification of samba server install, didn't you?
mgriessmeier wrote:
TODO: Salting all the samba stuff for o.s.d and o3
are you?
- Subject changed from Add samba server to osd to test installation over smb to [sles][functional][tools] Extend Installation over smb functionality for openSUSE and add samba server setup to salt recipes
- Assignee deleted (
mgriessmeier)
not working on that, don't know if it's still necessary - smb tests currently running are working fine.
probably someone have to look again if new smb tests are introduced
- Subject changed from [sles][functional][tools] Extend Installation over smb functionality for openSUSE and add samba server setup to salt recipes to [tools] Extend Installation over smb functionality for openSUSE and add samba server setup to salt recipes
Removing from QA SLE Functional backlog as of now.
- Subject changed from [tools] Extend Installation over smb functionality for openSUSE and add samba server setup to salt recipes to [tools][sle][functional] Extend Installation over smb functionality for openSUSE and add samba server setup to salt recipes
Well, we shouldn't because it's a subticket of an epic which is part of "[sle][functional]". The QA SLE functional does not have to do it when e.g. someone from "[tools]" does it but eventually I see it as necessary for us so we can delay it, set it to feedback, wait for others but not make it disappear from our backlog.
- Target version set to Milestone 13
- Status changed from In Progress to Workable
- Target version changed from Milestone 13 to Milestone 15
- Due date set to 2018-04-24
- Subject changed from [tools][sle][functional] Extend Installation over smb functionality for openSUSE and add samba server setup to salt recipes to [tools][sle][functional][u] Extend Installation over smb functionality for openSUSE and add samba server setup to salt recipes
- Due date deleted (
2018-04-24)
- Target version changed from Milestone 15 to Milestone 18
no capacity for S14-S17, delaying
- Target version changed from Milestone 18 to Milestone 18
- Status changed from Workable to Rejected
- Assignee set to okurz
let's leave it like it is. For now we just can not assure o3 to show the same coverage as osd which should be fine. o3 is lacking in administration and e.g. salt-recipes and it does not look like we are moving there anywhere close.
Also available in: Atom
PDF