Skip to content

CI: Add Epoxy - #3368

Merged
EmilienM merged 1 commit into
gophercloud:mainfrom
shiftstack:add-epoxy
May 22, 2025
Merged

EmilienM merged 1 commit into
gophercloud:mainfrom
shiftstack:add-epoxy

Conversation

@stephenfin

@stephenfin stephenfin commented May 7, 2025 •

Copy link
Copy Markdown
Contributor

Per $subject. I will split this into multiple PRs if it ends up with loads of failures (like sadly suspect it will).

Update I've split this up:

@github-actions github-actions Bot added semver:patch No API change edit:actions This PR updates GitHub Actions code edit:testinfra This PR updates testing infrastructure code labels May 7, 2025
@coveralls

coveralls commented May 7, 2025 •

Copy link
Copy Markdown

Coverage Status

coverage: 63.828%. remained the same
when pulling 3bb3270 on shiftstack:add-epoxy
into 0d4b2d4 on gophercloud:main.

@stephenfin stephenfin changed the title CI: Add Epoxy, drop Bobcat CI: Add Epoxy May 12, 2025
@stephenfin
stephenfin force-pushed the add-epoxy branch 2 times, most recently from c5c87cf to cb18a35 Compare May 12, 2025 10:59
Comment thread .github/workflows/functional-containerinfra.yaml
Comment thread .github/workflows/functional-keymanager.yaml
@pierreprinetti pierreprinetti added backport-v1 This PR will be backported to v1 backport-v2 This PR will be backported to v2 labels May 16, 2025

@pierreprinetti pierreprinetti left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Maybe this can too run on 24.04?

We opt to run on Jammy for now due to to [1]. That's okay since Jammy is
a supported host for Epoxy [2]. We should migrate once [1] has been
resolved, however.

[1] https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2065685
[2] https://governance.openstack.org/tc/reference/runtimes/2025.1.html

Signed-off-by: Stephen Finucane <[email protected]>
@stephenfin

Copy link
Copy Markdown
Contributor Author

Maybe this can too run on 24.04?

We can't yet. From the commit message:

We opt to run on Jammy for now due to to [1]. That's okay since Jammy is
a supported host for Epoxy [2]. We should migrate once [1] has been
resolved, however.

[1] https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2065685
[2] https://governance.openstack.org/tc/reference/runtimes/2025.1.html

I've fixed this issue on master here. I've just proposed a backport to stable/2025.1 here but that could be a while getting in. I'd rather come back to this later.

@EmilienM
EmilienM dismissed pierreprinetti’s stale review May 22, 2025 12:08

Pierre approved it and then requested some change for the Ubuntu version, which was answered (not possible now); so it's good to go.

@EmilienM
EmilienM merged commit 9f4389e into gophercloud:main May 22, 2025
@EmilienM
EmilienM deleted the add-epoxy branch May 22, 2025 12:08
@github-actions

Copy link
Copy Markdown

Failed to backport PR to v1 branch. See logs for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-v1 This PR will be backported to v1 backport-v2 This PR will be backported to v2 edit:actions This PR updates GitHub Actions code edit:testinfra This PR updates testing infrastructure code semver:patch No API change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants