Jacob Helwig
2011-Jun-15 21:27 UTC
[Puppet Users] Open Source Team iteration & planning summary 2011-06-15
Just a heads-up that we won''t have as much time to work on our normal backlog & go through submitted patches over the next week or so due to several of us being out for conferences and other travel obligations. Finished backlog items: * #4416 - Resources cannot be used on the run where they are synced This has been merged into the 2.6.x branch, and is planned for release in 2.6.9. Occasionally, when delivering a new provider to the agent via pluginsync, the provider would be loaded before the type. When this happened the provider would cause the type to be loaded, but the type was still in the list of things to be loaded. When the autoloader would get to loading the type, this would cause the type to effectively "forget" that it had a provider that was loaded before. Now, the type explicitly checks for already loaded providers whenever it is loaded. This isn''t an ideal fix, since the type is still needlessly loaded multiple times, however a more robust solution around how the autoloader behaves, and is used is planned for Telly (#3741). * #7127 - prerun_command don''t stop puppet on error This has been merged into the 2.6.x branch, and is planned for release in 2.6.9. Previously, the prerun command wouldn''t actually halt a puppet run when it exited non-zero. The pre & postrun commands have been updated so that if the prerun command fails: * The catalog will not be applied. * The prerun command errors will be included in the report. * The report status will not be altered. * The report is sent out. * The agent & apply will exit 1 where appropriate. If the postrun command fails: * Include the postrun command errors in the report. * The report status will not be altered. * The report is sent out. * The agent & apply will exit 1 where appropriate. This brings the behavior of the pre & postrun commands in line with what their documented behavior was. This also involved some additional refactoring around report handling in the transaction which means that pluginsync errors would be included in the uploaded report. * #7224 - Bad english: hostname was not match with the server certificate This has been merged into the 2.7.x branch, and is planned for release in 2.7.1. Previously, when connecting to a master using a name that wasn''t part of its certificate (From either certname, or certdnsnames), then the agent would report "hostname was not match with the server certificate". The REST API handling has been updated to catch these kinds of SSL errors, and replace them with a message that is hopefully much more informative. The new message is in the following form, where ''localhost'' is the name used to connect to the master, and ''foobar'', ''one_cert'', ''two_cert'', ''red_cert'', ''blue_cert'' are the expected possible host names from certdnsnames: Server hostname ''localhost'' did not match server certificate; expected one of foobar, one_cert, two_cert, red_cert, blue_cert Removed backlog items: These have been re-prioritized according to the road map that we published earlier in the week: http://projects.puppetlabs.com/projects/puppet/wiki/Road_map * #7742 - Package type V2 - apt * #7743 - Package type V2 - dpkg * #7744 - Package type V2 - aptitude New backlog items: * #7316 - puppet applications delivered via pluginsync don''t work. * #4916 - Plugins should not be able to override core functionality. * #7788 - Puppet should allow rubygems to deliver new functionality * #3910 - Server is not authoritative over client environment when specified in an ENC * #2247 - enablerepo and disablerepo for yum type * #3534 - Dashboard should support ability to set variables as arrays in the ENC Current backlog: * #7316 - puppet applications delivered via pluginsync don''t work. * #5517 - behavior change within 2.6 makes it impossible to override class parameters of "included" parametrized classes * #3741 - Custom facts loaded multiple times * #3669 - Make puppet honor DNS SRV records * #4916 - Plugins should not be able to override core functionality. * #7788 - Puppet should allow rubygems to deliver new functionality * #3910 - Server is not authoritative over client environment when specified in an ENC * #2247 - enablerepo and disablerepo for yum type * #3534 - Dashboard should support ability to set variables as arrays in the ENC -- Jacob Helwig