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

Solution for error: Could not autoload puppet/type/elasticsearch_user #1020

Closed
wants to merge 1 commit into from

Conversation

lkosz
Copy link

@lkosz lkosz commented Feb 26, 2019

Hello

PR contains solution for error Could not find a suitable provider for elasticsearch_role/elasticsearch_user_roles Could not autoload puppet/type/elasticsearch_user Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Virtual Query, Could not autoload puppet/type/elasticsearch_user: Could not autoload puppet/provider/elasticsearch_user/elasticsearch_users: no such file to load -- puppet/provider/elastic_user_command

@elasticmachine
Copy link

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

…rch_role/elasticsearch_user_roles

 On branch elasticsearch_user_roles_error
 Changes to be committed:
	modified:   lib/puppet/provider/elasticsearch_user/elasticsearch_users.rb
@lkosz lkosz force-pushed the elasticsearch_user_roles_error branch from 962d877 to de1a75f Compare February 26, 2019 10:00
@tylerjl
Copy link
Contributor

tylerjl commented Feb 26, 2019

Hi @lkosz - the problem you mention this as a solution for talks about using require_relative and refers to a different provider (elasticsearch_user_roles) instead of elasticsearch_user as you've changed here. Is $LOAD_PATH changes the right change, and if so, does it need to be made to the rest of the files that include relative files in lib/?

@lkosz
Copy link
Author

lkosz commented Feb 28, 2019

@tylerjl hmmm yes, you're right, I've pasted wrong error :) This PR solve following exact error on my side:
Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Virtual Query, Could not autoload puppet/type/elasticsearch_user: Could not autoload puppet/provider/elasticsearch_user/elasticsearch_users: no such file to load -- puppet/provider/elastic_user_command. I've changed PR title and description.
I'm preety sure I saw issue for it, but can't find it now.
It's related to both of issues: #982 and #1002 and I think attachment of such line to other libraries may be helpful :)

@lkosz lkosz changed the title Solution for error: Could not find a suitable provider for elasticsearch_user_roles Solution for error: Could not autoload puppet/type/elasticsearch_user Feb 28, 2019
@tylerjl
Copy link
Contributor

tylerjl commented Feb 28, 2019

@lkosz I agree and think that preemptively adding that line to other library files would be good here, otherwise I think that other users (and yourself) will probably just run into additional exceptions later in the run when Puppet tries to load files beyond the one changed here. Could you add that fix to the other libraries files to ensure that it's fixed for everything?

crispygoth added a commit to crispygoth/puppet-elasticsearch that referenced this pull request Jun 7, 2019
added fix to all files as mentioned by reviewer

voxpupuli#1020
@daisukixci
Copy link

Are there news about this PR ?

@smasa90
Copy link

smasa90 commented Jun 20, 2019

#982 (comment)

@tylerjl
Copy link
Contributor

tylerjl commented Aug 20, 2019

Closing in favor of #1036 which covers more files 👍

@tylerjl tylerjl closed this Aug 20, 2019
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 this pull request may close these issues.

None yet

5 participants