Open mreed8855 opened 9 years ago
Hey Mike - apologies for the delayed response. We've made significant changes to the way jujuresources deals with proxies. We may get lucky and have your issue fixed as well. These fixes are are available in jujuresources >= 0.3.0 and jujubigdata >= 4.5.0. All of the the Apache-based big data charms in the ~bigdata-dev namespace have been updated to use this library:
https://jujucharms.com/u/bigdata-dev/#charms
At your convenience, would you refresh your local charms with the latest from the ~bigdata-dev namespace and try your deployment again? Also, please pass along any proxy config from the machine where you're running juju:
$ env | grep -i proxy
Thanks!
Currently I am having issues using juju-resources to access resources on a local mirror on a restricted system during a hadoop deployment. The issue may be due to multiple charms attempting to connect to a single mirror.
Here is the deployer file of the configuration I am attempting: -https://pastebin.canonical.com/139163/
The following is an example of the config.yaml file used for the charms: -https://pastebin.canonical.com/139161/
Verification of the resources: -https://pastebin.canonical.com/139157/
Log of the successful and failed connections: -https://pastebin.canonical.com/139160/
Resource.yaml file: (all of the resource.yaml files are the same) -https://pastebin.canonical.com/139162/