Bug 1652841 - Upgrade openstack-java-sdk to 3.2.5
Summary: Upgrade openstack-java-sdk to 3.2.5
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: openstack-java-sdk
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.3.0
: ---
Assignee: Sandro Bonazzola
QA Contact: Pavel Novotny
URL:
Whiteboard:
Depends On:
Blocks: 1539829
TreeView+ depends on / blocked
 
Reported: 2018-11-23 09:07 UTC by Dominik Holler
Modified: 2019-05-08 12:31 UTC (History)
2 users (show)

Fixed In Version: openstack-java-sdk-3.2.5-1.el7ev
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-08 12:31:06 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1036 0 None None None 2019-05-08 12:31:08 UTC

Description Dominik Holler 2018-11-23 09:07:52 UTC 
Version 3.2.5 of openstack-java-sdk adds support for the port_security_enabled of OpenStack networks. This update is required because Engine is going to be extended to control this attribute during the creation of new external networks.
Comment 2 Sandro Bonazzola 2018-11-23 13:19:23 UTC 
CentOS Virt SIG build is in testing here: https://cbs.centos.org/koji/buildinfo?buildID=24667
Comment 3 Dominik Holler 2018-11-23 13:59:01 UTC 
(In reply to Sandro Bonazzola from comment #2)
> CentOS Virt SIG build is in testing here:
> https://cbs.centos.org/koji/buildinfo?buildID=24667

Thanks, I verified that the rpms are good.
Comment 7 errata-xmlrpc 2019-05-08 12:31:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:1036
Note You need to log in before you can comment on or make changes to this bug.