Details
-
Epic
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
-
None
-
Ambari: Patch Upgrades
Description
Documentation and updates to follow
Attachments
Attachments
Issue Links
- is depended upon by
-
AMBARI-14714 [Umbrella] Multi Everything Architecture
- Open
- relates to
-
AMBARI-18634 Support Offline Stack Upgrades In a Cluster
- Resolved
-
AMBARI-18678 Support Multiple Component Versions
- Resolved
- links to
Issues in epic
|
AMBARI-13326 | Service and Component info for repo_versions | Resolved | Nate Cole | ||
|
AMBARI-13423 | Distributing patch repo bits should target specific hosts | Resolved | Nate Cole | ||
|
AMBARI-14650 | Add persistence for Repo Version file | Resolved | Nate Cole | ||
|
AMBARI-14743 | Update package installation for version definition file | Resolved | Nate Cole | ||
|
AMBARI-14867 | Use entities for parent/child repository versions | Resolved | Nate Cole | ||
|
AMBARI-14924 | Create patch upgrade orchestration based on available services | Resolved | Nate Cole | ||
|
AMBARI-14972 | Add PK to servicecomponentdesiredstate Table To Support FK Relationships | Resolved | Jonathan Hurley | ||
|
AMBARI-14978 | Create Upgrade Packs for Patch Upgrades | Resolved | Nate Cole | ||
|
AMBARI-15058 | Schema changes for component history | Resolved | Jonathan Hurley | ||
|
AMBARI-15094 | Patch Upgrade UpgradeCatalog Changes | Resolved | Jonathan Hurley | ||
|
AMBARI-15097 | Remove targeted orchestration for patches | Resolved | Nate Cole | ||
|
AMBARI-15131 | Create Component/Service Upgrade History On Finalize | Resolved | Jonathan Hurley | ||
|
AMBARI-18391 | Prerequisite checks should only check services that are getting upgraded | Resolved | Nate Cole | ||
|
AMBARI-18432 | Re-enable orchestration to use VDF | Resolved | Nate Cole | ||
|
AMBARI-18473 | Scope and Services need to be used for orchestration | Resolved | Nate Cole | ||
|
AMBARI-18557 | Create Component to Repo Version associations | Resolved | Nate Cole | ||
|
AMBARI-19381 | Heartbeat version transitions must update Component alongside Cluster | Resolved | Nate Cole | ||
|
AMBARI-20774 | Service Upgrade VDF Creates Host Version Entries For All Hosts With INSTALLING | Resolved | Jonathan Hurley | ||
|
AMBARI-20894 | Setting Desired Stack Ids to Correct Values During Service and Patch Upgrades | Resolved | Jonathan Hurley | ||
|
AMBARI-20923 | Repositories must be resolved correctly when installing new components | Resolved | Nate Cole | ||
|
AMBARI-20940 | Propagate Component versions and states to Service | Resolved | Jonathan Hurley | ||
|
AMBARI-20957 | Remove cluster_version use | Resolved | Nate Cole | ||
|
AMBARI-20958 | Host Version on Finalization Must Be Scoped Correctly Based on Upgrade Type | Resolved | Jonathan Hurley | ||
|
AMBARI-20971 | Repository Resource Providers Should Expose the Repository ID by Default on Minimal Responses | Resolved | Jonathan Hurley | ||
|
AMBARI-20991 | Cluster Repository State Is Not Calculated Correctly For Service/Patch Repos | Resolved | Jonathan Hurley | ||
|
AMBARI-20996 | Fallback Cluster Current Version Is Blank Which Causes Upgrade Errors | Resolved | Jonathan Hurley | ||
|
AMBARI-21022 | Upgrades Should Be Associated With Repositories Instead of String Versions | Resolved | Jonathan Hurley | ||
|
AMBARI-21047 | Iterative Fixes For Patch/Service Upgrade Development | Resolved | Jonathan Hurley | ||
|
AMBARI-21078 | Merging Configurations On Service/Patch Upgrades Should Create New Configurations Only For Included Services | Resolved | Jonathan Hurley | ||
|
AMBARI-21114 | Fix Unit Test Failures From Prior Patch/Service Upgrade Commits | Resolved | Jonathan Hurley | ||
|
AMBARI-21149 | Configurations Created During Upgrade Must Use Correct StackId Based on Service | Resolved | Jonathan Hurley | ||
|
AMBARI-21162 | Enabling Kerberos should use cluster stack id | Resolved | Nate Cole | ||
|
AMBARI-21169 | Service and Patch Upgrade Catalog Changes for 2.6.0 | Resolved | Dmitry Lysnichenko | ||
|
AMBARI-21175 | Host Versions Remain on CURRENT During STANDARD (Full) Upgrades | Resolved | Jonathan Hurley | ||
|
AMBARI-21179 | Remove RepositoryVersionState of INIT | Resolved | Jonathan Hurley | ||
|
AMBARI-21180 | Component command changes must include version numbers for all services | Resolved | Nate Cole | ||
|
AMBARI-21188 | Configuration Symlink Is Incorrect After Stack Distribution | Resolved | Jonathan Hurley | ||
|
AMBARI-21241 | Support revert for patch upgrades | Resolved | Nate Cole | ||
|
AMBARI-21289 | Service creation requires a repository id, not a string version | Resolved | Nate Cole | ||
|
AMBARI-21580 | Replace Hard Coded stack-select Structures | Resolved | Jonathan Hurley | ||
|
AMBARI-21581 | Replace Hard Coded conf-select Structures | Resolved | Jonathan Hurley | ||
|
AMBARI-21626 | Configs For Target Stack Are Not Created During Upgrade | Resolved | Jonathan Hurley | ||
|
AMBARI-21639 | When Adding a New Service the Repository ID is Required | Resolved | Nate Cole | ||
|
AMBARI-21643 | Annotate upgrade packs for scope | Resolved | Jonathan Hurley | ||
|
AMBARI-21653 | Create VDF and xsd to support MAINT upgrades | Resolved | Nate Cole | ||
|
AMBARI-21656 | Patch/Service Downgrades Are Not Correctly Scoped | Resolved | Jonathan Hurley | ||
|
AMBARI-21671 | Expose via API whether a service will participate in an upgrade | Resolved | Nate Cole | ||
|
AMBARI-21672 | Update Orchestration to support MAINT | Resolved | Jonathan Hurley | ||
|
AMBARI-21677 | Upgrade Pre-Checks Should Take PATCH/SERVICE Types Into Account | Resolved | Jonathan Hurley | ||
|
AMBARI-21679 | Service Checks Will Run Multiple Times In Patch/Service Upgrades | Resolved | Nate Cole | ||
|
AMBARI-21683 | Service and Patch Upgrade Catalog Changes for 3.0 | Resolved | Jonathan Hurley | ||
|
AMBARI-21693 | Can't register multiple PATCH versions | Resolved | Nate Cole | ||
|
AMBARI-21719 | Result of install_packages uses version string instead of repo_version_id | Resolved | Nate Cole | ||
|
AMBARI-21722 | Begin Using Service Versions In Python stack_feature Code | Resolved | Jonathan Hurley | ||
|
AMBARI-21734 | Upgrade Associated Repository is Wrong for Downgrades and Patches | Resolved | Jonathan Hurley | ||
|
AMBARI-21758 | Prevent New Clusters from Being Provisioned With PATCH/MAINT Repos | Resolved | Jonathan Hurley | ||
|
AMBARI-21766 | When Matching New VDFs for Parent Repos only Consider STANDARD Types | Resolved | Jonathan Hurley | ||
|
AMBARI-21801 | No Hosts are Targeted For MAINT VDF If Available Services is Empty | Resolved | Jonathan Hurley | ||
|
AMBARI-21806 | Repository Entities Which Can't Be Removed Should Be Hide-able | Resolved | Jonathan Hurley | ||
|
AMBARI-21828 | Backend should sort repo_version by version string | Resolved | Nate Cole | ||
|
AMBARI-21842 | PATCH and MAINT Orchestrations Should Only Invoke stack-select On Specific Packages | Resolved | Jonathan Hurley | ||
|
AMBARI-21853 | Packages Already Installed Cause Problems When Scoping By New Repo ID Schema | Resolved | Jonathan Hurley | ||
|
AMBARI-21854 | Adapt Repository Files For Existing Deployments | Resolved | Dmytro Grinenko | ||
|
AMBARI-21931 | Use Correct Packages For Clients Where Stack Tools Support It | Resolved | Jonathan Hurley | ||
|
AMBARI-22083 | Wrong Hadoop Home Directory Is Being Picked Up on MAINT/PATCH Upgraded Clusters | Resolved | Jonathan Hurley |
AMBARI-12556
Ambari: Patch Upgrades
false
AMBARI-12556
Ambari: Patch Upgrades