Activity
From 11/07/2017 to 12/06/2017
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...
11/30/2017
-
06:35 PM Bug #21827 (Closed): Chef environments page fails to load if current organization/location does not match linked smart proxy
- After upgrading foreman, i am getting the following 500 error when viewing the chef environments page in the UI:
<pr...
11/20/2017
-
10:36 PM Bug #21705: chef-client enteres endless loop with foreman handler
- I attached the client.rb
Most wired part is, that i didn't see that happen while running in foreground or via cron... -
- This is weird, nothing indicates any issue but I clearly see facts being sent twice. How did you configure the handle...
-
- We use:
- foreman-1.15.6
- foreman-proxy-1.15.6
- foreman_chef-0.5.0
I attached the end of a run with at least ... -
- Could you please set a loglevel in chef client to debug and upload a log from such run? Feel free to cut it when it s...
-
- On some systems, the chef-client enters a endless loop if the foreman handler is installed and the chef-client runs i...
11/09/2017
-
07:22 PM Bug #21622: Similarly named Chef Environments are not imported
- Thought I'd work around this by adding the environments manually. But we cannot.
This is a flaw in the environment... -
- On our server we have some similarly named Chef Environments:
dev Development
dev-ng Development Nex... -
- Pull request #78 is in with feature.
Optional variable is chef_bootstrap_version
Script now checks for this va... -
05:51 PM Feature #21620 (Ready For Testing): Allow version to be specified for chef omnibus bootstrap template.
-
- Fairly self explanitory; allow for an optional variable to specify a version of chef client to pass to the omnibus bo...
Also available in: Atom