Actions
Bug #6255
closed
First access to rule page leads to "server can not be contacted at this time"
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
On recent 3.0 nightlies, the first time we go on the rule page we get a "server cannot be contacted at this time".
Seems to appears only with certains condition on the browser - it seems that something must be initialised, but if it was even in a distant past, it is OK.
Clearing cache on browser is not sufficient to bring it back.
Using a new URL for Rudder make it appears - so something cookies or local storage related ?
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/826
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 2be8dc51b297b07dbe75dc156b42d07a2489fcc3.
Updated by François ARMAND almost 10 years ago
Applied in changeset 4e64c5846e1b05fbf6fc4dc9b29c1b8f0509f188.
Updated by Vincent MEMBRÉ over 9 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/
Actions