-
Notifications
You must be signed in to change notification settings - Fork 59
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 fetch profiles from chef server #361
Comments
Hey There If you're looking for more immediate troubleshooting help make sure to check out #general on the Chef Community Slack. There's plenty of folks there willing to lend a helping hand. Thanks for the first issue. We hope we can get back to you soon with a solution. |
Currently updating to 7.4.0; will update issue (and/or close) shortly |
Just to make sure this isn't going to get auto-closed because I misunderstood: is there more information I need to provide? (To confirm: I did update to 7.4.0 and still had same issue. ) |
@jillson apologies for the late follow-up, but is this still an issue in the latest version of the cookbook? |
Unfortunately, not able to test currently. I gave up and just kept my monkeypatch in place |
Cookbook version
Edit: 7.4.0 (and also 7.3.0)
Chef-client version
14.8.12
Platform Details
RHEL 7.6 on AWS EC2 instance. We appear to be using inspec 3.0.61 (bundled with chef client)
Scenario:
We have chef server configured to proxy requests to chef automate for profiles, and then publish the results of the audit cookbook through chef server to chef automate.
Steps to Reproduce:
Followed standard configuration as far as I know. Using the bottom configuration option from https://github.com/chef-cookbooks/audit/blob/master/docs/supported_configuration.md (i.e.
Expected Result:
Audit results published
Actual Result:
Using the stock code, I get an error. The error message is [] is undefined for URI::HTTPS. The real meaning is that the code was being passed in a URI:HTTPS but was expecting either a string (which gets parsed to a URI:HTTPS) or a hash (which will have a :url value that gets passed as a string to be parsed).
If I edit line 123 or so in * /opt/chef/embedded/lib/ruby/gems/2.5.0/gems/inspec-core-3.0.61/lib/fetchers/url.rb * to add
at the top of the * def parse_uri(target) * method, then I get the expected result.
The text was updated successfully, but these errors were encountered: