[jira] [Commented] (AMBARI-21651) Backport AMBARI-12556 UI Work For Patch/Service Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112717#comment-16112717 ] Oleg Nechiporenko commented on AMBARI-21651: +1 for patch > Backport AMBARI-12556 UI Work For Patch/Service Upgrades > > > Key: AMBARI-21651 > URL: https://issues.apache.org/jira/browse/AMBARI-21651 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21651.patch > > > we no longer take stack name or repository version for pre-upgrade checks. > Instead, we need the repository ID. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21497) Conflicts in the ambari config groups
[ https://issues.apache.org/jira/browse/AMBARI-21497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16112415#comment-16112415 ] Oleg Nechiporenko commented on AMBARI-21497: +1 for patch > Conflicts in the ambari config groups > - > > Key: AMBARI-21497 > URL: https://issues.apache.org/jira/browse/AMBARI-21497 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21497_branch-2.5.patch, AMBARI-21497.patch > > > Ambari is arbitrarily changing settings for different config groups when > pushing changes to other config groups. > This is causing yarn to have settings for RAM that well exceed system limits, > which causes other processes to run out of RAM and then become unavailable. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21388) Can't delete hosts components via bulk-menu
[ https://issues.apache.org/jira/browse/AMBARI-21388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070222#comment-16070222 ] Oleg Nechiporenko commented on AMBARI-21388: +1 for patch > Can't delete hosts components via bulk-menu > --- > > Key: AMBARI-21388 > URL: https://issues.apache.org/jira/browse/AMBARI-21388 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21388.patch > > > *STR* > * Select two hosts via checkboxes > * On the bulk-menu select "Selected Hosts" -> "Datanodes" (or any other > available component) -> "Delete" > * Confirmation popup appears. Click OK > * Nothing happens. Only gray background appears -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21385) Selected hosts are not dropped event if some of the selected hosts was deleted
[ https://issues.apache.org/jira/browse/AMBARI-21385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070215#comment-16070215 ] Oleg Nechiporenko commented on AMBARI-21385: +1 for patch > Selected hosts are not dropped event if some of the selected hosts was deleted > -- > > Key: AMBARI-21385 > URL: https://issues.apache.org/jira/browse/AMBARI-21385 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21385.patch > > > *STR* > * Selected two hosts on the Hosts page via checkboxes > * Delete one of the selected hosts > * After page refresh bulk-dropdown menu shows that two hosts are selected > (however hosts-table doesn't contain deleted host and only one checkbox is > checked) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21384) Message for deleted hosts is confusing
[ https://issues.apache.org/jira/browse/AMBARI-21384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070207#comment-16070207 ] Oleg Nechiporenko commented on AMBARI-21384: +1 for patch > Message for deleted hosts is confusing > -- > > Key: AMBARI-21384 > URL: https://issues.apache.org/jira/browse/AMBARI-21384 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21384.patch > > > Message in the popup is about deleted hosts. However list of deleted > components is shown. > See screenshot attached -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21344) Add Services Using Repository ID
[
https://issues.apache.org/jira/browse/AMBARI-21344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063138#comment-16063138
]
Oleg Nechiporenko commented on AMBARI-21344:
+1 for patch
> Add Services Using Repository ID
>
>
> Key: AMBARI-21344
> URL: https://issues.apache.org/jira/browse/AMBARI-21344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-21344.patch
>
>
> Currently, the web client uses the repository version when adding services.
> Since multiple repositories from different vendors may have identical
> repository strings, we should switch to using the unique Repo ID instead of
> the version. Here's an example of the call being made today:
> {code:title=POST http://localhost:8080/api/v1/clusters/c1/services}
> [
> {
> "ServiceInfo": {
> "service_name": "ZOOKEEPER",
> "desired_repository_version": "2.6.0.0-334"
> }
> }
> ]
> {code}
> This should change to the following:
> {code:title=POST http://localhost:8080/api/v1/clusters/c1/services}
> [
> {
> "ServiceInfo": {
> "service_name": "ZOOKEEPER",
> "desired_repository_version_id": 1
> }
> }
> ]
> {code}
> The same change needs to be made for when a service is added to a cluster.
> However, this case it a bit trickier if there are multiple repositories.
> Until a more well-defined UX workflow is available, the following should be
> used for adding services:
> - If there is only a single repository, then use that one
> - If there are more than 1 repository, then choose the most recent repository
> -- It cannot be a {{PATCH}} repository
> -- Its status must be {{CURRENT}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21344) Add Services Using Repository ID
[
https://issues.apache.org/jira/browse/AMBARI-21344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko reassigned AMBARI-21344:
--
Assignee: Antonenko Alexander
> Add Services Using Repository ID
>
>
> Key: AMBARI-21344
> URL: https://issues.apache.org/jira/browse/AMBARI-21344
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-21344.patch
>
>
> Currently, the web client uses the repository version when adding services.
> Since multiple repositories from different vendors may have identical
> repository strings, we should switch to using the unique Repo ID instead of
> the version. Here's an example of the call being made today:
> {code:title=POST http://localhost:8080/api/v1/clusters/c1/services}
> [
> {
> "ServiceInfo": {
> "service_name": "ZOOKEEPER",
> "desired_repository_version": "2.6.0.0-334"
> }
> }
> ]
> {code}
> This should change to the following:
> {code:title=POST http://localhost:8080/api/v1/clusters/c1/services}
> [
> {
> "ServiceInfo": {
> "service_name": "ZOOKEEPER",
> "desired_repository_version_id": 1
> }
> }
> ]
> {code}
> The same change needs to be made for when a service is added to a cluster.
> However, this case it a bit trickier if there are multiple repositories.
> Until a more well-defined UX workflow is available, the following should be
> used for adding services:
> - If there is only a single repository, then use that one
> - If there are more than 1 repository, then choose the most recent repository
> -- It cannot be a {{PATCH}} repository
> -- Its status must be {{CURRENT}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-20569) Configure KMS/Zookeeper settings automatically when multiple KMS are involved
[
https://issues.apache.org/jira/browse/AMBARI-20569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050303#comment-16050303
]
Oleg Nechiporenko commented on AMBARI-20569:
+1 for patch
> Configure KMS/Zookeeper settings automatically when multiple KMS are involved
> -
>
> Key: AMBARI-20569
> URL: https://issues.apache.org/jira/browse/AMBARI-20569
> Project: Ambari
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-20569.patch
>
>
> When multiple KMS is involved, these steps should be followed to configure
> multiple instances to share correctly.
> http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.3/bk_security/content/ranger_kms_multi_kms.html
> Can we add logic in Ambari to set these values correctly when second KMS is
> added?
> {code}
> hadoop.kms.cache.enable=false
> hadoop.kms.cache.timeout.ms=0
> hadoop.kms.current.key.cache.timeout.ms=0
> hadoop.kms.authentication.signer.secret.provider=zookeeper
> hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string={internal
> ip of first node}:2181,{internal ip of second node}:2181, ...
> hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type=none{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21102) To/From Version Information is Incorrect When Looking at Prior Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-21102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024555#comment-16024555 ] Oleg Nechiporenko commented on AMBARI-21102: +1 for patch > To/From Version Information is Incorrect When Looking at Prior Upgrades > --- > > Key: AMBARI-21102 > URL: https://issues.apache.org/jira/browse/AMBARI-21102 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21102.patch, Screen Shot 2017-05-19 at 2.50.50 > PM.png, Screen Shot 2017-05-19 at 2.51.04 PM.png > > > Create a SERVICE or PATCH upgrade for a single service. Once the upgrade > completes, the "Upgrade History" section of Ambari contains incorrect > information: > - The upgrade says "Upgrade from 2.5.4.0", yet 2.5.4.0 was the target. It > should say "Upgrade to 2.5.4.0". When dowgrading, it should use the "from" > preposition. > - The To/From fields are still present in the list of upgrades, and they are > blank. They should be removed and a per-service display should be used > instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21072) Removal of from/to Upgrade Versions in Web Client
[
https://issues.apache.org/jira/browse/AMBARI-21072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017349#comment-16017349
]
Oleg Nechiporenko commented on AMBARI-21072:
+1 for patch
> Removal of from/to Upgrade Versions in Web Client
> -
>
> Key: AMBARI-21072
> URL: https://issues.apache.org/jira/browse/AMBARI-21072
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21072.patch
>
>
> Beginning with AMBARI-21022, there is no longer a single from/to version for
> a given upgrade/downgrade. The following properties have been removed:
> {code}
> Upgrade/repository_version
> Upgrade/from_version
> Upgrade/to_version
> {code}
> Instead, they have been replaced with:
> {code}
> Upgrade/repository_version_id
> Upgrade/associated_version
> Upgrade/versions
> {code}
> - {{Upgrade/repository_version_id}} - the ID of the repository when creating
> a new upgrade. This replaces the ambiguous "repository_version" field which
> was previously used.
> - {{Upgrade/associated_version}} - a read-only property which gives you
> either the "upgrade to" version or "downgrade from" version. It's
> "associated" with the upgrade's direction. This will help you build strings
> like, "Upgrading to 2.5.0.0" and "Downgrading from 2.5.0.0". The prior way of
> display this "Downgrading to 2.5.0.0" is incorrect now as services can be
> downgraded to different versions.
> - {{Upgrade/versions}} - a read-only structure which essentially gives you
> the to/from of each service in the upgrade. Example:
> {code:title=Upgrade of STORM/ZK On Different Repos}
> "Upgrade": {
> "associated_version": "2.5.4.0-121",
> "cluster_name": "c1",
> "direction": "UPGRADE",
> "downgrade_allowed": true,
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 100,
> "request_context": "Upgrading to 2.5.4.0-121",
> "request_id": 18,
> "request_status": "COMPLETED",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING",
> "versions": {
> "STORM": {
> "from_repository_id": 1,
> "from_repository_version": "2.5.0.0-1237",
> "target_repository_id": 5,
> "target_repository_version": "2.5.4.0-121"
> },
> "ZOOKEEPER": {
> "from_repository_id": 2,
> "from_repository_version": "2.5.2.9-",
> "target_repository_id": 5,
> "target_repository_version": "2.5.4.0-121"
> }
> }
> },
> {code}
> {code:title=Downgrade of STORM/ZK Back To Different Repos}
> "Upgrade": {
> "associated_version": "2.5.4.0-121",
> "cluster_name": "c1",
> "direction": "DOWNGRADE",
> "downgrade_allowed": false,
> "pack": "nonrolling-upgrade-2.5",
> "progress_percent": 100,
> "request_context": "Downgrading from 2.5.4.0-121",
> "request_id": 18,
> "request_status": "COMPLETED",
> "type": "INTERNAL_REQUEST",
> "upgrade_type": "NON_ROLLING",
> "versions": {
> "STORM": {
> "from_repository_id": 5,
> "from_repository_version": "2.5.4.0-121",
> "to_repository_id": 1,
> "to_repository_version": "2.5.0.0-1237"
> },
> "ZOOKEEPER": {
> "from_repository_id": 5,
> "from_repository_version": "2.5.4.0-121",
> "to_repository_id": 2,
> "to_repository_version": "2.5.2.9-"
> }
> }
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21041) Pause Upgrade button is present in the wizard even after Upgrade is finalized
[ https://issues.apache.org/jira/browse/AMBARI-21041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013937#comment-16013937 ] Oleg Nechiporenko commented on AMBARI-21041: +1 for patches > Pause Upgrade button is present in the wizard even after Upgrade is finalized > - > > Key: AMBARI-21041 > URL: https://issues.apache.org/jira/browse/AMBARI-21041 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Vivek Sharma >Assignee: Antonenko Alexander >Priority: Critical > Labels: express_upgrade > Fix For: 2.5.1 > > Attachments: AMBARI-21041_2.5.patch, AMBARI-21041.patch > > > Once the Express Upgrade is finalized the wizard still shows 'Pause Upgrade' > button. > Expected Result: Pause Upgrade should be hidden or grayed out at this stage > Two side-effects of this issue: > 1. Bad user experience - upgrade has completed, we still let them pause the > upgrade > 2. If user pauses the upgrade, it brings Ambari into a state where it thinks > that Upgrade is actually paused and locks the screen for any actions. The UI > still shows "Upgrade:Action Required" but there is no way to open the EU > wizard again. As a result, Ambari functionality cannot be used -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-21041) Pause Upgrade button is present in the wizard even after Upgrade is finalized
[ https://issues.apache.org/jira/browse/AMBARI-21041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko reassigned AMBARI-21041: -- Assignee: Antonenko Alexander > Pause Upgrade button is present in the wizard even after Upgrade is finalized > - > > Key: AMBARI-21041 > URL: https://issues.apache.org/jira/browse/AMBARI-21041 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Vivek Sharma >Assignee: Antonenko Alexander >Priority: Critical > Labels: express_upgrade > Fix For: 2.5.1 > > Attachments: AMBARI-21041_2.5.patch, AMBARI-21041.patch > > > Once the Express Upgrade is finalized the wizard still shows 'Pause Upgrade' > button. > Expected Result: Pause Upgrade should be hidden or grayed out at this stage > Two side-effects of this issue: > 1. Bad user experience - upgrade has completed, we still let them pause the > upgrade > 2. If user pauses the upgrade, it brings Ambari into a state where it thinks > that Upgrade is actually paused and locks the screen for any actions. The UI > still shows "Upgrade:Action Required" but there is no way to open the EU > wizard again. As a result, Ambari functionality cannot be used -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20841) Pause Button Appears After Successful Downgrade
[ https://issues.apache.org/jira/browse/AMBARI-20841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982673#comment-15982673 ] Oleg Nechiporenko commented on AMBARI-20841: +1 for patch > Pause Button Appears After Successful Downgrade > --- > > Key: AMBARI-20841 > URL: https://issues.apache.org/jira/browse/AMBARI-20841 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.1 > > Attachments: AMBARI-20841.patch > > > Pause button remains on upgrade wizard after successful downgrade. > - Upgrade from HDP 2.x to 2.y > - At finalize, try downgrade > Notice the pause button on the downgrade screen still. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20609) Fix Install Wizard data attribute
[ https://issues.apache.org/jira/browse/AMBARI-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978553#comment-15978553 ] Oleg Nechiporenko commented on AMBARI-20609: Patch AMBARI-20609-back-next.patch committed to trunk. > Fix Install Wizard data attribute > -- > > Key: AMBARI-20609 > URL: https://issues.apache.org/jira/browse/AMBARI-20609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-20609_additional-fix.patch, > AMBARI-20609-assign.patch, AMBARI-20609-back-next.patch, AMBARI-20609.patch, > AMBARI-20609_review.patch, AMBARI-20609-step4.patch, > AMBARI-20609_step7.patch, AMBARI-20609-step9.patch, > AMBARI-20609-steps0-3.patch > > > There have been a lot of frontend changes committed to trunk in preparation > for Ambari 3.0's new look and feel. > Obviously, this makes our current XPaths incompatible for trunk. > For starters, we need to make changes to XPaths and other changes necessary > so that we can at least run Install Wizard against the trunk code base. Also, > we need to make sure that Ambari Web's code itself is using best practices > with use of specific IDs and class names, etc. > We will implement special data attribute for XPaths -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20609) Fix Install Wizard data attribute
[ https://issues.apache.org/jira/browse/AMBARI-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20609: --- Attachment: AMBARI-20609-back-next.patch > Fix Install Wizard data attribute > -- > > Key: AMBARI-20609 > URL: https://issues.apache.org/jira/browse/AMBARI-20609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-20609_additional-fix.patch, > AMBARI-20609-assign.patch, AMBARI-20609-back-next.patch, AMBARI-20609.patch, > AMBARI-20609_review.patch, AMBARI-20609-step4.patch, > AMBARI-20609_step7.patch, AMBARI-20609-step9.patch, > AMBARI-20609-steps0-3.patch > > > There have been a lot of frontend changes committed to trunk in preparation > for Ambari 3.0's new look and feel. > Obviously, this makes our current XPaths incompatible for trunk. > For starters, we need to make changes to XPaths and other changes necessary > so that we can at least run Install Wizard against the trunk code base. Also, > we need to make sure that Ambari Web's code itself is using best practices > with use of specific IDs and class names, etc. > We will implement special data attribute for XPaths -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20680) Response popup: Add copy icon for "Request URL" and "Response Body" sections
[ https://issues.apache.org/jira/browse/AMBARI-20680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko resolved AMBARI-20680. Resolution: Fixed > Response popup: Add copy icon for "Request URL" and "Response Body" sections > > > Key: AMBARI-20680 > URL: https://issues.apache.org/jira/browse/AMBARI-20680 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20680.patch > > > Ability to copy request url and response body will be helpful. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20680) Response popup: Add copy icon for "Request URL" and "Response Body" sections
[ https://issues.apache.org/jira/browse/AMBARI-20680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967301#comment-15967301 ] Oleg Nechiporenko commented on AMBARI-20680: Committed to internal brunch > Response popup: Add copy icon for "Request URL" and "Response Body" sections > > > Key: AMBARI-20680 > URL: https://issues.apache.org/jira/browse/AMBARI-20680 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20680.patch > > > Ability to copy request url and response body will be helpful. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20679) Size of API Response popup should be responsive as per the browser screen size
[ https://issues.apache.org/jira/browse/AMBARI-20679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko resolved AMBARI-20679. Resolution: Fixed Committed to internal brunch > Size of API Response popup should be responsive as per the browser screen size > -- > > Key: AMBARI-20679 > URL: https://issues.apache.org/jira/browse/AMBARI-20679 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20679.patch > > > *STR:* > # Click on Try button for any GET API > # This will show a pop up with the response of the API > Width of this popup should be wider and should be in ratio with the size of > the browser screen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20732) Remove duplicate condition from route
[
https://issues.apache.org/jira/browse/AMBARI-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20732:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove duplicate condition from route
> -
>
> Key: AMBARI-20732
> URL: https://issues.apache.org/jira/browse/AMBARI-20732
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20732.patch
>
>
> {{adminServiceAutoStart.enter}} contains duplicate
> {{!App.isAuthorized('CLUSTER.MANAGE_AUTO_START')}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20732) Remove duplicate condition from route
[
https://issues.apache.org/jira/browse/AMBARI-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15965447#comment-15965447
]
Oleg Nechiporenko commented on AMBARI-20732:
Build failed not because of this patch
{noformat}
[INFO] Ambari Web . SUCCESS [05:06 min]
[INFO] Ambari Server .. FAILURE [25:11 min]
{noformat}
> Remove duplicate condition from route
> -
>
> Key: AMBARI-20732
> URL: https://issues.apache.org/jira/browse/AMBARI-20732
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20732.patch
>
>
> {{adminServiceAutoStart.enter}} contains duplicate
> {{!App.isAuthorized('CLUSTER.MANAGE_AUTO_START')}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20732) Remove duplicate condition from route
[
https://issues.apache.org/jira/browse/AMBARI-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964566#comment-15964566
]
Oleg Nechiporenko commented on AMBARI-20732:
Committed to trunk
> Remove duplicate condition from route
> -
>
> Key: AMBARI-20732
> URL: https://issues.apache.org/jira/browse/AMBARI-20732
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20732.patch
>
>
> {{adminServiceAutoStart.enter}} contains duplicate
> {{!App.isAuthorized('CLUSTER.MANAGE_AUTO_START')}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20732) Remove duplicate condition from route
[
https://issues.apache.org/jira/browse/AMBARI-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20732:
---
Status: Patch Available (was: Open)
> Remove duplicate condition from route
> -
>
> Key: AMBARI-20732
> URL: https://issues.apache.org/jira/browse/AMBARI-20732
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20732.patch
>
>
> {{adminServiceAutoStart.enter}} contains duplicate
> {{!App.isAuthorized('CLUSTER.MANAGE_AUTO_START')}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20732) Remove duplicate condition from route
[
https://issues.apache.org/jira/browse/AMBARI-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964211#comment-15964211
]
Oleg Nechiporenko commented on AMBARI-20732:
+1 by [~BuzhorDenys] on the review board
> Remove duplicate condition from route
> -
>
> Key: AMBARI-20732
> URL: https://issues.apache.org/jira/browse/AMBARI-20732
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20732.patch
>
>
> {{adminServiceAutoStart.enter}} contains duplicate
> {{!App.isAuthorized('CLUSTER.MANAGE_AUTO_START')}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20732) Remove duplicate condition from route
[
https://issues.apache.org/jira/browse/AMBARI-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20732:
---
Attachment: (was: AMBARI-20732.patch)
> Remove duplicate condition from route
> -
>
> Key: AMBARI-20732
> URL: https://issues.apache.org/jira/browse/AMBARI-20732
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20732.patch
>
>
> {{adminServiceAutoStart.enter}} contains duplicate
> {{!App.isAuthorized('CLUSTER.MANAGE_AUTO_START')}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20732) Remove duplicate condition from route
[
https://issues.apache.org/jira/browse/AMBARI-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20732:
---
Attachment: AMBARI-20732.patch
> Remove duplicate condition from route
> -
>
> Key: AMBARI-20732
> URL: https://issues.apache.org/jira/browse/AMBARI-20732
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20732.patch
>
>
> {{adminServiceAutoStart.enter}} contains duplicate
> {{!App.isAuthorized('CLUSTER.MANAGE_AUTO_START')}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20732) Remove duplicate condition from route
[
https://issues.apache.org/jira/browse/AMBARI-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20732:
---
Attachment: (was: AMBARI-20732.patch)
> Remove duplicate condition from route
> -
>
> Key: AMBARI-20732
> URL: https://issues.apache.org/jira/browse/AMBARI-20732
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20732.patch
>
>
> {{adminServiceAutoStart.enter}} contains duplicate
> {{!App.isAuthorized('CLUSTER.MANAGE_AUTO_START')}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20732) Remove duplicate condition from route
[
https://issues.apache.org/jira/browse/AMBARI-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20732:
---
Attachment: AMBARI-20732.patch
> Remove duplicate condition from route
> -
>
> Key: AMBARI-20732
> URL: https://issues.apache.org/jira/browse/AMBARI-20732
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20732.patch
>
>
> {{adminServiceAutoStart.enter}} contains duplicate
> {{!App.isAuthorized('CLUSTER.MANAGE_AUTO_START')}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20732) Remove duplicate condition from route
[
https://issues.apache.org/jira/browse/AMBARI-20732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20732:
---
Attachment: AMBARI-20732.patch
> Remove duplicate condition from route
> -
>
> Key: AMBARI-20732
> URL: https://issues.apache.org/jira/browse/AMBARI-20732
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20732.patch
>
>
> {{adminServiceAutoStart.enter}} contains duplicate
> {{!App.isAuthorized('CLUSTER.MANAGE_AUTO_START')}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20732) Remove duplicate condition from route
Oleg Nechiporenko created AMBARI-20732:
--
Summary: Remove duplicate condition from route
Key: AMBARI-20732
URL: https://issues.apache.org/jira/browse/AMBARI-20732
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 3.0.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Fix For: 3.0.0
{{adminServiceAutoStart.enter}} contains duplicate
{{!App.isAuthorized('CLUSTER.MANAGE_AUTO_START')}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20680) Response popup: Add copy icon for "Request URL" and "Response Body" sections
[ https://issues.apache.org/jira/browse/AMBARI-20680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20680: --- Attachment: AMBARI-20680.patch > Response popup: Add copy icon for "Request URL" and "Response Body" sections > > > Key: AMBARI-20680 > URL: https://issues.apache.org/jira/browse/AMBARI-20680 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20680.patch > > > Ability to copy request url and response body will be helpful. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20679) Size of API Response popup should be responsive as per the browser screen size
[ https://issues.apache.org/jira/browse/AMBARI-20679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20679: --- Issue Type: Task (was: Bug) > Size of API Response popup should be responsive as per the browser screen size > -- > > Key: AMBARI-20679 > URL: https://issues.apache.org/jira/browse/AMBARI-20679 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20679.patch > > > *STR:* > # Click on Try button for any GET API > # This will show a pop up with the response of the API > Width of this popup should be wider and should be in ratio with the size of > the browser screen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20680) Response popup: Add copy icon for "Request URL" and "Response Body" sections
Oleg Nechiporenko created AMBARI-20680: -- Summary: Response popup: Add copy icon for "Request URL" and "Response Body" sections Key: AMBARI-20680 URL: https://issues.apache.org/jira/browse/AMBARI-20680 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 3.0.0 Ability to copy request url and response body will be helpful. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20679) Size of API Response popup should be responsive as per the browser screen size
[ https://issues.apache.org/jira/browse/AMBARI-20679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20679: --- Attachment: AMBARI-20679.patch > Size of API Response popup should be responsive as per the browser screen size > -- > > Key: AMBARI-20679 > URL: https://issues.apache.org/jira/browse/AMBARI-20679 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20679.patch > > > *STR:* > # Click on Try button for any GET API > # This will show a pop up with the response of the API > Width of this popup should be wider and should be in ratio with the size of > the browser screen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20679) Size of API Response popup should be responsive as per the browser screen size
Oleg Nechiporenko created AMBARI-20679: -- Summary: Size of API Response popup should be responsive as per the browser screen size Key: AMBARI-20679 URL: https://issues.apache.org/jira/browse/AMBARI-20679 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 3.0.0 *STR:* # Click on Try button for any GET API # This will show a pop up with the response of the API Width of this popup should be wider and should be in ratio with the size of the browser screen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20609) Fix Install Wizard data attribute
[ https://issues.apache.org/jira/browse/AMBARI-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950765#comment-15950765 ] Oleg Nechiporenko commented on AMBARI-20609: +1 for AMBARI-20609-steps0-3.patch > Fix Install Wizard data attribute > -- > > Key: AMBARI-20609 > URL: https://issues.apache.org/jira/browse/AMBARI-20609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-20609-assign.patch, AMBARI-20609_review.patch, > AMBARI-20609-step4.patch, AMBARI-20609-steps0-3.patch > > > There have been a lot of frontend changes committed to trunk in preparation > for Ambari 3.0's new look and feel. > Obviously, this makes our current XPaths incompatible for trunk. > For starters, we need to make changes to XPaths and other changes necessary > so that we can at least run Install Wizard against the trunk code base. Also, > we need to make sure that Ambari Web's code itself is using best practices > with use of specific IDs and class names, etc. > We will implement special data attribute for XPaths -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20609) Fix Install Wizard data attribute
[ https://issues.apache.org/jira/browse/AMBARI-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20609: --- Attachment: AMBARI-20609_review.patch > Fix Install Wizard data attribute > -- > > Key: AMBARI-20609 > URL: https://issues.apache.org/jira/browse/AMBARI-20609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-20609-assign.patch, AMBARI-20609_review.patch, > AMBARI-20609-step4.patch > > > There have been a lot of frontend changes committed to trunk in preparation > for Ambari 3.0's new look and feel. > Obviously, this makes our current XPaths incompatible for trunk. > For starters, we need to make changes to XPaths and other changes necessary > so that we can at least run Install Wizard against the trunk code base. Also, > we need to make sure that Ambari Web's code itself is using best practices > with use of specific IDs and class names, etc. > We will implement special data attribute for XPaths -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20619) JS error on Step6 installer when click "all/none"
[
https://issues.apache.org/jira/browse/AMBARI-20619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20619:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> JS error on Step6 installer when click "all/none"
> -
>
> Key: AMBARI-20619
> URL: https://issues.apache.org/jira/browse/AMBARI-20619
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20619.patch
>
>
> Issue appears not every time you click "all" / "none"
> JS-error:
> {{Uncaught TypeError: Cannot read property 'then' of undefined}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20609) Fix Install Wizard data attribute
[ https://issues.apache.org/jira/browse/AMBARI-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20609: --- Attachment: AMBARI-20609-assign.patch > Fix Install Wizard data attribute > -- > > Key: AMBARI-20609 > URL: https://issues.apache.org/jira/browse/AMBARI-20609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-20609-assign.patch > > > There have been a lot of frontend changes committed to trunk in preparation > for Ambari 3.0's new look and feel. > Obviously, this makes our current XPaths incompatible for trunk. > For starters, we need to make changes to XPaths and other changes necessary > so that we can at least run Install Wizard against the trunk code base. Also, > we need to make sure that Ambari Web's code itself is using best practices > with use of specific IDs and class names, etc. > We will implement special data attribute for XPaths -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20609) Fix Install Wizard data attribute
[ https://issues.apache.org/jira/browse/AMBARI-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20609: --- Attachment: (was: AMBARI-20609-step5_6.patch) > Fix Install Wizard data attribute > -- > > Key: AMBARI-20609 > URL: https://issues.apache.org/jira/browse/AMBARI-20609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 3.0.0 > > > There have been a lot of frontend changes committed to trunk in preparation > for Ambari 3.0's new look and feel. > Obviously, this makes our current XPaths incompatible for trunk. > For starters, we need to make changes to XPaths and other changes necessary > so that we can at least run Install Wizard against the trunk code base. Also, > we need to make sure that Ambari Web's code itself is using best practices > with use of specific IDs and class names, etc. > We will implement special data attribute for XPaths -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (AMBARI-20609) Fix Install Wizard data attribute
[ https://issues.apache.org/jira/browse/AMBARI-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20609: --- Comment: was deleted (was: Patch for step5 and step6 is added) > Fix Install Wizard data attribute > -- > > Key: AMBARI-20609 > URL: https://issues.apache.org/jira/browse/AMBARI-20609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 3.0.0 > > > There have been a lot of frontend changes committed to trunk in preparation > for Ambari 3.0's new look and feel. > Obviously, this makes our current XPaths incompatible for trunk. > For starters, we need to make changes to XPaths and other changes necessary > so that we can at least run Install Wizard against the trunk code base. Also, > we need to make sure that Ambari Web's code itself is using best practices > with use of specific IDs and class names, etc. > We will implement special data attribute for XPaths -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20609) Fix Install Wizard data attribute
[ https://issues.apache.org/jira/browse/AMBARI-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947026#comment-15947026 ] Oleg Nechiporenko commented on AMBARI-20609: Patch for step5 and step6 is added > Fix Install Wizard data attribute > -- > > Key: AMBARI-20609 > URL: https://issues.apache.org/jira/browse/AMBARI-20609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-20609-step5_6.patch > > > There have been a lot of frontend changes committed to trunk in preparation > for Ambari 3.0's new look and feel. > Obviously, this makes our current XPaths incompatible for trunk. > For starters, we need to make changes to XPaths and other changes necessary > so that we can at least run Install Wizard against the trunk code base. Also, > we need to make sure that Ambari Web's code itself is using best practices > with use of specific IDs and class names, etc. > We will implement special data attribute for XPaths -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20609) Fix Install Wizard data attribute
[ https://issues.apache.org/jira/browse/AMBARI-20609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20609: --- Attachment: AMBARI-20609-step5_6.patch > Fix Install Wizard data attribute > -- > > Key: AMBARI-20609 > URL: https://issues.apache.org/jira/browse/AMBARI-20609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-20609-step5_6.patch > > > There have been a lot of frontend changes committed to trunk in preparation > for Ambari 3.0's new look and feel. > Obviously, this makes our current XPaths incompatible for trunk. > For starters, we need to make changes to XPaths and other changes necessary > so that we can at least run Install Wizard against the trunk code base. Also, > we need to make sure that Ambari Web's code itself is using best practices > with use of specific IDs and class names, etc. > We will implement special data attribute for XPaths -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20619) JS error on Step6 installer when click "all/none"
[
https://issues.apache.org/jira/browse/AMBARI-20619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947018#comment-15947018
]
Oleg Nechiporenko commented on AMBARI-20619:
Tested manually on the real cluster
> JS error on Step6 installer when click "all/none"
> -
>
> Key: AMBARI-20619
> URL: https://issues.apache.org/jira/browse/AMBARI-20619
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20619.patch
>
>
> Issue appears not every time you click "all" / "none"
> JS-error:
> {{Uncaught TypeError: Cannot read property 'then' of undefined}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20619) JS error on Step6 installer when click "all/none"
[
https://issues.apache.org/jira/browse/AMBARI-20619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20619:
---
Attachment: AMBARI-20619.patch
> JS error on Step6 installer when click "all/none"
> -
>
> Key: AMBARI-20619
> URL: https://issues.apache.org/jira/browse/AMBARI-20619
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20619.patch
>
>
> Issue appears not every time you click "all" / "none"
> JS-error:
> {{Uncaught TypeError: Cannot read property 'then' of undefined}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20619) JS error on Step6 installer when click "all/none"
[
https://issues.apache.org/jira/browse/AMBARI-20619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20619:
---
Status: Patch Available (was: Open)
+1 by [~BuzhorDenys] on the review board
> JS error on Step6 installer when click "all/none"
> -
>
> Key: AMBARI-20619
> URL: https://issues.apache.org/jira/browse/AMBARI-20619
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20619.patch
>
>
> Issue appears not every time you click "all" / "none"
> JS-error:
> {{Uncaught TypeError: Cannot read property 'then' of undefined}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20619) JS error on Step6 installer when click "all/none"
Oleg Nechiporenko created AMBARI-20619:
--
Summary: JS error on Step6 installer when click "all/none"
Key: AMBARI-20619
URL: https://issues.apache.org/jira/browse/AMBARI-20619
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 3.0.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Fix For: 3.0.0
Issue appears not every time you click "all" / "none"
JS-error:
{{Uncaught TypeError: Cannot read property 'then' of undefined}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20602) Comparison for configs with list of hostNames doesn't show all hosts correctly
[ https://issues.apache.org/jira/browse/AMBARI-20602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20602: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Comparison for configs with list of hostNames doesn't show all hosts correctly > -- > > Key: AMBARI-20602 > URL: https://issues.apache.org/jira/browse/AMBARI-20602 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20602.patch > > > Normal format for such configs - "HostName and N others". > Sometimes "HostName" is missing and value is shown as "and N others". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20602) Comparison for configs with list of hostNames doesn't show all hosts correctly
[ https://issues.apache.org/jira/browse/AMBARI-20602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20602: --- Status: Patch Available (was: Open) +1 by [~BuzhorDenys] on the review board > Comparison for configs with list of hostNames doesn't show all hosts correctly > -- > > Key: AMBARI-20602 > URL: https://issues.apache.org/jira/browse/AMBARI-20602 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20602.patch > > > Normal format for such configs - "HostName and N others". > Sometimes "HostName" is missing and value is shown as "and N others". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20602) Comparison for configs with list of hostNames doesn't show all hosts correctly
[ https://issues.apache.org/jira/browse/AMBARI-20602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20602: --- Attachment: AMBARI-20602.patch > Comparison for configs with list of hostNames doesn't show all hosts correctly > -- > > Key: AMBARI-20602 > URL: https://issues.apache.org/jira/browse/AMBARI-20602 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20602.patch > > > Normal format for such configs - "HostName and N others". > Sometimes "HostName" is missing and value is shown as "and N others". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20602) Comparison for configs with list of hostNames doesn't show all hosts correctly
Oleg Nechiporenko created AMBARI-20602: -- Summary: Comparison for configs with list of hostNames doesn't show all hosts correctly Key: AMBARI-20602 URL: https://issues.apache.org/jira/browse/AMBARI-20602 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 3.0.0 Normal format for such configs - "HostName and N others". Sometimes "HostName" is missing and value is shown as "and N others". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20577) Not all config groups are shown in the config history table
[
https://issues.apache.org/jira/browse/AMBARI-20577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20577:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Not all config groups are shown in the config history table
> ---
>
> Key: AMBARI-20577
> URL: https://issues.apache.org/jira/browse/AMBARI-20577
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20577.patch
>
>
> Filter view should be bound to the {{controller.content.[]}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20577) Not all config groups are shown in the config history table
[
https://issues.apache.org/jira/browse/AMBARI-20577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943139#comment-15943139
]
Oleg Nechiporenko commented on AMBARI-20577:
Committed to trunk
> Not all config groups are shown in the config history table
> ---
>
> Key: AMBARI-20577
> URL: https://issues.apache.org/jira/browse/AMBARI-20577
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20577.patch
>
>
> Filter view should be bound to the {{controller.content.[]}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20577) Not all config groups are shown in the config history table
[
https://issues.apache.org/jira/browse/AMBARI-20577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20577:
---
Status: Patch Available (was: Open)
+1 by [~BuzhorDenys] on the review board
> Not all config groups are shown in the config history table
> ---
>
> Key: AMBARI-20577
> URL: https://issues.apache.org/jira/browse/AMBARI-20577
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20577.patch
>
>
> Filter view should be bound to the {{controller.content.[]}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20577) Not all config groups are shown in the config history table
[
https://issues.apache.org/jira/browse/AMBARI-20577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20577:
---
Attachment: AMBARI-20577.patch
> Not all config groups are shown in the config history table
> ---
>
> Key: AMBARI-20577
> URL: https://issues.apache.org/jira/browse/AMBARI-20577
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20577.patch
>
>
> Filter view should be bound to the {{controller.content.[]}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20577) Not all config groups are shown in the config history table
Oleg Nechiporenko created AMBARI-20577:
--
Summary: Not all config groups are shown in the config history
table
Key: AMBARI-20577
URL: https://issues.apache.org/jira/browse/AMBARI-20577
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 3.0.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Fix For: 3.0.0
Filter view should be bound to the {{controller.content.[]}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20526) Config is not shown on comparison mode if it doesn't exist in the latest version
[
https://issues.apache.org/jira/browse/AMBARI-20526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938087#comment-15938087
]
Oleg Nechiporenko commented on AMBARI-20526:
Build failed not because of this patch
{noformat}
[INFO] Ambari Web . SUCCESS [05:24 min]
{noformat}
> Config is not shown on comparison mode if it doesn't exist in the latest
> version
>
>
> Key: AMBARI-20526
> URL: https://issues.apache.org/jira/browse/AMBARI-20526
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20526.patch
>
>
> * Add custom config and save configs
> * Remove this custom config and save configs
> * Compare this to config versions
> *ER* Config is shown as "Undefined"
> *AR* Config is not shown
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-20526) Config is not shown on comparison mode if it doesn't exist in the latest version
[ https://issues.apache.org/jira/browse/AMBARI-20526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko resolved AMBARI-20526. Resolution: Fixed > Config is not shown on comparison mode if it doesn't exist in the latest > version > > > Key: AMBARI-20526 > URL: https://issues.apache.org/jira/browse/AMBARI-20526 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20526.patch > > > * Add custom config and save configs > * Remove this custom config and save configs > * Compare this to config versions > *ER* Config is shown as "Undefined" > *AR* Config is not shown -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20526) Config is not shown on comparison mode if it doesn't exist in the latest version
[ https://issues.apache.org/jira/browse/AMBARI-20526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937909#comment-15937909 ] Oleg Nechiporenko commented on AMBARI-20526: +1 by [~jaimin] on the review board > Config is not shown on comparison mode if it doesn't exist in the latest > version > > > Key: AMBARI-20526 > URL: https://issues.apache.org/jira/browse/AMBARI-20526 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20526.patch > > > * Add custom config and save configs > * Remove this custom config and save configs > * Compare this to config versions > *ER* Config is shown as "Undefined" > *AR* Config is not shown -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20498) Ambari logo and title should not get hidden when user scrolls down the page
[ https://issues.apache.org/jira/browse/AMBARI-20498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20498: --- Attachment: AMBARI-20498.patch > Ambari logo and title should not get hidden when user scrolls down the page > --- > > Key: AMBARI-20498 > URL: https://issues.apache.org/jira/browse/AMBARI-20498 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20498.patch > > > As of now scrollbar is applied to the entire page. > Rather iAmbari logo and title "Ambari REST API explorer" div should be > static. So when user scrolls down to see APIs, logo and title is still > visible on the top of the page -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20498) Ambari logo and title should not get hidden when user scrolls down the page
Oleg Nechiporenko created AMBARI-20498: -- Summary: Ambari logo and title should not get hidden when user scrolls down the page Key: AMBARI-20498 URL: https://issues.apache.org/jira/browse/AMBARI-20498 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 3.0.0 As of now scrollbar is applied to the entire page. Rather iAmbari logo and title "Ambari REST API explorer" div should be static. So when user scrolls down to see APIs, logo and title is still visible on the top of the page -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20495) Ambari REST API explorer should show ambari logo
[ https://issues.apache.org/jira/browse/AMBARI-20495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20495: --- Issue Type: Task (was: Bug) > Ambari REST API explorer should show ambari logo > > > Key: AMBARI-20495 > URL: https://issues.apache.org/jira/browse/AMBARI-20495 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20495.patch > > > clicking on the logo should route to ambari -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20481) Start/Stop Service command may silently fail without any reporting for user
[
https://issues.apache.org/jira/browse/AMBARI-20481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20481:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Start/Stop Service command may silently fail without any reporting for user
> ---
>
> Key: AMBARI-20481
> URL: https://issues.apache.org/jira/browse/AMBARI-20481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20481.patch
>
>
> * Go to HDFS
> * Click "Start" or "Stop" on Service Actions menu
> * Request may fails
> *ER* Popup with reason should be shown (e.g. {{defaultErrorHandler}})
> *AR* Nothing happens
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20495) Ambari REST API explorer should show ambari logo
[ https://issues.apache.org/jira/browse/AMBARI-20495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20495: --- Attachment: AMBARI-20495.patch > Ambari REST API explorer should show ambari logo > > > Key: AMBARI-20495 > URL: https://issues.apache.org/jira/browse/AMBARI-20495 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20495.patch > > > clicking on the logo should route to ambari -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20495) Ambari REST API explorer should show ambari logo
Oleg Nechiporenko created AMBARI-20495: -- Summary: Ambari REST API explorer should show ambari logo Key: AMBARI-20495 URL: https://issues.apache.org/jira/browse/AMBARI-20495 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 3.0.0 clicking on the logo should route to ambari -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20481) Start/Stop Service command may silently fail without any reporting for user
[
https://issues.apache.org/jira/browse/AMBARI-20481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929564#comment-15929564
]
Oleg Nechiporenko commented on AMBARI-20481:
Committed to trunk
> Start/Stop Service command may silently fail without any reporting for user
> ---
>
> Key: AMBARI-20481
> URL: https://issues.apache.org/jira/browse/AMBARI-20481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20481.patch
>
>
> * Go to HDFS
> * Click "Start" or "Stop" on Service Actions menu
> * Request may fails
> *ER* Popup with reason should be shown (e.g. {{defaultErrorHandler}})
> *AR* Nothing happens
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20458) Admin/Version page doesn't mark StackAndVersion item as active
[ https://issues.apache.org/jira/browse/AMBARI-20458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20458: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Admin/Version page doesn't mark StackAndVersion item as active > -- > > Key: AMBARI-20458 > URL: https://issues.apache.org/jira/browse/AMBARI-20458 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20458.patch > > > * Go to Admin Stacks page > * "Stack and Versions" item in the main menu is shown as active > * Click on Versions Tab > *ER* "Stack and Versions" item is active > *AR* "Stack and Versions" item is not active -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20481) Start/Stop Service command may silently fail without any reporting for user
[
https://issues.apache.org/jira/browse/AMBARI-20481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20481:
---
Status: Patch Available (was: Open)
+1 by [~BuzhorDenys] on the review board
> Start/Stop Service command may silently fail without any reporting for user
> ---
>
> Key: AMBARI-20481
> URL: https://issues.apache.org/jira/browse/AMBARI-20481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20481.patch
>
>
> * Go to HDFS
> * Click "Start" or "Stop" on Service Actions menu
> * Request may fails
> *ER* Popup with reason should be shown (e.g. {{defaultErrorHandler}})
> *AR* Nothing happens
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20481) Start/Stop Service command may silently fail without any reporting for user
[
https://issues.apache.org/jira/browse/AMBARI-20481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20481:
---
Attachment: AMBARI-20481.patch
> Start/Stop Service command may silently fail without any reporting for user
> ---
>
> Key: AMBARI-20481
> URL: https://issues.apache.org/jira/browse/AMBARI-20481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20481.patch
>
>
> * Go to HDFS
> * Click "Start" or "Stop" on Service Actions menu
> * Request may fails
> *ER* Popup with reason should be shown (e.g. {{defaultErrorHandler}})
> *AR* Nothing happens
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20481) Start/Stop Service command may silently fail without any reporting for user
Oleg Nechiporenko created AMBARI-20481:
--
Summary: Start/Stop Service command may silently fail without any
reporting for user
Key: AMBARI-20481
URL: https://issues.apache.org/jira/browse/AMBARI-20481
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 3.0.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Fix For: 3.0.0
* Go to HDFS
* Click "Start" or "Stop" on Service Actions menu
* Request may fails
*ER* Popup with reason should be shown (e.g. {{defaultErrorHandler}})
*AR* Nothing happens
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20456) Few breadcrumbs are missing
[ https://issues.apache.org/jira/browse/AMBARI-20456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20456: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Few breadcrumbs are missing > --- > > Key: AMBARI-20456 > URL: https://issues.apache.org/jira/browse/AMBARI-20456 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20456.patch > > > * admin/stack/versions > * admin/stack/history > * some views > Add ability to generate breadcrumbs from Routes if they are not set manually -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20458) Admin/Version page doesn't mark StackAndVersion item as active
[ https://issues.apache.org/jira/browse/AMBARI-20458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926201#comment-15926201 ] Oleg Nechiporenko commented on AMBARI-20458: Committed to trunk > Admin/Version page doesn't mark StackAndVersion item as active > -- > > Key: AMBARI-20458 > URL: https://issues.apache.org/jira/browse/AMBARI-20458 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20458.patch > > > * Go to Admin Stacks page > * "Stack and Versions" item in the main menu is shown as active > * Click on Versions Tab > *ER* "Stack and Versions" item is active > *AR* "Stack and Versions" item is not active -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20458) Admin/Version page doesn't mark StackAndVersion item as active
[ https://issues.apache.org/jira/browse/AMBARI-20458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20458: --- Status: Patch Available (was: Open) > Admin/Version page doesn't mark StackAndVersion item as active > -- > > Key: AMBARI-20458 > URL: https://issues.apache.org/jira/browse/AMBARI-20458 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20458.patch > > > * Go to Admin Stacks page > * "Stack and Versions" item in the main menu is shown as active > * Click on Versions Tab > *ER* "Stack and Versions" item is active > *AR* "Stack and Versions" item is not active -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20458) Admin/Version page doesn't mark StackAndVersion item as active
[ https://issues.apache.org/jira/browse/AMBARI-20458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926056#comment-15926056 ] Oleg Nechiporenko commented on AMBARI-20458: +1 by [~BuzhorDenys] on the review board > Admin/Version page doesn't mark StackAndVersion item as active > -- > > Key: AMBARI-20458 > URL: https://issues.apache.org/jira/browse/AMBARI-20458 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20458.patch > > > * Go to Admin Stacks page > * "Stack and Versions" item in the main menu is shown as active > * Click on Versions Tab > *ER* "Stack and Versions" item is active > *AR* "Stack and Versions" item is not active -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20458) Admin/Version page doesn't mark StackAndVersion item as active
[ https://issues.apache.org/jira/browse/AMBARI-20458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20458: --- Attachment: AMBARI-20458.patch > Admin/Version page doesn't mark StackAndVersion item as active > -- > > Key: AMBARI-20458 > URL: https://issues.apache.org/jira/browse/AMBARI-20458 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20458.patch > > > * Go to Admin Stacks page > * "Stack and Versions" item in the main menu is shown as active > * Click on Versions Tab > *ER* "Stack and Versions" item is active > *AR* "Stack and Versions" item is not active -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20458) Admin/Version page doesn't mark StackAndVersion item as active
Oleg Nechiporenko created AMBARI-20458: -- Summary: Admin/Version page doesn't mark StackAndVersion item as active Key: AMBARI-20458 URL: https://issues.apache.org/jira/browse/AMBARI-20458 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 3.0.0 * Go to Admin Stacks page * "Stack and Versions" item in the main menu is shown as active * Click on Versions Tab *ER* "Stack and Versions" item is active *AR* "Stack and Versions" item is not active -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20456) Few breadcrumbs are missing
[ https://issues.apache.org/jira/browse/AMBARI-20456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925951#comment-15925951 ] Oleg Nechiporenko commented on AMBARI-20456: Committed to trunk > Few breadcrumbs are missing > --- > > Key: AMBARI-20456 > URL: https://issues.apache.org/jira/browse/AMBARI-20456 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20456.patch > > > * admin/stack/versions > * admin/stack/history > * some views > Add ability to generate breadcrumbs from Routes if they are not set manually -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20456) Few breadcrumbs are missing
[ https://issues.apache.org/jira/browse/AMBARI-20456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20456: --- Status: Patch Available (was: Open) +1 by [~BuzhorDenys] on the review board > Few breadcrumbs are missing > --- > > Key: AMBARI-20456 > URL: https://issues.apache.org/jira/browse/AMBARI-20456 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20456.patch > > > * admin/stack/versions > * admin/stack/history > * some views > Add ability to generate breadcrumbs from Routes if they are not set manually -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20456) Few breadcrumbs are missing
[ https://issues.apache.org/jira/browse/AMBARI-20456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20456: --- Attachment: AMBARI-20456.patch > Few breadcrumbs are missing > --- > > Key: AMBARI-20456 > URL: https://issues.apache.org/jira/browse/AMBARI-20456 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20456.patch > > > * admin/stack/versions > * admin/stack/history > * some views > Add ability to generate breadcrumbs from Routes if they are not set manually -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20456) Few breadcrumbs are missing
Oleg Nechiporenko created AMBARI-20456: -- Summary: Few breadcrumbs are missing Key: AMBARI-20456 URL: https://issues.apache.org/jira/browse/AMBARI-20456 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 3.0.0 * admin/stack/versions * admin/stack/history * some views Add ability to generate breadcrumbs from Routes if they are not set manually -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20441) Alert Definition "Last Changed" field is shown incorrect if alert wan't triggered any time
[ https://issues.apache.org/jira/browse/AMBARI-20441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924171#comment-15924171 ] Oleg Nechiporenko commented on AMBARI-20441: Patch was already committed > Alert Definition "Last Changed" field is shown incorrect if alert wan't > triggered any time > -- > > Key: AMBARI-20441 > URL: https://issues.apache.org/jira/browse/AMBARI-20441 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20441.patch > > > * Go to Alert Definition details page for Definition with NONE status (e.g. > "NameNode Heap Usage (Daily)") > *AR* "Last Changed" is shown as "Jan 01 1970" > *ER* This field should be empty -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20441) Alert Definition "Last Changed" field is shown incorrect if alert wan't triggered any time
[ https://issues.apache.org/jira/browse/AMBARI-20441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20441: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Alert Definition "Last Changed" field is shown incorrect if alert wan't > triggered any time > -- > > Key: AMBARI-20441 > URL: https://issues.apache.org/jira/browse/AMBARI-20441 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20441.patch > > > * Go to Alert Definition details page for Definition with NONE status (e.g. > "NameNode Heap Usage (Daily)") > *AR* "Last Changed" is shown as "Jan 01 1970" > *ER* This field should be empty -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20441) Alert Definition "Last Changed" field is shown incorrect if alert wan't triggered any time
[ https://issues.apache.org/jira/browse/AMBARI-20441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923953#comment-15923953 ] Oleg Nechiporenko commented on AMBARI-20441: Committed to trunk > Alert Definition "Last Changed" field is shown incorrect if alert wan't > triggered any time > -- > > Key: AMBARI-20441 > URL: https://issues.apache.org/jira/browse/AMBARI-20441 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20441.patch > > > * Go to Alert Definition details page for Definition with NONE status (e.g. > "NameNode Heap Usage (Daily)") > *AR* "Last Changed" is shown as "Jan 01 1970" > *ER* This field should be empty -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20441) Alert Definition "Last Changed" field is shown incorrect if alert wan't triggered any time
[ https://issues.apache.org/jira/browse/AMBARI-20441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20441: --- Status: Patch Available (was: Open) +1 by [~BuzhorDenys] on the review board > Alert Definition "Last Changed" field is shown incorrect if alert wan't > triggered any time > -- > > Key: AMBARI-20441 > URL: https://issues.apache.org/jira/browse/AMBARI-20441 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20441.patch > > > * Go to Alert Definition details page for Definition with NONE status (e.g. > "NameNode Heap Usage (Daily)") > *AR* "Last Changed" is shown as "Jan 01 1970" > *ER* This field should be empty -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20441) Alert Definition "Last Changed" field is shown incorrect if alert wan't triggered any time
[ https://issues.apache.org/jira/browse/AMBARI-20441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-20441: --- Attachment: AMBARI-20441.patch > Alert Definition "Last Changed" field is shown incorrect if alert wan't > triggered any time > -- > > Key: AMBARI-20441 > URL: https://issues.apache.org/jira/browse/AMBARI-20441 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-20441.patch > > > * Go to Alert Definition details page for Definition with NONE status (e.g. > "NameNode Heap Usage (Daily)") > *AR* "Last Changed" is shown as "Jan 01 1970" > *ER* This field should be empty -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20441) Alert Definition "Last Changed" field is shown incorrect if alert wan't triggered any time
Oleg Nechiporenko created AMBARI-20441: -- Summary: Alert Definition "Last Changed" field is shown incorrect if alert wan't triggered any time Key: AMBARI-20441 URL: https://issues.apache.org/jira/browse/AMBARI-20441 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 3.0.0 * Go to Alert Definition details page for Definition with NONE status (e.g. "NameNode Heap Usage (Daily)") *AR* "Last Changed" is shown as "Jan 01 1970" *ER* This field should be empty -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20415) JS error when filtering config history table
[
https://issues.apache.org/jira/browse/AMBARI-20415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923868#comment-15923868
]
Oleg Nechiporenko commented on AMBARI-20415:
Build failed not because of this patch
https://builds.apache.org/job/Ambari-branch-2.5/1243/console:
{noformat}
[INFO] Ambari Web . SUCCESS [02:38 min]
[INFO] Ambari Server .. FAILURE [20:34 min]
{noformat}
https://builds.apache.org/job/Ambari-trunk-Commit/7018/console:
{noformat}
[INFO] Ambari Web . SUCCESS [04:22 min]
[INFO] Ambari Server .. FAILURE [20:31 min]
{noformat}
> JS error when filtering config history table
>
>
> Key: AMBARI-20415
> URL: https://issues.apache.org/jira/browse/AMBARI-20415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20415.patch
>
>
> * Open Config History Page
> * Filter table by Group Name
> *AR* JS-error appears:
> {noformat}Uncaught TypeError: this.saveStartIndex is not a function{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20415) JS error when filtering config history table
[
https://issues.apache.org/jira/browse/AMBARI-20415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20415:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> JS error when filtering config history table
>
>
> Key: AMBARI-20415
> URL: https://issues.apache.org/jira/browse/AMBARI-20415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20415.patch
>
>
> * Open Config History Page
> * Filter table by Group Name
> *AR* JS-error appears:
> {noformat}Uncaught TypeError: this.saveStartIndex is not a function{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-20415) JS error when filtering config history table
[
https://issues.apache.org/jira/browse/AMBARI-20415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923868#comment-15923868
]
Oleg Nechiporenko edited comment on AMBARI-20415 at 3/14/17 9:27 AM:
-
Build failed not because of this patch
https://builds.apache.org/job/Ambari-branch-2.5/1243/console :
{noformat}
[INFO] Ambari Web . SUCCESS [02:38 min]
[INFO] Ambari Server .. FAILURE [20:34 min]
{noformat}
https://builds.apache.org/job/Ambari-trunk-Commit/7018/console :
{noformat}
[INFO] Ambari Web . SUCCESS [04:22 min]
[INFO] Ambari Server .. FAILURE [20:31 min]
{noformat}
was (Author: onechiporenko):
Build failed not because of this patch
https://builds.apache.org/job/Ambari-branch-2.5/1243/console:
{noformat}
[INFO] Ambari Web . SUCCESS [02:38 min]
[INFO] Ambari Server .. FAILURE [20:34 min]
{noformat}
https://builds.apache.org/job/Ambari-trunk-Commit/7018/console:
{noformat}
[INFO] Ambari Web . SUCCESS [04:22 min]
[INFO] Ambari Server .. FAILURE [20:31 min]
{noformat}
> JS error when filtering config history table
>
>
> Key: AMBARI-20415
> URL: https://issues.apache.org/jira/browse/AMBARI-20415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20415.patch
>
>
> * Open Config History Page
> * Filter table by Group Name
> *AR* JS-error appears:
> {noformat}Uncaught TypeError: this.saveStartIndex is not a function{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20415) JS error when filtering config history table
[
https://issues.apache.org/jira/browse/AMBARI-20415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907588#comment-15907588
]
Oleg Nechiporenko commented on AMBARI-20415:
Committed to trunk and 2.5
> JS error when filtering config history table
>
>
> Key: AMBARI-20415
> URL: https://issues.apache.org/jira/browse/AMBARI-20415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20415.patch
>
>
> * Open Config History Page
> * Filter table by Group Name
> *AR* JS-error appears:
> {noformat}Uncaught TypeError: this.saveStartIndex is not a function{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20415) JS error when filtering config history table
[
https://issues.apache.org/jira/browse/AMBARI-20415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20415:
---
Status: Patch Available (was: Open)
+1 by [~atkach] on the review board
> JS error when filtering config history table
>
>
> Key: AMBARI-20415
> URL: https://issues.apache.org/jira/browse/AMBARI-20415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20415.patch
>
>
> * Open Config History Page
> * Filter table by Group Name
> *AR* JS-error appears:
> {noformat}Uncaught TypeError: this.saveStartIndex is not a function{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20415) JS error when filtering config history table
[
https://issues.apache.org/jira/browse/AMBARI-20415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20415:
---
Attachment: AMBARI-20415.patch
> JS error when filtering config history table
>
>
> Key: AMBARI-20415
> URL: https://issues.apache.org/jira/browse/AMBARI-20415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-20415.patch
>
>
> * Open Config History Page
> * Filter table by Group Name
> *AR* JS-error appears:
> {noformat}Uncaught TypeError: this.saveStartIndex is not a function{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20415) JS error when filtering config history table
Oleg Nechiporenko created AMBARI-20415:
--
Summary: JS error when filtering config history table
Key: AMBARI-20415
URL: https://issues.apache.org/jira/browse/AMBARI-20415
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Fix For: 2.5.0
* Open Config History Page
* Filter table by Group Name
*AR* JS-error appears:
{noformat}Uncaught TypeError: this.saveStartIndex is not a function{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20388) Diff tool shows additional line when comparing configs from custom config group
[ https://issues.apache.org/jira/browse/AMBARI-20388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko reassigned AMBARI-20388: -- Assignee: Oleg Nechiporenko > Diff tool shows additional line when comparing configs from custom config > group > --- > > Key: AMBARI-20388 > URL: https://issues.apache.org/jira/browse/AMBARI-20388 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Oleg Nechiporenko > Fix For: 2.5.0 > > > - Create a custom config group for a service > - Update few properties and save to get a version for this custom group > - Add another property and save just to generate more config version > - Compare these 2 versions. Usually diff shows only the values from compared > versions > - But looks like it shows the current value and the values in each version as > well. > - In default group we dont see that extra line with the current value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20375:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903139#comment-15903139
]
Oleg Nechiporenko commented on AMBARI-20375:
Committed to trunk
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903137#comment-15903137
]
Oleg Nechiporenko commented on AMBARI-20375:
Tested manually on the real cluster
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20376) While Moving Namenode via Move Master wizard, datanodes reported as down
[
https://issues.apache.org/jira/browse/AMBARI-20376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902987#comment-15902987
]
Oleg Nechiporenko commented on AMBARI-20376:
+1 for patch
> While Moving Namenode via Move Master wizard, datanodes reported as down
>
>
> Key: AMBARI-20376
> URL: https://issues.apache.org/jira/browse/AMBARI-20376
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20376.patch
>
>
> While Moving Namenode via Move Master wizard, datanodes reported as down
> while starting ATS.
> Seeing this in a couple of splits today. ATS fails to start showing there are
> no live datanodes
> {code}
> {
> "RemoteException": {
> "exception": "RetriableException",
> "javaClassName": "org.apache.hadoop.ipc.RetriableException",
> "message": "org.apache.hadoop.hdfs.server.namenode.SafeModeException:
> Cannot set permission for /ats/done. Name node is in safe mode.\nThe reported
> blocks 934 has reached the threshold 0.9900 of total blocks 934. The number
> of live datanodes 3 has reached the minimum number 0. In safe mode extension.
> Safe mode will be turned off automatically in 21 seconds."
> }
> }
> {code}
> The step before ATS start, starts datanode explicitly. On retry ATS will
> possibly come up. But no retries were needed before
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20375:
---
Status: Patch Available (was: Open)
+1 by [~BuzhorDenys] on the review board
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Nechiporenko updated AMBARI-20375:
---
Attachment: AMBARI-20375.patch
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20375) Remove duplicate code from wizard menu
Oleg Nechiporenko created AMBARI-20375:
--
Summary: Remove duplicate code from wizard menu
Key: AMBARI-20375
URL: https://issues.apache.org/jira/browse/AMBARI-20375
Project: Ambari
Issue Type: Task
Components: ambari-web
Affects Versions: 3.0.0
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Fix For: 3.0.0
{{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as computed
macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
