** Description changed:
+ The Landscape Team has proposed an SRU to solve this bug.
+
+ Statement explaining the impact
+ =====================
+
It's possible to have a client machine in a situation where landscape
itself is using a proxy, but not smart. In networks where the only way
out is via a proxy, this means that that machine would never be able to
perform package operations, nor report the packages it has installed and
available.
Even if smart checks the http_proxy env var, it's entirely possible the
admin didn't set it. A contributing factor is that the landscape-config
wizard explicitly asks for a proxy, so it's not unreasonable for the
admin to assume smart would be setup too.
- I suggest to have landscape-config also set the proxy for smart if one
- is set for landscape.
+ How the bug has been addressed
+ ======================
+
+ Introducing a new smart plugin that inherits the proxy settings from the
+ landscape-client configuration file.
+
+ Detailed instructions how to reproduce the bug
+ ==============================
+
+ Simply install landscape-client in an environment using a proxy.
** Changed in: smart (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: landscape-client (Ubuntu)
Status: Invalid => Fix Committed
** Changed in: landscape-client
Status: Invalid => Fix Released
** Changed in: landscape
Status: Invalid => Fix Released
--
need to set proxy for smart too
https://bugs.launchpad.net/bugs/236884
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
