Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 994495

Summary: virt-sandbox-service can't delete running container
Product: Red Hat Enterprise Linux 7 Reporter: zhe peng <zpeng>
Component: libvirt-sandboxAssignee: Daniel Berrangé <berrange>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.0CC: ajia, dyuan, gsun, mzhan, weizhan
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libvirt-sandbox-0.5.0-2.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 12:06:23 UTC 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 zhe peng 2013-08-07 11:57:06 UTC
Description of problem:
virt-sandbox-service can't delete a running container.

Version-Release number of selected component (if applicable):
libvirt-sandbox-0.5.0-1.el7.x86_64
libvirt-1.1.1-2.el7.x86_64
kernel-3.10.0-6.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1:create&start a contariner

2:#virt-sandbox-service delete apache01
# echo $?
0
3:#virsh -c lxc:/// list --all
 Id    Name                           State
----------------------------------------------------
 5558  apache01                       running


Actual results:
container still in running status

Expected results:
delete container

Additional info:

Comment 1 Wayne Sun 2013-08-07 12:06:34 UTC
Fix in upstream:

https://www.redhat.com/archives/libvir-list/2013-August/msg00288.html

commit 5963dea4662219058e47d678ba9a3c98b67fceb6
Author: Wayne Sun <gsun>
Date:   Wed Aug 7 19:50:41 2013 +0800

    Fix delete of running containers
    
    The stop function is removed since 0.5.0, update delete function
    using virsh destroy to stop container.
    
    Signed-off-by: Wayne Sun <gsun>

Comment 3 zhe peng 2013-08-14 03:15:37 UTC
verify with build:
libvirt-sandbox-0.5.0-2.el7.x86_64
libvirt-1.1.1-2.el7.x86_64
kernel-3.10.0-6.el7.x86_64

step:
1:create&start a contariner

2:#virt-sandbox-service delete apache01
/usr/bin/virt-sandbox-service: Cannot delete running container

3:#virsh -c lxc:/// destroy apache01
Domain apache01 destroyed

# virt-sandbox-service delete apache01 ;echo $?
0

verification passed. move to verified.

Comment 5 Ludek Smid 2014-06-13 12:06:23 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.