[MIR] ipmitool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cluster-glue (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
ipmitool (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Availability: ipmitool is in universe in Precise, Trusty and Xenial.
Rationale: ipmitool is a new Recommends of cluster-glue, which is in Main. Additionally, ipmitool is a reasonably common program for systems management, and it makes some sense for it to be in Main.
Security: The security history for the ipmitool package is fairly quiet.
Reviewing CVEs for ipmitool, I found only one relevant one: http://
ipmitool installs one binary to /usr/sbin:
/usr/sbin/ipmievd
and one corresponding service:
/etc/init.d/ipmievd
/lib/systemd/
ipmievd itself is a logging daemon that transfer logs from a BMC to syslog and seems like a low exposure (accounting for the afore-mentioned CVE).
Quality assurance:
Installation of ipmitool results in an immediately working package. Site-specific options for accessing a BMC may be necessary, but are documented in the man-page.
No debconf questions are asked during installation.
https:/
Debian's bug tracker implies no significant bugs exist, excepting possibly related to whether ipmievd should start by default (due to dependencies on particular kernel modules).
https:/
The upstream bug tracker https:/
ipmitool is well-maintained in Debian and Ubuntu.
ipmitool does not ship a test suite; any test suite it shipped would also have strict hardware dependencies, I think.
ipmitool uses a debian/watch file and uscan/uupdate function currently.
I am not sure that the end-user application (ipmitool itself) has been internationalized yet. Nor does there appear to be a desktop file, but ipmitool would primarily be used on servers.
Dependencies:
All build and binary dependencies (including Recommends:) are satisfyable in main.
Standards compliance: The package meets the FHS and Debian Policy standards.
Maintenance: The Ubuntu Server team will maintain this package.
Background information:
The package descriptions correctly explain the general purpose and context of the package.
== Original report ==
cluster-glue has added a recommends: against ipmitool, currently in universe. This looks to me like a reasonable thing to have in main, but needs to go through the MIR process.
cluster-glue is owned by the server team.
Related branches
- James Page: Approve
- Bryce Harrington: Approve
- Canonical Server: Pending requested
-
Diff: 501 lines (+241/-122)7 files modifiedSTRUCTURE (+5/-1)
live-common (+1/-1)
supported-hardware-server (+15/-0)
supported-landscape (+4/-0)
supported-misc-servers (+83/-120)
supported-openstack (+107/-0)
supported-sysadmin-server (+26/-0)
CVE References
Changed in ipmitool (Ubuntu): | |
assignee: | nobody → Ubuntu Server Team (ubuntu-server) |
Changed in ipmitool (Ubuntu): | |
status: | Incomplete → New |
status: | New → Incomplete |
description: | updated |
Changed in ipmitool (Ubuntu): | |
status: | Incomplete → New |
Changed in ipmitool (Ubuntu): | |
assignee: | Ubuntu Server Team (ubuntu-server) → Jamie Strandboge (jdstrand) |
Changed in ipmitool (Ubuntu): | |
assignee: | Jamie Strandboge (jdstrand) → Ubuntu Security Team (ubuntu-security) |
Changed in ipmitool (Ubuntu): | |
status: | New → Won't Fix |
tags: | added: server-triage-discuss |
tags: | removed: server-todo |
It's probably worth noting (on this oddly-stalled MIR...) that, despite ipmitool being in universe, it would be a complete lie to claim that Canonical doesn't already support it. We've patched it quite heavily here and there for both paying customer and community bugs, we use it quite heavily internally, and recommend it often externally. The part where it's managed to continue living in universe is really just a side-effect of none of its dependencies making it to main until now, not an explicit statement of support.