1.0.0 release is not compatible with OpenStack Mitaka

Bug #1600162 reported by James Page
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vmware-nsx (Ubuntu)
Fix Released
Medium
Unassigned
Xenial
Fix Released
Medium
Unassigned
Yakkety
Fix Released
Medium
Unassigned

Bug Description

[Impact]
NSX SDN support is currently broken in Ubuntu 16.04

[Test Case]
Deploy OpenStack with NSX SDN; resulting cloud is not functional
Package FTBFS, with missing dependencies and then incompatibilities with neutron core.

[Regression Potential]
Well it can't get much worse that it is now..

[Original Bug Report]
The vmware-nsx team released an 8.0.0 release (which is compatible with OpenStack Mitaka as shipped in 16.04); the 1.0.0 release a) fails to pass its unit tests a b) is not compatible with Mitaka.

We need to update to 8.0.0 to provide compatibility.

James Page (james-page)
Changed in vmware-nsx (Ubuntu Yakkety):
status: New → Triaged
Changed in vmware-nsx (Ubuntu Xenial):
status: New → Triaged
importance: Undecided → Medium
Changed in vmware-nsx (Ubuntu Yakkety):
importance: Undecided → Medium
Revision history for this message
James Page (james-page) wrote :

8.0.0 is stuck in proposed for yakkety; its failing to build with the rest of the openstack components for newton.

Revision history for this message
James Page (james-page) wrote :

Build failures resolved in yakkety (should push through to -updates soon).

8.0.0 version uploaded to xenial-proposed for SRU Team review.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package vmware-nsx - 8.0.0-2ubuntu1

---------------
vmware-nsx (8.0.0-2ubuntu1) yakkety; urgency=medium

  * d/p/*: Pick numerous patches from upstream VCS to resolve unit
    test compatibility with Newton beta releases, resolving FTBFS.

 -- James Page <email address hidden> Fri, 22 Jul 2016 13:39:55 +0100

Changed in vmware-nsx (Ubuntu Yakkety):
status: Triaged → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello James, or anyone else affected,

Accepted vmware-nsx into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/vmware-nsx/8.0.0-0ubuntu0.16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in vmware-nsx (Ubuntu Xenial):
status: Triaged → Fix Committed
tags: added: verification-needed
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello James, or anyone else affected,

Accepted vmware-nsx into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/vmware-nsx/8.0.0-0ubuntu0.16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

James Page (james-page)
tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package vmware-nsx - 8.0.0-0ubuntu0.16.04.2

---------------
vmware-nsx (8.0.0-0ubuntu0.16.04.2) xenial; urgency=medium

  * d/python-vmware-nsx.{install,maintscript}: Install nsx.ini to
    /etc/neutron/plugins/vmware rather than directly into /etc/neutron,
    and deal with migration of any user changes (LP: #1610252).

vmware-nsx (8.0.0-0ubuntu0.16.04.1) xenial; urgency=medium

  [ James Page ]
  * New upstream release for OpenStack Mitaka (LP: #1600162, Closes: #830337).
  * Align (Build-)Depends with upstream.
  * Fix epoch for python-neutron-lbaas dependencies.
  * Switch to ostestr for unit test execution, avoiding test races and
    associated FTBFS (Closes: #830337).
  * Add BD on python-testresources (indirect test dependency).

  [ Ondřej Nový ]
  * Fixed VCS URLs (https).
  * d/rules: Removed UPSTREAM_GIT with default value
  * d/copyright: Changed source URL to https protocol

 -- James Page <email address hidden> Fri, 05 Aug 2016 14:46:20 +0100

Changed in vmware-nsx (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Update Released

The verification of the Stable Release Update for vmware-nsx has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.