Bug 1661809 - python-swift not installed on UC or OC Controller nodes in '14 -p 2018-12-07.2'
Summary: python-swift not installed on UC or OC Controller nodes in '14 -p 2018-12-07.2'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-swiftclient
Version: 14.0 (Rocky)
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Christian Schwede (cschwede)
QA Contact: Mike Abrams
Laura Marsh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-23 14:37 UTC by Mike Abrams
Modified: 2020-05-05 09:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-05 09:38:34 UTC
Target Upstream Version:
Embargoed:
cschwede: needinfo-


Attachments (Terms of Use)

Comment 2 Christian Schwede (cschwede) 2019-01-03 09:52:12 UTC
Mike and me discussed this moments ago. Actually there are two commands involved that are no longer directly available on the UC/OC nodes, because these are much more lightweight with everything running in the containers nowadays.

For the swift-ring-builder command, it would be sufficient to just execute it directly within the containers. For example:

docker exec -ti -u swift swift_object_server swift-ring-builder /etc/swift/object.builder

For the swift CLI itself, one would need to install the rpm. 

That said, I think this one needs no code fix, but a doc note.

Comment 9 Dan Macpherson 2019-01-22 03:08:33 UTC
Hi Laura,

Was doing a review of the director guide content and came across this item. I think the "Managing containerized services" module isn't the best place for it -- This module is really just for basic container management commands. The content you put together is something more so specific to Swift rather than containers in general. So it might be a good idea to put together a standalone "Managing object storage" module.

Any chance we can put this new content in its own module?

- Dan


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