openstack/nova
Code Issues Proposed changes

make incomplete_consumer_project_id a valid UUID

Browse Source 
Unfortunately, when I added the CONF.incomplete_consumer_project_id and
CONF.incomplete_consumer_user_id options, the default value for those
options was an invalid UUID (it had 13 zeroes for the last part of the
UUID instead of 12). This is preventing some work that tries to disable
warnings about invalid UUIDs being stored in ovo UUIDField objects.

The work to "heal allocations" will be able to fix up any deployments
that deployed the invalid UUID default CONF value because it looks for
any instances in Nova where the placement allocation records don't have
a matching user/project and replaces the mismatched user/project IDs on
the consumer appropriately.

Change-Id: I67b3b771f20e0b83225fce4839d378696fe1ab24
Closes-bug: #1780107
This commit is contained in:
Jay Pipes 2018-07-05 08:06:12 -04:00 committed by Chris Dent
parent 194e842c30
commit 4b62b6bfc9
2 changed files with 2 additions and 2 deletions
nova
conf
placement.py
tests/functional/api/openstack/placement/gabbits
ensure-consumer.yaml

2
nova/conf/placement.py

@ -17,7 +17,7 @@ from nova.conf import utils as confutils
DEFAULT_SERVICE_TYPE = 'placement'
DEFAULT_CONSUMER_MISSING_ID = '00000000-0000-0000-0000-0000000000000'
DEFAULT_CONSUMER_MISSING_ID = '00000000-0000-0000-0000-000000000000'
placement_group = cfg.OptGroup(
'placement',

2
nova/tests/functional/api/openstack/placement/gabbits/ensure-consumer.yaml

@ -11,7 +11,7 @@ defaults:
openstack-api-version: placement 1.7
vars:
- &default_incomplete_id 00000000-0000-0000-0000-0000000000000
- &default_incomplete_id 00000000-0000-0000-0000-000000000000
tests:
- name: put an allocation without project/user (1.7)