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

Documentation feedback: [FFU 16.2 -> 17.1] tripleo-<stack>-baremetal-deployment.yaml doesn't have HostnameMap parameter

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • rhos-17.1.5
    • rhos-17.1.4
    • documentation
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • None
    • Moderate

      The following sentence was added by https://issues.redhat.com/browse/OSP-33036

      https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html/framework_for_upgrades_16.2_to_17.1/performing-the-overcloud-adoption_overcloud-adoption#running-the-overcloud-upgrade-preparation_overcloud-adoption

- tripleo-<stack>-baremetal-deployment.yaml
  - Check that the value of HostnameMap in this file matches the HostnameMap value from your current overcloud, and correct the value if required.

      However, tripleo-<stack>-baremetal-deployment.yaml doesn't have the HostnameMap parameter.
      This document may confuse customers.

      Instead of HostnameMap, it has some mapping information between baremetal node UUIDs, hostnames and IP address.
      We should check the mapping instead of the HostnameMap parameter.

      I'm suggesting an example documentation update below.
      What do you think about this idea?

      tripleo-<stack>-baremetal-deployment.yaml 
Verify that this file has the correct mappings between the baremetal node UUIDs, hostnames and IP addresses that match your current overcloud.

              kgilliga@redhat.com Katie Gilligan
              rhn-support-yatanaka Yamato Tanaka
              rhos-dfg-upgrades
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: