canonical / canonical/cloud-init
collect-logs should attempt to capture cloud-init version using more than dpkg
Open
bug
launchpad
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 1.1k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 18
Description
This bug was originally filed in Launchpad as [LP: #1820609](https://bugs.launchpad.net/cloud-init/+bug/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.
Contributor guide
Assessment
This issue has not been assessed yet.