Bug #990
wrong error message when looking for puppetca certificate list
| Status: | New | Start: | 06/15/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Paul Kelly |
% Done: | 0% |
|
| Category: | PuppetCA | |||
| Target version: | - | |||
| Backlog: | No | Difficulity: | ||
| Votes: | 0 |
Description
this happens when the proxy is not reachable:
undefined method `map' for true:TrueClass
History
Updated by Paul Kelly almost 2 years ago
- Category set to PuppetCA
- Status changed from New to Feedback
- Assigned to set to Ohad Levy
When I stop the smart-proxy and then http://localhost:3000/smart_proxies/5/puppetca I get this message
Connection refused - connect(2)
Hardly elegant but certainly correct.
Could you see try this operation again?
Updated by Ohad Levy almost 2 years ago
- Assigned to changed from Ohad Levy to Paul Kelly
the main issue here (at least for the first error) is that the proxy library code checks the return code and the return length,
if its smaller then 2 it returns a true object.
any idea why we do that?
Updated by Paul Kelly almost 2 years ago
the smallest valid reply is "{}", which is two characters. JSON.parse chokes on anything less than two characters.
I guess it is trying to say:-
I got a valid rely cos the code says ok
return the value that we got or say that we succeeded in doing whatever we were asked.
A delete operation returns nothing.
Updated by Ohad Levy almost 2 years ago
Paul Kelly wrote:
the smallest valid reply is "{}", which is two characters. JSON.parse chokes on anything less than two characters. I guess it is trying to say:- I got a valid rely cos the code says ok return the value that we got or say that we succeeded in doing whatever we were asked.
A delete operation returns nothing.
yeah, but in this case, it returns simply true, which is wrong... can we look into it again?
Updated by Ohad Levy almost 2 years ago
- Target version deleted (
0.4)
Updated by Benjamin Papillon 6 months ago
- Status changed from Feedback to New
