group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #24365
[Bug 1593469] Re: [2.0] VMware power type error: __init__() takes 1 positional argument but 2 were given
This bug was fixed in the package python-pyvmomi -
6.5.0.2017.5-0ubuntu1~16.04.1
---------------
python-pyvmomi (6.5.0.2017.5-0ubuntu1~16.04.1) xenial; urgency=medium
* Upload to xenial (LP: #1593469)
-- Julian Andres Klode <juliank@xxxxxxxxxx> Thu, 05 Apr 2018 15:13:56
+0200
** Changed in: python-pyvmomi (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1593469
Title:
[2.0] VMware power type error: __init__() takes 1 positional argument
but 2 were given
Status in MAAS:
Incomplete
Status in python-pyvmomi package in Ubuntu:
Fix Released
Status in python-pyvmomi source package in Xenial:
Fix Released
Bug description:
[Impact]
python-pyvmomi in xenial is outdated and does not allow connecting to vsphere with TLS validation. Updating to 6.5 fixes this and probably a few other issues.
[Test case]
For example,
>>> from pyVim.connect import SmartConnect
>>> import ssl
>>> context = ssl.SSLContext(ssl.PROTOCOL_SSLv23)
>>> context.verify_mode = ssl.CERT_NONE
>>> si = SmartConnect(host=host, user=user, pwd=password, port=port, sslContext=context)
should work.
This is basically a HWE type scenario.
[Regression potential]
Compatibility with vSphere 4.1 is not guaranteed anymore. Some bug fixes; and otherwise it's mostly just new data types and methods, so low likelihood of regressions on that side. As a bonus point, we won't have any changes to bionic.
[Original bug report]
When adding VMware power type in 2.0.0 beta7:
Failed to query node's BMC - __init__() takes 1 positional argument
but 2 were given
The same VMware details (UUID, vCenter IP address, username/password,
etc.) worked in an earlier version of the maas server, which was
Ubuntu 14.04 / maas 1.9.
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-====================================-============-=================================================
ii maas 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server common files
ii maas-dhcp 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DHCP server
ii maas-dns 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS DNS server
ii maas-proxy 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS Caching Proxy
ii maas-rack-controller 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Rack Controller for MAAS
ii maas-region-api 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region controller API service for MAAS
ii maas-region-controller 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.0.0~beta7+bzr5112-0ubuntu1~xenial1 all MAAS server provisioning libraries (Python 3)
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1593469/+subscriptions