[jira] [Commented] (AMBARI-21853) Packages Already Installed Cause Problems When Scoping By New Repo ID Schema

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-21853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147382#comment-16147382 ] 

Hudson commented on AMBARI-21853:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #87 (See [https://builds.apache.org/job/Ambari-branch-2.6/87/])
AMBARI-21853 - Packages Already Installed Cause Problems When Scoping By (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c919f22f4c3fffee6b840ecef5ce0e73ac0eda1f])
* (edit) ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py
* (edit) ambari-common/src/main/python/resource_management/libraries/script/script.py


> 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)