[jira] [Commented] (AMBARI-22001) Add service wizard stuck at step 8
[ https://issues.apache.org/jira/browse/AMBARI-22001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172667#comment-16172667 ] Hudson commented on AMBARI-22001: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8098 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8098/]) AMBARI-22001. Add service wizard stuck at step 8. (Jaimin) (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=87c4205c21489cfe8bab160fb82e3429c4fb832e]) * (edit) ambari-web/app/controllers/wizard/step8_controller.js > Add service wizard stuck at step 8 > -- > > Key: AMBARI-22001 > URL: https://issues.apache.org/jira/browse/AMBARI-22001 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-22001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21985) Option to skip Host Check during the host add wizard
[ https://issues.apache.org/jira/browse/AMBARI-21985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172644#comment-16172644 ] Hudson commented on AMBARI-21985: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8097 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8097/]) AMBARI-21985. Option to skip Host Check during the host add wizard. (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=878dc6ac72b9d5d87a5f6c21991290886459eede]) * (edit) ambari-web/app/config.js * (edit) ambari-web/app/controllers/wizard/step2_controller.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/mixins/main/host/details/actions/check_host.js * (edit) ambari-web/app/templates/wizard/step2.hbs * (edit) ambari-web/app/views/wizard/step2_view.js > Option to skip Host Check during the host add wizard > > > Key: AMBARI-21985 > URL: https://issues.apache.org/jira/browse/AMBARI-21985 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-21985.patch > > > some times we see customers were not able to add the new hosts to cluster. > message says it is checking for potential problems but it never gets > completed. because of that customers were not able to add the hosts. but > after that they were able to add the hosts with API call. This allows a the > administrator to skip Host Check after a due warning > Attach one or more files to this issue -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21954) Option to skip Host Check during the host add wizard
[ https://issues.apache.org/jira/browse/AMBARI-21954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172635#comment-16172635 ] Hudson commented on AMBARI-21954: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #250 (See [https://builds.apache.org/job/Ambari-branch-2.6/250/]) AMBARI-21954. Option to skip Host Check during the host add wizard. (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f49cf54e9655a9f99b33cce52436edf34c372676]) * (edit) ambari-web/app/controllers/wizard/step2_controller.js * (edit) ambari-web/app/config.js * (edit) ambari-web/app/controllers/wizard/step3_controller.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/templates/wizard/step2.hbs * (edit) ambari-web/app/views/wizard/step2_view.js > Option to skip Host Check during the host add wizard > > > Key: AMBARI-21954 > URL: https://issues.apache.org/jira/browse/AMBARI-21954 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.6.0 > > Attachments: AMBARI-21954_branch-2.6.patch, Skip Host Check > checkbox.png, Skip Host Check warning.png > > > some times we see customers were not able to add the new hosts to cluster. > message says it is checking for potential problems but it never gets > completed. because of that customers were not able to add the hosts. but > after that they were able to add the hosts with API call. This allows a the > administrator to skip Host Check after a due warning -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22001) Add service wizard stuck at step 8
[ https://issues.apache.org/jira/browse/AMBARI-22001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-22001: -- Resolution: Fixed Status: Resolved (was: Patch Available) Received +1 on reviewboard. Patch committed to trunk > Add service wizard stuck at step 8 > -- > > Key: AMBARI-22001 > URL: https://issues.apache.org/jira/browse/AMBARI-22001 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-22001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22001) Add service wizard stuck at step 8
[ https://issues.apache.org/jira/browse/AMBARI-22001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-22001: -- Attachment: AMBARI-22001.patch > Add service wizard stuck at step 8 > -- > > Key: AMBARI-22001 > URL: https://issues.apache.org/jira/browse/AMBARI-22001 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-22001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22001) Add service wizard stuck at step 8
[ https://issues.apache.org/jira/browse/AMBARI-22001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-22001: -- Status: Patch Available (was: Open) > Add service wizard stuck at step 8 > -- > > Key: AMBARI-22001 > URL: https://issues.apache.org/jira/browse/AMBARI-22001 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-22001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22001) Add service wizard stuck at step 8
Jaimin Jetly created AMBARI-22001: - Summary: Add service wizard stuck at step 8 Key: AMBARI-22001 URL: https://issues.apache.org/jira/browse/AMBARI-22001 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Jaimin Jetly Assignee: Jaimin Jetly Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21985) Option to skip Host Check during the host add wizard
[ https://issues.apache.org/jira/browse/AMBARI-21985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-21985: -- Resolution: Fixed Status: Resolved (was: Patch Available) Patch received +1 on reviewboard. Patch committed to trunk. > Option to skip Host Check during the host add wizard > > > Key: AMBARI-21985 > URL: https://issues.apache.org/jira/browse/AMBARI-21985 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-21985.patch > > > some times we see customers were not able to add the new hosts to cluster. > message says it is checking for potential problems but it never gets > completed. because of that customers were not able to add the hosts. but > after that they were able to add the hosts with API call. This allows a the > administrator to skip Host Check after a due warning > Attach one or more files to this issue -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21954) Option to skip Host Check during the host add wizard
[ https://issues.apache.org/jira/browse/AMBARI-21954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-21954: -- Resolution: Fixed Status: Resolved (was: Patch Available) Patch received +1 on reviewboard. Patch committed to branch-2.6 > Option to skip Host Check during the host add wizard > > > Key: AMBARI-21954 > URL: https://issues.apache.org/jira/browse/AMBARI-21954 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.6.0 > > Attachments: AMBARI-21954_branch-2.6.patch, Skip Host Check > checkbox.png, Skip Host Check warning.png > > > some times we see customers were not able to add the new hosts to cluster. > message says it is checking for potential problems but it never gets > completed. because of that customers were not able to add the hosts. but > after that they were able to add the hosts with API call. This allows a the > administrator to skip Host Check after a due warning -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21966) "Next" button on "Assign Masters" page gets disabled when installing Ambari
[ https://issues.apache.org/jira/browse/AMBARI-21966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172573#comment-16172573 ] Hudson commented on AMBARI-21966: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #249 (See [https://builds.apache.org/job/Ambari-branch-2.6/249/]) Revert "AMBARI-21966. "Next" button on "Assign Masters" page gets (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1140bbc077aa96df395a06a15c18cd281a3839e3]) * (edit) ambari-web/app/mixins/wizard/assign_master_components.js > "Next" button on "Assign Masters" page gets disabled when installing Ambari > --- > > Key: AMBARI-21966 > URL: https://issues.apache.org/jira/browse/AMBARI-21966 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21966_branch-2.6.patch, AMBARI-21966.patch > > > "Next" button on "Assign Masters" page (step 5) gets disabled if you revisit > the page from "Assign Slaves and Clients" page (step 6) by pressing "Back" > button when installing Ambari. > To enable the "Next" button again, we need to refresh the page in Browser. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22000) Select Hosts page while enabling HSI does not load
[ https://issues.apache.org/jira/browse/AMBARI-22000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly reassigned AMBARI-22000: - Assignee: (was: Jaimin Jetly) > Select Hosts page while enabling HSI does not load > -- > > Key: AMBARI-22000 > URL: https://issues.apache.org/jira/browse/AMBARI-22000 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Jaimin Jetly >Priority: Critical > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22000) Select Hosts page while enabling HSI does not load
Jaimin Jetly created AMBARI-22000: - Summary: Select Hosts page while enabling HSI does not load Key: AMBARI-22000 URL: https://issues.apache.org/jira/browse/AMBARI-22000 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Jaimin Jetly Assignee: Jaimin Jetly Priority: Critical Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172485#comment-16172485
]
Hudson commented on AMBARI-21917:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8096 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8096/])
AMBARI-21917. Some services had issue coming up after express upgrade on
(swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=23e080aba77ecddf69a16b973764f3bcb4b15607])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/metadata/CachedRoleCommandOrderProvider.java
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172467#comment-16172467
]
Hudson commented on AMBARI-21917:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #248 (See
[https://builds.apache.org/job/Ambari-branch-2.6/248/])
AMBARI-21917. Some services had issue coming up after express upgrade on
(swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3e8ba2a1f1b4bc8d4152492cf2fd65895111d926])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/metadata/CachedRoleCommandOrderProvider.java
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21999) Always Take Target Read-Only Properties On Stack Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172438#comment-16172438
]
Hadoop QA commented on AMBARI-21999:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887950/AMBARI-21999.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12290//console
This message is automatically generated.
> Always Take Target Read-Only Properties On Stack Upgrade
>
>
> Key: AMBARI-21999
> URL: https://issues.apache.org/jira/browse/AMBARI-21999
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21999.patch
>
>
> STR:
> - Install a stack, such as HDP 2.3
> - Modify the {{cluster-env/stack_features}} structure
> - Upgrade to HDP 2.6
> The auto-merge which happens can't properly merge
> {{cluster-env/stack_features}} since it has deviated from the stock values of
> HDP 2.3. This is dangerous since this is needed for proper operation.
> Because it's defined as a read-only value, we should be able to detect this
> in the auto-merge fro the upgrade and force it to the new stack's default
> value...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172435#comment-16172435
]
Hadoop QA commented on AMBARI-21917:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887980/AMBARI-21917.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12289//console
This message is automatically generated.
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172404#comment-16172404
]
Aravindan Vijayan commented on AMBARI-21917:
+1
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21145) allow wildcard for log directory folder in the path component of Logfeeder input
[ https://issues.apache.org/jira/browse/AMBARI-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172403#comment-16172403 ] Juanjo Marron commented on AMBARI-21145: Can we confirm this JIRA has been resolved by AMBARI-21387? In that case it could be marked as resolved > allow wildcard for log directory folder in the path component of Logfeeder > input > > > Key: AMBARI-21145 > URL: https://issues.apache.org/jira/browse/AMBARI-21145 > Project: Ambari > Issue Type: Improvement > Components: logsearch >Affects Versions: 2.5.0 >Reporter: Keta Patel >Assignee: Keta Patel >Priority: Minor > > The wildcard processing in Logfeeder is carried out only for the last file > component in the log path. For a few services, where there are multiple log > folders and log files from each of the folders is desired to be parsed in > Logsearch UI, the lack of a wildcard processing for the previous portions > becomes an issue. Hence, introducing wildcard processing for the log > directory part of the "path" in the Logfeeder's input for the service will > help resolve this issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-21917:
-
Attachment: AMBARI-21917.patch
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-21917:
-
Status: Patch Available (was: Open)
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172400#comment-16172400
]
Siddharth Wagle commented on AMBARI-21917:
--
Speculative patch awaiting test results.
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21917.patch
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21917) Some services had issue coming up after express upgrade on IOP clusters
[
https://issues.apache.org/jira/browse/AMBARI-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-21917:
-
Attachment: (was: AMBARI-21917.patch)
> Some services had issue coming up after express upgrade on IOP clusters
> ---
>
> Key: AMBARI-21917
> URL: https://issues.apache.org/jira/browse/AMBARI-21917
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.0
>
>
> The RCO cache gets cleared on an upgrade to make sure new RCO is loaded.
> However, certain test environments have reported seeing incorrect / older RCO
> still in effect after Finalize and the operations failing due to this.
> The server log does indicate RCO getting cleared:
> {code}
> 24 Aug 2017 17:15:26,701 INFO [Server Action Executor Worker 1509]
> StackUpgradeFinishListener:92 - Clearing RCO cache
> {code}
> But the initialization statements are missing. Making a defensive patch to
> for re-creation of RCO.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21999) Always Take Target Read-Only Properties On Stack Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21999:
-
Attachment: AMBARI-21999.patch
> Always Take Target Read-Only Properties On Stack Upgrade
>
>
> Key: AMBARI-21999
> URL: https://issues.apache.org/jira/browse/AMBARI-21999
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21999.patch
>
>
> STR:
> - Install a stack, such as HDP 2.3
> - Modify the {{cluster-env/stack_features}} structure
> - Upgrade to HDP 2.6
> The auto-merge which happens can't properly merge
> {{cluster-env/stack_features}} since it has deviated from the stock values of
> HDP 2.3. This is dangerous since this is needed for proper operation.
> Because it's defined as a read-only value, we should be able to detect this
> in the auto-merge fro the upgrade and force it to the new stack's default
> value...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21999) Always Take Target Read-Only Properties On Stack Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21999:
-
Status: Patch Available (was: Open)
> Always Take Target Read-Only Properties On Stack Upgrade
>
>
> Key: AMBARI-21999
> URL: https://issues.apache.org/jira/browse/AMBARI-21999
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21999.patch
>
>
> STR:
> - Install a stack, such as HDP 2.3
> - Modify the {{cluster-env/stack_features}} structure
> - Upgrade to HDP 2.6
> The auto-merge which happens can't properly merge
> {{cluster-env/stack_features}} since it has deviated from the stock values of
> HDP 2.3. This is dangerous since this is needed for proper operation.
> Because it's defined as a read-only value, we should be able to detect this
> in the auto-merge fro the upgrade and force it to the new stack's default
> value...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172131#comment-16172131 ] Hudson commented on AMBARI-21971: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8095 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8095/]) Revert "AMBARI-21971. Fix compilation with java7" (Nishant: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=baa16567244e7246f5cc7cd964b1fba81bc21447]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/DruidHighAvailabilityCheckTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DruidHighAvailabilityCheck.java > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21971.1.patch, AMBARI-21971.2.patch, > AMBARI-21971-ADDENDUM.patch, AMBARI-21971.patch > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21998) Ambari upgrade don't delete stale constraints
[
https://issues.apache.org/jira/browse/AMBARI-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172094#comment-16172094
]
Hadoop QA commented on AMBARI-21998:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887923/AMBARI-21998.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12288//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12288//console
This message is automatically generated.
> Ambari upgrade don't delete stale constraints
> -
>
> Key: AMBARI-21998
> URL: https://issues.apache.org/jira/browse/AMBARI-21998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Attachments: AMBARI-21998.patch
>
>
> During Ambari upgrade from 2.2.2 to 2.5 I discovered that some UNIQUE
> constraints are definned without name in older Ambari versions, and then
> altered by name in UpgadeCatalogs/newer DDLs.
> For example:
> Ambari 2.2.2
> https://github.com/apache/ambari/blob/branch-2.2.2/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
> {code} UNIQUE (ldap_user, user_name));{code}
> Ambari-2.4.0
> https://github.com/apache/ambari/blob/branch-2.4/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql#L288
> {code} CONSTRAINT UNQ_users_0 UNIQUE (user_name, user_type)){code}
> As a result, during upgrade from Ambari 2.2.2 to Ambari 2.5.0, the stale
> unique constraint with default name is not deleted.
> That will reproduce on Postgres for any upgrade path that includes these
> versions.
> {code}ambari=# \d+ users
> Table "ambari.users"
> Column |Type | Modifiers
> | Storage | Description
> ---+-++--+-
> user_id | integer | not null
>| plain|
> principal_id | bigint | not null
>| plain|
> ldap_user | integer | not null default 0
>| plain|
> user_name | character varying(255) | not null
>| extended |
> create_time | timestamp without time zone | default now()
>| plain|
> user_password | character varying(255) |
>| extended |
> active| integer | not null default 1
>| plain|
> active_widget_layouts | character varying(1024) | default NULL::character
> varying| extended |
> user_type | character varying(255) | default
> 'LOCAL'::character varying | extended |
> Indexes:
> "users_pkey" PRIMARY KEY, btree (user_id)
> "unq_users_0" UNIQUE, btree (user_name, user_type)
> "users_ldap_user_key" UNIQUE, btree (ldap_user, user_name)
> Foreign-key constraints:
> "fk_users_principal_id" FOREIGN KEY (principal_id) REFERENCES
> adminprincipal(principal_id)
> Referenced by:
> TABLE "members" CONSTRAINT "fk_members_user_id" FOREIGN KEY (user_id)
> REFERENCES users(user_id)
> Has OIDs: no
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21997) Unsupported major.minor version 52.0 when using com.networknt:json-schema-validator
[
https://issues.apache.org/jira/browse/AMBARI-21997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172082#comment-16172082
]
Hudson commented on AMBARI-21997:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8094 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8094/])
AMBARI-21997. Unsupported major.minor version 52.0 when using (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9be7569b96a99932758065ff2289399eecadf024])
* (edit) ambari-server/pom.xml
> Unsupported major.minor version 52.0 when using
> com.networknt:json-schema-validator
> ---
>
> Key: AMBARI-21997
> URL: https://issues.apache.org/jira/browse/AMBARI-21997
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21997_branch-2.6_01.patch,
> AMBARI-21997_trunk_01.patch
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test failed:
> java.lang.UnsupportedClassVersionError: com/networknt/schema/JsonSchema :
> Unsupported major.minor version 52.0 -> [Help 1]
> {code}
> *Cause*
> com.networknt:json-schema-validator:0.1.7 is compiled for Java 1.8, causing
> unit tests to fail when using Java 1.7
> *Solution*
> Use com.networknt:json-schema-validator:0.1.10, which appears to work when
> using either Java 1.7 or Java 1.8.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21999) Always Take Target Read-Only Properties On Stack Upgrade
Jonathan Hurley created AMBARI-21999:
Summary: Always Take Target Read-Only Properties On Stack Upgrade
Key: AMBARI-21999
URL: https://issues.apache.org/jira/browse/AMBARI-21999
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.6.0
STR:
- Install a stack, such as HDP 2.3
- Modify the {{cluster-env/stack_features}} structure
- Upgrade to HDP 2.6
The auto-merge which happens can't properly merge
{{cluster-env/stack_features}} since it has deviated from the stock values of
HDP 2.3. This is dangerous since this is needed for proper operation.
Because it's defined as a read-only value, we should be able to detect this in
the auto-merge fro the upgrade and force it to the new stack's default value...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172058#comment-16172058 ] Nishant Bangarwa commented on AMBARI-21971: --- thanks for the update. Have reverted this in trunk. only committed in branch-2.6 > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21971.1.patch, AMBARI-21971.2.patch, > AMBARI-21971-ADDENDUM.patch, AMBARI-21971.patch > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21997) Unsupported major.minor version 52.0 when using com.networknt:json-schema-validator
[
https://issues.apache.org/jira/browse/AMBARI-21997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172048#comment-16172048
]
Hudson commented on AMBARI-21997:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #247 (See
[https://builds.apache.org/job/Ambari-branch-2.6/247/])
AMBARI-21997. Unsupported major.minor version 52.0 when using (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b58fc71fe2a8fcca30d8731b860f499c286a9fea])
* (edit) ambari-server/pom.xml
> Unsupported major.minor version 52.0 when using
> com.networknt:json-schema-validator
> ---
>
> Key: AMBARI-21997
> URL: https://issues.apache.org/jira/browse/AMBARI-21997
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21997_branch-2.6_01.patch,
> AMBARI-21997_trunk_01.patch
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test failed:
> java.lang.UnsupportedClassVersionError: com/networknt/schema/JsonSchema :
> Unsupported major.minor version 52.0 -> [Help 1]
> {code}
> *Cause*
> com.networknt:json-schema-validator:0.1.7 is compiled for Java 1.8, causing
> unit tests to fail when using Java 1.7
> *Solution*
> Use com.networknt:json-schema-validator:0.1.10, which appears to work when
> using either Java 1.7 or Java 1.8.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172041#comment-16172041 ] Olivér Szabó commented on AMBARI-21971: --- hi, [~nishantbangarwa] I do not think the java7 fix part is required for trunk (only for branch-2.6): take a look: https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development from 3.0, java 8 is required (but i guess the issue happened because the feature was developed on trunk) > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21971.1.patch, AMBARI-21971.2.patch, > AMBARI-21971-ADDENDUM.patch, AMBARI-21971.patch > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21996) Provide maintenance mode off count for component
[
https://issues.apache.org/jira/browse/AMBARI-21996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172031#comment-16172031
]
Hadoop QA commented on AMBARI-21996:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887926/AMBARI-21996.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12287//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12287//console
This message is automatically generated.
> Provide maintenance mode off count for component
>
>
> Key: AMBARI-21996
> URL: https://issues.apache.org/jira/browse/AMBARI-21996
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Ishan Bhatt
>Assignee: Dmytro Sen
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-21996.patch
>
>
> Similar to "installed_count" property which provides the info about how many
> hostComponents are STOPPED, can we add an
> InstalledWithMaintenanceModeOffCount property which provides the number of
> hostComponents which are stopped AND in maintenance mode? This is required to
> compute whether start/start all button should be enabled or not.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172027#comment-16172027 ] Hudson commented on AMBARI-21971: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8093 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8093/]) AMBARI-21971. Fix compilation with java7 (Nishant: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f7c9e1ee5799632ce8ce2d68a56dbdb2aabf29d4]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DruidHighAvailabilityCheck.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/DruidHighAvailabilityCheckTest.java > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21971.1.patch, AMBARI-21971.2.patch, > AMBARI-21971-ADDENDUM.patch, AMBARI-21971.patch > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21997) Unsupported major.minor version 52.0 when using com.networknt:json-schema-validator
[
https://issues.apache.org/jira/browse/AMBARI-21997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-21997:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 9be7569b96a99932758065ff2289399eecadf024
Author: Robert Levas
Date: Tue Sep 19 12:45:10 2017 -0400
{noformat}
Committed to branch-2.6
{noformat}
commit b58fc71fe2a8fcca30d8731b860f499c286a9fea
Author: Robert Levas
Date: Tue Sep 19 12:46:20 2017 -0400
{noformat}
> Unsupported major.minor version 52.0 when using
> com.networknt:json-schema-validator
> ---
>
> Key: AMBARI-21997
> URL: https://issues.apache.org/jira/browse/AMBARI-21997
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21997_branch-2.6_01.patch,
> AMBARI-21997_trunk_01.patch
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test failed:
> java.lang.UnsupportedClassVersionError: com/networknt/schema/JsonSchema :
> Unsupported major.minor version 52.0 -> [Help 1]
> {code}
> *Cause*
> com.networknt:json-schema-validator:0.1.7 is compiled for Java 1.8, causing
> unit tests to fail when using Java 1.7
> *Solution*
> Use com.networknt:json-schema-validator:0.1.10, which appears to work when
> using either Java 1.7 or Java 1.8.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21995) Revise log message for component version not found
[
https://issues.apache.org/jira/browse/AMBARI-21995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171985#comment-16171985
]
Hudson commented on AMBARI-21995:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8092 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8092/])
AMBARI-21995. Revise log message for component version not found (ncole)
(ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cc70c2b5bdf7f889fe2c24fcbbe11945ee2e3a33])
* (edit)
ambari-common/src/main/python/resource_management/libraries/script/script.py
> Revise log message for component version not found
> --
>
> Key: AMBARI-21995
> URL: https://issues.apache.org/jira/browse/AMBARI-21995
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
> Fix For: 2.6.0
>
> Attachments: AMBARI-21995.patch
>
>
> A confusing log message is being printed because it is executed from the
> {{before-INSTALL}} hook.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21996) Provide maintenance mode off count for component
[ https://issues.apache.org/jira/browse/AMBARI-21996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21996: Status: Patch Available (was: In Progress) > Provide maintenance mode off count for component > > > Key: AMBARI-21996 > URL: https://issues.apache.org/jira/browse/AMBARI-21996 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Ishan Bhatt >Assignee: Dmytro Sen > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-21996.patch > > > Similar to "installed_count" property which provides the info about how many > hostComponents are STOPPED, can we add an > InstalledWithMaintenanceModeOffCount property which provides the number of > hostComponents which are stopped AND in maintenance mode? This is required to > compute whether start/start all button should be enabled or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21996) Provide maintenance mode off count for component
[ https://issues.apache.org/jira/browse/AMBARI-21996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21996: Attachment: AMBARI-21996.patch > Provide maintenance mode off count for component > > > Key: AMBARI-21996 > URL: https://issues.apache.org/jira/browse/AMBARI-21996 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Ishan Bhatt >Assignee: Dmytro Sen > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-21996.patch > > > Similar to "installed_count" property which provides the info about how many > hostComponents are STOPPED, can we add an > InstalledWithMaintenanceModeOffCount property which provides the number of > hostComponents which are stopped AND in maintenance mode? This is required to > compute whether start/start all button should be enabled or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21997) Unsupported major.minor version 52.0 when using com.networknt:json-schema-validator
[
https://issues.apache.org/jira/browse/AMBARI-21997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171981#comment-16171981
]
Hadoop QA commented on AMBARI-21997:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887918/AMBARI-21997_branch-2.6_01.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12286//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12286//console
This message is automatically generated.
> Unsupported major.minor version 52.0 when using
> com.networknt:json-schema-validator
> ---
>
> Key: AMBARI-21997
> URL: https://issues.apache.org/jira/browse/AMBARI-21997
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21997_branch-2.6_01.patch,
> AMBARI-21997_trunk_01.patch
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test failed:
> java.lang.UnsupportedClassVersionError: com/networknt/schema/JsonSchema :
> Unsupported major.minor version 52.0 -> [Help 1]
> {code}
> *Cause*
> com.networknt:json-schema-validator:0.1.7 is compiled for Java 1.8, causing
> unit tests to fail when using Java 1.7
> *Solution*
> Use com.networknt:json-schema-validator:0.1.10, which appears to work when
> using either Java 1.7 or Java 1.8.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21996) Provide maintenance mode off count for component
[ https://issues.apache.org/jira/browse/AMBARI-21996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21996: Attachment: (was: AMBARI-21996.patch) > Provide maintenance mode off count for component > > > Key: AMBARI-21996 > URL: https://issues.apache.org/jira/browse/AMBARI-21996 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Ishan Bhatt >Assignee: Dmytro Sen > Fix For: trunk, 3.0.0 > > > Similar to "installed_count" property which provides the info about how many > hostComponents are STOPPED, can we add an > InstalledWithMaintenanceModeOffCount property which provides the number of > hostComponents which are stopped AND in maintenance mode? This is required to > compute whether start/start all button should be enabled or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21996) Provide maintenance mode off count for component
[ https://issues.apache.org/jira/browse/AMBARI-21996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-21996: Attachment: AMBARI-21996.patch > Provide maintenance mode off count for component > > > Key: AMBARI-21996 > URL: https://issues.apache.org/jira/browse/AMBARI-21996 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Ishan Bhatt >Assignee: Dmytro Sen > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-21996.patch > > > Similar to "installed_count" property which provides the info about how many > hostComponents are STOPPED, can we add an > InstalledWithMaintenanceModeOffCount property which provides the number of > hostComponents which are stopped AND in maintenance mode? This is required to > compute whether start/start all button should be enabled or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21998) Ambari upgrade don't delete stale constraints
[
https://issues.apache.org/jira/browse/AMBARI-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21998:
Status: Patch Available (was: Open)
> Ambari upgrade don't delete stale constraints
> -
>
> Key: AMBARI-21998
> URL: https://issues.apache.org/jira/browse/AMBARI-21998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Attachments: AMBARI-21998.patch
>
>
> During Ambari upgrade from 2.2.2 to 2.5 I discovered that some UNIQUE
> constraints are definned without name in older Ambari versions, and then
> altered by name in UpgadeCatalogs/newer DDLs.
> For example:
> Ambari 2.2.2
> https://github.com/apache/ambari/blob/branch-2.2.2/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
> {code} UNIQUE (ldap_user, user_name));{code}
> Ambari-2.4.0
> https://github.com/apache/ambari/blob/branch-2.4/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql#L288
> {code} CONSTRAINT UNQ_users_0 UNIQUE (user_name, user_type)){code}
> As a result, during upgrade from Ambari 2.2.2 to Ambari 2.5.0, the stale
> unique constraint with default name is not deleted.
> That will reproduce on Postgres for any upgrade path that includes these
> versions.
> {code}ambari=# \d+ users
> Table "ambari.users"
> Column |Type | Modifiers
> | Storage | Description
> ---+-++--+-
> user_id | integer | not null
>| plain|
> principal_id | bigint | not null
>| plain|
> ldap_user | integer | not null default 0
>| plain|
> user_name | character varying(255) | not null
>| extended |
> create_time | timestamp without time zone | default now()
>| plain|
> user_password | character varying(255) |
>| extended |
> active| integer | not null default 1
>| plain|
> active_widget_layouts | character varying(1024) | default NULL::character
> varying| extended |
> user_type | character varying(255) | default
> 'LOCAL'::character varying | extended |
> Indexes:
> "users_pkey" PRIMARY KEY, btree (user_id)
> "unq_users_0" UNIQUE, btree (user_name, user_type)
> "users_ldap_user_key" UNIQUE, btree (ldap_user, user_name)
> Foreign-key constraints:
> "fk_users_principal_id" FOREIGN KEY (principal_id) REFERENCES
> adminprincipal(principal_id)
> Referenced by:
> TABLE "members" CONSTRAINT "fk_members_user_id" FOREIGN KEY (user_id)
> REFERENCES users(user_id)
> Has OIDs: no
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21998) Ambari upgrade don't delete stale constraints
[
https://issues.apache.org/jira/browse/AMBARI-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21998:
Attachment: AMBARI-21998.patch
> Ambari upgrade don't delete stale constraints
> -
>
> Key: AMBARI-21998
> URL: https://issues.apache.org/jira/browse/AMBARI-21998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Attachments: AMBARI-21998.patch
>
>
> During Ambari upgrade from 2.2.2 to 2.5 I discovered that some UNIQUE
> constraints are definned without name in older Ambari versions, and then
> altered by name in UpgadeCatalogs/newer DDLs.
> For example:
> Ambari 2.2.2
> https://github.com/apache/ambari/blob/branch-2.2.2/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
> {code} UNIQUE (ldap_user, user_name));{code}
> Ambari-2.4.0
> https://github.com/apache/ambari/blob/branch-2.4/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql#L288
> {code} CONSTRAINT UNQ_users_0 UNIQUE (user_name, user_type)){code}
> As a result, during upgrade from Ambari 2.2.2 to Ambari 2.5.0, the stale
> unique constraint with default name is not deleted.
> That will reproduce on Postgres for any upgrade path that includes these
> versions.
> {code}ambari=# \d+ users
> Table "ambari.users"
> Column |Type | Modifiers
> | Storage | Description
> ---+-++--+-
> user_id | integer | not null
>| plain|
> principal_id | bigint | not null
>| plain|
> ldap_user | integer | not null default 0
>| plain|
> user_name | character varying(255) | not null
>| extended |
> create_time | timestamp without time zone | default now()
>| plain|
> user_password | character varying(255) |
>| extended |
> active| integer | not null default 1
>| plain|
> active_widget_layouts | character varying(1024) | default NULL::character
> varying| extended |
> user_type | character varying(255) | default
> 'LOCAL'::character varying | extended |
> Indexes:
> "users_pkey" PRIMARY KEY, btree (user_id)
> "unq_users_0" UNIQUE, btree (user_name, user_type)
> "users_ldap_user_key" UNIQUE, btree (ldap_user, user_name)
> Foreign-key constraints:
> "fk_users_principal_id" FOREIGN KEY (principal_id) REFERENCES
> adminprincipal(principal_id)
> Referenced by:
> TABLE "members" CONSTRAINT "fk_members_user_id" FOREIGN KEY (user_id)
> REFERENCES users(user_id)
> Has OIDs: no
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21998) Ambari upgrade don't delete stale constraints
[
https://issues.apache.org/jira/browse/AMBARI-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21998:
Component/s: ambari-server
> Ambari upgrade don't delete stale constraints
> -
>
> Key: AMBARI-21998
> URL: https://issues.apache.org/jira/browse/AMBARI-21998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
>
> During Ambari upgrade from 2.2.2 to 2.5 I discovered that some UNIQUE
> constraints are definned without name in older Ambari versions, and then
> altered by name in UpgadeCatalogs/newer DDLs.
> For example:
> Ambari 2.2.2
> https://github.com/apache/ambari/blob/branch-2.2.2/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
> {code} UNIQUE (ldap_user, user_name));{code}
> Ambari-2.4.0
> https://github.com/apache/ambari/blob/branch-2.4/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql#L288
> {code} CONSTRAINT UNQ_users_0 UNIQUE (user_name, user_type)){code}
> As a result, during upgrade from Ambari 2.2.2 to Ambari 2.5.0, the stale
> unique constraint with default name is not deleted.
> That will reproduce on Postgres for any upgrade path that includes these
> versions.
> {code}ambari=# \d+ users
> Table "ambari.users"
> Column |Type | Modifiers
> | Storage | Description
> ---+-++--+-
> user_id | integer | not null
>| plain|
> principal_id | bigint | not null
>| plain|
> ldap_user | integer | not null default 0
>| plain|
> user_name | character varying(255) | not null
>| extended |
> create_time | timestamp without time zone | default now()
>| plain|
> user_password | character varying(255) |
>| extended |
> active| integer | not null default 1
>| plain|
> active_widget_layouts | character varying(1024) | default NULL::character
> varying| extended |
> user_type | character varying(255) | default
> 'LOCAL'::character varying | extended |
> Indexes:
> "users_pkey" PRIMARY KEY, btree (user_id)
> "unq_users_0" UNIQUE, btree (user_name, user_type)
> "users_ldap_user_key" UNIQUE, btree (ldap_user, user_name)
> Foreign-key constraints:
> "fk_users_principal_id" FOREIGN KEY (principal_id) REFERENCES
> adminprincipal(principal_id)
> Referenced by:
> TABLE "members" CONSTRAINT "fk_members_user_id" FOREIGN KEY (user_id)
> REFERENCES users(user_id)
> Has OIDs: no
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21998) Ambari upgrade don't delete stale constraints
Dmitry Lysnichenko created AMBARI-21998:
---
Summary: Ambari upgrade don't delete stale constraints
Key: AMBARI-21998
URL: https://issues.apache.org/jira/browse/AMBARI-21998
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Priority: Critical
During Ambari upgrade from 2.2.2 to 2.5 I discovered that some UNIQUE
constraints are definned without name in older Ambari versions, and then
altered by name in UpgadeCatalogs/newer DDLs.
For example:
Ambari 2.2.2
https://github.com/apache/ambari/blob/branch-2.2.2/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
{code} UNIQUE (ldap_user, user_name));{code}
Ambari-2.4.0
https://github.com/apache/ambari/blob/branch-2.4/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql#L288
{code} CONSTRAINT UNQ_users_0 UNIQUE (user_name, user_type)){code}
As a result, during upgrade from Ambari 2.2.2 to Ambari 2.5.0, the stale unique
constraint with default name is not deleted.
That will reproduce on Postgres for any upgrade path that includes these
versions.
{code}ambari=# \d+ users
Table "ambari.users"
Column |Type | Modifiers
| Storage | Description
---+-++--+-
user_id | integer | not null
| plain|
principal_id | bigint | not null
| plain|
ldap_user | integer | not null default 0
| plain|
user_name | character varying(255) | not null
| extended |
create_time | timestamp without time zone | default now()
| plain|
user_password | character varying(255) |
| extended |
active| integer | not null default 1
| plain|
active_widget_layouts | character varying(1024) | default NULL::character
varying| extended |
user_type | character varying(255) | default
'LOCAL'::character varying | extended |
Indexes:
"users_pkey" PRIMARY KEY, btree (user_id)
"unq_users_0" UNIQUE, btree (user_name, user_type)
"users_ldap_user_key" UNIQUE, btree (ldap_user, user_name)
Foreign-key constraints:
"fk_users_principal_id" FOREIGN KEY (principal_id) REFERENCES
adminprincipal(principal_id)
Referenced by:
TABLE "members" CONSTRAINT "fk_members_user_id" FOREIGN KEY (user_id)
REFERENCES users(user_id)
Has OIDs: no
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21971) Add Druid High Availability Check for Rolling Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21971: -- Attachment: AMBARI-21971-ADDENDUM.patch > Add Druid High Availability Check for Rolling Upgrades > -- > > Key: AMBARI-21971 > URL: https://issues.apache.org/jira/browse/AMBARI-21971 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21971.1.patch, AMBARI-21971.2.patch, > AMBARI-21971-ADDENDUM.patch, AMBARI-21971.patch > > > For Druid Rolling Upgrades check that each druid component is installed on > more than 1 node and is HA enabled. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21995) Revise log message for component version not found
[
https://issues.apache.org/jira/browse/AMBARI-21995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171938#comment-16171938
]
Hudson commented on AMBARI-21995:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #245 (See
[https://builds.apache.org/job/Ambari-branch-2.6/245/])
AMBARI-21995. Revise log message for component version not found (ncole)
(ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f961d8ecb192413c445d45e6976f999a6b7df1fb])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
* (edit)
ambari-common/src/main/python/resource_management/libraries/script/script.py
> Revise log message for component version not found
> --
>
> Key: AMBARI-21995
> URL: https://issues.apache.org/jira/browse/AMBARI-21995
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
> Fix For: 2.6.0
>
> Attachments: AMBARI-21995.patch
>
>
> A confusing log message is being printed because it is executed from the
> {{before-INSTALL}} hook.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21997) Unsupported major.minor version 52.0 when using com.networknt:json-schema-validator
[
https://issues.apache.org/jira/browse/AMBARI-21997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-21997:
--
Status: Patch Available (was: In Progress)
> Unsupported major.minor version 52.0 when using
> com.networknt:json-schema-validator
> ---
>
> Key: AMBARI-21997
> URL: https://issues.apache.org/jira/browse/AMBARI-21997
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21997_branch-2.6_01.patch,
> AMBARI-21997_trunk_01.patch
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test failed:
> java.lang.UnsupportedClassVersionError: com/networknt/schema/JsonSchema :
> Unsupported major.minor version 52.0 -> [Help 1]
> {code}
> *Cause*
> com.networknt:json-schema-validator:0.1.7 is compiled for Java 1.8, causing
> unit tests to fail when using Java 1.7
> *Solution*
> Use com.networknt:json-schema-validator:0.1.10, which appears to work when
> using either Java 1.7 or Java 1.8.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21997) Unsupported major.minor version 52.0 when using com.networknt:json-schema-validator
[
https://issues.apache.org/jira/browse/AMBARI-21997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-21997:
--
Attachment: AMBARI-21997_branch-2.6_01.patch
AMBARI-21997_trunk_01.patch
> Unsupported major.minor version 52.0 when using
> com.networknt:json-schema-validator
> ---
>
> Key: AMBARI-21997
> URL: https://issues.apache.org/jira/browse/AMBARI-21997
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21997_branch-2.6_01.patch,
> AMBARI-21997_trunk_01.patch
>
>
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
> project ambari-server: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test failed:
> java.lang.UnsupportedClassVersionError: com/networknt/schema/JsonSchema :
> Unsupported major.minor version 52.0 -> [Help 1]
> {code}
> *Cause*
> com.networknt:json-schema-validator:0.1.7 is compiled for Java 1.8, causing
> unit tests to fail when using Java 1.7
> *Solution*
> Use com.networknt:json-schema-validator:0.1.10, which appears to work when
> using either Java 1.7 or Java 1.8.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21995) Revise log message for component version not found
[
https://issues.apache.org/jira/browse/AMBARI-21995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-21995.
Resolution: Fixed
> Revise log message for component version not found
> --
>
> Key: AMBARI-21995
> URL: https://issues.apache.org/jira/browse/AMBARI-21995
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
> Fix For: 2.6.0
>
> Attachments: AMBARI-21995.patch
>
>
> A confusing log message is being printed because it is executed from the
> {{before-INSTALL}} hook.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21995) Revise log message for component version not found
[
https://issues.apache.org/jira/browse/AMBARI-21995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-21995:
---
Attachment: AMBARI-21995.patch
> Revise log message for component version not found
> --
>
> Key: AMBARI-21995
> URL: https://issues.apache.org/jira/browse/AMBARI-21995
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
> Fix For: 2.6.0
>
> Attachments: AMBARI-21995.patch
>
>
> A confusing log message is being printed because it is executed from the
> {{before-INSTALL}} hook.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171923#comment-16171923 ] Hudson commented on AMBARI-21994: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8091 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8091/]) AMBARI-21994 Upgrade history view style issue. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b9652bd7b1ea4d5e04a06f8924399ea8a1c64ea2]) * (edit) ambari-web/app/styles/stack_versions.less > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21997) Unsupported major.minor version 52.0 when using com.networknt:json-schema-validator
Robert Levas created AMBARI-21997:
-
Summary: Unsupported major.minor version 52.0 when using
com.networknt:json-schema-validator
Key: AMBARI-21997
URL: https://issues.apache.org/jira/browse/AMBARI-21997
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
Fix For: 2.6.0
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on
project ambari-server: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.20:test failed:
java.lang.UnsupportedClassVersionError: com/networknt/schema/JsonSchema :
Unsupported major.minor version 52.0 -> [Help 1]
{code}
*Cause*
com.networknt:json-schema-validator:0.1.7 is compiled for Java 1.8, causing
unit tests to fail when using Java 1.7
*Solution*
Use com.networknt:json-schema-validator:0.1.10, which appears to work when
using either Java 1.7 or Java 1.8.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21996) Provide maintenance mode off count for component
[ https://issues.apache.org/jira/browse/AMBARI-21996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21996: - Component/s: (was: ambari-web) ambari-server > Provide maintenance mode off count for component > > > Key: AMBARI-21996 > URL: https://issues.apache.org/jira/browse/AMBARI-21996 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Ishan Bhatt >Assignee: Dmytro Sen > Fix For: trunk, 3.0.0 > > > Similar to "installed_count" property which provides the info about how many > hostComponents are STOPPED, can we add an > InstalledWithMaintenanceModeOffCount property which provides the number of > hostComponents which are stopped AND in maintenance mode? This is required to > compute whether start/start all button should be enabled or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21996) Provide maintenance mode off count for component
Ishan Bhatt created AMBARI-21996: Summary: Provide maintenance mode off count for component Key: AMBARI-21996 URL: https://issues.apache.org/jira/browse/AMBARI-21996 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Dmytro Sen Fix For: trunk, 3.0.0 Similar to "installed_count" property which provides the info about how many hostComponents are STOPPED, can we add an InstalledWithMaintenanceModeOffCount property which provides the number of hostComponents which are stopped AND in maintenance mode? This is required to compute whether start/start all button should be enabled or not. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171899#comment-16171899 ] Hudson commented on AMBARI-21994: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #244 (See [https://builds.apache.org/job/Ambari-branch-2.6/244/]) AMBARI-21994 Upgrade history view style issue. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d0d3c49f707ca0f3d2abf79e330942c2e077cb31]) * (edit) ambari-web/app/styles/stack_versions.less > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21994: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171861#comment-16171861 ] Andrii Tkach commented on AMBARI-21994: --- committed to trunk and branch-2.6 > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21994) Upgrade history view style issue
[
https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171847#comment-16171847
]
Hadoop QA commented on AMBARI-21994:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887901/AMBARI-21994.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12285//console
This message is automatically generated.
> Upgrade history view style issue
>
>
> Key: AMBARI-21994
> URL: https://issues.apache.org/jira/browse/AMBARI-21994
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: 1.png, AMBARI-21994.patch
>
>
> Can we make sure all arrows and labels in dropdown are aligned?
> Maybe have to boost the width on the ‘service name’ to accommodate longer
> service names
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21994) Upgrade history view style issue
[
https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171822#comment-16171822
]
Hadoop QA commented on AMBARI-21994:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887901/AMBARI-21994.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12284//console
This message is automatically generated.
> Upgrade history view style issue
>
>
> Key: AMBARI-21994
> URL: https://issues.apache.org/jira/browse/AMBARI-21994
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: 1.png, AMBARI-21994.patch
>
>
> Can we make sure all arrows and labels in dropdown are aligned?
> Maybe have to boost the width on the ‘service name’ to accommodate longer
> service names
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21995) Revise log message for component version not found
Nate Cole created AMBARI-21995:
--
Summary: Revise log message for component version not found
Key: AMBARI-21995
URL: https://issues.apache.org/jira/browse/AMBARI-21995
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 2.6.0
A confusing log message is being printed because it is executed from the
{{before-INSTALL}} hook.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171786#comment-16171786 ] Hudson commented on AMBARI-21993: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8090 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8090/]) AMBARI-21993. Pre upgrade check dialog style issues (alexantonenko) (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7cebdebbdfb6c249945c03e12f203b3fc05fe926]) * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21994: -- Attachment: (was: AMBARI-21994.patch) > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21994: -- Attachment: AMBARI-21994.patch > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171783#comment-16171783 ] Andrii Babiichuk commented on AMBARI-21994: --- +1 for the patch > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21994) Upgrade history view style issue
[
https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171775#comment-16171775
]
Hadoop QA commented on AMBARI-21994:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887900/AMBARI-21994.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12283//console
This message is automatically generated.
> Upgrade history view style issue
>
>
> Key: AMBARI-21994
> URL: https://issues.apache.org/jira/browse/AMBARI-21994
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: 1.png, AMBARI-21994.patch
>
>
> Can we make sure all arrows and labels in dropdown are aligned?
> Maybe have to boost the width on the ‘service name’ to accommodate longer
> service names
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21994: -- Status: Patch Available (was: Open) > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21994: -- Attachment: AMBARI-21994.patch > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, AMBARI-21994.patch > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21970) Enable sticky bit for curl_krb_cache
[
https://issues.apache.org/jira/browse/AMBARI-21970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171765#comment-16171765
]
Hadoop QA commented on AMBARI-21970:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887890/AMBARI-21970.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12281//console
This message is automatically generated.
> Enable sticky bit for curl_krb_cache
>
>
> Key: AMBARI-21970
> URL: https://issues.apache.org/jira/browse/AMBARI-21970
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Krishnama Raju K
>Assignee: Eugene Chekanskiy
>Priority: Minor
> Attachments: AMBARI-21970.patch
>
>
> In secure environment, we see that "/var/lib/ambari-agent/tmp" has sticky bit
> enabled. Trying to enable such permissions ( sticky bit or any other
> permissions ) for "curl_krb_request.py" is being over written after few
> seconds.
> It is observed that the chmod permissions set in "curl_krb_request.py"
> enforces periodic 0777 as shown in below snippet.
> {code:java}
> curl_krb_cache_path = os.path.join(tmp_dir, "curl_krb_cache")
> if not os.path.exists(curl_krb_cache_path):
> os.makedirs(curl_krb_cache_path)
> os.chmod(curl_krb_cache_path, 0777)
> {code}
> Ref:
> https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py
> Hence, code changes need to be done for setting the sticky bit to prevent
> access from users who did not create the specific file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21994) Upgrade history view style issue
Andrii Tkach created AMBARI-21994: - Summary: Upgrade history view style issue Key: AMBARI-21994 URL: https://issues.apache.org/jira/browse/AMBARI-21994 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.6.0 Can we make sure all arrows and labels in dropdown are aligned? Maybe have to boost the width on the ‘service name’ to accommodate longer service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21994) Upgrade history view style issue
[ https://issues.apache.org/jira/browse/AMBARI-21994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21994: -- Attachment: 1.png > Upgrade history view style issue > > > Key: AMBARI-21994 > URL: https://issues.apache.org/jira/browse/AMBARI-21994 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png > > > Can we make sure all arrows and labels in dropdown are aligned? > Maybe have to boost the width on the ‘service name’ to accommodate longer > service names -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171757#comment-16171757 ] Hudson commented on AMBARI-21993: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #243 (See [https://builds.apache.org/job/Ambari-branch-2.6/243/]) AMBARI-21993. Pre upgrade check dialog style issues (alexantonenko) (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=af80df2ec3bc384f8a3ff44ce8fe141f849f0cbb]) * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171726#comment-16171726 ] Hudson commented on AMBARI-21992: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8089 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8089/]) AMBARI-21992. Update Already Installed Icon Appears On Old Repo (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=271fbc7ca83cfb67f7b4d2adec61000c571e8aff]) * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_column_view_test.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171721#comment-16171721 ] Andrii Tkach commented on AMBARI-21993: --- +1 for the patch > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21993) Pre upgrade check dialog style issues
[
https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171714#comment-16171714
]
Hadoop QA commented on AMBARI-21993:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887888/AMBARI-21993_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12279//console
This message is automatically generated.
> Pre upgrade check dialog style issues
> -
>
> Key: AMBARI-21993
> URL: https://issues.apache.org/jira/browse/AMBARI-21993
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch,
> AMBARI-21993_trunk.patch
>
>
> # Top whitespace between text and grey area is to small, but bottom
> whitespace between grey area and button area is to big:
> !1.png|thumbnail!
> # Second text should be the same size as in check while upgrading:
> !2.png|thumbnail! !3.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171677#comment-16171677 ] Hudson commented on AMBARI-21992: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #242 (See [https://builds.apache.org/job/Ambari-branch-2.6/242/]) AMBARI-21992. Update Already Installed Icon Appears On Old Repo (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5fd168a5fc0cab49820a4d394ea3b24c4c7a0422]) * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_column_view_test.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21907) Ambari can demand an invalid python class name (containing hyphens) for the service advisor
[ https://issues.apache.org/jira/browse/AMBARI-21907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diego Santesteban updated AMBARI-21907: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari can demand an invalid python class name (containing hyphens) for the > service advisor > --- > > Key: AMBARI-21907 > URL: https://issues.apache.org/jira/browse/AMBARI-21907 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Diego Santesteban >Assignee: Diego Santesteban > Fix For: trunk, 2.5.3, 2.6.0 > > Attachments: AMBARI-21907.patch > > Original Estimate: 4h > Time Spent: 6h > Remaining Estimate: 0h > > The service advisor class name is created as 'stackName + versionString + > serviceName + "ServiceAdvisor"'. When stackName, versionString or serviceName > contains a hyphen, the class name that Ambari wants is not valid in python. > Ambari should remove non-alphanumeric characters from the service advisor > class name. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21992: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171660#comment-16171660 ] Andrii Tkach commented on AMBARI-21992: --- +1 for the patch > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[
https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171656#comment-16171656
]
Hadoop QA commented on AMBARI-21992:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887883/AMBARI-21992_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12278//console
This message is automatically generated.
> Update Already Installed Icon Appears On Old Repo
> -
>
> Key: AMBARI-21992
> URL: https://issues.apache.org/jira/browse/AMBARI-21992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.6.0
>
> Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch
>
>
> The "Update Available, but already installed." icon appears on repos which
> have previously been applied and then moved off of.
> STR:
> * Install HDP 2.6.0.0 for ZK and Storm
> * Register a PATCH HDP 2.6.0.1 for Storm
> * Apply the patch
> * Register a PATCH HDP 2.6.0.2 for Storm
> * Apply the patch
> The old repo moves into the correct state, but displays the icon indicating
> that Storm is already at the right version.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21970) Enable sticky bit for curl_krb_cache
[
https://issues.apache.org/jira/browse/AMBARI-21970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Chekanskiy reassigned AMBARI-21970:
--
Assignee: Eugene Chekanskiy
> Enable sticky bit for curl_krb_cache
>
>
> Key: AMBARI-21970
> URL: https://issues.apache.org/jira/browse/AMBARI-21970
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Krishnama Raju K
>Assignee: Eugene Chekanskiy
>Priority: Minor
> Attachments: AMBARI-21970.patch
>
>
> In secure environment, we see that "/var/lib/ambari-agent/tmp" has sticky bit
> enabled. Trying to enable such permissions ( sticky bit or any other
> permissions ) for "curl_krb_request.py" is being over written after few
> seconds.
> It is observed that the chmod permissions set in "curl_krb_request.py"
> enforces periodic 0777 as shown in below snippet.
> {code:java}
> curl_krb_cache_path = os.path.join(tmp_dir, "curl_krb_cache")
> if not os.path.exists(curl_krb_cache_path):
> os.makedirs(curl_krb_cache_path)
> os.chmod(curl_krb_cache_path, 0777)
> {code}
> Ref:
> https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py
> Hence, code changes need to be done for setting the sticky bit to prevent
> access from users who did not create the specific file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21970) Enable sticky bit for curl_krb_cache
[
https://issues.apache.org/jira/browse/AMBARI-21970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Chekanskiy updated AMBARI-21970:
---
Status: Patch Available (was: Open)
> Enable sticky bit for curl_krb_cache
>
>
> Key: AMBARI-21970
> URL: https://issues.apache.org/jira/browse/AMBARI-21970
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Krishnama Raju K
>Assignee: Eugene Chekanskiy
>Priority: Minor
> Attachments: AMBARI-21970.patch
>
>
> In secure environment, we see that "/var/lib/ambari-agent/tmp" has sticky bit
> enabled. Trying to enable such permissions ( sticky bit or any other
> permissions ) for "curl_krb_request.py" is being over written after few
> seconds.
> It is observed that the chmod permissions set in "curl_krb_request.py"
> enforces periodic 0777 as shown in below snippet.
> {code:java}
> curl_krb_cache_path = os.path.join(tmp_dir, "curl_krb_cache")
> if not os.path.exists(curl_krb_cache_path):
> os.makedirs(curl_krb_cache_path)
> os.chmod(curl_krb_cache_path, 0777)
> {code}
> Ref:
> https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py
> Hence, code changes need to be done for setting the sticky bit to prevent
> access from users who did not create the specific file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21970) Enable sticky bit for curl_krb_cache
[
https://issues.apache.org/jira/browse/AMBARI-21970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Chekanskiy updated AMBARI-21970:
---
Attachment: AMBARI-21970.patch
> Enable sticky bit for curl_krb_cache
>
>
> Key: AMBARI-21970
> URL: https://issues.apache.org/jira/browse/AMBARI-21970
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Krishnama Raju K
>Assignee: Eugene Chekanskiy
>Priority: Minor
> Attachments: AMBARI-21970.patch
>
>
> In secure environment, we see that "/var/lib/ambari-agent/tmp" has sticky bit
> enabled. Trying to enable such permissions ( sticky bit or any other
> permissions ) for "curl_krb_request.py" is being over written after few
> seconds.
> It is observed that the chmod permissions set in "curl_krb_request.py"
> enforces periodic 0777 as shown in below snippet.
> {code:java}
> curl_krb_cache_path = os.path.join(tmp_dir, "curl_krb_cache")
> if not os.path.exists(curl_krb_cache_path):
> os.makedirs(curl_krb_cache_path)
> os.chmod(curl_krb_cache_path, 0777)
> {code}
> Ref:
> https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py
> Hence, code changes need to be done for setting the sticky bit to prevent
> access from users who did not create the specific file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Attachment: AMBARI-21993.patch > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Status: Patch Available (was: Open) > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Attachment: AMBARI-21993_trunk.patch > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png, AMBARI-21993.patch, > AMBARI-21993_trunk.patch > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21993: Assignee: Antonenko Alexander > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Description: # Top whitespace between text and grey area is to small, but bottom whitespace between grey area and button area is to big: !1.png|thumbnail! # Second text should be the same size as in check while upgrading: !2.png|thumbnail! !3.png|thumbnail! > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png > > > # Top whitespace between text and grey area is to small, but bottom > whitespace between grey area and button area is to big: > !1.png|thumbnail! > # Second text should be the same size as in check while upgrading: > !2.png|thumbnail! !3.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21993) Pre upgrade check dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-21993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21993: - Attachment: 3.png 2.png 1.png > Pre upgrade check dialog style issues > - > > Key: AMBARI-21993 > URL: https://issues.apache.org/jira/browse/AMBARI-21993 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, 3.png > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21993) Pre upgrade check dialog style issues
Antonenko Alexander created AMBARI-21993: Summary: Pre upgrade check dialog style issues Key: AMBARI-21993 URL: https://issues.apache.org/jira/browse/AMBARI-21993 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[ https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171623#comment-16171623 ] Hudson commented on AMBARI-21991: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8088 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8088/]) AMBARI-21991. Clarify MAINT Upgrade Message About Existing Services (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d0e44a15466548e06b977c9d514b4a4ff4f52296]) * (edit) ambari-web/app/messages.js > Clarify MAINT Upgrade Message About Existing Services > - > > Key: AMBARI-21991 > URL: https://issues.apache.org/jira/browse/AMBARI-21991 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21991.patch > > > The message that is displayed for the service's tooltip when it will not be > upgraded is a bit unclear: > "Update available, but already installed" > We should change it to read the following: > "The version of this service included in this repository is already installed > in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21992: - Attachment: AMBARI-21992_trunk.patch > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21992: - Status: Patch Available (was: Open) > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21992: - Attachment: AMBARI-21992.patch > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21992.patch, AMBARI-21992_trunk.patch > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
[ https://issues.apache.org/jira/browse/AMBARI-21992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21992: Assignee: Antonenko Alexander > Update Already Installed Icon Appears On Old Repo > - > > Key: AMBARI-21992 > URL: https://issues.apache.org/jira/browse/AMBARI-21992 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > > The "Update Available, but already installed." icon appears on repos which > have previously been applied and then moved off of. > STR: > * Install HDP 2.6.0.0 for ZK and Storm > * Register a PATCH HDP 2.6.0.1 for Storm > * Apply the patch > * Register a PATCH HDP 2.6.0.2 for Storm > * Apply the patch > The old repo moves into the correct state, but displays the icon indicating > that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21992) Update Already Installed Icon Appears On Old Repo
Antonenko Alexander created AMBARI-21992: Summary: Update Already Installed Icon Appears On Old Repo Key: AMBARI-21992 URL: https://issues.apache.org/jira/browse/AMBARI-21992 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Fix For: 2.6.0 The "Update Available, but already installed." icon appears on repos which have previously been applied and then moved off of. STR: * Install HDP 2.6.0.0 for ZK and Storm * Register a PATCH HDP 2.6.0.1 for Storm * Apply the patch * Register a PATCH HDP 2.6.0.2 for Storm * Apply the patch The old repo moves into the correct state, but displays the icon indicating that Storm is already at the right version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[ https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171593#comment-16171593 ] Hudson commented on AMBARI-21991: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #241 (See [https://builds.apache.org/job/Ambari-branch-2.6/241/]) AMBARI-21991. Clarify MAINT Upgrade Message About Existing Services (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3a1c3a6e46bd0c3f91b3cb3467f91617d10d57ce]) * (edit) ambari-web/app/messages.js > Clarify MAINT Upgrade Message About Existing Services > - > > Key: AMBARI-21991 > URL: https://issues.apache.org/jira/browse/AMBARI-21991 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21991.patch > > > The message that is displayed for the service's tooltip when it will not be > upgraded is a bit unclear: > "Update available, but already installed" > We should change it to read the following: > "The version of this service included in this repository is already installed > in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21735) Parameterize Maven Surefire Build argLine
[
https://issues.apache.org/jira/browse/AMBARI-21735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171592#comment-16171592
]
Jonathan Hurley commented on AMBARI-21735:
--
DDLs? Wrong Jira?
> Parameterize Maven Surefire Build argLine
> -
>
> Key: AMBARI-21735
> URL: https://issues.apache.org/jira/browse/AMBARI-21735
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.6.0
>
> Attachments: AMBARI-21735.patch
>
>
> Regardless of what options are set via {{MAVEN_OPTS}} or even
> {{-DargLine=...}}, the surefire plugin seems to force the hard coded arg
> lines for forked VMs:
> {code}
> /Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/jre/bin/java
> -Xms512m -Xmx1024m -jar
> {code}
> Setting argLines to different values is never picked up.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[ https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21991: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Clarify MAINT Upgrade Message About Existing Services > - > > Key: AMBARI-21991 > URL: https://issues.apache.org/jira/browse/AMBARI-21991 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21991.patch > > > The message that is displayed for the service's tooltip when it will not be > upgraded is a bit unclear: > "Update available, but already installed" > We should change it to read the following: > "The version of this service included in this repository is already installed > in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21991) Clarify MAINT Upgrade Message About Existing Services
[ https://issues.apache.org/jira/browse/AMBARI-21991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171542#comment-16171542 ] Andrii Tkach commented on AMBARI-21991: --- +1 for the patch > Clarify MAINT Upgrade Message About Existing Services > - > > Key: AMBARI-21991 > URL: https://issues.apache.org/jira/browse/AMBARI-21991 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21991.patch > > > The message that is displayed for the service's tooltip when it will not be > upgraded is a bit unclear: > "Update available, but already installed" > We should change it to read the following: > "The version of this service included in this repository is already installed > in the cluster." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
