You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2017/09/25 18:15:00 UTC

[jira] [Updated] (AMBARI-22014) Patch upgrade is going into incorrect state during package installation with invalid VDF

     [ https://issues.apache.org/jira/browse/AMBARI-22014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nate Cole updated AMBARI-22014:
-------------------------------
    Attachment: AMBARI-22014.patch

> Patch upgrade is going into incorrect state during package installation with invalid VDF 
> -----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-22014
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22014
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-upgrade
>    Affects Versions: 2.6.0
>         Environment: ambari-server --version 2.6.0.0-118
> ambari-server --hash d5003eb9d176f46c8be8aeba084630fa9f1f2728
>            Reporter: Supreeth Sharma
>            Assignee: Nate Cole
>            Priority: Critical
>              Labels: patch-upgrade
>         Attachments: AMBARI-22014.patch
>
>
> Patch upgrade is going into incorrect state when invalid VDF is used during package installation.
> Steps to reproduce :
> 1) Create a Centos7 HDP cluster with ambari
> 2) Register the VDF for Centos6 (mistakenly I registered the invalid VDF)
> 3) Click on install packages. 
> Install packages throws 500 ("Repositories for os type redhat7 are not defined. Repo version=2.6.0.2-81, stackId=HDP-2.6"), but in the UI it still shows the state as 'installing'. Also Its not allowing to deregister the VDF as the state is installing.
> Its better to check the validity of the VDF during registration, rather than failing during package installation.
> Workaround : I was able to come out of this state by restarting ambari server and I was able to deregister the version as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)