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:
Satellite by default configures pulp to have these checksums allowed.
# grep CHECKSUM /etc/pulp/settings.py
ALLOWED_CONTENT_CHECKSUMS = ["md5", "sha1", "sha224", "sha256", "sha384", "sha512"]
One must be able to opt md5 out of it as it's only used as a content_checksum for some older repos but doing so, breaks the satellite-installer completely.
Version-Release number of selected component (if applicable):
Satellite 6.13.1 ( probably 6.12 as well )
How reproducible:
100%
Steps to Reproduce and Actual Results:
-----------
Scenario 1:
-----------
## Break ###
1. Notice the current values of installer options":
# satellite-installer -S satellite --full-help | grep checksum
--foreman-proxy-content-pulpcore-allowed-content-checksums List of checksums to use for pulpcore content operations (current: ["md5", "sha1", "sha224", "sha256", "sha384", "sha512"])
--reset-foreman-proxy-content-pulpcore-allowed-content-checksums Reset pulpcore_allowed_content_checksums to the default value (["sha1", "sha224", "sha256", "sha384", "sha512"])
2. Run "satellite-installer --reset-foreman-proxy-content-pulpcore-allowed-content-checksums" to get rid of md5 from the list.
3. Installer fails on :
~~
2023-07-14 09:32:44 [NOTICE] [configure] 1250 configuration steps out of 1590 steps complete.
2023-07-14 09:33:45 [ERROR ] [configure] 'pulpcore-manager reset-admin-password --random' returned 1 instead of one of [0]
2023-07-14 09:33:45 [ERROR ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]/returns: change from 'notrun' to ['0'] failed: 'pulpcore-manager reset-admin-password --random' returned 1 instead of one of [0]
2023-07-14 09:33:52 [ERROR ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]: Failed to call refresh: 'pulpcore-manager reset-admin-password --random' returned 1 instead of one of [0]
2023-07-14 09:33:52 [ERROR ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]: 'pulpcore-manager reset-admin-password --random' returned 1 instead of one of [0]
~~
4. Reason\Traceback:
~~
2023-07-14 09:33:45 [INFO ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]/returns: raise e
2023-07-14 09:33:45 [INFO ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]/returns: File "/usr/lib/python3.9/site-packages/pulpcore
/app/settings.py", line 428, in <module>
2023-07-14 09:33:45 [INFO ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]/returns: raise ImproperlyConfigured(
2023-07-14 09:33:45 [INFO ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]/returns: django.core.exceptions.ImproperlyConfigured: Ther
e have been identified artifacts with forbidden checksum 'md5'. Run 'pulpcore-manager handle-artifact-checksums' first to unset forbidden checksums.
~~
## Rollback ##
** Either use satellite-installer itself or edit /etc/foreman-installer/scenarios.d/satellite-answers.yaml file and add back "md5" in the list of "pulpcore_allowed_content_checksums"
** Re-run satellite-installer if answer file was modified.
** Result:
* Installer successfully completes.
* We are back to the old value for ALLOWED_CONTENT_CHECKSUMS which includes md5
-----------
Scenario 2:
-----------
## Break ###
A) Repeat Step 1 2 and 3 from Scenario 1.
B) Run
# PULP_SETTINGS=/etc/pulp/settings.py runuser -u pulp -- pulpcore-manager handle-artifact-checksums
C) Re-run satellite-installer and it will fail on the exact same step.
D) Try to revert back i.e. include back md5 but still it fails on the same step.
## Rollback ##
** Once again run handle-artifact-checksums so that whatever was removed in the first run, would be recalculated and added back in the second run w.r.t md5 checksum of content artifacts
# PULP_SETTINGS=/etc/pulp/settings.py runuser -u pulp -- pulpcore-manager handle-artifact-checksums
** Re-run the installer and it will be successfully completed.
Expected results:
* No such issues should happen
* Installer should allow removing md5 from the list of ALLOWED_CONTENT_CHECKSUMS
Additional info:
The end-user is afraid that, on their FIPS-enabled Satellite 6.13, since they cannot remove md5 from the ALLOWED_CONTENT_CHECKSUMS list, That is immediately marking the satellite non-compliant to FIPS-140-2 standards.
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: Satellite by default configures pulp to have these checksums allowed. # grep CHECKSUM /etc/pulp/settings.py ALLOWED_CONTENT_CHECKSUMS = ["md5", "sha1", "sha224", "sha256", "sha384", "sha512"] One must be able to opt md5 out of it as it's only used as a content_checksum for some older repos but doing so, breaks the satellite-installer completely. Version-Release number of selected component (if applicable): Satellite 6.13.1 ( probably 6.12 as well ) How reproducible: 100% Steps to Reproduce and Actual Results: ----------- Scenario 1: ----------- ## Break ### 1. Notice the current values of installer options": # satellite-installer -S satellite --full-help | grep checksum --foreman-proxy-content-pulpcore-allowed-content-checksums List of checksums to use for pulpcore content operations (current: ["md5", "sha1", "sha224", "sha256", "sha384", "sha512"]) --reset-foreman-proxy-content-pulpcore-allowed-content-checksums Reset pulpcore_allowed_content_checksums to the default value (["sha1", "sha224", "sha256", "sha384", "sha512"]) 2. Run "satellite-installer --reset-foreman-proxy-content-pulpcore-allowed-content-checksums" to get rid of md5 from the list. 3. Installer fails on : ~~ 2023-07-14 09:32:44 [NOTICE] [configure] 1250 configuration steps out of 1590 steps complete. 2023-07-14 09:33:45 [ERROR ] [configure] 'pulpcore-manager reset-admin-password --random' returned 1 instead of one of [0] 2023-07-14 09:33:45 [ERROR ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]/returns: change from 'notrun' to ['0'] failed: 'pulpcore-manager reset-admin-password --random' returned 1 instead of one of [0] 2023-07-14 09:33:52 [ERROR ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]: Failed to call refresh: 'pulpcore-manager reset-admin-password --random' returned 1 instead of one of [0] 2023-07-14 09:33:52 [ERROR ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]: 'pulpcore-manager reset-admin-password --random' returned 1 instead of one of [0] ~~ 4. Reason\Traceback: ~~ 2023-07-14 09:33:45 [INFO ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]/returns: raise e 2023-07-14 09:33:45 [INFO ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]/returns: File "/usr/lib/python3.9/site-packages/pulpcore /app/settings.py", line 428, in <module> 2023-07-14 09:33:45 [INFO ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]/returns: raise ImproperlyConfigured( 2023-07-14 09:33:45 [INFO ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[reset-admin-password --random]/Exec[pulpcore-manager reset-admin-password --random]/returns: django.core.exceptions.ImproperlyConfigured: Ther e have been identified artifacts with forbidden checksum 'md5'. Run 'pulpcore-manager handle-artifact-checksums' first to unset forbidden checksums. ~~ ## Rollback ## ** Either use satellite-installer itself or edit /etc/foreman-installer/scenarios.d/satellite-answers.yaml file and add back "md5" in the list of "pulpcore_allowed_content_checksums" ** Re-run satellite-installer if answer file was modified. ** Result: * Installer successfully completes. * We are back to the old value for ALLOWED_CONTENT_CHECKSUMS which includes md5 ----------- Scenario 2: ----------- ## Break ### A) Repeat Step 1 2 and 3 from Scenario 1. B) Run # PULP_SETTINGS=/etc/pulp/settings.py runuser -u pulp -- pulpcore-manager handle-artifact-checksums C) Re-run satellite-installer and it will fail on the exact same step. D) Try to revert back i.e. include back md5 but still it fails on the same step. ## Rollback ## ** Once again run handle-artifact-checksums so that whatever was removed in the first run, would be recalculated and added back in the second run w.r.t md5 checksum of content artifacts # PULP_SETTINGS=/etc/pulp/settings.py runuser -u pulp -- pulpcore-manager handle-artifact-checksums ** Re-run the installer and it will be successfully completed. Expected results: * No such issues should happen * Installer should allow removing md5 from the list of ALLOWED_CONTENT_CHECKSUMS Additional info: The end-user is afraid that, on their FIPS-enabled Satellite 6.13, since they cannot remove md5 from the ALLOWED_CONTENT_CHECKSUMS list, That is immediately marking the satellite non-compliant to FIPS-140-2 standards.