"An error occurred while trying to load data. This could be due to temporary outage. You can retry the operation by clicking retry button" , when try to enable DRS

Products

• VMware vCenter Server 8.0

Issue/Introduction

• After upgrading the vCenter Server to a major version (e.g., from 7.0 to 8.0), users may experience an issue where the DRS option is grayed out or cannot be enabled.
• Error details like "Invalid query" or "HTTP response with status code 431 (enable debug logging for details): Request Header Fields Too Large" comes when trying to Edit the DRS settings

 

 

• Cluster services will be healthy.
• All vCenter services will be up and running.

From the /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log

Caused by: com. vmware. vapi. client. exception. TransportProtocolException: HTTP response with status code 431 (enable debug logging for details) : Request Header Fields Too Large
at com. vmware. vapi. internal. protocol. client. rpc.http. ApacheHttpUtil. validateHttpResponse (ApacheHttpUtil. java: 101)
at com. vmware. vapi. internal. protocol. client. rpc.http. handle. NioSingleResponseConsumer. responseCompleted (NioSingleResponseConsumer. java: 61)
at com. vmware. vapi. internal.protocol. client. rpc.http.handle. NioDecoratorConsumer. responseCompleted (NioDecoratorConsumer. java: 45)
at org. apache.http. impl.nio.client.MainClientExec. responseCompleted (MainClientExec. java : 383)
at org. apache. http. impl.nio.client.DefaultClientExchangeHandlerImpl. responseCompleted (DefaultClientExchangeHandlerImpl. java: 173)
at org. apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse (HttpAsyncRequestExecutor. java: 448)
at org. apache. http.nio.protocol. HttpAsyncRequestExecutor. inputReady (HttpAsyncRequestExecutor. java: 338)
at org. apache. http. impl.nio. DefaultNHttpClientConnection. consumeInput (DefaultNHttpClientConnection. java: 265)

Environment

VMware vCenter Server 8.x

Cause

This issue occurs due to browser caching of UI elements from the previous vCenter Server version. The cached elements from version 7.0 conflict with the new 8.0 interface components, causing unexpected behavior such as:

• Grayed out DRS settings.
• Unable to enable DRS.
• Grayed out login button.
• Appearance of deprecated UI elements.
• Inconsistent interface behavior.

Resolution

To resolve this issue:

Method 1:

1.  Clear the browser cache:
   1. For Chrome: Settings > Privacy and Security > Clear browsing data
   2. For Firefox: Options > Privacy & Security > Clear Data
   3. For Edge: Settings > Privacy, search, and services > Clear browsing data
2. Close all browser windows
3. Reopen the browser and access the vCenter Server web interface

Method 2:

1. Use an Incognito/Private browsing window to access the vCenter Server interface.
2. If issue still exists, restart the UI service on the vCenter: 
   • To stop the service: service-control --stop vsphere-ui
   • To start the service: service-control --start vsphere-ui

Method 3:

1. If none of the above works, consider restarting all the services of the vCenter: Stopping, Starting or Restarting VMware vCenter Server Appliance services
   • To stop the service: service-control --stop all
   • To start the service: service-control --start all

Additional Information

• This issue is specific to browser caching and does not indicate any problem with the vCenter Server installation or upgrade.
• The issue may affect some users but not others, depending on their browser cache state.
• For future upgrades, consider having users clear their browser cache immediately after the upgrade is completed.