Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1517697 - [TestOnly] Upgrade OSP10 -> OSP11 with existing VM and validate existing VM and new VMs are working
Summary: [TestOnly] Upgrade OSP10 -> OSP11 with existing VM and validate existing VM a...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 10.0 (Newton)
Assignee: Yariv
QA Contact: Yariv
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-27 09:10 UTC by Saravanan KR
Modified: 2018-08-13 12:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-08-13 12:34:31 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Saravanan KR 2017-11-27 09:10:45 UTC
Description of problem:
OSP10 is with dpdkvhostuser mode. Sockets are created at /var/run/openvswitch directory.
OSP11 is with dpdkvhostuserclient mode. Sockets are created at /var/lib/vhost_sockets directory.
Perform upgrade test from OSP10 to OSP11.

Steps to Reproduce:
1. Deploy OSP10 with DPDK and create a VM and ensure ping is working
2. Upgrade OSP10 -> OSP11
3. Ensure the existing VM is working after migration and pingable
4. Create new VMs and ensure it is pingable

* Not sure if this scenario has been already tested. If already tested and validated, please specific it and close the BZ. 
* In order to have better picture, logs and contents for the vhost socket directory would be more helpful.

Note You need to log in before you can comment on or make changes to this bug.