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

Could not find dependency Package #17

Closed
summerm78 opened this issue Oct 5, 2016 · 11 comments
Closed

Could not find dependency Package #17

summerm78 opened this issue Oct 5, 2016 · 11 comments
Labels

Comments

@summerm78
Copy link

Hi

We use your puppet module in our environment and get an error with the newest version.

Error: Failed to apply catalog: Could not find dependency Package[ca-certificates] for File[our_root_ca.crt] at /etc/puppet/environments/KT_puppet_13/modules/ca_cert/manifests/ca.pp:102

The package ca-certificates is available yum info ca-certificates Loaded plugins: langpacks, product-id, rhnplugin, search-disabled-repos, subscription-manager This system is not registered with RHN Classic or Red Hat Satellite. You can use rhn_register to register. Red Hat Satellite or RHN Classic support will be disabled. Installed Packages Name : ca-certificates Arch : noarch Version : 2015.2.6 Release : 70.1.el7_2 Size : 1.1 M Repo : installed From repo : rhel-7-server-rpms Summary : The Mozilla CA root certificate bundle URL : http://www.mozilla.org/ License : Public Domain Description : This package contains the set of CA certificates chosen by the : Mozilla Foundation for use with the Internet PKI

and installed on all systems.

OS is RHEL 7.

@pcfens
Copy link
Contributor

pcfens commented Oct 5, 2016

Is the ca_cert class declared anywhere, or only ca_cert::ca resources?

@summerm78
Copy link
Author

The class is defined in the environment in Satellite 6.

@pcfens
Copy link
Contributor

pcfens commented Oct 5, 2016

I'm not familiar with how Satellite manages it's puppet configs, so I'll have to take a look a little bit deeper.

While I'm figuring out what's going on, could you try pinning the module to us version 1.4.1 instead of latest? I suspect that the error is related to a change introduced in 1.4.2.

@summerm78
Copy link
Author

We have already pinned the module to version 1.4.1. With this version the the module workes.

@pcfens
Copy link
Contributor

pcfens commented Oct 11, 2016

Is there any chance you can test what's hosted in GitHub for me? I've modified the defined resource type so that the files depend on the ca_cert class rather than the package specifically.

@summerm78
Copy link
Author

Sorry for the late response. I tried it, but i get the same error.

@pcfens
Copy link
Contributor

pcfens commented Oct 13, 2016

If you're managing a CA in a manifest (as opposed to hiera), could you try adding require => Class['ca_cert'], to your ca_cert::ca { ... resource with the latest version that you've been having issues with?

If it changes the error message could you send that along? If it works then it should help point me to where I need to dig some more.

Thanks for working through this with me.

@summerm78
Copy link
Author

I've to take a deeper look at this with a workmate on monday and we will provide feedback as son as possible.

@summerm78
Copy link
Author

With version 1.5.0 we get it running. But we have to include the ca_cert in our init.pp.

class root { include ca_cert #include root::ssh_key include root::cert }

@pcfens
Copy link
Contributor

pcfens commented Oct 20, 2016

That sounds about right then. The class itself needs to be declared before managing CAs since it's what takes care of package management and updating the system CA list when something changes.

You can use include ::ca_cert as many times as you want without causing an error, so you can drop that piece in your root::cert class and other CA managing modules and they'll each work without a wrapper module around them.

@pcfens
Copy link
Contributor

pcfens commented Jan 3, 2017

I'm going to go ahead and close tbis since it sounds like everything is working. If you still are having issues we can always reopen this.

@pcfens pcfens closed this as completed Jan 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants