el7 artifacts are returned when el5 is passed as options
Open
Nobody has claimed this yet.
Type: Bug
- Dominant language
- Ruby
- Stars
- 13
- Forks
- 55
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 8
Description
Version:
v3.11.5
Environment:
Tested on both Mac OS 10.13.6 + ChefDK 2.5.3 and on RHEL 5 + Chef 12.22.5
Scenario:
Trying to fetch the latest chef 13 version for RHEL 5.
Steps to Reproduce:
$ chef exec irb
irb(main):001:0> require 'mixlib/install'
=> true
irb(main):002:0> Mixlib::Install.new({:product_name=>"chef", :platform_version_compatibility_mode=>true, :platform=>"el", :platform_version=>"5", :architecture=>"x86_64", :channel=>:stable, :product_version=>'13'}).artifact_info.url
=> "https://packages.chef.io/files/stable/chef/13.12.3/el/7/chef-13.12.3-1.el7.x86_64.rpm"
irb(main):003:0> Mixlib::Install::VERSION
=> "3.11.5"
Expected Result:
"http://packages.chef.io/files/stable/chef/13.6.4/el/5/chef-13.6.4-1.el5.x86_64.rpm"
Actual Result:
"https://packages.chef.io/files/stable/chef/13.12.3/el/7/chef-13.12.3-1.el7.x86_64.rpm"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the Mixlib::Install.new options shown, then trace the artifact_info.url path that resolves platform_version compatibility. Verify the fix by confirming that el5 returns the expected Chef 13.6.4 URL rather than the el7 artifact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100