Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRichard W.M. Jones
2016-09-09 13:08:51 UTC
Description of problem:
vhostmd is a host daemon which generates metrics for guests. It
is used by SAP guests in particular.
vm-dump-metrics(-devel) is a guest package which can be used to
read these metrics. It is also used by SAP software.
These packages are currently build for all architectures, but
we only ship when on x86_64 in "RHEL for SAP".
It has been requested that these packages are added to:
s390x
ppc64
ppc64le (or maybe not? - this is not clear - see below)
in:
RHEL 7.2-z
RHEL 7.3
RHEL 7.4 and onwards
Some unknowns about this request:
- Are we creating a special RHEL for SAP channel for POWER8 and s390x?
- Are there different channels for host and guest, or is it all the same?
- Are we shipping the ppc64le version?
Version-Release number of selected component (if applicable):
- vhostmd-0.5-11.el7_1
See also:
https://bugzilla.redhat.com/show_bug.cgi?id=1182612 (s390x)
https://bugzilla.redhat.com/show_bug.cgi?id=1118683 (POWER8)
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=423527http://git.app.eng.bos.redhat.com/git/rcm/rcm-metadata.git/tree/distill_ng/rhel-7/rhel-7.3-prepopulate.json#n65734
Comment 1Richard W.M. Jones
2016-09-09 13:11:53 UTC
Frank can you help with the questions in comment 0?
I see that most of the questions have been answered around ppc64 and ppc64le, both of which are needed.
We also need to support s390x as we are adding that arch to RHEL for SAP Applications as well.
To answer the other questions above:
Yes, we have separate RHEL for SAP Applications channels where we put the unique SAP Apps content as this content can NEVER be shipped in our standard RHEL channel. And yes, we have different channels for each arch, similar to what we do for RHEL.
I think that's the last of the questions, but if more is needed, please let me know.
Regards,
Cathy
devel_ack+ for missing ppc64le, not sure why I though that SAP is not on ppc64le
Thanks
Lubos
Comment 12Richard W.M. Jones
2017-02-06 09:53:47 UTC
Currently we're looking for just the following packages:
* vm-dump-metrics
* vm-dump-metrics-devel
on the following architectures:
* ppc64
* ppc64le
* s390x
for the following version:
* RHEL 7.2-z
* RHEL 7.3-z
* RHEL 7.4
Note that we're in fact *not* wishing to distribute vhostmd
at all (although the above packages are built from the vhostmd
sources). vhostmd is a hypervisor package which will be built
and distributed by IBM. We only need to guest-side packages as above.
I've update the summary to make this clearer.
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-2017:1850