Bug 1716294
Summary: | Could not create host via hammer : Unable to delete PuppetCA certificate | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Nikhil Kathole <nkathole> |
Component: | Hosts | Assignee: | Ewoud Kohl van Wijngaarden <ekohlvan> |
Status: | CLOSED ERRATA | QA Contact: | Nikhil Kathole <nkathole> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.6.0 | CC: | egolov, inecas, jyejare, kgaikwad, pcreech, sghai, sjagtap |
Target Milestone: | 6.6.0 | Keywords: | Regression, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | foreman-proxy-1.22.0-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-22 13:30:45 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: |
Description
Nikhil Kathole
2019-06-03 07:26:25 UTC
The issue is observed while provisioning: - from UI also - on VMWare and GCE Linking a known upstream issue, should be fixed by now (since snap 6) FailedQA Version tested: Satellite 6.6 snap 7 # rpm -qa | grep satellite satellite-maintain-0.0.1-1.el7sat.noarch satellite-installer-6.6.0.11-1.beta.el7sat.noarch satellite-cli-6.6.0-5.beta.el7sat.noarch satellite-common-6.6.0-5.beta.el7sat.noarch satellite-6.6.0-5.beta.el7sat.noarch tfm-rubygem-foreman_theme_satellite-4.0.1.1-1.el7sat.noarch PR linked is not part of satellite snap. I guess we are missing cherry-pick. Upstream bug assigned to ekohlvan Not sure why the automation didn't pick this up and moved it to POST, but upstream it's been fixed in 1.22.0-RC2. VERIFIED version tested: Satellite 6.6.0 snap 9 Successfully created host with hammer. 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:3175 |