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

Fix buildah retry mechanism #681

Merged
merged 1 commit into from
Jun 11, 2024

Conversation

xDaile
Copy link
Contributor

@xDaile xDaile commented Jun 4, 2024

CLOUDDST-22677
CLOUDDST-21131

Buildah retry mechanism fix:

  • Regex repaired in a way, it can accept old messages too

lipoja
lipoja previously approved these changes Jun 5, 2024
@xDaile xDaile force-pushed the buildah_retry_fix branch 5 times, most recently from 773a54d to 34b3ee6 Compare June 10, 2024 13:29
@xDaile xDaile force-pushed the buildah_retry_fix branch from 34b3ee6 to 5ab3dc8 Compare June 11, 2024 10:17
@xDaile xDaile merged commit 2380e21 into release-engineering:master Jun 11, 2024
2 checks passed
network_regexes = [
r'.*([e,E]rror:? creating build container).*(:?(50[0-9]|125)\s.*$)',
r'.*(read\/write on closed pipe.*$)',
]

Choose a reason for hiding this comment

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

Have you considered to get regular expressions from config file?
So one needn't deploy new version of IIB just to retry new network issue reported by buildah

Copy link
Contributor Author

@xDaile xDaile Jun 11, 2024

Choose a reason for hiding this comment

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

@lipoja what do you think?

IMO those network issues error messages are not changing that fast, so we would need to have that in config.

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.

5 participants