Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debian - Nobody-Group idmapd issue #88

Closed
jurim76 opened this issue Oct 8, 2018 · 3 comments
Closed

Debian - Nobody-Group idmapd issue #88

jurim76 opened this issue Oct 8, 2018 · 3 comments

Comments

@jurim76
Copy link

jurim76 commented Oct 8, 2018

By default Nobody-Group for idmapd service is "nobody" group , but in Debian user nobody belongs to "nogroup" group and service is refused to start under "nobody:nobody".
If define options in puppet, for example
class { '::nfs':
client_idmapd_setting => [ 'Nobody-User=nobody', 'Nobody-Group=nogroup' ]
}
and got error
Error: /Stage[main]/Nfs::Client::Config/Augeas[/etc/default/nfs-common]: Could not evaluate: Unknown command Nobody
Notice: /Stage[main]/Nfs::Client/Anchor[nfs::client::end]: Dependency Augeas[/etc/default/nfs-common] has failures: true

@derdanne
Copy link
Contributor

derdanne commented Oct 9, 2018

Hey, thanks for your report.

When using client_idmapd_setting, you'll have to use the augeas syntax ("set key value") like:

$client_idmapd_setting = ['set NEED_IDMAPD yes']

--> https://puppet.com/docs/puppet/5.5/resources_augeas.html

@derdanne derdanne closed this as completed Oct 9, 2018
@jurim76
Copy link
Author

jurim76 commented Oct 9, 2018

This does not work for me, if client uses NFSv4. The module make attempt to write idmapd settings into nfs-common config, which is wrong.

From nfs/manifests/client/config.pp
if $::nfs::client::nfs_v4 {
if $::nfs::defaults_file != undef {
augeas { $::nfs::defaults_file: <- variable point to /etc/default/nfs-common, not /etc/idmapd.conf
context => "/files/${::nfs::defaults_file}",
changes => $::nfs::client_idmapd_setting,
}
}

@derdanne
Copy link
Contributor

derdanne commented Oct 9, 2018

Hi, this is a valid point, please look at the issue #87, which adresses the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants