Bug #6198
closed
Server cannot be contacted at this time when deleting a Directive
Description
On Rudder 3.0, we get the dreaded "Server cannot be contacted at this time" when trying to delete a directive
Updated by François ARMAND about 11 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)
Updated by François ARMAND about 11 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 ?
Updated by François ARMAND about 11 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 :(
Updated by François ARMAND about 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 225d2a844bc71a9916954a89c5c420bd00ad1e35.
Updated by Nicolas CHARLES about 11 years ago
Applied in changeset fb27962ffc110b9c75bb25a0abd70b96937cf4ba.
Updated by Vincent MEMBRÉ almost 11 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
- Announcement 3.0
- Changelog 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/