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

Missing dependency for selinux::boolean #387

Closed
jcbollinger opened this issue Mar 18, 2024 · 2 comments
Closed

Missing dependency for selinux::boolean #387

jcbollinger opened this issue Mar 18, 2024 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@jcbollinger
Copy link

jcbollinger commented Mar 18, 2024

Affected Puppet, Ruby, OS and module versions/distributions

The issue was observed with

  • Puppet: 7.28
  • Ruby: bundled with PDK 3.0.1
  • Distribution: RHEL 7.9
  • Module version: 3.4.1, 4.1.0

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

class mymodule::myclass {
  selinux::boolean { 'use_nfs_home_dirs': ensure => 'on' }
}

What are you seeing

Spec tests of one of my modules fails with

error during compilation: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Unknown resource type: 'selboolean' (file: /home/me/puppet/environments/production/modules/mymodule/spec/fixtures/modules/selinux/manifests/boolean.pp, line: 40, column: 5) (file: /home/me/puppet/environments/production/modules/mymodule/spec/fixtures/modules/mymodule/manifests/myclass.pp, line: 34) on node mybox.my.org

What behaviour did you expect instead

Catalog compilation should succeed.

Output log

See above.

Any additional information you'd like to impart

I presume that the wanted selboolean is the one from puppetlabs-selinux_core, but puppet-selinux's metadata does not express a dependency on that module. At minimum, adding puppetlabs-selinux_core to my test fixture resolved my test failures.

@kenyon
Copy link
Member

kenyon commented Mar 18, 2024

See #355.

@kenyon kenyon added the duplicate This issue or pull request already exists label Mar 18, 2024
@kenyon
Copy link
Member

kenyon commented Mar 18, 2024

Closing as a duplicate of #355.

@kenyon kenyon closed this as not planned Won't fix, can't repro, duplicate, stale Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants