Actions
Bug #4048
closed
Reports of distributePolicy promises is in 'Unknown' status caused by a duplicate reports about 'configuration-repository' git lock
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
A merge of #3899 on branch 2.6 was not correctly made and led to broke reporting of a Rudder server check.
Updated by Nicolas PERRON over 10 years ago
- Status changed from New to Pending technical review
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/217
Pull Request URL added: https://github.com/Normation/rudder-techniques/pull/217
Jon, could you review it please ?
Updated by Nicolas PERRON over 10 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset commit:e1790e5d8feb5c8d66dcc35c880cc9f6088a3086.
Updated by Jonathan CLARKE over 10 years ago
Applied in changeset commit:04711c841ac4d7dae41dd55039b3fe6d5fe0a659.
Updated by Jonathan CLARKE over 10 years ago
Clarifying the title - nothing is actually broken here, we just get duplicate reports. This causes "Unknown" compliance in the webapp, but still works just fine.
Updated by Jonathan CLARKE over 10 years ago
- Subject changed from The check of the 'configuration-repository' git lock is broken since a wrong merge from 2.4 to 2.6 to Duplicate reports from check of the 'configuration-repository' git lock since a wrong merge from 2.4 to 2.6
Updated by Nicolas PERRON over 10 years ago
- Subject changed from Duplicate reports from check of the 'configuration-repository' git lock since a wrong merge from 2.4 to 2.6 to Reports of 'Check configuration-repository GIT lock' of Rudder server is in 'Unknown status' state caused by a duplicate reports
Updated by Nicolas PERRON over 10 years ago
- Subject changed from Reports of 'Check configuration-repository GIT lock' of Rudder server is in 'Unknown status' state caused by a duplicate reports to Reports of 'Check configuration-repository GIT lock' of Rudder server is in 'Unknown' status caused by a duplicate reports
Updated by Nicolas PERRON over 10 years ago
- Subject changed from Reports of 'Check configuration-repository GIT lock' of Rudder server is in 'Unknown' status caused by a duplicate reports to Reports of distributePolicy promises is in 'Unknown' status caused by a duplicate reports about 'configuration-repository' git lock
Updated by Nicolas PERRON over 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.9 which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-November/000062.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog26
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE about 9 years ago
- Project changed from 24 to Rudder
- Category set to Techniques
Actions