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

denylist: snooze podman.network-single on openstack #1144

Merged

Conversation

dustymabe
Copy link
Member

@dustymabe dustymabe commented Jul 28, 2021

See coreos/fedora-coreos-tracker#901

The problem comes and goes in the vexxhost environment. Let's wait
a month and see if it's better then.

@dustymabe
Copy link
Member Author

requires coreos/coreos-assembler#2324

See coreos/fedora-coreos-tracker#901

The problem comes and goes in the vexxhost environment. Let's wait
a month and see if it's better then.
@dustymabe dustymabe force-pushed the dusty-podman-network-single-openstack branch from 018d8bb to b711d6d Compare July 29, 2021 13:38
@dustymabe dustymabe changed the title denylist: deny podman.network-single on openstack denylist: snooze podman.network-single on openstack Jul 29, 2021
Copy link
Member

@jlebon jlebon left a comment

Choose a reason for hiding this comment

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

Should we get in touch with our contacts at VexxHost to check if they know anything?

@dustymabe
Copy link
Member Author

Should we get in touch with our contacts at VexxHost to check if they know anything?

I'd love to dig in and understand the particular failure but since it's only failing on one platform and 98 or 99 of 100 of the iterations of this particular test pass, I'm inclined to say we've got more important things to work on right now.

@jlebon jlebon merged commit 14d9684 into coreos:testing-devel Jul 30, 2021
@jlebon
Copy link
Member

jlebon commented Jul 30, 2021

Should we get in touch with our contacts at VexxHost to check if they know anything?

I'd love to dig in and understand the particular failure but since it's only failing on one platform and 98 or 99 of 100 of the iterations of this particular test pass, I'm inclined to say we've got more important things to work on right now.

Not saying we need to spend a lot of time trying to fix this. Snoozing is fine. But as cloud maintainers, they might be interested to know about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants