Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
In case there's no steps in the github issue. Write the steps here.
Description of problem:
"HttpProxy" configuration in /etc/waagent.conf doesn't work. The waagent connect to Azure Server directly.
Version-Release number of selected component (if applicable):
WALinuxAgent-2.1.5 (upstream, package by tester)
RHEL Version:
RHEL-7.3-20160729.1
How reproducible:
100%
Steps to Reproduce:
1. Prepare a VM on Azure with squid installed. Prepare a RHEL7.3 VM on Azure. These 2 VMs are in the same Virtual Network. Make sure that the client VM can connect to the Internet through the squid proxy, such as:
# wget -e "http_proxy=[squid VM private IP]:3128" http://www.baidu.com
Can download index.html successfully.
2. Change HttpProxy configurations in /etc/waagent.conf at the client VM:
HttpProxy.Host=[squid VM private IP]
HttpProxy.Port=3128
3. restart waagent service
# systemctl restart waagent
3. Catch packages at the squid VM and the client VM:
#tcpdump -s 0 -A 'tcp[((tcp[12:1] & 0xf0) >> 2):4] = 0x47455420'
Actual results:
Client VM: Can catch packages sent by waagent.
Squid VM: No packages come from client VM are catched.
Expected results:
Squid VM: Can capture upload blob packages at proxy.
Additional info:
1. It works well in WALA-2.0.16.
2. The root cause is that the PUT block/page blob request doesn't use proxy(wire.py Line 390 and 410), which do use proxy in 2.0.16.