|
Bugzilla – Full Text Bug Listing |
| Summary: | proxy "localhost" should be ignored on update | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Christian Boltz <suse-beta> |
| Component: | Update Problems | Assignee: | Katarina Machalkova <kmachalkova> |
| Status: | RESOLVED FIXED | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | jsuchome, ma |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christian Boltz
2006-04-02 17:10:05 UTC
Another possible solutions: - offer "retry without proxy" in case the internet test fails - add a dialog allowing to edit the proxy settings I think starting the proxy would be complicated. In addition to not knowing which one to start, it may have dependencies that we would not fulfill. The filtered proxy settings should probably be entered directly to the environment of the main yast process. We do not have a builtin for it yet but it seems worth it because setting them individually for each child (internet test, online update, rug) would be error prone. I agree, we cannot decide, which proxy to start. I'm especially thinking of 3rd party proxies, like webwasher (a Siemens product, in the past were versions for Linux avail), which won't fullfill any "Provides:" keywords, we might introduce in the init script. :( I think, we should favor a combination of both: an additional button "enter internet without proxy", which removes the proxy variable in main yast for each child. Reassigning to the new co-maintainer of yast2-network. second service... ping ;-) Any chance to get this fixed for 10.2? Eh .. we're beyond the text freeze and I guess some new strings would be needed to resolve this. But let me see what I can do. *** Bug 260407 has been marked as a duplicate of this bug. *** OK, I'm going to check in the following fix: Before the download of release notes starts, it is checked whether configured http proxy is available, just in the same way as if user clicked on 'Test your proxy settings' button in proxy module. * if the proxy test passes, these proxy settings will be used ( --proxy and --proxy-user curl parameters, if applicable) * if it fails, internet test will try direct connection without proxy Then, if the direct connection succeeds, internet test will be evaluated as passed and user can proceed to registration/online update stuff. If it fails (for whatever reason e.g firewall blocking direct connection to remote port 80), the test will be evaluated as failed as well -> no registration/online update This is all I can do on yast2-network side. I don't know whether yast online_update reads *_proxy environment variables and uses them in any way. Jirko? The only network-related settings yast2-online-update uses are those from Internet.ycp module:
if (!Internet::do_you)
skip YOU
if (!Internet::Status ())
Internet::Start ("")
That's basically all.
I've checked in the fix (y2-network 2.15.25) as stated comment #9. However, it only makes internet test pass, so that registration and online update steps are not skipped (provided that proxy-less connection would work out). But initialization of installation sources in online update will most likely fail at the end, because appropriate zypp inst. sources need proxy to be up and running. Michael, please open a new bugreport on handling proxy stuff in zypp installation sources (if you haven't already done so) and assign it to libzypp folks. |