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.
Bug 2043724 - Conversion fails due to gnome-documents-libs conflict
Summary: Conversion fails due to gnome-documents-libs conflict
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: convert2rhel
Version: 7.9
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Michal Bocek
QA Contact: Upgrades and Supportability
Miriam Portman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-21 20:29 UTC by Gregg Phillips
Modified: 2023-05-11 10:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-31 13:03:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
SOS report from the affected system. (12.44 MB, application/x-xz)
2022-01-21 20:29 UTC, Gregg Phillips
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OAMG-6411 0 None None None 2022-01-21 20:34:31 UTC
Red Hat Issue Tracker RHELC-67 0 None None None 2023-05-11 10:23:15 UTC
Red Hat Issue Tracker RHELPLAN-109152 0 None None None 2022-01-21 20:34:34 UTC
Red Hat Product Errata RHSA-2022:6268 0 None None None 2022-08-31 13:03:54 UTC

Description Gregg Phillips 2022-01-21 20:29:17 UTC
Created attachment 1852612 [details]
SOS report from the affected system.

Description of problem:

Error when running yum update -y

Version-Release number of selected component (if applicable):


How reproducible:

[root@crotwell ~]# yum update -y
Loaded plugins: fastestmirror, langpacks, product-id, search-disabled-repos,
              : subscription-manager
Loading mirror speeds from cached hostfile
convert2rhel-for-rhel-7-rpms                             | 3.8 kB     00:00     
https://cdn.redhat.com/content/dist/rhel/server/7/%24releasever/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (Red Hat Enterprise Linux 7 Server (RPMs)),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=rhel-7-server-rpms ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable rhel-7-server-rpms
        or
            subscription-manager repos --disable=rhel-7-server-rpms

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=rhel-7-server-rpms.skip_if_unavailable=true

failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more mirrors to try.
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
[root@crotwell ~]# 


Steps to Reproduce:
1.run yum update -y
2.
3.

Actual results:

[root@crotwell ~]# yum update -y
Loaded plugins: fastestmirror, langpacks, product-id, search-disabled-repos,
              : subscription-manager
Loading mirror speeds from cached hostfile
convert2rhel-for-rhel-7-rpms                             | 3.8 kB     00:00     
https://cdn.redhat.com/content/dist/rhel/server/7/%24releasever/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (Red Hat Enterprise Linux 7 Server (RPMs)),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=rhel-7-server-rpms ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable rhel-7-server-rpms
        or
            subscription-manager repos --disable=rhel-7-server-rpms

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=rhel-7-server-rpms.skip_if_unavailable=true

failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more mirrors to try.
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
[root@crotwell ~]# 

Expected results:

Should download any available software updates.

Additional info:

Comment 3 Gregg Phillips 2022-01-21 21:46:23 UTC
I found the following command using a Google Search:

echo 7Server > /etc/yum/vars/releasever

This has fixed the problem above. However I am unsure of the status of the system. Whether it has been completely converted or still has remnants of the old CentOS systems.

Gregg.

Comment 4 Gregg Phillips 2022-01-21 21:51:41 UTC
The following CentOS packages are still showing as being installed on this converted system:

[root@crotwell ~]# rpm -qa | grep centos
kde-settings-ksplash-19-23.12.el7.centos.noarch
abrt-addon-vmcore-2.1.11-60.el7.centos.x86_64
anaconda-gui-21.48.22.159-1.el7.centos.x86_64
PackageKit-glib-1.1.10-2.el7.centos.x86_64
abrt-python-2.1.11-60.el7.centos.x86_64
PackageKit-gstreamer-plugin-1.1.10-2.el7.centos.x86_64
initial-setup-gui-0.3.9.45-1.el7.centos.x86_64
redhat-lsb-submod-security-4.1-27.el7.centos.1.x86_64
abrt-cli-2.1.11-60.el7.centos.x86_64
abrt-desktop-2.1.11-60.el7.centos.x86_64
libreport-gtk-2.1.11-53.el7.centos.x86_64
plymouth-core-libs-0.8.9-0.34.20140113.el7.centos.x86_64
abrt-tui-2.1.11-60.el7.centos.x86_64
plymouth-system-theme-0.8.9-0.34.20140113.el7.centos.x86_64
compat-glibc-headers-2.12-4.el7.centos.x86_64
system-config-date-1.10.6-3.el7.centos.noarch
plymouth-theme-charge-0.8.9-0.34.20140113.el7.centos.x86_64
redhat-lsb-core-4.1-27.el7.centos.1.x86_64
abrt-dbus-2.1.11-60.el7.centos.x86_64
libreport-plugin-reportuploader-2.1.11-53.el7.centos.x86_64
PackageKit-gtk3-module-1.1.10-2.el7.centos.x86_64
libreport-python-2.1.11-53.el7.centos.x86_64
libreport-anaconda-2.1.11-53.el7.centos.x86_64
abrt-libs-2.1.11-60.el7.centos.x86_64
kde-settings-plasma-19-23.12.el7.centos.noarch
abrt-addon-python-2.1.11-60.el7.centos.x86_64
thunderbird-91.4.0-3.el7.centos.x86_64
anaconda-core-21.48.22.159-1.el7.centos.x86_64
plymouth-plugin-label-0.8.9-0.34.20140113.el7.centos.x86_64
libreport-rhel-anaconda-bugzilla-2.1.11-53.el7.centos.x86_64
qt-settings-19-23.12.el7.centos.noarch
PackageKit-1.1.10-2.el7.centos.x86_64
plymouth-0.8.9-0.34.20140113.el7.centos.x86_64
libreport-plugin-ureport-2.1.11-53.el7.centos.x86_64
abrt-addon-xorg-2.1.11-60.el7.centos.x86_64
redhat-rpm-config-9.1.0-88.el7.centos.noarch
yum-3.4.3-168.el7.centos.noarch
abrt-gui-libs-2.1.11-60.el7.centos.x86_64
PackageKit-command-not-found-1.1.10-2.el7.centos.x86_64
anaconda-tui-21.48.22.159-1.el7.centos.x86_64
libreport-web-2.1.11-53.el7.centos.x86_64
kde-settings-19-23.12.el7.centos.noarch
abrt-addon-pstoreoops-2.1.11-60.el7.centos.x86_64
plymouth-graphics-libs-0.8.9-0.34.20140113.el7.centos.x86_64
libreport-plugin-bugzilla-2.1.11-53.el7.centos.x86_64
abrt-console-notification-2.1.11-60.el7.centos.x86_64
initial-setup-0.3.9.45-1.el7.centos.x86_64
libreport-filesystem-2.1.11-53.el7.centos.x86_64
libreport-2.1.11-53.el7.centos.x86_64
basesystem-10.0-7.el7.centos.noarch
compat-glibc-2.12-4.el7.centos.x86_64
abrt-addon-ccpp-2.1.11-60.el7.centos.x86_64
libreport-plugin-rhtsupport-2.1.11-53.el7.centos.x86_64
abrt-gui-2.1.11-60.el7.centos.x86_64
anaconda-widgets-21.48.22.159-1.el7.centos.x86_64
abrt-addon-kerneloops-2.1.11-60.el7.centos.x86_64
kde-settings-pulseaudio-19-23.12.el7.centos.noarch
libreport-plugin-mailx-2.1.11-53.el7.centos.x86_64
plymouth-plugin-two-step-0.8.9-0.34.20140113.el7.centos.x86_64
PackageKit-yum-1.1.10-2.el7.centos.x86_64
plymouth-scripts-0.8.9-0.34.20140113.el7.centos.x86_64
abrt-2.1.11-60.el7.centos.x86_64
libreport-cli-2.1.11-53.el7.centos.x86_64
[root@crotwell ~]# 


Gregg.

Comment 5 Michal Bocek 2022-01-25 21:24:03 UTC
Hi Gregg,

Thank you for filing the issue and I'm sorry for the bad experience - we'll try fixing that in the later versions.


The conversion failed during its last phase. There are two options to finish the conversion:

1. If you have a full system backup, you can revert to the pre-conversion state, remove the gnome-documents-libs package and re-run convert2rhel.

2. If you're unable to revert the system to a pre-conversion state, remove the gnome-documents-libs package and re-run the following command which failed during the conversion:

$ yum distro-sync -y --disablerepo=* --releasever=7Server --enablerepo=rhel-7-server-rpms libreport-filesystem basesystem libodfgen libmwaw libstaroffice liborcus libwps liblangtag libetonyek mythes mythes-en libcmis clucene-contribs-lib highlight libzmf libabw libfreehand libpagemaker libcdr libmspub libvisio redhat-rpm-config compat-glibc-headers compat-glibc yum-plugin-fastestmirror yum libexttextcat lpsolve libreport-python libreport abrt-libs PackageKit-glib libreport-web kde-settings plymouth-core-libs PackageKit-yum PackageKit plymouth-scripts plymouth plymouth-graphics-libs libreport-plugin-rhtsupport libreport-plugin-reportuploader libreport-plugin-bugzilla libreport-cli ptlib opal plymouth-plugin-label plymouth-plugin-two-step plymouth-theme-charge libreport-anaconda libreport-rhel-anaconda-bugzilla qt-settings kde-settings-ksplash kde-settings-plasma libreport-plugin-ureport abrt abrt-dbus abrt-python abrt-addon-kerneloops abrt-addon-pstoreoops abrt-addon-vmcore abrt-addon-python abrt-addon-xorg abrt-tui abrt-retrace-client abrt-addon-ccpp abrt-cli openchange libreport-gtk abrt-gui-libs abrt-gui gnome-documents-libs anaconda-widgets libgepub gstreamer1-plugins-bad-free-gtk evolution-langpacks evolution evolution-mapi-langpacks evolution-mapi system-config-date anaconda-tui anaconda-core anaconda-gui initial-setup unoconv initial-setup-gui ekiga gnome-documents evolution-help abrt-desktop PackageKit-gtk3-module kde-settings-pulseaudio abrt-console-notification plymouth-system-theme PackageKit-gstreamer-plugin PackageKit-command-not-found libreport-plugin-mailx libreoffice-data evolution-ews-langpacks evolution-ews autocorr-en libreoffice-opensymbol-fonts libreoffice-ure-common libreoffice-ure libreoffice-langpack-en libreoffice-gtk3 libreoffice-gtk2 libreoffice-x11 libreoffice-core libreoffice-pyuno libreoffice-writer libreoffice-graphicfilter libreoffice-pdfimport libreoffice-draw libreoffice-emailmerge libreoffice-calc libreoffice-math libreoffice-impress libreofficekit redhat-lsb-submod-security redhat-lsb-core pcsc-lite-doc pcsc-lite-devel vulkan-filesystem vulkan thunderbird

Then check if /etc/yum.conf was manually edited prior to the conversion - do that by running `$ rpm -Vf /etc/yum.conf` and let me know if you see /etc/yum.conf in the output of the command. If so, one additional simple step would be needed.

If the yum command finishes successfully it would conclude the conversion.

Comment 7 Gregg Phillips 2022-01-26 16:49:37 UTC
#2 & 3 seem to have fixed the system. Are there best practices for preparing a system before running the convert2rhel tool?

Thank you for your assistance.

Gregg.

Comment 10 John 2022-07-14 01:07:54 UTC
I just hit this issue last week... conversion bombed out before finishing with:

Transaction check error:
  file /usr/lib64/gnome-documents/girepository-1.0/Gd-1.0.typelib from install of gnome-documents-3.14.3-3.el7.x86_64 conflicts with file from package gnome-documents-libs-3.28.2-2.el7.x86_64
  file /usr/lib64/gnome-documents/girepository-1.0/GdPrivate-1.0.typelib from install of gnome-documents-3.14.3-3.el7.x86_64 conflicts with file from package gnome-documents-libs-3.28.2-2.el7.x86_64
  file /usr/lib64/gnome-documents/libgd.so from install of gnome-documents-3.14.3-3.el7.x86_64 conflicts with file from package gnome-documents-libs-3.28.2-2.el7.x86_64
  file /usr/lib64/gnome-documents/libgdprivate-1.0.so from install of gnome-documents-3.14.3-3.el7.x86_64 conflicts with file from package gnome-documents-libs-3.28.2-2.el7.x86_64
  file /usr/share/glib-2.0/schemas/org.gnome.Documents.enums.xml from install of gnome-documents-3.14.3-3.el7.x86_64 conflicts with file from package gnome-documents-libs-3.28.2-2.el7.x86_64
  file /usr/share/gnome-documents/getting-started/C/gnome-documents-getting-started.pdf from install of gnome-documents-3.14.3-3.el7.x86_64 conflicts with file from package gnome-documents-libs-3.28.2-2.el7.x86_64
  file /usr/share/gnome-documents/gir-1.0/Gd-1.0.gir from install of gnome-documents-3.14.3-3.el7.x86_64 conflicts with file from package gnome-documents-libs-3.28.2-2.el7.x86_64
  file /usr/share/gnome-documents/gir-1.0/GdPrivate-1.0.gir from install of gnome-documents-3.14.3-3.el7.x86_64 conflicts with file from package gnome-documents-libs-3.28.2-2.el7.x86_64

I checked the log and I already removed the gnome-documents rpm, and re-ran the failed command, so my system is OK, although i was unsure until I came here whether I'd missed out on any other small tweaks to finalise the conversion.

Nice to know there isn't really anything left to do after fixing that final failed command.


Anyway, I will just point out, that this bug is now almost 5 months old, and it's still not fixed.
Nor is it documented at the link Michal Bocek proudly posted above.

So once again, Red Hat has failed, dismally, and utterly, to show any respect or care for its customers.

Once again, Red Hat is aware of a bug, which can't be hard to fix, or at least warn the customer of.

And, instead, it gets ignored for 5 months, and customers are left with ruined systems, rushing to rollback snapshots, googling for solutions, wallowing through logfiles to try to identify and fix an error that should already be fixed, and then wasting more time coming to this bugzilla to report the bug, only to find it was reported almost 6 months ago, and Red Hat have done nothing.

Brilliant.
Thanks again, Red Hat.
Great Job.

Comment 11 Eric Gustavsson 2022-07-15 13:58:17 UTC
Hi John

I can assure you we are working on solutions to fix this. We are aiming to have a solution that should mitigate against these kinds of issues within our next v0.27 release. Right now we are prioritizing a more general approach that should tackle all of these kinds of issues in the future rather than tackling this issue separately as we as a team have to prioritize our time.

What benefit does it bring us to ignore bugs that either prevents or complicates converting customers systems over to RHEL? None. As a team we delegate our resources and will have things that are not tackled right away. We have other bugs that are more devastating to customers, or simply more prominent. And other features that would improve the quality of life or make the conversion even less prone to failed conversions

I apologize for the lack of communication regarding the bug. Here is a link to a feature that might help once we finalize it, you can follow its progress here in the Jira issue I linked or by going to the GitHub PR linked within.
https://issues.redhat.com/browse/RHELC-576

If you have any questions regarding Convert2RHEL or other feedback feel free to let me know here or you could create a discussion on GitHub
https://github.com/oamg/convert2rhel/discussions

Best regards,
Eric

Comment 12 John 2022-07-19 00:50:40 UTC
Thanks for the response Eric, 
It' nice to know a better fix is being worked on.

I must just note though, that in the meantime this bug could be prevented from impacting customers with a simple check for the problematic rpm, gnome-documents-libs.
I know there will be other problematic rpms that crop up and cause the same issue,
And, I also know it's also a pain to make small changes to codebase to workaround specific bugs like this, temporarily, especially if those workarounds need to be removed once your improved solution comes through.

But this gnome-documents-libs one seems to be one of the main culprits, so checking for it will save quite a few customers some grief - and would be worth the small effort if the improved fix is going to take some time to come through, which does look to be the case.

Cheers & regards,
John

Comment 13 Eric Gustavsson 2022-07-19 15:24:22 UTC
You're right, in hindsight we should've fixed this issue while working on the generic solution. I'm afraid that we don't have time to create a patch release before the minor release due to time constraints for dev freeze and validation. Our aim for v0.27 should be around the end of August

If our generic solution doesn't make it, we will add the workaround fix for this issue so that either way it is resolved for v0.27

Best regards,
Eric

Comment 14 Eric Gustavsson 2022-08-03 11:57:12 UTC
@rolivier while you're adding to excluded packages, could you add this bug fixed there as well?

Comment 15 Rodolfo Olivieri 2022-08-03 12:29:12 UTC
Hi, @egustavs! Of course. I will take care of that.

Comment 19 Daniel Diblik 2022-08-24 13:13:29 UTC
The bug was tested as a part of automated regression testing on version *convert2rhel-0.26-1.el7.noarch* and *convert2rhel-1.0-1.el7.noarch* with their respective results provided below:


: : : : : : : : : : : : : : : : : : : : {convert2rhel-0.26-1.el7.noarch} : : : : : : : : : : : : : : : : : : : : 


=================================== FAILURES ===================================
__________________________ test_remove_excluded_pkgs ___________________________

...output omitted...

    def test_remove_excluded_pkgs(shell, convert2rhel):
        """
        Ensure Convert2RHEL removes packages, which are specified as excluded_pkgs in config.
        Verification scenarios cover just some packages causing major issues.
        Those are specified in their respective test plan (remove_excluded_pkgs_epel7 and remove_excluded_pkgs_epel8).
        Packages are set as an environment variable.
        """
        packages = os.environ["PACKAGES"]
        assert (
            shell(
                f"yum install -y {packages}",
            ).returncode
            == 0
        )
    
        # run utility until the reboot
        with convert2rhel(
            ("-y --no-rpm-va --serverurl {} --username {} --password {} --pool {} --debug").format(
                env.str("RHSM_SERVER_URL"),
                env.str("RHSM_USERNAME"),
                env.str("RHSM_PASSWORD"),
                env.str("RHSM_POOL"),
            )
        ) as c2r:
            pass
>       assert c2r.exitstatus == 0
E       assert 1 == 0
E         +1
E         -0

tests/integration/tier1/remove-excld-pkgs/test_remove_excld_pkgs.py:31: AssertionError

...output omitted...

=========================== short test summary info ============================
FAILED tests/integration/tier1/remove-excld-pkgs/test_remove_excld_pkgs.py::test_remove_excluded_pkgs
=================== 1 failed, 1 warning in 89.78s (0:01:29) ====================


: : : : : : : : : : : : : : : : : : : : {convert2rhel-1.0-1.el7.noarch} : : : : : : : : : : : : : : : : : : : : 

... output omitted ...

out: Executing a command:
out: rpm -qi gnome-documents-libs
out: 
out: 
out: package gnome-documents-libs is not installed
out: PASSED
out: 
... output omitted ...
out: =================== 1 passed, 1 warning in 594.35s (0:09:54) ===================

Comment 21 errata-xmlrpc 2022-08-31 13:03:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: convert2rhel security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:6268


Note You need to log in before you can comment on or make changes to this bug.