Dependency problems with recent gem releases of ohai and mixlib-shellout


#1

Hey chefs,

In order to prep for upcoming Chef Client 12 release, yesterday we’ve
released ohai 7.6.0, mixlib-shellout 1.6.1 & mixlib-shellout 2.0.0.

Unfortunately with these releases we have broken gem installation of chef
(gem install chef) for version 11.16.4 due to dependency conflicts. Huge
thanks goes to migurski [https://github.com/migurski] for bringing this up
to our attention.

You can read more about the details of the issue and our plan on resolving
it at https://github.com/opscode/chef/issues/2517. In order to prevent
further spreading of the issue we will yank ohai 7.6.0 release soon.

After mitigating the issue we’ll do a blog post with more details and have
a postmortem in order to ensure the problem doesn’t happen again.

Sorry for the inconvenience we’ve caused and thanks for your patience while
this gets sorted out.

– Serdar


#2

Ohai chefs,

Yesterday we have a postmortem about the recent issues we had with ohai /
mixlib-shellout releases.

You can read about the details of the issues in this blog post:

Issues are now mitigated with yanking ohai 7.6.0 version and releasing an
ohai 0.8.1 (needed to skip 0.8.0 due to a tagging issue).

In our postmortem we’ve decided to implement these corrective actions:

Thanks again for everyone’s patience with us during the disruption we’ve
caused during latest releases.

On Tue, Dec 2, 2014 at 12:37 PM, Serdar Sutay serdar@getchef.com wrote:

Hey chefs,

In order to prep for upcoming Chef Client 12 release, yesterday we’ve
released ohai 7.6.0, mixlib-shellout 1.6.1 & mixlib-shellout 2.0.0.

Unfortunately with these releases we have broken gem installation of chef
(gem install chef) for version 11.16.4 due to dependency conflicts. Huge
thanks goes to migurski [https://github.com/migurski] for bringing this
up to our attention.

You can read more about the details of the issue and our plan on resolving
it at https://github.com/opscode/chef/issues/2517. In order to prevent
further spreading of the issue we will yank ohai 7.6.0 release soon.

After mitigating the issue we’ll do a blog post with more details and have
a postmortem in order to ensure the problem doesn’t happen again.

Sorry for the inconvenience we’ve caused and thanks for your patience
while this gets sorted out.

– Serdar