Replies: 3 comments 2 replies
-
it is mind boggling that there is no 301 redirect setup for this move form salt project. where have common sense gone? |
Beta Was this translation helpful? Give feedback.
1 reply
-
How do you fix this within a debian network install? Would following this guide get so-setup woring? Is the salt repo a variable in so-setup....Can we the change DNS address in one place? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Version
2.4.10
Installation Method
Network installation on Ubuntu (unsupported)
Description
installation
Installation Type
Standalone
Location
on-prem with Internet access
Hardware Specs
Exceeds minimum requirements
CPU
16
RAM
32GB
Storage for /
1TB
Storage for /nsm
1TB
Network Traffic Collection
tap
Network Traffic Speeds
1Gbps to 10Gbps
Status
Yes, all services on all nodes are running OK
Salt Status
Yes, there are salt failures (please provide detail below)
Logs
Yes, there are additional clues in /opt/so/log/ (please provide detail below)
Detail
The Salt Project has migrated its package repositories from repo.saltproject.io to packages.broadcom.com.
Since repo.saltproject.io is no longer available, network installations are failing.
Repository Migration:
Deprecated Repo: repo.saltproject.io
New Repo: packages.broadcom.com
Recommendations:
Update Repository Configurations: Modify your system's package manager configurations to point to the new repository URLs.
References:
https://saltproject.io/blog/
Upcoming bootstrap subdomain decommission
FAQs from Salt Project Repo Migration
Has anyone seen plans about Security Onion editing the install config? How can we proceed with network installations?
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions