Comment 2 for bug 1621344
Revision history for this message
| Andres Rodriguez (andreserl) wrote Re: [2.0] Multiple failed trusty deployments -- rename failed, Stale file handle | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
Hi Larry,
To me this seems like broken archives:
Package lvm2 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package python-oauthlib is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'lvm2' has no installation candidate
E: Package 'xfsprogs' has no installation candidate
E: Package 'python-oauthlib' has no installation candidate
Or maybe curtin/cloud-init trying to isntall something they shouldn't ? If you are saing that you are deploying Trusty and you see the issues above, then this is not curtin/cloud-init provided that it is python2 and those packages should be available in the archive.
Also, have you seen at maas-proxy ? Is it running ? You can try restarting maas-proxy or even cleaning up its cache and restarting and see if that makes a difference ?