8/17 Opscode Ticket Triage


#1

The exact day we do triage here is shuffling around, but we will keep
at it. Below is the result of this weeks triage work. More news to
come in the next day or so.

To merge:
CHEF-2179 - new log output for chef runs is a bit too verbose
CHEF-1898 - Knife error messages get sent to stdout
CHEF-2509 - “knife configure -i” incorrectly adds the deprecated
cookbook shadowing configuration
CHEF-2530 - chef-solr-rebuild is broken
CHEF-2532 -Clean up spec output
CHEF-2542 - Missing specs for some of the knife client commands
CHEF-2547 - yum provider - arch in package name triggers provides search
COOK-426 - openldap cookbook fails to create
/var/cache/local/preseeding on relevant platforms
COOK-471 - apt cookbook’s execute apt-get update should ignore_failure
COOK-538 - bootstrap-latest (0.10.0) doesn’t work on ubuntu natty
COOK-585 - RabbitMQ service is not managed by Chef
COOK-636 - Nagios server recipe attempts to start too soon
COOK-646 - Nagios cookbook fails from bootstrap because of invalid
"monitoring" hostgroup
COOK-680 - Gecode recipe should rebuild if gecode is already installed
COOK-686 - create firewall and firewall_rule resources
COOK-687 - create UFW providers for all resources
COOK-700 - Windows registry provider should be more robust and Convenient

Other:
CHEF-2512 - knife cookbook site install with specific version fails
Reopened - Regex appears to need some work
CHEF-2527 - "Horrible error message when users delete current
environment via WebUI
Closed - Duplicate bug on wrong tracker
CHEF-2549 - Add start handlers to a chef-client run.
Reopened - Add a test please
OHAI-103 - don’t hardcode paths to binaries, let the current
environment find them.
Reopened - There are still paths in execute commands
OHAI-141 - ohai on hardy throws an undefined method
Closed - Wontfix, backporting for Rubygems on Ubuntu 8.04 (hardy) is too old
OHAI-144 - documentation for ohai [attributes] regression
Reopened - Solve using banner instead


Bryan McLellan | opscode | senior systems administrator
© 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org


#2

Bryan,

Would it be possible to first evaluate the outcome of the previous
triage before new tickets get triaged? My COOK-604 ticket was triaged
in June, but hasn’t been merged until now. :frowning:

Ringo


#3

On Thu, Aug 18, 2011 at 1:23 AM, Ringo De Smet ringo.desmet@gmail.com wrote:

Would it be possible to first evaluate the outcome of the previous
triage before new tickets get triaged? My COOK-604 ticket was triaged
in June, but hasn’t been merged until now. :frowning:

My team doesn’t manage the COOK project. However, I completely
recognize it has been a problem and I’m actively working on getting
increased attention to it. Stick around and we’ll fix that up soon.

Bryan