Confusing 'Skipping "horizon" postconfig' message printed

[Jiří Stránský]

A message gets printed when deploying overcloud:

Skipping "horizon" postconfig because it wasn't found in the endpoint map output

This can generate false alarms among users, as the message looks like something went wrong but in fact it didn't. We don't need horizon endpoints for anything nowadays, it was only for Tuskar UI.

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/357039
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=390ab1d9b41902f933e3c5b108c521a1c2a988a5
Submitter: Jenkins
Branch: master

commit 390ab1d9b41902f933e3c5b108c521a1c2a988a5
Author: Jiri Stransky <email address hidden>
Date: Thu Aug 18 11:05:58 2016 +0200

    Don't alarm users with "skipping postconfig" messages

    On each overcloud deploy we printed a message like:

        Skipping "horizon" postconfig because it wasn't found in the
        endpoint map output

    and in trunk with composable services we now print even more of
    these. Such messages are slightly confusing because it looks like
    something went wrong when in fact everything's fine. The fix is twofold:

    1) Only print the "skipping postconfig" messages in debug mode.

    2) Remove Horizon from the services list. It's not customary to create a
       service entry and endpoints in Keystone for Horizon (after all it's
       not an API). We only used to create that endpoint because it was a
       requirement of Tuskar UI.

    Change-Id: I1ac30419104cd66312cd9aec7cc1ace867d1df4b
    Closes-Bug: #1614115

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-tripleoclient 5.0.0 release.