ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Cole (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-22240) Restart of random service could fail during express downgrade
Date Mon, 16 Oct 2017 01:54:01 GMT

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

Nate Cole updated AMBARI-22240:
-------------------------------
    Description: 
Turns out when we did the import for PU, we neglected to bring over the per-service config
changes that are required to support it.  This didn't show during all our development because
we were only checking on the same stack.

This jira brings in those changes such that we are correctly creating and reverting configs
when crossing stack versions.

  was:
In some cases, when downgrading an EU at finalize, the {{cluster-env}} configuration is not
being set correctly to enabled.  It looks like some entities are not being merged:
{noformat}
ambari=# select config_id, type_name, stack_id, version, version_tag, selected, unmapped from
ambari.clusterconfig where type_name = 'cluster-env' order by version_tag;
 config_id |  type_name  | stack_id | version |     version_tag      | selected | unmapped
-----------+-------------+----------+---------+----------------------+----------+----------
        43 | cluster-env |        8 |       1 | version1             |        0 |        0
        54 | cluster-env |        8 |       2 | version1507910265301 |        0 |        0
       102 | cluster-env |        8 |       3 | version1507917459553 |        0 |        0
       113 | cluster-env |        6 |       4 | version1507917549402 |        0 |        0
{noformat}


> Restart of random service could fail during express downgrade
> -------------------------------------------------------------
>
>                 Key: AMBARI-22240
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22240
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 2.6.0
>
>
> Turns out when we did the import for PU, we neglected to bring over the per-service config
changes that are required to support it.  This didn't show during all our development because
we were only checking on the same stack.
> This jira brings in those changes such that we are correctly creating and reverting configs
when crossing stack versions.



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

Mime
View raw message