Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1456794 - openstack overcloud generate fencing not working as expected.
openstack overcloud generate fencing not working as expected.
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
11.0 (Ocata)
x86_64 Linux
medium Severity medium
: rc
: 12.0 (Pike)
Assigned To: Emilien Macchi
Udi Shkalim
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-05-30 07:45 EDT by VIKRANT
Modified: 2018-02-05 14:07 EST (History)
8 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170821194253.el7ost puppet-tripleo-7.3.0-0.20170821114704.el7ost puppet-pacemaker-0.6.1-0.20170808002406.e0f9c42.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-13 16:29:42 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1686115 None None None 2017-07-06 05:37 EDT
OpenStack gerrit 459787 None None None 2017-07-06 05:38 EDT
OpenStack gerrit 473735 None None None 2017-07-06 05:39 EDT
OpenStack gerrit 473736 None None None 2017-07-06 05:38 EDT
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Description VIKRANT 2017-05-30 07:45:49 EDT
Description of problem:

in lab environment, we were having OSP 10 setup, undercloud upgraded from OSP 10 to OSP 11 but overcloud node is still having OSP 10. I don't think it should matter in this scenario. 

i tried to create fencing.yaml to reproduce one Cu. scenario. I can see that fencing.yaml contains only two nodes. 

https://bugzilla.redhat.com/show_bug.cgi?id=1426481

Version-Release number of selected component (if applicable):
RHEL OSP 11

How reproducible:
Everytime. 

Steps to Reproduce:
1. Try to follow the steps given in official guide. 
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/advanced_overcloud_customization/#enable_fencing
2.
3.

Actual results:
It's picking the compute nodes for fencing. 

Expected results:
It should generate the fence configuration for overcloud controller node.

Additional info:

More information coming in internal comment.
Comment 7 Udi Shkalim 2017-11-15 09:52:08 EST
Verified on openstack-tripleo-heat-templates-7.0.3-0.20171024200823.el7ost.noarch puppet-pacemaker-0.6.1-0.20171024215340.9a46ecd.el7ost.noarch puppet-tripleo-7.4.3-0.20171025110206.el7ost.noarch



[stack@undercloud-0 ~]$ cat fencing.yaml 
parameter_defaults:
  EnableFencing: true
  FencingConfig:
    devices:
    - agent: fence_ipmilan
      host_mac: 52:54:00:54:fa:60
      params:
        ipaddr: 172.16.0.4
        ipport: '6230'
        lanplus: true
        login: admin
        passwd: password
        pcmk_host_list: compute-0
        privlvl: administrator
    - agent: fence_ipmilan
      host_mac: 52:54:00:96:a7:24
      params:
        ipaddr: 172.16.0.4
        ipport: '6231'
        lanplus: true
        login: admin
        passwd: password
        pcmk_host_list: compute-1
        privlvl: administrator
    - agent: fence_ipmilan
      host_mac: 52:54:00:dd:77:49
      params:
        ipaddr: 172.16.0.4
        ipport: '6232'
        lanplus: true
        login: admin
        passwd: password
        pcmk_host_list: controller-2
        privlvl: administrator
    - agent: fence_ipmilan
      host_mac: 52:54:00:91:0a:96
      params:
        ipaddr: 172.16.0.4
        ipport: '6233'
        lanplus: true
        login: admin
        passwd: password
        pcmk_host_list: controller-0
        privlvl: administrator
    - agent: fence_ipmilan
      host_mac: 52:54:00:03:b4:d9
      params:
        ipaddr: 172.16.0.4
        ipport: '6234'
        lanplus: true
        login: admin
        passwd: password
        pcmk_host_list: controller-1
        privlvl: administrator
[stack@undercloud-0 ~]$ openstack baremetal list
Missing value auth-url required for auth plugin password
[stack@undercloud-0 ~]$ . stackrc 
(undercloud) [stack@undercloud-0 ~]$ openstack baremetal list
This command is deprecated. Instead, use 'openstack baremetal node list'.
+--------------------------------------+--------------+--------------------------------------+-------------+--------------------+-------------+
| UUID                                 | Name         | Instance UUID                        | Power State | Provisioning State | Maintenance |
+--------------------------------------+--------------+--------------------------------------+-------------+--------------------+-------------+
| fe83c6c8-b1a4-45bd-aaee-1e58c9bbd17a | compute-1    | e88b0889-4896-4a3a-af32-3d61361d59ec | power on    | active             | False       |
| 926edde5-165c-4901-9d87-fd689509eb3c | compute-0    | 0dbc20ff-fb35-4101-bbe7-44cde0b22a23 | power on    | active             | False       |
| 574a8b86-7c99-4b56-9263-899504257e22 | controller-2 | 649e962c-5fef-461e-a6d2-4123c2a56f0f | power on    | active             | False       |
| 7c72978b-c4da-4e0f-987c-a4d843eb8cca | controller-1 | 6ee499b3-78eb-4565-b902-e12adaa509e1 | power on    | active             | False       |
| 1e8a3760-5f08-4670-9127-9a7dcdc535fe | controller-0 | 26f22317-8de4-414e-a725-ae0d351fd4b8 | power on    | active             | False       |
+--------------------------------------+--------------+--------------------------------------+-------------+--------------------+-------------+
(undercloud) [stack@undercloud-0 ~]$ openstack overcloud generate fencing --ipmi-lanplus --ipmi-level administrator --output fencing.yaml instackenv.json
Comment 10 errata-xmlrpc 2017-12-13 16:29:42 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462

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