Activity
From 12/04/2017 to 01/02/2018
01/02/2018
- 01:05 PM Bug #21705: chef-client enteres endless loop with foreman handler
- Elias Abacioglu wrote:
> I can confirm it's not the latest chef-client.
> We've had this issue with nodes that run ... - 10:50 AM Bug #22084 (Need more information): CentOS7.4 platform how to upgrade foreman_chef-0.5.0 into foreman_chef-0.6.0
12/28/2017
- 05:06 PM Bug #22084: CentOS7.4 platform how to upgrade foreman_chef-0.5.0 into foreman_chef-0.6.0
- You seem to be running 0.5 still, is it rpm based installation? If so, you should wait until official rpm builds hit ...
12/27/2017
- 02:37 PM Bug #22084: CentOS7.4 platform how to upgrade foreman_chef-0.5.0 into foreman_chef-0.6.0
- I upgrade my ruby from 2.0.0 to 2.4.1,then run gem install 'foreman_chef'
[root@foreman tfm]# gem env
RubyGems En... - 01:12 PM Bug #22084 (Resolved): CentOS7.4 platform how to upgrade foreman_chef-0.5.0 into foreman_chef-0.6.0
- There is an error [ForemanChef :: ProxyException]: Unable to communicate with Chef proxy,so i shoud upgrade foreman_c...
12/26/2017
- 12:17 PM Feature #22048: ERF12-8219 [ForemanChef::ProxyException]: Unable to communicate with Chef proxy,
- Marek Hulán wrote:
> This is most likely incompatibility with Foreman 1.16, closing as a duplicate of #19620, please...
12/22/2017
- 07:28 PM Revision 56e327c2 (foreman_chef): Version bump to 0.6.0
- 07:27 PM Feature #18056 (Closed): Use remote execution to start chef-client run
- 07:24 PM Bug #19978 (Closed): Chef Plugin: [foreman-tasks/action] [E] ERF12-0944 [ForemanChef::ProxyException]: Unable to communicate with Chef proxy, 500 Internal Server Error (ForemanChef::ProxyException)
- According to the trace, it was failing in validation bootstrap method since there was wrong setting name used. This s...
- 07:23 PM Bug #22064 (New): Rebulding does not work because of Chef ACL system
- Somewhere around Chef 12, just deleting client stopped working for rebuild since the new client does not have ACL for...
- 07:23 PM Revision 5aac30a3 (foreman_chef): Merge pull request #61 from ares/fix/18056
- Fixes #18056 - use REX in host detail page
- 07:09 PM Bug #21587: Create host fails but the task is marked as succeeded. No useful logs are created that show why the task failed.
- Aaron, Chris, just to be sure, what is your bootstrap method? You can find out at Setting -> Chef -> validation_boots...
- 05:00 PM Bug #21587: Create host fails but the task is marked as succeeded. No useful logs are created that show why the task failed.
- Also one more note, the task really succeeded so you most likely have chef client created on chef-server, the rollbac...
- 04:59 PM Bug #21587: Create host fails but the task is marked as succeeded. No useful logs are created that show why the task failed.
- Thanks for the report and sorry for the delay. According to the trace, Chef communication worked just fine, the CR co...
- 07:03 PM Revision f0876d68 (foreman_chef): Merge pull request #83 from ares/fix/21622
- Fixes #21622 - accept hyphens and underscore in env name
- 07:02 PM Revision 37c1f0e9 (foreman_chef): Fixes #21622 - accept hyphens and underscore in env name
- 06:59 PM Bug #21622 (Closed): Similarly named Chef Environments are not imported
- Thanks for the report and sorry for the delay. I updated the validation according to "the docs":https://docs.chef.io/...
- 06:59 PM Feature #21620 (Closed): Allow version to be specified for chef omnibus bootstrap template.
- 06:57 PM Revision 4bc05eaf (foreman_chef): Merge pull request #82 from ares/review/pr78
- Fixes #21620 - Add support for optional version
- 06:53 PM Bug #22063 (Closed): Orchestration is triggered twice
- 04:47 PM Bug #22063 (Closed): Orchestration is triggered twice
- If users don't use validate.pem but rather do the full orchestration, the orchestration is triggered twice, once by a...
- 06:52 PM Bug #19620 (Closed): Settings compatibility with Foreman 1.16
- 06:52 PM Bug #21827 (Closed): Chef environments page fails to load if current organization/location does not match linked smart proxy
- 06:29 PM Bug #21827: Chef environments page fails to load if current organization/location does not match linked smart proxy
- This looks like the environment's proxy can't be found. Did you delete some proxy? Is the proxy assigned to your curr...
- 06:46 PM Revision 7685b82a (foreman_chef): Refs #21620 - further improvements to version configuration
- 06:34 PM Revision 3622ef69 (foreman_chef): Fixes #21620 - Add support for optional version
- 06:30 PM Revision dacf3dbc (foreman_chef): Merge pull request #81 from ares/fix/21827
- Fixes #21827 - load proxies from all taxonomies
- 06:29 PM Revision 5737260d (foreman_chef): Merge pull request #80 from ares/fix/22063
- Fixes #22063 - avoid double client creation
- 06:29 PM Revision 626fcb68 (foreman_chef): Fixes #21827 - load proxies from all taxonomies
- 04:52 PM Revision e0eedb94 (foreman_chef): Fixes #22063 - avoid double client creation
- 04:45 PM Feature #22048 (Duplicate): ERF12-8219 [ForemanChef::ProxyException]: Unable to communicate with Chef proxy,
- This is most likely incompatibility with Foreman 1.16, closing as a duplicate of #19620, please let us know if you us...
- 04:01 PM Revision d7d007b7 (foreman_chef): Refs #19620 - add explicit namespace
- 03:55 PM Revision faa9fd40 (foreman_chef): Fixes #18056 - use REX in host detail page
- 03:48 PM Revision 2795302b (foreman_chef): Merge pull request #79 from ares/fix/chef_problems
- Fix various compatibility issues with 1.15/1.16/1.17
- 03:04 PM Bug #21705: chef-client enteres endless loop with foreman handler
- I've done some strace:ing and tcpflow:ing, can see that the first "POST /api/reports", receives a "HTTP/1.1 201 Creat...
- 03:01 PM Refactor #18055 (Closed): Update template with parameter macros introduced in Foreman 1.15
- Applied in changeset commit:foreman_chef|9e5ce7666e3ec2d95e25c15d733ea1504851d68b.
- 02:44 PM Revision 84a6545d (foreman_chef): Merge pull request #60 from ares/fix/18055
- Fixes #18055 - Update templates with params macros
- 02:44 PM Revision 9e5ce766 (foreman_chef): Fixes #18055 - Update templates with params macros
- 01:54 PM Revision 56195ddb (foreman_chef): Improve logging
- 01:49 PM Revision 8174d209 (foreman_chef): Fix templates for 1.17
- 01:23 PM Revision d5ab274a (foreman_chef): Fix settings usage - removed in 1.16
- 01:08 PM Revision ac6d540c (foreman_chef): Extend rescueing
12/21/2017
- 09:54 AM Feature #22048: ERF12-8219 [ForemanChef::ProxyException]: Unable to communicate with Chef proxy,
- Please do not assign tickets to people out of the blue. Thanks.
- 04:02 AM Feature #22048 (Duplicate): ERF12-8219 [ForemanChef::ProxyException]: Unable to communicate with Chef proxy,
- The following error occurred when I tried to delete a host "ERF12-8219 [ForemanChef::ProxyException]: Unable to commu...
12/20/2017
- 02:09 PM Bug #21705: chef-client enteres endless loop with foreman handler
- I can confirm it's not the latest chef-client.
We've had this issue with nodes that run both chef v12 and v13 under ...
12/19/2017
- 04:47 PM Bug #21705: chef-client enteres endless loop with foreman handler
- I'm also affected by this, running chef-handler-foreman v0.2.0.
@[2017-12-19T17:39:38+01:00] INFO: Sending resourc...
12/12/2017
12/11/2017
- 10:24 PM Bug #21939 (Duplicate): Foreman/Katello 1.16/3.5 fails on db:seed because undefined method `foreman_url'
- Hi,
i have trouble running "Running foreman-installer --scenario katello --upgrade" which fails because something ...
12/04/2017
- 11:53 AM Bug #21827: Chef environments page fails to load if current organization/location does not match linked smart proxy
- Thanks a lot for the report. I think there will be more things that needs to be updated for 1.16 compatibility. I wil...
Also available in: Atom