Bug 858636

Summary: Selecting synchronize network time results in an error.
Product: [Fedora] Fedora Reporter: richb
Component: system-config-dateAssignee: Nils Philippsen <nphilipp>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, jthompso, nphilipp, richb, stephent98, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-11 18:46:49 UTC Type: Bug
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
Screen shot showing the error none

Description richb 2012-09-19 09:36:44 UTC
Created attachment 614286 [details]
Screen shot showing the error

Description of problem:

In the post installation Date and Time screen, selecting synchronize date and time over the network, an error dialogue appears: 'Couldn't write to /etc/ntp.conf or /etc/sysconfig/network


Version-Release number of selected component (if applicable):
Fedora 18 Alpha

How reproducible:
Default installation, then select synchronize date and time over the network.

Steps to Reproduce:
1.Complete installation
2.In the post install Date + Time tab, select Synchronize date and time over the network
  
Actual results:
an error dialogue appears: 'Couldn't write to /etc/ntp.conf or /etc/sysconfig/network

Expected results:
Use ntp to set the date and time.

Additional info:

Comment 1 Joe Thompson 2012-09-26 06:59:33 UTC
This looks like a dupe of 857412.

Comment 2 Steve Tyler 2012-10-11 16:24:41 UTC
(In reply to comment #1)
> This looks like a dupe of 857412.

BZ will make a link from this: "Bug 857412".

Comment 3 Adam Williamson 2012-10-11 18:46:49 UTC

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