Bug 165852

Summary: NTP configuration / complex configuration: options lost
Product: [openSUSE] SUSE Linux 10.1 Reporter: Tim Fechtner <timmi>
Component: YaST2Assignee: Lukas Ocilka <locilka>
Status: VERIFIED FIXED QA Contact: Stanislav Visnovsky <visnov>
Severity: Normal    
Priority: P5 - None    
Version: RC 2   
Target Milestone: RC 2   
Hardware: x86   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: /var/log/YaST2 as tar.bz2 archive
/var/log/YaST2 as tar.bz2 archive, this time from RC2

Description Tim Fechtner 2006-04-13 12:33:08 UTC
- Start YaST
- Network Services / NTP client
- choose a single server by adress (not the "pool" option), here Germany / ptb2
- save the changes
- another time Network Services / NTP client: the formaly choosen server adress is displayed
- choose complex configuration

Here is only the local clock awaible.

It seems that informations made in complex configuration are applied correctly, but when you want to change the configuration, they aren't displayed anymore.

When choosing the pool option and then switching to complex configuration, the things are a little bit different: the default options for "pool" seem to be applied always. This means when you choose "pool" and than complex configuration, everything is displayed correct (3 server entries). Then you make a change to these entries (for example disable "get initial time from this server" for all servers). Then you click "finish". The options are applied correctly. On the next boot, the initial time really isn't get from the servers. But when you reopen then in yast the ntp configuration and go to complex configuration and edit one of the server entries, then "get initial time from this server" is checked - also this isn't true for the actually working configuration.
Comment 1 Tim Fechtner 2006-04-13 12:35:30 UTC
Created attachment 78249 [details]
/var/log/YaST2 as tar.bz2 archive
Comment 2 Michael Gross 2006-04-13 13:24:37 UTC
Martin, can you help here?
Comment 3 Lukas Ocilka 2006-04-13 13:43:16 UTC
Already fixed :)

-------------------------------------------------------------------
Tue Apr 11 11:53:06 CEST 2006 - locilka@suse.cz

- Switching from simple to complex configuration was eating server
  entries (#165149).
- 2.13.6

-------------------------------------------------------------------

Now I see the point of "get initial time from this server"
You are trying to change the automatically added "Pool NTP org" servers.
Comment 4 Lukas Ocilka 2006-04-13 14:04:58 UTC
-------------------------------------------------------------------
Thu Apr 13 16:02:25 CEST 2006 - locilka@suse.cz

- Leaving the 'initial_sync' and 'options' for pool.ntp.org feature
  without change when user has previously changed them (#165852).
- 2.13.7

-------------------------------------------------------------------
Comment 5 Tim Fechtner 2006-04-25 14:35:29 UTC
Is only partially fixed in RC2.

Do the following:

YaST -> NIS-conf -> choose Public NTP / Spain / hora.oxixares.com (Spain)

Finish

YaST -> NIS-conf -> choose Public NTP / Germany / tack.fh-augsburg.de

Now open complex configuration: showed is the (spanish) configuration who was saved and applyed the last time with "finish", and NOT the newly made (german) configuration.

Reopening. Changing version from beta9 to RC2.
Comment 6 Tim Fechtner 2006-04-25 14:41:14 UTC
Created attachment 79963 [details]
/var/log/YaST2 as tar.bz2 archive, this time from RC2
Comment 7 Lukas Ocilka 2006-04-25 14:49:51 UTC
Sorry, but you cannot allways reopen the bug if it's related to the ntp-client :)
If you have anothr bug, open another bugreport. This one was about "NTP configuration / complex configuration: options lost"

Your bug is about switching from simple to complex configuration.
Comment 8 Tim Fechtner 2006-04-25 15:01:10 UTC
> Sorry, but you cannot allways reopen the bug if it's related to the
> ntp-client :)
> If you have anothr bug, open another bugreport. This one was about
> "NTP configuration / complex configuration: options lost"
>
> Your bug is about switching from simple to complex configuration.

Done. The rest is working fine, so I set to verified.