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.
DescriptionJan Pokorný [poki]
2016-05-20 18:29:56 UTC
To preserve our own sanity, finally switch over to following schema:
- have all the packages providing metadata stated as BuildRequires
(possibly incl. cman for ccs_update_schema)
- possibly invoke explicit "ccs_update_schema -f" as part of %build
- ship resulting /var/lib/cluster/cluster.rng
as /usr/share/ccs/cluster.rng
-> no need to handle extra bug if there is any other for ricci component
as metadata will get updated just as a matter of new build if the
timing is suitable (see below)
Obstacles:
- all such packages providing metadata need to be pushed to buildroot
explicitly/knowingly
- the last build of ricci component has to be queued after the last build
of each such package that modifies metadata in any way (can lead to
multiple iterations during last-minute fluctuations in the packages,
hence requires responsible handling)
+++ This bug was initially created as a clone of Bug #1272588 +++