[
https://issues.apache.org/jira/browse/AMBARI-21853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21853:
-------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Packages Already Installed Cause Problems When Scoping By New Repo ID Schema
> ----------------------------------------------------------------------------
>
> Key: AMBARI-21853
> URL: https://issues.apache.org/jira/browse/AMBARI-21853
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.6.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: yumrpm.patch
>
>
> The recent changes in repository creation and management (AMBARI-20871,
> AMBARI-21719, AMBARI-21398) has caused a regression with previously installed
> packages. When Ambari goes to install a package (new install, reinstall,
> etc), we scan the packages in the available and installed repositories.
> Using the found packages, we try to match this up with the package from the
> {{metainfo.xml}} of the component. However, we're now restricting the
> packages to that of the current repository.
> When the packages have already been installed (sysprepp'd clusters, cluster
> being upgraded from older Ambaris), the repositories have already been
> named/created and the packages are associated with them. This prevents them
> from being returned in our above queries.
> The temporary workaround here is to scan the {{/etc/yum.repos.d}} directory
> for repo files which match our current URL or mirrorlist. If found, also
> include those repos in our scans...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
