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 968232 - libvirt should managed all container created by virt-sandbox-service
Summary: libvirt should managed all container created by virt-sandbox-service
Keywords:
Status: CLOSED DUPLICATE of bug 988493
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt-sandbox
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Berrangé
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-29 09:25 UTC by zhe peng
Modified: 2019-02-14 02:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-01 14:59:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description zhe peng 2013-05-29 09:25:04 UTC 
Description of problem:
libvirt should managed all container created by virt-sandbox-service

Version-Release number of selected component (if applicable):
libvirt-1.0.5-2.el7.x86_64
libvirt-sandbox-0.2.0-1.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1: use virt-sandbox-service to create a container and start
#virt-sandbox-service create -C -u httpd.service http1

#virt-sandbox-service start http1

# virt-sandbox-service list --running
http1

2: use virsh to check container status
#virsh -c lxc:/// list --all
 Id    Name                           State
----------------------------------------------------
 8072  http1                          running

3:destroy the container
#virsh -c lxc:/// destroy http1 
or
#virt-sandbox-service stop http1

4:check container status
# virsh -c lxc:/// list --all
 Id    Name                           State
----------------------------------------------------

5:define a container which name is same with stopped container,start the container by virt-sandbox-service will get error.
#virsh -c lxc:/// define http1.xml
Domain http1 defined from http1.xml

#virt-sandbox-service start http1
Unable to start container: Failed to create domain: operation failed: domain 'http1' already exists with uuid ea1a9e67-927d-4365-b735-9280b4414818



Actual results:
see step.

Expected results:
all container managed by libvirt, resolve conflict.



Additional info:
Comment 2 Daniel Berrangé 2013-08-01 14:59:05 UTC 

*** This bug has been marked as a duplicate of bug 988493 ***
Note You need to log in before you can comment on or make changes to this bug.