OCP 4: Canary route checks failing or canary route deployed with two routerCanonicalHostname entries with different domains

Issue

• On OpenShift 4, canary route checks are failing leading to degraded ingress operator state:

    message: 'The "default" ingress controller reports Degraded=True: DegradedConditions:
      One or more other status conditions indicate a degraded state: CanaryChecksSucceeding=False
      (CanaryChecksRepetitiveFailures: Canary route checks for the default ingress
      controller are failing)'

• On OpenShift 4, canary route shows multiple routerName fields or multiple routerCanonicalHostname entries showing a secondary domain address

• On OpenShift 4, Console access via curl or webpage may throw errors intermittently regarding common name being invalid, or mismatching the expected domain requested. (e.g. the certificate is invalid, expected *.apps, returned *.) or similar messaging.