Unable to update self hosted Engine due to missing mirrors
Hi together, I already checked the other Threads here :) I know that there was an issue with old CentOS 8 repos. Currently Im trying so update our self hosted engine as always but I get the following error: Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': Cannot prepare internal mirrorlist: No URLs in mirrorlist Is there any "official" advise what I have to change in my repo lists? I don't want to break something. Thank you very much :)
Hi Jonas, I would like to say that I also have a 4.4 HE (4.4.5.11-1) that I am trying to upgrade to the latest one, and have this issue. I read through https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D3FEXQ5KOLN3SST... https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4EBNIFJ3ANERON4... but did not manage to get out of the issue. I tried: - yum remove ovirt-release44 - Download and install manually (rpm -i) https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm After this I have regained a functional package manager on the engine. However trying to go further in the update procedure (https://ovirt.org/documentation/upgrade_guide/#Updating_a_self-hosted_engine...) running engine-upgrade-check fails with
OK: Downloaded CentOS Linux 8 - AppStream FAIL: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist
So I am stuck in wait of a comment from someone more knowledgeable too!
On Tue, Feb 15, 2022 at 6:48 PM Gianluca Merlo <gianluca.merlo@gmail.com> wrote:
Hi Jonas,
I would like to say that I also have a 4.4 HE (4.4.5.11-1) that I am trying to upgrade to the latest one, and have this issue. I read through
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D3FEXQ5KOLN3SST... https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4EBNIFJ3ANERON4...
but did not manage to get out of the issue. I tried:
- yum remove ovirt-release44 - Download and install manually (rpm -i) https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
After this I have regained a functional package manager on the engine. However trying to go further in the update procedure (https://ovirt.org/documentation/upgrade_guide/#Updating_a_self-hosted_engine...) running
engine-upgrade-check
fails with
OK: Downloaded CentOS Linux 8 - AppStream FAIL: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist
So I am stuck in wait of a comment from someone more knowledgeable too!
Did you upgrade the machine to CentOS Stream? CentOS Linux archives are gone. Good luck and best regards, -- Didi
Il giorno mer 16 feb 2022 alle ore 10:22 Yedidyah Bar David <didi@redhat.com> ha scritto:
On Tue, Feb 15, 2022 at 6:48 PM Gianluca Merlo <gianluca.merlo@gmail.com> wrote:
Hi Jonas,
I would like to say that I also have a 4.4 HE (4.4.5.11-1) that I am
trying to upgrade to the latest one, and have this issue. I read through
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D3FEXQ5KOLN3SST...
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4EBNIFJ3ANERON4...
but did not manage to get out of the issue. I tried:
- yum remove ovirt-release44 - Download and install manually (rpm -i)
https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
After this I have regained a functional package manager on the engine.
However trying to go further in the update procedure ( https://ovirt.org/documentation/upgrade_guide/#Updating_a_self-hosted_engine...) running
engine-upgrade-check
fails with
OK: Downloaded CentOS Linux 8 - AppStream FAIL: Failed to download metadata for repo 'appstream': Cannot prepare
Error: Failed to download metadata for repo 'appstream': Cannot
internal mirrorlist: No URLs in mirrorlist prepare internal mirrorlist: No URLs in mirrorlist
So I am stuck in wait of a comment from someone more knowledgeable too!
Did you upgrade the machine to CentOS Stream? CentOS Linux archives are gone.
No, I did not do anything apart from trying to fix sources set up from ovirt-release44. May I ask if you could share some guidance on the process? I can see that various third parties provide their "guide" on how to perform the migration, the most "neutral" one I could find is https://unix.stackexchange.com/questions/552873/how-to-switch-from-centos-8-... but I am having a hard time finding any "official" documentation from CentOS or oVirt. May I also ask if this is the way to do it on Hosted Engine (not standalone) deployments, or may it be that there are easier ways to accomplish this in this scenario (e.g. redeployment from newer image)? It would be nice to know if there is any documentation I missed on how to best handle the Centos 8 -> Centos 8 Stream conversion in my case (which is hosted engine on ovirt-node hosts).
Good luck and best regards, -- Didi
Thank you and everyone in advance for your help.
On Wed, Feb 16, 2022 at 2:09 PM Gianluca Merlo <gianluca.merlo@gmail.com> wrote:
Il giorno mer 16 feb 2022 alle ore 10:22 Yedidyah Bar David <didi@redhat.com> ha scritto:
On Tue, Feb 15, 2022 at 6:48 PM Gianluca Merlo <gianluca.merlo@gmail.com> wrote:
Hi Jonas,
I would like to say that I also have a 4.4 HE (4.4.5.11-1) that I am trying to upgrade to the latest one, and have this issue. I read through
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D3FEXQ5KOLN3SST... https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4EBNIFJ3ANERON4...
but did not manage to get out of the issue. I tried:
- yum remove ovirt-release44 - Download and install manually (rpm -i) https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
After this I have regained a functional package manager on the engine. However trying to go further in the update procedure (https://ovirt.org/documentation/upgrade_guide/#Updating_a_self-hosted_engine...) running
engine-upgrade-check
fails with
OK: Downloaded CentOS Linux 8 - AppStream FAIL: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist
So I am stuck in wait of a comment from someone more knowledgeable too!
Did you upgrade the machine to CentOS Stream? CentOS Linux archives are gone.
No, I did not do anything apart from trying to fix sources set up from ovirt-release44. May I ask if you could share some guidance on the process?
Sorry, I only did this on very few development machines, so do not have any significant "real life experience" to share.
I can see that various third parties provide their "guide" on how to perform the migration, the most "neutral" one I could find is
https://unix.stackexchange.com/questions/552873/how-to-switch-from-centos-8-...
but I am having a hard time finding any "official" documentation from CentOS
I think the "official" doc is: https://www.centos.org/centos-stream/ -> Press "8" -> check "Converting from CentOS Linux 8 to CentOS Stream 8" This is very similar to, and slightly more specific/safe, than: https://centos.org/distro-faq/#q7-how-do-i-migrate-my-centos-linux-8-install... The stackexchange answer above is also slightly more detailed than both of these, based on a specific user's experience. I definitely recommend trying first on test machines, as similar as possible to your production ones.
or oVirt.
You are right - there are no oVirt-specific migration procedures I am aware of.
May I also ask if this is the way to do it on Hosted Engine (not standalone) deployments, or may it be that there are easier ways to accomplish this in this scenario (e.g. redeployment from newer image)?
There is a way, which is to follow the general hosted-engine backup/restore procedure. This isn't an in-place upgrade - requires a new storage space for the hosted-engine domain, etc. The appliance that the oVirt project releases is based on Stream since 4.4.6 IIRC. Same for ovirt-node - so if you use node, the normal upgrade process for it will get you Stream.
It would be nice to know if there is any documentation I missed on how to best handle the Centos 8 -> Centos 8 Stream conversion in my case (which is hosted engine on ovirt-node hosts).
See above. I don't think you'll find anything more specific or official. I recommend searching this list's archive - we had several relevant threads over the last year - and testing on copies/clones of your existing ones, if in production. Again good luck, best regards, -- Didi
Il giorno mer 16 feb 2022 alle ore 13:33 Yedidyah Bar David <didi@redhat.com> ha scritto:
On Wed, Feb 16, 2022 at 2:09 PM Gianluca Merlo <gianluca.merlo@gmail.com> wrote:
Il giorno mer 16 feb 2022 alle ore 10:22 Yedidyah Bar David <
On Tue, Feb 15, 2022 at 6:48 PM Gianluca Merlo <
gianluca.merlo@gmail.com> wrote:
Hi Jonas,
I would like to say that I also have a 4.4 HE (4.4.5.11-1) that I am
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D3FEXQ5KOLN3SST...
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4EBNIFJ3ANERON4...
but did not manage to get out of the issue. I tried:
- yum remove ovirt-release44 - Download and install manually (rpm -i)
https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
After this I have regained a functional package manager on the
engine. However trying to go further in the update procedure ( https://ovirt.org/documentation/upgrade_guide/#Updating_a_self-hosted_engine...) running
engine-upgrade-check
fails with
OK: Downloaded CentOS Linux 8 - AppStream FAIL: Failed to download metadata for repo 'appstream': Cannot
Error: Failed to download metadata for repo 'appstream': Cannot
didi@redhat.com> ha scritto: trying to upgrade to the latest one, and have this issue. I read through prepare internal mirrorlist: No URLs in mirrorlist prepare internal mirrorlist: No URLs in mirrorlist
So I am stuck in wait of a comment from someone more knowledgeable
too!
Did you upgrade the machine to CentOS Stream? CentOS Linux archives are gone.
No, I did not do anything apart from trying to fix sources set up from ovirt-release44. May I ask if you could share some guidance on the process?
Sorry, I only did this on very few development machines, so do not have any significant "real life experience" to share.
I can see that various third parties provide their "guide" on how to perform the migration, the most "neutral" one I could find is
https://unix.stackexchange.com/questions/552873/how-to-switch-from-centos-8-...
but I am having a hard time finding any "official" documentation from
CentOS
I think the "official" doc is:
https://www.centos.org/centos-stream/ -> Press "8" -> check "Converting from CentOS Linux 8 to CentOS Stream 8"
I completely missed that and it was in plain view! It is brief, but gives weight to other procedures online! Thank you.
This is very similar to, and slightly more specific/safe, than:
https://centos.org/distro-faq/#q7-how-do-i-migrate-my-centos-linux-8-install...
The stackexchange answer above is also slightly more detailed than both of these, based on a specific user's experience.
I definitely recommend trying first on test machines, as similar as possible to your production ones.
Fortunately it is not strictly a production environment, I am not in a hurry and can afford some downtime, but I cannot afford total loss. I will consider if it is possible to spin up a 4.4.5 setup, but I had some bad luck in the past with a similar scenario (testing an upgrade of things that were no longer in the mirrors) that makes me skeptical about the feasibility of the test.
or oVirt.
You are right - there are no oVirt-specific migration procedures I am aware of.
May I also ask if this is the way to do it on Hosted Engine (not standalone) deployments, or may it be that there are easier ways to accomplish this in this scenario (e.g. redeployment from newer image)?
There is a way, which is to follow the general hosted-engine backup/restore procedure. This isn't an in-place upgrade - requires a new storage space for the hosted-engine domain, etc.
The appliance that the oVirt project releases is based on Stream since 4.4.6 IIRC. Same for ovirt-node - so if you use node, the normal upgrade process for it will get you Stream.
It would be nice to know if there is any documentation I missed on how to best handle the Centos 8 -> Centos 8 Stream conversion in my case (which is hosted engine on ovirt-node hosts).
See above. I don't think you'll find anything more specific or official. I recommend searching this list's archive - we had several relevant threads over the last year - and testing on copies/clones of your existing ones, if in production.
Thanks again. I am currently conflicted about choosing one of the following two options 1. Manually update the engine in-place to CentOS stream then follow the standard ovirt-node update procedure for hosts. The engine could be kind of a snowflake after this I assume, but unless a catastrophe happens I assume I should be able to eventually redeploy it from scratch from a backup down the line if anything goes wrong, once I update nodes (and thus the engine appliance image). This procedure seems easy, the risk comes from something unforeseen happening in the CentOS stream upgrade. 2. Update nodes first, then take advantage of the updated engine appliance image to do a redeployment of the engine from a backup. This seems safer than the latter, but I am also doubtful about the possibility of restoring a 4.4.5 backup on a newer version of the engine, which may break the deal. Also, I am not sure if updating hosts before the engine is a supported path. I think I will review backup/restore procedures just in case, reflect a bit and wait if someone from the community or the development team has suggestions on these (or alternative) procedures, just to have further confirmation.
Again good luck, best regards, -- Didi
On Wed, Feb 16, 2022 at 5:08 PM Gianluca Merlo <gianluca.merlo@gmail.com> wrote:
Il giorno mer 16 feb 2022 alle ore 13:33 Yedidyah Bar David <didi@redhat.com> ha scritto:
On Wed, Feb 16, 2022 at 2:09 PM Gianluca Merlo <gianluca.merlo@gmail.com> wrote:
Il giorno mer 16 feb 2022 alle ore 10:22 Yedidyah Bar David <didi@redhat.com> ha scritto:
On Tue, Feb 15, 2022 at 6:48 PM Gianluca Merlo <gianluca.merlo@gmail.com> wrote:
Hi Jonas,
I would like to say that I also have a 4.4 HE (4.4.5.11-1) that I am trying to upgrade to the latest one, and have this issue. I read through
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D3FEXQ5KOLN3SST... https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4EBNIFJ3ANERON4...
but did not manage to get out of the issue. I tried:
- yum remove ovirt-release44 - Download and install manually (rpm -i) https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
After this I have regained a functional package manager on the engine. However trying to go further in the update procedure (https://ovirt.org/documentation/upgrade_guide/#Updating_a_self-hosted_engine...) running
engine-upgrade-check
fails with
OK: Downloaded CentOS Linux 8 - AppStream FAIL: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist
So I am stuck in wait of a comment from someone more knowledgeable too!
Did you upgrade the machine to CentOS Stream? CentOS Linux archives are gone.
No, I did not do anything apart from trying to fix sources set up from ovirt-release44. May I ask if you could share some guidance on the process?
Sorry, I only did this on very few development machines, so do not have any significant "real life experience" to share.
I can see that various third parties provide their "guide" on how to perform the migration, the most "neutral" one I could find is
https://unix.stackexchange.com/questions/552873/how-to-switch-from-centos-8-...
but I am having a hard time finding any "official" documentation from CentOS
I think the "official" doc is:
https://www.centos.org/centos-stream/ -> Press "8" -> check "Converting from CentOS Linux 8 to CentOS Stream 8"
I completely missed that and it was in plain view! It is brief, but gives weight to other procedures online! Thank you.
I admit I missed it too on first glance. Not sure why... But I was certain it should be there so looked harder :-).
This is very similar to, and slightly more specific/safe, than:
https://centos.org/distro-faq/#q7-how-do-i-migrate-my-centos-linux-8-install...
The stackexchange answer above is also slightly more detailed than both of these, based on a specific user's experience.
I definitely recommend trying first on test machines, as similar as possible to your production ones.
Fortunately it is not strictly a production environment, I am not in a hurry and can afford some downtime, but I cannot afford total loss. I will consider if it is possible to spin up a 4.4.5 setup, but I had some bad luck in the past with a similar scenario (testing an upgrade of things that were no longer in the mirrors)
Perhaps you remember more details? Rollback, inside engine-setup, in case it ran into some problem, indeed relies on having the currently-installed version available for reinstall. Generally speaking, when we release new versions, we keep old ones in-place. This might not be enough, though, depending on external dependencies availability etc.
that makes me skeptical about the feasibility of the test.
Understood.
or oVirt.
You are right - there are no oVirt-specific migration procedures I am aware of.
May I also ask if this is the way to do it on Hosted Engine (not standalone) deployments, or may it be that there are easier ways to accomplish this in this scenario (e.g. redeployment from newer image)?
There is a way, which is to follow the general hosted-engine backup/restore procedure. This isn't an in-place upgrade - requires a new storage space for the hosted-engine domain, etc.
The appliance that the oVirt project releases is based on Stream since 4.4.6 IIRC. Same for ovirt-node - so if you use node, the normal upgrade process for it will get you Stream.
It would be nice to know if there is any documentation I missed on how to best handle the Centos 8 -> Centos 8 Stream conversion in my case (which is hosted engine on ovirt-node hosts).
See above. I don't think you'll find anything more specific or official. I recommend searching this list's archive - we had several relevant threads over the last year - and testing on copies/clones of your existing ones, if in production.
Thanks again. I am currently conflicted about choosing one of the following two options
Manually update the engine in-place to CentOS stream then follow the standard ovirt-node update procedure for hosts. The engine could be kind of a snowflake after this I assume, but unless a catastrophe happens I assume I should be able to eventually redeploy it from scratch from a backup down the line if anything goes wrong, once I update nodes (and thus the engine appliance image). This procedure seems easy, the risk comes from something unforeseen happening in the CentOS stream upgrade. Update nodes first, then take advantage of the updated engine appliance image to do a redeployment of the engine from a backup. This seems safer than the latter, but I am also doubtful about the possibility of restoring a 4.4.5 backup on a newer version of the engine, which may break the deal.
This should work, although we by no means test upgrade from/to each and every possible combination. Should be easy to test on a separate test machine, though - just install current engine and restore from a backup with engine-backup. Make sure this test machine does not have access to your hosts, so that it does not accidentally start trying to manage them.
Also, I am not sure if updating hosts before the engine is a supported path.
Not sure it's officially supported, but should generally work, if the versions are not too far apart.
I think I will review backup/restore procedures just in case, reflect a bit and wait if someone from the community or the development team has suggestions on these (or alternative) procedures, just to have further confirmation.
Good luck and best regards, -- Didi
Yes the machine is running under CentOS Stream. This is my repo list. Any ideas? #yum repolist repo id repo name appstream CentOS Stream 8 - AppStream baseos CentOS Stream 8 - BaseOS extras CentOS Stream 8 - Extras ovirt-4.4 Latest oVirt 4.4 Release ovirt-4.4-centos-ceph-pacific Ceph packages for x86_64 ovirt-4.4-centos-gluster8 CentOS-8 - Gluster 8 ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd ovirt-4.4-centos-stream-advanced-virtualization Advanced Virtualization CentOS Stream packages for x86_64 ovirt-4.4-centos-stream-nfv-openvswitch CentOS-8 - NFV OpenvSwitch ovirt-4.4-centos-stream-ovirt44 CentOS-8 Stream - oVirt 4.4 ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sac ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzo ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64 ovirt-4.4-openstack-victoria OpenStack Victoria Repository ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL powertools CentOS Stream 8 - PowerTools
Hi, I wanted to update my oVirt Engine Host and Hosts servers this morning, but I encouter the same error : engine-upgrade-check or dnf update : FAIL: Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': Cannot prepare internal mirrorlist: No URLs in mirrorlist The Engine and the Hosts are running Centos Stream with oVirt 4.4.9.
The same issue for me, on engine and ovirt-node hosts Le 21/02/2022 à 13:37, yannick.barone@carandache.com a écrit :
Hi,
I wanted to update my oVirt Engine Host and Hosts servers this morning, but I encouter the same error :
engine-upgrade-check or dnf update :
FAIL: Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': Cannot prepare internal mirrorlist: No URLs in mirrorlist
The Engine and the Hosts are running Centos Stream with oVirt 4.4.9. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/YJLQSYSAUZULKZ...
-- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr
On Mon, Feb 21, 2022 at 4:58 PM Nathanaël Blanchet <blanchet@abes.fr> wrote:
The same issue for me, on engine and ovirt-node hosts
Le 21/02/2022 à 13:37, yannick.barone@carandache.com a écrit :
Hi,
I wanted to update my oVirt Engine Host and Hosts servers this morning, but I encouter the same error :
engine-upgrade-check or dnf update :
FAIL: Failed to download metadata for repo 'ovirt-4.4-centos-gluster8': Cannot prepare internal mirrorlist: No URLs in mirrorlist
The Engine and the Hosts are running Centos Stream with oVirt 4.4.9.
Please try first: sudo dnf reinstall --disablerepo='*' https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm Thanks and best regards, -- Didi
Please find below the result : # dnf reinstall --disablerepo='*' https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm ovirt-release44.rpm 48 kB/s | 21 kB 00:00 Package ovirt-release44-4.4.10.1-1.el8.noarch not installed, cannot reinstall it. No match for argument: /var/cache/dnf/commandline-a76fe31ae310b0c7/packages/ovirt-release44.rpm Error: No packages marked for reinstall.
In fact, the repo is (for any reason) not installed at all, so simply do: sudo dnf install --disablerepo='*' https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm Le 21/02/2022 à 16:39, Yannick Barone a écrit :
Please find below the result :
# dnf reinstall --disablerepo='*' https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm ovirt-release44.rpm 48 kB/s | 21 kB 00:00 Package ovirt-release44-4.4.10.1-1.el8.noarch not installed, cannot reinstall it. No match for argument: /var/cache/dnf/commandline-a76fe31ae310b0c7/packages/ovirt-release44.rpm Error: No packages marked for reinstall. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5C32SPWQ6DNL7M...
-- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr
Le 21/02/2022 à 16:28, Yedidyah Bar David a écrit :
sudo dnf reinstall --disablerepo='*' https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
It partially solves the issue: Error: Problem: package ansible-runner-service-1.0.7-1.el8.noarch requires ansible, but none of the providers can be installed - package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64 - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch It seems that 4.4.10 upgrades ansible from 2.9 branch to 2.12.... -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr
Yes Engine check was ok, but running a dnf update give this error too : ]# dnf update Last metadata expiration check: 0:03:50 ago on Mon 21 Feb 2022 04:42:08 PM CET. Error: Problem: package ansible-runner-service-1.0.7-1.el8.noarch requires ansible, but none of the providers can be installed - package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64 - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.17-1.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.18-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.20-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.21-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.23-2.el8.noarch - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.24-2.el8.noarch - cannot install the best update candidate for package ansible-runner-service-1.0.7-1.el8.noarch - cannot install the best update candidate for package ansible-2.9.27-2.el8.noarch - package ansible-2.9.20-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.16-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.19-1.el8.noarch is filtered out by exclude filtering - package ansible-2.9.23-1.el8.noarch is filtered out by exclude filtering - package ansible-1:2.9.27-4.el8.noarch is filtered out by exclude filtering (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Ansible is now being shipped as part of appstream in rhel8.6/centos stream repos. Not sure how this will be solved for ovirt/rhv :) But the most likely answer for a workaround is you need to exclude ansible-core in appstream repository. Or via cli something along the lines of "dnf update -x ansible-core" Greetings Klaas On 2/21/22 16:43, Nathanaël Blanchet wrote:
Le 21/02/2022 à 16:28, Yedidyah Bar David a écrit :
sudo dnf reinstall --disablerepo='*' https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
It partially solves the issue:
Error: Problem: package ansible-runner-service-1.0.7-1.el8.noarch requires ansible, but none of the providers can be installed - package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64 - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch
It seems that 4.4.10 upgrades ansible from 2.9 branch to 2.12....
Le 21/02/2022 à 17:15, Klaas Demter a écrit :
Ansible is now being shipped as part of appstream in rhel8.6/centos stream repos. Not sure how this will be solved for ovirt/rhv :) But the most likely answer for a workaround is you need to exclude ansible-core in appstream repository. Or via cli something along the lines of "dnf update -x ansible-core" Thank you, it is ok now but... we are faced to the first side effects of an upstream distribution that continuously ships newer packages and finally breaks dependencies (at least repos) into a stable ovirt realease.
Greetings
Klaas
On 2/21/22 16:43, Nathanaël Blanchet wrote:
Le 21/02/2022 à 16:28, Yedidyah Bar David a écrit :
sudo dnf reinstall --disablerepo='*' https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
It partially solves the issue:
Error: Problem: package ansible-runner-service-1.0.7-1.el8.noarch requires ansible, but none of the providers can be installed - package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64 - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch
It seems that 4.4.10 upgrades ansible from 2.9 branch to 2.12....
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OANKECW6C4SM6U...
-- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr
Le 21/02/2022 à 17:15, Klaas Demter a écrit : Thank you, it is ok now but... we are faced to the first side effects of an upstream distribution that continuously ships newer packages and finally breaks dependencies (at least repos) into a stable ovirt realease.
which is the effect I was (so pessimistically) pointing to with regards to oVirt's future. And I'd say the repos are the least of your worries, it's the unavoidable code gaps in a fully agile multiverse that I'm more sceptical about. It's fully [up]stream or nothing, unless someone outside IBM/Redhat takes that fully into their hands.
OK, I had to install the rpm instead of reinstall it : # dnf install --disablerepo='*' https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm ovirt-release44.rpm 48 kB/s | 21 kB 00:00 Dependencies resolved. ================================================================================================================================================================================================================== Package Architecture Version Repository Size ================================================================================================================================================================================================================== Upgrading: ovirt-release44 noarch 4.4.10.1-1.el8 @commandline 21 k Transaction Summary ================================================================================================================================================================================================================== Upgrade 1 Package Total size: 21 k Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Upgrading : ovirt-release44-4.4.10.1-1.el8.noarch 1/2 Running scriptlet: ovirt-release44-4.4.10.1-1.el8.noarch 1/2 Cleanup : ovirt-release44-4.4.9.3-1.el8.noarch 2/2 Verifying : ovirt-release44-4.4.10.1-1.el8.noarch 1/2 Verifying : ovirt-release44-4.4.9.3-1.el8.noarch 2/2 Upgraded: ovirt-release44-4.4.10.1-1.el8.noarch Complete! It seems to be ok noww, thanks.
participants (8)
-
Gianluca Merlo -
jonas＠fleckmail.de -
Klaas Demter -
Nathanaël Blanchet -
Thomas Hoberg -
Yannick Barone -
yannick.barone＠carandache.com
-
Yedidyah Bar David