Bug 1299265
| Summary: | nova-consoleauth fails to parse the ipv6 address in nova.conf/memcached_servers | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> | |
| Component: | openstack-tripleo-heat-templates | Assignee: | Marios Andreou <mandreou> | |
| Status: | CLOSED ERRATA | QA Contact: | yeylon <yeylon> | |
| Severity: | high | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 7.0 (Kilo) | CC: | apevec, dmacpher, emacchi, jcoufal, jslagle, lhh, mandreou, mburns, rhel-osp-director-maint, srevivo, yeylon | |
| Target Milestone: | y3 | |||
| Target Release: | 7.0 (Kilo) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-tripleo-heat-templates-0.8.6-106.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
'nova-consoleauth' failed to start due to how it parsed IPv6 addresses for 'memcached_servers' in 'nova.conf'. This fix corrects for the director's Heat template collection parses 'memcached_servers'. The 'nova-consoleauth' service now starts successfully.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1299510 (view as bug list) | Environment: | ||
| Last Closed: | 2016-02-18 16:50:09 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1299510 | |||
| Bug Blocks: | ||||
|
Description
Marius Cornea
2016-01-18 00:00:55 UTC
what if you put brackets in config file? Like: memcached_servers = ['[fd00:fd00:fd00:2000:f816:3eff:febb:6f34]:11211'] (memcached_servers is an array). If it works, we might want to patch THT. I got the same result: memcached_servers=['[fd00:fd00:fd00:2000:f816:3eff:feec:863c]:11211'] ValueError: Unable to parse connection string: "['[fd00:fd00:fd00:2000:f816:3eff:feec:863c]:11211']" (In reply to Marius Cornea from comment #2) > I got the same result: > > memcached_servers=['[fd00:fd00:fd00:2000:f816:3eff:feec:863c]:11211'] > > > ValueError: Unable to parse connection string: > "['[fd00:fd00:fd00:2000:f816:3eff:feec:863c]:11211']" on my v4 env, the memcached_servers in nova.conf is like: memcached_servers=172.16.2.8:11211,172.16.2.6:11211,172.16.2.9:11211 so i don't think we need the external []... so: memcached_servers=[fd00:fd00:fd00:2000:f816:3eff:feec:863c]:11211,[fd00:fd00:fd00:2000:f816:3eff:feec:864a]:11211 can we try it. at least i can't find any reports of upstream bug at https://bugs.launchpad.net/nova wrt memcached/consoleauth v6... not to say there isn't one. 12:58 < mcornea> marios: it doesn't seem to work: ValueError: Unable to parse connection string: "[fd00:fd00:fd00:2000:f816:3eff:fea4:38ba]:11211" It looks that this got fixed by: https://bugs.launchpad.net/python-memcached/+bug/1028412 but the installed version(python-memcached-1.48-4.el7.noarch) doesn't contain the patch. I got it successfully started with python-memcached-1.53-3.el7ost.noarch and the following declaration in nova.conf: memcached_servers=inet6:[fd00:fd00:fd00:2000:f816:3eff:fea4:38ba]:11211 openstack-tripleo-heat-templates-0.8.6-106.el7ost.noarch
[root@overcloud-controller-0 ~]# systemctl status openstack-nova-consoleauth.service
● openstack-nova-consoleauth.service - Cluster Controlled openstack-nova-consoleauth
Loaded: loaded (/usr/lib/systemd/system/openstack-nova-consoleauth.service; disabled; vendor preset: disabled)
Drop-In: /run/systemd/system/openstack-nova-consoleauth.service.d
└─50-pacemaker.conf
Active: active (running) since Tue 2016-01-19 05:42:00 EST; 29min ago
Main PID: 8519 (nova-consoleaut)
CGroup: /system.slice/openstack-nova-consoleauth.service
└─8519 /usr/bin/python /usr/bin/nova-consoleauth
Jan 19 05:41:59 overcloud-controller-0.localdomain systemd[1]: Starting Cluster Controlled openstack-nova-consoleauth...
Jan 19 05:42:00 overcloud-controller-0.localdomain systemd[1]: Started Cluster Controlled openstack-nova-consoleauth.
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. https://rhn.redhat.com/errata/RHBA-2016-0264.html |