Bug 1279589

Summary: Incorrect type usage of extension api
Product: [oVirt] ovirt-engine Reporter: Alon Bar-Lev <alonbl>
Component: Extension-APIAssignee: Yaniv Kaul <ykaul>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: bugs, gklein, iheim
Target Milestone: ovirt-4.0.0-alphaKeywords: CodeChange
Target Release: 4.0.0Flags: rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
alonbl: devel_ack+
pstehlik: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1280246 (view as bug list) Environment:
Last Closed: 2016-07-27 13:00:07 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:
Bug Depends On:    
Bug Blocks: 1280246    

Description Alon Bar-Lev 2015-11-09 19:55:37 UTC
1. ExtMap.get tries to cast to default value type.
2. AVAILABLE_NAMESPACES is a collection not a list.

Comment 1 Red Hat Bugzilla Rules Engine 2015-11-09 19:55:41 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Red Hat Bugzilla Rules Engine 2015-11-09 19:59:12 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 Ondra Machacek 2016-02-25 09:39:19 UTC
This one shouldn't be ON_QA, because there is no 4.0 build for QE, yet.

Comment 7 Gil Klein 2016-07-27 13:00:07 UTC
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA