I think this is intended behavior based on below commit

https://github.com/kubernetes-incubator/service-catalog/commit/ce28252dac9bb66e5fce5ac9cbd6f8cc8834e74c


Assume we need to make a tweak to openshift-ansible to handle the change.

https://github.com/openshift/openshift-ansible/pull/5899

I just notice the changes in latest ose-service-catalog image is that changed the binary name to "service-catalog" and added "<server>" for apiserver and controller-manager.

sh-4.2$ /usr/bin/service-catalog --help
This is an all-in-one binary that can run any of the various Kubernetes
service-catalog servers.

Usage

  service-catalog <server> [flags]

Servers

  apiserver
    The main API entrypoint and interface to the storage system. The API server
    is also the focal point for all authorization decisions.

  controller-manager
    The service-catalog controller manager is a daemon that embeds the core
    control loops shipped with the service catalog.

Call 'service-catalog --make-symlinks' to create symlinks for each server in the local directory.
Call 'service-catalog <server> --help' for help on a specific server.

So, please update daemonset configuration of apiserver and controller-manager in ansible-installer if the current change is you expect..

I will retry after PR merge https://github.com/openshift/openshift-ansible/pull/5899

Verified with openshift-ansible-3.7.0-0.185.0, the bug have been fixed. Thanks.

Verified and LGTM.

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/RHSA-2017:3188