Bug 2087067
Summary: | Re-enabling puppet fails when it was disabled with -f option before | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Vladimír Sedmík <vsedmik> |
Component: | Puppet | Assignee: | Sayan Das <saydas> |
Status: | NEW --- | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
Severity: | medium | Docs Contact: | Zuzana Lena Ansorgova <zuansorg> |
Priority: | medium | ||
Version: | 6.11.0 | CC: | ahumbe, bangelic, dhjoshi, ehelms, gpathan, gsigrisi, ldelouw, lstejska, nalfassi, rlavi, saydas, zuansorg |
Target Milestone: | Unspecified | Keywords: | Reopened, Triaged, WorkAround |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
.Disabled Puppet with all data removed cannot be re-enabled
If the Puppet plug-in was disabled with the `-f, --remove-all-data` argument and you attempt to enable it again, Satellite maintain fails.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-11-21 13:07:15 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
Vladimír Sedmík
2022-05-17 08:55:52 UTC
*** Bug 2123439 has been marked as a duplicate of this bug. *** Added fully-reviewed RN. Connecting Redmine issue: Bug #36942: Unable to enable back puppet plugin again after completely purging the puppet plugin and related stuff - Foreman https://projects.theforeman.org/issues/36942 Fixes #36942 - Improve the puppet plugin cleanup by sayan3296 · Pull Request #9918 · theforeman/foreman https://github.com/theforeman/foreman/pull/9918 Hi, I suggest to remove the issue from 6.15. There hasn't been done any work from the engineering side, and since we have only two snaps before the freeze there is little to no chance of fixing it in time. If we want to fix it in 6.16, we should align it with the scope and make the prioritization accordingly. |