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

Edpm-ansible jinja fixes due to Ansible-core 2.19

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • rhos-18.0.13
    • None
    • edpm-ansible
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • openstack-ansible-ee-container-1.0.15-2
    • None
    • Important

      When running dataplane-adoption I run into "badly" formatted strings in `chassis_mac_mappings` which appears to be constructed here[1]

      Example:

      external_ids:ovn-chassis-mac-mappings=\"Nonedatacentre:3e:0a:a7:14:e9:f4\" external_ids:ovn-encap-ip=172.19.0.103 external_ids:ovn-encap-type=geneve external_ids:ovn-encap-tos=0 external_ids:ovn-match-northd-version=False external_ids:ovn-monitor-all=True external_ids:ovn-remote=\"\"

      Notice `None` before datacenter
      Also notice that ovn-remote is empty and fails with

      "ovs-vsctl: external_ids:ovn-remote=: argument does not end in \"=\" followed by a value."

      Pod is running ansible-core 2.19
      Most likely related to OSPRH-18609

      [1] https://github.com/openstack-k8s-operators/edpm-ansible/blob/main/roles/edpm_ovn/defaults/main.yml#L84

              mtomaska@redhat.com Miro Tomaska
              mtomaska@redhat.com Miro Tomaska
              Fiorella Yanac Fiorella Yanac
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: