replace tectonicClusterID tag with openshiftClusterID

[staebler]

The tectonicClusterID tag is being replaced with openshiftClusterID in the installer. This change will use the new tag name.

Hold on openshift/installer#817.

/hold

[pravisankar]

/lgtm

[ironcladlou]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ironcladlou, pravisankar, staebler

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [ironcladlou]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[staebler]

/hold cancel

[staebler]

/retest

[ironcladlou]

Users are reporting a private zone discovery failure; pretty sure this change has broken wildcard DNS management:

time="2018-12-11T16:16:51Z" level=error msg="failed to reconcile: failed to ensure clusteringress openshift-ingress-operator/default: failed to ensure DNS for router service openshift-ingress/router-default: failed to find private zone for cluster"

Unfortunately e2e testing of the feature is still in-progress.

[ironcladlou]

Still investigating — my latest cluster has the right tags on the zones, so these users could be using out of date installers or resources.

[ironcladlou]

Solved. In the reported cases, an updated release payload was being deployed to an old cluster platform. The users needed to create a cluster with a new installer version.