Bug 2123737

Summary:	afterburn-sshkeys@.service missing instance name error when uninstalling afterburn
Product:	Red Hat Enterprise Linux 9	Reporter:	Michael Nguyen <mnguyen>
Component:	rust-afterburn	Assignee:	Steven Presti <spresti>
Status:	ASSIGNED ---	QA Contact:	RHCOS SST QE <rhcos-sst-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, jwboyer
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michael Nguyen 2022-09-02 13:18:30 UTC

Description of problem:
Uninstalling afterburn throws systemd error about missing the instance name.

Version-Release number of selected component (if applicable):
afterburn-5.3.0-1.el9.x86_64
afterburn-dracut-5.3.0-1.el9.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Download afterburn and afterburn-dracut rpm and install with `rpm -i`
2. Uninstall with `rpm -e afterburn afterburn-dracut`


Actual results:
The package gets uninstalled but throws an error message:
Failed to stop afterburn-sshkeys@.service: Unit name afterburn-sshkeys@.service is missing the instance name.
See system logs and 'systemctl status afterburn-sshkeys@.service' for details.

Expected results:
The package uninstalls with no error messages


Additional info:

[root@kvm-07-guest37 rpm]# rpm -qa | grep afterburn
afterburn-5.3.0-1.el9.x86_64
afterburn-dracut-5.3.0-1.el9.x86_64
[root@kvm-07-guest37 rpm]# rpm -e afterburn afterburn-dracut
Failed to stop afterburn-sshkeys@.service: Unit name afterburn-sshkeys@.service is missing the instance name.
See system logs and 'systemctl status afterburn-sshkeys@.service' for details.

Comment 1 Benjamin Gilbert 2022-09-02 21:51:06 UTC

The Fedora package has the same behavior.  I suspect we've always had this bug.