collect-logs should attempt to capture cloud-init version using more than dpkg

[ubuntu-server-builder]

This bug was originally filed in Launchpad as LP: #1820609

Launchpad details

affected_projects = []
assignee = None
assignee_name = None
date_closed = None
date_created = 2019-03-18T13:42:10.489808+00:00
date_fix_committed = None
date_fix_released = None
id = 1820609
importance = low
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1820609
milestone = None
owner = oddbloke
owner_name = Dan Watkins
private = False
status = triaged
submitter = oddbloke
submitter_name = Dan Watkins
tags = []
duplicates = []

Launchpad user Dan Watkins(oddbloke) wrote on 2019-03-18T13:42:10.489808+00:00

dpkg is only present on Debian derivatives; we should attempt to use other package management tools during cloud-init collect-logs to improve our chances of getting a useful version number in the collected tarball.

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2019-03-18T13:59:35.567003+00:00

+1. we used dpkg because at one point at least, the "packaged version" meant more than the upstream version. Now in Ubuntu and in rpm packages built from packages/redhat/cloud-init.spec.in a simple 'cloud-init --version' will include the package information as well.

That will not be the case with other packaging systems though.