[ClusterLabs] Unable to Build fence-agents from Source on RHEL6

Jason A Ramsey jason at eramsey.org
Wed Aug 10 19:03:53 EDT 2016

Believe me, I would love to use a more modern dist, but RHEL6 is currently our standard image…

[ jR ]
  M: +1 (703) 628-2621
  @: jason at eramsey.org
  there is no path to greatness; greatness is the path

On 8/10/16, 2:50 PM, "Jan Pokorný" <jpokorny at redhat.com> wrote:

    On 10/08/16 16:52 +0000, Jason A Ramsey wrote:
    > Installing the openwsman-python package doesn’t work. Configure’ing
    > the fence-agents source tree fails because it still can’t find the
    > pywsman module. I thought that it might be because it’s looking in
    > /usr/lib/python-x/site-packages rather than
    > /usr/lib64/python-x/site-packages (or vice versa…I can’t remember…)
    > but when I looked at the output, it was definitely looking in the
    > directory that had pywsman.py/pyc/pyo or whatever it was.
    Hmm, here's why:
    # python -c 'import pywsman'                                      
    > Traceback (most recent call last):                                                            
    >   File "<string>", line 1, in <module>                                                        
    >   File "/usr/lib/python2.6/site-packages/pywsman.py", line 25, in <module>                    
    >     _pywsman = swig_import_helper()                                                           
    >   File "/usr/lib/python2.6/site-packages/pywsman.py", line 17, in swig_import_helper          
    >     import _pywsman                                                                           
    > ImportError: /usr/lib64/python2.6/site-packages/_pywsman.so: undefined symbol: SWIG_exception 
    it should also answer your "it’s not in the default yum repos" point
    you've raised as indeed, both libwsman-devel and openwsman-python
    are in "optional" repository with RHEL 6, meaning packages as-are,
    without liabilities (mostly enabling the supported ones to be built;
    openwsman-python in particular can be just a never triggered byproduct
    when the important sibling packages, perhaps build prerequisites,
    got built).
    So either stick with upstream provided version for binaries + bindings
    or you may have better luck with RHEL 7 (slash derivatives).
    Anyway, you got me (indirectly) to make this PR against FAs:
    Jan (Poki)

More information about the Users mailing list