RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 956939 - packstack install fails if ntp server does not respond
Summary: packstack install fails if ntp server does not respond
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Martin Magr
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-26 03:39 UTC by Robert Harker
Modified: 2016-03-30 23:02 UTC (History)
4 users (show)

Fixed In Version: openstack-packstack-2013.1.1-0.7.dev580
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-30 23:02:23 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 29532 0 None None None Never

Description Robert Harker 2013-04-26 03:39:18 UTC
Description of problem:
packstack install fails if ntp server does not respond

Version-Release number of selected component (if applicable):
openstack-packstack.noarch                                         2013.1.1-0.5.dev538.el6                                     @openstack-grizzly


How reproducible:
Happens about 5-10% of the time I try and run packstack install

Steps to Reproduce:
1.Run:
  packstack -answer-file=<file>

  
Actual results:
If one of the listed ntp server fails to respond the packstack install fails with:
Installing:
Clean Up...                                              [ DONE ]
Adding pre install manifest entries...                   [ DONE ]
Installing time synchronization via NTP...
ERROR : Given host is unreachable: 0.fedora.pool.ntp.org
Please check log file /var/tmp/packstack/20130425-203129-rs39W8/openstack-setup.log for more information

Expected results:
packstack should install

Additional info:
/var/tmp/packstack/20130425-203129-rs39W8/openstack-setup.log
2013-04-25 20:31:29::INFO::run_setup::366::root:: Comparing pre- conditions, value: 'False', and match: 'True'
2013-04-25 20:31:29::INFO::run_setup::366::root:: Comparing pre- conditions, value: 'False', and match: 'True'
2013-04-25 20:31:29::INFO::run_setup::366::root:: Comparing pre- conditions, value: 'y', and match: 'y'
2013-04-25 20:31:29::INFO::run_setup::366::root:: Comparing pre- conditions, value: 'yes', and match: 'yes'
2013-04-25 20:31:29::INFO::run_setup::366::root:: Comparing pre- conditions, value: 'yes', and match: 'yes'
2013-04-25 20:31:39::ERROR::run_setup::906::root:: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 900, in main
    _main(confFile)
  File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 597, in _main
    runSequences()
  File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 574, in runSequences
    controller.runAllSequences()
  File "/usr/lib/python2.6/site-packages/packstack/installer/setup_controller.py", line 77, in runAllSequences
    sequence.run()
  File "/usr/lib/python2.6/site-packages/packstack/installer/setup_sequences.py", line 153, in run
    step.run()
  File "/usr/lib/python2.6/site-packages/packstack/installer/setup_sequences.py", line 60, in run
    function()
  File "/usr/lib/python2.6/site-packages/packstack/plugins/prescript_000.py", line 159, in create_ntp_manifest
    validators.validate_ping(srv)
  File "/usr/lib/python2.6/site-packages/packstack/installer/validators.py", line 184, in validate_ping
    raise ParamValidationError(msg % param)
ParamValidationError: Given host is unreachable: 0.fedora.pool.ntp.org

Comment 1 Derek Higgins 2013-04-26 08:53:33 UTC
This is not a problem with packstack it is supposed to stop if the ntp server entered isn't reachable. We don't want to proceed if there is a problem with the ntp server. I think this is reasonable behavior. 

Maybe we could retry once incase there was a network glitch but still stop if the second test still shows problems.

Comment 2 Robert Harker 2013-04-26 09:18:55 UTC
Except that it still fails if you list multiple ntp servers and only one fails.
I would think to get started packstack should run as long as one of the listed ntp servers responds.

Comment 3 Robert Harker 2013-04-26 09:19:26 UTC
Can we increase the timeout for each ntp server?

Comment 4 Martin Magr 2013-05-13 14:08:30 UTC
I think Packstack definitely should continue if at least one ntp server responds. Will be fixed.


Note You need to log in before you can comment on or make changes to this bug.