[upgrade] upgrade procedure should update agent/mc agent/network checker
Bug #1343139 reported by
Dima Shulyak
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
High
|
Fuel Python (Deprecated) |
Bug Description
Packages fuel agent, mcollective agent and network checker are part of control plane and not openstack.
Not upgrading them means that bugs fixed in those packages wont affect already deployed nodes.
It also introduces some limitation on changing/adding actions to astute/network checker.
If this will be considered by design, atleast it should be fixed by puppet in case of environment patching, because as for now - they are installed by means of kickstart/preseed configurations.
summary: |
- upgrade procedure should update agent/mc agent/netwrok checker + [upgrade] upgrade procedure should update agent/mc agent/netwrok checker |
tags: | added: patching upgrade |
Changed in fuel: | |
status: | New → Confirmed |
summary: |
- [upgrade] upgrade procedure should update agent/mc agent/netwrok checker + [upgrade] upgrade procedure should update agent/mc agent/network checker |
tags: | added: release-notes |
Changed in fuel: | |
milestone: | 6.0 → 6.1 |
Changed in fuel: | |
status: | Confirmed → Won't Fix |
tags: | added: release-notes-done |
To post a comment you must log in.
Nailgun and Astute should support both versions of network checker.
Currently we cannot upgrade network checkers and mcollective agents, here are several reasons
1. it won't help, because after deployment user can run network checker on old cluster with new astute/nailgun
2. openstack patching feature was created to update minor changes for openstack, so, we cannot deliver code which breaks backward compatibility