action #35745
closed[sle][functional][y][bsc#1083487] - Use static port configuration for NIS/NFS instead of disabling firewalld in MM nfs client/server test suites
0%
Description
Description¶
According to bsc#1083487 yast2 configuration part for nis-server shows "Some firewalld services are not available" firewalld does not support dynamically allocated ports by rpcbind, which affects NIS & NFS configuration.
We already disable firewalld, to solve this, but there is more secure solution we could apply by configuring static ports for NIS/NFS server/client
Acceptance criteria¶
- Firewalld is not turned of for MM NIS/NFS test suites
- Service uses configuration with static ports
Suggestions¶
- read about rpc.idmapd (8) - NFSv4 ID <-> Name Mapper, rpc.mountd (8) - NFS mount daemon, rpc.nfsd (8) - NFS server process, rpc.statd (8) - NSM service daemon, ypserv (8) - NIS Server
- update /etc/sysconfig/nfs & /etc/sysconfig/ypserv accordingly
Inspiration
https://www.systutorials.com/39625/fixing-ports-used-by-nfs-server/
Updated by mloviska almost 6 years ago
- Related to action #23822: [sle][functional][y][bsc#1073281][easy] new needles and workaround is needed by test module nis_server added
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional][y][bsc#1083487 ] - NIS/NFS workaround to [sle][functional][y][bsc#1083487] - NIS/NFS workaround
- Description updated (diff)
- Category set to New test
- Target version set to Milestone 19
Sorry, these are not acceptance criteria, rather suggestions. I'm not even sure what the ACs are. I am curious, why did you create this issue, just after reading the bug or were you approached by someone else? So far I would not consider this of high importance but if someone sees a higher need then I am happy to re-evaluate.
Updated by mloviska almost 6 years ago
I am considering this ticket as future enhancement for MM nis_client/server test. As there is the known issue with firewalld that it does not support dynamically allocated ports by rpcbind/portmapper we should adjust our test case accordingly. I do not feel we can exclude this scenario since majority of our distros are moving toward firewalld and there is a hight chance that customer will face this issue as well. Basically it is an reminder for me or anyone else who is interested in how to configure static ports for nis/nfs service. It is completely fine to keep this ticket with normal prio. However I do not see a problem to include this ticket in upcoming sprints.
Updated by okurz almost 6 years ago
- Target version changed from Milestone 19 to Milestone 19
Updated by riafarov over 5 years ago
- Subject changed from [sle][functional][y][bsc#1083487] - NIS/NFS workaround to [sle][functional][y][bsc#1083487] - Use static port configuration for NIS/NFS instead of disabling firewalld in MM nfs client/server test suites
- Description updated (diff)
- Status changed from New to Workable
Updated by okurz over 5 years ago
- Target version changed from Milestone 19 to future
Updated by riafarov over 3 years ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
New test)
Updated by okurz over 2 years ago
- Priority changed from Normal to Low
This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. The ticket will be set to the next lower priority of "Low" as discussed with qe-yast PO oorlov (https://suse.slack.com/archives/C02LECV2R0X/p1636974668013200)