Bug 1310705 - Problem when configuring ovirt-engine with dockerc plugin enabled
Summary: Problem when configuring ovirt-engine with dockerc plugin enabled
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Engine
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.0.0-alpha
: 4.0.0
Assignee: Rafael Martins
QA Contact: Gonza
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-22 14:45 UTC by Rafael Martins
Modified: 2019-04-28 11:13 UTC (History)
2 users (show)

Fixed In Version: ovirt 4.0.0 alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-11 08:55:19 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 53838 0 master MERGED packaging: setup: dockerc: fix usage of ovirt_setup_lib.hostname 2016-02-23 14:49:05 UTC

Description Rafael Martins 2016-02-22 14:45:42 UTC 
Description of problem: When configuring ovirt-engine with dockerc plugin enabled, I got an error when the plugin instantiates the Hostname class from ovirt_setup_lib, and instead of store the object in a variable, it stores the return of the getHostname method, that is a string, and not the Hostname instance object.


Version-Release number of selected component (if applicable):


How reproducible: run engine-setup with docker plugin installed and enable cinder and glance support (not sure if both are needed)


Actual results: Error message saying that a string does not have a isResolvedByDNS method (unfortunately I lost the logs in a snapshot rollback)


Expected results: ovirt-engine properly installed and running


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