← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1864410] Re: [xenial] fence_scsi does not support hostnames in node list

 

** Also affects: fence-agents (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** No longer affects: fence-agents (Ubuntu Xenial)

** Summary changed:

- [xenial] fence_scsi does not support hostnames in node list
+ [bionic] fence_scsi does not support hostnames in node list

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1864410

Title:
  [bionic] fence_scsi does not support hostnames in node list

Status in fence-agents package in Ubuntu:
  New
Status in fence-agents source package in Bionic:
  New

Bug description:
  Whenever configuring fence_scsi in a pacemaker cluster, the
  "fence_scsi" fencing agent won't support having node names in its
  pcmk_host_list. You can reproduce this behavior using the fence_scsi
  agent directly:

  $ sudo fence_scsi --verbose -n clubionic01 --action=off -d /dev/disk
  /by-path/acpi-VMBUS:01-scsi-0:0:0:0

  Delay 0 second(s) before logging in to the fence device
  Executing: /usr/sbin/corosync-cmapctl totem.cluster_name

  0 totem.cluster_name (str) = clubionic

  
  Executing: /usr/sbin/corosync-cmapctl nodelist.

  0 nodelist.local_node_pos (u32) = 0
  nodelist.node.0.name (str) = clubionic01
  nodelist.node.0.nodeid (u32) = 1
  nodelist.node.0.ring0_addr (str) = 10.250.3.10
  nodelist.node.1.name (str) = clubionic02
  nodelist.node.1.nodeid (u32) = 2
  nodelist.node.1.ring0_addr (str) = 10.250.3.11
  nodelist.node.2.name (str) = clubionic03
  nodelist.node.2.nodeid (u32) = 3
  nodelist.node.2.ring0_addr (str) = 10.250.3.12

  
  Failed: unable to parse output of corosync-cmapctl or node does not exist

  Please use '-h' for usage

  ----------

  When using IP address fence_scsi agent works:

  rafaeldtinoco@clubionic01:~$ sudo fence_scsi --verbose -n 10.250.3.10 --action=off -d /dev/disk/by-path/acpi-VMBUS:01-scsi-0:0:0:0
  Delay 0 second(s) before logging in to the fence device
  Executing: /usr/sbin/corosync-cmapctl totem.cluster_name

  0 totem.cluster_name (str) = clubionic

  
  Executing: /usr/sbin/corosync-cmapctl nodelist.

  0 nodelist.local_node_pos (u32) = 0
  nodelist.node.0.name (str) = clubionic01
  nodelist.node.0.nodeid (u32) = 1
  nodelist.node.0.ring0_addr (str) = 10.250.3.10
  nodelist.node.1.name (str) = clubionic02
  nodelist.node.1.nodeid (u32) = 2
  nodelist.node.1.ring0_addr (str) = 10.250.3.11
  nodelist.node.2.name (str) = clubionic03
  nodelist.node.2.nodeid (u32) = 3
  nodelist.node.2.ring0_addr (str) = 10.250.3.12

  
  Executing: /usr/bin/sg_turs /dev/disk/by-path/acpi-VMBUS:01-scsi-0:0:0:0

  0

  Executing: /usr/bin/sg_turs /dev/disk/by-path/acpi-
  VMBUS:01-scsi-0:0:0:0

  0

  Executing: /usr/bin/sg_persist -n -i -k -d /dev/disk/by-path/acpi-
  VMBUS:01-scsi-0:0:0:0

  0   PR generation=0x4, there are NO registered reservation keys

  
  No registration for key 3abe0000 on device /dev/disk/by-path/acpi-VMBUS:01-scsi-0:0:0:0

  Success: Already OFF

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864410/+subscriptions


References