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

Openstack UPI - Reintroduce unique resource names

XMLWordPrintable

    • +
    • Moderate
    • No
    • ShiftStack Sprint 259, ShiftStack Sprint 260
    • 2
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, adding IPv6 support for user-provisioned installation platforms caused an issue with naming {rh-openstack-first} resources, especially when you run two user-provisioned installation clusters on the same {rh-openstack-first} platform. This happened because the two clusters share the same names for network, subnets, and router resources. With this release, all the resources names for a cluster remain unique for that cluster so no interfere occurs. (link:https://issues.redhat.com/browse/OCPBUGS-42011[*OCPBUGS-42011*])
      Show
      * Previously, adding IPv6 support for user-provisioned installation platforms caused an issue with naming {rh-openstack-first} resources, especially when you run two user-provisioned installation clusters on the same {rh-openstack-first} platform. This happened because the two clusters share the same names for network, subnets, and router resources. With this release, all the resources names for a cluster remain unique for that cluster so no interfere occurs. (link: https://issues.redhat.com/browse/OCPBUGS-42011 [* OCPBUGS-42011 *])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-36855. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-33973. The following is the description of the original issue:

      Description of problem:

      The network resource provisioning playbook for 4.15 dualstack UPI contains a task for adding an IPv6 subnet to the existing external router [1].
      This task fails with:
      - ansible-2.9.27-1.el8ae.noarch & ansible-collections-openstack-1.8.0-2.20220513065417.5bb8312.el8ost.noarch in OSP 16 env (RHEL 8.5) or
      - openstack-ansible-core-2.14.2-4.1.el9ost.x86_64 & ansible-collections-openstack-1.9.1-17.1.20230621074746.0e9a6f2.el9ost.noarch in OSP 17 env (RHEL 9.2)
      
      Besides that we need to have a way for identifying resources for particular deployment, as it may interfere with existing one.

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

      4.15.0-0.nightly-2024-01-22-160236

      How reproducible:

      Always

      Steps to Reproduce:

      1. Set the os_subnet6 in the inventory file for setting dualstack
      2. Run the 4.15 network.yaml playbook
      

      Actual results:

      Playbook fails:
      TASK [Add IPv6 subnet to the external router] ********************************** fatal: [localhost]: FAILED! => {"changed": false, "extra_data": {"data": null, "details": "Invalid input for external_gateway_info. Reason: Validation of dictionary's keys failed. Expected keys: {'network_id'} Provided keys: {'external_fixed_ips'}.", "response": "{\"NeutronError\": {\"type\": \"HTTPBadRequest\", \"message\": \"Invalid input for external_gateway_info. Reason: Validation of dictionary's keys failed. Expected keys: {'network_id'} Provided keys: {'external_fixed_ips'}.\", \"detail\": \"\"}}"}, "msg": "Error updating router 8352c9c0-dc39-46ed-94ed-c038f6987cad: Client Error for url: https://10.46.43.81:13696/v2.0/routers/8352c9c0-dc39-46ed-94ed-c038f6987cad, Invalid input for external_gateway_info. Reason: Validation of dictionary's keys failed. Expected keys: {'network_id'} Provided keys: {'external_fixed_ips'}."}

      Expected results:

      Successful playbook execution

      Additional info:

      The router can be created in two different tasks, the playbook [2] worked for me.

      [1] https://github.com/openshift/installer/blob/1349161e2bb8606574696bf1e3bc20ae054e60f8/upi/openstack/network.yaml#L43
      [2] https://file.rdu.redhat.com/juriarte/upi/network.yaml

              maandre@redhat.com Martin André
              openshift-crt-jira-prow OpenShift Prow Bot
              Jon Uriarte Jon Uriarte
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: