Bug #31979
open
/api/v2/reports (used by Ansible) wants the client smart proxy to have 'Puppet' feature
Added by Dominique Quatravaux almost 4 years ago.
Updated almost 4 years ago.
Description
What I attempted:
- set up a smart proxy with Ansible feature on, but Puppet feature off
- ran Ansible role
What I expected to happen:
- facts should appear in the Foreman database
- report should appear in the Foreman database
What happened instead:
- facts did appear in the Foreman database
- I see a 403 error in the logs regarding /api/v2/reports
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8361 added
So I made https://github.com/theforeman/foreman/pull/8361 and it does fix the problem at hand; however I'm sure there is room for improvement:
- I have no idea if and how to move this change into the foreman_ansible plugin
- I assume other consumers of /api/v2/reports (Chef? Salt?) will want something similar
Thanks for any suggestion, I'll be happy to revisit my PR!
- Pull request https://github.com/theforeman/foreman_ansible/pull/388 added
- Pull request deleted (
https://github.com/theforeman/foreman/pull/8361)
Please close in favor of #31980
Also available in: Atom
PDF
Updated by 
Updated by