Description of problem:
oc logs supports not only pods. Current usage info conflicts with examples and makes users confused.
usage info should be updated to include other resource types such as BC,DC
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. oc logs -h
oc logs [-f] [-p] POD [-c CONTAINER] [options]
# Start streaming the logs of the most recent build of the openldap build config.
oc logs -f bc/openldap
# Start streaming the logs of the latest deployment of the mysql deployment config.
oc logs -f dc/mysql
# Get the logs of the first deployment for the mysql deployment config. Note that logs
# from older deployments may not exist either because the deployment was successful
# or due to deployment pruning or manual deletion of the deployment.
oc logs --version=1 dc/mysql
# Return a snapshot of ruby-container logs from pod backend.
oc logs backend -c ruby-container
# Start streaming of ruby-container logs from pod backend.
oc logs -f pod/backend -c ruby-container
update usage info accordingly.
This is fixed.
oc logs [-f] [-p] (POD | TYPE/NAME) [-c CONTAINER] [flags]
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.