cmd/openshift-install/gather: Guard against cluster-side artifact collisions #1836
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.
Support running multiple gather commands without cluster-side collisions. For example:
gather bootstrap, her command writes a tarball on the bootstrap machine and starts downloading it.gather bootstrap, his command starts writing to the same tarball on the bootstrap machine.But maybe Alice's download already has an open file descriptor, so Bob's clobber doesn't break the download? I guess it depends on the specifics of how
installer-gather.sh's> ~/log-bundle.tar.gzworked. With this pull request, we avoid potential issues by passing in an optional gather ID which the cluster-side scripts use to uniquify their collection directories. We still race if multiple gathers are launched in the same second, but that's at least a narrower window, and we can close it later by using a better source of random characters.