Bug 711112 - f14 yum errors with public production repo
Summary: f14 yum errors with public production repo
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Justin Clift
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks: ce-p2-beta-fixed
TreeView+ depends on / blocked
 
Reported: 2011-06-06 15:09 UTC by Dave Johnson
Modified: 2015-07-13 04:35 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-14 13:30:47 UTC
Embargoed:


Attachments (Terms of Use)

Description Dave Johnson 2011-06-06 15:09:14 UTC
Tried to install on a f14 system and it failed with the following...

wget -O /etc/yum.repos.d/fedora-aeolus.repo http://repos.fedorapeople.org/repos/aeolus/conductor/0.2.0/fedora-aeolus.repo; yum -y install aeolus-configure aeolus-conductor aeolus-conductor-doc aeolus-conductor-daemons;


--> Running transaction check
---> Package condor.x86_64 0:7.6.0-2dcloud.fc14 set to be installed
--> Processing Dependency: libdeltacloud.so.5(LIBDCLOUDAPI_0.0.0)(64bit) for package: condor-7.6.0-2dcloud.fc14.x86_64
--> Processing Dependency: libdeltacloud.so.5(LIBDCLOUDAPI_1.0.0)(64bit) for package: condor-7.6.0-2dcloud.fc14.x86_64
--> Processing Dependency: libdeltacloud.so.5(LIBDCLOUDAPI_2.0.0)(64bit) for package: condor-7.6.0-2dcloud.fc14.x86_64
--> Processing Dependency: libdeltacloud.so.5()(64bit) for package: condor-7.6.0-2dcloud.fc14.x86_64
---> Package libmlx4.x86_64 0:1.0.1-6.fc14 set to be installed
--> Finished Dependency Resolution
Error: Package: condor-7.6.0-2dcloud.fc14.x86_64 (fedora-aeolus)
           Requires: libdeltacloud.so.5(LIBDCLOUDAPI_1.0.0)(64bit)
           Available: libdeltacloud-0.7-1.fc14.x86_64 (fedora-aeolus)
               libdeltacloud.so.5(LIBDCLOUDAPI_1.0.0)(64bit)
           Available: libdeltacloud-0.8-1.fc14.i686 (updates)
               Not found
Error: Package: condor-7.6.0-2dcloud.fc14.x86_64 (fedora-aeolus)
           Requires: libdeltacloud.so.5()(64bit)
           Available: libdeltacloud-0.7-1.fc14.x86_64 (fedora-aeolus)
               libdeltacloud.so.5()(64bit)
           Available: libdeltacloud-0.8-1.fc14.i686 (updates)
               Not found
Error: Package: condor-7.6.0-2dcloud.fc14.x86_64 (fedora-aeolus)
           Requires: libdeltacloud.so.5(LIBDCLOUDAPI_2.0.0)(64bit)
           Available: libdeltacloud-0.7-1.fc14.x86_64 (fedora-aeolus)
               libdeltacloud.so.5(LIBDCLOUDAPI_2.0.0)(64bit)
           Available: libdeltacloud-0.8-1.fc14.i686 (updates)
               Not found
Error: Package: condor-7.6.0-2dcloud.fc14.x86_64 (fedora-aeolus)
           Requires: libdeltacloud.so.5(LIBDCLOUDAPI_0.0.0)(64bit)
           Available: libdeltacloud-0.7-1.fc14.x86_64 (fedora-aeolus)
               libdeltacloud.so.5(LIBDCLOUDAPI_0.0.0)(64bit)
           Available: libdeltacloud-0.8-1.fc14.i686 (updates)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Comment 1 Chris Lalancette 2011-06-06 15:25:14 UTC
Nasty.  I don't know how to resolve this.

conductor-0.2.0 relied on condor-7.6.0-2dcloud, which in turn relied on libdeltacloud 0.7.  Unfortunately, due to various bugs, the API in libdeltacloud had to be broken for 0.8, which is what is now available in the Fedora 14 repositories.  That means that condor-7.6.0-3dcloud will work fine (which is what is in testing), but condor 7.6.0-2dcloud will no longer work.

What I don't understand is why it couldn't resolve the dependency, since deltacloud 0.7 is available in the 0.2.0 repositories.  I guess the version bump overrides the Requires in yum logic, though I'm not sure.

Chris Lalancette

Comment 2 wes hayutin 2011-06-06 15:47:30 UTC
why is the 0.2.0 fedora repo changing at all?

Comment 3 Chris Lalancette 2011-06-06 16:26:43 UTC
It's not; the fedora updates repositories are what is changing, and since we have set 0.2.0 in stone, so to speak, it is not keeping up with the changes that are going on in fedora updates.

Chris Lalancette

Comment 4 wes hayutin 2011-06-06 17:51:06 UTC
ahh.. thanks Chris!! Thats an interesting problem.. maybe something I can chat w/ eggs about

Comment 5 wes hayutin 2011-06-13 13:45:48 UTC
*** Bug 711610 has been marked as a duplicate of this bug. ***

Comment 6 Justin Clift 2011-06-13 14:33:19 UTC
Hmmmm, maybe we should add the 0.2.0 deps it can't resolve to the 0.2.0 repo, to ensure people have a smooth install experience.

It's not exactly great from a "purity" point of view, but the point here is to let people install it with minimal hassles.

?

Comment 7 Chris Lalancette 2011-06-13 15:33:40 UTC
That won't work.  Those RPMs are already in the 0.2.0 repositories, but the problem is that the RPMs available in updates are newer.  So it sees something like "condor Requires libdeltacloud", then goes to resolve the libdeltacloud.  It finds libdeltacloud in 2 places; fedora-aeolus, with version 0.7, and updates, with version 0.8.  It then selects the newest one (0.8, from updates), and when it re-runs dependencies, it fails because 0.8 doesn't provide the correct library version.

Like I said, I'm not quite sure what to do here :(.

Chris Lalancette

Comment 8 Justin Clift 2011-06-13 15:42:01 UTC
Ahhh, that sounds pretty easy to fix.  We should be able to add version into to the Requires like, so it'll pick the 0.7 version.

Comment 9 Justin Clift 2011-06-13 17:39:59 UTC
Found a working solution, that we just need to figure the best way to implement.

The existing condor package that we carry has these lines in the spec file:

  BuildRequires: libdeltacloud-devel >= 0.7
  Requires: libdeltacloud >= 0.7

Removing the ">" from those lines works, as it tells yum to ignore anything later than 0.7 (tested):

  BuildRequires: libdeltacloud-devel = 0.7
  Requires: libdeltacloud = 0.7

So, the solution seems to be us tweaking the condor package we provide (new revision -3?), with that change.

Comment 10 Chris Lalancette 2011-06-13 18:03:03 UTC
Ah, nice work.  Yeah, that will work.

Note: we don't want to call the condor package -3, because I've been using the release number as an "aeolus patch-level" marker.  I'd rather call it 2.1, so:

condor-7.6.0-2.1dcloud

Chris Lalancette

Comment 11 Justin Clift 2011-06-13 19:38:51 UTC
*** Bug 711610 has been marked as a duplicate of this bug. ***

Comment 12 Justin Clift 2011-06-14 07:57:59 UTC
Found another solution too, which was to add:

  --exclude="libdeltacloud-0.8"

to the Fedora 14 installation instructions for the stable repo.

This works (tested), so the Aeolus website has been updated to include it:

  http://www.aeolusproject.org/get_it.html#stablefedora

It would probably be nice to have the updated condor package as well,
but it's no longer as urgent as it was. :)

Comment 13 Justin Clift 2011-06-14 13:30:47 UTC
Chris has uploaded a new condor package (-2.1) which fixes the dependency problem, so the exclude option mentioned in comment 12 is no longer needed.

The instructions on the website work "out of the box" on Fedora 14 again.

Comment 14 wes hayutin 2011-06-14 14:20:17 UTC
ready for qe

Comment 15 wes hayutin 2011-06-20 15:56:53 UTC
verified in ami

Comment 16 wes hayutin 2011-07-05 15:04:11 UTC
removing ce-p2-beta

Comment 17 wes hayutin 2011-07-05 15:07:53 UTC
second attempt to remove ce-p2-beta

Comment 18 wes hayutin 2011-08-01 20:00:47 UTC
release pending...

Comment 19 wes hayutin 2011-08-01 20:00:49 UTC
release pending...

Comment 20 wes hayutin 2011-08-01 20:01:01 UTC
release pending.. 2

Comment 22 wes hayutin 2011-12-08 14:02:27 UTC
closing out old bugs

Comment 23 wes hayutin 2011-12-08 14:14:22 UTC
perm close


Note You need to log in before you can comment on or make changes to this bug.