Bug 573118

Event posted on 03-12-2010 04:22pm EST by RFE-tool

1) Customer Name:
Boehringer Ingelheim Pharma GmbH & Co. KG

2) Nature Of Problem:
Since hardware sometimes comes with wildly wrong system clocks,
provisioning those machines will fail because the date can be outside of
the validity of the SSL certificates. Therefore every machine must be
checked for reasonable timestamps before it is provisioned.

3) Business Requirements Satisfied By Request:
Provisioning a large number of machines could be very simple but since
each BIOS time needs to be checked manually before, the whole process is
hugely more timeconsuming then it could be.

4) Functional Requirements That Are Not Presently Possible:
Kickstart should be able to run ntpdate before the system will be
registered (which will fail with wrong dates)

5) What Will Success Look Like:
Systems will install unattended even with vastly wrong system clocks.

6) Desired Release Vehicle:
Satellite release

7) Request Meets The Rhel Inclusion Criteria:
No

8) Affected Packages:
provisioning

9) Sales Sponsor:


10) Rh Business Opportunity With Customer:


11) Status And Risk To Contract If Not Satisfied:


12) If this request is vendor specific, has the customer engaged the
partner as well?:
Not Applicable




RFE-tool assigned to issue for SEG - Feature Request.

This event sent from IssueTracker by jwest  [SEG - Feature Request]
 issue 622103

Very good feature request!

A short term work around would be to edit  /var/lib/cobbler/snippets/redhat_register and add the appropriate ntpdate command before the registration line.  (Only for Satellite 5.3).

-Justin

1) is the ntpdate command available in %post - I expect so in chroot environment. 

2) we should also expose this in the bootstrap script and UI to push the script and input box on user input for ntpserver to use. 

3) We expose an option in kickstart of select/sync ntpdate and input box on user input for ntpserver to use. 

Cliff

Is this being watched anymore?

Hi,

This feature request seems to have been in sat-short since 17th July 2010. Is there any update or information I can give to the customer about if and / or when we're likely to include this into Satellite?

Thanks

Imo

Hi, 

I was just wondering if any decision had been made about this RFE? 

Thanks

Imo

(In reply to Imogen Flood-Murphy from comment #10)
> Hi, 
> 
> I was just wondering if any decision had been made about this RFE? 
> 
> Thanks
> 
> Imo

No. I'm going to add it to the weekly RFE meeting triage pad to discuss. My recommendation will be to move it into the Satellite 6 (Foreman provisioning) trackers, vs keeping it on the Satellite 5 RFE trackers (sat-short). 

Cliff

Already in the default Foreman/Satellite 6 kickstart file, moving to ON_QA.

https://github.com/theforeman/foreman/blob/f1627da8f/app/views/unattended/kickstart/provision.erb#L104-L107

This was delivered with Satellite 6.0 which was released on 10 September 2014.