We've hit this problem as well on the current stable branch, and will be trying to work around it by deploying landscape and dependencies to a separate "landscape" model where we can set the legacy-style proxy settings with limited impact to other apps.
Also, it's worth noting that this issue is kind of "hidden". What I mean is: the charm is effectively broken once the add-apt-repository call fails, yet that just causes a blocked status and it's not until several hooks later that things "really" break. We happened to check "juju show-status-log $unit" and could find the root cause there.
We've hit this problem as well on the current stable branch, and will be trying to work around it by deploying landscape and dependencies to a separate "landscape" model where we can set the legacy-style proxy settings with limited impact to other apps.
Also, it's worth noting that this issue is kind of "hidden". What I mean is: the charm is effectively broken once the add-apt-repository call fails, yet that just causes a blocked status and it's not until several hooks later that things "really" break. We happened to check "juju show-status-log $unit" and could find the root cause there.