The bug was not reproduced with ISO that contained openstack-auth-1.1.7 packet:
To test if this bug was observed with openstack-auth packet version: 1.1.7
I took "fuel-5.1.1-20-2014-11-18_11-07-36.iso" and deployed the following
configurations:
Configuration1:
OpenStack Release: Icehouse on CentOS 6.5
Deployment Mode: Multi-node with HA
Compute: QEMU
Network: Nova-Network
Storage Backends: Cinder (Default), Glance (Default
In both configurations when I shutted down (killed) primary controller
haproxy switched to another one and I was able to log into dashboard,
the message "Something went wrong! An unexpected error has occurred.
Try refreshing the page. If that doesn't help, contact your local administrator."
was not observed.
The bug was not reproduced with ISO that contained openstack- auth-1. 1.7 packet:
To test if this bug was observed with openstack-auth packet version: 1.1.7 1.1-20- 2014-11- 18_11-07- 36.iso" and deployed the following
I took "fuel-5.
configurations:
Configuration1:
OpenStack Release: Icehouse on CentOS 6.5
Deployment Mode: Multi-node with HA
Compute: QEMU
Network: Nova-Network
Storage Backends: Cinder (Default), Glance (Default
3 Controllers
3 Compute
# rpm -qa | grep openstack-auth django- openstack- auth-1. 1.7-1.mira1. noarch
python-
------- ------- ------- ------- ------- ------- ------- --
Configuration2:
OpenStack Release: Icehouse on Ubuntu 12.04.4
Deployment Mode: Multi-node with HA
Compute: QEMU
Network: Nova-Network
Storage Backends: Cinder (Default), Glance (Default
3 Controllers
3 Compute
# dpkg -l | grep openstack-auth openstack- auth 1.1.7-ubuntu1 Django authentication backend for Openstack
ii python-
------- ------- ------- ------- ------- ------- ------- --
In both configurations when I shutted down (killed) primary controller
haproxy switched to another one and I was able to log into dashboard,
the message "Something went wrong! An unexpected error has occurred.
Try refreshing the page. If that doesn't help, contact your local administrator."
was not observed.