Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-46431

"oc rollout cancel/oc rollout latest/oc rollout retry" only work for deploymentconfig, should be deprecated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.17
    • oc
    • None
    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None
    • We removed DeploymentConfig from the examples and descriptions of `oc rollout` command (and the inner subcommands). Help texts will no longer mention DeploymentConfig (apart from oc rollout latest, cancel, retry).
    • Removed Functionality
    • In Progress

      Description of problem:

      We are planning to disable the DeploymentConfig capability by default starting OCP 4.19. Customers are therefore migrating their DeploymentConfigs to Deployments (see also OCPSTRAT-1465).

      "oc rollout cancel/oc rollout latest/oc rollout retry" only work for deploymentconfig, should be deprecated

      Version-Release number of selected component (if applicable):

      $oc version --client
      Client Version: 4.17.0-0.nightly-2024-10-07-141000
      Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3

      How reproducible:

      Always

      Steps to Reproduce:
      1. Run `oc rollout cancel/oc rollout latest/oc rollout retry`

      Actual results:

      These only work for deploymentconfig, should also be deprecated

      Expected results:

      These command should be deprecated.

      Additional info:

       

              aos-workloads-staff Workloads Team Bot Account
              yinzhou@redhat.com ying zhou
              ying zhou ying zhou
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: