Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-19242

Documentation feedback: "openstack overcloud node delete" command of "Removing a Compute node manually" is wrong

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • rhos-17.1.z
    • documentation
    • None
    • 0
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • rhos-workloads-compute
    • None
    • Important

      "Removing a Compute node manually" document has the following command:

      https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html/installing_and_managing_red_hat_openstack_platform_with_director/assembly_scaling-overcloud-nodes#proc_removing-compute-node-manually_scaling-overcloud-nodes

      18. Delete the Compute node from the stack:
      (undercloud)$ openstack overcloud node delete --stack <overcloud> <node> --baremetal-deployment <baremetal_deployment_file> 
      

      However this command definitely fails with the following error:

      (undercloud) [stack@undercloud ~]$ openstack overcloud node delete --stack central central-novacompute-1 --baremetal-deployment central/overcloud-baremetal-deploy.yaml 
      usage: openstack overcloud node delete [-h] [-b <BAREMETAL DEPLOYMENT FILE>] [--stack STACK] [--timeout <TIMEOUT>] [--overcloud-ssh-port-timeout OVERCLOUD_SSH_PORT_TIMEOUT] [-y] [<node> ...]
      openstack overcloud node delete: error: argument -b/--baremetal-deployment: not allowed with argument <node>
      

      If I remember correctly, this document had correct contents previously, but the current content is wrong.
      I'm not sure why this document was updated with the wrong content.

              joflynn@redhat.com Joanne O'Flynn
              rhn-support-yatanaka Yamato Tanaka
              rhos-workloads-compute
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: