Troubleshooting Red Spinning Cog and Configuration Delays in Akuity ArgoCD

Understanding potential causes and resolutions for instance configuration delays and permission errors in Akuity ArgoCD.

Red Spinning Cog & Configuration Delays

• If you see a red spinning cog along with the message "Configuring the instance is taking too long," it is likely due to:
  • A transient issue or a delay in scheduling pods.
  • Recent configuration changes, which can trigger pod cycling on Akuity’s end.
  • Pod restarts taking longer than expected.
• Akuity runs everything in an HA (High Availability) configuration, but certain operations—such as instance creation—may still be impacted by delays or issues, potentially preventing the instance from starting.

Permission Errors in ArgoCD

• Dex Pod Restarts: If you were experiencing permission errors in ArgoCD, it may have been due to Dex pods restarting, indicating a transient issue.
• HA Maintenance: Despite some pods restarting, timestamps indicate HA was maintained, so errors inside ArgoCD were unexpected.