Instance create fails due to invalid DNS record name

Bug #1262789 reported by Steve Leon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
Undecided
Steve Leon

Bug Description

DNS records are obtained from a decoded hash of the instance names. SInce we use base64 encoding, sometimes the record name that we get starts with a hyphen '-'. This is illegal for hostname. Also base64 encoding gives you upper and lower case letters. Hostnames are case insensitive.

The fix would be to use base32 encoding which gives you upper case letters and numbers which are legal for hostnames.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

Fix proposed to branch: master
Review: https://review.openstack.org/63186

Changed in trove:
assignee: nobody → Steve Leon (steve-leon)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/63186
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=56dda9825beaf9580ca6099c76e2c0d6037db9eb
Submitter: Jenkins
Branch: master

commit 56dda9825beaf9580ca6099c76e2c0d6037db9eb
Author: Steve Leon <email address hidden>
Date: Thu Dec 19 10:20:35 2013 -0800

    Using base32 encoding to generate DNS records

    The Designate driver generate record names by
    hashing and 64-base encoding the instance ID.
    The problem is that 64-base encoding can generate
    hyphens and upper/lower case letters. Hyphens are
    illegal when it is at the beginning of the name.
    Name is also case insensitive. So the best solution
    is to use BASE-32 encoding.

    Change-Id: Ie98a0a50a609207df041c5f0bc2f622701ee9848
    Closes-Bug: #1262789

Changed in trove:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in trove:
milestone: none → icehouse-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in trove:
milestone: icehouse-2 → 2014.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.