Bug 1492578

Summary: rhel: add criu to s390x
Product: Red Hat Enterprise Linux 7 Reporter: Lubos Kocman <lkocman>
Component: relengAssignee: Lubos Kocman <lkocman>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: areber, dtodorov, jstodola, jvavra, lmiksik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1492579 (view as bug list) Environment:
Last Closed: 2018-04-10 10:12:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1492579    

Description Lubos Kocman 2017-09-18 08:36:24 UTC
Starting with rhel-7.5 criu will be available for s390x and needs to be
added to the rhel-7.5 product listing.
Please also add criu to the rhel-alt-7.5 product listing for aarch64 and
s390x.
rhel-7.5 s390x: https://bugzilla.redhat.com/show_bug.cgi?id=1456513
rhel-alt-7.5 s390x: https://bugzilla.redhat.com/show_bug.cgi?id=1457955
rhel-alt-7.5 aarch64: https://bugzilla.redhat.com/show_bug.cgi?id=1464596

Adrian via Lubos

(originally reported as RCM-21637) I'll keep separate request for alt and rhel

Comment 3 Lubos Kocman 2017-10-09 12:57:46 UTC
Hi Adrian, we're missing pm_ack here. Let me get it.

Lubos

Comment 4 Adrian Reber 2017-10-09 13:00:19 UTC
Thanks!

Comment 5 Lubos Kocman 2017-10-09 13:28:42 UTC
Hello Adrian,

since the errata was created today (but it's more about the build attach time to the advisory) you'll need to wait for upcoming nightly to take.

So just click on reload filelists tomorrow and you should see s390x. I did check config and all is in place.

Lubos

Comment 16 errata-xmlrpc 2018-04-10 10:12:53 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-2018:0700