Ambari
  1. Ambari
  2. AMBARI-2547

Security wizard: Successive refreshes at some point results in blank screen.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.5
    • Fix Version/s: 1.2.5
    • Component/s: ambari-web
    • Labels:

      Description

      This ticket addresses following issues:
      • Refreshing at the moment when none of the stage is running brings up blank screen. The time window for this is small. Once entered in this state, user needs to quit the wizard and go through the wizard again to enable security.
      • On Google chrome multiple refreshes occasionally cancels the request (snapshot_1.png). This calls ajax error callback function which sets the error flag and resets the request Id to its default value. Setting the error flag will mark the stage as failure and show retry button which can be accepted. But setting the request Id to its default value makes retry button fire a API for new request. We should persist the request Id to let the user poll on the same Id on hitting retry button. Ajax call error while polling request shouldn't reset requestId. Only task failures in the polled response data should reset request Id.
      • Refresh on the step2 (Configure Services) navigates to step1 of the wizard.
      • We keep persisting entire localDb on the server side with the help of an observable function. This is for multiple browser support. This is large amount of data and its noticed to have slower ui on refreshes as refresh calls the function multiple time. We need to isolate other data and persist only security wizard specific data on the server.
      1. AMBARI-2547.patch
        24 kB
        Jaimin D Jetly
      2. snapshot_1.png
        348 kB
        Jaimin D Jetly
      3. AMBARI-2547_2.patch
        25 kB
        Jaimin D Jetly

        Activity

        Jaimin D Jetly made changes -
        Status Patch Available [ 10002 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Jaimin D Jetly made changes -
        Description h5. This ticket addresses following issues:

        * Refreshing at the moment when none of the stage is running brings up blank screen. The time window for this is small. Once entered in this state, user needs to quit the wizard and go through the wizard again to enable security.
        * On Google chrome multiple refreshes occasionally cancels the request (snapshot_1.png). This calls ajax error callback function which sets the error flag and resets the request Id to its default value. Setting the error flag will mark the stage as failure and show retry button which can be accepted. But setting the request Id to its default value makes retry button fire a API for new request. We should persist the request Id to let the user poll on the same Id on hitting retry button. Ajax call error while polling request shouldn't reset requestId. Only task failures in the polled response data should reset request Id.
        * We keep persisting entire localDb on the server side with the help of an observable function. This is for multiple browser support. This is large amount of data and its noticed to have slower ui on refreshes as refresh calls the function multiple time. We need to isolate other data and persist only security wizard specific data on the server.
        h5. This ticket addresses following issues:

        * Refreshing at the moment when none of the stage is running brings up blank screen. The time window for this is small. Once entered in this state, user needs to quit the wizard and go through the wizard again to enable security.
        * On Google chrome multiple refreshes occasionally cancels the request (snapshot_1.png). This calls ajax error callback function which sets the error flag and resets the request Id to its default value. Setting the error flag will mark the stage as failure and show retry button which can be accepted. But setting the request Id to its default value makes retry button fire a API for new request. We should persist the request Id to let the user poll on the same Id on hitting retry button. Ajax call error while polling request shouldn't reset requestId. Only task failures in the polled response data should reset request Id.
        * Refresh on the step2 (Configure Services) navigates to step1 of the wizard.
        * We keep persisting entire localDb on the server side with the help of an observable function. This is for multiple browser support. This is large amount of data and its noticed to have slower ui on refreshes as refresh calls the function multiple time. We need to isolate other data and persist only security wizard specific data on the server.
        Jaimin D Jetly made changes -
        Attachment AMBARI-2547_2.patch [ 12590718 ]
        Jaimin D Jetly made changes -
        Description h5. This ticket addresses following issues:

        * Refreshing at the moment when none of the stage is running brings up blank screen. The time window for this is small. Once entered in this state, user needs to quit the wizard and go through the wizard again to enable security.
        * On Google chrome multiple refreshes occasionally cancels the request (snapshot_1). This calls ajax error callback function which sets the error flag and resets the request Id to its default value. Setting the error flag will mark the stage as failure and show retry button which can be accepted. But setting the request Id to its default value makes retry button fire a API for new request. We should persist the request Id to let the user poll on the same Id on hitting retry button. Ajax call error while polling request shouldn't reset requestId. Only task failures in the polled response data should reset request Id.
        * We keep persisting entire localDb on the server side with the help of an observable function. This is for multiple browser support. This is large amount of data and its noticed to have slower ui on refreshes as refresh calls the function multiple time. We need to isolate other data and persist only security wizard specific data on the server.
        h5. This ticket addresses following issues:

        * Refreshing at the moment when none of the stage is running brings up blank screen. The time window for this is small. Once entered in this state, user needs to quit the wizard and go through the wizard again to enable security.
        * On Google chrome multiple refreshes occasionally cancels the request (snapshot_1.png). This calls ajax error callback function which sets the error flag and resets the request Id to its default value. Setting the error flag will mark the stage as failure and show retry button which can be accepted. But setting the request Id to its default value makes retry button fire a API for new request. We should persist the request Id to let the user poll on the same Id on hitting retry button. Ajax call error while polling request shouldn't reset requestId. Only task failures in the polled response data should reset request Id.
        * We keep persisting entire localDb on the server side with the help of an observable function. This is for multiple browser support. This is large amount of data and its noticed to have slower ui on refreshes as refresh calls the function multiple time. We need to isolate other data and persist only security wizard specific data on the server.
        Jaimin D Jetly made changes -
        Description h5. This ticket addresses following issues:

        * Refreshing at the moment when none of the stage is running brings up blank screen. The time window for this is small. Once entered in this state, user needs to quit the wizard and go through the wizard again to enable security.
        * On Google chrome multiple refreshes occasionally cancels the request. This calls ajax error callback function which sets the error flag and resets the request Id to its default value. Setting the error flag will mark the stage as failure and show retry button which can be accepted. But setting the request Id to its default value makes retry button fire a API for new request. We should persist the request Id to let the user poll on the same Id on hitting retry button. Ajax call error while polling request shouldn't reset requestId. Only task failures in the polled response data should reset request Id.
        * We keep persisting entire localDb on the server side with the help of an observable function. This is for multiple browser support. This is large amount of data and its noticed to have slower ui on refreshes as refresh calls the function multiple time. We need to isolate other data and persist only security wizard specific data on the server.
        h5. This ticket addresses following issues:

        * Refreshing at the moment when none of the stage is running brings up blank screen. The time window for this is small. Once entered in this state, user needs to quit the wizard and go through the wizard again to enable security.
        * On Google chrome multiple refreshes occasionally cancels the request (snapshot_1). This calls ajax error callback function which sets the error flag and resets the request Id to its default value. Setting the error flag will mark the stage as failure and show retry button which can be accepted. But setting the request Id to its default value makes retry button fire a API for new request. We should persist the request Id to let the user poll on the same Id on hitting retry button. Ajax call error while polling request shouldn't reset requestId. Only task failures in the polled response data should reset request Id.
        * We keep persisting entire localDb on the server side with the help of an observable function. This is for multiple browser support. This is large amount of data and its noticed to have slower ui on refreshes as refresh calls the function multiple time. We need to isolate other data and persist only security wizard specific data on the server.
        Jaimin D Jetly made changes -
        Attachment snapshot_1.png [ 12590680 ]
        Jaimin D Jetly made changes -
        Description h5. This ticket addresses following issues:

        * Refreshing at the moment when none of the stage is running brings up blank screen. The time window for this is small. Once entered in this state, user needs to quit the wizard and go through the wizard again to enable security.
        * On Google chrome multiple refreshes occasionally cancels the request. This calls ajax error callback function which sets the error flag and resets the request Id to its default value. Setting the error flag will mark the stage as failure and show retry button which can be accepted. But setting the request Id to its default value makes retry button fire a API for new request. We should persist the request Id to let the user poll on the same Id on hitting retry button. Ajax call error while polling request shouldn't reset requestId. Only task failures in the polled response data should reset request Id.
        * We keep persisting entire localDb on the server side with the help of an observable function. This is for multiple browser support. This is large amount of data and its noticed to have slower ui on refreshes as refresh calls the function multiple time. We need to isolate other data and persist only security wizard specific data on the server.
        Jaimin D Jetly made changes -
        Status Open [ 1 ] Patch Available [ 10002 ]
        Jaimin D Jetly made changes -
        Field Original Value New Value
        Attachment AMBARI-2547.patch [ 12590601 ]
        Jaimin D Jetly created issue -

          People

          • Assignee:
            Jaimin D Jetly
            Reporter:
            Jaimin D Jetly
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development