Description of problem: Currently there is no guarantee that a content url may not change So it could go from: /foo/$arch/$release/bar to /foo/$arch/$release/baz This is a one to one change. We can support this but do not currently. After every manifest import, we would need to detect that there was a change (by comparing the existing relative path to the new computed one), change the relative url on each repo, change the path in pulp, and finally trigger a distributor publish in pulp.
This would also need to work across organizations, and to ignore cases where the content url had a one-to-many change (meaning that it went from having two variable substitutions ($arch and $release) to having only one). Should we try to preserve the existing content for systems?
Opened: https://bugzilla.redhat.com/show_bug.cgi?id=1188319 for easier notification of content url changes. I would not expect this for 6.1 though.
I have removed the blocker flag since it was moved out of 6.1.
We have found out (per Joey Boggs) that this bug prevents us from making any changes to the download page pulldown menu values for RHEV and, as such, we cannot enter correct and understandable values for customers to easily download the software needed for RHEV. This is affecting release 3.6 now... I would like to ask that the resolution date be pulled in as it apparently affects customer facing data for more than just Satellite.
Any update of fixing this?
Any forecast for this update?? We have found out (per Joey Boggs) that this bug prevents us from making any changes to the download page pulldown menu values for RHV and, as such, we cannot enter correct and understandable values for customers to easily download the software needed for RHV. This is affecting current RHV releases now... I would like to ask that the resolution date be pulled in as it apparently affects customer facing data for more than just Satellite.
after clarification with Justin, moving to subscription component
When will this be done -- it's customer impacting...
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
I'm reopening this at the request of ahills in IT. ahills isn't proposing we fix this in all previous versions, ideally just 6.5. So hopefully at some point we can fix 'broken' content urls prior to rhel 7's EOL
Connecting redmine issue https://projects.theforeman.org/issues/26694 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26694 has been resolved.
Verified in Satellite 6.6 Snap 6 Followed the steps outlined in https://github.com/Katello/katello/pull/8094#issuecomment-487203053 Made a few adjustments to the steps, but nothing significant. (content_label, cdn url path) Manifest 1 ---------- Upstream URL: http://my.fake.cdn/pub/manifest-prs/cdn/content/dist/rhel/server/7/7Server/x86_64/rhv/4.0/os Published At https://my.sat.com/pulp/repos/tester/Library/content/dist/rhel/server/7/7Server/x86_64/rhv/4.0/os/ Upstream URL: http://my.fake.cdn/pub/manifest-prs/cdn/content/dist/rhel/server/6/6Server/x86_64/rhevm/3.3/os Published At: https://my.sat.com/pulp/repos/tester/Library/content/dist/rhel/server/6/6Server/x86_64/rhevm/3.3/os/ Manifest 2 ---------- Upstream URL: http://my.fake.cdn/pub/manifest-prs/cdn/content/dist/foo/x86_64/rhv/4.0/os Published At https://my.sat.com/pulp/repos/tester/Library/content/dist/foo/x86_64/rhv/4.0/os/ Upstream URL: http://my.fake.cdn/pub/manifest-prs/cdn/content/dist/rhel/server/6/6Server/x86_64/rhevm/3.3/os Published At: https://my.sat.com/pulp/repos/tester/Library/content/dist/rhel/server/6/6Server/x86_64/rhevm/3.3/os/
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3172