Bug #18197
closed
Bug #18192: Resources are lost during an upgrade from 6.0 to 6.1
pending changes of resources (files deleted / modified / added ) are commited automatically during upgrade
Added by Vincent MEMBRÉ about 4 years ago.
Updated about 4 years ago.
Category:
Web - Config management
- Category set to Web - Config management
- Target version set to 6.1.4
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/3210
- Status changed from In progress to Pending release
- Fix check changed from To do to Error - Blocking
it still commits ressources at upgrade
I had a technique with one resources not commited, and it was commited at upgrade
root@server:/var/rudder/configuration-repository/techniques/ncf_techniques/technique_avec_1_ressource_commit__et_une_pas_commit_/1.0/resources# git log .
commit 9eb818bddde20c3ffa4152bf56ef2144a706e592
Author: root user (CLI) <root@localhost>
Date: Tue Sep 15 14:21:28 2020 +0200 Forced technique upgrade from version on Tue Sep 15 14:21:28 CEST 2020commit 68e7d2dae751d1ada5a3c6cef39ef24ba57f2534
Author: admin <email not set>
Date: Tue Sep 15 14:12:03 2020 +0200 Committing technique technique avec 1 ressource commité et une pas commité
- Fix check changed from Error - Blocking to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.4 which was released today.
Also available in: Atom
PDF