Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1690906 - [DELL EMC 8.0 BUG]: Launching ESXI OMSA IP using DWS RHEL 8.0 OS IP fails with OM 9.2
Summary: [DELL EMC 8.0 BUG]: Launching ESXI OMSA IP using DWS RHEL 8.0 OS IP fails wit...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: openwsman
Version: 8.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: 8.1
Assignee: Vitezslav Crhonek
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-20 13:02 UTC by Santhosh_M_R
Modified: 2019-03-24 19:34 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)
Login failed (deleted)
2019-03-20 13:02 UTC, Santhosh_M_R
no flags Details
RHEL8.0 OMSA logs (deleted)
2019-03-20 13:13 UTC, Santhosh_M_R
no flags Details
RHEL8.0 failing logs (deleted)
2019-03-20 13:13 UTC, Santhosh_M_R
no flags Details
RHEL 7.5 working OMSA logs (deleted)
2019-03-20 13:17 UTC, Santhosh_M_R
no flags Details
RHEL7.5 passing logs (deleted)
2019-03-20 13:19 UTC, Santhosh_M_R
no flags Details

Description Santhosh_M_R 2019-03-20 13:02:36 UTC
Created attachment 1546059 [details]
Login failed

Description of problem:
With OM 9.2 unable to launch ESXI OMSA IP using DWS RHEL 8.0 OS IP

Version-Release number of selected component (if applicable):
net-snmp-5.8-7.el8.x86_64.rpm
libwsman1-2.6.5-4.el8.i686.rpm
libxslt-devel-1.1.32-3.el8.i686.rpm
openwsman-client-2.6.5-4.el8.i686.rpm
openwsman-server-2.6.5-4.el8.i686.rpm
libcmpiCppImpl0-2.0.3-15.el8.i686.rpm
sblim-sfcb-1.4.9-16.el8.x86_64.rpm

How reproducible:
Frequently

Steps to Reproduce:
-) Install OMSA 9.2 on ESXI 6.7 OS "esxcli software vib install -d /var/log/vmware/OM-0000.vib".

-) Install RHEL 8.0 On any server and install all dependency packages
"zypper install net-snmp python pciutils libwsman3 libxslt1 openwsman-server libcmpiCppImpl0 sblim-sfcb".
-) install OMSA in RHEL 8.0 by mounting "om_dvd_lin920_3142". 
-) Launch ESXI OMSA IP using DWS RHEL 8.0 OS IP . 
  
Actual results:
Login Failed .. Connection Error.

Expected results:
should be able to launch ESXI OMSA IP using DWS RHEL 8.0 OS IP

Additional info:
Working fine in RHEL7.5.
RHEL 7.5 versions : 

  net-snmp-5.7.2-32.el7.x86_64
  libwsman1-2.6.3-3.git4391e5c.el7.x86_64
  libxslt-1.1.28-5.el7.x86_64
  openwsman-client-2.6.3-3.git4391e5c.el7.x86_64
  openwsman-server-2.6.3-3.git4391e5c.el7.x86_64
  libcmpiCppImpl0-2.0.3-5.el7.x86_64
  sblim-sfcb-1.3.16-12.el7_0.x86_64

Comment 1 Santhosh_M_R 2019-03-20 13:13:02 UTC
Created attachment 1546071 [details]
RHEL8.0 OMSA logs

Comment 2 Santhosh_M_R 2019-03-20 13:13:54 UTC
Created attachment 1546072 [details]
RHEL8.0 failing logs

Comment 3 Santhosh_M_R 2019-03-20 13:17:55 UTC
Created attachment 1546073 [details]
RHEL 7.5 working OMSA  logs

Comment 4 Santhosh_M_R 2019-03-20 13:19:14 UTC
Created attachment 1546075 [details]
RHEL7.5 passing logs

Comment 5 Vitezslav Crhonek 2019-03-20 13:48:57 UTC
Although I have no knowledge of OMSA... comparing differences between passing/failing logs - it seems to me that the problem is somewhere in CIM provider for DCIM_OEM_DataAccessModule class on managed machine, relevant part of logs:

works:
Jul 20 05:42:11 [108309] Inbound call...
Jul 20 05:42:11 [108309] uri: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/DCIM_OEM_DataAccessModule, action: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/DCIM_OEM_DataAccessModule/SendCmd
Jul 20 05:42:11 [108309] namespace: http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd
Jul 20 05:42:11 [108309] namespace: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2
Jul 20 05:42:11 [108309] Processing Filters: inbound
Jul 20 05:42:11 [108309] Checking Message ID: fff03825-f8cd-4706-b3e6-1878a5f9840d
Jul 20 05:42:11 [108309] Custom Method Endpoint Called
Jul 20 05:42:11 [108309] username: root, password: XXXXX
Jul 20 05:42:11 [108309] Connecting using sfcc XML frontend
Jul 20 05:42:11 [108309] new cimclient: 0x 659e8f8
Jul 20 05:42:11 [108309] new cimclient: 1
Jul 20 05:42:11 [108309] text: __cimnamespace
Jul 20 05:42:11 [108309] text: InstanceID
Jul 20 05:42:11 [108309] method or action: SendCmd
Jul 20 05:42:11 [108309] CIM Namespace: root/dcim/sysman
Jul 20 05:42:11 [108309] method or action: SendCmd
Jul 20 05:42:11 [108309] text: CommandAndArguments
Jul 20 05:42:11 [108309] class available
Jul 20 05:42:11 [108309] enumInstanceNames rc=0, msg=(null)

fails:
Jul 20 05:41:38 [108309] Inbound call...
Jul 20 05:41:38 [108309] uri: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/DCIM_OEM_DataAccessModule, action: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/DCIM_OEM_DataAccessModule/SendCmd
Jul 20 05:41:38 [108309] namespace: http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd
Jul 20 05:41:38 [108309] namespace: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2
Jul 20 05:41:38 [108309] Processing Filters: inbound
Jul 20 05:41:38 [108309] Checking Message ID: uuid:f73eb50a-7170-1170-8003-7d52b6f70a00
Jul 20 05:41:38 [108309] Custom Method Endpoint Called
Jul 20 05:41:38 [108309] username: root, password: XXXXX
Jul 20 05:41:38 [108309] Connecting using sfcc XML frontend
Jul 20 05:41:38 [108309] new cimclient: 0x 65a1aa8
Jul 20 05:41:38 [108309] new cimclient: 1
Jul 20 05:41:38 [108309] text: InstanceID
Jul 20 05:41:38 [108309] method or action: SendCmd
Jul 20 05:41:38 [108309] method or action: SendCmd
Jul 20 05:41:38 [108309] text: CommandAndArguments
Jul 20 05:41:38 [108309] class available
Jul 20 05:41:38 [108309] enumInstanceNames rc=5, msg=(null)

rc=5 - it's not able to enumerate instance names and pass it to openwsmand.

Does the CIM stack work correctly? Are there all necessary providers installed? (For example sblim-cmpi-base is available on RHEL7, but it is _not_ available on RHEL8 - isn't it needed?) Can you enumerate instances of DCIM_OEM_DataAccessModule class not using openwsman protocol, but directly with CIM using some CIM client?

Comment 6 Santhosh_M_R 2019-03-22 07:10:05 UTC
Yes the CIM stack is working correctly we have tried with RHEL 7.5 . We are installing the following packages (net-snmp, python, pciutils, libwsman1, libxslt1, openwsman-server, libcmpiCppImpl0, sblim-sfcb ). We are trying to enumerate instances but openslp-server-2.0.0-18.el8.x86_64, openslp-devel-2.0.0-18.el8.x86_64, and sblim-wbemcli packages missing to check using CIM client.


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