-
Notifications
You must be signed in to change notification settings - Fork 421
Issues: chef-boneyard/chef-client
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
Author
Label
Milestones
Assignee
Sort
Issues list
Windows scheduled task fails if Chef log directory doesn't exist
#741
opened Apr 5, 2022 by
splatteredbits
In a kitchen run, "chef-client" cookbook v12.3.3 failing on Redhat 6.10 while v12.3.2 works OK
#738
opened Jun 23, 2021 by
tas50
RHEL/CentOS 6 Kitchen tests are terminated by the chef-client restart action
#726
opened Mar 23, 2021 by
chrisminton
chef_client_trusted_certificate forces all file names to end in '.pem'
#723
opened Feb 2, 2021 by
ghost
Add a graceful-restart option in service restart script
Status: Good First Issue
An issue ready for a new contributor.
#508
opened Jul 20, 2017 by
haidangwa
Support for logrotate on windows machines
Type: Enhancement
Adds new functionality.
#451
opened Dec 24, 2016 by
bdrepaul
When setting up Automate related features, take care of SSL cert handling as well
Type: Enhancement
Adds new functionality.
#448
opened Dec 7, 2016 by
yvovandoorn
Chef postrotate command does not release log files
Status: Good First Issue
An issue ready for a new contributor.
Type: Bug
Does not work as expected.
#369
opened Mar 1, 2016 by
eherot
Windows root_owner should be System
Type: Enhancement
Adds new functionality.
#333
opened Aug 21, 2015 by
Annih
ProTip!
Add no:assignee to see everything thatβs not assigned.