I am not able to send the facts and reports to the Foreman. Please suggest the working configuration for chef-client. My configuration is: ######################################## [root@vboxcentos7 ~]# cat /etc/chef/client.rb log_level :info log_location STDOUT chef_server_url "https://chef-aws.example.com:443/organizations/example"; # Chef Server URL validation_client_name "example-validator" file_backup_path "/var/lib/chef" file_cache_path "/var/cache/chef" pid_file "/var/run/chef/client.pid"
require 'chef_handler_foreman' foreman_server_options :url => "https://foreman-aws.example.com:8443"; #Foreman Proxy foreman_facts_upload true foreman_reports_upload true ############################ Part of logs of the chef-client responsible for sending the reports to foreman : ####################################### Running handlers: [2016-08-05T11:19:32+00:00] INFO: Running report handlers [2016-08-05T11:19:36+00:00] INFO: Sending attributes to foreman - ChefHandlerForeman::ForemanFacts Running handlers complete [2016-08-05T11:19:39+00:00] INFO: Report handlers complete Deprecated features used! "method access to node attributes (node.foo.bar) is deprecated and will be removed in Chef 13, please use bracket syntax (node["foo"]["bar"]) at 3 locations: - /var/cache/chef/cookbooks/java/attributes/default.rb:22:in `from_file' - /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef_handler_foreman-0.1.1/lib/chef_handler_foreman/foreman_facts.rb:40:in `prepare_facts' - /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef_handler_foreman-0.1.1/lib/chef_handler_foreman/foreman_facts.rb:41:in `prepare_facts' Cloning resource attributes for user[activemq] from prior resource (CHEF-3694) Previous user[activemq]: /var/cache/chef/cookbooks/activemq/recipes/user.rb:8:in `from_file' Current user[activemq]: /var/cache/chef/cookbooks/activemq/recipes/user.rb:19:in `from_file' at 1 location: - /var/cache/chef/cookbooks/activemq/recipes/user.rb:19:in `from_file' Cloning resource attributes for directory[/opt] from prior resource (CHEF-3694) Previous directory[/opt]: /var/cache/chef/cookbooks/activemq/recipes/default.rb:27:in `from_file' Current directory[/opt]: /var/cache/chef/cookbooks/activemq/recipes/default.rb:32:in `from_file' at 1 location: - /var/cache/chef/cookbooks/activemq/recipes/default.rb:32:in `from_file' Chef Client finished, 3/19 resources updated in 17 seconds [2016-08-05T11:19:39+00:00] INFO: Sending resource update report to foreman (run-id: ) [2016-08-05T11:19:41+00:00] INFO: Sending resource update report (run-id: 799ece5d-5f88-4ae4-9b92-203a06003a93) ####################################### On Thursday, August 4, 2016 at 4:45:50 PM UTC+5:30, Marek Hulán wrote: > > On Wednesday 03 of August 2016 02:22:29 Abir wrote: > > I don't think the Chef plugin can act as a proxy for the Chef server. I > > don't believe that would be possible ( or very secure ). > > > > This diagram in the official manual will give you an > > idea:https://theforeman.org/plugins/foreman_chef/0.3/chef.svg > > > > Foreman simply receives the results of a Chef run Through the handler > and > > verifies this information with the chef server. The communication > between > > the chef client and server remains unchanged. > > You are correct. The Foreman chef plugin originally worked as endpoint for > the > client handler but it ignores authentication completely so you should > always > configure it to communicate through smart proxy (with smart proxy chef > plugin). > > Rajnesh, what exactly does not work for you? You don't mention any error > message. > > -- > Marek > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
