[Release 1.3.3] Proxy configuration about bosh-oneagent-release HOT 7 CLOSED

Can you share an exemplary runtime-config which reflects your configuration?
So we can try to reproduce this properly on our end.

from bosh-oneagent-release.

Hi,

thanks for your reply. We have the following setting in runtime-config which is working with 1.3.2 when we switch to 1.3.3 the agent download is working with proxy but it seems the agent is not using the proxy to deliver the data to dynatrace. The agent is asking the local DNS server instead of using the configured proxy to reach the remote dynatrace server.

- name: dynatrace-oneagent-addon
  jobs:
  - name: dynatrace-oneagent
    release: dynatrace-oneagent
  include:
    deployments:
    - cf
    stemcell:
    - os: ubuntu-xenial
  exclude:
    lifecycle: errand
  properties:
    dynatrace:
      environmentid: "((iaas.dynatrace.environmentid))"
      apitoken: "((/dynatrace_oneagent_apitoken))"
      apiurl: https://((iaas.dynatrace.apihost))/e/((iaas.dynatrace.environmentid))/api
      hostgroup: "((iaas.cf.system_domain))"
      infraonly: 0
      validatedownload: false
      proxy: "((http_proxy))"

from bosh-oneagent-release.

Thanks, i'll try to reproduce this.

Could you, in the meantime, also share the install log of the bosh-release from /var/vcap/sys/log/dynatrace-oneagent/dynatrace-install.log? Make sure to remove any sensitive data from it though :-)

from bosh-oneagent-release.

Thanks, i'll try to reproduce this.

Could you, in the meantime, also share the install log of the bosh-release from /var/vcap/sys/log/dynatrace-oneagent/dynatrace-install.log? Make sure to remove any sensitive data from it though :-)

Hi, thanks for the support here's the install log:
Dynatrace_install.log

from bosh-oneagent-release.

I did some quick tests with v1.3.2 and v1.3.3 and got the same result for both. Which is kinda what i expected, since the logic at that place didn't change between the two versions. Just some variables got renamed.
And for downloading the agent the proxy settings seemed to have worked fine, because otherwords you'd have gotten some errors like this:

Downloading agent installer from <TENANT>
curl: (5) Could not resolve proxy: <NONFUNCTIONALPROXY>

So the problem is possibly not with the bosh-release itself but somewhere else. Do you know if the same installer/agent version was used in both cases? In the attached install log it was 1.201.129.20201001-102441.

from bosh-oneagent-release.

@arthfl thanks for the effort, I can see that for both versions, the installer is 1.201.129.20201001-102441
what does it mean this?

from bosh-oneagent-release.

@giva01121 Since this doesn't look like an issue with the bosh-release itself but maybe rather with the installer (which is fetched by the release), can you open a support case with us (Dynatrace) for this please?

I'm closing this issue with that, since the follow-up will be handled internally :-)

from bosh-oneagent-release.