Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Description of problem:
Installation of katello from upstream repos on rhel7 in FIPS mode, foreman-installer --scenario katello fails on executing
'/usr/bin/pulp-gen-ca-certificate' returned 1 instead of one of [0]
When running the command directly on the machine, it executes without providing any output with exitcode 1.
This problem does not occur when installing nightly on non-FIPS rhel
Version-Release number of selected component (if applicable):
foreman-1.18.0-0.develop.201802231059git8bd79a1.el7.noarch
katello-3.7.0-1.nightly.el7.noarch
How reproducible:
always
Comment 5pulp-infra@redhat.com
2018-05-01 16:32:10 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 6pulp-infra@redhat.com
2018-05-01 16:32:14 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 7pulp-infra@redhat.com
2018-05-23 15:32:46 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
I haven't been able to reproduce this locally thus far on FIPS-enabled CentOS 7, using the "centos7-fips-katello-nightly" box provided by Forklift.
Likewise, during the normal installation of Pulp on our own development infrastructure for FIPS, `pulp-gen-ca-certificate` returns 0.
If we could run this job again, I suspect it would pass, but I'd like to be sure before I mark the issue closed. It's possible there is something different about the Jenkins environment that causes it to fail.
Comment 11pulp-infra@redhat.com
2018-06-11 17:32:47 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 12pulp-infra@redhat.com
2018-06-11 21:52:23 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 13pulp-infra@redhat.com
2018-06-11 23:07:55 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 14pulp-infra@redhat.com
2018-07-09 15:06:31 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
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/RHSA-2019:1222