(FM-8784) Back out CentOS 8 from Travis CI tests #1270
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sheenaajay
approved these changes
Dec 11, 2019
(FM-8784) Back out CentOS 8, Puppet 6 tests from .travis.yml (FM-8784) Back out CentOS 8, Puppet 5 tests from .travis.yml
sanfrancrisko
force-pushed
the
FM-8784
branch
from
ac5c176 to
73fbe7c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Provisioning of CentOS 8 images using Docker, appears to be failing: https://travis-ci.org/puppetlabs/puppetlabs-mysql/builds/623152079
Encountered this locally too when provisioning via Docker, however, this may be a different issue where
rpm --rebuilddbwas failing on new containers: https://bugzilla.redhat.com/show_bug.cgi?id=1680124. I ran with a provision task that disabledrpm --rebuildb- this worked locally, but NOT on Travis.Further investigation and RCA is still required. In order to bypass a release blocker, we should disable the tests running on CentOS 8 and then re-enable when we have determined the root cause of the provisioning issue.