You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
packages.broadcom.com has no AAAA record / IPv6 support #67051
After discovering the sudden and fun breaking change (salt-bootstrap:#2027) of deprecating repo.saltstack.io recently, we tried to follow the community’s effort to patch the install script and to install salt manually. However, some of our infrastructure is IPv6-only.
Setup
IPv6-only deployment.
Steps to Reproduce Issue
Try to install salt-minion from packages.broadcom.com in an IPv6-only network.
@ScriptAutomate thanks! Do you have already feedback from them? One of my clients has severe issues right now and we are duct taping the fun out of these sites 😕 The reason being Cannot initiate the connection to packages.broadcom.com:443 (100.21.156.46). - connect (101: Network is unreachable) completely breaks the ability to upgrade and install things on Debian
No changes have been made to packages.broadcom.com
Internal teams at Broadcom are aware of this issue: they have no estimated date upon when they'd have changes implemented
Expect that any new updates may take several months
The Salt Project team is unable to assist further at this time. I will only update this issue when we get more relevant updates from Broadcom teams internally in regard to this issue.
For those that are Broadcom / VMware by Broadcom customers: we recommend opening a ticket with support about this issue, as that will help raise further awareness and priority internally as they track impacted customers.
After further investigation, found that JFrog SaaS infra is not configured to support IPv6 - leaving Broadcom dependent on changes via JFrog
Confirmed with JFrog, through support contact, that they indeed do not currently support IPv6 as an option but are aware of the need (already had an internal backlog item for it). Though, they have no ETA on implementation and will be providing no estimate
For those that are Broadcom / VMware by Broadcom customers: we recommend opening a ticket with Broadcom support about this issue, as that will help raise further awareness as they track impacted customers
Since the Salt Project Team is unable to take further action at this time, we are going to close this ticket as not planned / won't fix.
Speaking of IPv6 support: I'm sharing here in this issue thread a link to a feature request I've submitted for GitHub since there have been users reporting problems using some services/endpoints/features of GitHub. Sharing for awareness.
Still an issue - how difficult can it be to assign an IPv6 address in AWS?
packages.broadcom.com is an alias for broadcom.jfrog.io.
broadcom.jfrog.io is an alias for endpointdns-prod-usw2-lb.jfrog.io.
endpointdns-prod-usw2-lb.jfrog.io is an alias for k8s-jfrogsaa-jfrogsaa-5de72c2913-023a3012b9c76b9c.elb.us-west-2.amazonaws.com.
k8s-jfrogsaa-jfrogsaa-5de72c2913-023a3012b9c76b9c.elb.us-west-2.amazonaws.com has address 54.185.186.5
k8s-jfrogsaa-jfrogsaa-5de72c2913-023a3012b9c76b9c.elb.us-west-2.amazonaws.com has address 100.21.156.46
k8s-jfrogsaa-jfrogsaa-5de72c2913-023a3012b9c76b9c.elb.us-west-2.amazonaws.com has address 44.226.59.123
Activity
ScriptAutomate commentedon Nov 12, 2024
We've reached out to the Broadcom team that manages this, and will update this issue when more information is made available.
[-]packages.broadcom.com has no AAAA record[/-][+]packages.broadcom.com has no AAAA record / IPv6 support[/+]chrisnew commentedon Nov 25, 2024
@ScriptAutomate thanks! Do you have already feedback from them? One of my clients has severe issues right now and we are duct taping the fun out of these sites 😕 The reason being
Cannot initiate the connection to packages.broadcom.com:443 (100.21.156.46). - connect (101: Network is unreachable)completely breaks the ability to upgrade and install things on DebianAxisNL commentedon Nov 25, 2024
Same here, I manage dozens of ipv6-only machines, got a problem connecting those. Disabled the repo for now.
ScriptAutomate commentedon Nov 26, 2024
@chrisnew @AxisNL The team owning this started engaging with JFrog last week. No new updates on our end.
pk-lms-dev commentedon Dec 4, 2024
Oh yes, IPv6 for the repo please!
ichilton commentedon Dec 12, 2024
Any update on this? - I too have v6 only machines which are unable to access the repo.
MEschenbacher commentedon Dec 29, 2024
I'd like to chime in, please support the current internet protocol version.
ScriptAutomate commentedon Jan 15, 2025
Updates:
packages.broadcom.comThe Salt Project team is unable to assist further at this time. I will only update this issue when we get more relevant updates from Broadcom teams internally in regard to this issue.
For those that are Broadcom / VMware by Broadcom customers: we recommend opening a ticket with support about this issue, as that will help raise further awareness and priority internally as they track impacted customers.
ScriptAutomate commentedon Jan 30, 2025
Updates:
Since the Salt Project Team is unable to take further action at this time, we are going to close this ticket as not planned / won't fix.
ScriptAutomate commentedon Feb 14, 2025
Speaking of IPv6 support: I'm sharing here in this issue thread a link to a feature request I've submitted for GitHub since there have been users reporting problems using some services/endpoints/features of GitHub. Sharing for awareness.
mattgroves commentedon Jun 19, 2025
Still an issue - how difficult can it be to assign an IPv6 address in AWS?