[jira] [Updated] (AMBARI-18774) Install Package for non-HDP stack fails with non-VDF repo version
[
https://issues.apache.org/jira/browse/AMBARI-18774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-18774:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Install Package for non-HDP stack fails with non-VDF repo version
> -
>
> Key: AMBARI-18774
> URL: https://issues.apache.org/jira/browse/AMBARI-18774
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18774.2.patch, AMBARI-18774.patch
>
>
> Install Package fails when registering a new non-HDP version without using a
> VDF. This is because the repo version is saved as display name (i.e.
> "HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered
> using VDF, we dont run into this issue as the version is set correctly.
> {code}
> Ambari cannot install version HDF-2.1.0.0. Version 2.0.1.0-12 is already
> installed.
> {code}
> Fix:
> Remove HDP specific hardcodings from RepositoryVersionEntity.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18774) Install Package for non-HDP stack fails with non-VDF repo version
[
https://issues.apache.org/jira/browse/AMBARI-18774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-18774:
---
Attachment: AMBARI-18774.2.patch
> Install Package for non-HDP stack fails with non-VDF repo version
> -
>
> Key: AMBARI-18774
> URL: https://issues.apache.org/jira/browse/AMBARI-18774
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18774.2.patch, AMBARI-18774.patch
>
>
> Install Package fails when registering a new non-HDP version without using a
> VDF. This is because the repo version is saved as display name (i.e.
> "HDF-2.1.0.0-30" instead of "2.1.0.0-30"). If a new version is registered
> using VDF, we dont run into this issue as the version is set correctly.
> {code}
> Ambari cannot install version HDF-2.1.0.0. Version 2.0.1.0-12 is already
> installed.
> {code}
> Fix:
> Remove HDP specific hardcodings from RepositoryVersionEntity.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
