Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is the default yum repo path correct? #49

Open
alexjfisher opened this issue Mar 10, 2016 · 3 comments
Open

Is the default yum repo path correct? #49

alexjfisher opened this issue Mar 10, 2016 · 3 comments
Labels

Comments

@alexjfisher
Copy link
Member

Hi

From what I can tell, (for RHEL6) the module is using
https://packages.vmware.com/tools/esx/latest/rhel6/x86_64/index.html

It appears these packages haven't been updated since August?
Have vmware done some reorganising?
Perhaps
https://packages.vmware.com/tools/releases/latest/rhel6/x86_64/index.html is the correct url these days?

Not sure.

@razorsedge razorsedge self-assigned this Mar 11, 2016
@razorsedge
Copy link
Contributor

I see new bits in esx, they just are not linked to latest. I am not sure what the release directory is for. If they are reorganizing, its going to be painful trying to figure out the logic to get the right URL.

@alexjfisher
Copy link
Member Author

It appears that since version 10 of vmware tools, new releases of vmware tools are no longer linked to versions of ESX.
https://blogs.vmware.com/vsphere/2015/09/vmware-tools-10-0-0-released.html

At the same time, the release directory only contains version 10.x releases.

It'd be nice if they'd updated some docs in https://packages.vmware.com/tools/docs/manuals/index.html or provided a clear explanation in an updated https://packages.vmware.com/tools/versions

@razorsedge
Copy link
Contributor

Good find. That explains things.

I guess for now we could have tools_version => latest point to the new release directory location and any other value point to the esx location. The trouble appears when people start wanting the 10.0.5 version instead of the 6.0u1 version .

divad added a commit to divad/puppet-vmwaretools that referenced this issue Jul 19, 2016
VMware have changed the layout of packages.vmware.com necessitating a change to this module to use the new location for the latest package releases. This PR could however break users who are specifying releases before version 10, so you might want to build a more complicated change which checks the specified version if there is one and selects either esx/$version or releases/$version...
@razorsedge razorsedge removed their assignment Apr 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants