Error during unpacking rpm package filesystem-2.4.30-3.el6.x86_64 when converting from CENTOS6 to RHEL6 about convert2rhel

[Venefilyn]

Hi!

Are you able to get the machine working by rebooting and running yum update -y after the error has occurred? Does this happen on version 0.13 or an older version? yum list convert2rhel

[bocekm]

Hi, thanks for the report.

Please make sure that your / and /sys/ folders are not mounted as read-only (https://unix.stackexchange.com/questions/173896/sys-cpio-chown-failed-read-only-file-system-building-passenger-rpm-using-d).
Are the CentOS 6 systems VMs or containers?

Regarding the possible recovery - the failure happened after the point where conver2rhel is able to do a rollback.
But you can try going to /var/lib/convert2rhel/ and run rpm -i --replacepkgs *rpm. That should at least get you to a point from where you can run convert2rhel again.

[ahilden]

The version of convert2rhel I have installed was 0.9-1.el6. I was able to revert. The backup of the rpms was in /tmp/convert2rhel as opposed to /var/lib/convert2rhel. I was able to run rpm -i --replacepkgs *rpm and will be trying to move forward again. I'm not sure what is wrong with sys, although it seems like all of our centos6 system are like this though and they indirectly cause the filesystem package to fail to install.

[root@dashdb-prod-staging-txn-test2 ahilden]# mount |grep sys
sysfs on /sys type sysfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
[root@dashdb-prod-staging-txn-test2 ahilden]# chown root /sys
chown: changing ownership of `/sys': Read-only file system
[root@dashdb-prod-staging-txn-test2 ahilden]# 

I was able remount /sys rw to correct the issue with filesystem.
mount -o remount,rw /sys

After this the conversion was successful. I'm not sure why all of our systems are like this or if it's a common occurrence on centos6.

[bocekm]

We'll be adding checks for /sys/ being mounted as rw to convert2rhel. It's tracked internally under https://issues.redhat.com/browse/OAMG-4310.
Before that happens, we'll have a warning in the main article https://access.redhat.com/articles/2360841 soon.
Thanks for your time spent on this issue, @ahilden.