Bug 747869

Summary: First time wizard doesn't make a time synchronizing successfully
Product: [Fedora] Fedora Reporter: Rolle <rolle.hoffmann>
Component: system-config-dateAssignee: Nils Philippsen <nphilipp>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mlichvar, nphilipp, pertusus
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-10 15:43:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
firstboot-log.txt is the attachment from comment 3 none

Description Rolle 2011-10-21 08:30:55 UTC 
Description of problem:
At the first boot after installation process, the first time wizard couldn't synchronize the time with NTP. So the wizard doesn't finished this step and I can't finished the first time.


Version-Release number of selected component (if applicable):
Fedora 16 prerelease (nightly build 2011-10-19)

How reproducible:
Tried 2 times. On both tries it doesn't work.

Steps to Reproduce:
1. Install Fedora 16 (nightly build 2011-10-19)
2. first boot -> the first bott wizard appears
3. Select time-synchronizing over internet (no UTC is selected)
4. The wizard tries, but it never ends. And I can't cancel this process and can't go to the next step.
  
Actual results:
Time synchronizing in the first boot wizard doesn't work. It never ends.

Expected results:
Time synchronizing should do successfully and the wizard let me go to the next step.

Additional info:
Comment 1 Nils Philippsen 2011-10-21 11:38:51 UTC 
I tried this on an installed F-16 machine, i.e. configured firstboot to be run again and rebooted, which worked for me. I'll try this in a new VM installed from TC2: http://alt.fedoraproject.org/pub/alt/stage/16.TC2/
Comment 2 Nils Philippsen 2011-10-21 13:31:22 UTC 
Configuring NTP in forstboot also worked with TC2 for me.

Have you installed any non-standard packages on your system (e.g. ntp instead of chrony)?

Additionally, please do the following:

- Boot your system
- When firstboot appears, advance to the "Date & Time" step
- Switch to a virtual console (e.g. press Ctrl+Alt+F3)
- Login as root
- If the "strace" package isn't installed (check with "rpm -q strace"), install it: "yum install strace"
- Find out the firstboot processes and their IDs: "pgrep -lf firstboot"
- Attach strace to these processes and begin logging their system calls like this: "strace -Ff -o /tmp/firstboot-log.txt -p <pid>" -- supply "-p <pid>" for each process ID found in the previous step (the actual command could e.g. look like this: "strace -Ff -o /tmp/firstboot-log.txt -p 1234 -p 1238")
- Switch back to firstboot (Ctrl+Alt+F1), then select "Synchronize date and time over the network", then click "Forward"
- If it doesn't advance, let it run for a while (say a minute)
- Switch back to the virtual console (Ctrl+Alt+F3)
- Interrupt the strace program (Ctrl+C)
- Attach the log file /tmp/firstboot-log.txt to this bug report ("Add an attachment" above)

Thanks.
Comment 3 Rolle 2011-10-24 18:06:19 UTC 
Today I tried it again with my same nightly build cd from 2011-10-19.
I followed your instructions. Thank you for your instructions. But Murphy is here, in this try all is functional. The time synchronized immediately and the next step is going on.
Comment 4 Rolle 2011-10-24 18:09:11 UTC 
Created attachment 529938 [details]
firstboot-log.txt is the attachment from comment 3
Comment 5 Rolle 2011-10-25 14:03:13 UTC 
These Bugreports may address the same problem:
Bug 734906
Bug 736181
Bug 737235
Bug 747869
Comment 6 Nils Philippsen 2012-12-10 15:43:02 UTC 
Whoa, dropped this, sorry. With the information available, this could have many causes, in and out of system-config-date. Unfortunately without being able to reproduce it, there's not much to work with. Therefore I'll close this bug, please reopen if it happens again.