Currently workload VMs start before subnet is connected to router.
When DVR is enabled this causes sometimes that one of the VMs is not
able to get metadata.
Closes bug: #1947547
(Manually cherry picked from Neutron d49ce1652d31fb884285ed30e39ec10ef40c864d)
Change-Id: Ifd686d7ff452abd1226fbbc97f499e05102e4596
Some VMs are created before the ovn mgiration process starts in order to
verify they are healthy after the migration
Sometimes these VMs are not accessible via ssh due to an issue in cirros
0.4.0 that was fixed in a later release [1]
Closes-Bug: #1945299
[1] https://github.com/cirros-dev/cirros/pull/11
Change-Id: Ib133b5e1bed19aeac8514e3c6690ca768991bbd4
(cherry picked from neutron commit
459f63439beb81a33e5e65d0c54c61832186f42e)
Change-Id: Iedb47e413596f1124727a88e373bc3ffe433232b
The link used for downloading cirros image is now redirecting to
some other location. Due to this reason the image was not downloaded
properly and created vm instance was not usable causing migration
to fail. This patch sets a correct link for cirros image. It also
adds a -L flag to curl allowing it to follow redirects and download
the image successfully.
Change-Id: Iebc8278aca56f87fcf74cc2725a1ffc1197c1bf4
The ovn_migration.yaml playbook uses the tag 'include_role'
which is not allowed. We see the below error.
This patch fixes it
ERROR! 'include_role' is not a valid attribute for a Play
The error appears to have been in '/home/stack/ovn_migration/
tripleo_environment/playbooks/ovn-migration.yml': line 76, column 3, but may
be elsewhere in the file depending on the exact syntax problem.
This patch also fixes another error. When the pre migation VM is created, we
test it by running the command '/sbin/ip'. In some of the cirros images
the right path is '/bin/ip'. So change this to the comand 'date'.
Change-Id: Id8f8e2bbc71fee63f14339bc6041c04f3a177495
Closes-bug: #1788158
This patch adds ansible playbooks and roles to carry out migration of
an existing ML2/OVS tripleo setup to ML2/OVN.
In this patch, all the migration tasks are carried out using ansible.
Below are the migration steps
1. Generates a hosts file with the ip addresses of the controllers
and computes.
2. Creates pre migration resources (including a VM) and validates them
3. Runs the overcloud deploy script with ovn-controller's configured to
use a temporary ovs bridge (OVNIntegrationBridge: "br-migration")
4. Carry out the migration tasks
- Generate the OVN north db by running ovn sync util
- Configure ovn-controllers to take over br-int
- Delete all the qrouter/q-dhcp namespaces
5. Validates the pre migration resources again to check if everything is fine
or not.
6. Deletes the pre migration resources and creates and validates post migration
resources.
7. Deletes the post migration resources
8. And finally runs the overcloud deploy script again by setting
"OVNIntegrationBridge: "br-int"
Co-authored-by: Miguel Angel Ajo <majopela@redhat.com>
Change-Id: I29f0d729f8e2ad644aa1eead7c0802995ee279a9
Lucas Alvares Gomes
Eduardo Olivares
Roman Safronov
Numan Siddique