[ 
https://issues.apache.org/jira/browse/AMBARI-12264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613712#comment-14613712
 ] 

Hudson commented on AMBARI-12264:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.1 #165 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/165/])
AMBARI-12264 - Some Execution Commands Send Stale Configs During Upgrade 
Causing Invalid Alerts (jonathanhurley) (jhurley: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=18bfe58a2d23db6b3e44059e4f04a7ffcd1f0adf)
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderHDP22Test.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariActionExecutionHelper.java
* ambari-server/src/test/resources/stacks/HDP/2.2.0/upgrades/upgrade_test.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java


> Some Execution Commands Send Stale Configs During Upgrade Causing Invalid 
> Alerts
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-12264
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12264
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Blocker
>             Fix For: 2.1.0
>
>
> During an upgrade, the alert check for hive transitions to the new port, 
> {{10010}} and begins returning valid checks once the upgraded hive server 
> starts up on the new port. 
> However, after the upgrade is finalized, it is observed that the 
> configurations sent down to the agents contains the old hive thrift port, 
> {{10000}} from before the upgrade ran. 
> Restarting the agents corrects the problems since the configurations in 
> ambari server are still correct.
> The problem is that some commands, namely, {{ACTIONEXECUTE}} must also set
> - {code}
>     "forceRefreshConfigTagsBeforeExecution": [
>         "*"
>     ],
> {code}
> on the {{ExecutionCommands}} being sent down.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to