Re: [openstack-dev] [chef] fog-openstack 0.2.0 breakage
On Fri, Aug 31, 2018 at 8:59 AM, Samuel Cassiba wrote: > Ohai! > > fog-openstack 0.2.0 was recently released, which had less than optimal > effects on Chef OpenStack due to the client cookbook's lack of version > pinning on the gem. > Currently, the client cookbook is pinned to <0.2.0 going back to Ocata. Supermarket is updated as well. Due to the fallout generated, 0.2.x will be allowed where ChefDK introduces it, but 0.2.1 should be usable if you want to give it a go. Best, scas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [chef] fog-openstack 0.2.0 breakage
Thanks for notifying about this, Samuel. Our most modern deployment is actually currently blocked on this and I'm glad to see a resolution. Best, -jay On 08/31/2018 11:59 AM, Samuel Cassiba wrote: Ohai! fog-openstack 0.2.0 was recently released, which had less than optimal effects on Chef OpenStack due to the client cookbook's lack of version pinning on the gem. The crucial change is that fog-openstack itself now determines Identity API versions internally, in preparation for a versionless Keystone endpoint. Chef OpenStack has carried code for Identity API determination for years, to facilitate migrating from Identity v2.0 to Identity v3. Unfortunately, those two methods became at odds with the release of fog-openstack 0.2. At the time of this writing, PR #421 (https://github.com/fog/fog-openstack/pull/421) has been merged, but there is no new release on rubygems.org as of yet. That is likely to happen Very Soon(tm). On the home front, with the help of Roger Luethi and Christoph Albers, we've introduced version constraints to the client cookbook to pin the gem to 0.1.x. At present, we've merged constraints for master, stable/queens and stable/pike. The new release was primed to go into ChefDK 3.2 had it not been brought up sooner. Thank you to everyone who gave a heads-up! Best, scas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] fog-openstack 0.2.0 breakage
Ohai! fog-openstack 0.2.0 was recently released, which had less than optimal effects on Chef OpenStack due to the client cookbook's lack of version pinning on the gem. The crucial change is that fog-openstack itself now determines Identity API versions internally, in preparation for a versionless Keystone endpoint. Chef OpenStack has carried code for Identity API determination for years, to facilitate migrating from Identity v2.0 to Identity v3. Unfortunately, those two methods became at odds with the release of fog-openstack 0.2. At the time of this writing, PR #421 (https://github.com/fog/fog-openstack/pull/421) has been merged, but there is no new release on rubygems.org as of yet. That is likely to happen Very Soon(tm). On the home front, with the help of Roger Luethi and Christoph Albers, we've introduced version constraints to the client cookbook to pin the gem to 0.1.x. At present, we've merged constraints for master, stable/queens and stable/pike. The new release was primed to go into ChefDK 3.2 had it not been brought up sooner. Thank you to everyone who gave a heads-up! Best, scas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
