Hello Lee, or anyone else affected,

Accepted maas into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/maas/2.0.0~rc2+bzr5156-0ubuntu1~16.04.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Description changed:

  [Impact]
- With a recent update of python from 3.5.1 to 3.5.2, the pathlib.Path.path 
property is gone. This impacts MAAS as it will case it to fail importing SSH 
keys, which prevents users from deploying.
+ With a recent update of python from 3.5.1 to 3.5.2, the pathlib.Path.path 
property is gone. This impacts MAAS as it will cause it to fail importing SSH 
keys, which prevents users from deploying.
  
  [Test Case]
- 1. Intsall MAAS
+ 1. Install MAAS
  2. Import SSH Key (example, maas maas sshkeys create key="$(ssh-add -L | grep 
[email protected])")
  
  With fix - The key will be imported correctly.
  Without fix - The key will fail to import.
  
  Work around sudden loss of pathlib.Path.path property in Python 3.5.2
  release.
  
  [Regression Potential]
  None. Tested and proved that using the different path fixes the issue.
  
  == Original bug report ==
  When I add a public SSH key over the API or in the UI I get the following 
error
  
  $ maas maas sshkeys create key="$(ssh-add -L | grep [email protected])"
  {"key": ["Invalid SSH public key: 'PosixPath' object has no attribute 
'path'"]}
  
  This was introduced in 5118 in the validation code of SSH keys but
  appears to be exposing a bigger bug. If you run ./bin/test.rack
  src/provisioningserver/utils/tests/test_sshkey.py the tests fail. I'm
  guessing that something is mocking check_output in a previous test and
  not unmocking it.

** Changed in: maas (Ubuntu Xenial)
       Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604128

Title:
  [2.0RC2] Unable to add a public SSH Key due to lp1604147

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to