fix: nfs client check, updated RFS

[stafaniasaju]

• RFS changes reimplemented
• bug fix for NFS client check. Now checks explicitly on RHEL and SLES

[surajsbharadwaj]

Can you please make the following changes ?

1. Include prefix for sap_hana_preconfigure, sap_netweaver_preconfigure, sap_general_preconfigure ::::

should be redhat.sap_install.sap_general_preconfigure
....
.


ansible-power-linux-sap/roles/powervs_configure_os_for_sap/tasks/rhel_saptune.yml

Line 9 in ff0055d

name: sap_hana_preconfigure

2. Remove #no-fcqdn [name]. For lvg, vgs etc use community.general (sync with @ludwig)
3. RFS :
1. - name: Update rps_sock_flow_entries runtime value ?? Why should this be performed when reloading it later ?
2. Create custom systemd unit for RFS configuration ? Should happen if it doesn’t exit. Idempotent must be respected

[stafaniasaju]

Can you please make the following changes ?

1. Include prefix for sap_hana_preconfigure, sap_netweaver_preconfigure, sap_general_preconfigure ::::

should be redhat.sap_install.sap_general_preconfigure .... .


ansible-power-linux-sap/roles/powervs_configure_os_for_sap/tasks/rhel_saptune.yml

Line 9 in ff0055d

name: sap_hana_preconfigure

2. Remove #no-fcqdn [name]. For lvg, vgs etc use community.general (sync with @ludwig)
3. RFS :
4. • name: Update rps_sock_flow_entries runtime value ?? Why should this be performed when reloading it later ?
5. Create custom systemd unit for RFS configuration ? Should happen if it doesn’t exit. Idempotent must be respected

The rfs-config.service is a custom service, not a standard one. It is explicitly defined in the playbook to handle a specialized task: dynamically configuring rps_flow_cnt for network interface queues, which cannot be directly persisted via traditional mechanisms like sysctl. After considering few options to modify sysfs file, I think using a systemd service is a good option to persist changes.
Necessary changes implemented for all other comments.
Will resolve the pipeline run failure with Sahitya.