Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 910727 - Cannot spawn new machines. The scheduler.log says TypeError: can't compare datetime.datetime to NoneType
Cannot spawn new machines. The scheduler.log says TypeError: can't compare da...
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova (Show other bugs)
2.0 (Folsom)
x86_64 Linux
unspecified Severity high
: snapshot5
: 2.1
Assigned To: Russell Bryant
Jaroslav Henner
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-13 06:47 EST by Jaroslav Henner
Modified: 2013-04-04 16:21 EDT (History)
4 users (show)

See Also:
Fixed In Version: openstack-nova-2012.2.3-5.el6ost
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-04-04 16:21:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1096719 None None None Never
Red Hat Product Errata RHSA-2013:0709 normal SHIPPED_LIVE Moderate: openstack-nova security and bug fix update 2013-04-04 20:19:00 EDT

  None (edit)
Description Jaroslav Henner 2013-02-13 06:47:47 EST
Description of problem:

The test Tempest test (not-public hash d868607874f8b4c44a8e4443469e7cd343e7f75a) that is resizing the server:

nosetests --nologcapture -v --with-id --tests tempest.tests.compute.servers.test_disk_config:TestServerDiskConfig.test_resize_server_from_manual_to_auto

causes further attempts to boot an instance to fail with following in the scheduler log:

TypeError: can't compare datetime.datetime to NoneType



Version-Release number of selected component (if applicable):
openstack-nova-2012.2.2-9.el6ost.noarch

How reproducible:
With the mentioned test, 4/4.

Steps to Reproduce:
1. Run the test
2. nova boot the same image
3.
  
Actual results:
further instance spawns impossible

Expected results:
no problems

Additional info:
Comment 2 Jaroslav Henner 2013-02-13 06:52:05 EST
Note I found https://lists.launchpad.net/openstack/msg20738.html which seems to be not resolved.
Comment 4 Jaroslav Henner 2013-02-13 06:57:55 EST
restarting the openstack-nova-scheduler seems to fix this.
Comment 5 Jaroslav Henner 2013-02-22 04:34:33 EST
This may be a regression. I need to check that.
Comment 6 Russell Bryant 2013-03-06 18:05:24 EST
Looks like this is the bug:

    https://bugs.launchpad.net/nova/+bug/1096719

I submitted a stable/folsom backport here:

    https://bugs.launchpad.net/nova/+bug/1096719
Comment 7 Russell Bryant 2013-03-06 18:06:13 EST
the stable/folsom backport is actually over here:

    https://review.openstack.org/23758
Comment 11 Jaroslav Henner 2013-03-21 17:06:58 EDT
I am not sure what have changed in my environment, I cannot reproduce with pre openstack-nova-2012.2.3-5.el6ost package, nor with newer one. So I guess VERIFIED
Comment 13 errata-xmlrpc 2013-04-04 16:21:12 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0709.html

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