Project

General

Profile

Actions

Bug #4328

closed

'sshConfiguration' Technique v3.0: "SSH Port Configuration" returns "No answer" if disabled + typo

Added by Alex Tkachenko over 10 years ago. Updated about 10 years ago.

Status:
Released
Priority:
2
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

There is a typo in the rudder_openssh_server_configuration_reporting methods section. It currently reads:

...
# When no port edition is defined
"any" 
usebundle  => rudder_common_report("${service_name}", "result_success", "${${params}[report]}", "SSH port configuration", "None", "The ${service_name} port configuration are not set for edition"),
ifvarclass => "${class_prefix}_ports_edit";
...

In this form, if no port configuration is requested, this results in "No Answer" response for the SSH Port Configuration section. I believe the intent was to use the negated class, i.e.

ifvarclass => "!${class_prefix}_ports_edit";

Also there is a typo in the message itself. I think it should read "The ${service_name} port configuration is not set for edition"

(discovered in rudder v 2.8.1; 2.9.1 seems to have the same issue).


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #3975: OpenSSH v3 technique => no answerRejectedMatthieu CERDA2013-09-30Actions
Actions

Also available in: Atom PDF