From owner-freebsd-ports-bugs@freebsd.org Fri Sep 6 16:12:10 2019 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DDA1CF7426 for ; Fri, 6 Sep 2019 16:12:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46Q2d65bKYz4XJV for ; Fri, 6 Sep 2019 16:12:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id BFD97F7425; Fri, 6 Sep 2019 16:12:10 +0000 (UTC) Delivered-To: ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BF9C7F7424 for ; Fri, 6 Sep 2019 16:12:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Q2d64k91z4XJT for ; Fri, 6 Sep 2019 16:12:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 868AE1F662 for ; Fri, 6 Sep 2019 16:12:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x86GCAN8052838 for ; Fri, 6 Sep 2019 16:12:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x86GCAKW052837 for ports-bugs@FreeBSD.org; Fri, 6 Sep 2019 16:12:10 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 240371] iocage destroy doesn't handle renamed jails Date: Fri, 06 Sep 2019 16:12:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: lacibsd@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2019 16:12:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240371 Bug ID: 240371 Summary: iocage destroy doesn't handle renamed jails Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: lacibsd@gmail.com If you rename a jail and later destroy a jail which has a dependent jail, "iocage destroy jailname" will list the original name of the dependent jail= not the current one. See details below:=20 --- % iocage list +-----+----------+-------+--------------+------------+ | JID | NAME | STATE | RELEASE | IP4 | +=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D+=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D+ | 1 | 2blog | up | 11.2-RELEASE | 172.16.1.3 | +-----+----------+-------+--------------+------------+ | 7 | 2sql | up | 11.2-RELEASE | 172.16.1.2 | +-----+----------+-------+--------------+------------+ | - | 2sql_old | down | 11.2-RELEASE | 172.16.1.4 | +-----+-------+-------+--------------+------------+ % sudo iocage destroy 2sql_old Password: This will destroy jail 2sql_old Are you sure? [y/N]: y 2sql_old has dependent jails (who may also have dependents), use --recursiv= e to destroy: 20190728 20190729 20190730 20190731 20190801 20190802 20190803 3sql % sudo iocage destroy 2sql_old --recursive=20 % iocage list +-----+-------+-------+--------------+------------+ | JID | NAME | STATE | RELEASE | IP4 | +=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ | 1 | 2blog | up | 11.2-RELEASE | 172.16.1.3 | +-----+-------+-------+--------------+------------+ --- 3sql was renamed to 2sql (JID 7) a few months ago, at iocage destroy, iocage presented the original name rather than the current one. I ended up destroy= ing the wrong jail as well --=20 You are receiving this mail because: You are the assignee for the bug.=