Bug 1166842

Summary: netapp bindings missing directory in expected path
Product: Red Hat CloudForms Management Engine Reporter: Dave Johnson <dajohnso>
Component: StorageAssignee: Rich Oliveri <roliveri>
Status: CLOSED EOL QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3.0CC: jhardy, jprause, jrafanie, obarenbo, xlecauch
Target Milestone: GAKeywords: ZStream
Target Release: 5.3.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: appliance:netapp
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1166841 Environment:
Last Closed: 2017-02-28 19:38:54 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:
Bug Depends On: 1166841    
Bug Blocks:    

Description Dave Johnson 2014-11-21 17:15:07 UTC
+++ This bug was initially created as a clone of Bug #1166841 +++

Description of problem:
=============================
We have known for a bit that something was going on with netapp integration.  This week qe & dev dug into it and figured out this appears to be a build issue.

Ultimately we are missing a lib directory in the path which breaks the integration.  5.2 works, 5.3 does not.

5.2: /var/www/miq/lib/NetappManageabilityAPI/NmaCore/lib/x86_64-linux/ruby1.9.3
5.3: /var/www/miq/lib/NetappManageabilityAPI/NmaCore/x86_64-linux/ruby1.9.3


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


How reproducible:
===========================
100%


Steps to Reproduce:
============================
1.  install netapp client sdk
2.  enable netapp feature
3.  add filer to manage


Actual results:
===================
failure

Expected results:
====================
success


Additional info:

Comment 1 Joe Rafaniello 2015-01-22 18:44:27 UTC
As was we discussed in regards to https://bugzilla.redhat.com/show_bug.cgi?id=1166841, this issue was being looked at by possibly replacing the c binding with a pure ruby implementation.