Charm doesn't allow setting cpu-shared-set and cpu-dedicated-set without vcpu_pin_set set

Bug #1897275 reported by Nikolay Vinogradov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Nova Compute Charm
Fix Released
High
Edward Hope-Morley

Bug Description

I'm deploying OpenStack Ussuri on Bionic using the charm cs:nova-compute-kvm-320 with Juju 2.8.3 and MAAS 2.8.1.

In my bundle.yaml vcpu-pin-set option was not set for nova-compute-kvm charm. I had all-green Juju deployment when I attempted to set Nova's cpu_shared_set and cpu_dedicated_set using corresponding charm options cpu-shared-set and cpu-dedicated-set:

$ juju config nova-compute-kvm-critical -m openstack cpu-shared-set="8-23"
$ juju config nova-compute-kvm -m openstack cpu-dedicated-set="24-63"

config-changed hook would fail after the second command with a traceback like this: https://pastebin.ubuntu.com/p/pFRs6thHqC/

Nova's vcpu_pin_set option has been being deprecated since Train: [1]

[1] https://docs.openstack.org/releasenotes/nova/train.html#deprecation-notes

Revision history for this message
Nikolay Vinogradov (nikolay.vinogradov) wrote :

It looks like the workaround is to just set vcpu-pin-set to any value:

$ grep 'vcpu_pin_set\|cpu_shared_set\|cpu_dedicated_set' /etc/nova/nova.conf
cpu_shared_set = 8-23
cpu_dedicated_set = 24-63

description: updated
Revision history for this message
Edward Hope-Morley (hopem) wrote :

Going to get this fixed since the workaround is resulting in a fair amount of confusion

Changed in charm-nova-compute:
importance: Undecided → High
assignee: nobody → Edward Hope-Morley (hopem)
milestone: none → 21.01
Revision history for this message
Edward Hope-Morley (hopem) wrote :
Changed in charm-nova-compute:
status: New → In Progress
David Ames (thedac)
Changed in charm-nova-compute:
milestone: 21.01 → none
Changed in charm-nova-compute:
status: In Progress → Fix Committed
milestone: none → 21.04
Changed in charm-nova-compute:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.