Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v4.0-rhel] Cirrus: Use fixed netavark/aardvark-dns branch #14326

Conversation

cevich
Copy link
Member

@cevich cevich commented May 23, 2022

This is important for the stability of CI in case of a future backport
that happens to be incompatible with netavark/aardvark main. Since CI
doesn't run very often on the podman v4.0 branch, an incompatible change
may not be noticed. Fix this by switching off of the main branch onto
a netavark/aardvark release branches.

Does this PR introduce a user-facing change?

None

@cevich
Copy link
Member Author

cevich commented May 23, 2022

Note: This won't be significantly impacted by merge-order in relation to containers/aardvark-dns#143

@cevich
Copy link
Member Author

cevich commented May 23, 2022

Oof, I'm at a loss as to why validate fails here, where it passed just fine in the most recent merged PR.

@cevich cevich changed the title Cirrus: Use fixed netavark/aardvark-dns branch [v4.0-rhel] Cirrus: Use fixed netavark/aardvark-dns branch May 23, 2022
@cevich cevich force-pushed the fix_netavark-aardvark_branch branch from e55a0a2 to fc591a9 Compare May 23, 2022 19:03
Pascal Bourdier and others added 2 commits May 23, 2022 15:06
avoid this warn:
```
golangci/golangci-lint info installed ./bin/golangci-lint
golangci/golangci-lint err this script is deprecated, please do not use it anymore. check goreleaser/godownloader#207
```

Signed-off-by: Pascal Bourdier <[email protected]>
Signed-off-by: Chris Evich <[email protected]>
This is important for the stability of CI in case of a  future backport
that happens to be incompatible with netavark/aardvark `main`.  Since CI
doesn't run very often on the podman `v4.0` branch, an incompatible change
may not be noticed.  Fix this by switching off of the `main` branch onto
a netavark/aardvark release branches.

Signed-off-by: Chris Evich <[email protected]>
@cevich cevich force-pushed the fix_netavark-aardvark_branch branch from fc591a9 to 45d9aad Compare May 23, 2022 19:06
@cevich
Copy link
Member Author

cevich commented May 23, 2022

Oof, I'm at a loss as to why

Okay, validate should be fixed by backporting update to the installer script that was failing before.

Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
@containers/podman-maintainers PTAL

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 2, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cevich, vrothberg

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

The pull request process is described here

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 Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 2, 2022
@Luap99
Copy link
Member

Luap99 commented Jun 2, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 2, 2022
@openshift-merge-robot openshift-merge-robot merged commit dac9960 into containers:v4.0-rhel Jun 2, 2022
@cevich cevich deleted the fix_netavark-aardvark_branch branch April 18, 2023 14:48
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Aug 29, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note-none
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants