yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Reading the docs on the upgrade_levels config options, only
[upgrade_levels]/compute supports 'auto', so that's why it's blowing up
since you're setting it for everything.

** Changed in: nova
       Status: New => Invalid

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

Title:
  nova-compute version cap leads to ValueError

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Setting the following config on a compute host leads to a Stacktrace.

  
  [upgrade_levels]
  compute = auto
  cells = auto
  intercell = auto
  cert = auto
  scheduler = auto
  conductor = auto
  console = auto
  consoleauth = auto
  network = auto
  baseapi = auto

  Stacktrace:

  2018-07-16 14:02:39.011 474 ERROR nova   File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/client.py", line 119, in _check_version_cap
  2018-07-16 14:02:39.011 474 ERROR nova     if not utils.version_is_compatible(self.version_cap, version):
  2018-07-16 14:02:39.011 474 ERROR nova   File "/usr/lib/python2.7/dist-packages/oslo_messaging/_utils.py", line 40, in version_is_compatible
  2018-07-16 14:02:39.011 474 ERROR nova     if int(version_parts[0]) != int(imp_version_parts[0]):  # Major
  2018-07-16 14:02:39.011 474 ERROR nova ValueError: invalid literal for int() with base 10: 'auto'

  
  The same setting on a controller node works fine. Is it not supposed to use these version caps on a compute node or is this simply a bug in the code?

  
  # nova-compute --version
  17.0.4

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