packages.broadcom.com has no AAAA record / IPv6 support

[chrisnew]

Description of Issue/Question

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.

The core issue can be reproduced as shown below:

$ dig -t aaaa packages.broadcom.com

; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu <<>> -t aaaa packages.broadcom.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52388
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;packages.broadcom.com.		IN	AAAA

;; ANSWER SECTION:
packages.broadcom.com.	56	IN	CNAME	broadcom.jfrog.io.
broadcom.jfrog.io.	60	IN	CNAME	endpointdns-prod-usw2-lb.jfrog.io.
endpointdns-prod-usw2-lb.jfrog.io. 60 IN CNAME	k8s-jfrogsaa-jfrogsaa-5de72c2913-023a3012b9c76b9c.elb.us-west-2.amazonaws.com.

Versions and Systems

not applicable

[ScriptAutomate]

We've reached out to the Broadcom team that manages this, and will update this issue when more information is made available.

[chrisnew]

@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

[AxisNL]

Same here, I manage dozens of ipv6-only machines, got a problem connecting those. Disabled the repo for now.

[ScriptAutomate]

@chrisnew @AxisNL The team owning this started engaging with JFrog last week. No new updates on our end.

[pk-lms-dev]

Oh yes, IPv6 for the repo please!

[ichilton]

Any update on this? - I too have v6 only machines which are unable to access the repo.

[MEschenbacher]

I'd like to chime in, please support the current internet protocol version.

[ScriptAutomate]

Updates:

• 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.