Project

General

Profile

Bug #5367

Node acceptance dialog timeouts although it's working in background

Added by Lionel Le Folgoc almost 4 years ago. Updated about 1 month ago.

Status:
New
Priority:
2
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
Target version (plugin):
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Pull Request:
Priority:
29

Description

Hi,

(distributed 2.11.1 setup on ec2)
I've created 500 random inventories and I'm trying to accept the "nodes" into rudder.
With "Accept new nodes", I select 10 nodes, "Accept into rudder", wait, wait, wait, then:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /rudder/secure/nodeManager/manageNewNode.

Reason: Error reading from remote server
<pre>
Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /rudder/secure/nodeManager/manageNewNode.

Reason: Error reading from remote server
</pre>

But if I go to the "list node" page, I can see that these 10 nodes are actually being accepted right now (they're appearing one by one). After a minute or so, the 10 nodes have been accepted.

So the error above is a bit misleading. ;-)
Thanks.


Related issues

Related to Rudder - Bug #10434: Error on one inventory when trying to accept 100 inventories at the same time New

History

#1 Updated by Matthieu CERDA almost 4 years ago

  • Category set to Web - Nodes & inventories
  • Status changed from New to 8
  • Assignee set to François ARMAND
  • Priority changed from N/A to 2
  • Target version set to 2.11.2

Hmmm, this looks like a webapp issue, maybe a timing one (too short timeout ?).

Giving this to FAR for evaluation :)

Thanks Lionel !

#2 Updated by Nicolas PERRON almost 4 years ago

  • Target version changed from 2.11.2 to 2.11.3

#3 Updated by Matthieu CERDA over 3 years ago

  • Target version changed from 2.11.3 to 2.11.4

#4 Updated by François ARMAND over 3 years ago

OK, so the problem seems that we have a timeout for async (ajax) requests, and that the underlying process does not terminate before that timeout. So the ajax call actually thinks it failed, and the server acceptation process don't know that and continue its work of accepting nodes.

We could have a longer timeout for ajax requests, but of course, that doesn't solve the problem in any way. The real solution is to make the acceptation process completly asynchrone, and to have a client-side knows it is.

I don't see for now a way to resolve that without the async solution, perhaps something with partial response only for subset of the whole acceptance.

#5 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.4 to 2.11.5

#6 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.5 to 2.11.6

#7 Updated by François ARMAND over 3 years ago

Some more thought on that let me think that the behaviour as it is can't be corrected without a major refactoring of the page, and so must go in a future version of Rudder as a feature.

I think we should have one async acceptation by node (queued on the server), with a little wheel until the node is accepted (and here, we are seing a green "ok"). Node would be added one by one, so that raise the question about how to manage the start of promise generation. We can't just start one for each node, but we also can't add a grace period before starting it, else it may be delayed for hours. Or perhaps just delay with a max bound (10 minutes ?)

#8 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.6 to 2.11.7

#9 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.7 to 2.11.8

#10 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.8 to 2.11.9

#11 Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.9 to 2.11.10

#12 Updated by Benoît PECCATTE about 3 years ago

  • Status changed from 8 to New

#13 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.11.10 to 2.11.11

#14 Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.11.11 to 2.11.12

#15 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.11.12 to 2.11.13

#16 Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.11.13 to 2.11.14

#17 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.14 to 2.11.15

#18 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.15 to 2.11.16

#19 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.16 to 2.11.17

#20 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.17 to 2.11.18

#21 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.18 to 2.11.19

#22 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.19 to 2.11.20

#23 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.20 to 2.11.21

#24 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.21 to 2.11.22

#25 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.22 to 2.11.23

#26 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 2.11.23 to 2.11.24

#27 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 2.11.24 to 308

#28 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 308 to 3.1.14

#29 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.14 to 3.1.15

#30 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.15 to 3.1.16

#31 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.16 to 3.1.17

#32 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.17 to 3.1.18

#33 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.18 to 3.1.19

#34 Updated by François ARMAND about 1 year ago

  • Related to Bug #10434: Error on one inventory when trying to accept 100 inventories at the same time added

#35 Updated by François ARMAND about 1 year ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority set to 0

#36 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.19 to 3.1.20

#37 Updated by Jonathan CLARKE about 1 year ago

  • Assignee deleted (François ARMAND)

#38 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.20 to 3.1.21

#39 Updated by François ARMAND about 1 year ago

  • Priority changed from 0 to 14

#40 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.21 to 3.1.22

#41 Updated by Benoît PECCATTE 12 months ago

  • Priority changed from 14 to 27

#42 Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 3.1.22 to 3.1.23

#43 Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 3.1.23 to 3.1.24

#44 Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 3.1.24 to 3.1.25
  • Priority changed from 27 to 28

#45 Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 3.1.25 to 387

#46 Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 387 to 4.1.10

#47 Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 4.1.10 to 4.1.11
  • Priority changed from 28 to 29

#48 Updated by Vincent MEMBRÉ 2 months ago

  • Target version changed from 4.1.11 to 4.1.12

#49 Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 4.1.12 to 4.1.13

Also available in: Atom PDF