-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
None
-
False
-
False
-
-
8
-
1.4 GA, 2023-Q2, 2023-R4
-
Testable
We received a message on Convert2RHEL Development group chat regarding some failures in Convert2RHEL on RHEL 7.9, in special, there is one that needs further investigation when Convert2RHEL is run with satellite support, the problem is-as follow (short description):
Running Convert2RHEL without the repofiles that lives under /etc/yum.repos.d/ and reaching the rollback phase (Whenever a problem happens before the point of no return), the tools seem to be putting back the repofiles in /etc/yum.repos.d/ with the external CDN present in there.
Convert2RHEL should handle better the case where the customer does changes to files owned by packages the tool removes so that when a rollback occurs it applies the customer's changes to the file after reinstalling the removed packages.
Notes
Acceptance Criteria
- before removing packages convert2rhel backs up files of these packages which have been changed by the customer
- we need to make a note when a file has been removed by the customer
- after re-installation of the removed packages during a rollback we either copy back the customer's changed files or we remove files that used to be removed before the conversion (depending on what the customer has done to the package file prior to the conversion)
- is caused by
-
RHELC-877 shim-x64 package conflict during yum transaction validation
- Closed
- is depended on by
-
RHELC-1249 Incomplete rollback: katello package is not removed
- Closed
- links to
-
RHEA-2023:124609 convert2rhel bug fix and enhancement update
-
RHEA-2023:124610 convert2rhel bug fix and enhancement update