Knife-windows 0.8.0 release -- please upgrade for KB2918614 regression workaround


#1

Hello Chefs. We’ve released knife-windows 0.8.0 to RubyGems. This release
includes an important fix to work around blocking failures in Windows
bootstrap caused by a recent OS patch KB2918614 (
http://support.microsoft.com/kb/2918614). We’ve also added a new capability
to use NTLM authentication when knife-windows commands are run from a
Windows workstation.

For detailed release notes, see
https://github.com/opscode/knife-windows/blob/0.8.0/RELEASE_NOTES.md.

Changes in this release are given below – special thanks to Josh
Mahowald
for contributing a fix to return nonzero exit codes on failure.
Nick Carpenter also contributed a related fix to propagate the remote
command’s exit code to the knife winrm subcommand’s exit status. Anyone can
learn how to become a contributor at
http://docs.opscode.com/community_contributions.html.

To report bugs in knife-windows, please visit
https://github.com/opscode/knife-windows/issues to create a new issue.

Other notes:

· If you are executing knife-windows from a Windows system, you can
use winrm without SSL (currently the default) without setting the
AllowUnencrypted and Basic authentication options on the remote system’s
WinRM configuration. The default winrm quickconfig configuration for WinRM
will let you bootstrap a system without SSL using NTLM without the need for
preconfiguring WinRM to enable bootstrap.

· The workaround for the OS patch KB2918614 regression does not
address other regressions installing Windows Installer (MSI) packages that
may be caused by that patch. If your Chef Client run during bootstrap
installs MSI packages, you may encounter a failure to install such packages
if the bootstrap is initiated over WinRM. Please see
https://github.com/opscode/knife-windows/issues/96 for possible workarounds
until a new OS patch for Windows is released to fix this.

Changes in knife-windows:

  • knife-windows #98
    Get winrm command exit code if it is not expected

  • knife-windows #96
    Fix break from OS patch KB2918614

  • Remove the ‘instance data’ method of creating EC2 servers

  • Update winrm-s dependency along with em-winrm and winrm dependencies

  • Return failure codes from knife winrm even when returns is not set

  • Support Windows negotiate authentication protocol when running knife on
    Windows

Thank you!

-Adam Edwards

Engineer at Chef Software, Inc.


#2

Thanks for this Adam and others, as an avid Windows admin I’ve been looking forward to this being fixed.

Thanks!
Chris

From: Adam Edwards [mailto:adamed@getchef.com]
Sent: 07 October 2014 00:15
To: chef-dev@lists.opscode.com; chef@lists.opscode.com
Subject: [chef] knife-windows 0.8.0 release – please upgrade for KB2918614 regression workaround

Hello Chefs. We’ve released knife-windows 0.8.0 to RubyGems. This release includes an important fix to work around blocking failures in Windows bootstrap caused by a recent OS patch KB2918614 (http://support.microsoft.com/kb/2918614). We’ve also added a new capability to use NTLM authentication when knife-windows commands are run from a Windows workstation.

For detailed release notes, see https://github.com/opscode/knife-windows/blob/0.8.0/RELEASE_NOTES.md.

Changes in this release are given below – special thanks to Josh Mahowald for contributing a fix to return nonzero exit codes on failure. Nick Carpenter also contributed a related fix to propagate the remote command’s exit code to the knife winrm subcommand’s exit status. Anyone can learn how to become a contributor at http://docs.opscode.com/community_contributions.html.

To report bugs in knife-windows, please visit https://github.com/opscode/knife-windows/issues to create a new issue.

Other notes:

• If you are executing knife-windows from a Windows system, you can use winrm without SSL (currently the default) without setting the AllowUnencrypted and Basic authentication options on the remote system’s WinRM configuration. The default winrm quickconfig configuration for WinRM will let you bootstrap a system without SSL using NTLM without the need for preconfiguring WinRM to enable bootstrap.

• The workaround for the OS patch KB2918614 regression does not address other regressions installing Windows Installer (MSI) packages that may be caused by that patch. If your Chef Client run during bootstrap installs MSI packages, you may encounter a failure to install such packages if the bootstrap is initiated over WinRM. Please see https://github.com/opscode/knife-windows/issues/96 for possible workarounds until a new OS patch for Windows is released to fix this.

Changes in knife-windows:

  • knife-windows #98 Get winrm command exit code if it is not expected
  • knife-windows #96 Fix break from OS patch KB2918614
  • Remove the ‘instance data’ method of creating EC2 servers
  • Update winrm-s dependency along with em-winrm and winrm dependencies
  • Return failure codes from knife winrm even when returns is not set
  • Support Windows negotiate authentication protocol when running knife on Windows

Thank you!

-Adam Edwards
Engineer at Chef Software, Inc.