You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/08/21 03:47:51 UTC

[jira] [Updated] (AMBARI-2969) Erroneous error message when saving new configuration

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

Sumit Mohanty updated AMBARI-2969:
----------------------------------

    Attachment: AMBARI-2969.patch

{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main ....................................... SUCCESS [0.887s]
[INFO] Apache Ambari Project POM ......................... SUCCESS [0.255s]
[INFO] Ambari Web ........................................ SUCCESS [8.053s]
[INFO] Ambari Server ..................................... SUCCESS [8:38.437s]
[INFO] Ambari Agent ...................................... SUCCESS [19.638s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
{noformat}
                
> Erroneous error message when saving new configuration
> -----------------------------------------------------
>
>                 Key: AMBARI-2969
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2969
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.4.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.4.0
>
>         Attachments: AMBARI-2969.patch
>
>
> The root cause for this issue is that after upgrade of the stack, Ambari DB is left with conflicting desired and current values for stack version. So when upgrade cluster request is issued, Ambari tries to upgrade the stack itself.
> Ambari's stack upgrade feature is not applicable for 1.4.0 and should be disabled as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira