Bug 1009161
Summary: | Gem loading error: Could not find excon (~> 0.25.0) | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Og Maciel <omaciel> |
Component: | Provisioning | Assignee: | Jason Montleon <jmontleo> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Corey Welton <cwelton> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.2 | CC: | cwelton, dcleal, mmccune |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ruby193-rubygem-excon-0.25.3-2.el6sat | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-04-24 17:09:47 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Og Maciel
2013-09-17 20:46:04 UTC
Just an FYI, syncing is unrelated to this error, this is most likely a setup/dependency error ruby193-rubygem-fog requires rubygem-excon >= 0.25.0 and only 0.20.0 was in the repo. I caught this earlier today testing after I updated foreman and updated excon and the fog spec file once I saw it. For reproducing it, just check the cron.log about an hour after installation. Normally there's a cronjob installed in /etc/cron.d/foreman that runs every 30 minutes. Agreed with Mike, this'll have no effect on syncing or anything except various Foreman cleanup operations. This no longer occurs in SNAP2. QA verified. This was verified and delivered with MDP2. Closing it out. This was delivered and verified with MDP2. Closing the bug. |