Comment 13 for bug 236884

This just happened to a real customer. shang debugged it and indeed it was a missing proxy setting for smart. The "smart update" cronjob was always stuck at this customer.

The customer said he did configure a proxy via landscape-config, but that smart didn't get that setting.