enable_server swift3 fails test for legacy swift service

Bug #1313414 reported by Alun Champion
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devstack
Invalid
Undecided
Unassigned

Bug Description

Enabling swift3 causes the check for legacy swift service name to trip up:
    FATAL: 'swift' is not supported as a service name
    FATAL: Use the actual swift service names to enable tham as required:
    FATAL: s-proxy s-object s-container s-account

Offending line:
153 if [[ ,${ENABLED_SERVICES} =~ ,"swift" ]]; then

Presumably just needs to be changed to:
153 if [[ ,${ENABLED_SERVICES}, =~ ,"swift", ]]; then

Revision history for this message
Sean Dague (sdague) wrote :

This devstack bug was last updated over 180 days ago, as devstack
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.

Changed in devstack:
status: New → Invalid
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.