[
https://issues.apache.org/jira/browse/AMBARI-20510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933948#comment-15933948
]
Hudson commented on AMBARI-20510:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7094 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7094/])
AMBARI-20510. Oozie Database URL property was changed by itself (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a13e96e755f5daf692375b15bd32767eda987b6d])
* (add) ambari-web/test/mixins/common/loading_overlay_support_test.js
* (edit) ambari-web/app/controllers/main/service/info/configs.js
* (edit) ambari-web/app/styles/application.less
* (edit) ambari-web/app/mixins.js
* (edit) ambari-web/app/templates/common/configs/service_config_layout_tab.hbs
* (edit) ambari-web/app/styles/config_history_flow.less
* (edit) ambari-web/app/views/common/configs/service_config_layout_tab_view.js
* (edit) ambari-web/app/views/common/configs/config_category_container_view.js
* (add) ambari-web/app/mixins/common/loading_overlay_support.js
* (edit) ambari-web/app/assets/test/tests.js
> Oozie Database URL property was changed by itself
> -------------------------------------------------
>
> Key: AMBARI-20510
> URL: https://issues.apache.org/jira/browse/AMBARI-20510
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.5.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-20510.patch
>
>
> After investigation, I figured out, that in our tests when we trying to setup
> config on Oozie tab application replaces the correct Oozie DB URL with the
> wrong one.
> You can see this on video 1:07-1:11.
> Looks like StackAdvisor response received twice.
> When we choose "Existing MySQL/MaridDB Database" Database URL property
> changed according the value with "Oozie Server host", test changed it as
> needed (according to pattern)
> OOZIE_DB_URL = "jdbc:mysql://" +
> AmbariProperties.INSTALL_EXTERNAL_DB_HOST_NAME + "/" + "ooziedb";
> and immediately this property was changed to the old one
> go to HDFS configs
> in chrome dev console select Network, set throttling -> GPRS
> change "NameNode Java heap size"
> go to Advanced (config tab) and change "NameNode new generation size"
> once you will get response for recommendations, value of "NameNode new
> generation size" will be changed to recommended one
> If you have bad internet connection you can make a stack of recommendation
> requests, that will hang in pending state, and once resolved will apply
> recommended values
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
