Skip to content

Error out if the variant does not exist in git#764

Merged
openshift-merge-bot[bot] merged 3 commits into
validatedpatterns:mainfrom
mbaldessari:errorout-on-wrong-variant
Jul 9, 2026
Merged

Error out if the variant does not exist in git#764
openshift-merge-bot[bot] merged 3 commits into
validatedpatterns:mainfrom
mbaldessari:errorout-on-wrong-variant

Conversation

@mbaldessari

Copy link
Copy Markdown
Contributor

Tested with:

main:
  clusterGroupName: broken

And got:

conditions:
- lastTransitionTime: "2026-07-08T14:55:04Z"
  lastUpdateTime: "2026-07-08T14:56:05Z"
  message: 'required values file not found: values-broken.yaml'
  status: "True"
  type: Missing

Also tested with a correct clusterGroupName and got a correct
deployment.

@openshift-ci openshift-ci Bot requested review from OAharoni-RedHat and beekhof July 8, 2026 15:15
@openshift-ci

openshift-ci Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mbaldessari

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved label Jul 8, 2026
Tested with:

    main:
      clusterGroupName: broken

And got:

    conditions:
    - lastTransitionTime: "2026-07-08T14:55:04Z"
      lastUpdateTime: "2026-07-08T14:56:05Z"
      message: 'required values file not found: values-broken.yaml'
      status: "True"
      type: Missing

Also tested with a correct clusterGroupName and got a correct
deployment.
@mbaldessari mbaldessari force-pushed the errorout-on-wrong-variant branch from 71a3252 to b69714f Compare July 8, 2026 15:47
After git fetch, only refs/remotes/origin/<branch> is updated while
refs/heads/<branch> stays at the old commit. getCommitFromTarget was
checking the local branch ref first, so reconcile loops kept checking
out a stale commit even after new changes were pushed to the remote.

Reorder reference resolution to prefer the remote tracking ref, which
reflects the latest fetched state.
@darkdoc

darkdoc commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm label Jul 9, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit c67fb23 into validatedpatterns:main Jul 9, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants