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.
Composer is unusable from RHEL systems, because Anaconda cannot access content from the CDN (see bug #1663950).
It could if composer could pass subscription certificates through. I've proposed a pull request upstream to do just that:
https://github.com/dcantrell/pykickstart/pull/250
$ rhpkg push
Enumerating objects: 6, done.
Counting objects: 100% (6/6), done.
Delta compression using up to 8 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 4.53 KiB | 2.26 MiB/s, done.
Total 4 (delta 2), reused 0 (delta 0)
remote: *** Checking commit a968ae58f9be9176bc9dff15fdc4c43355d3fbef
remote: *** Resolves:
remote: *** Unapproved:
remote: *** rhbz#1693952
remote: *** No approved issue IDs referenced in log message or changelog for a968ae58f9be9176bc9dff15fdc4c43355d3fbef
remote: *** Unapproved issue IDs referenced in log message or changelog for a968ae58f9be9176bc9dff15fdc4c43355d3fbef
remote: *** Commit a968ae58f9be9176bc9dff15fdc4c43355d3fbef denied
remote: *** Current checkin policy requires:
remote: (((release == + and zstream == + and zstream_target_release == 8.0.0) or ((jiraProject == RHELPLAN) and ((jiraField(release) == +) or (jiraField(BZ release) == +)) and ((jiraField(zstream) == +) or (jiraField(BZ zstream) == +)) and (jiraField(ZStream Target Release) == 8.0.0))) or ((release == + and (blocker == + or exception == +) and (internal_target_release == 8.0.0 or internal_target_release == 8.0.0.0)) or ((jiraProject == RHELPLAN) and ((jiraField(release) == +) or (jiraField(BZ release) == +)) and (((jiraField(blocker) == +) or (jiraField(BZ blocker) == +)) or ((jiraField(exception) == +) or (jiraField(BZ exception) == +))) and (jiraField(fixVersions) in (8.0.0, 8.0.0.0)))))
remote: *** See https://mojo.redhat.com/docs/DOC-1020853 for more information
remote: hooklet hooks/update.secondary.d/01-gitbzverify.py failed
remote: hooks/update.secondary died
remote: error: hook declined to update refs/heads/rhel-8.0.0
To ssh://pkgs.devel.redhat.com/rpms/pykickstart
! [remote rejected] rhel-8.0.0 -> rhel-8.0.0 (hook declined)
error: failed to push some refs to 'ssh://dcantrel.redhat.com/rpms/pykickstart'
Could not execute push: Failed to execute command.
What needs to happen for me to push this change and build it?
I apparently fat fingered the commit message. This is bug ONE SIX SIX THREE NINE FIVE TWO, not ONE SIX NINE THREE NINE FIVE TWO. Fun! Fixed and pushed, build is happening.
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-2019:3432