instackenv.json pm_addr always 127.0.0.1

[Chris Jones]

I've done a few test deployments of oooq recently and noticed that in instackenv.json, the pm_addr is always 127.0.0.1.

I think this is incorrect, and it should actually be an IP address that's on the undercloud machine, since that is where vbmc is running?

[Chris Jones (cmsj)]

roles/libvirt/setup/overcloud/templates/instackenv.json.j2 gives the impression that it's intending to select an external IP address for the host_ip value.

[Ronelle Landy (rlandy)]

Please add more info on how you are running quickstart and what your test env consists of.
What is breaking?

[Chris Jones (cmsj)]

I was working on TripleO's fencing support (i.e. a HA deployment where overcloud controllers can power each other off if they become unresponsive) which configures Pacemaker to use IPMI to turn nodes off.

The 127.0.0.1 value meant that the nodes were trying to talk to themselves for IPMI, which afaics doesn't make any sense?

[Chris Jones (cmsj)]

(my env was a fairly stock quickstart, just set up to do an HA deployment. Is the 127.0.0.1 pm_addr normal? Or is that some weird side effect of something else I was doing?)

[Launchpad Janitor (janitor)]

[Expired for tripleo because there has been no activity for 60 days.]

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/509229

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/509229
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=f22d154c37610498d315981e3d2927f1ccdbe4aa
Submitter: Jenkins
Branch: master

commit f22d154c37610498d315981e3d2927f1ccdbe4aa
Author: Michele Baldessari <email address hidden>
Date: Tue Oct 3 19:08:19 2017 +0200

    pm_addr in instack should not be localhost

    Currently when oooq deploy the undercloud, the instack.json file
    has the following entries:
    ...
          "name": "compute-0",
          "pm_password": "password",
          "pm_type": "ipmi",
          "pm_user": "admin",
          "pm_addr": "127.0.0.1",
          "pm_port": "6233",
          "mac": [
            "00:a2:18:01:33:cf"
          ],
    ...

    While this works for ironic on the undercloud, it is problematic
    as soon as we use the instack.json to configure fencing for the
    overcloud. Let's replace 127.0.0.1 with the ip used by the undercloud.
    This way ironic on the undercloud keeps working and the fencing
    configuration that gets generated via 'overcloud generate fencing
    instack.json' is correct.

    Change-Id: I0727a9224b5e9eaafaa374ecfbcd4fb9ccb52d58
    Closes-Bug: #1656878

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-quickstart 2.1.1 release.