Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1895304 - Rebase SLOF to match version included in qemu for RHEL-AV-8.4
Summary: Rebase SLOF to match version included in qemu for RHEL-AV-8.4
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: SLOF
Version: 8.4
Hardware: ppc64le
OS: Linux
high
high
Target Milestone: rc
: 8.4
Assignee: Miroslav Rezanina
QA Contact: xianwang
URL:
Whiteboard:
Depends On:
Blocks: 1897025
TreeView+ depends on / blocked
 
Reported: 2020-11-06 09:49 UTC by xianwang
Modified: 2020-12-02 18:42 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 06:38:06 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description xianwang 2020-11-06 09:49:14 UTC
Description of problem:
We would rebase the SLOF package so that the downstream SLOF build in RHEL-AV-8.4 matches the version included in the upstream qemu on which the RHEL-AV-8.4 qemu is based.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

Comment 1 David Gibson 2020-11-24 03:24:58 UTC
It turns out that upstream qemu didn't update SLOF images from qemu-5.1 to qemu-5.2.  Therefore, there's not really anything to be done here, we can use the existing downstream SLOF from RHEL-AV-8.3 with RHEL-AV-8.4 as well.

Mirek, do you need anything more from me to wrap this up?

Comment 2 Miroslav Rezanina 2020-11-24 06:38:06 UTC
There's no update of SLOF since last rebase done in 8.3 so we do not need to rebase and keep current version.


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