[docs] Document procedure on keeping master node up-to-date
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Svetlana Karslioglu |
Bug Description
Whenever a user installs (or upgrades to) 6.1 GA his installation may contain not all the latest bugfixes and updates as there could be new patches delivered as part of update bundle which is released on regular basis by MOS and Fuel teams.
This means that if user wants to install latest environments wit
This also means that if user wants to install new environments or do manipulations with existing ones (starting with 6.1 versions) he needs to keep master node state synchronized with nodes of the environments, e.g environment being manipulated should have the same set of repos configured as master node has and master node should have installed latest packages from these repos by applying following commands:
`List of commands to come`
Also, user should know that update repositories that are configured should be
accessible from all nodes in order for updates to be consumed.
description: | updated |
tags: | added: life-cycle-management |
no longer affects: | fuel/6.1.x |
no longer affects: | fuel/7.0.x |
Changed in fuel: | |
milestone: | 7.0 → 5.1.1-updates |
milestone: | 5.1.1-updates → 8.0 |
tags: | added: area-docs |
Guys, I've confirmed it for 6.1 as well. Please, assign this bug to any of your teammates.