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.
Bug 1828559 - healthchecks using curl are failing to honor no_proxy cidr notation
Summary: healthchecks using curl are failing to honor no_proxy cidr notation
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: curl
Version: 8.1
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Daniel Rusek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-27 20:23 UTC by David Hill
Modified: 2023-09-07 23:01 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-28 13:16:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-41941 0 None None None 2023-09-07 23:01:51 UTC
Red Hat Knowledge Base (Solution) 5019691 0 None None None 2020-04-27 20:34:03 UTC

Internal Links: 1837458

Description David Hill 2020-04-27 20:23:05 UTC 
Description of problem:
healthchecks using curl are failing to honor no_proxy cidr notation:


pr 27 14:29:07 undercloud healthcheck_swift_proxy[894392]: 407 135.28.13.29:8080 0.052233 seconds
Apr 27 14:29:07 undercloud healthcheck_swift_proxy[894392]: Error: non zero exit code: 1: OCI runtime error
Apr 27 14:29:07 undercloud systemd[1]: tripleo_swift_proxy_healthcheck.service: Main process exited, code=exited, status=1/FAILURE
Apr 27 14:29:07 undercloud systemd[1]: tripleo_swift_proxy_healthcheck.service: Failed with result 'exit-code'.
Apr 27 14:29:07 undercloud systemd[1]: Failed to start swift_proxy healthcheck.
Apr 27 14:29:12 undercloud systemd[1]: Starting logrotate_crond healthcheck...
Apr 27 14:29:12 undercloud systemd[1]: Starting zaqar_websocket healthcheck...


Version-Release number of selected component (if applicable):
Latest

How reproducible:
Proxied environment health check are failing

Steps to Reproduce:
1. Configure proxy with CIDR notation
2. Look in /var/log/messages once deployment is completed for healthchecks errors
3.

Actual results:
FAils

Expected results:
Succeeds

Additional info:
Comment 1 David Hill 2020-04-27 20:25:21 UTC 
Apr 27 14:29:07 undercloud systemd[1]: Started nova_api_cron healthcheck.
Apr 27 14:29:07 undercloud healthcheck_swift_proxy[894392]: curl: (22) The requested URL returned error: 407 Proxy Authentication Required
Apr 27 14:29:07 undercloud healthcheck_swift_proxy[894392]: 407 10.10.10.10:8080 0.052233 seconds
Apr 27 14:29:07 undercloud healthcheck_swift_proxy[894392]: Error: non zero exit code: 1: OCI runtime error
Apr 27 14:29:07 undercloud systemd[1]: tripleo_swift_proxy_healthcheck.service: Main process exited, code=exited, status=1/FAILURE
Apr 27 14:29:07 undercloud systemd[1]: tripleo_swift_proxy_healthcheck.service: Failed with result 'exit-code'.
Apr 27 14:29:07 undercloud systemd[1]: Failed to start swift_proxy healthcheck.
Comment 12 Brent Baude 2020-04-28 17:04:34 UTC 
if this is a curl problem, would it be possible to correct the component and assignee?
Comment 14 Kamil Dudka 2020-05-04 15:41:11 UTC 
I believe that curl's documentation is accurate -- you cannot specify a range of IP addresses with the NO_PROXY environment variable.  As far as I know, this has never been supported by curl.  See the following upstream issue for some background info:

https://github.com/curl/curl/issues/1208
Comment 15 Derrick Ornelas 2020-05-14 20:35:42 UTC 
So it seems like the problem is with the way that Openstack is trying to use curl.  Assuming that changing curl is not an option, should this be closed, or does the Openstack team want to move it over to the OSP product to track fixes for their healthchecks?
Comment 16 Cody Swanson 2020-05-19 20:26:55 UTC 
Hi Derrick, 

I opened the follow bug[1] for the OSP containers team to look into this as well. I will leave it to them to determine what the best approach to resolve the issue is.  


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1837458
Comment 17 Kamil Dudka 2020-05-28 13:16:57 UTC 
curl works as documented.  The OpenStack issue is tracked at bug #1837458.  I am closing this bug.
Note You need to log in before you can comment on or make changes to this bug.