Submitter: Zuul
Branch:    master

commit db686fe1856456e5e1486f0935aa4426c805520f
Author: esberglu <>
Date:   Mon Feb 12 12:18:57 2018 -0600

    Use correct arguments in task inits
    The CreateAndConnectCfgDrive and DeleteVOpt tasks were passing the
    instance into the task.Task init as the first argument. The first arg
    for the Task init is actually the task name [1]. This means that those
    task names were string representations of the instance which will cause
    failures if there are any non-ascii characters. This corrects the Task
    init calls by removing instance as the first argument. The name kwarg
    is now being used throughout the PowerVM tasks to avoid similar issues
    in the future.
    Change-Id: I991a5ea33daa9a21f774fe24882ed40f990b8e0e
    Closes-Bug: #1748950

** 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).

  PowerVM driver passing bad kwargs into Task init method

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  The PowerVM virt driver is passing the instance as the first argument
  to the Task init in a few places [1] [2]. The init method [3] expects
  the first arg to be the task name. This results in the task name being
  the string representation of the instance. The instance should no
  longer be passed into the Task init and the task names should be
  passed to the init using the name kwarg.

  This doesn't break the typical flows, however if the instance has any
  non-ascii characters in the string representation, the task will fail
  to compile.

  This affects queens and master branches using the PowerVM virt driver.


To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to