aws / aws/aws-parallelcluster

NFS - Disable V2 and V3

Open
#6,622 1 comment 0 reactions 0 assignees View on GitHub
3.x Backlog Feature Request
Dominant language
Python
Stars
888
Forks
314
Avg merge
1d 10h
Merged PRs (30d)
43

Description

**Required Info:**
- AWS ParallelCluster version [e.g. 3.1.1]: 3.11.1

CIS security controls would like to have rpcbind.service and rpcbind.socket disabled/masked. The build-image requires a start of rpcbind which as I understand is only required for NFS2 and 3. Is it possible to not make this a requirement?

Error -
Expected process to exit with [0], but received '1'
Stdout: ---- Begin output of ["/usr/bin/systemctl", "--system", "start", "rpc-statd.service"] ----
Stdout: STDOUT:
Stdout: STDERR: Failed to start rpc-statd.service: Unit rpcbind.socket is masked.
Stdout: ---- End output of ["/usr/bin/systemctl", "--system", "start", "rpc-statd.service"] ----
Stdout: Ran ["/usr/bin/systemctl", "--system", "start", "rpc-statd.service"] returned 1

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start at the build-image path that invokes systemctl to start rpc-statd.service, and inspect how rpcbind.service and rpcbind.socket are required; reproduce the failure with rpcbind.socket masked. Done means the requested NFS V2/V3 behavior and the masked-service case are handled without the reported exit-1 failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, linux
Domain
infrastructure, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.