Public bug reported:
This happens on a fully updated Queens release using Ubuntu's Bionic
release.
Basically the vmwareapi/driver.py opens the log-file and passes it to
nova.privsep.path.last_bytes as argument.
However, nova.privsep.path.last_bytes expects a path and not a file-
handle. Thus it throws a TypeError exception.
Changing the vmwareapi/driver.py to call
```
read_log_data, remaining = nova.privsep.path.last_bytes(path, MAX_CONSOLE_BYTES)
```
instead, fixes the issue.
** Affects: nova
Importance: Undecided
Status: New
--
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/1786683
Title:
instance log with vmware fails
Status in OpenStack Compute (nova):
New
Bug description:
This happens on a fully updated Queens release using Ubuntu's Bionic
release.
Basically the vmwareapi/driver.py opens the log-file and passes it to
nova.privsep.path.last_bytes as argument.
However, nova.privsep.path.last_bytes expects a path and not a file-
handle. Thus it throws a TypeError exception.
Changing the vmwareapi/driver.py to call
```
read_log_data, remaining = nova.privsep.path.last_bytes(path,
MAX_CONSOLE_BYTES)
```
instead, fixes the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1786683/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
