yahoo-eng-team team mailing list archive

[David Salisbury <launchpad@xxxxxxxxxxxxxxxxxxxxx>]

Public bug reported:

Seen in Grizzly, suspect it might be present in master too from looking
at the code.

Before:
==============

openstack41@lab6-n13:~$ nova service-list
+------------------+----------+----------+----------+-------+----------------------------+
| Binary           | Host     | Zone     | Status   | State | Updated_at                 |
+------------------+----------+----------+----------+-------+----------------------------+
| nova-compute     | lab5-n03 | nova     | disabled | down  | 2014-04-12T15:14:13.000000 |
... snipped ...
+------------------+----------+----------+----------+-------+----------------------------+


Enable the service:
==============

openstack41@lab6-n13:~$ nova service-enable lab5-n03 nova-compute
+----------+--------------+---------+
| Host     | Binary       | Status  |
+----------+--------------+---------+
| lab5-n03 | nova-compute | enabled |
+----------+--------------+---------+

After enabling:
==============

openstack41@lab6-n13:~$ nova service-list
+------------------+----------+----------+----------+-------+----------------------------+
| Binary           | Host     | Zone     | Status   | State | Updated_at                 |
+------------------+----------+----------+----------+-------+----------------------------+
| nova-compute     | lab5-n03 | nova     | enabled  | up    | 2014-04-12T15:26:11.000000 |
... snipped ...
+------------------+----------+----------+----------+-------+----------------------------+


What I think should happen is that the state should stay "down" even though the record was updated.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1306972

Title:
  Enabling/disabling a down service causes service-list to show it as
  "up"

Status in OpenStack Compute (Nova):
  New

Bug description:
  Seen in Grizzly, suspect it might be present in master too from
  looking at the code.

  Before:
  ==============

  openstack41@lab6-n13:~$ nova service-list
  +------------------+----------+----------+----------+-------+----------------------------+
  | Binary           | Host     | Zone     | Status   | State | Updated_at                 |
  +------------------+----------+----------+----------+-------+----------------------------+
  | nova-compute     | lab5-n03 | nova     | disabled | down  | 2014-04-12T15:14:13.000000 |
  ... snipped ...
  +------------------+----------+----------+----------+-------+----------------------------+

  
  Enable the service:
  ==============

  openstack41@lab6-n13:~$ nova service-enable lab5-n03 nova-compute
  +----------+--------------+---------+
  | Host     | Binary       | Status  |
  +----------+--------------+---------+
  | lab5-n03 | nova-compute | enabled |
  +----------+--------------+---------+

  After enabling:
  ==============

  openstack41@lab6-n13:~$ nova service-list
  +------------------+----------+----------+----------+-------+----------------------------+
  | Binary           | Host     | Zone     | Status   | State | Updated_at                 |
  +------------------+----------+----------+----------+-------+----------------------------+
  | nova-compute     | lab5-n03 | nova     | enabled  | up    | 2014-04-12T15:26:11.000000 |
  ... snipped ...
  +------------------+----------+----------+----------+-------+----------------------------+

  
  What I think should happen is that the state should stay "down" even though the record was updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1306972/+subscriptions