DescribeAvailabilityZones: services alive status is not consistent (if clocks are not synced)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Low
|
Unassigned |
Bug Description
Tested on Revision No : 624
If I run describe-
I am using default "service_down_time" flag which is set to 60.
root@ubuntu-
AVAILABILITYZONE nova available
AVAILABILITYZONE |- ubuntu-compute-01
AVAILABILITYZONE | |- nova-compute enabled XXX 2011-01-27 19:19:59
AVAILABILITYZONE |- ubuntu-compute-03
AVAILABILITYZONE | |- nova-compute enabled XXX 2011-01-27 19:19:58
AVAILABILITYZONE |- ubuntu-compute-02
AVAILABILITYZONE | |- nova-compute enabled :-) 2011-01-27 19:19:54
AVAILABILITYZONE |- ubuntu-
AVAILABILITYZONE | |- nova-scheduler enabled :-) 2011-01-27 19:19:50
AVAILABILITYZONE | |- nova-network enabled :-) 2011-01-27 19:19:52
root@ubuntu-
AVAILABILITYZONE nova available
AVAILABILITYZONE |- ubuntu-compute-01
AVAILABILITYZONE | |- nova-compute enabled :-) 2011-01-27 19:24:00
AVAILABILITYZONE |- ubuntu-compute-03
AVAILABILITYZONE | |- nova-compute enabled XXX 2011-01-27 19:24:09
AVAILABILITYZONE |- ubuntu-compute-02
AVAILABILITYZONE | |- nova-compute enabled XXX 2011-01-27 19:24:05
AVAILABILITYZONE |- ubuntu-
AVAILABILITYZONE | |- nova-scheduler enabled :-) 2011-01-27 19:24:01
AVAILABILITYZONE | |- nova-network enabled :-) 2011-01-27 19:23:54
Related branches
- Soren Hansen (community): Needs Information
- Rick Harris: Pending requested
- Vish Ishaya: Pending requested
-
Diff: 20 lines (+8/-2)1 file modifiednova/api/ec2/cloud.py (+8/-2)
Changed in nova: | |
assignee: | nobody → Tushar Patil (tpatil) |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → Low |
summary: |
- DescribeAvailabilityZones: services alive status is not consistent + DescribeAvailabilityZones: services alive status is not consistent (if + clocks are not synced) |
Changed in nova: | |
assignee: | nobody → 蒋闻天 (jiangwt100) |
assignee: | 蒋闻天 (jiangwt100) → nobody |
This can happen if you have clock skew. Try installing ntp on all of your boxes so the clocks are in sync.
On Jan 27, 2011, at 11:24 AM, Tushar Patil wrote:
> Public bug reported: availability- zones repeatedly for 4-5 times, each time network- api-server: /home/openstack /nova# euca-describe- availability- zones verbose network- api-server network- api-server: /home/openstack /nova# euca-describe- availability- zones verbose network- api-server /bugs.launchpad .net/bugs/ 708822 ilityZones: services alive status is not consistent availability- zones repeatedly for 4-5 times, each network- api-server: /home/openstack /nova# euca-describe- availability- zones verbose network- api-server
>
> Tested on Revision No : 624
>
> If I run describe-
> it shows service status as different.
>
> I am using default "service_down_time" flag which is set to 60.
>
> root@ubuntu-
> AVAILABILITYZONE nova available
> AVAILABILITYZONE |- ubuntu-compute-01
> AVAILABILITYZONE | |- nova-compute enabled XXX 2011-01-27 19:19:59
> AVAILABILITYZONE |- ubuntu-compute-03
> AVAILABILITYZONE | |- nova-compute enabled XXX 2011-01-27 19:19:58
> AVAILABILITYZONE |- ubuntu-compute-02
> AVAILABILITYZONE | |- nova-compute enabled :-) 2011-01-27 19:19:54
> AVAILABILITYZONE |- ubuntu-
> AVAILABILITYZONE | |- nova-scheduler enabled :-) 2011-01-27 19:19:50
> AVAILABILITYZONE | |- nova-network enabled :-) 2011-01-27 19:19:52
>
> root@ubuntu-
> AVAILABILITYZONE nova available
> AVAILABILITYZONE |- ubuntu-compute-01
> AVAILABILITYZONE | |- nova-compute enabled :-) 2011-01-27 19:24:00
> AVAILABILITYZONE |- ubuntu-compute-03
> AVAILABILITYZONE | |- nova-compute enabled XXX 2011-01-27 19:24:09
> AVAILABILITYZONE |- ubuntu-compute-02
> AVAILABILITYZONE | |- nova-compute enabled XXX 2011-01-27 19:24:05
> AVAILABILITYZONE |- ubuntu-
> AVAILABILITYZONE | |- nova-scheduler enabled :-) 2011-01-27 19:24:01
> AVAILABILITYZONE | |- nova-network enabled :-) 2011-01-27 19:23:54
>
> ** Affects: nova
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Nova Bug
> Team, which is subscribed to OpenStack Compute (nova).
> https:/
>
> Title:
> DescribeAvailab
>
> Status in OpenStack Compute (Nova):
> New
>
> Bug description:
> Tested on Revision No : 624
>
> If I run describe-
> time it shows service status as different.
>
> I am using default "service_down_time" flag which is set to 60.
>
> root@ubuntu-
> AVAILABILITYZONE nova available
> AVAILABILITYZONE |- ubuntu-compute-01
> AVAILABILITYZONE | |- nova-compute enabled XXX 2011-01-27 19:19:59
> AVAILABILITYZONE |- ubuntu-compute-03
> AVAILABILITYZONE | |- nova-compute enabled XXX 2011-01-27 19:19:58
> AVAILABILITYZONE |- ubuntu-compute-02
> AVAILABILITYZONE | |- nova-compute enabled :-) 2011-01-27 19:19:54
> AVAILABILITYZONE |- ubuntu-
> AVAILABILITYZONE | |- nova-scheduler enabled :-) 2011-01-27 19:19...