ubuntu-support-status fails with exception if using libvirt from the ocata cloud-archive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
High
|
Unassigned | ||
update-manager (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Setps to reproduce:
1. Use Ubuntu 16.04.2 LTS
2. Add Cloud-Archive for Ocata: sudo add-apt-repository cloud-archive:ocata
3. Install libvirt-clients: sudo apt-get install libvirt-clients
4. Run ubuntu-
Expected result:
List of support durations for the installed packages
Actual result:
Traceback (most recent call last):
File "/usr/bin/
pkg.name, support_tag)
File "/usr/bin/
raise Exception("No Release file found for %s" % pkgname)
Exception: No Release file found for libvirt-clients
By Digging through the source code I've found out that the cloud-archive packages have a "Supported: 48m" field and are therefore considered by the release check but the package list is ignored as its origin and label are != "Ubuntu". Packages which have an equivalent in the standard ubuntu package sources silently fallback to the standard package. However, there is no equivalent for libvirt-clients and therefore ubuntu-
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libvirt-clients 2.5.0-3ubuntu5~
ProcVersionSign
Uname: Linux 4.4.0-81-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CrashDB:
{
}
Date: Tue Jun 27 17:46:50 2017
JournalErrors:
Error: command ['journalctl', '-b', '--priority=
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
Michael,
Thanks for reporting this. I'm seeing the same behavior. It looks like the ubuntu- support- status command from the update-manager package will need some updates to better handle cloud-archive packages.
Corey