Description of problem:
I just did an update to 2.4.0-1 from 2.3.1-1. I noticed that I got a .rpmnew file for consumer.conf, but I did not get one for admin.conf. The new admin.conf clobbered the existing one.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Upgrade from 2.3.1 to 2.4.0
Observe that your admin.conf customizations were clobbered.
There should have been an admin.conf.rpmnew created.
This is most likely due to re-packaging of the package. We just need to confirm that and then close it.
Confirmed above comment#1. Moving it to docs bug so that we can add a quick note about it in 2.4 release notes.
We are rebasing pulp-2.4.1, and so all of these bugs can no longer be considered MODIFIED. We will need to recheck them against the rebased build to make sure the cherry picking strategy did not introduce any regressions.
We are rebasing pulp-2.4.1, and so all of these bugs can no longer be considered ON_QA. We will need to recheck them against the rebased build to make sure the cherry picking strategy did not introduce any regressions.
This is actually already fixed in Read the Docs. Preethi, can you verify that the warning about admin.conf is published to QE this one?
This is fixed in Pulp-2.4.1-1.