RDU Upgrades are failing due to error on "Upgrade Plug-In" stage mentioning "%s" due to proxy.
search cancel

RDU Upgrades are failing due to error on "Upgrade Plug-In" stage mentioning "%s" due to proxy.

book

Article ID: 413710

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

 

  • Unable to perform an RDU upgrade because of an error mentioning "%s" on the "Upgrade Plug-In" stage .
  • The errors on /var/log/vmware/vlcm/vlcm.log will have entries as shown below : 
    YYYY-MM-DDTHH:MM:22.094Z warning vlcm [curl/curl.go:278] [opID=task-id##--h5:70030547-3fd2] Unexpected status code [0] and err [<nil>], retries should not stop
YYYY-MM-DDTHH:MM:25.156Z error vlcm [exec/exec.go:115] [opID=task-id##--h5:70030547-3fd2] Run command [/usr/bin/curl --capath /etc/ssl/certs -L -C - --retry 0 --verbose --fail -w vlcm_http_code: %{http_code}\n --connect-timeout 15 --proxy *** --noproxy localhost, 127.0.0.1, .*.domain.sub.com, .*.domain.com --tlsv1.2 --tls-max 1.3 --tls13-ciphers TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256 --ciphers ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-SHA:AES128-SHA:TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256 --curves prime256v1:secp384r1:secp521r1 -o /tmp/custom-repo-updates-1613881850/rpm-manifest.json https://vcenter.second-domain.com:443/lcm-ui/repos/patcher_repo/package-pool/rpm-manifest.json] failed (duration: 59ms)
YYYY-MM-DDTHH:MM:25.156Z error vlcm [logger/multiline.go:17] [opID=task-id##--h5:70030547-3fd2] curl failed
YYYY-MM-DDTHH:MM:25.156Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] ERR:001 exit status 22
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:51] [opID=task-id##--h5:70030547-3fd2] ERR:002-
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:001   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:002                                  Dload  Upload   Total   Spent    Left  Speed
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:003   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Host <proxy-address>:<proxy-port> was resolved.
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:004 * IPv6: (none)
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:005 * IPv4: <proxy-ip>, <proxy-ip-2>
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:006 *   Trying <proxy-ip>:<proxy-port>...
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:007 * Connected to <proxy-address> (<proxy-ip>) port <proxy-port>
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:008 * CONNECT tunnel: HTTP/1.1 negotiated
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:009 * allocate connect buffer
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:010 * Establish HTTP proxy tunnel to vcenter.second-domain.com:443
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:011 > CONNECT vcenter.second-domain.com:443 HTTP/1.1
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:012 > Host: vcenter.second-domain.com:443
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:013 > User-Agent: curl/8.7.1
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:014 > Proxy-Connection: Keep-Alive
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:015 >
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:016 < HTTP/1.1 407 Proxy Authorization Required
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:017 < Date: Tue, 07 Oct 2025 04:23:25 GMT
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:018 < Proxy-Connection: keep-alive
YYYY-MM-DDTHH:MM:25.157Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:019 < Via: 1.1 <load-balancer>
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:020 < Cache-Control: no-store
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:021 < Content-Type: text/html
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:022 < Content-Language: en
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:023 < Proxy-Authenticate: Negotiate
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:024 < Proxy-Authenticate: NTLM
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:025 < Access-Control-Allow-Origin: *
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:026 < Content-Length: 666
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:027 <
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:028 * Ignore 666 bytes of response-body
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:029 * The requested URL returned error: 407
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:030   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:031 * Closing connection
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:032 curl: (22) The requested URL returned error: 407
YYYY-MM-DDTHH:MM:25.158Z error vlcm [logger/multiline.go:43] [opID=task-id##--h5:70030547-3fd2] OUT:033 vlcm_http_code: 000

 

Environment

VMware vCenter Server

Cause

The vCenter Server will connect to its own URL using a curl command in this stage.
As it references the FQDN , the curl command will go to the proxy settings configured on the vCenter Server. 

Resolution

  1. Confirm if the vCenter Server is trying to reach the vCenter URL through a proxy through the errors on the logs.
  2. If yes, check if the NO_PROXY configuration has any illegal characters and is correctly configured How to configure Proxy Settings for vCenter Server
  3. If the NO_PROXY list is configured correctly and there are no entries in the list to exclude the vCenter, add the entry explicitly as such :
    localhost, 127.0.0.1,.*.domain.sub.com,.*.domain.com,vcenter.second-domain.com

Additional Information

The NO_PROXY list requires following its syntax. 
If the vCenter name in this case was vcenter.domain.com, the issue would still arise due to spaces in the NO_PROXY list which can be seen on the error as shown below :
 localhost, 127.0.0.1, .*.domain.sub.com, .*.domain.com

Powered by Wolken Software