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.

Sign up for GitHub

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

Jump to bottom

CVMFS_SYSLOG_LEVEL now supports a setting of 2 #162

Open
jcpunk opened this issue Jan 20, 2023 · 0 comments
Open

CVMFS_SYSLOG_LEVEL now supports a setting of 2 #162

jcpunk opened this issue Jan 20, 2023 · 0 comments
Labels
good first issue Good for newcomers

Comments

@jcpunk
Copy link
Contributor

jcpunk commented Jan 20, 2023

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 7
  • Ruby: AIO
  • Distribution: RHEL8
  • Module version: 8.1.0

How to reproduce (e.g Puppet code you use)

Set cvmfs_syslog_level to 2

What are you seeing

Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, lambda: parameter 'cvmfs_syslog_level' expects a value of type Undef or Integer[0, 1], got Integer[2, 2]

What behaviour did you expect instead

Loglevel to match upstream support

Output log

Any additional information you'd like to impart

https://cvmfs.readthedocs.io/en/stable/apx-parameters.html
@smortex smortex added the good first issue Good for newcomers label Jan 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smortex @jcpunk