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

Migration fails when creating the port of the VM

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • Critical

      In a RHOSO 18 FR4 fresh environment:

      Migrate a VM fails with the following error:

      TASK [os_migrate.vmware_migration_kit.import_workloads : Create network port] ***  
      18:34:04
      274
      fatal: [conversion_host]: FAILED! => {"changed": false, "msg": "Failed to create port: Expected HTTP response code [201 202] when accessing [POST https://neutron-public-openstack.apps.cluster-nnjpv.dynamic.redhatworkshops.io/v2.0/ports], but got 400 instead: {\"NeutronError\": {\"type\": \"InvalidInput\", \"message\": \"Invalid input for operation: IP addresses '10.0.0.2' already used by the 'network:distributed' port(s) in the same network.\", \"detail\": \"\"}}", "ports": null} 
      [lab-user@bastion ~]$ openstack port list +--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+ | ID | Name | MAC Address | Fixed IP Addresses | Status | +--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+ | 2a569fab-6826-48f4-87c5-cc56f0e3d7ee | | fa:16:3e:67:d3:7c | ip_address='11.0.0.2', subnet_id='4830dbba-7904-4260-a3de-fe66c9a6b148' | DOWN | | 3196f431-be50-49ad-90ac-5450f9c415d2 | | fa:16:3e:25:09:fa | ip_address='10.0.0.143', subnet_id='3771db71-d7f8-4148-a293-3602645cacb1' | ACTIVE | | 38b3b559-d3af-4e9e-842d-e5a7f1bf9b2b | | fa:16:3e:e7:ea:10 | ip_address='11.0.0.54', subnet_id='4830dbba-7904-4260-a3de-fe66c9a6b148' | ACTIVE | | 7a5e3573-4267-48a4-acb9-3eb1d587f704 | | fa:16:3e:55:fe:75 | ip_address='10.0.0.1', subnet_id='3771db71-d7f8-4148-a293-3602645cacb1' | ACTIVE | | 94ee2da7-59a8-40c6-9b7c-a38dddad64ea | | fa:16:3e:30:f7:4f | ip_address='10.0.0.2', subnet_id='3771db71-d7f8-4148-a293-3602645cacb1' | DOWN | | 9adc8a93-cba4-461f-918b-e144d29c7973 | | fa:16:3e:c6:5e:0d | | DOWN | | c7197187-1c52-457b-a1d6-f2525415dd27 | | fa:16:3e:85:94:6d | ip_address='192.168.7.61', subnet_id='e26ff518-d20f-4d4e-acca-c770028f61cc' | DOWN | | ef27f642-6139-4a0a-94e6-f86dc78ec740 | | fa:16:3e:dc:0e:6e | ip_address='192.168.7.58', subnet_id='e26ff518-d20f-4d4e-acca-c770028f61cc' | N/A | +--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+
      

      Looking at neutron logs:

      OVN's validation rejects the 0.0.0.0/0 allowed address pair because it would conflict with 10.0.0.2
       
      Apparently it's related to the use of of IP address "0.0.0.0/0" as source of AllowedAddressPairs parameter here: https://github.com/os-migrate/vmware-migration-kit/blob/main/plugins/module_utils/openstack/network.go#L93
       
       

              rhn-engineering-mbultel mathieu bultel
              pnavarro@redhat.com Pedro Navarro Perez
              rhos-dfg-migrations
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: