Actions
Bug #6935
closed
Name Resolution 3.0 doesn't report a thing
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
Hi,
I created a Name Resolution directive 3.0 in Rudder 3.0.6, and applied it to a group.
Server and node are debian jessie
The configuration in the directive is applied on the nodes contained in the group, but the nodes don't log the promise (no trace of it), and the server doesn't get an answer for the Rule.
Updated by Julien Bouillot over 9 years ago
I opened the ticket in the wrong project, please close this one, i'll open a new one in the appropriate project and drink some more coffee
Updated by Nicolas CHARLES over 9 years ago
- Project changed from Rudder websites to Rudder
I corrected the project, thank you Julien
Updated by Vincent MEMBRÉ over 9 years ago
- Has duplicate Bug #6936: Name Resolution 3.0 doesn't report a thing added
Updated by Alexis Mousset over 9 years ago
It should have been fixed by #6775, which will be released in the next minor version, namely 3.0.7 for the 3.0 branch.
Updated by Alexis Mousset over 9 years ago
- Is duplicate of Bug #6775: No reporting in dnsConfiguration 3.0 added
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from New to Released
This bug has been fixed in Rudder 3.0.7 and 3.1.0 which were released today.
- Announcement 3.0 3.1
- Changelog 3.0 3.1
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Alexis Mousset over 5 years ago
- Target version set to 3.0.7
- Priority set to 0
Actions