Project

General

Profile

Actions

Bug #4244

closed

With initial-promises, error message is not displayed when policies could not be updated

Added by Jonathan CLARKE about 11 years ago. Updated almost 11 years ago.

Status:
Released
Priority:
3
Assignee:
Matthieu CERDA
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

If the agent cannot get it's promises from the server, it should display this:

*********************************************************************************
* rudder-agent could not get an updated configuration from the policy server. *
* This can be caused by a network issue, an unavailable server, or if this *
* node has not yet been accepted in the Rudder root server. *
*********************************************************************************

However, due to the classes changed in Rudder 2.6 to use rudder_promises_generated to optimize copy time, it doesn't get displayed.

Actions #1

Updated by Jonathan CLARKE about 11 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Matthieu CERDA
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/249
Actions #2

Updated by Jonathan CLARKE about 11 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset policy-templates:commit:162660c65f80039941f9a517142116e6cb53f119.

Actions #3

Updated by Matthieu CERDA about 11 years ago

Applied in changeset policy-templates:commit:92f1b2955fcd559f72fddfa37c2c74b46afb9c3c.

Actions #4

Updated by Vincent MEMBRÉ almost 11 years ago

  • Subject changed from Error message about no updated files is not displayed in initial-promises to With initial-promises, error message is not displayed when policies could not be updated
Actions #5

Updated by Vincent MEMBRÉ almost 11 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.10 which was released today.
Check out:

Actions

Also available in: Atom PDF