Project

General

Profile

Actions

Bug #6198

closed

Server cannot be contacted at this time when deleting a Directive

Added by Nicolas CHARLES about 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
1
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

On Rudder 3.0, we get the dreaded "Server cannot be contacted at this time" when trying to delete a directive


Related issues

Related to Rudder - Bug #6172: "Server cannot be contacted at this time" when tring to get Event Log detailsReleasedFrançois ARMAND2015-01-22Actions
Related to Rudder - Bug #6203: If I create a rule, the Rules table is not correctly refreshed, and I get a neverending "loading"ReleasedVincent MEMBRÉ2015-01-30Actions
Actions #1

Updated by François ARMAND about 6 years ago

I can't reproduce this one nor #6203.

So either were corrected at some point by something else (but nothing obvious for that), or they depends on something else. They both seem linked to ajax timeout, so I suspect something like an error in the JS returned interpreted differently by browser, or something like network condition...

Nico, do you still get them ?

(see also #6203)

Actions #2

Updated by François ARMAND about 6 years ago

  • Status changed from New to Discussion
  • Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES

I also tested with Firefox 31.4esr, and it works as expected.

Nico, could you test with a recent version ?

Actions #3

Updated by François ARMAND about 6 years ago

  • Status changed from Discussion to Pending technical review
  • Pull Request set to https://github.com/Normation/rudder/pull/817

OK, so we were trying to redisplay the form of the deleted directive :(

https://github.com/Normation/rudder/pull/817

Actions #4

Updated by François ARMAND about 6 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #6

Updated by Vincent MEMBRÉ about 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0, which was released on 2015/02/16

Actions

Also available in: Atom PDF