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

BZ#2241092 The output example of `overcloud deploy` in OSP17.1 document seems to be the old version's one.

XMLWordPrintable

    • Low

      Description of problem:

      One of our customers pointed out the part which should be fixed in our document of OSP17.1:

      Documentation: Installing and managing Red Hat OpenStack Platform with director
      Section: "11.3.6. Creating your overcloud"

      URL: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1/html-single/installing_and_managing_red_hat_openstack_platform_with_director/index#proc_creating-your-overcloud_ironic_provisioning

      There is the following output example in Procedure 4 and 5:
      ~~~
      PLAY RECAP *************************************************************
      overcloud-compute-0 : ok=160 changed=67 unreachable=0 failed=0
      overcloud-controller-0 : ok=210 changed=93 unreachable=0 failed=0
      undercloud : ok=10 changed=7 unreachable=0 failed=0

      Tuesday 15 October 2018 18:30:57 +1000 (0:00:00.107) 1:06:37.514 ******
      ========================================================================
      ~~~

      ~~~
      Ansible passed.
      Overcloud configuration completed.
      Overcloud Endpoint: http://192.168.24.113:5000
      Overcloud Horizon Dashboard URL: http://192.168.24.113:80/dashboard
      Overcloud rc file: /home/stack/overcloudrc
      Overcloud Deployed
      ~~~

      The customer reported that the output example seems to be old and OSP17.1's one is a bit different from the above.
      For example, in OSP17.1, it has the information on ephemeral-heat pod like the following:

      ~~~
      2023-09-08 12:37:52.442 604435 INFO tripleoclient.v1.overcloud_deploy.DeployOvercloud [-] Stopping ephemeral heat.
      2023-09-08 12:37:52.579 604435 INFO tripleoclient.heat_launcher [-] Pod does not exist: ephemeral-heat
      ~~~

      Additionally, the date(15 October 2018) in the above output is when OSP17.1 is not released.

      Would it be possible to replace the output with the OSP17.1's one?

              drosenfe David Rosenfeld
              jira-bugzilla-migration RH Bugzilla Integration
              rhos-docs@redhat.com rhos-docs@redhat.com
              rhos-dfg-df
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: