[ https://issues.apache.org/jira/browse/RATIS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser reopened RATIS-672: ------------------------------ Reopening as I reverted the change. https://builds.apache.org/job/PreCommit-RATIS-Build/1014/console shows a failure message similar to what you mentioned, Clay. {noformat} Step 12/24 : RUN mkdir -p $HOME/protobuf && cd $HOME/protobuf && wget --continue "${ratis_protoc_url:?Need \$ratis_protoc_url}" && if [ "$(sha256sum "${ratis_protoc_file:?Need \$ratis_protoc_file}")" != "${ratis_protoc_sum:?Need \$ratis_protoc_sum} $ratis_protoc_file" ]; then echo "Checksum failed for $ratis_protoc_file" > /dev/stderr && exit 1; fi && unzip "$ratis_protoc_file" && mv $HOME/protobuf/bin/protoc /usr/local/bin && chmod 755 /usr/local/bin/protoc ---> Running in 5e9b84f37c43 /bin/sh: 1: ratis_protoc_url: Need $ratis_protoc_url The command '/bin/sh -c mkdir -p $HOME/protobuf && cd $HOME/protobuf && wget --continue "${ratis_protoc_url:?Need \$ratis_protoc_url}" && if [ "$(sha256sum "${ratis_protoc_file:?Need \$ratis_protoc_file}")" != "${ratis_protoc_sum:?Need \$ratis_protoc_sum} $ratis_protoc_file" ]; then echo "Checksum failed for $ratis_protoc_file" > /dev/stderr && exit 1; fi && unzip "$ratis_protoc_file" && mv $HOME/protobuf/bin/protoc /usr/local/bin && chmod 755 /usr/local/bin/protoc' returned a non-zero code: 2 {noformat} I thought the docker side of this change was of little consequence -- I guess not :) > Vagrant and Docker Test 404 on Maven Download > --------------------------------------------- > > Key: RATIS-672 > URL: https://issues.apache.org/jira/browse/RATIS-672 > Project: Ratis > Issue Type: Improvement > Components: test > Reporter: Clay B. > Assignee: Clay B. > Priority: Trivial > Fix For: 0.5.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > The Vagrant tests are > [pointing|https://github.com/apache/incubator-ratis/blob/35838f032a4096d78843130fa1435bcddf5ce961/dev-support/vagrant/Vagrantfile#L92] > to a specific mirror and a URL which broke with the new Maven 3.6.x release. > We should point to an {{archive.apache.org}} URL if I understand correctly. -- This message was sent by Atlassian Jira (v8.3.4#803005)