Smart doesn't import proxy information from Landscape
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Smart Package Manager |
Fix Released
|
Medium
|
Unassigned | ||
smart (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Intrepid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The Landscape Team has proposed an SRU to solve this bug.
This bug was supposed to be fixed by the smart intrepid SRU for Bug #236884 (version 1.1.1~bzr200810
=== 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.
=== How the bug has been addressed ===
Setting a smart configuration value in the Landscape smart plugin, that makes smart use the same proxy used in the Landscape configuration if any.
=== Detailed instructions how to reproduce the bug ===
Simply install landscape-client in an environment using a proxy.
Changed in smart: | |
status: | Fix Committed → Won't Fix |
Changed in smart: | |
status: | Won't Fix → Fix Released |
> Jaunty, Karmic and Lucid versions all have the patch already applied.
Closing lucid task then.