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

pam-auth-update --package prompts interactive debconf #261

Open
puneetloya opened this issue Apr 8, 2020 · 0 comments
Open

pam-auth-update --package prompts interactive debconf #261

puneetloya opened this issue Apr 8, 2020 · 0 comments

Comments

@puneetloya
Copy link

Describe the bug

include_recipe 'os-hardening'

pam-auth-update --package prompts for debconf during the chef-run and it fails

Expected behavior
A clear and concise description of what you expected to happen.

Actual behavior

  • execute[update-pam] action run

    ================================================================================
    Error executing action run on resource 'execute[update-pam]'

    Mixlib::ShellOut::ShellCommandFailed

    Expected process to exit with [0], but received '255'
    ---- Begin output of /usr/sbin/pam-auth-update --package ----
    STDOUT:
    STDERR: Failed to open terminal.debconf: whiptail output the above errors, giving up!
    Use of uninitialized value $ret in scalar chomp at /usr/share/perl5/Debconf/Client/ConfModule.pm line 132, line 8.
    Use of uninitialized value $ret in split at /usr/share/perl5/Debconf/Client/ConfModule.pm line 133, line 8.
    Use of uninitialized value $ret[0] in string eq at /usr/share/perl5/Debconf/Client/ConfModule.pm line 134, line 8.
    ---- End output of /usr/sbin/pam-auth-update --package ----
    Ran /usr/sbin/pam-auth-update --package returned 255


**OS / Environment**
Ubuntu 14.04
**Chef Version**
```paste below
12.12.15

Cookbook Version

3.2.1

Additional context
using DEBIAN_FRONTEND=noninteractive works, just wondering thats the right solution. if thats true I will put a PR. This used to work before not sure why it would happen right now. Recently we ran a script to make a lot of directories non-writable, not sure if that should cause this.

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

No branches or pull requests

1 participant