Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1615369 - [Rebase] Rebase nbdkit to version 1.2.6
[Rebase] Rebase nbdkit to version 1.2.6
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: nbdkit (Show other bugs)
4.2.5
Unspecified Unspecified
unspecified Severity high
: ovirt-4.2.6
: ---
Assigned To: Tomáš Golembiovský
Pavol Brilla
: Rebase, ZStream
: 1615600 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-08-13 08:50 EDT by Tomáš Golembiovský
Modified: 2018-09-13 10:12 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Rebase package(s) to version: 1.2.6
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-09-04 09:44:27 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2633 None None None 2018-09-04 09:44 EDT

  None (edit)
Description Tomáš Golembiovský 2018-08-13 08:50:47 EDT
Rebase nbdkit to version 1.2.4
Comment 1 Tomáš Golembiovský 2018-08-13 10:40:55 EDT
nbdkit-1.2.6-1.1.lp.el7ev
Comment 2 Michal Skrivanek 2018-08-14 00:26:21 EDT
*** Bug 1615600 has been marked as a duplicate of this bug. ***
Comment 6 Pavol Brilla 2018-08-29 06:51:30 EDT
this is rebase, checking erratum for correct build inclusion to batch
Comment 9 errata-xmlrpc 2018-09-04 09:44:27 EDT
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/RHBA-2018:2633

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