Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Other: HVR UI Update to show correct version of Agent

Answered
Siju Michael User

After upgrading the HVR version and the agents. The UI is still showing the older version or incorrect version of agent. The suspected reason is the UI is not updated with correct value present in the repo DB.

  1. UI --> Repo DB  (Bidirectional call for make all in sync)
  2. Agent or Hub --> Repo DB (Bidirectional call for making all in sync)
  3. Agent changes in #2 call are reflected into Repo DB, but not back to #1 to reflect in UI without any explicit refresh action from UI.

 

Imaging from a customer view who uses only UI and handles operations in production without deep knowledge on how HVR works, it’s a panic situation for any debugging activities once you spot 2 different values.

  1. Similar to status checks for license or fetch calls happening on hub, it will be good idea to update the agent version back to UI to avoid this. (Depending on the TTL of the call and response payload volume vs what is currently in performance metrics of each API calls from UI to DB)
  2. Add some more details about what to do on refresh only jobs in the upgrade procedure documentations.

More details on the UI calls and why its not reflecting or use cases involved can be found from the support ticket # 29984

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Mark Van de Wiel User

    Siju,

    Thank you for sharing your concern.

    For any one of the locations HVR stores a number of discovered properties in the hvr_location_property table. Every time we reconnedt to the location we validate and update these. The UI picks up the values from the table.

    It may be that an upgrade was performed on the source without restarting agent listener and/or capture/integrate process. In that case updating the discovered property would be delayed until the next reconnect.

    If you have access to the HVR repository database, could you run the following query substituting your hub name and location name:

    select prop_value,
    insert_tstamp
    , delete_tstamp
    from hvr_location_property
    where hub_name = '<hub name>'
    and loc_name = '<location name>'
    and prop_name = 'Agent_Version' ;

    See if that value was updated post update and after processes have been restarted. If you still see a discrepancy in the UI after refreshing the window then please file a support ticket as it would be a bug.

    Thanks,
    Mark.