Bug 902767

Summary: YaST Proxy "test proxy settings" error when functioning normally
Product: [openSUSE] openSUSE 13.1 Reporter: Forgotten User 4cj_cU3qj6 <forgotten_4cj_cU3qj6>
Component: YaST2Assignee: Martin Vidner <mvidner>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: forgotten_4cj_cU3qj6
Version: FinalFlags: gs: needinfo? (forgotten_4cj_cU3qj6)
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 13.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: latest logfile per request

Description Forgotten User 4cj_cU3qj6 2014-10-27 18:15:00 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0
Build Identifier: 

Have a 12.3 and a 13.1 box.  The YaST/Proxy Test Proxy Settings works OK with 12.3 but not 13.1 (reinstalled both to check not hardware).  Yet the proxy works just fine in 13.1.

Reproducible: Always

Steps to Reproduce:
1. Set up YaST/Proxy
2. save and close - verify proxy works by refreshing repos
3. reopen and press "Test Proxy Settings"
Actual Results:  
In 12.3: "Proxy settings work correctly."
in 13.1: 
* Rebuilt URL to: http://www.novell.com/
* Adding handle: conn: 0xef2050
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0xef2050) send_pipe: 1, recv_pipe: 0
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* About to connect() to proxy proxy.domain.dom port 4319 (#0)
*   Trying 101.0.114.39...
* Connected to proxy.domain.dom (101.0.114.39) port 4319 (#0)
* Proxy auth using Basic with user 'rffry'
> GET http://www.novell.com/ HTTP/1.1
> Proxy-Authorization: Basic MTYxWDDGV9Vk
> User-Agent: curl/7.32.0
> Host: www.novell.com
> Accept: */*
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.1 301 Moved Permanently
< Date: Wed, 22 Oct 2014 18:25:59 GMT
* Server Apache is not blacklisted
< Server: Apache
< Location: http://www.novell.com/home/
< X-Mag: 6EAD06EADDDDB09;5a386713;71780882;usrLkup->0;usrBase->0;getPRBefFind->0;getPRBefFind->0;PRAfterFind->0;www_root;publicURL->0;FP4->0;
< Keep-Alive: timeout=2, max=96
< Content-Type: text/html; charset=iso-8859-1
< Set-Cookie: lb_novell=OAODEBIJ; Domain=.novell.com; Path=/
< Content-Length: 377
< Age: 11
< Via: 1.1 www.novell.com (Access Gateway-ag-6DDDD6E4F4DDDD09-71522482), 1.1 proxy.domain.dom:4319 (Cisco-IronPort-WSA/7.7.0-753)
< Connection: keep-alive
< Proxy-Connection: keep-alive
< 
{ [data not shown]

10    377  10   377    1     1   1919      0 --:--:-- --:--:-- --:--:--  1922
* Connection #0 to host proxy.domain.dom left intact

"Wizard" time. http://foldoc.org/wizard

Expected Results:  
"Proxy settings work correctly." in 13.1x64

This may be related to an additional "bug" I will report next: 
Although the proxy works fine, domain filtering seems to be in-place on my LAN (enforced by some non-proxy mechanism) which interacts with the meta-links in some repos to prevent packages from being downloaded.  Although "ignore" is chosen in YaST or "zypper patch" - none of the packages actually install - even those reported as "retrieved" and "applied" by zypper (YaST quits early).  This does not happen when using fully-local repos, such as mirrors.kernel.org, in which case all updates/packages are downloaded an successfully installed.  The issue is inability for important *patches* (such as the recent front-page bash patch) and no ability to troubleshoot via the proxy settings.
Comment 1 Gabriele Mohr 2014-10-30 09:42:01 UTC
Please attach YaST log-files, see
http://en.opensuse.org/openSUSE:Report_a_YaST_bug.
Comment 2 Forgotten User 4cj_cU3qj6 2014-10-30 17:26:34 UTC
Created attachment 611894 [details]
latest logfile per request

The proxy IP/port has been "anonymized"
Comment 3 Martin Vidner 2014-11-03 15:39:50 UTC
Thanks for the report. It is already fixed for 13.2.

*** This bug has been marked as a duplicate of bug 853725 ***