-
Notifications
You must be signed in to change notification settings - Fork 65
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
unable to add pulp_rpmrepo (undefined method `each' for nil:NilClass) #245
Comments
Do you happen to have a line number where it went wrong? Other than that I'm surprised you have to include apache and those modules since we include what we need. If we don't, that's a bug. For the README expansion see #242. |
@ekohl - Admittedly that part of the profile was 'inherited' config. It is probably not necessary. I will try removing it. It doesn't really give a line number with the error, but it works fine if I change the yaml key (such that I even tried shortening the yaml to:
Still getting:
I also updated my pulp profile recently to include a few more things, one of which trusts the CA cert at the system level, which I read might be an issue in other issues.
|
Can you remove the gpg_key line and try again? I think the error is from there. The provider tries to read that as a path on the disk. |
Tried it, same error. Not sure why that would be a nil.each? For what its worth, my data entries look like:
... and I am populating /var/lib/pulp/static/rpm-gpg with puppet. (see manifest above) |
for what its worth, I ran into a cyclic dependency issue today with this... In order to trust the CA certificate, you install the "ca-certificates" package, which, of course you have to get from pulp, with its untrusted SSL CA ... I had to make base and updates http for now till I figure that one out. :) ~tommy |
Steps to reproduce(READY)
RESULTS:Pulp is installed, but we got this error: ERROR1:
WORKAROUND1:
ERROR2:
I hope this helps! |
With the following pulp_rpmrepo { 'centos-7-x86_64-base':
display_name => 'CentOS 7 x86_64 Base',
feed => 'http://mirror.centos.org/centos/7/os/x86_64/',
relative_url => 'centos/7/os/x86_64/',
gpg_key => '/etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7',
remove_missing => true,
retain_old_count => 2,
serve_http => true,
serve_https => true,
validate => true,
repoview => false,
} Then it applies succesfully:
I extended the code in #248 with an additional acceptance test locally. Could you create a repository using pure puppet code? I wonder if there's some odd conversion going on somewhere with hiera. |
I added "test-" in front, to be sure it wasn't clashing with one of my manually added repos...
and the results:
still getting the same error :( I wonder if there is something else (some other packages?) that are interfering somehow?
Not sure what to check next? |
I suspect you have something in your pulp database that the provider doesn't handle properly. I'm currently looking into them and clean them up a bit but for now my knowledge about them is still a bit limited. |
I see (a/the) problem: Here is a small portion of the "provider" (that has a .each)
For what its worth, this has plenty of repos, using On that whim, I tried tailing the weblogs and:
|
That's not the only place where nils can show up and there are no checks for it. |
@TJM the I dunno if this will affect the |
I moved my ~/.pulp/admin.conf aside (that had a username and password in it) and tried to use
but...
So, problems are...
The one thing that might be different then... according to my puppet manifest, I am using "repos::upstream" ... maybe I should not be? |
Updating the curl line from above, --cert tommy :)
|
https://www.redhat.com/archives/pulp-list/2016-March/msg00050.html I took the https://github.com/Katello/puppet-pulp/blob/master/manifests/apache.pp#L51-L62 https://github.com/Katello/puppet-pulp/blob/master/manifests/init.pp#L105-L106 I think I can workaround this by setting |
OK, so I have solved Problem 3 (my SSL Cert auth/e was broken), but these are still up for grabs:
|
I think it does. See #138 as well for why it's there but it's not a good default. I wasn't aware (yet) that it does a direct API call. That makes me wonder if we should drop pulp-admin altogether and fully move to the API. |
I would say either use the API or use |
@ekohl - Yes, #138 is the same issue I saw. The problem is the way that pulp server generates its auth certs is not compatible with whatever else is generating auth certs (guessing thats katello related).... and I do realize that I am using I agree with @walkamongus. I suggest going all one direction or the other. The Tommy |
I quite agree with that but it looks like each one is used when it's more relevant: state checking is done through the API (whose syntax fits better for that) and modifications are made much easier by using pulp-admin, which makes adding optional params easy. |
We created our pulp server today and tried to use the pulp_rpmrepo provider to configure it, but it is getting the following error: (end of puppet agent -t --debug)
Here is the relevant data:
Here is the profile/manifests/pulp.pp:
In addition, I had to SSH in and run
pulp-admin login -u admin
using the "default_password" to populate /root/.pulp/user-cert.pem. Should that be necessary? (or am I missing something, the README.md is a bit thin) :)~tommy
The text was updated successfully, but these errors were encountered: