Severity
Blocking for a small number of customers
Version
2026.2.2237, not present in 2026.2.4069
Latest Version
The problem does not exist in the latest build
What happened?
If a project references an OIDC account and running in the V2 resilient pipeline, then the Git credentials needed to clone the Git repository are not persisted, making the Git repository clone fail for Argo CD steps.
Reproduction
- Add an Argo CD step (with valid Git credential)
- Add an Azure OIDC account variable to the same project
- Deploy
Error and Stacktrace
Found 1 Argo CD applications to update
Processing application update-image-tags-helm-octopub-test
Updating application source 'values-source'
No Git credentials found for: 'https://github.com/OctopusDeployTesting/frank-samples-argo-cd-gitops', will attempt to clone repository anonymously.
Cloning repository https://github.com/OctopusDeployTesting/frank-samples-argo-cd-gitops
Value cannot be null. (Parameter 'login')
System.ArgumentNullException
at Octokit.Ensure.ArgumentNotNull(Object value, String name) in /_/Octokit/Helpers/Ensure.cs:line 22
at Octokit.Ensure.ArgumentNotNullOrEmptyString(String value, String name) in /_/Octokit/Helpers/Ensure.cs:line 44
at Octokit.Credentials..ctor(String login, String password, AuthenticationType authenticationType) in /_/Octokit/Http/Credentials.cs:line 20
at Octokit.Credentials..ctor(String login, String password) in /_/Octokit/Http/Credentials.cs:line 16
More Information
This is due to a bug in equality comparison, causing the Git credentials to not be updated in the database.
Fixed by:
https://github.com/OctopusDeploy/OctopusDeploy/pull/41787, https://github.com/OctopusDeploy/OctopusDeploy/pull/41739, https://github.com/OctopusDeploy/OctopusDeploy/pull/41757
Workaround
Remove reference to OIDC account
Severity
Blocking for a small number of customers
Version
2026.2.2237, not present in 2026.2.4069
Latest Version
The problem does not exist in the latest build
What happened?
If a project references an OIDC account and running in the V2 resilient pipeline, then the Git credentials needed to clone the Git repository are not persisted, making the Git repository clone fail for Argo CD steps.
Reproduction
Error and Stacktrace
More Information
This is due to a bug in equality comparison, causing the Git credentials to not be updated in the database.
Fixed by:
https://github.com/OctopusDeploy/OctopusDeploy/pull/41787, https://github.com/OctopusDeploy/OctopusDeploy/pull/41739, https://github.com/OctopusDeploy/OctopusDeploy/pull/41757
Workaround
Remove reference to OIDC account