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
after the system was bootstrapped to uyni, the susemanager generated repository to include a proxy parameter::
[susemanager:rhel-9-for-x86_64-appstream-uyuni]
name=Red Hat Enterprise Linux 9 Server - BaseOS
enabled=1
baseurl=XXXXXXXXXXXXXX
susemanager_token=YYYYYYYY
gpgcheck=0
repo_gpgcheck=0
type=rpm-md proxy=_none_ or to be able to add a specific proxy to
The text was updated successfully, but these errors were encountered:
Can you share more about the use case for this proxy parameter?
We have quiet a lot of systems that are accessing other webapps through a http/https proxy
[susemanager:rhel-8-for-x86_64-appstream-uyuni]
name=RedHat Enterprise Linux 8 AppStream (x86_64)
enabled=1
baseurl=https://uyuni-proxy02.domain.loc:443/rhn/manager/download/rhel-8-for-x86_64-appstream-uyuni
susemanager_token=xxxxxxxxxxxxxxxxxxxxxx
gpgcheck=0
repo_gpgcheck=0
type=rpm-md
proxy=_none_
Now, if we don't add proxy=_none_ to the repo, the yum update will timeout. The workaround for now, is just to apply a scheduled highstate, that appends that line to "susemanager:channels.repo"
Short description
after the system was bootstrapped to uyni, the susemanager generated repository to include a proxy parameter::
[susemanager:rhel-9-for-x86_64-appstream-uyuni]
name=Red Hat Enterprise Linux 9 Server - BaseOS
enabled=1
baseurl=XXXXXXXXXXXXXX
susemanager_token=YYYYYYYY
gpgcheck=0
repo_gpgcheck=0
type=rpm-md
proxy=_none_ or to be able to add a specific proxy to
The text was updated successfully, but these errors were encountered: