[
https://issues.apache.org/jira/browse/AMBARI-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juanjo Marron resolved AMBARI-10642.
------------------------------------
Resolution: Duplicate
Fix Version/s: 2.4.0
> Mechanism to automatically update Ambari versions in component upgrades
> -----------------------------------------------------------------------
>
> Key: AMBARI-10642
> URL: https://issues.apache.org/jira/browse/AMBARI-10642
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-web
> Affects Versions: 2.0.0
> Reporter: Juanjo Marron
> Priority: Minor
> Fix For: 2.4.0
>
>
> Currently, Ambari reflects the version of the component in the UI in:
> - The installation wizard when adding services.
> - Once services are installed under Ambari -> Admin -> Repositories.
> These versions are read from the metainfo.xml files included in each service
> in the Ambari code.
> When a service is updated hosting a new rpm in the yum repo, if it changes
> also the component version number, the version property in the metainfo file
> should be edited as well to show this version change
> This minor change forces to rebuild the Ambari server rpm and reinstall it
> to modified the version value.
> Update Ambari versions automatically could be provided as part of Ambari
> offering a mechanism that reads the version of the component from the
> installed rpm package and write it on the metainfo file of the service
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
