Need way to pin Chef version for omnibus install

Bug #1462693 reported by Alexander Dupuy on 2015-06-06
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
cloud-init
Medium
Ethan Apodaca

Bug Description

Although it is possible to specify an alternate URL for the omnibus installer, there's no way to request installation of a particular version. The downloaded (install.sh) artifact from the URL takes a '-v VERSION' argument, but there's no way to pass that argument through the cc_chef cloud-init module.

Without any way to pin the version, I am doomed to see messages like this in the cloud-init output logs:

Downloading Chef for ubuntu...
downloading https://www.chef.io/chef/metadata?v=&prerelease=false&nightlies=false&p=ubuntu&pv=14.04&m=x86_64
  to file /tmp/install.sh.1243/metadata.txt
trying wget...
url https://opscode-omnibus-packages.s3.amazonaws.com/ubuntu/10.04/x86_64/chef_12.3.0-1_amd64.deb
md5 d8421c9b3010deb03e713ada00387e8a
sha256 e06eb748e44d0a323f4334aececdf3c2c74d2f97323678ad3a43c33ac32b4f81
downloaded metadata file looks valid...
downloading https://opscode-omnibus-packages.s3.amazonaws.com/ubuntu/10.04/x86_64/chef_12.3.0-1_amd64.deb
  to file /tmp/install.sh.1243/chef_12.3.0-1_amd64.deb
trying wget...
Comparing checksum with sha256sum...

WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING

You are installing an omnibus package without a version pin. If you are installing
on production servers via an automated process this is DANGEROUS and you will
be upgraded without warning on new releases, even to new major releases.
Letting the version float is only appropriate in desktop, test, development or
CI/CD environments.

WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING

Installing Chef
installing with dpkg...
...

Related branches

Changed in cloud-init:
status: New → Confirmed
Alex L. Demidov (alexeydemidov) wrote :

With Chef 13 just released it is getting more serious - there is currently no way to force install of version 12.

Scott Moser (smoser) on 2017-08-21
Changed in cloud-init:
importance: Undecided → Medium
assignee: nobody → Ethan Apodaca (papodaca)
Chad Smith (chad.smith) on 2017-09-13
Changed in cloud-init:
status: Confirmed → In Progress
Chad Smith (chad.smith) on 2017-09-14
Changed in cloud-init:
status: In Progress → Fix Committed
milestone: none → 0.7.10

This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers