action #41231
closed[kernel][fate:ready][important][fate#325872] write resolv.conf to /run instead of /etc (for network manager and wicked)
0%
Description
Description (copied from fate)¶
following up on the discussion on the Factory list it looks like other network managing implementations switched to writing the resolv.conf to /run and leave
/etc/resolv.conf as symlink. /etc nowadays moves towards not having programs automatically update it but leave that to the admin. So I think it would make sense for netconfig to follow and use /run too.
Likely impacts YaST which needs to be able to deal with this
See https://fate.suse.com/325872
Acceptance criteria¶
- Manual testing is performed
- Existing tests are adjusted to use new structure
- Automated check is considered and implemented as part of this ticket if trivial, or follow-up task is created
Updated by okurz over 5 years ago
- Subject changed from [functional][y][fate#325872] write resolv.conf to /run instead of /etc (for network manager and wicked) to [kernel][fate:ready][important][fate#325872] write resolv.conf to /run instead of /etc (for network manager and wicked)
- Category set to New test
It's an "important" feature but not "mandatory" but I agree it makes sense to look into this. For now as discussed with @sebchlad putting to the QSK team's backlog. We can split subtickets out from there.
"sebchlad" is already "QA reviewer" on the fate.
Updated by jlausuch over 4 years ago
can we close this?
I see the Jira Fate marked as DONE
https://jira.suse.com/browse/SLE-4599
Updated by asmorodskyi over 4 years ago
- Status changed from In Progress to Resolved
Feature was implemented quite some time ago . Only concern is acceptance criteria defined by Rodion. first two points giving strong yes, but 3d one - as far as I can tell there is no explicit automated check implemented. I still put it to Resolved because I don't such need but fell free to reopen if you think that we need such explicit check ...