Bug 1086687 - [RFE] Host install: improve message into events if host cannot be installed because yum cannot find packages
Summary: [RFE] Host install: improve message into events if host cannot be installed b...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 3.4.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Scott Herold
QA Contact: Shai Revivo
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-11 10:14 UTC by Martin Pavlik
Modified: 2016-02-10 19:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-16 14:46:32 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:
sherold: Triaged+

Attachments (Terms of Use)
deploy log (226.75 KB, text/x-log)
2014-04-11 10:14 UTC, Martin Pavlik 		no flags Details
View All

Description Martin Pavlik 2014-04-11 10:14:36 UTC 
Created attachment 885357 [details]
deploy log

Description of problem:

if host installation fails on missing repository, all that is logged into GUI event log is following message, which does not really explain what happened

Host dell-07 installation failed. Command returned failure code 1 during SSH session 'root.66.71'.

it would be nice if it could pass the info from yum

2014-04-11 10:43:31 ERROR otopi.plugins.otopi.packagers.yumpackager yumpackager.error:97 Yum Cannot queue package openstack-neutron: Package openstack-neutron cannot be found


Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 3.4.0-0.13.beta3.el6ev 

How reproducible:


Steps to Reproduce:
1. disable some of the needed repos (e.g. rhevm.reop)
2. try to install host through RHEV-M


Actual results:
Host dell-07 installation failed. Command returned failure code 1 during SSH session 'root.66.71'.

Expected results:
more detailed info on the failure

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