Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
DescriptionSergei Petrosian
2022-02-16 08:53:45 UTC
Description of problem:
A common user scenario is to be able to reset configuration to the defaults.
When running `postconf -d` to receive default values, `postconf` prints upstream defaults. However, in RHEL, some defaults settings are different from the upstream defaults. Hence, it is impossible to get the real default settings for some parameters.
The fault defaults can be found by running `postconf -n` that prints settings that are different from the defaults.
Version-Release number of selected component (if applicable):
postfix-3.5.8-2.el8.x86_64.rpm
How reproducible:
Always
Steps to Reproduce:
1. Install postfix
2. Enter `postconf -d` to find the default settings
3. Enter `postconf` to find the current settings
Actual results:
Some values at the output of `postconf -d` and `postconf` are different.
Expected results:
The outputs of `postconf -d` and `postconf` must be the same because we have just installed the package and did not change any settings.
Additional info:
The script that compares outputs of two commands and prints settings that are different:
~~~
#!/bin/bash
settings_to_apply=__postconf_settings_to_apply.txt
current_settings=__postconf_current.txt
default_settings=__postconf_defaults.txt
postconf > $current_settings
postconf -d > $default_settings
while read line; do
if ! grep -Fxq "$line" $current_settings; then
echo $line >> $settings_to_apply
fi
done < $default_settings
cat $settings_to_apply
~~~
I think that the settings are rewritten in the spec file here but I might be wrong:
https://src.osci.redhat.com/rpms/postfix/blob/rhel-9.0.0/f/postfix.spec#_356
Comment 1Jaroslav Škarvada
2022-02-16 16:44:57 UTC
Yes, this is problem and currently I am unsure how to solve it the best way. RHEL defaults differ a bit from the upstream defaults. The 'postconf -d' shows upstream defaults. But there is no option to show RHEL defaults. We could a) patch 'postconf -d' to show the RHEL defaults but then there will be no way how to get the upstream defaults (i.e. 'postconf -d' behavior will differ from the upstream). Or b) we could propose new postconf option to show the RHEL defaults, then the postconf behavior will differ from the upstream. Or c) we could provide new tool to show just the RHEL defaults. Or d) update the RHEL defaults to be the same as the upstream defaults. Unfortunately, d) probably isn't currently possible, because we need some hardening.
How about providing a new file `/etc/postconf/main.cf.distribution.defaults` that is a copy of the distribution default `main.cf`?
This can be done within the spec file.
Comment 4RHEL Program Management
2023-08-16 07:28:34 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Description of problem: A common user scenario is to be able to reset configuration to the defaults. When running `postconf -d` to receive default values, `postconf` prints upstream defaults. However, in RHEL, some defaults settings are different from the upstream defaults. Hence, it is impossible to get the real default settings for some parameters. The fault defaults can be found by running `postconf -n` that prints settings that are different from the defaults. Version-Release number of selected component (if applicable): postfix-3.5.8-2.el8.x86_64.rpm How reproducible: Always Steps to Reproduce: 1. Install postfix 2. Enter `postconf -d` to find the default settings 3. Enter `postconf` to find the current settings Actual results: Some values at the output of `postconf -d` and `postconf` are different. Expected results: The outputs of `postconf -d` and `postconf` must be the same because we have just installed the package and did not change any settings. Additional info: The script that compares outputs of two commands and prints settings that are different: ~~~ #!/bin/bash settings_to_apply=__postconf_settings_to_apply.txt current_settings=__postconf_current.txt default_settings=__postconf_defaults.txt postconf > $current_settings postconf -d > $default_settings while read line; do if ! grep -Fxq "$line" $current_settings; then echo $line >> $settings_to_apply fi done < $default_settings cat $settings_to_apply ~~~ I think that the settings are rewritten in the spec file here but I might be wrong: https://src.osci.redhat.com/rpms/postfix/blob/rhel-9.0.0/f/postfix.spec#_356