Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

commands on iocage-devel release are borked #894

Open
dlangille opened this issue Mar 21, 2019 · 64 comments

Comments

@dlangille
Copy link
Contributor

commented Mar 21, 2019

Is there some update command I am supposed to run when moving from py36-iocage-0.9.10 to py36-iocage-devel-1.0.0.20190308,1?

[dan@x8dtu:~] $ iocage -v
Version	1.2 BETA

[dan@x8dtu:~] $ sudo iocage list
Usage: iocage [OPTIONS] COMMAND [ARGS]...
Try "iocage --help" for help.

Error: No such command "list".


[dan@x8dtu:~] $ sudo iocage get all x8dtu-pg01
Usage: iocage [OPTIONS] COMMAND [ARGS]...
Try "iocage --help" for help.

Error: No such command "get".

[dan@x8dtu:~] $ iocage snapshot
Usage: iocage [OPTIONS] COMMAND [ARGS]...
Try "iocage --help" for help.

Error: No such command "snapshot".

This seems ominous as if there are only a few commands available:


[dan@x8dtu:/var/cache/pkg] $ iocage 
Usage: iocage [OPTIONS] COMMAND [ARGS]...

  A jail manager.

Options:
  -v, --version  Display iocage's version and exit.
  -f, --force    Allow iocage to rename datasets.
  -D, --debug    Log debug output to the console.
  --help         Show this message and exit.

Commands:
  migrate  Migrate all iocage_legacy develop basejails to new clonejails.

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Mar 21, 2019

This was my upgrade:

[dan@x8dtu:~] $ pkg search iocage
py36-iocage-1.1                FreeBSD jail manager written in Python3
py36-iocage-devel-1.0.0.20190308,1 FreeBSD jail manager written in Python3
[dan@x8dtu:~] $ sudo pkg delete py36-iocage
Checking integrity... done (0 conflicting)
The following package(s) are locked and may not be removed:

	py36-iocage

1 packages requested for removal: 1 locked, 0 missing
[dan@x8dtu:~] $ sudo pkg unlock py36-iocage
py36-iocage-0.9.10: unlock this package? [y/N]: y
Unlocking py36-iocage-0.9.10
[dan@x8dtu:~] $ sudo pkg delete py36-iocage
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
	py36-iocage-0.9.10

Number of packages to be removed: 1

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling py36-iocage-0.9.10...
[1/1] Deleting files for py36-iocage-0.9.10: 100%
[dan@x8dtu:~] $ sudo pkg install py36-iocage-devel
Updating local repository catalogue...
Fetching meta.txz: 100%    820 B   0.8kB/s    00:01    
Fetching packagesite.txz: 100%  244 KiB 249.8kB/s    00:01    
Processing entries: 100%
local repository update completed. 995 packages processed.
All repositories are up to date.
The following 5 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	py36-iocage-devel: 1.0.0.20190308,1
	py36-GitPython: 2.1.11
	py36-gitdb2: 2.0.5
	py36-smmap2: 2.0.5
	py36-ddt: 1.2.1

Number of packages to be installed: 5

The process will require 4 MiB more space.
792 KiB to be downloaded.

Proceed with this action? [y/N]: y
[1/5] Fetching py36-iocage-devel-1.0.0.20190308,1.txz: 100%  210 KiB 215.4kB/s    00:01    
[2/5] Fetching py36-GitPython-2.1.11.txz: 100%  459 KiB 469.7kB/s    00:01    
[3/5] Fetching py36-gitdb2-2.0.5.txz: 100%   84 KiB  85.7kB/s    00:01    
[4/5] Fetching py36-smmap2-2.0.5.txz: 100%   32 KiB  33.0kB/s    00:01    
[5/5] Fetching py36-ddt-1.2.1.txz: 100%    7 KiB   7.0kB/s    00:01    
Checking integrity... done (0 conflicting)
[1/5] Installing py36-smmap2-2.0.5...
[1/5] Extracting py36-smmap2-2.0.5: 100%
[2/5] Installing py36-gitdb2-2.0.5...
[2/5] Extracting py36-gitdb2-2.0.5: 100%
[3/5] Installing py36-ddt-1.2.1...
[3/5] Extracting py36-ddt-1.2.1: 100%
[4/5] Installing py36-GitPython-2.1.11...
[4/5] Extracting py36-GitPython-2.1.11: 100%
[5/5] Installing py36-iocage-devel-1.0.0.20190308,1...
[5/5] Extracting py36-iocage-devel-1.0.0.20190308,1: 100%
[dan@x8dtu:~] $ sudo pkg autoremove
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages:

Installed packages to be REMOVED:
	py36-dulwich-0.18.6

Number of packages to be removed: 1

The operation will free 2 MiB.

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling py36-dulwich-0.18.6...
[1/1] Deleting files for py36-dulwich-0.18.6: 100%

@drjohnnyfever1

This comment has been minimized.

Copy link
Contributor

commented Apr 3, 2019

Think this is the same as #890. Seems to be an issue with the PATH variable for the rc script.

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 3, 2019

Nice catch, thank you.

The team have been quiet for some time. @skarekrow .... what's up?

@skarekrow

This comment has been minimized.

Copy link
Member

commented Apr 4, 2019

@dlangille Just busy :)

@skarekrow

This comment has been minimized.

Copy link
Member

commented Apr 4, 2019

@william-gr Thoughts?

@william-gr

This comment has been minimized.

Copy link

commented Apr 4, 2019

ENOTIME, anyone willing to submit a patch to the port? ;)

@william-gr

This comment has been minimized.

Copy link

commented Apr 4, 2019

Or take maintainership :D

@drjohnnyfever1

This comment has been minimized.

Copy link
Contributor

commented Apr 4, 2019

I have a local patch that fixes it but I doubt it does it 'the right way'.

FWIW I see the same thing on github master branch not just the -devel port.

@drjohnnyfever1

This comment has been minimized.

Copy link
Contributor

commented Apr 5, 2019

Upon further investigation Dan's issue may be different than I thought. (Only happens when invoking iocage with the service command) Thus far I've been unable to reproduce even using the iocage-devel port.

Dan, whats your PATH look like if you sudo a new shell?

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 5, 2019

sudo is not required to produce the issue:

[dan@x8dtu:~] $ iocage list
Usage: iocage [OPTIONS] COMMAND [ARGS]...
Try "iocage --help" for help.

Error: No such command "list".
[dan@x8dtu:~] $ echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/home/dan/bin

[dan@x8dtu:~] $ sudo iocage list
Usage: iocage [OPTIONS] COMMAND [ARGS]...
Try "iocage --help" for help.

Error: No such command "list".

[dan@x8dtu:~] $ sudo echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/home/dan/bin

If I revert back to 0.9.10:

[dan@x8dtu:/var/cache/pkg] $ iocage list
+-----+-----------------+-------+--------------+-----+
| JID |      NAME       | STATE |   RELEASE    | IP4 |
+=====+=================+=======+==============+=====+
| 70  | mailjail        | up    | 11.2-RELEASE | -   |
+-----+-----------------+-------+--------------+-----+
| 71  | mx-ingress01    | up    | 11.2-RELEASE | -   |
+-----+-----------------+-------+--------------+-----+
| 76  | x8dtu-ingress01 | up    | 11.2-RELEASE | -   |
+-----+-----------------+-------+--------------+-----+
| 77  | x8dtu-nginx01   | up    | 11.2-RELEASE | -   |
+-----+-----------------+-------+--------------+-----+
| 75  | x8dtu-pg01      | up    | 11.2-RELEASE | -   |
+-----+-----------------+-------+--------------+-----+
| 78  | x8dtu-pg02      | up    | 11.2-RELEASE | -   |
+-----+-----------------+-------+--------------+-----+

[dan@x8dtu:/var/cache/pkg] $ pkg info -x iocage
py36-iocage-0.9.10
[dan@x8dtu:/var/cache/pkg] $ 

@igalic

This comment has been minimized.

Copy link
Contributor

commented Apr 6, 2019

$ sudo echo $PATH still only echos your path, since the shell resolves the variables before they are passed to sudo

sudo's path is determined by the sudoers file, or else, by the -E option

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 6, 2019

Us users can always be told what commands you want run so there is no confusion. Always willing to help.

Not sure what you need yet. Still guessing.

[dan@x8dtu:~] $ sudo /bin/sh
# id
uid=0(root) gid=0(wheel) groups=0(wheel),5(operator)
# echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/home/dan/bin
# 

Or perhaps this:

[dan@x8dtu:~] $ su
Password:
root@x8dtu:/usr/home/dan # echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
root@x8dtu:/usr/home/dan # 

Let's remove sudo from the mix:

root@x8dtu:/usr/home/dan # bash
[root@x8dtu:/usr/home/dan] # cd
[root@x8dtu:] # echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin
[root@x8dtu:] # pkg search iocage
py36-iocage-1.1 FreeBSD jail manager written in Python3
py36-iocage-devel-1.0.0.20190308,1 FreeBSD jail manager written in Python3
[root@x8dtu:] # pkg install py36-iocage-devel

....

[root@x8dtu:] # pkg info -x iocage
py36-iocage-devel-1.0.0.20190308,1
[root@x8dtu:] # iocage list
Usage: iocage [OPTIONS] COMMAND [ARGS]...
Try "iocage --help" for help.

Error: No such command "list".
[root@x8dtu:~] #

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2019

I deleted a comment I just posted: user error. I was expecting iocage -l to work and when it didn't I assumed it was related to the above...

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2019

FreshPorts is dead in the water.

@skarekrow

This comment has been minimized.

Copy link
Member

commented Apr 9, 2019

@dlangille What does pip3 freeze show?

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2019

$ pip3 freeze
bash: pip3: command not found
@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2019

python36-3.6.8_1 in use here.

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2019

I just built and install from head. Commands are borked there too.

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2019

# iocage --version
Version	1.2 RC

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2019

ENOTIME, anyone willing to submit a patch to the port? ;)

I just build a local package, does not fix the problem

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2019

I tried the fix from #890 (comment) but I get the same errors described there.

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2019

@dlangille What does pip3 freeze show?

Is this what you were looking for @skarekrow ?

[dan@x8dtu:~] $ pip-3.6 freeze
asn1crypto==0.22.0
certifi==2019.3.9
cffi==1.12.2
chardet==3.0.4
Click==7.0
coloredlogs==10.0
cryptography==2.6.1
ddt==1.2.1
dnspython==1.16.0
gitdb2==2.0.5
GitPython==2.1.11
humanfriendly==4.16.1
idna==2.8
iocage-cli==1.2rc0
libzfs==1.0
netifaces==0.10.9
pycparser==2.18
pyOpenSSL==18.0.0
PySocks==1.6.8
pytest-runner==2.11.1
requests==2.21.0
six==1.12.0
smmap2==2.0.5
texttable==1.6.1
tqdm==4.31.1
urllib3==1.22
You are using pip version 9.0.3, however version 19.0.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
[dan@x8dtu:~] $ 

@skarekrow

This comment has been minimized.

Copy link
Member

commented Apr 9, 2019

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2019

Yes, I am, from latest git.

EDIT: to be clear: I was not running from a git clone.

I built sysutils/iocage with the latest commit from git, and installed that package.

@skarekrow

This comment has been minimized.

Copy link
Member

commented Apr 9, 2019

What sticks out between my machine and yours is that your humanfriendly is not 4.17, and urllib3 is not 1.24.1.

Can you try upgrading those deps and see if this resolves your problem?

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2019

"solution": install git

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented May 19, 2019

@sonicaj ^ We should be only prompting the user about this tunable (non-fatally) if the jail actually has it enabled.

And if you do prompt, it should not be a fatal issue. Keep processing the other jails

@igalic

This comment has been minimized.

Copy link
Contributor

commented May 19, 2019

does make sense from a security point of view for instance.

What do you mean? I don't use rctl as far as I know. Why does that prevent my jails from being started?

oh! i thought you got that error when starting a jail that had an rctl set!

@skarekrow

This comment has been minimized.

Copy link
Member

commented May 19, 2019

does make sense from a security point of view for instance.

What do you mean? I don't use rctl as far as I know. Why does that prevent my jails from being started?

oh! i thought you got that error when starting a jail that had an rctl set!

Yeah that's the intention behind it anyways :D

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented May 19, 2019

Also, running poudriere testport on sysutils/iocage-devel gives this:

====> Running Q/A tests (stage-qa)
Warning: You have disabled the licenses framework with DISABLE_LICENSES, unable to run checks
====> Checking for pkg-plist issues (check-plist)
===> Parsing plist
===> Checking for items in STAGEDIR missing from pkg-plist
Error: Orphaned: %%PYTHON_SITELIBDIR%%/iocage_lib-1.2rc0-py%%PYTHON_VER%%.egg-info/PKG-INFO
Error: Orphaned: %%PYTHON_SITELIBDIR%%/iocage_lib-1.2rc0-py%%PYTHON_VER%%.egg-info/SOURCES.txt
Error: Orphaned: %%PYTHON_SITELIBDIR%%/iocage_lib-1.2rc0-py%%PYTHON_VER%%.egg-info/dependency_links.txt
Error: Orphaned: %%PYTHON_SITELIBDIR%%/iocage_lib-1.2rc0-py%%PYTHON_VER%%.egg-info/entry_points.txt
Error: Orphaned: %%PYTHON_SITELIBDIR%%/iocage_lib-1.2rc0-py%%PYTHON_VER%%.egg-info/requires.txt
Error: Orphaned: %%PYTHON_SITELIBDIR%%/iocage_lib-1.2rc0-py%%PYTHON_VER%%.egg-info/top_level.txt
===> Checking for items in pkg-plist which are not in STAGEDIR
===> Error: Plist issues found.
*** Error code 1

Stop.
@skarekrow

This comment has been minimized.

Copy link
Member

commented May 19, 2019

@sonicaj

This comment has been minimized.

Copy link
Member

commented May 19, 2019

@sonicaj ^ We should be only prompting the user about this tunable (non-fatally) if the jail actually has it enabled.

And if you do prompt, it should not be a fatal issue. Keep processing the other jails

@dlangille please confirm that your jail doesn't have an rctl key set.

root@bsd11:~ # sysctl kern.racct.enable
kern.racct.enable: 0
root@bsd11:~ #
root@bsd11:~ #
root@bsd11:~ # iocage list
+-----+---------+-------+--------------+--------------+
| JID |  NAME   | STATE |   RELEASE    |     IP4      |
+=====+=========+=======+==============+==============+
| -   | jail    | down  | 11.2-RELEASE | 192.168.0.24 |
+-----+---------+-------+--------------+--------------+
| -   | newjail | down  | 11.2-RELEASE | -            |
+-----+---------+-------+--------------+--------------+
root@bsd11:~ #
root@bsd11:~ # iocage --version
Version	1.2 RC
root@bsd11:~ # iocage start jail
* Starting jail
  + Started OK
  + Using devfs_ruleset: 5
  + Using IP options: ip4.addr=vtnet0|192.168.0.24 ip4.saddrsel=1 ip4=new ip6.saddrsel=1 ip6=new
  + Starting services OK
  + Executing poststart OK
root@bsd11:~ #
@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented May 19, 2019

I know nothing about rctl keys. How do I check to see if it is loaded?

Today I added kern.racct.enable="1" to /boot/loader.conf so that is set now.

Is there some specific test I can do for you?

@sonicaj

This comment has been minimized.

Copy link
Member

commented May 19, 2019

Well going through your jails and making sure that none of them have any of these keys set is a good start :p

types = {
        'cputime', 'datasize', 'stacksize', 'coredumpsize',
        'memoryuse', 'memorylocked', 'maxproc', 'openfiles',
        'vmemoryuse', 'pseudoterminals', 'swapuse', 'nthr',
        'msgqqueued', 'msgqsize', 'nmsgq', 'nsem', 'nsemop',
        'nshm', 'shmsize', 'wallclock', 'pcpu', 'readbps',
        'writebps', 'readiops', 'writeiops'
    }
@sonicaj

This comment has been minimized.

Copy link
Member

commented May 19, 2019

Although looking at your snippet above, one of your rc jail is affected. So that narrows the list of jails to check

@sonicaj

This comment has been minimized.

Copy link
Member

commented May 19, 2019

Or you could create an issue and provide a debug, we can look into that ourselves then. However you feel good :)

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented May 20, 2019

Well going through your jails and making sure that none of them have any of these keys set is a good start :p

I'm sorry. I have no idea what you mean by 'going through'.

Where is this type set?

I am guessing

$ iocage get all x8dtu-ingress01 | grep type
type:jail
types = {
        'cputime', 'datasize', 'stacksize', 'coredumpsize',
        'memoryuse', 'memorylocked', 'maxproc', 'openfiles',
        'vmemoryuse', 'pseudoterminals', 'swapuse', 'nthr',
        'msgqqueued', 'msgqsize', 'nmsgq', 'nsem', 'nsemop',
        'nshm', 'shmsize', 'wallclock', 'pcpu', 'readbps',
        'writebps', 'readiops', 'writeiops'
    }
@sonicaj

This comment has been minimized.

Copy link
Member

commented May 20, 2019

So each of the above in types is a property/prop. When you do iocage get all jailname, you'll see that you have a few props which match the names i shared above. They must be off which would indicate that you do not want to use that property, if there's any which is not off, then that is the one causing issues and we should see why it isn't off, was it something done by us or perhaps you at some point changed it.
If you're still having any issues with this, please open up a new issue ( preferably jira as we can securely get the debug there ), and we can investigate what's going wrong.
Thank you

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented May 20, 2019

Is this what you're looking for:

[dan@x8dtu:/iocage/jails] $ iocage get all x8dtu-ingress01 | egrep -ie 'cputime|datasize|stacksize|coredumpsize|memoryuse|memorylocked|maxproc|openfiles|vmemoryuse|pseudoterminals|swapuse|nthr|msgqqueued|msgqsize|nmsgq|nsem|nsemop|nshm|shmsize|wallclock|pcpu|readbps|writebps|readiops|writeiops' | grep -v off
memoryuse:8G:log
@sonicaj

This comment has been minimized.

Copy link
Member

commented May 20, 2019

Yup indeed, so memoryuse is a rctl property and that's why rctl validation was being performed. You should change that to off if you dont want it.
If there's any confusion, please let me know

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented May 20, 2019

memoryuse is now off in all jails. I am sure I was not using it because kern.racct.enable was originally off. I have rebooted the server and all jails came back up.

At present, the only change from 1d9efee I am running with is:

export PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin

which was added to /usr/local/etc/rc.d/iocage

@sonicaj

This comment has been minimized.

Copy link
Member

commented May 20, 2019

So @dlangille i can't find a reference which would indicate that we at any point set that prop to that value on our own. @skarekrow can you please confirm this as well ?

@skarekrow

This comment has been minimized.

Copy link
Member

commented May 20, 2019

So @dlangille i can't find a reference which would indicate that we at any point set that prop to that value on our own. @skarekrow can you please confirm this as well ?

I also cannot

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented May 20, 2019

@skarekrow

This comment has been minimized.

Copy link
Member

commented May 20, 2019

These jails are 4 years old?

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented May 20, 2019

Some are, some are not.

[dan@tallboy:~] $ iocage get memoryuse clavin2
8G:log
[dan@tallboy:~] $ iocage get memoryuse mailjail2
8G:log
[dan@tallboy:~] $ iocage get memoryuse mx-ingress02.freshports.org
off
[dan@tallboy:~] $ iocage get memoryuse ns1
8G:log
[dan@tallboy:~] $ iocage get memoryuse ns2
8G:log
[dan@tallboy:~] $ iocage get memoryuse tallboy-mqtt
off
[dan@tallboy:~] $ iocage get memoryuse wikis
8G:log
[dan@tallboy:~] $ 

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented May 20, 2019

[dan@tallboy:~] $ zfs get -t filesystem -r creation system/iocage
NAME                                                  PROPERTY  VALUE                  SOURCE
system/iocage                                         creation  Sat Mar  7 18:13 2015  -
system/iocage/.defaults                               creation  Sun Jun 21 15:57 2015  -
system/iocage/base                                    creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE                       creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root                  creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/bin              creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/boot             creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/lib              creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/libexec          creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/rescue           creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/sbin             creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/usr              creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/usr/bin          creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/usr/include      creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/usr/lib          creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/usr/lib32        creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/usr/libdata      creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/usr/libexec      creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/usr/sbin         creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/usr/share        creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.2-RELEASE/root/usr/src          creation  Sun Aug 16 18:32 2015  -
system/iocage/base/10.3-RELEASE                       creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root                  creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/bin              creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/boot             creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/lib              creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/libexec          creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/rescue           creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/sbin             creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/usr              creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/usr/bin          creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/usr/include      creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/usr/lib          creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/usr/lib32        creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/usr/libdata      creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/usr/libexec      creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/usr/sbin         creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/usr/share        creation  Wed Jul 27  0:57 2016  -
system/iocage/base/10.3-RELEASE/root/usr/src          creation  Wed Jul 27  0:57 2016  -
system/iocage/download                                creation  Sat Mar  7 18:13 2015  -
system/iocage/download/10.1-RELEASE                   creation  Sat Mar  7 18:13 2015  -
system/iocage/download/10.2-RELEASE                   creation  Sun Aug 16 18:30 2015  -
system/iocage/download/10.3-RELEASE                   creation  Wed Jul 27  0:52 2016  -
system/iocage/download/11.1-RELEASE                   creation  Thu Dec 28 23:47 2017  -
system/iocage/images                                  creation  Mon Oct 23 15:09 2017  -
system/iocage/jails                                   creation  Sat Mar  7 18:13 2015  -
system/iocage/jails/clavin2                           creation  Mon Oct 23 15:12 2017  -
system/iocage/jails/clavin2/data                      creation  Mon Oct 23 15:12 2017  -
system/iocage/jails/clavin2/root                      creation  Mon Oct 23 15:12 2017  -
system/iocage/jails/mailjail2                         creation  Mon Oct 23 15:13 2017  -
system/iocage/jails/mailjail2/data                    creation  Mon Oct 23 15:13 2017  -
system/iocage/jails/mailjail2/root                    creation  Mon Oct 23 15:13 2017  -
system/iocage/jails/mx-ingress02.freshports.org       creation  Thu Dec 28 23:53 2017  -
system/iocage/jails/mx-ingress02.freshports.org/root  creation  Thu Dec 28 23:53 2017  -
system/iocage/jails/ns1                               creation  Mon Oct 23 15:13 2017  -
system/iocage/jails/ns1/data                          creation  Mon Oct 23 15:13 2017  -
system/iocage/jails/ns1/root                          creation  Mon Oct 23 15:13 2017  -
system/iocage/jails/ns2.unixathome.org                creation  Mon Oct 23 15:13 2017  -
system/iocage/jails/ns2.unixathome.org/data           creation  Mon Oct 23 15:13 2017  -
system/iocage/jails/ns2.unixathome.org/root           creation  Mon Oct 23 15:13 2017  -
system/iocage/jails/tallboy-mqtt                      creation  Fri Mar 30 21:43 2018  -
system/iocage/jails/tallboy-mqtt/root                 creation  Fri Mar 30 21:43 2018  -
system/iocage/jails/wikis                             creation  Mon Oct 23 15:13 2017  -
system/iocage/jails/wikis/data                        creation  Mon Oct 23 15:13 2017  -
system/iocage/jails/wikis/root                        creation  Mon Oct 23 15:13 2017  -
system/iocage/log                                     creation  Mon Oct 23 15:09 2017  -
system/iocage/releases                                creation  Sat Mar  7 18:13 2015  -
system/iocage/releases/10.1-RELEASE                   creation  Sat Mar  7 18:13 2015  -
system/iocage/releases/10.1-RELEASE/root              creation  Sat Mar  7 18:13 2015  -
system/iocage/releases/10.2-RELEASE                   creation  Sun Aug 16 18:30 2015  -
system/iocage/releases/10.2-RELEASE/root              creation  Sun Aug 16 18:30 2015  -
system/iocage/releases/10.3-RELEASE                   creation  Wed Jul 27  0:52 2016  -
system/iocage/releases/10.3-RELEASE/root              creation  Wed Jul 27  0:52 2016  -
system/iocage/releases/11.1-RELEASE                   creation  Thu Dec 28 23:47 2017  -
system/iocage/releases/11.1-RELEASE/root              creation  Thu Dec 28 23:47 2017  -
system/iocage/templates                               creation  Mon Oct 23 15:09 2017  -

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented May 20, 2019

tallboy-mqtt and mx-ingress02.freshports.org do not have that value set, and they were created in Mar 2018 and Dec 2017 respectively

n2s was created in Oct 2017, and it has it set.

@skarekrow

This comment has been minimized.

Copy link
Member

commented May 20, 2019

It was very old legacy behavior that existed for a short period of time. I thought all these jails were recent, we both only audited the python code for obvious reasons ;)

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented May 21, 2019

Fair enough too.

@dlangille dlangille referenced this issue Aug 10, 2019
0 of 2 tasks complete

skarekrow added a commit that referenced this issue Aug 10, 2019

@sonicaj sonicaj reopened this Aug 10, 2019

@sonicaj

This comment has been minimized.

Copy link
Member

commented Aug 10, 2019

Requires fixes in the port

@dlangille

This comment has been minimized.

Copy link
Contributor Author

commented Aug 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.