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.
DescriptionJessica Richards
2023-04-11 17:49:18 UTC
Description of problem:
The customer runs this command on their Satellite server:
# hammer settings set --id foreman_proxy_content_auto_sync --value false
Then they repeatedly run this string of commands:
# echo; hammer settings list | grep foreman_proxy_content_auto_sync; echo; hammer settings list --search "foreman_proxy_content_auto_sync"; echo; hammer settings info --id foreman_proxy_content_auto_sync
Those commands do not initially all give the same result ("false"), but eventually they all do. The customer doesn't have this problem when updating this value through the web interface.
Version-Release number of selected component (if applicable):
satellite-6.11.3-1.el7sat.noarch
How reproducible:
unclear; i was unable to reproduce this on my own satellite server
Actual results:
It takes time for all of the following commands to give the same result ("false"):
# echo; hammer settings list | grep foreman_proxy_content_auto_sync; echo; hammer settings list --search "foreman_proxy_content_auto_sync"; echo; hammer settings info --id foreman_proxy_content_auto_sync
Expected results:
All of the following commands should give the same result:
# hammer settings list | grep foreman_proxy_content_auto_sync
# hammer settings list --search "foreman_proxy_content_auto_sync"
# hammer settings info --id foreman_proxy_content_auto_sync
Additional info:
Applying performance tuning to this Satellite server hasn't helped.
I couldn't reproduce this when switching the setting from true to false, but I could see it happening when going from false to true.
This seems to have the same root cause as BZ2157869 - Satellite "does not notice" when a setting changes to its default value and applying the fix from the other BZ seems to resolve the issue described here. I'll go ahead and close this one as a duplicate, if you feel the other BZ does not fully cover the issue described here, feel free to reopen.
*** This bug has been marked as a duplicate of bug 2157869 ***
Description of problem: The customer runs this command on their Satellite server: # hammer settings set --id foreman_proxy_content_auto_sync --value false Then they repeatedly run this string of commands: # echo; hammer settings list | grep foreman_proxy_content_auto_sync; echo; hammer settings list --search "foreman_proxy_content_auto_sync"; echo; hammer settings info --id foreman_proxy_content_auto_sync Those commands do not initially all give the same result ("false"), but eventually they all do. The customer doesn't have this problem when updating this value through the web interface. Version-Release number of selected component (if applicable): satellite-6.11.3-1.el7sat.noarch How reproducible: unclear; i was unable to reproduce this on my own satellite server Actual results: It takes time for all of the following commands to give the same result ("false"): # echo; hammer settings list | grep foreman_proxy_content_auto_sync; echo; hammer settings list --search "foreman_proxy_content_auto_sync"; echo; hammer settings info --id foreman_proxy_content_auto_sync Expected results: All of the following commands should give the same result: # hammer settings list | grep foreman_proxy_content_auto_sync # hammer settings list --search "foreman_proxy_content_auto_sync" # hammer settings info --id foreman_proxy_content_auto_sync Additional info: Applying performance tuning to this Satellite server hasn't helped.