Bug #3683: Rudder returns "Server cannot be contacted" if a group criteria is based on a wrong regexp - Rudder - Issue Tracker

Actions

Copy link

Bug #3683

closed

Rudder returns "Server cannot be contacted" if a group criteria is based on a wrong regexp

Added by Nicolas PERRON over 11 years ago. Updated about 11 years ago.

Status:

Released

Priority:

Assignee:

François ARMAND

Category:

Web - Nodes & inventories

Target version:

2.4.9

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

Searching nodes for a group which got a criteria based on a wrong regexp will timeout with the message "Server cannot be contacted".
I met the case by using a criteria: Node Summary => Hostname => Regexp => debian-7-[0-9](2).* (using parenthesis instead of curled brace) for example.

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Jonathan CLARKE over 11 years ago

I think this may be the same as #3734, but I'm not sure. Let's wait until it's fixed, then check again.

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Target version changed from 2.6.3 to 2.6.4

Actions

Copy link

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.6.4 to 2.6.5

Actions

Copy link

Updated by François ARMAND about 11 years ago

Status changed from New to Discussion
Assignee set to Nicolas PERRON

It could be linked to #3674, as suggest: http://www.rudder-project.org/redmine/issues/3674#note-36.

Nicolas, do you think it could be the case?

Actions

Copy link

Updated by Nicolas PERRON about 11 years ago

François ARMAND wrote:

It could be linked to #3674, as suggest: http://www.rudder-project.org/redmine/issues/3674#note-36.

Nicolas, do you think it could be the case?

It seems to be related. Actually, I can't reproduce the issue but Nicolas and me are convinced that it was related to PostgreSQL.

Actions

Copy link

Updated by Nicolas PERRON about 11 years ago

Status changed from Discussion to Rejected

Nicolas PERRON wrote:

François ARMAND wrote:

It could be linked to #3674, as suggest: http://www.rudder-project.org/redmine/issues/3674#note-36.

Nicolas, do you think it could be the case?

It seems to be related. Actually, I can't reproduce the issue but Nicolas and me are convinced that it was related to PostgreSQL.

I suppose we can reject this bug.

Actions

Copy link

Updated by Nicolas CHARLES about 11 years ago

Status changed from Rejected to 8
Assignee deleted (~~Nicolas PERRON~~)
Priority changed from N/A to 2
Target version changed from 2.6.5 to 2.4.9

I'm resurecting the bug
Using a really invalid regexp (like debian-7-[0-9)(2). ) causes the applicatin to fail

The logs contain
java.util.regex.PatternSyntaxException: Unclosed character class near index 17
debian-7-[0-9)(2).
                 ^
        at java.util.regex.Pattern.error(Pattern.java:1713) ~[na:1.6.0_26]
[2013-09-04 15:41:18] ERROR net.liftweb.http.LiftRules - Exception being returned to browser when processing /ajax_request/F714768057225JST3HG-40/
java.util.regex.PatternSyntaxException: Unclosed character class near index 17
debian-7-[0-9)(2).
                 ^
        at java.util.regex.Pattern.error(Pattern.java:1713) ~[na:1.6.0_26]
(END)

Apply on 2.4 (without the dreaded Server Cannot Be Contacted at this time) up to 2.7

Actions

Copy link

Updated by Nicolas CHARLES about 11 years ago

Subject changed from Rudder 2.6.2 return "Server cannot be contacted" if a group criteria is based on a wrong regexp to Rudder returns "Server cannot be contacted" if a group criteria is based on a wrong regexp

Actions

Copy link