Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-7651

Add ClusterID to Login Banner

XMLWordPrintable

    • None
    • Future Sustainability
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request

      Add ClusterID to Login Banner

      2. What is the nature and description of the request?

      When building a new OCP cluster (with the same FQDN name), there are times when it seems like a previous install has been wiped out completely but somehow there is an issue that appears whether it is x509 error or one of the hosts booted off of an old image somehow.  To make troubleshooting these types of issues easier, could we add the random GUID of the cluster to the login banner at the console?

      3. Why does the customer need this? (List the business requirements here)

      During POCs that I participate in, there are times when a hard drive was not wiped completely and we go in circles trying to figure out which host is the culprit.  If all the machines showed the GUID of the cluster (based on the unique image that was built), this would help.

      Another possibility is perhaps showing this information for each host as we view the agent-install logs (wait-for bootstrap-complete for example) for each host or even add a check that all the hosts have the same cluster GUID when they reboot.

      4. List any affected packages or components.

      openshift-install binary
      assisted-installer tooling

              racedoro@redhat.com Ramon Acedo
              kcalliga@redhat.com Keith Calligan (Inactive)
              None
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                None
                None