Troubleshooting issues

Red Hat OpenShift GitOps 1.21

Troubleshooting topics for OpenShift GitOps and your cluster

Red Hat OpenShift Documentation Team

Abstract

This document provides information about how to troubleshoot issues in OpenShift GitOps.

Chapter 1. Auto-reboot during Argo CD sync with machine configurations

When using the Machine Config Operator (MCO) with Argo CD GitOps workflows, node reboots triggered by machine configuration changes can interrupt application synchronization and impact performance. This can occur when the MCO reboots a node that hosts the Argo CD application controller, terminating an active sync operation. Prevent these interruptions and ensure that the MCO and Argo CD work together reliably.

1.1. Enhance performance in machine configurations and Argo CD

Using the Machine Config Operator (MCO) with Argo CD GitOps workflows can impact performance when node reboots interrupt synchronization operations.

1.1.1. Problem description

The following sequence leads to synchronization failures and performance degradation:

  1. Argo CD starts an automated sync after a commit to the Git repository that contains application resources.
  2. If Argo CD detects a new or updated machine configuration during the sync, the MCO applies the change and begins rebooting nodes.
  3. If a rebooting node hosts the Argo CD application controller, the controller terminates and the sync is aborted.

Because the MCO reboots nodes sequentially and Argo CD workloads can be rescheduled during each reboot, synchronization takes significant time to complete. This results in unpredictable behavior until the MCO finishes rebooting all affected nodes.

1.1.2. Solution

To prevent node reboots from interrupting Argo CD sync operations, use one of the following approaches:

  • Sync waves: Configure Argo CD sync waves to apply machine configurations in a separate phase from application resources.
  • Manual sync: Disable automatic syncing for machine configurations and trigger syncs during maintenance windows.
  • Resource hooks: Use Argo CD resource hooks to control when machine configurations are applied.

For implementation details, see the additional resources section.

1.2. Additional resources

Legal Notice

Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.
The OpenStack® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.
All other trademarks are the property of their respective owners.