Bug #3683
closed
Rudder returns "Server cannot be contacted" if a group criteria is based on a wrong regexp
Added by Nicolas PERRON almost 11 years ago.
Updated over 10 years ago.
Category:
Web - Nodes & inventories
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.
I think this may be the same as #3734, but I'm not sure. Let's wait until it's fixed, then check again.
- Target version changed from 2.6.3 to 2.6.4
- Target version changed from 2.6.4 to 2.6.5
- Status changed from New to Discussion
- Assignee set to Nicolas PERRON
- 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.
- 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
- 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
- Assignee set to Nicolas CHARLES
- Status changed from 8 to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/312
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
This bug has been fixed in Rudder 2.4.9, which was released today.
Check out:
- Status changed from Pending release to Released
Also available in: Atom
PDF
Updated by 
Updated by Nicolas PERRON 
Updated by 
Updated by 
Updated by Anonymous