[CentOS-devel] CentOS Upgrade Tool

Hi everyone,

I hope this is the best place to post this question.

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.

These are the errors I am getting:

[root at apssopenvas /]# /usr/bin/redhat-upgrade-tool-cli --network 7 --instrepo=http://mirror.centos.org/centos/7/os/x86_64
setting up repos...
Could not retrieve mirrorlist http://updates.atomicorp.com/channels/mirrorlist/atomic/centos-7.0-x86_64 error was
14: PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Could not retrieve mirrorlist http://updates.atomicorp.com/channels/mirrorlist/atomic-testing/centos-7.0-x86_64 error was
14: PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
YumRepo Error: All mirror URLs are not using ftp, http[s] or file.
 Eg. 7.0 is not a valid and current release or hasnt been released yet/
removing mirrorlist with no valid mirrors: /var/tmp/system-upgrade/base/mirrorlist.txt
YumRepo Error: All mirror URLs are not using ftp, http[s] or file.
 Eg. 7.0 is not a valid and current release or hasnt been released yet/
removing mirrorlist with no valid mirrors: /var/tmp/system-upgrade/extras/mirrorlist.txt
YumRepo Error: All mirror URLs are not using ftp, http[s] or file.
 Eg. 7.0 is not a valid and current release or hasnt been released yet/
removing mirrorlist with no valid mirrors: /var/tmp/system-upgrade/updates/mirrorlist.txt
No upgrade available for the following repos: atomic atomic-testing base extras updates
.treeinfo                                                                                                                                        | 1.1 kB     00:00
preupgrade-assistant risk check found EXTREME risks for this upgrade.
Run preupg --riskcheck --verbose to view these risks.
Continuing with this upgrade is not recommended.

And this is the reason for the risk:

[root at apssopenvas /]# preupg --riskcheck --verbose
INPLACERISK: EXTREME: This machine seems to run on a Microsoft hypervisor.

Thank you!

Cheers,

Bruno Martins