Project

General

Profile

Actions

Bug #16920

closed

[libpam-arvados-go] the deployed pam config breaks /usr/sbin/pam-auth-update

Added by Javier Bértoli about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Story points:
-

Description

Ward reported that he was seing a lot of errors in shell.ce8i5:

[shell.tordo] Use of uninitialized value $fieldname in hash element at /usr/sbin/pam-auth-update line 704, <PROFILE> line 1.[shell.tordo] Use of uninitialized value $fieldname in hash element at /usr/sbin/pam-auth-update line 705, <PROFILE> line 1.
[shell.tordo] Use of uninitialized value $fieldname in hash element at /usr/sbin/pam-auth-update line 704, <PROFILE> line 2.
[shell.tordo] Use of uninitialized value $fieldname in hash element at /usr/sbin/pam-auth-update line 705, <PROFILE> line 2.
[shell.tordo] Use of uninitialized value $fieldname in hash element at /usr/sbin/pam-auth-update line 704, <PROFILE> line 3.
[shell.tordo] Use of uninitialized value $fieldname in hash element at /usr/sbin/pam-auth-update line 705, <PROFILE> line 3.
[shell

Checking what's going on, the issue is caused by the file /usr/share/pam-configs/arvados-go that we're deploying with our packages.

The errors are caused by the headers we're adding: removing all the commented lines makes the errors go away.


Related issues 1 (0 open1 closed)

Related to Arvados - Idea #15348: [pam] PAM module in GoResolvedTom Clegg06/23/2020Actions
Actions #1

Updated by Ward Vandewege about 4 years ago

Actions #2

Updated by Ward Vandewege about 4 years ago

  • Target version changed from To Be Groomed to 2020-10-07 Sprint
  • Assigned To set to Ward Vandewege
  • Status changed from New to Resolved
Actions

Also available in: Atom PDF