action #35401
closed
[functional][sle][u] dns_srv: Improve test coverage by changing deprecated 'hostname' with 'dig'
Added by SLindoMansilla about 6 years ago.
Updated about 4 years ago.
Description
Motivation¶
"dns_srv" is failing on bsc#1064438 where the bug assignee is very responsive but it is not clear if the test case even is valid. As many s390x tests fail on dns_srv and can not progress further and we have less failures on other test modules for SLE15 now we should make sure tests do not fail on "dns_srv" anymore.
Acceptance criteria¶
- AC: The module dns_srv uses dig instead of hostname.
Tasks¶
- Implement suggestions mentioned in bsc#1064438
Further information¶
- Related to action #34990: [functional][sle][u][fast] Add workaround for bsc#1064438 - "openQA test fails in dns_srv - "bind" cannot resolve localhost after installation" added
Suggestions from: https://bugzilla.suse.com/show_bug.cgi?id=1064438#c28
We could improve this test by:
1: Use dig instead of host (host is deprecated anyway)
2: Supply the IP (v6 _and_ v4) explicitly while resolving the request (this avoids the first resolving over /etc/hosts)
3: Run "dig localhost @localhost" in a third step to also test this weird, chained resolving
- Subject changed from [functional][sle] Improve test coverage by changing deprecated 'hostname' with 'dig' to [functional][sle] dns_srv: Improve test coverage by changing deprecated 'hostname' with 'dig'
- Description updated (diff)
- Status changed from New to Workable
- Subject changed from [functional][sle] dns_srv: Improve test coverage by changing deprecated 'hostname' with 'dig' to [functional][sle][u] dns_srv: Improve test coverage by changing deprecated 'hostname' with 'dig'
- Due date changed from 2018-05-08 to 2018-06-05
- Target version set to Milestone 16
ok, the idea makes sense but I do not think we have that capacity right now. Let's try in S18
- Due date deleted (
2018-06-05)
- Target version changed from Milestone 16 to future
Honestly I think we have better things to do at current times and I do not see a reason to replace working tool as long as the command itself does not report as deprecated or is not available to us anymore.
- Target version changed from future to future
- Status changed from Workable to New
Bulk action to set status back to "New" for older tickets which are in "future". They would need to be revisited in time when we come up with a defined plan and assign to a milestone.
- Priority changed from Normal to Low
let's focus more on improving our current tests and workflows first. Putting to "holding tank" :)
- Status changed from New to Rejected
not failing for a long time
Also available in: Atom
PDF