Red Hat Bugzilla – Bug 1278555
rhevm-doc-ja-JP-3.6.0-1 fails update from 3.5.x
Last modified: 2016-04-12 17:25:51 EDT
Created attachment 1090314 [details]
Description of problem:
When trying to upgrade ovirt-engine to 3.6.0 from 3.5.x, the upgrade fails.
The following error appears in the logs:
2015-11-05 18:59:56 ERROR otopi.plugins.otopi.packagers.yumpackager yumpackager.error:100 Yum Error unpacking rpm package rhevm-doc-ja-JP-3.6.0-1.el6eng.noarch
2015-11-05 18:59:56 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:91 Yum Script sink: error: unpacking of archive failed on file /usr/share/doc/rhevm-doc/manual/ja-JP: cpio: rename failed - Is a directory
2015-11-05 18:59:56 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:91 Yum Done: rhevm-doc-ja-JP-3.6.0-1.el6eng.noarch
Version-Release number of selected component (if applicable):
Ugrading to: rhevm-doc-ja-JP-3.6.0-1.el6eng.noarch
From: rhevm-doc-ja-JP.noarch 0:3.5.3-1.el6eng
Added full engine-setup log.
Package for 3.6.0 is empty (only two directories) while the 3,5 package contains many files.
Since GA has been pushed back to March, 3.6 documentation translation will not commence until late Jan 2016.
For rhevm-doc queries, you might want to check with Greg Sheremeta.
(In reply to Barak Korren from comment #1)
> Package for 3.6.0 is empty (only two directories) while the 3,5 package
> contains many files.
@Greg - aren't the docs (in all locales) contain the exact same files as 3.5 at this point?
Interesting bug. Looks like we have a candidate for some CI upgrade tests.
At this point in the release cycle, each locale's RPM contains two symlinks over to English. Those are the "directories" Barak referred to.
Seems like yum can't handle an upgrade where a directory is changing to a symlink. Ultimately, it's a bug in the packaging of rhevm-doc, and I'll need to fix it.
Greg - any updates? I've marked it as urgent severity, as it is upgrade related.
Yep, I'll get it fixed today :) Sorry for the delay!
RHEV 3.6.0 BETA2 is out, any open bugs are moved to the BETA3 milestone.
3.6.0-2 fixes the issue.
This issue also affects