yahoo-eng-team team mailing list archive

[OpenStack Infra <1417027@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/319461
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4eb95a1b897505fb4e4ec17541eeebb79e7217a8
Submitter: Jenkins
Branch:    master

commit 4eb95a1b897505fb4e4ec17541eeebb79e7217a8
Author: Belmiro Moreira <moreira.belmiro.email.lists@xxxxxxxxx>
Date:   Fri May 20 23:14:03 2016 +0200

    No disable reason defined for new services
    
    Services can be disabled by several reasons and admins can use the API to
    specify a reason. However, currently if new services are added and
    "enable_new_services=False" there is no disable reason specified.
    Having services disabled with no reason specified creates additional checks on
    the operators side that increases with the deployment size.
    
    This patch specifies the disable reason:
    "New service disabled due to config option"
    when a new service is added and "enable_new_services=False".
    
    Closes-Bug: #1417027
    
    Change-Id: I52dd763cf1b58ba3ff56fe97f37eca18c915681d


** Changed in: nova
       Status: In Progress => Fix Released

-- 
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/1417027

Title:
  No disable reason defined for new services when
  "enable_new_services=False"

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  When a service is added and "enable_new_services=False" there is no disable
  reason specified.
  Services can be disabled by several reasons and the admins can use the API to
  specify a reason. However, having services disabled with no reason specified 
  creates additional checks on the operators side that increases with the 
  deployment size.

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