Comment 8 for bug 1721383

Summary of test cases for each bug:
For LP #1699789
The Ubuntu Xenial installer doesn't offer option to provide http/https proxy to be used by Landscape client when selecting "Manage system with Landscape" on upgrades management tasksel question. Therefore if system is placed behind proxy it will not be able to communicate with Landscape server. During system installation installer is asking user to provide proxy that is used by APT. It would be suitable that same proxy would be used for Landscape.

For LP #1208393
For a company that exclusively uses Landscape for software updates, it is also good practice to remove unneeded software.
On the shell, this can be achieved using "apt-get autoremove"
It would be desirable to have this functionality available in Landscape.

For LP #1618483
When running landscape-config, this prompt always defaults to Yes:
"Request a new registration for this computer now? (Y/n):"
The landscape-config command can be used to change configuration options in /etc/landscape/client.conf and should default to No when running this command on a computer that is already registered to a Landscape server and that server doesn't change during that run of landscape-config.

To reproduce:

1) Install landscape-client package on computer.
2) Run landscape-config to register client for the first time.
3) Run landscape-config again to change an option:
sudo landscape-config --ping-interval=60

For LP #1531150
The package reporter is not getting the proxy settings set in /etc/landscape/client.conf:
http_proxy = <your-proxy>
https_proxy = <your-proxy>

It will respect the environment variables if they are somehow set when landscape-client is started, but not if the values are just defined in that configuration file.
Clients can ping and broker exchanges work. There are ways the environment values can leak into the process and invalidate the test.
For example, if you have the http_proxy and https_proxy variables in root's environment, and restart the client, it will inherit those, and invalidate the test.
Or let's say you have them in ubuntu's environment, and use sudo to restart the client. They won't be propagated to the daemon by default unless -E is used, and/or the proxy variables are whitelisted in /etc/sudoers.