Bug 1300398 - Horizon fails to load in IPv6 deployment
Horizon fails to load in IPv6 deployment
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
medium Severity high
: y3
: 7.0 (Kilo)
Assigned To: Emilien Macchi
Depends On:
Blocks: 1320512
  Show dependency treegraph
Reported: 2016-01-20 11:40 EST by Marius Cornea
Modified: 2016-04-18 03:13 EDT (History)
8 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-0.8.6-110.el7ost
Doc Type: Bug Fix
Doc Text:
Horizon failed to load in IPv6 Overclouds due to issues with how the director detected and parsed IPv6 addresses for Memcached. This fix changes how the director's Heat template collection enables IPv6 addresses for Memcached. This includes a new parameter 'MemcachedIPv6' that defines if Memcached uses IPv4 or IPv6 addresses.
Story Points: ---
Clone Of:
: 1320512 (view as bug list)
Last Closed: 2016-02-18 11:50:38 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marius Cornea 2016-01-20 11:40:14 EST
Description of problem:
Horizon fails to load in IPv6 deployment:
 mod_wsgi (pid=7160): Exception occurred processing WSGI script '/usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi'.
 Traceback (most recent call last):
   File "/usr/lib/python2.7/site-packages/django/http/response.py", line 309, in close
   File "/usr/lib/python2.7/site-packages/django/dispatch/dispatcher.py", line 201, in send
     response = receiver(signal=self, sender=sender, **named)
   File "/usr/lib/python2.7/site-packages/django/core/cache/__init__.py", line 156, in close_caches
   File "/usr/lib/python2.7/site-packages/django/core/cache/backends/memcached.py", line 111, in close
   File "/usr/lib/python2.7/site-packages/django/core/cache/backends/memcached.py", line 175, in _cache
     self._client = self._lib.Client(self._servers, pickleProtocol=pickle.HIGHEST_PROTOCOL)
   File "/usr/lib/python2.7/site-packages/memcache.py", line 207, in __init__
   File "/usr/lib/python2.7/site-packages/memcache.py", line 253, in set_servers
     for s in servers]
   File "/usr/lib/python2.7/site-packages/memcache.py", line 1087, in __init__
     raise ValueError('Unable to parse connection string: "%s"' % host)
 ValueError: Unable to parse connection string: "fd00:fd00:fd00:2000:f816:3eff:fe07:286:11211"

This is the cache config in /etc/openstack-dashboard/local_settings:

    'default': {

#        'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'
        'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',

        'LOCATION': [ 'fd00:fd00:fd00:2000:f816:3eff:fe07:286:11211','fd00:fd00:fd00:2000:f816:3eff:feac:a861:11211','fd00:fd00:fd00:2000:f816:3eff:fe1b:11d1:11211', ],


Version-Release number of selected component (if applicable):
Comment 2 Marius Cornea 2016-01-21 06:28:40 EST
Comment 4 errata-xmlrpc 2016-02-18 11:50:38 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.