New install of snapd on RHEL 8.10. Working to get a CyberArk component installed.
With a CyberArk Consultant, we verified the network Requirements (References in comment)
This is where we stop. Out firewall/proxy teams are not seeing any traffic from our server outbound, and I cannot find any logging on the host that indicates the problem.
Can someone explain to me what is happening at this point of attempting to install hello-world? Where should it be reaching to? How can I validate my environment is configured correctly?
Our company runs Satellite for updates, so I don’t have any other resources to turn to internally for assistance.
Since you mentioned a proxy, have you set http_proxy & https_proxy in the snapd’s environment? You can run snap debug connectivity to check whether the snap store can be reached.
For the proxy topic, in our environment, servers only sit behind our firewall, workstations are funneled through the proxy. One of our Linux admins recommended that we have the proxy team put in a bypass. Our proxy team has not seen any instances of our server’s IP address in any of their logs.
I will look into setting the proxy in the environment, just to make sure.
Update - Since posting this:
Not sure what is occurring, but on another thread, I saw a reference to downloading hello-world, so I ran the following:
The handling of snap download works separately from any other snap command, it is a distinct and separate implementation (which causes other issues too) so you can not really compare its behavior to something like snap install or snap refresh which both use some internal way in snapd to handle the download while snap download is actually implemented directly in the snap command itself without the need to talk to the snapd server…
I believe alternative method to what @ogra suggested is to have a look at the snapd.service definition (systemctl cat snapd.service), there should be an Environment=... entry, which IIRC on Fedora/RHEL/CentOS references /etc/sysconfig/snapd. Then edit that file, add http_proxy & https_proxy entries, which are generally recognized as proxy settings by most programs (that’s likely why snap download worked for you, I’m guessing you already have those in your env. The entries should look like so:
http_proxy=<your-proxy>
https_proxy=<your-proxy>
save it, run systemctl restart snapd.service, verify with snap debug connectivity.
Thanks for all of the feedback and suggestions. I really appreciate your time.
I ran with @ogra proposed option first, and attempted the snap system proxy command, this resulted in a timeout error.
So then I edited my /etc/sysconfig/snapd file and restarted the service as described by @mborzecki1
These are the entries in my snapd, proxy team verified the addresses are the same for both. I tried it with and without the ports, received the same result.
