Bug 1003959

Summary: Make "Nothing to do" error from yum in Puppet installs a little easier to decipher
Product: [Community] RDO Reporter: Perry Myers <pmyers>
Component: openstack-packstackAssignee: Martin Magr <mmagr>
Status: CLOSED CURRENTRELEASE QA Contact: yeylon <yeylon>
Severity: low Docs Contact:
Priority: medium    
Version: unspecifiedCC: aortega, derekh, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-packstack-2013.2.1-0.11.dev806.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-30 22:59:41 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 Perry Myers 2013-09-03 14:54:44 UTC 
From this discussion:
http://openstack.redhat.com/forum/discussion/519/puppet-fails-to-set-openvswitch-from-absent-to-present/p1

It's clear that the current error messages from yum when package installation fails are not really good enough.  Yum will just say "Nothing to do" which doesn't tell the user what really happened.

What we should do is have Packstack catch that sort of error from Yum/Puppet and let the user know that the issue is that the package in question was a dependency and it failed to install for some reason.
Comment 1 Martin Magr 2013-09-20 14:05:53 UTC 
*** Bug 1003957 has been marked as a duplicate of this bug. ***