[jira] [Updated] (AMBARI-18844) Web Client Should Support HOST_ORDERED Upgrades In Progress
[
https://issues.apache.org/jira/browse/AMBARI-18844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-18844:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Web Client Should Support HOST_ORDERED Upgrades In Progress
> ---
>
> Key: AMBARI-18844
> URL: https://issues.apache.org/jira/browse/AMBARI-18844
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18844.patch, AMBARI-18844_branch-2.5.patch
>
>
> {{HOST_ORDERED}} upgrades which are initiated from the APIs currently don't
> show up as an upgrade "In Progress" in the web client. Although this upgrade
> type is not going to be exposed as a first-class upgrade type for Ambari 2.5,
> the web client must still behave correctly when encountering a
> {{HOST_ORDERED}} upgrade already running.
> The following criteria should be met:
> - The web client displays a banner that there is an upgrade in progress (or
> holding or waiting for input, etc) just like it would for other upgrade types.
> - Destructive behavior such as running commands, adding/remove
> hosts/services, changing configs, etc, should be prevented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18844) Web Client Should Support HOST_ORDERED Upgrades In Progress
[
https://issues.apache.org/jira/browse/AMBARI-18844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-18844:
--
Status: Patch Available (was: Open)
> Web Client Should Support HOST_ORDERED Upgrades In Progress
> ---
>
> Key: AMBARI-18844
> URL: https://issues.apache.org/jira/browse/AMBARI-18844
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18844.patch, AMBARI-18844_branch-2.5.patch
>
>
> {{HOST_ORDERED}} upgrades which are initiated from the APIs currently don't
> show up as an upgrade "In Progress" in the web client. Although this upgrade
> type is not going to be exposed as a first-class upgrade type for Ambari 2.5,
> the web client must still behave correctly when encountering a
> {{HOST_ORDERED}} upgrade already running.
> The following criteria should be met:
> - The web client displays a banner that there is an upgrade in progress (or
> holding or waiting for input, etc) just like it would for other upgrade types.
> - Destructive behavior such as running commands, adding/remove
> hosts/services, changing configs, etc, should be prevented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18844) Web Client Should Support HOST_ORDERED Upgrades In Progress
[
https://issues.apache.org/jira/browse/AMBARI-18844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-18844:
--
Attachment: AMBARI-18844_branch-2.5.patch
> Web Client Should Support HOST_ORDERED Upgrades In Progress
> ---
>
> Key: AMBARI-18844
> URL: https://issues.apache.org/jira/browse/AMBARI-18844
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18844.patch, AMBARI-18844_branch-2.5.patch
>
>
> {{HOST_ORDERED}} upgrades which are initiated from the APIs currently don't
> show up as an upgrade "In Progress" in the web client. Although this upgrade
> type is not going to be exposed as a first-class upgrade type for Ambari 2.5,
> the web client must still behave correctly when encountering a
> {{HOST_ORDERED}} upgrade already running.
> The following criteria should be met:
> - The web client displays a banner that there is an upgrade in progress (or
> holding or waiting for input, etc) just like it would for other upgrade types.
> - Destructive behavior such as running commands, adding/remove
> hosts/services, changing configs, etc, should be prevented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18844) Web Client Should Support HOST_ORDERED Upgrades In Progress
[
https://issues.apache.org/jira/browse/AMBARI-18844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-18844:
--
Attachment: AMBARI-18844.patch
> Web Client Should Support HOST_ORDERED Upgrades In Progress
> ---
>
> Key: AMBARI-18844
> URL: https://issues.apache.org/jira/browse/AMBARI-18844
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18844.patch, AMBARI-18844_branch-2.5.patch
>
>
> {{HOST_ORDERED}} upgrades which are initiated from the APIs currently don't
> show up as an upgrade "In Progress" in the web client. Although this upgrade
> type is not going to be exposed as a first-class upgrade type for Ambari 2.5,
> the web client must still behave correctly when encountering a
> {{HOST_ORDERED}} upgrade already running.
> The following criteria should be met:
> - The web client displays a banner that there is an upgrade in progress (or
> holding or waiting for input, etc) just like it would for other upgrade types.
> - Destructive behavior such as running commands, adding/remove
> hosts/services, changing configs, etc, should be prevented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18844) Web Client Should Support HOST_ORDERED Upgrades In Progress
[
https://issues.apache.org/jira/browse/AMBARI-18844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-18844:
--
Attachment: (was: AMBARI-18844.patch)
> Web Client Should Support HOST_ORDERED Upgrades In Progress
> ---
>
> Key: AMBARI-18844
> URL: https://issues.apache.org/jira/browse/AMBARI-18844
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18844.patch, AMBARI-18844_branch-2.5.patch
>
>
> {{HOST_ORDERED}} upgrades which are initiated from the APIs currently don't
> show up as an upgrade "In Progress" in the web client. Although this upgrade
> type is not going to be exposed as a first-class upgrade type for Ambari 2.5,
> the web client must still behave correctly when encountering a
> {{HOST_ORDERED}} upgrade already running.
> The following criteria should be met:
> - The web client displays a banner that there is an upgrade in progress (or
> holding or waiting for input, etc) just like it would for other upgrade types.
> - Destructive behavior such as running commands, adding/remove
> hosts/services, changing configs, etc, should be prevented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18844) Web Client Should Support HOST_ORDERED Upgrades In Progress
[
https://issues.apache.org/jira/browse/AMBARI-18844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-18844:
--
Attachment: AMBARI-18844.patch
> Web Client Should Support HOST_ORDERED Upgrades In Progress
> ---
>
> Key: AMBARI-18844
> URL: https://issues.apache.org/jira/browse/AMBARI-18844
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18844.patch
>
>
> {{HOST_ORDERED}} upgrades which are initiated from the APIs currently don't
> show up as an upgrade "In Progress" in the web client. Although this upgrade
> type is not going to be exposed as a first-class upgrade type for Ambari 2.5,
> the web client must still behave correctly when encountering a
> {{HOST_ORDERED}} upgrade already running.
> The following criteria should be met:
> - The web client displays a banner that there is an upgrade in progress (or
> holding or waiting for input, etc) just like it would for other upgrade types.
> - Destructive behavior such as running commands, adding/remove
> hosts/services, changing configs, etc, should be prevented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
