[jira] [Updated] (AMBARI-23444) Allow Custom Hooks on a Per-Role Basis
[
https://issues.apache.org/jira/browse/AMBARI-23444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-23444:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Allow Custom Hooks on a Per-Role Basis
> --
>
> Key: AMBARI-23444
> URL: https://issues.apache.org/jira/browse/AMBARI-23444
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent, ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Labels: pull-request-available
> Fix For: trunk
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Expand hooks with a service-specific hooks. In addition, we must use custom
> command parameters to help with this. For examples:
> {{before-KAFKA-INSTALL}}
> {{after-STORM-START}}
> {{after-KAFKA-RESTART}} <-- this is a custom command, not a "regular" command
>
> The more-specific hooks should execute tightly to the command script. For
> example:
> {{before-INSTALL}}
> {{before-KAFKA-INSTALL}}
> install script for Kafka
> {{after-KAFKA-INSTALL}}
> {{after-INSTALL}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25050) Create Ambari Setting to Control VDF Filesystem Access
Nate Cole created AMBARI-25050:
--
Summary: Create Ambari Setting to Control VDF Filesystem Access
Key: AMBARI-25050
URL: https://issues.apache.org/jira/browse/AMBARI-25050
Project: Ambari
Issue Type: Task
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 2.8.0
Create an entry in {{ambari.properties}} to control whether to allow reading
filesystem VDF. Default {{false}} for this access.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-25036) Update Stack Classloader Loading Pattern
[
https://issues.apache.org/jira/browse/AMBARI-25036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-25036.
Resolution: Fixed
> Update Stack Classloader Loading Pattern
>
>
> Key: AMBARI-25036
> URL: https://issues.apache.org/jira/browse/AMBARI-25036
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Update the {{StackInfo}} to load an instance of a class with its own
> classloader
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25036) Update Stack Classloader Loading Pattern
Nate Cole created AMBARI-25036:
--
Summary: Update Stack Classloader Loading Pattern
Key: AMBARI-25036
URL: https://issues.apache.org/jira/browse/AMBARI-25036
Project: Ambari
Issue Type: Task
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 2.8.0
Update the {{StackInfo}} to load an instance of a class with its own classloader
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-25002) Allow Stack To Define Custom Rolling Orchestration Logic
[ https://issues.apache.org/jira/browse/AMBARI-25002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-25002. Resolution: Fixed > Allow Stack To Define Custom Rolling Orchestration Logic > > > Key: AMBARI-25002 > URL: https://issues.apache.org/jira/browse/AMBARI-25002 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-server-spi >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > Use the SPI to allow stacks to provide their own code-based logic classes. > The first iteration will allow a stack to compute how many slave components > can run at the same time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25002) Allow Stack To Define Custom Rolling Orchestration Logic
Nate Cole created AMBARI-25002: -- Summary: Allow Stack To Define Custom Rolling Orchestration Logic Key: AMBARI-25002 URL: https://issues.apache.org/jira/browse/AMBARI-25002 Project: Ambari Issue Type: Task Components: ambari-server, ambari-server-spi Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.8.0 Use the SPI to allow stacks to provide their own code-based logic classes. The first iteration will allow a stack to compute how many slave components can run at the same time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24909) Parallel Client Fixes for Server Side Tasks
[ https://issues.apache.org/jira/browse/AMBARI-24909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-24909. Resolution: Fixed > Parallel Client Fixes for Server Side Tasks > --- > > Key: AMBARI-24909 > URL: https://issues.apache.org/jira/browse/AMBARI-24909 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The fix for parallel clients (AMBARI-24873) was broken for server-side action > tasks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24909) Parallel Client Fixes for Server Side Tasks
Nate Cole created AMBARI-24909: -- Summary: Parallel Client Fixes for Server Side Tasks Key: AMBARI-24909 URL: https://issues.apache.org/jira/browse/AMBARI-24909 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.8.0 The fix for parallel clients (AMBARI-24873) was broken for server-side action tasks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24873) Rolling Upgrade Orchestration Changes For Client Performance
[ https://issues.apache.org/jira/browse/AMBARI-24873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-24873. Resolution: Fixed > Rolling Upgrade Orchestration Changes For Client Performance > > > Key: AMBARI-24873 > URL: https://issues.apache.org/jira/browse/AMBARI-24873 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Allow a new grouping for clients whereby: > * The first client is upgraded > * Run a service check on the first client to verify configs, etc. > * Run balance of clients in parallel -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24873) Rolling Upgrade Orchestration Changes For Client Performance
Nate Cole created AMBARI-24873: -- Summary: Rolling Upgrade Orchestration Changes For Client Performance Key: AMBARI-24873 URL: https://issues.apache.org/jira/browse/AMBARI-24873 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.8.0 Allow a new grouping for clients whereby: * The first client is upgraded * Run a service check on the first client to verify configs, etc. * Run balance of clients in parallel -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24780) Add Hotfix to VDF Release Element
[
https://issues.apache.org/jira/browse/AMBARI-24780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-24780.
Resolution: Fixed
> Add Hotfix to VDF Release Element
> -
>
> Key: AMBARI-24780
> URL: https://issues.apache.org/jira/browse/AMBARI-24780
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> VDF should allow for an optional element: {{hotfix}} that is separate from
> the build number. In addition, the stack should be flexible enough to supply
> how version information is formatted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24780) Add Hotfix to VDF Release Element
[
https://issues.apache.org/jira/browse/AMBARI-24780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-24780:
---
Summary: Add Hotfix to VDF Release Element (was: VDF Should Allow Hotfix)
> Add Hotfix to VDF Release Element
> -
>
> Key: AMBARI-24780
> URL: https://issues.apache.org/jira/browse/AMBARI-24780
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.8.0
>
>
> VDF should allow for an optional element: {{hotfix}} that is separate from
> the build number. In addition, the stack should be flexible enough to supply
> how version information is formatted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24780) VDF Should Allow Hotfix
Nate Cole created AMBARI-24780:
--
Summary: VDF Should Allow Hotfix
Key: AMBARI-24780
URL: https://issues.apache.org/jira/browse/AMBARI-24780
Project: Ambari
Issue Type: Task
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 2.8.0
VDF should allow for an optional element: {{hotfix}} that is separate from the
build number. In addition, the stack should be flexible enough to supply how
version information is formatted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24728) Orchestration Should Save Upgrade Pack for source or target
[ https://issues.apache.org/jira/browse/AMBARI-24728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-24728. Resolution: Fixed > Orchestration Should Save Upgrade Pack for source or target > --- > > Key: AMBARI-24728 > URL: https://issues.apache.org/jira/browse/AMBARI-24728 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Stacks may now contain source stack information. Make sure that when > orchestration happens that we indicate how to find the upgrade pack which was > resolved and persist it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24728) Orchestration Should Save Upgrade Pack for source or target
Nate Cole created AMBARI-24728: -- Summary: Orchestration Should Save Upgrade Pack for source or target Key: AMBARI-24728 URL: https://issues.apache.org/jira/browse/AMBARI-24728 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.8.0 Stacks may now contain source stack information. Make sure that when orchestration happens that we indicate how to find the upgrade pack which was resolved and persist it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24691) Refactor Upgrade Classes to Proper Packages
[ https://issues.apache.org/jira/browse/AMBARI-24691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-24691. Resolution: Fixed > Refactor Upgrade Classes to Proper Packages > --- > > Key: AMBARI-24691 > URL: https://issues.apache.org/jira/browse/AMBARI-24691 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > With SPI changes, key upgrade classes should move to the correct package to > separate definition from orchestration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24691) Refactor Upgrade Classes to Proper Packages
Nate Cole created AMBARI-24691: -- Summary: Refactor Upgrade Classes to Proper Packages Key: AMBARI-24691 URL: https://issues.apache.org/jira/browse/AMBARI-24691 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole With SPI changes, key upgrade classes should move to the correct package to separate definition from orchestration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24687) Upgrade Pack Should Allow Source Information
[
https://issues.apache.org/jira/browse/AMBARI-24687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-24687.
Resolution: Fixed
> Upgrade Pack Should Allow Source Information
>
>
> Key: AMBARI-24687
> URL: https://issues.apache.org/jira/browse/AMBARI-24687
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Allow Upgrade Packs to specify {{source}} information in addition to
> {{target}} (for backward compatibility)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24687) Upgrade Pack Should Allow Source Information
Nate Cole created AMBARI-24687:
--
Summary: Upgrade Pack Should Allow Source Information
Key: AMBARI-24687
URL: https://issues.apache.org/jira/browse/AMBARI-24687
Project: Ambari
Issue Type: Task
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 2.8.0
Allow Upgrade Packs to specify {{source}} information in addition to {{target}}
(for backward compatibility)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24686) Ambari 2.8 Stack Upgrades
Nate Cole created AMBARI-24686: -- Summary: Ambari 2.8 Stack Upgrades Key: AMBARI-24686 URL: https://issues.apache.org/jira/browse/AMBARI-24686 Project: Ambari Issue Type: Epic Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24659) Provide common built-in upgrade actions
Nate Cole created AMBARI-24659: -- Summary: Provide common built-in upgrade actions Key: AMBARI-24659 URL: https://issues.apache.org/jira/browse/AMBARI-24659 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 Create a built-in upgrade pack that provides certain operations across all upgrades. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24608) Package install should handle multiple deployed mpacks
[ https://issues.apache.org/jira/browse/AMBARI-24608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-24608. Resolution: Fixed > Package install should handle multiple deployed mpacks > -- > > Key: AMBARI-24608 > URL: https://issues.apache.org/jira/browse/AMBARI-24608 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Installation of packages should cross mpacks. This changes from previous due > to installation out of several repo sets. Previous ambari was one single repo > set per install. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24608) Package install should handle multiple deployed mpacks
Nate Cole created AMBARI-24608: -- Summary: Package install should handle multiple deployed mpacks Key: AMBARI-24608 URL: https://issues.apache.org/jira/browse/AMBARI-24608 Project: Ambari Issue Type: Task Components: ambari-admin Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 Installation of packages should cross mpacks. This changes from previous due to installation out of several repo sets. Previous ambari was one single repo set per install. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24481) Orchestration: Remove singular upgrade pack from UpgradeContext; resolve ServiceGroup names
[ https://issues.apache.org/jira/browse/AMBARI-24481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-24481. Resolution: Fixed > Orchestration: Remove singular upgrade pack from UpgradeContext; resolve > ServiceGroup names > --- > > Key: AMBARI-24481 > URL: https://issues.apache.org/jira/browse/AMBARI-24481 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > This JIRA addresses the following issues in orchestration: > * Remove service group name stub. > * Remove UpgradeContext upgrade pack since each service group may have its > own upgrade pack. > * Allow subsequent calls to attempt to create an upgrade -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24481) Orchestration: Remove singular upgrade pack from UpgradeContext; resolve ServiceGroup names
Nate Cole created AMBARI-24481: -- Summary: Orchestration: Remove singular upgrade pack from UpgradeContext; resolve ServiceGroup names Key: AMBARI-24481 URL: https://issues.apache.org/jira/browse/AMBARI-24481 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 This JIRA addresses the following issues in orchestration: * Remove service group name stub. * Remove UpgradeContext upgrade pack since each service group may have its own upgrade pack. * Allow subsequent calls to attempt to create an upgrade -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24430) Orchestration: Display Names are not being resolved
[
https://issues.apache.org/jira/browse/AMBARI-24430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-24430.
Resolution: Fixed
> Orchestration: Display Names are not being resolved
> ---
>
> Key: AMBARI-24430
> URL: https://issues.apache.org/jira/browse/AMBARI-24430
> Project: Ambari
> Issue Type: Task
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This is a result of new methods that passed in {{null}} in order to compile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24430) Orchestration: Display Names are not being resolved
Nate Cole created AMBARI-24430:
--
Summary: Orchestration: Display Names are not being resolved
Key: AMBARI-24430
URL: https://issues.apache.org/jira/browse/AMBARI-24430
Project: Ambari
Issue Type: Task
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 3.0.0
This is a result of new methods that passed in {{null}} in order to compile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24258) Completely Remove Upgrade Pack Target Information
Nate Cole created AMBARI-24258: -- Summary: Completely Remove Upgrade Pack Target Information Key: AMBARI-24258 URL: https://issues.apache.org/jira/browse/AMBARI-24258 Project: Ambari Issue Type: Task Affects Versions: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 Completely Remove Upgrade Pack Target Information. This eventually will be replace with source information for lookup by Upgrade Plans -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24197) Change Orchestrator for Lifecycle groupings
[ https://issues.apache.org/jira/browse/AMBARI-24197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-24197. Resolution: Fixed > Change Orchestrator for Lifecycle groupings > --- > > Key: AMBARI-24197 > URL: https://issues.apache.org/jira/browse/AMBARI-24197 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Change code to add lifecycles when orchestrating. This is the just the first > step of changes required to support this mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24197) Change Orchestrator for Lifecycle groupings
Nate Cole created AMBARI-24197: -- Summary: Change Orchestrator for Lifecycle groupings Key: AMBARI-24197 URL: https://issues.apache.org/jira/browse/AMBARI-24197 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 Change code to add lifecycles when orchestrating. This is the just the first step of changes required to support this mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24197) Change Orchestrator for Lifecycle groupings
[ https://issues.apache.org/jira/browse/AMBARI-24197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-24197: --- Issue Type: Task (was: Bug) > Change Orchestrator for Lifecycle groupings > --- > > Key: AMBARI-24197 > URL: https://issues.apache.org/jira/browse/AMBARI-24197 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > > Change code to add lifecycles when orchestrating. This is the just the first > step of changes required to support this mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24119) TaskWrapper should only wrap a single task
[
https://issues.apache.org/jira/browse/AMBARI-24119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-24119.
Resolution: Fixed
> TaskWrapper should only wrap a single task
> --
>
> Key: AMBARI-24119
> URL: https://issues.apache.org/jira/browse/AMBARI-24119
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{TaskWrapper}} should be holding one and only task - the hosts are the
> multiplicity of the wrapper, not the task.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24119) TaskWrapper should only wrap a single task
Nate Cole created AMBARI-24119:
--
Summary: TaskWrapper should only wrap a single task
Key: AMBARI-24119
URL: https://issues.apache.org/jira/browse/AMBARI-24119
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 3.0.0
{{TaskWrapper}} should be holding one and only task - the hosts are the
multiplicity of the wrapper, not the task.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24096) Add Upgrade Pack to Upgrade Plan
[ https://issues.apache.org/jira/browse/AMBARI-24096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-24096. Resolution: Fixed > Add Upgrade Pack to Upgrade Plan > > > Key: AMBARI-24096 > URL: https://issues.apache.org/jira/browse/AMBARI-24096 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Add the upgrade pack to the detail for an UpgradePlan. This value will be > used to test the API and will eventually be calculated when creating a plan > that doesn't include this value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24096) Add Upgrade Pack to Upgrade Plan
[ https://issues.apache.org/jira/browse/AMBARI-24096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-24096: --- Issue Type: Task (was: Bug) > Add Upgrade Pack to Upgrade Plan > > > Key: AMBARI-24096 > URL: https://issues.apache.org/jira/browse/AMBARI-24096 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > > Add the upgrade pack to the detail for an UpgradePlan. This value will be > used to test the API and will eventually be calculated when creating a plan > that doesn't include this value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24096) Add Upgrade Pack to Upgrade Plan
Nate Cole created AMBARI-24096: -- Summary: Add Upgrade Pack to Upgrade Plan Key: AMBARI-24096 URL: https://issues.apache.org/jira/browse/AMBARI-24096 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 Add the upgrade pack to the detail for an UpgradePlan. This value will be used to test the API and will eventually be calculated when creating a plan that doesn't include this value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24060) Sys-prepped Hosts do not Install and Finalize correctly
[ https://issues.apache.org/jira/browse/AMBARI-24060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-24060. Resolution: Fixed > Sys-prepped Hosts do not Install and Finalize correctly > --- > > Key: AMBARI-24060 > URL: https://issues.apache.org/jira/browse/AMBARI-24060 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > * Installation of packages using a host that is sys-prepped is choosing > package names in a non-deterministic way on ubuntu14/16 > * Finalization is failing when there are no packages installed on-system. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24060) Sys-prepped Hosts do not Install and Finalize correctly
Nate Cole created AMBARI-24060: -- Summary: Sys-prepped Hosts do not Install and Finalize correctly Key: AMBARI-24060 URL: https://issues.apache.org/jira/browse/AMBARI-24060 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.7.0 * Installation of packages using a host that is sys-prepped is choosing package names in a non-deterministic way on ubuntu14/16 * Finalization is failing when there are no packages installed on-system. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23989) Provide Patch or Maint Flag to Command JSON
[ https://issues.apache.org/jira/browse/AMBARI-23989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-23989. Resolution: Fixed > Provide Patch or Maint Flag to Command JSON > --- > > Key: AMBARI-23989 > URL: https://issues.apache.org/jira/browse/AMBARI-23989 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Provide information for either Upgrade or Downgrade that indicates when the > bits only are switched. This means some commands may be omitted if they > won't affect the state of the cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23989) Provide Patch or Maint Flag to Command JSON
[ https://issues.apache.org/jira/browse/AMBARI-23989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-23989: --- Summary: Provide Patch or Maint Flag to Command JSON (was: Provide Patch or Maint Flag to Agents) > Provide Patch or Maint Flag to Command JSON > --- > > Key: AMBARI-23989 > URL: https://issues.apache.org/jira/browse/AMBARI-23989 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.7.0 > > > Provide information for either Upgrade or Downgrade that indicates when the > bits only are switched. This means some commands may be omitted if they > won't affect the state of the cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23989) Provide Patch or Maint Flag to Agents
Nate Cole created AMBARI-23989: -- Summary: Provide Patch or Maint Flag to Agents Key: AMBARI-23989 URL: https://issues.apache.org/jira/browse/AMBARI-23989 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.7.0 Provide information for either Upgrade or Downgrade that indicates when the bits only are switched. This means some commands may be omitted if they won't affect the state of the cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23946) Stack upgrade from 2.6.5 to 3.0.0 fails because WebHCat component doesn't exist
[ https://issues.apache.org/jira/browse/AMBARI-23946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-23946. Resolution: Fixed > Stack upgrade from 2.6.5 to 3.0.0 fails because WebHCat component doesn't > exist > --- > > Key: AMBARI-23946 > URL: https://issues.apache.org/jira/browse/AMBARI-23946 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Target and Source stacks are not represented correctly during an express > upgrade -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23946) Stack upgrade from 2.6.5 to 3.0.0 fails because WebHCat component doesn't exist
Nate Cole created AMBARI-23946: -- Summary: Stack upgrade from 2.6.5 to 3.0.0 fails because WebHCat component doesn't exist Key: AMBARI-23946 URL: https://issues.apache.org/jira/browse/AMBARI-23946 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.7.0 Target and Source stacks are not represented correctly during an express upgrade -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23907) HDFS Prepare should not be called if there is no path to Downgrade
[ https://issues.apache.org/jira/browse/AMBARI-23907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-23907. Resolution: Fixed > HDFS Prepare should not be called if there is no path to Downgrade > -- > > Key: AMBARI-23907 > URL: https://issues.apache.org/jira/browse/AMBARI-23907 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Add a boolean check for whether a downgrade is allowed before calling prepare > during an EU -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23907) HDFS Prepare should not be called if there is no path to Downgrade
Nate Cole created AMBARI-23907: -- Summary: HDFS Prepare should not be called if there is no path to Downgrade Key: AMBARI-23907 URL: https://issues.apache.org/jira/browse/AMBARI-23907 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.7.0 Add a boolean check for whether a downgrade is allowed before calling prepare during an EU -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23726) Mpack Installation Response is not Updating State
[
https://issues.apache.org/jira/browse/AMBARI-23726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-23726.
Resolution: Fixed
> Mpack Installation Response is not Updating State
> -
>
> Key: AMBARI-23726
> URL: https://issues.apache.org/jira/browse/AMBARI-23726
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {{mpack_host_state}} is not being updated when the custom action is getting
> invoked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23726) Mpack Installation Response is not Updating State
Nate Cole created AMBARI-23726:
--
Summary: Mpack Installation Response is not Updating State
Key: AMBARI-23726
URL: https://issues.apache.org/jira/browse/AMBARI-23726
Project: Ambari
Issue Type: Task
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 3.0.0
{{mpack_host_state}} is not being updated when the custom action is getting
invoked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23697) Replace Cluster install_packages with an Upgrade Plan Installation
[ https://issues.apache.org/jira/browse/AMBARI-23697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-23697. Resolution: Fixed > Replace Cluster install_packages with an Upgrade Plan Installation > -- > > Key: AMBARI-23697 > URL: https://issues.apache.org/jira/browse/AMBARI-23697 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Add functionality to install an mpack for upgrade purposes. > Does not include tests. Add an annotation marker for this purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23697) Replace Cluster install_packages with an Upgrade Plan Installation
[ https://issues.apache.org/jira/browse/AMBARI-23697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-23697: --- Description: Add functionality to install an mpack for upgrade purposes. Does not include tests. Add an annotation marker for this purpose. was: Add functionality to install an mpack for upgrade purposes. Do not include tests. Add an annotation marker for this purpose. > Replace Cluster install_packages with an Upgrade Plan Installation > -- > > Key: AMBARI-23697 > URL: https://issues.apache.org/jira/browse/AMBARI-23697 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > > Add functionality to install an mpack for upgrade purposes. > Does not include tests. Add an annotation marker for this purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23697) Replace Cluster install_packages with an Upgrade Plan Installation
Nate Cole created AMBARI-23697: -- Summary: Replace Cluster install_packages with an Upgrade Plan Installation Key: AMBARI-23697 URL: https://issues.apache.org/jira/browse/AMBARI-23697 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 Add functionality to install an mpack for upgrade purposes. Do not include tests. Add an annotation marker for this purpose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23441) API Addition for Upgrade Plan for Config Changes
[ https://issues.apache.org/jira/browse/AMBARI-23441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole reassigned AMBARI-23441: -- Assignee: Nate Cole > API Addition for Upgrade Plan for Config Changes > > > Key: AMBARI-23441 > URL: https://issues.apache.org/jira/browse/AMBARI-23441 > Project: Ambari > Issue Type: Task >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > Add config changes per service group detail -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23441) API Addition for Upgrade Plan for Config Changes
[ https://issues.apache.org/jira/browse/AMBARI-23441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-23441. Resolution: Fixed > API Addition for Upgrade Plan for Config Changes > > > Key: AMBARI-23441 > URL: https://issues.apache.org/jira/browse/AMBARI-23441 > Project: Ambari > Issue Type: Task >Reporter: Nate Cole >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Add config changes per service group detail -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23441) API Addition for Upgrade Plan for Config Changes
Nate Cole created AMBARI-23441: -- Summary: API Addition for Upgrade Plan for Config Changes Key: AMBARI-23441 URL: https://issues.apache.org/jira/browse/AMBARI-23441 Project: Ambari Issue Type: Task Reporter: Nate Cole -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23318) API Addition for Upgrade Plan
[ https://issues.apache.org/jira/browse/AMBARI-23318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-23318: --- Summary: API Addition for Upgrade Plan (was: API Addition for Upgrade Plan for Config Changes) > API Addition for Upgrade Plan > - > > Key: AMBARI-23318 > URL: https://issues.apache.org/jira/browse/AMBARI-23318 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > > Add an endpoint to create upgrade plans. An upgrade plan holds all the > "configuration" settings for an upgrade, as well as the service groups and > target mpacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23441) API Addition for Upgrade Plan for Config Changes
[ https://issues.apache.org/jira/browse/AMBARI-23441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-23441: --- Description: Add config changes per service group detail > API Addition for Upgrade Plan for Config Changes > > > Key: AMBARI-23441 > URL: https://issues.apache.org/jira/browse/AMBARI-23441 > Project: Ambari > Issue Type: Task >Reporter: Nate Cole >Priority: Major > > Add config changes per service group detail -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23318) API Addition for Upgrade Plan for Config Changes
[ https://issues.apache.org/jira/browse/AMBARI-23318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-23318. Resolution: Fixed > API Addition for Upgrade Plan for Config Changes > > > Key: AMBARI-23318 > URL: https://issues.apache.org/jira/browse/AMBARI-23318 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > > Add an endpoint to create upgrade plans. An upgrade plan holds all the > "configuration" settings for an upgrade, as well as the service groups and > target mpacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23318) API Addition for Upgrade Plan for Config Changes
[ https://issues.apache.org/jira/browse/AMBARI-23318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-23318: --- Summary: API Addition for Upgrade Plan for Config Changes (was: API Addition for Upgrade Plan) > API Addition for Upgrade Plan for Config Changes > > > Key: AMBARI-23318 > URL: https://issues.apache.org/jira/browse/AMBARI-23318 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > > Add an endpoint to create upgrade plans. An upgrade plan holds all the > "configuration" settings for an upgrade, as well as the service groups and > target mpacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23329) Ambari: set "cloud storage" usage tracking properties for AWS, Azure object stores
[
https://issues.apache.org/jira/browse/AMBARI-23329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-23329.
Resolution: Fixed
> Ambari: set "cloud storage" usage tracking properties for AWS, Azure object
> stores
> --
>
> Key: AMBARI-23329
> URL: https://issues.apache.org/jira/browse/AMBARI-23329
> Project: Ambari
> Issue Type: Task
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Set the following properties for HDP stack:
> {noformat}
> fs.azure.user.agent.prefix
> fs.s3a.user.agent.prefix
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23329) Ambari: set "cloud storage" usage tracking properties for AWS, Azure object stores
Nate Cole created AMBARI-23329:
--
Summary: Ambari: set "cloud storage" usage tracking properties for
AWS, Azure object stores
Key: AMBARI-23329
URL: https://issues.apache.org/jira/browse/AMBARI-23329
Project: Ambari
Issue Type: Task
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 2.6.2
Set the following properties for HDP stack:
{noformat}
fs.azure.user.agent.prefix
fs.s3a.user.agent.prefix
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23318) API Addition for Upgrade Plan
Nate Cole created AMBARI-23318: -- Summary: API Addition for Upgrade Plan Key: AMBARI-23318 URL: https://issues.apache.org/jira/browse/AMBARI-23318 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 Add an endpoint to create upgrade plans. An upgrade plan holds all the "configuration" settings for an upgrade, as well as the service groups and target mpacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23317) Management Packs: Upgrade Orchestration
Nate Cole created AMBARI-23317: -- Summary: Management Packs: Upgrade Orchestration Key: AMBARI-23317 URL: https://issues.apache.org/jira/browse/AMBARI-23317 Project: Ambari Issue Type: Epic Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 This Epic covers work items need for changes to upgrade orchestration based on the mpack model. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23156) Remove Required Group Name and Expose Lifecycle to API
[ https://issues.apache.org/jira/browse/AMBARI-23156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-23156. Resolution: Fixed > Remove Required Group Name and Expose Lifecycle to API > -- > > Key: AMBARI-23156 > URL: https://issues.apache.org/jira/browse/AMBARI-23156 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The group name is no longer a required field. Expose lifecycle via API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23156) Remove Required Group Name and Expose Lifecycle to API
[ https://issues.apache.org/jira/browse/AMBARI-23156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-23156: --- Description: The group name is no longer a required field. Expose lifecycle via API > Remove Required Group Name and Expose Lifecycle to API > -- > > Key: AMBARI-23156 > URL: https://issues.apache.org/jira/browse/AMBARI-23156 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > > The group name is no longer a required field. Expose lifecycle via API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23156) Remove Required Group Name and Expose Lifecycle to API
[ https://issues.apache.org/jira/browse/AMBARI-23156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole reassigned AMBARI-23156: -- Assignee: Nate Cole > Remove Required Group Name and Expose Lifecycle to API > -- > > Key: AMBARI-23156 > URL: https://issues.apache.org/jira/browse/AMBARI-23156 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23156) Remove Required Group Name and Expose Lifecycle to API
Nate Cole created AMBARI-23156: -- Summary: Remove Required Group Name and Expose Lifecycle to API Key: AMBARI-23156 URL: https://issues.apache.org/jira/browse/AMBARI-23156 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23125) Move check-properties XML
[ https://issues.apache.org/jira/browse/AMBARI-23125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-23125. Resolution: Fixed > Move check-properties XML > - > > Key: AMBARI-23125 > URL: https://issues.apache.org/jira/browse/AMBARI-23125 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Major > Fix For: 3.0.0 > > > This jira further refines the upgrade packs for prechecks and removes > intermediate-stacks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23125) Move check-properties XML
Nate Cole created AMBARI-23125: -- Summary: Move check-properties XML Key: AMBARI-23125 URL: https://issues.apache.org/jira/browse/AMBARI-23125 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 This jira further refines the upgrade packs for prechecks and removes intermediate-stacks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23053) Rename NON-ROLLING to EXPRESS
[ https://issues.apache.org/jira/browse/AMBARI-23053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-23053. Resolution: Fixed > Rename NON-ROLLING to EXPRESS > - > > Key: AMBARI-23053 > URL: https://issues.apache.org/jira/browse/AMBARI-23053 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The term "non-rolling" was coined before we used "Express". The enum should > be called EXPRESS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23053) Rename NON-ROLLING to EXPRESS
Nate Cole created AMBARI-23053: -- Summary: Rename NON-ROLLING to EXPRESS Key: AMBARI-23053 URL: https://issues.apache.org/jira/browse/AMBARI-23053 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 The term "non-rolling" was coined before we used "Express". The enum should be called EXPRESS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23036) Create Lifecycle changes for Upgrade Packs
[
https://issues.apache.org/jira/browse/AMBARI-23036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-23036.
Resolution: Fixed
> Create Lifecycle changes for Upgrade Packs
> --
>
> Key: AMBARI-23036
> URL: https://issues.apache.org/jira/browse/AMBARI-23036
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In Upgrade Packs, abstract the {{}} element further and wrap them with
> a {{}} element.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23036) Create Lifecycle changes for Upgrade Packs
Nate Cole created AMBARI-23036:
--
Summary: Create Lifecycle changes for Upgrade Packs
Key: AMBARI-23036
URL: https://issues.apache.org/jira/browse/AMBARI-23036
Project: Ambari
Issue Type: Task
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 3.0.0
In Upgrade Packs, abstract the {{}} element further and wrap them with a
{{}} element.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22995) Remove deprecated Upgrade Packs
[ https://issues.apache.org/jira/browse/AMBARI-22995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-22995. Resolution: Fixed > Remove deprecated Upgrade Packs > --- > > Key: AMBARI-22995 > URL: https://issues.apache.org/jira/browse/AMBARI-22995 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h > Remaining Estimate: 0h > > The old upgrade packs and test should be removed to make way for the new > format that supports lifecycles. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22995) Remove deprecated Upgrade Packs
Nate Cole created AMBARI-22995: -- Summary: Remove deprecated Upgrade Packs Key: AMBARI-22995 URL: https://issues.apache.org/jira/browse/AMBARI-22995 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 The old upgrade packs and test should be removed to make way for the new format that supports lifecycles. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22994) Management Packs: Upgrade Pack Changes
Nate Cole created AMBARI-22994: -- Summary: Management Packs: Upgrade Pack Changes Key: AMBARI-22994 URL: https://issues.apache.org/jira/browse/AMBARI-22994 Project: Ambari Issue Type: Epic Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 This epic is used to track all the work necessary to change Upgrade Packs to work with the architecture changes for Management Packs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22938) Ambari server start fails with fresh Ambari installation
[
https://issues.apache.org/jira/browse/AMBARI-22938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357402#comment-16357402
]
Nate Cole commented on AMBARI-22938:
I had this exact problem when I didn't have the mpacks-v2 property set in
ambari.properties. We're somehow ignoring that but the Guice exception is
getting thrown.
We should either propogate the exception or give a better message (or both).
> Ambari server start fails with fresh Ambari installation
>
>
> Key: AMBARI-22938
> URL: https://issues.apache.org/jira/browse/AMBARI-22938
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
>
> On branch *branch-feature-AMBARI-14714*, after installation, Ambari server
> starts fails as following :
> {code:title=/var/log/ambari-server/ambari-server.out}
> An unexpected error occured during starting Ambari Server.
> Exception in thread "main"
> com.google.inject.internal.util.$ComputationException:
> java.lang.ArrayIndexOutOfBoundsException: 7786
> at
> com.google.inject.internal.util.$MapMaker$StrategyImpl.compute(MapMaker.java:553)
> at
> com.google.inject.internal.util.$MapMaker$StrategyImpl.compute(MapMaker.java:419)
> at
> com.google.inject.internal.util.$CustomConcurrentHashMap$ComputingImpl.get(CustomConcurrentHashMap.java:2041)
> at
> com.google.inject.internal.util.$StackTraceElements.forMember(StackTraceElements.java:53)
> at com.google.inject.internal.Errors.formatSource(Errors.java:690)
> at com.google.inject.internal.Errors.formatInjectionPoint(Errors.java:720)
> at com.google.inject.internal.Errors.formatSource(Errors.java:684)
> at com.google.inject.internal.Errors.format(Errors.java:555)
> at
> com.google.inject.ProvisionException.getMessage(ProvisionException.java:59)
> at java.lang.Throwable.getLocalizedMessage(Throwable.java:391)
> at java.lang.Throwable.toString(Throwable.java:480)
> at java.lang.String.valueOf(String.java:2994)
> at java.io.PrintStream.println(PrintStream.java:821)
> at java.lang.Throwable$WrappedPrintStream.println(Throwable.java:748)
> at java.lang.Throwable.printStackTrace(Throwable.java:655)
> at java.lang.Throwable.printStackTrace(Throwable.java:643)
> at java.lang.Throwable.printStackTrace(Throwable.java:634)
> at
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1118)
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 7786
> at com.google.inject.internal.asm.$ClassReader.readClass(Unknown Source)
> at com.google.inject.internal.asm.$ClassReader.accept(Unknown Source)
> at com.google.inject.internal.asm.$ClassReader.accept(Unknown Source)
> at com.google.inject.internal.util.$LineNumbers.(LineNumbers.java:62)
> at
> com.google.inject.internal.util.$StackTraceElements$1.apply(StackTraceElements.java:36)
> at
> com.google.inject.internal.util.$StackTraceElements$1.apply(StackTraceElements.java:33)
> at
> com.google.inject.internal.util.$MapMaker$StrategyImpl.compute(MapMaker.java:549)
> ... 17 more
> {code}
>
>
> Stack trace while debugging gives the following:
>
> {code:java}
> Error preallocating sequence numbers. The sequence table information is not
> complete.
> {code}
> CC [~jluniya] | [~mradhakrishnan]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22936) Remove Code for ExperiementalFeature.PARALLEL_PROCESSING
[ https://issues.apache.org/jira/browse/AMBARI-22936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-22936. Resolution: Fixed > Remove Code for ExperiementalFeature.PARALLEL_PROCESSING > > > Key: AMBARI-22936 > URL: https://issues.apache.org/jira/browse/AMBARI-22936 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22936) Remove Code for ExperiementalFeature.PARALLEL_PROCESSING
Nate Cole created AMBARI-22936: -- Summary: Remove Code for ExperiementalFeature.PARALLEL_PROCESSING Key: AMBARI-22936 URL: https://issues.apache.org/jira/browse/AMBARI-22936 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22773) Ambari repository version is set to 2.6.3.0-235 irrespective of HDP version installed on cluster
[ https://issues.apache.org/jira/browse/AMBARI-22773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334287#comment-16334287 ] Nate Cole commented on AMBARI-22773: You would have to check the View code. That is contributed separately from Ambari proper. > Ambari repository version is set to 2.6.3.0-235 irrespective of HDP version > installed on cluster > > > Key: AMBARI-22773 > URL: https://issues.apache.org/jira/browse/AMBARI-22773 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Sonia Garudi >Priority: Major > Attachments: screenshot1.JPG, screenshot2.JPG > > > I have installed HDP-2.6.2.0 on my cluster. In the admin view, the version > installed on the cluster is shown as 2.6.3.0-235.(Attached screenshot1.jpg) > The version is same irrespective of which version is actually installed on > the cluster at step1(installer flow). > However, while registering a new version through the admin view, the version > is set to appropriate value.(Attached screenshot2.jpg) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22694) For mixed OS deploy, some pig tests failed with MR job failing with 'IOException: Unable to get CompressorType for codec (org.apache.hadoop.io.compress.SnappyCodec)'
[ https://issues.apache.org/jira/browse/AMBARI-22694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-22694. Resolution: Fixed > For mixed OS deploy, some pig tests failed with MR job failing with > 'IOException: Unable to get CompressorType for codec > (org.apache.hadoop.io.compress.SnappyCodec)' > - > > Key: AMBARI-22694 > URL: https://issues.apache.org/jira/browse/AMBARI-22694 > Project: Ambari > Issue Type: Bug >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22694) For mixed OS deploy, some pig tests failed with MR job failing with 'IOException: Unable to get CompressorType for codec (org.apache.hadoop.io.compress.SnappyCodec)'
Nate Cole created AMBARI-22694: -- Summary: For mixed OS deploy, some pig tests failed with MR job failing with 'IOException: Unable to get CompressorType for codec (org.apache.hadoop.io.compress.SnappyCodec)' Key: AMBARI-22694 URL: https://issues.apache.org/jira/browse/AMBARI-22694 Project: Ambari Issue Type: Bug Reporter: Nate Cole Assignee: Nate Cole Priority: Critical Fix For: 2.6.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22676) [Patch Hive]webhcat: test_sqoop fails with hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist
[ https://issues.apache.org/jira/browse/AMBARI-22676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-22676: --- Resolution: Fixed Status: Resolved (was: Patch Available) > [Patch Hive]webhcat: test_sqoop fails with > hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist > --- > > Key: AMBARI-22676 > URL: https://issues.apache.org/jira/browse/AMBARI-22676 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.2 > > Attachments: AMBARI-22676.patch > > > Tie HIVE and SQOOP for upgrades in order to make sure the sqoop tarball gets > uploaded on the new version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22676) [Patch Hive]webhcat: test_sqoop fails with hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist
[ https://issues.apache.org/jira/browse/AMBARI-22676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-22676: --- Status: Patch Available (was: Open) > [Patch Hive]webhcat: test_sqoop fails with > hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist > --- > > Key: AMBARI-22676 > URL: https://issues.apache.org/jira/browse/AMBARI-22676 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.2 > > Attachments: AMBARI-22676.patch > > > Tie HIVE and SQOOP for upgrades in order to make sure the sqoop tarball gets > uploaded on the new version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22676) [Patch Hive]webhcat: test_sqoop fails with hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist
[ https://issues.apache.org/jira/browse/AMBARI-22676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-22676: --- Attachment: AMBARI-22676.patch > [Patch Hive]webhcat: test_sqoop fails with > hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist > --- > > Key: AMBARI-22676 > URL: https://issues.apache.org/jira/browse/AMBARI-22676 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.2 > > Attachments: AMBARI-22676.patch > > > Tie HIVE and SQOOP for upgrades in order to make sure the sqoop tarball gets > uploaded on the new version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22676) [Patch Hive]webhcat: test_sqoop fails with hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist
Nate Cole created AMBARI-22676: -- Summary: [Patch Hive]webhcat: test_sqoop fails with hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist Key: AMBARI-22676 URL: https://issues.apache.org/jira/browse/AMBARI-22676 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Priority: Critical Fix For: 2.6.2 Tie HIVE and SQOOP for upgrades in order to make sure the sqoop tarball gets uploaded on the new version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22665) Livy2 Does Not Start On HDP 2.6.0 to 2.6.3
[
https://issues.apache.org/jira/browse/AMBARI-22665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295343#comment-16295343
]
Nate Cole commented on AMBARI-22665:
+1 on patch
> Livy2 Does Not Start On HDP 2.6.0 to 2.6.3
> --
>
> Key: AMBARI-22665
> URL: https://issues.apache.org/jira/browse/AMBARI-22665
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22665.patch
>
>
> Livy2 was added as a component in HDP 2.6, starting with HDP 2.6.0.0.
> However, there was no stack-select or conf-select support for some reason.
> stack-select and conf-select was built into HDP 2.6.4.0.
> Ambari added {{livy2}} as a known conf-select to the HDP 2.6 stack. On
> deployments of HDP 2.6.4+, this is correct and the server can properly start.
> However, when using Ambari to deploy Livy2 on HDP 2.6.0 - 2.6.3, we see the
> following:
> {code}
> 2017-12-18 14:53:52,711 - Checking to see which directories will be created
> for livy2 on version 2.6.0.0-334
> 2017-12-18 14:53:52,711 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'dry-run-create', '--package', 'livy2', '--stack-version', '2.6.0.0-334',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-12-18 14:53:52,734 - call returned (1, 'livy2 not installed or incorrect
> package name', '')
> 2017-12-18 14:53:52,735 - Creating /etc/livy2/2.6.0.0-334/0 if it does not
> exist
> 2017-12-18 14:53:52,736 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'livy2', '--stack-version', '2.6.0.0-334',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-12-18 14:53:52,765 - call returned (1, 'livy2 not installed or incorrect
> package name', '')
> 2017-12-18 14:53:52,766 - checked_call[('ambari-python-wrap',
> '/usr/bin/conf-select', 'set-conf-dir', '--package', 'livy2',
> '--stack-version', '2.6.0.0-334', '--conf-version', '0')] {'logoutput':
> False, 'sudo': True, 'quiet': False}
> 2017-12-18 14:53:52,795 - Could not select the directory for package livy2.
> Error: Execution of 'ambari-python-wrap /usr/bin/conf-select set-conf-dir
> --package livy2 --stack-version 2.6.0.0-334 --conf-version 0' returned 1.
> livy2 not installed or incorrect package name
> 2017-12-18 14:53:52,796 - /etc/livy2/conf is a directory - it must be
> converted into a symlink
> {code}
> Essentially, Ambari is trying to setup the configuration pointers, but it is
> ignoring the dry-run result code. At the end of the day, we end up with Livy2
> not starting b/c we're manipulated the configuration pointers, but
> {{conf-select}} failed to properly create a versioned configuration directory.
> The solution is to check the dry-run result code and do nothing if
> conf-select doesn't support the package.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-18683) Argument for manually setting CURRENT is unclear
[
https://issues.apache.org/jira/browse/AMBARI-18683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-18683.
Resolution: Won't Do
> Argument for manually setting CURRENT is unclear
>
>
> Key: AMBARI-18683
> URL: https://issues.apache.org/jira/browse/AMBARI-18683
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
> Fix For: 3.0.0
>
>
> It is currently possible to set the CURRENT {{repo_version}} for a component.
> The API is a little misleading. The call below should also check for the
> version string, not just the display name. Could also check for the id itself
> too.
> {noformat}
> PUT /api/v1/clusters/c1/stack_versions
> {
> "ClusterStackVersions": {
> "force": true,
> "state": "CURRENT",
> "repository_version": "HDP-2.5.1.0"<--- must be display name
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22587) Storm service check failed during PU due to CNF StormAtlasHook
[
https://issues.apache.org/jira/browse/AMBARI-22587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-22587:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Storm service check failed during PU due to CNF StormAtlasHook
> --
>
> Key: AMBARI-22587
> URL: https://issues.apache.org/jira/browse/AMBARI-22587
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Attachments: AMBARI-22587.patch
>
>
> RCA:
> * Installation of {{storm_\{version\}}} packages triggers the install of
> {{atlas-metadata_\{version\}-storm-plugin}} package.
> * When upgrading including ATLAS but not STORM, the atlas bits are put down
> just fine, but {{/usr/hdp/\{new_version\}/atlas/hook/storm}} doesn't exist.
> * Symlinks of {{storm/extlib}} to {{atlas/hook/storm}} become broken because
> the hooks aren't there.
> We should be requiring a patch of ATLAS to also require STORM be patched as
> well in order to get the plugins installed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22587) Storm service check failed during PU due to CNF StormAtlasHook
[
https://issues.apache.org/jira/browse/AMBARI-22587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-22587:
---
Status: Patch Available (was: Open)
> Storm service check failed during PU due to CNF StormAtlasHook
> --
>
> Key: AMBARI-22587
> URL: https://issues.apache.org/jira/browse/AMBARI-22587
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Attachments: AMBARI-22587.patch
>
>
> RCA:
> * Installation of {{storm_\{version\}}} packages triggers the install of
> {{atlas-metadata_\{version\}-storm-plugin}} package.
> * When upgrading including ATLAS but not STORM, the atlas bits are put down
> just fine, but {{/usr/hdp/\{new_version\}/atlas/hook/storm}} doesn't exist.
> * Symlinks of {{storm/extlib}} to {{atlas/hook/storm}} become broken because
> the hooks aren't there.
> We should be requiring a patch of ATLAS to also require STORM be patched as
> well in order to get the plugins installed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22587) Storm service check failed during PU due to CNF StormAtlasHook
[
https://issues.apache.org/jira/browse/AMBARI-22587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-22587:
---
Attachment: AMBARI-22587.patch
> Storm service check failed during PU due to CNF StormAtlasHook
> --
>
> Key: AMBARI-22587
> URL: https://issues.apache.org/jira/browse/AMBARI-22587
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Attachments: AMBARI-22587.patch
>
>
> RCA:
> * Installation of {{storm_\{version\}}} packages triggers the install of
> {{atlas-metadata_\{version\}-storm-plugin}} package.
> * When upgrading including ATLAS but not STORM, the atlas bits are put down
> just fine, but {{/usr/hdp/\{new_version\}/atlas/hook/storm}} doesn't exist.
> * Symlinks of {{storm/extlib}} to {{atlas/hook/storm}} become broken because
> the hooks aren't there.
> We should be requiring a patch of ATLAS to also require STORM be patched as
> well in order to get the plugins installed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22587) Storm service check failed during PU due to CNF StormAtlasHook
Nate Cole created AMBARI-22587:
--
Summary: Storm service check failed during PU due to CNF
StormAtlasHook
Key: AMBARI-22587
URL: https://issues.apache.org/jira/browse/AMBARI-22587
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Priority: Critical
RCA:
* Installation of {{storm_\{version\}}} packages triggers the install of
{{atlas-metadata_\{version\}-storm-plugin}} package.
* When upgrading including ATLAS but not STORM, the atlas bits are put down
just fine, but {{/usr/hdp/\{new_version\}/atlas/hook/storm}} doesn't exist.
* Symlinks of {{storm/extlib}} to {{atlas/hook/storm}} become broken because
the hooks aren't there.
We should be requiring a patch of ATLAS to also require STORM be patched as
well in order to get the plugins installed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22573) Stack deploy fails because repo file is unable to be parsed
[ https://issues.apache.org/jira/browse/AMBARI-22573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-22573: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Stack deploy fails because repo file is unable to be parsed > --- > > Key: AMBARI-22573 > URL: https://issues.apache.org/jira/browse/AMBARI-22573 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22573.patch > > > Missing tag in a metainfo.xml file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22573) Stack deploy fails because repo file is unable to be parsed
[ https://issues.apache.org/jira/browse/AMBARI-22573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-22573: --- Status: Patch Available (was: Open) > Stack deploy fails because repo file is unable to be parsed > --- > > Key: AMBARI-22573 > URL: https://issues.apache.org/jira/browse/AMBARI-22573 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22573.patch > > > Missing tag in a metainfo.xml file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22573) Stack deploy fails because repo file is unable to be parsed
[ https://issues.apache.org/jira/browse/AMBARI-22573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-22573: --- Attachment: AMBARI-22573.patch > Stack deploy fails because repo file is unable to be parsed > --- > > Key: AMBARI-22573 > URL: https://issues.apache.org/jira/browse/AMBARI-22573 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22573.patch > > > Missing tag in a metainfo.xml file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22573) Stack deploy fails because repo file is unable to be parsed
Nate Cole created AMBARI-22573: -- Summary: Stack deploy fails because repo file is unable to be parsed Key: AMBARI-22573 URL: https://issues.apache.org/jira/browse/AMBARI-22573 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Priority: Critical Fix For: 2.6.1 Missing tag in a metainfo.xml file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22546) LZO Upgrade pre-check is missing from BigInsights Upgrade packs
[ https://issues.apache.org/jira/browse/AMBARI-22546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271179#comment-16271179 ] Nate Cole commented on AMBARI-22546: Could not merge because changed files don't exist on trunk. > LZO Upgrade pre-check is missing from BigInsights Upgrade packs > --- > > Key: AMBARI-22546 > URL: https://issues.apache.org/jira/browse/AMBARI-22546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Attachments: AMBARI-22546.patch > > > Add the LZO check to the BI upgrade packs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22546) LZO Upgrade pre-check is missing from BigInsights Upgrade packs
[ https://issues.apache.org/jira/browse/AMBARI-22546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-22546: --- Resolution: Fixed Status: Resolved (was: Patch Available) > LZO Upgrade pre-check is missing from BigInsights Upgrade packs > --- > > Key: AMBARI-22546 > URL: https://issues.apache.org/jira/browse/AMBARI-22546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Attachments: AMBARI-22546.patch > > > Add the LZO check to the BI upgrade packs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22546) LZO Upgrade pre-check is missing from BigInsights Upgrade packs
[ https://issues.apache.org/jira/browse/AMBARI-22546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-22546: --- Status: Patch Available (was: Open) > LZO Upgrade pre-check is missing from BigInsights Upgrade packs > --- > > Key: AMBARI-22546 > URL: https://issues.apache.org/jira/browse/AMBARI-22546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Attachments: AMBARI-22546.patch > > > Add the LZO check to the BI upgrade packs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22546) LZO Upgrade pre-check is missing from BigInsights Upgrade packs
[ https://issues.apache.org/jira/browse/AMBARI-22546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-22546: --- Attachment: AMBARI-22546.patch > LZO Upgrade pre-check is missing from BigInsights Upgrade packs > --- > > Key: AMBARI-22546 > URL: https://issues.apache.org/jira/browse/AMBARI-22546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Attachments: AMBARI-22546.patch > > > Add the LZO check to the BI upgrade packs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22546) LZO Upgrade pre-check is missing from BigInsights Upgrade packs
Nate Cole created AMBARI-22546: -- Summary: LZO Upgrade pre-check is missing from BigInsights Upgrade packs Key: AMBARI-22546 URL: https://issues.apache.org/jira/browse/AMBARI-22546 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Priority: Critical Add the LZO check to the BI upgrade packs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22461) VDF defined HDP-GPL repo should be tagged appropriately
[ https://issues.apache.org/jira/browse/AMBARI-22461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-22461. Resolution: Fixed > VDF defined HDP-GPL repo should be tagged appropriately > --- > > Key: AMBARI-22461 > URL: https://issues.apache.org/jira/browse/AMBARI-22461 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Blocker > Fix For: 2.6.1 > > > Add XML elements to allow setting tags on a repository. The set of tags > should be strictly defined. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
