Sanitize default names, limit to 63 chars #25
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
pushed a commit
that referenced
this pull request
Aug 26, 2014
…es-to-63-chars Sanitize default names, limit to 63 chars
ghost
merged commit 
|
Thanks, you rock! |
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I discovered today that CentOS 7 apparently shipped with this bug. Creating a CentOS 7 server in DigitalOcean with a name > 63 characters results in a server with broken SSH access (port 22 not even open).
This change ports over all the changes that were made to kitchen-openstack to get around naming issues. Limits names to <= 63 characters and strips out potentially-problematic punctuation.