Bug 1293565 - Upgrade ovirt-setup-lib to 1.0.1
Summary: Upgrade ovirt-setup-lib to 1.0.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-setup-lib
Version: 3.6.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-3.6.2
: 3.6.2
Assignee: Sandro Bonazzola
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On: 1221926
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-22 08:02 UTC by Sandro Bonazzola
Modified: 2016-03-09 19:56 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Rebase: Bug Fixes Only
Doc Text:
An update to ovirt-setup-lib is now available. The package includes common code for rhevm and ovirt-hosted-engine-setup. This update provides fixes to better validate the engine virtual machine FQDN if the user chooses to configure it via cloud-init.
Clone Of:
Environment:
Last Closed: 2016-03-09 19:56:21 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-2016:0402 0 normal SHIPPED_LIVE new package: ovirt-setup-lib 2016-03-10 00:05:13 UTC

Description Sandro Bonazzola 2015-12-22 08:02:54 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Pavol Brilla 2016-01-21 16:26:32 UTC
Verified on: 3.6.2.6-0.1.el6

# rpm -q ovirt-setup-lib  rhevm
ovirt-setup-lib-1.0.1-1.el6ev.noarch
rhevm-3.6.2.6-0.1.el6.noarch

Comment 4 errata-xmlrpc 2016-03-09 19:56:21 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://rhn.redhat.com/errata/RHEA-2016-0402.html


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