Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1640911

Summary:	wrong message when getting storages for non active host
Product:	[oVirt] ovirt-engine	Reporter:	Lucie Leistnerova <lleistne>
Component:	RestAPI	Assignee:	Dana <delfassy>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.3.0	CC:	bugs, ebenahar, kgoldbla, mperina
Target Milestone:	ovirt-4.3.0	Flags:	rule-engine: ovirt-4.3+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.0_rc	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-13 07:46:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lucie Leistnerova 2018-10-19 07:11:52 UTC

Description of problem:
There are variable names instead of values when getting storages for non active host.

Version-Release number of selected component (if applicable):
ovirt-engine-restapi-4.3.0-0.0.master.20181016132820.gite60d148.el7.noarch

How reproducible: always


Steps to Reproduce:
1. put host in maintenance
2. get host's storages via api, e.g.:
curl -k -u admin@internal:passw -H "Prefer: persistent-auth" https://engine/ovirt-engine/api/hosts/<host-uuid>/storage


Actual results:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<fault>
    <detail>Cannot ${action} ${type}. The server ${VdsName} is not UP.</detail>
    <reason>Operation Failed</reason>
</fault>



Expected results:
${action} ${type} ${VdsName} changed to the values

Comment 2 Lucie Leistnerova 2018-12-11 08:42:11 UTC

Message changed to 'cannot fetch storage devices, host XXX is not up.'

verified in ovirt-engine-restapi-4.3.0-0.4.master.20181210172657.git88f34ae.el7.noarch

Comment 3 Sandro Bonazzola 2019-02-13 07:46:40 UTC

This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.