[Bug 240371] iocage destroy doesn't handle renamed jails

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Sep 6 16:12:10 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240371

            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 at FreeBSD.org
          Reporter: lacibsd at 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: 
---
% iocage list
+-----+----------+-------+--------------+------------+
| JID |   NAME   | STATE |   RELEASE    |    IP4     |
+=====+==========+=======+==============+============+
| 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 --recursive to
destroy:
  20190728
  20190729
  20190730
  20190731
  20190801
  20190802
  20190803
  3sql

% sudo iocage destroy 2sql_old --recursive 

% iocage list
+-----+-------+-------+--------------+------------+
| JID | NAME  | STATE |   RELEASE    |    IP4     |
+=====+=======+=======+==============+============+
| 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 destroying
the wrong jail as well

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list