Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-1017

Can't cancel login when using multi-cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.12.z
    • 4.11.z
    • Management Console
    • None
    • Important
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      The {product-title} {product-version} solves an issue with the multicluster web console where if you failed to log in to your previous cluster session, you could not log in to another cluster from the same login window. The web console login window would timeout, regardless of you entering the correct credentials for the previous cluster session at a later stage.

      If you entered incorrect credentials for a cluster in the multicluster console on {product-title} {product-version}, the web console remembers your previous cluster session, so that the login window would not timeout. If you want to access another cluster session, you can open a new web browser window and then log in to this cluster from the {product-title} web console.


      [IMPORTANT]
      ====
      Multicluster console is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production.

      These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
      ====

      (link:https://issues.redhat.com/browse/OCPBUGS-1017[*OCPBUGS-1017*])
      Show
      The {product-title} {product-version} solves an issue with the multicluster web console where if you failed to log in to your previous cluster session, you could not log in to another cluster from the same login window. The web console login window would timeout, regardless of you entering the correct credentials for the previous cluster session at a later stage. If you entered incorrect credentials for a cluster in the multicluster console on {product-title} {product-version}, the web console remembers your previous cluster session, so that the login window would not timeout. If you want to access another cluster session, you can open a new web browser window and then log in to this cluster from the {product-title} web console. [IMPORTANT] ==== Multicluster console is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see link: https://access.redhat.com/support/offerings/techpreview/ [Technology Preview Features Support Scope]. ==== (link: https://issues.redhat.com/browse/OCPBUGS-1017 [* OCPBUGS-1017 *])
    • Done

      When multi-cluster is enabled, it possible to get in a situation where you can't cancel login. If you select a cluster you don't know the credentials for, console will remember the last cluster and repeatedly send you to the login page with no way to cancel or go back. If we decide to set the last cluster in the user's preferences, it might be possible to get stuck even if you clear cookies and localStorage.

      There are similar issues logging into cluster that are hibernating. See attached video.

      cc sberens@redhat.com

            rh-ee-jonjacks Jon Jackson
            spadgett@redhat.com Samuel Padgett
            YaDan Pei YaDan Pei
            Darragh Fitzmaurice Darragh Fitzmaurice
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: