Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-14030

The "long_desc" for some of our power fence-agents is incorrect

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • rhel-9.4
    • rhel-9.2.0
    • fence-agents
    • None
    • fence-agents-4.10.0-60.el9
    • sst_high_availability
    • ssg_filesystems_storage_and_HA
    • 13
    • 17
    • 1
    • QE ack, Dev ack
    • False
    • Hide

      None

      Show
      None

      What were you trying to do that didn't work?

      The description provided for some power fence-agents says they are IO fencing agents which is incorrect. For example:

       

      # pcs stonith describe fence_cisco_ucs | head -n 4
      fence_cisco_ucs - Fence agent for Cisco UCS
      fence_cisco_ucs is an I/O Fencing agent which can be used with Cisco UCS to
      fence machines.
      

      We need to amend the docs["longdesc"] for any power fence-agents that says it is an IO fence-agent which is incorrect.

      # grep "I/O Fencing agent" /usr/sbin/fence_* | wc -l
      grep: /usr/sbin/fence_virt: binary file matches
      grep: /usr/sbin/fence_xvm: binary file matches
      36

       

      We need to verify that all the fence-agents we support correctly identity if they are storage or power fence-agents. 

       

      Please provide the package NVR for which bug is seen:

      # rpm -q fence-agents-cisco-ucs
      fence-agents-cisco-ucs-4.10.0-43.el9.noarch

      How reproducible:

      Everytime

      Steps to reproduce

      1. # pcs stonith describe fence_cisco_ucs

      Expected results

      The fence-agent should state the correct type of stonith device which is either a power or storage.

      Actual results

      Some power fence-agents state they are IO (or storage) fence-agents which is incorrect. 

            rhn-engineering-oalbrigt Oyvind Albrigtsen
            rhn-support-sbradley Shane Bradley
            Oyvind Albrigtsen Oyvind Albrigtsen
            Cluster QE Cluster QE
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: