Description of problem: The 'deploy' command has been discarded , but the help page of `oc rollback` still show it . Version-Release number of selected component (if applicable): [zhouying@dhcp-140-138 ~]$ oc version Client Version: 4.7.0-202012220147.p0-8fbc95f How reproducible: always Steps to Reproduce: 1.`oc rollback -h` Actual results: 1. Show the nonexistent command info: Any image triggers present in the rolled back configuration will be disabled with a warning. This is to help prevent your rolled back deployment from being replaced by a triggered deployment soon after your rollback. To re-enable the triggers, use the 'deploy' command. Expected results: 1. Show correct help info. Additional info:
the issue has fixed with latest oc client: [root@dhcp-140-138 verification-tests]# oc rollback -h Revert an application back to a previous deployment .... Any image triggers present in the rolled back configuration will be disabled with a warning. This is to help prevent your rolled back deployment from being replaced by a triggered deployment soon after your rollback. To re-enable the triggers, use the 'set triggers' command. [root@dhcp-140-138 verification-tests]# oc version --client Client Version: 4.7.0-202101092121.p0-eeb9d6d
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633