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

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.6.0
• Component/s: ambari-agent
• Epic Link: Ambari: Patch Upgrades
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 30/Aug/17 14:12
• Updated: 30/Aug/17 15:02
• Resolved: 30/Aug/17 14:25

Description

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