[jira] [Commented] (AMBARI-24105) Jackson library version mismatch casue MR jobs to fail
[ https://issues.apache.org/jira/browse/AMBARI-24105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512970#comment-16512970 ] Hudson commented on AMBARI-24105: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9458 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9458/]) [AMBARI-24105] Jackson library version mismatch casue MR jobs to fail (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=0536321d662e6ac247b43788bada7a01c466bb43]) * (edit) ambari-metrics/ambari-metrics-common/pom.xml > Jackson library version mismatch casue MR jobs to fail > -- > > Key: AMBARI-24105 > URL: https://issues.apache.org/jira/browse/AMBARI-24105 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24105) Jackson library version mismatch casue MR jobs to fail
[ https://issues.apache.org/jira/browse/AMBARI-24105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-24105. Resolution: Fixed PR merged to trunk. > Jackson library version mismatch casue MR jobs to fail > -- > > Key: AMBARI-24105 > URL: https://issues.apache.org/jira/browse/AMBARI-24105 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24106) Upgrade History Model Changes
[
https://issues.apache.org/jira/browse/AMBARI-24106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24106:
Labels: pull-request-available (was: )
> Upgrade History Model Changes
> -
>
> Key: AMBARI-24106
> URL: https://issues.apache.org/jira/browse/AMBARI-24106
> Project: Ambari
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> Upgrade History must be tied to MPacks/Service Groups/Service IDs. The
> following changes (in bulk) need to be performed:
> - Removing {{RepositoryVersionEntity}} from upgrade history
> - Associating history with a specific service group
> -- Associating that service group with to/from mpack versions
> - Exposing upgrade summary information for
> -- Service Groups
> -- Modules
> -- Module Components
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24107) Ranger & Atlas initial install require additional properties to be explicitly configured in the UI
[ https://issues.apache.org/jira/browse/AMBARI-24107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24107: Labels: pull-request-available (was: ) > Ranger & Atlas initial install require additional properties to be explicitly > configured in the UI > -- > > Key: AMBARI-24107 > URL: https://issues.apache.org/jira/browse/AMBARI-24107 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > > Great to see Ambari now allows deployment of Ranger and Altas services at > initial cluster install time. However, doing so complicates the install > process, as there are some additional configurations the user is required to > explicitly fill. Could we pre-populate this information, as to avoid > interrupting the install flow? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24107) Ranger & Atlas initial install require additional properties to be explicitly configured in the UI
Ishan Bhatt created AMBARI-24107: Summary: Ranger & Atlas initial install require additional properties to be explicitly configured in the UI Key: AMBARI-24107 URL: https://issues.apache.org/jira/browse/AMBARI-24107 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk Great to see Ambari now allows deployment of Ranger and Altas services at initial cluster install time. However, doing so complicates the install process, as there are some additional configurations the user is required to explicitly fill. Could we pre-populate this information, as to avoid interrupting the install flow? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24106) Upgrade History Model Changes
Jonathan Hurley created AMBARI-24106:
Summary: Upgrade History Model Changes
Key: AMBARI-24106
URL: https://issues.apache.org/jira/browse/AMBARI-24106
Project: Ambari
Issue Type: Task
Affects Versions: 3.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 3.0.0
Upgrade History must be tied to MPacks/Service Groups/Service IDs. The
following changes (in bulk) need to be performed:
- Removing {{RepositoryVersionEntity}} from upgrade history
- Associating history with a specific service group
-- Associating that service group with to/from mpack versions
- Exposing upgrade summary information for
-- Service Groups
-- Modules
-- Module Components
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24105) Jackson library version mismatch casue MR jobs to fail
[ https://issues.apache.org/jira/browse/AMBARI-24105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24105: Labels: pull-request-available (was: ) > Jackson library version mismatch casue MR jobs to fail > -- > > Key: AMBARI-24105 > URL: https://issues.apache.org/jira/browse/AMBARI-24105 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24105) Jackson library version mismatch casue MR jobs to fail
Aravindan Vijayan created AMBARI-24105: -- Summary: Jackson library version mismatch casue MR jobs to fail Key: AMBARI-24105 URL: https://issues.apache.org/jira/browse/AMBARI-24105 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24104) Host component creation fails when hadoop client from multiple mpacks is installed
[ https://issues.apache.org/jira/browse/AMBARI-24104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24104: Labels: pull-request-available (was: ) > Host component creation fails when hadoop client from multiple mpacks is > installed > -- > > Key: AMBARI-24104 > URL: https://issues.apache.org/jira/browse/AMBARI-24104 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jayush Luniya >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24097) Canceling task during blueprint install results in agent not responding to any other tasks
[ https://issues.apache.org/jira/browse/AMBARI-24097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512731#comment-16512731 ] Hudson commented on AMBARI-24097: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9457 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9457/]) AMBARI-24097. Canceling task during blueprint install results in agent (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=451cdacb6bd6549de297ef4c995111a6e01832f6]) * (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py AMBARI-24097. Canceling task during blueprint install results in agent (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=484cd10cf4066926cd8715821d9f5eb29e1c273b]) * (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py > Canceling task during blueprint install results in agent not responding to > any other tasks > -- > > Key: AMBARI-24097 > URL: https://issues.apache.org/jira/browse/AMBARI-24097 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-24097.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > If failing operation which is in retry cycle is canceled during blueprint > install. The agent will still continue to execute the canceled task. Resulting > in ActionQueue being stuck and no other task being able to start execution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24104) Host component creation fails when hadoop client from multiple mpacks is installed
Jayush Luniya created AMBARI-24104: -- Summary: Host component creation fails when hadoop client from multiple mpacks is installed Key: AMBARI-24104 URL: https://issues.apache.org/jira/browse/AMBARI-24104 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Jayush Luniya Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24083) Allow clients from multiple mpacks to be installed
[ https://issues.apache.org/jira/browse/AMBARI-24083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24083: Labels: pull-request-available (was: ) > Allow clients from multiple mpacks to be installed > -- > > Key: AMBARI-24083 > URL: https://issues.apache.org/jira/browse/AMBARI-24083 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jason Golieb >Assignee: Jason Golieb >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Due to service names being used as unique IDs, the same service from multiple > mpacks were not being installed, as configured in the installer wizard. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24096) Add Upgrade Pack to Upgrade Plan
[ https://issues.apache.org/jira/browse/AMBARI-24096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24096: Labels: pull-request-available (was: ) > Add Upgrade Pack to Upgrade Plan > > > Key: AMBARI-24096 > URL: https://issues.apache.org/jira/browse/AMBARI-24096 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > > Add the upgrade pack to the detail for an UpgradePlan. This value will be > used to test the API and will eventually be calculated when creating a plan > that doesn't include this value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24101) Blueprint MPack Auto-Download needs more detailed error reporting
[ https://issues.apache.org/jira/browse/AMBARI-24101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-24101: --- Status: Patch Available (was: In Progress) > Blueprint MPack Auto-Download needs more detailed error reporting > - > > Key: AMBARI-24101 > URL: https://issues.apache.org/jira/browse/AMBARI-24101 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The current error message does indicate which MPack is causing the issue, and > the ambari-server logs do show the exceptions causing the problem, but it > might be a good idea to make this error more obvious in the client error > message as well. > This JIRA tracks the work to investigate this problem, to determine if more > error-related information can be added to the client response when failures > of this type are detected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23945) Infra Solr migration: use less params for migration steps (make it easier to use)
[ https://issues.apache.org/jira/browse/AMBARI-23945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512569#comment-16512569 ] Hudson commented on AMBARI-23945: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9456 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9456/]) AMBARI-23945. Embed backup/migration/restore collection steps to (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2d925a47011283d25bb31fd7c16dce21defb7356]) * (edit) ambari-infra/ambari-infra-solr-client/README.md > Infra Solr migration: use less params for migration steps (make it easier to > use) > - > > Key: AMBARI-23945 > URL: https://issues.apache.org/jira/browse/AMBARI-23945 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24100) Websocket connection. Port is hardcoded
[ https://issues.apache.org/jira/browse/AMBARI-24100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-24100: - Status: Patch Available (was: Open) > Websocket connection. Port is hardcoded > --- > > Key: AMBARI-24100 > URL: https://issues.apache.org/jira/browse/AMBARI-24100 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > If the URL does not contain port then the protocol defines the port in case > of http it is 80, in case of https it is 443, if it contains it we should use > it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24100) Websocket connection. Port is hardcoded
[ https://issues.apache.org/jira/browse/AMBARI-24100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24100: Labels: pull-request-available (was: ) > Websocket connection. Port is hardcoded > --- > > Key: AMBARI-24100 > URL: https://issues.apache.org/jira/browse/AMBARI-24100 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > If the URL does not contain port then the protocol defines the port in case > of http it is 80, in case of https it is 443, if it contains it we should use > it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24101) Blueprint MPack Auto-Download needs more detailed error reporting
[ https://issues.apache.org/jira/browse/AMBARI-24101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24101: Labels: pull-request-available (was: ) > Blueprint MPack Auto-Download needs more detailed error reporting > - > > Key: AMBARI-24101 > URL: https://issues.apache.org/jira/browse/AMBARI-24101 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > The current error message does indicate which MPack is causing the issue, and > the ambari-server logs do show the exceptions causing the problem, but it > might be a good idea to make this error more obvious in the client error > message as well. > This JIRA tracks the work to investigate this problem, to determine if more > error-related information can be added to the client response when failures > of this type are detected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24103) topology_script.py return incorrect data
[
https://issues.apache.org/jira/browse/AMBARI-24103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24103:
Labels: pull-request-available (was: )
> topology_script.py return incorrect data
>
>
> Key: AMBARI-24103
> URL: https://issues.apache.org/jira/browse/AMBARI-24103
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> STR:
> 1) Change the rack of master HOST on '/\{YOUR_NEW_RACK_NAME}'
> 2) Restart all required services
> 3) Check that execute of bash 'topology_script.py HOST' returned
> \{YOUR_NEW_RACK_NAME}
> Actual result: topology_script.py return incorrect data, when the rack of
> host was changed on UI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24103) topology_script.py return incorrect data
Dmytro Sen created AMBARI-24103:
---
Summary: topology_script.py return incorrect data
Key: AMBARI-24103
URL: https://issues.apache.org/jira/browse/AMBARI-24103
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 2.7.0
STR:
1) Change the rack of master HOST on '/\{YOUR_NEW_RACK_NAME}'
2) Restart all required services
3) Check that execute of bash 'topology_script.py HOST' returned
\{YOUR_NEW_RACK_NAME}
Actual result: topology_script.py return incorrect data, when the rack of host
was changed on UI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24102) Update the Manage JN wizard step for multiple nameservice scenario
[ https://issues.apache.org/jira/browse/AMBARI-24102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512456#comment-16512456 ] Hudson commented on AMBARI-24102: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9455 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9455/]) AMBARI-24102 Update the Manage JN wizard step for multiple nameservice (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f1334dcdee050598019af49c4aef90c6d3f85871]) * (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/step3.hbs * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/utils/ajax/ajax.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/journalNode/step3_controller.js * (edit) ambari-web/app/controllers/main/admin/highAvailability/nameNode/step4_controller.js * (edit) ambari-web/app/views/main/admin/highAvailability/journalNode/step3_view.js > Update the Manage JN wizard step for multiple nameservice scenario > -- > > Key: AMBARI-24102 > URL: https://issues.apache.org/jira/browse/AMBARI-24102 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Update the Save namespace commands based on available nameservices. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24102) Update the Manage JN wizard step for multiple nameservice scenario
[ https://issues.apache.org/jira/browse/AMBARI-24102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24102: -- Resolution: Fixed Status: Resolved (was: Patch Available) Merged to trunk > Update the Manage JN wizard step for multiple nameservice scenario > -- > > Key: AMBARI-24102 > URL: https://issues.apache.org/jira/browse/AMBARI-24102 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Update the Save namespace commands based on available nameservices. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23945) Infra Solr migration: use less params for migration steps (make it easier to use)
[ https://issues.apache.org/jira/browse/AMBARI-23945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512406#comment-16512406 ] Hudson commented on AMBARI-23945: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9454 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9454/]) AMBARI-23945. Embed migration config generation steps to README.md (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=e11bab6b4247d3e957f1104679ccb9f6d98a7ef9]) * (edit) ambari-infra/ambari-infra-solr-client/README.md > Infra Solr migration: use less params for migration steps (make it easier to > use) > - > > Key: AMBARI-23945 > URL: https://issues.apache.org/jira/browse/AMBARI-23945 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24102) Update the Manage JN wizard step for multiple nameservice scenario
[ https://issues.apache.org/jira/browse/AMBARI-24102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24102: -- Status: Patch Available (was: Open) > Update the Manage JN wizard step for multiple nameservice scenario > -- > > Key: AMBARI-24102 > URL: https://issues.apache.org/jira/browse/AMBARI-24102 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Update the Save namespace commands based on available nameservices. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24102) Update the Manage JN wizard step for multiple nameservice scenario
[ https://issues.apache.org/jira/browse/AMBARI-24102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24102: Labels: pull-request-available (was: ) > Update the Manage JN wizard step for multiple nameservice scenario > -- > > Key: AMBARI-24102 > URL: https://issues.apache.org/jira/browse/AMBARI-24102 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > Update the Save namespace commands based on available nameservices. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24102) Update the Manage JN wizard step for multiple nameservice scenario
Andrii Babiichuk created AMBARI-24102: - Summary: Update the Manage JN wizard step for multiple nameservice scenario Key: AMBARI-24102 URL: https://issues.apache.org/jira/browse/AMBARI-24102 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 2.7.0 Update the Save namespace commands based on available nameservices. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24101) Blueprint MPack Auto-Download needs more detailed error reporting
Balázs Bence Sári created AMBARI-24101: -- Summary: Blueprint MPack Auto-Download needs more detailed error reporting Key: AMBARI-24101 URL: https://issues.apache.org/jira/browse/AMBARI-24101 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári Fix For: 3.0.0 The current error message does indicate which MPack is causing the issue, and the ambari-server logs do show the exceptions causing the problem, but it might be a good idea to make this error more obvious in the client error message as well. This JIRA tracks the work to investigate this problem, to determine if more error-related information can be added to the client response when failures of this type are detected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24100) Websocket connection. Port is hardcoded
[ https://issues.apache.org/jira/browse/AMBARI-24100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24100: Assignee: Antonenko Alexander > Websocket connection. Port is hardcoded > --- > > Key: AMBARI-24100 > URL: https://issues.apache.org/jira/browse/AMBARI-24100 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.7.0 > > > If the URL does not contain port then the protocol defines the port in case > of http it is 80, in case of https it is 443, if it contains it we should use > it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24100) Websocket connection. Port is hardcoded
Antonenko Alexander created AMBARI-24100: Summary: Websocket connection. Port is hardcoded Key: AMBARI-24100 URL: https://issues.apache.org/jira/browse/AMBARI-24100 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 If the URL does not contain port then the protocol defines the port in case of http it is 80, in case of https it is 443, if it contains it we should use it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24099) Service check failure is not skipped during upgrade even though "Skip All Service Check Failures" options is selected before Upgrade Start
[ https://issues.apache.org/jira/browse/AMBARI-24099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-24099: Affects Version/s: 2.7.0 > Service check failure is not skipped during upgrade even though "Skip All > Service Check Failures" options is selected before Upgrade Start > -- > > Key: AMBARI-24099 > URL: https://issues.apache.org/jira/browse/AMBARI-24099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Blocker > Fix For: 2.7.0 > > > Even after selecting "Skip all service check failures" option before starting > upgrade , the upgrade is not ignoring service check failures and upgrade gets > paused at the failure step. > The expected behaviour is: it should skip the failed service check and have a > message like "There are failures that were automatically skipped". > This behaviour is working fine for Slave Component failure skip. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24099) Service check failure is not skipped during upgrade even though "Skip All Service Check Failures" options is selected before Upgrade Start
[ https://issues.apache.org/jira/browse/AMBARI-24099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-24099: Fix Version/s: 2.7.0 > Service check failure is not skipped during upgrade even though "Skip All > Service Check Failures" options is selected before Upgrade Start > -- > > Key: AMBARI-24099 > URL: https://issues.apache.org/jira/browse/AMBARI-24099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Blocker > Fix For: 2.7.0 > > > Even after selecting "Skip all service check failures" option before starting > upgrade , the upgrade is not ignoring service check failures and upgrade gets > paused at the failure step. > The expected behaviour is: it should skip the failed service check and have a > message like "There are failures that were automatically skipped". > This behaviour is working fine for Slave Component failure skip. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24099) Service check failure is not skipped during upgrade even though "Skip All Service Check Failures" options is selected before Upgrade Start
[ https://issues.apache.org/jira/browse/AMBARI-24099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-24099: Component/s: ambari-server > Service check failure is not skipped during upgrade even though "Skip All > Service Check Failures" options is selected before Upgrade Start > -- > > Key: AMBARI-24099 > URL: https://issues.apache.org/jira/browse/AMBARI-24099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Blocker > > Even after selecting "Skip all service check failures" option before starting > upgrade , the upgrade is not ignoring service check failures and upgrade gets > paused at the failure step. > The expected behaviour is: it should skip the failed service check and have a > message like "There are failures that were automatically skipped". > This behaviour is working fine for Slave Component failure skip. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24099) Service check failure is not skipped during upgrade even though "Skip All Service Check Failures" options is selected before Upgrade Start
Dmitry Lysnichenko created AMBARI-24099: --- Summary: Service check failure is not skipped during upgrade even though "Skip All Service Check Failures" options is selected before Upgrade Start Key: AMBARI-24099 URL: https://issues.apache.org/jira/browse/AMBARI-24099 Project: Ambari Issue Type: Bug Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Even after selecting "Skip all service check failures" option before starting upgrade , the upgrade is not ignoring service check failures and upgrade gets paused at the failure step. The expected behaviour is: it should skip the failed service check and have a message like "There are failures that were automatically skipped". This behaviour is working fine for Slave Component failure skip. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24099) Service check failure is not skipped during upgrade even though "Skip All Service Check Failures" options is selected before Upgrade Start
[ https://issues.apache.org/jira/browse/AMBARI-24099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24099: Labels: pull-request-available (was: ) > Service check failure is not skipped during upgrade even though "Skip All > Service Check Failures" options is selected before Upgrade Start > -- > > Key: AMBARI-24099 > URL: https://issues.apache.org/jira/browse/AMBARI-24099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > Even after selecting "Skip all service check failures" option before starting > upgrade , the upgrade is not ignoring service check failures and upgrade gets > paused at the failure step. > The expected behaviour is: it should skip the failed service check and have a > message like "There are failures that were automatically skipped". > This behaviour is working fine for Slave Component failure skip. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24098) Filter have incorrect name on host page
[ https://issues.apache.org/jira/browse/AMBARI-24098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512331#comment-16512331 ] Hudson commented on AMBARI-24098: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9453 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9453/]) AMBARI-24098. Filter have incorrect name on host page (akovalenko) (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=69f7bae42103f716d381a14357696569d394dda6]) * (edit) ambari-web/app/models/host_component.js > Filter have incorrect name on host page > --- > > Key: AMBARI-24098 > URL: https://issues.apache.org/jira/browse/AMBARI-24098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Actual result: some filter for components has an incorrect name "Install > Pending" but should be "Install Pending..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24098) Filter have incorrect name on host page
[ https://issues.apache.org/jira/browse/AMBARI-24098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24098. -- Resolution: Fixed > Filter have incorrect name on host page > --- > > Key: AMBARI-24098 > URL: https://issues.apache.org/jira/browse/AMBARI-24098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Actual result: some filter for components has an incorrect name "Install > Pending" but should be "Install Pending..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24098) Filter have incorrect name on host page
[ https://issues.apache.org/jira/browse/AMBARI-24098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24098: Labels: pull-request-available (was: ) > Filter have incorrect name on host page > --- > > Key: AMBARI-24098 > URL: https://issues.apache.org/jira/browse/AMBARI-24098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > Actual result: some filter for components has an incorrect name "Install > Pending" but should be "Install Pending..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24098) Filter have incorrect name on host page
Aleksandr Kovalenko created AMBARI-24098: Summary: Filter have incorrect name on host page Key: AMBARI-24098 URL: https://issues.apache.org/jira/browse/AMBARI-24098 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Actual result: some filter for components has an incorrect name "Install Pending" but should be "Install Pending..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24093) Delete Button not enabled on Druid Router component
[ https://issues.apache.org/jira/browse/AMBARI-24093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512285#comment-16512285 ] Hudson commented on AMBARI-24093: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9452 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9452/]) AMBARI-24093 Delete Button not enabled on Druid Router component (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=5de78a9546e5cb9c0d9f5f33b46a113181e377a7]) * (edit) ambari-web/app/mappers/socket/topology_mapper.js > Delete Button not enabled on Druid Router component > --- > > Key: AMBARI-24093 > URL: https://issues.apache.org/jira/browse/AMBARI-24093 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > facing issue while trying to delete Druid Router, where the delete button is > disabled. > The Test performs the following: > * Select component from list (after clicking on add button) > * Start component > * Restart all component with stale config > * Run Service check against service > * Stop component > * Delete component > * Restart all component with stale config > * Run Service check > * Repeat the above steps for all possible components. > Noticed that the delete button was not enabled for Druid Router only. When I > accessed the cluster later, the delete button was enabled. This looks like an > intermittent issue. Only once I could reproduce this on my local after doing > various actions related to add/delete component. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24097) Canceling task during blueprint install results in agent not responding to any other tasks
[ https://issues.apache.org/jira/browse/AMBARI-24097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24097: Labels: pull-request-available (was: ) > Canceling task during blueprint install results in agent not responding to > any other tasks > -- > > Key: AMBARI-24097 > URL: https://issues.apache.org/jira/browse/AMBARI-24097 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-24097.patch > > > If failing operation which is in retry cycle is canceled during blueprint > install. The agent will still continue to execute the canceled task. Resulting > in ActionQueue being stuck and no other task being able to start execution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24093) Delete Button not enabled on Druid Router component
[ https://issues.apache.org/jira/browse/AMBARI-24093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512236#comment-16512236 ] Andrii Tkach commented on AMBARI-24093: --- committed to trunk > Delete Button not enabled on Druid Router component > --- > > Key: AMBARI-24093 > URL: https://issues.apache.org/jira/browse/AMBARI-24093 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > facing issue while trying to delete Druid Router, where the delete button is > disabled. > The Test performs the following: > * Select component from list (after clicking on add button) > * Start component > * Restart all component with stale config > * Run Service check against service > * Stop component > * Delete component > * Restart all component with stale config > * Run Service check > * Repeat the above steps for all possible components. > Noticed that the delete button was not enabled for Druid Router only. When I > accessed the cluster later, the delete button was enabled. This looks like an > intermittent issue. Only once I could reproduce this on my local after doing > various actions related to add/delete component. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24097) Canceling task during blueprint install results in agent not responding to any other tasks
Andrew Onischuk created AMBARI-24097: Summary: Canceling task during blueprint install results in agent not responding to any other tasks Key: AMBARI-24097 URL: https://issues.apache.org/jira/browse/AMBARI-24097 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.0 Attachments: AMBARI-24097.patch If failing operation which is in retry cycle is canceled during blueprint install. The agent will still continue to execute the canceled task. Resulting in ActionQueue being stuck and no other task being able to start execution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24093) Delete Button not enabled on Druid Router component
[ https://issues.apache.org/jira/browse/AMBARI-24093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach resolved AMBARI-24093. --- Resolution: Fixed > Delete Button not enabled on Druid Router component > --- > > Key: AMBARI-24093 > URL: https://issues.apache.org/jira/browse/AMBARI-24093 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > facing issue while trying to delete Druid Router, where the delete button is > disabled. > The Test performs the following: > * Select component from list (after clicking on add button) > * Start component > * Restart all component with stale config > * Run Service check against service > * Stop component > * Delete component > * Restart all component with stale config > * Run Service check > * Repeat the above steps for all possible components. > Noticed that the delete button was not enabled for Druid Router only. When I > accessed the cluster later, the delete button was enabled. This looks like an > intermittent issue. Only once I could reproduce this on my local after doing > various actions related to add/delete component. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24097) Canceling task during blueprint install results in agent not responding to any other tasks
[ https://issues.apache.org/jira/browse/AMBARI-24097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24097: - Status: Patch Available (was: Open) > Canceling task during blueprint install results in agent not responding to > any other tasks > -- > > Key: AMBARI-24097 > URL: https://issues.apache.org/jira/browse/AMBARI-24097 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-24097.patch > > > If failing operation which is in retry cycle is canceled during blueprint > install. The agent will still continue to execute the canceled task. Resulting > in ActionQueue being stuck and no other task being able to start execution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24087) The alert "DataNode Unmounted Data Dir" did not appear
[ https://issues.apache.org/jira/browse/AMBARI-24087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar resolved AMBARI-24087. Resolution: Fixed > The alert "DataNode Unmounted Data Dir" did not appear > -- > > Key: AMBARI-24087 > URL: https://issues.apache.org/jira/browse/AMBARI-24087 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > str: > 1) execute commands on hosts: > dd if=/dev/zero of=/grid/0/fs bs=1 count=0 seek=10G > mkfs.ext3 -F /grid/0/fs > mkdir /grid/1/ > mount -o loop,rw /grid/0/fs /grid/1/ > chown cstm-hdfs:hadoop /grid/1/ > 2) set DN dir property (dfs.datanode.data.dir) to > "/grid/0/hadoop/hdfs/data,/newdndir,/grid/1/hadoop/hdfs" and restart needed > services > 3) check that alert is not present "DataNode Unmounted Data Dir" (after 2 min) > 4) Stop DN(s) > 5) umount /grid/1/ > 6) Start DN(s) > 7) check that alert is present -- This message was sent by Atlassian JIRA (v7.6.3#76005)
