|
Bugzilla – Full Text Bug Listing |
| Summary: | yast NTP configuration: looking up NTP servers | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Karl Eichwalder <ke> |
| Component: | YaST2 | Assignee: | Katarina Machalkova <kmachalkova> |
| Status: | RESOLVED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | ||
| Version: | Alpha 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Documentation | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Uh, but the message (saying something like 'no servers found because your SuSEFirewall is running') is actually there :-) If you don't see it (and you definitely should), seems that you've hit the bug. Please attach YaST logs. Ping :) Without YaST logs, I tend to close this as 'worksforme', because it really does In the past, it never worked for me and there was no hint concerning firewall settings ;) And Tanja got also fooled by it recently (updating 10.1 to 10.2, IIRC). I'll try to catch a nice log soonish. Yes, I should pay more attention to these needinfo requests ;( You are right, Katarina :) I was able to verify your claim on SLES10 SP1 RC1. |
YaST offers to search for NTP servers in your net. This silently fails (~ "No server found") if the appropriate port is not open. I propose to enhance the result message. As an example, check the message you see, if you try to add an "Installation Source" (catalog) via SLP scan: ───────────────────────────────────────────────────┐ │ │ No SLP catalogs have been found on your network. │ │ │ This could be caused by a running SuSEfirewall2, │ │ │ which probably blocks the network scanning. │