<p dir="ltr"><br>
Il 06/Gen/2016 11:27, "Bruno Martins" <<a href="mailto:bruno.martins@rumos.pt">bruno.martins@rumos.pt</a>> ha scritto:<br>
><br>
> Hi everyone,<br>
><br>
> I hope this is the best place to post this question.<br>
><br>
> I was wondering how can one upgrade from CentOS 6.7 to CentOS 7.x using redhat-upgrade-tool-cli in a scenario where you're upgrading an Hyper-V based VM.<br>
><br>
> These are the errors I am getting:<br>
><br>
> [root@apssopenvas /]# /usr/bin/redhat-upgrade-tool-cli --network 7 --instrepo=<a href="http://mirror.centos.org/centos/7/os/x86_64">http://mirror.centos.org/centos/7/os/x86_64</a><br>
> setting up repos...<br>
> Could not retrieve mirrorlist <a href="http://updates.atomicorp.com/channels/mirrorlist/atomic/centos-7.0-x86_64">http://updates.atomicorp.com/channels/mirrorlist/atomic/centos-7.0-x86_64</a> error was<br>
> 14: PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"<br>
> Could not retrieve mirrorlist <a href="http://updates.atomicorp.com/channels/mirrorlist/atomic-testing/centos-7.0-x86_64">http://updates.atomicorp.com/channels/mirrorlist/atomic-testing/centos-7.0-x86_64</a> error was<br>
> 14: PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"<br>
> YumRepo Error: All mirror URLs are not using ftp, http[s] or file.<br>
> Eg. 7.0 is not a valid and current release or hasnt been released yet/<br>
> removing mirrorlist with no valid mirrors: /var/tmp/system-upgrade/base/mirrorlist.txt<br>
> YumRepo Error: All mirror URLs are not using ftp, http[s] or file.<br>
> Eg. 7.0 is not a valid and current release or hasnt been released yet/<br>
> removing mirrorlist with no valid mirrors: /var/tmp/system-upgrade/extras/mirrorlist.txt<br>
> YumRepo Error: All mirror URLs are not using ftp, http[s] or file.<br>
> Eg. 7.0 is not a valid and current release or hasnt been released yet/<br>
> removing mirrorlist with no valid mirrors: /var/tmp/system-upgrade/updates/mirrorlist.txt<br>
> No upgrade available for the following repos: atomic atomic-testing base extras updates<br>
> .treeinfo | 1.1 kB 00:00<br>
> preupgrade-assistant risk check found EXTREME risks for this upgrade.<br>
> Run preupg --riskcheck --verbose to view these risks.<br>
> Continuing with this upgrade is not recommended.<br>
><br>
> And this is the reason for the risk:<br>
><br>
> [root@apssopenvas /]# preupg --riskcheck --verbose<br>
> INPLACERISK: EXTREME: This machine seems to run on a Microsoft hypervisor.<br>
><br>
> Thank you!<br>
><br>
> Cheers,<br>
><br>
> Bruno Martins<br>
> _______________________________________________<br>
> CentOS-devel mailing list<br>
> <a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>
> <a href="https://lists.centos.org/mailman/listinfo/centos-devel">https://lists.centos.org/mailman/listinfo/centos-devel</a></p>
<p dir="ltr">Hello,<br>
I'm not an expert, but did you follow this link?<br>
<a href="https://wiki.centos.org/TipsAndTricks/CentOSUpgradeTool">https://wiki.centos.org/TipsAndTricks/CentOSUpgradeTool</a><br>
Because for CentOS I see that the command name begins with centos and not redhat.<br>
Also, the main error seems related to "not found" and indeed the mirrorlist path with "7.0" doesn't exist.<br>
But it does exist instead the path with<br>
<a href="http://updates.atomicorp.com/channels/mirrorlist/atomic/centos-7-x86_64">http://updates.atomicorp.com/channels/mirrorlist/atomic/centos-7-x86_64</a><br>
Perhaps a "yum clean all" and then follow the tips page could also resolve the repo mismatch problem.<br>
For the hypervisor problem I think it depends on the fact that cpuinfo is that of the hypervisor itself and not a real problem. Just my opinion.<br>
Hih,<br>
Gianluca</p>