Revert "Revert "Revert "Revert "Revert "Use Consistent Volume Size Across All Prod Instances""""" #69320
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.
Reverts #69308
This time, the upsize itself was successful! We updated Ubuntu and kicked off a build on the new volume as planned.
Unfortunately, this process revealed an existing issue in our stack right now; we have a circular dependency in the build between the creation of the web service and the creation of a
newrelic.ymlconfig file. This will only manifest when creating a new production server from scratch, which unfortunately means it manifests here.See thread here
Reverting this change so we can deploy a fix to that underlying problem.