Bug 1410709
| Summary: | [GSS] [RFE] remove firewalld from nfs-ganesha dependency in RHGS -RHEL 7 | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Riyas Abdulrasak <rnalakka> |
| Component: | nfs-ganesha | Assignee: | Kaleb KEITHLEY <kkeithle> |
| Status: | CLOSED ERRATA | QA Contact: | surabhi <sbhaloth> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.1 | CC: | abhishku, amukherj, asrivast, bkunal, bmohanra, bsrirama, jthottan, msaini, mzink, rcyriac, rhinduja, rhs-bugs, rnalakka, skoduri, storage-qa-internal |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | RHGS 3.3.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | nfs-ganesha-2.4.4-4 | Doc Type: | Enhancement |
| Doc Text: |
With this release, the dependency over firewalld is removed and NFS-Ganesha can be installed with ease without installing firewalld.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-09-21 04:47:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1369781, 1417138, 1417145 | ||
|
Description
Riyas Abdulrasak
2017-01-06 07:17:12 UTC
Thats right. We had a requirement to open up necessary ports required for nfs-ganesha (&side-band protocols) to function properly in firewalld (bug1245103). As part of those changes this dependency got created. In case if firewalld is installed at the time of installing nfs-ganesha, it shall create this dependency (thats because as mentioned by Byreddy above, few service files get installed) and I am not sure if it can be avoided. However does installing nfs-ganesha package fail when firewalld is not installed on the system? If that is the case, we can fix it by checking if firewalld is installed on the system instead of assuming it is available for >=rhel7 systems. What about moving rquota.xml firewalld service file nfs-ganesha-firewalld package and remove it from nfs-ganesha? (Use case: We are still using iptables-services instead of firewalld due to existing configuration management. We don't want to have both installed to avoid conflicts.) We should install the files. If firewalld is installed, they will be used. Requiring firewalld may have been overkill. I believe we can remove it and assume that if it is there, the rquota.xml, etc., files will be used. FYI, we don't support iptables-service in RHEL7 so the customer and/or GSS is skating on thin ice. ;-) Verified on the build nfs-ganesha-2.4.4-4. The dependency of firewalld has been removed and now yum deplist for nfs-ganesha does not list firewalld. Also removing firewalld doesn't remove nfs-ganesha packages. Marking the BZ verified. yum deplist nfs-ganesha | grep firewalld [root@dhcp46-132 yum.repos.d]# yum remove firewalld Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager Resolving Dependencies --> Running transaction check ---> Package firewalld.noarch 0:0.4.3.2-8.1.el7_3.2 will be erased --> Finished Dependency Resolution Dependencies Resolved ======================================================================================================================================================================== Package Arch Version Repository Size ======================================================================================================================================================================== Removing: firewalld noarch 0.4.3.2-8.1.el7_3.2 installed 1.7 M Transaction Summary ======================================================================================================================================================================== Remove 1 Package Installed size: 1.7 M Is this ok [y/N]: Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2779 |