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

puppet error on Ubuntu 20 LTS #38

Closed
djgreen opened this issue Apr 20, 2022 · 6 comments · Fixed by #39
Closed

puppet error on Ubuntu 20 LTS #38

djgreen opened this issue Apr 20, 2022 · 6 comments · Fixed by #39

Comments

@djgreen
Copy link

djgreen commented Apr 20, 2022

Error: Could not set 'file' on ensure: No such file or directory - A directory component in /etc/csh/login.d/lmod.csh20220420-10341-1vpkbzp.lock does not exist or is a dangling symbolic link (file: /etc/puppetlabs/code/environments/ece_production/modules/lmod/manifests/load.pp, line: 49)
Error: Could not set 'file' on ensure: No such file or directory - A directory component in /etc/csh/login.d/lmod.csh20220420-10341-1vpkbzp.lock does not exist or is a dangling symbolic link (file: /etc/puppetlabs/code/environments/ece_production/modules/lmod/manifests/load.pp, line: 49)
Wrapped exception:
No such file or directory - A directory component in /etc/csh/login.d/lmod.csh20220420-10341-1vpkbzp.lock does not exist or is a dangling symbolic link
Error: /Stage[main]/Lmod::Load/File[lmod-csh-load]/ensure: change from 'absent' to 'file' failed: Could not set 'file' on ensure: No such file or directory - A directory component in /etc/csh/login.d/lmod.csh20220420-10341-1vpkbzp.lock does not exist or is a dangling symbolic link (file: /etc/puppetlabs/code/environments/ece_production/modules/lmod/manifests/load.pp, line: 49)

Noticing the above error when running on Ubuntu 20 LTS.

@djgreen
Copy link
Author

djgreen commented Apr 20, 2022

Nevermind, realized that I wasn't installing csh or tcsh on my Ubuntu 20 systems. When I forced this, the issue went away.

Of course, not sure that it should be required if we weren't using it...

@treydock
Copy link
Owner

Did you happen to define a different list of runtime packages? This module should have already handled install csh and tcsh unless that list of packages was re-defined.

@djgreen
Copy link
Author

djgreen commented Apr 21, 2022

We haven't changed any of your code if that's what you're asking. We just call it. Where in your code do you force the installation of those packages?

@treydock
Copy link
Owner

Packages are listed here:

lmod::runtime_packages:
- 'lua5.3'
- 'lua-filesystem'
- 'lua-json'
- 'lua-posix'
- 'lua-term'
- 'tcl8.6'
- 'csh'
- 'tcsh'
- 'zsh'

They are installed for source and "none" install method here:

'source','none': {
if $lmod::install_method == 'source' {
include lmod::install::source
Class['lmod::install'] -> Class['lmod::install::source']
}
if $lmod::ensure == 'present' {
ensure_packages($lmod::runtime_packages, {'require' => $package_require})
ensure_packages($lmod::build_packages, {'require' => $package_require})
}
}

However the default install method is "package" so it would seem maybe the Lmod package for Ubuntu 20.04 is not depending on tcsh or csh? Notice one gap in the module's testing is it doesn't do acceptance testing for default package install, which is curious. I'm looking into that as I forget why that is.

@djgreen
Copy link
Author

djgreen commented Apr 21, 2022

Checked our config, and yes, we're using "install_method => 'package',"

treydock added a commit that referenced this issue Apr 21, 2022
…Ubuntu

Bump module dependency max versions
Fixes #38
treydock added a commit that referenced this issue Apr 21, 2022
…Ubuntu

Bump module dependency max versions
Fixes #38
treydock added a commit that referenced this issue Apr 21, 2022
…Ubuntu (#39)

Bump module dependency max versions
Fixes #38
@treydock
Copy link
Owner

Fix for this will be released with v3.2.0 once Github Actions complete.

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

Successfully merging a pull request may close this issue.

2 participants