Hide Forgot
Description of problem:update fails due to conflicting packages Version-Release number of selected component (if applicable):5.7.0.11 How reproducible:100% Steps to Reproduce: 1.provision 5.7.0.10 appliance 2.add repos for latest build 3.run 'yum update' or register RHSM and update through webui Actual results:update fails Expected results:update completes successfully Additional info: Transaction check error: file /opt/rh/cfme-gemset/gems/manageiq-api-client-0.1.0 from install of cfme-gemset-5.7.0.11-rc1.1.el7cf.x86_64 conflicts with file from package cfme-gemset-5.7.0.10-beta3.1.el7cf.x86_64 file /opt/rh/cfme-gemset/gems/query_relation-0.1.0 from install of cfme-gemset-5.7.0.11-rc1.1.el7cf.x86_64 conflicts with file from package cfme-gemset-5.7.0.10-beta3.1.el7cf.x86_64
This is because these gems moved from git-based gems to released gems without changing the version number. This shouldn't be an issue for post-GA upgrades as I expect these gems will stay released rather than git based. This *will* be an issue for anyone trying to upgrade from beta to beta or from beta to RC. Is that something we are trying to support? My suspicion is that this will work with next week's build. (i.e. upgrading from 5.7.0.11 to 5.7.0.12), but that may not be good enough if we are supporting beta to beta or beta to RC upgrades. If we want to support those upgrades we would need a new gem version to be released and included in the next build of the gemset rpm. That would allow the files to not conflict. Jason, which way do you want to go with this?
This is still due to this (rather old) BZ against rpm in Fedora https://bugzilla.redhat.com/show_bug.cgi?id=447156
A temporary workaround would be executing the following before attempting the upgrade on the server: `rm /opt/rh/cfme-gemset/gems/manageiq-api-client-0.1.0` `rm /opt/rh/cfme-gemset/gems/query_relation-0.1.0` Then the yum update will succeed.
New gem versions have been released: https://github.com/ManageIQ/query_relation/releases/tag/v0.1.1 https://github.com/ManageIQ/manageiq-api-client/releases/tag/v0.1.1 You can test this change by updating from 5.7.0.10 to the next built version (updating from versions 5.7.0.11 and forward would update cleanly even without this change).
Verified in 5.7.0.12