Bazel cannot reach to bcr.bazel.build from a ipv4 only machine with --host_jvm_args=-Djava.net.preferIPv6Addresses=true set
#21525
Assignees
Comments
meteorcloudy
added
P1
meteorcloudy
changed the title
--host_jvm_args=-Djava.net.preferIPv6Addresses=true setbcr.bazel.build from a ipv4 only machine with --host_jvm_args=-Djava.net.preferIPv6Addresses=true set
copybara-service bot
pushed a commit
that referenced
this issue
Feb 29, 2024
Bazel cannot reach to bcr.bazel.build from a ipv4 only machine with --host_jvm_args=-Djava.net.preferIPv6Addresses=true set. Our GCP VMs are ipv4 only and we recently enabled ipv6 for bcr.bazel.build. Related #21525 PiperOrigin-RevId: 611465054 Change-Id: I0c3d144d12ab167a18075e6719ff8597161798d1
iancha1992
pushed a commit
to iancha1992/bazel
that referenced
this issue
Feb 29, 2024
Bazel cannot reach to bcr.bazel.build from a ipv4 only machine with --host_jvm_args=-Djava.net.preferIPv6Addresses=true set. Our GCP VMs are ipv4 only and we recently enabled ipv6 for bcr.bazel.build. Related bazelbuild#21525 PiperOrigin-RevId: 611465054 Change-Id: I0c3d144d12ab167a18075e6719ff8597161798d1
meteorcloudy
added a commit
to meteorcloudy/bazel
that referenced
this issue
Mar 4, 2024
Bazel cannot reach to bcr.bazel.build from a ipv4 only machine with --host_jvm_args=-Djava.net.preferIPv6Addresses=true set. Our GCP VMs are ipv4 only and we recently enabled ipv6 for bcr.bazel.build. Related bazelbuild#21525 PiperOrigin-RevId: 611465054 Change-Id: I0c3d144d12ab167a18075e6719ff8597161798d1
github-merge-queue bot
pushed a commit
that referenced
this issue
Mar 4, 2024
…21546) Bazel cannot reach to bcr.bazel.build from a ipv4 only machine with --host_jvm_args=-Djava.net.preferIPv6Addresses=true set. Our GCP VMs are ipv4 only and we recently enabled ipv6 for bcr.bazel.build. Related #21525 PiperOrigin-RevId: 611465054 Change-Id: I0c3d144d12ab167a18075e6719ff8597161798d1
fweikert
pushed a commit
to fweikert/bazel
that referenced
this issue
Mar 5, 2024
Bazel cannot reach to bcr.bazel.build from a ipv4 only machine with --host_jvm_args=-Djava.net.preferIPv6Addresses=true set. Our GCP VMs are ipv4 only and we recently enabled ipv6 for bcr.bazel.build. Related bazelbuild#21525 PiperOrigin-RevId: 611465054 Change-Id: I0c3d144d12ab167a18075e6719ff8597161798d1
meteorcloudy
added a commit
that referenced
this issue
Mar 5, 2024
Bazel cannot reach to bcr.bazel.build from a ipv4 only machine with --host_jvm_args=-Djava.net.preferIPv6Addresses=true set. Our GCP VMs are ipv4 only and we recently enabled ipv6 for bcr.bazel.build. Related #21525 PiperOrigin-RevId: 611465054 Change-Id: I0c3d144d12ab167a18075e6719ff8597161798d1 Co-authored-by: Googler <pcloudy@google.com>
meteorcloudy
added
P2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug:
Recently, we enabled ipv6 support for bazel.build #21155
However, our CI revealed the issue described in the title.
The underlying problem is that with
--host_jvm_args=-Djava.net.preferIPv6Addresses=true:The problem is similar to #2486
https://buildkite.com/bazel/bazel-bazel/builds/27029
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Run
bazel --host_jvm_args=-Djava.net.preferIPv6Addresses=true build //...with Bzlmod enabled on a ipv4 only machine.Which operating system are you running Bazel on?
No response
What is the output of
bazel info release?No response
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: