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

Cannot set default properties: "ERROR: default was not found!" #24

Open
biochemie opened this issue Jun 13, 2017 · 4 comments
Open

Cannot set default properties: "ERROR: default was not found!" #24

biochemie opened this issue Jun 13, 2017 · 4 comments

Comments

@biochemie
Copy link

Trying to set default properties in iocell fails, as it appears the script is literally searching for a jail named "default" as opposed to applying it to the default settings.

Version: 2017-05-27 build from source in the FreeBSD ports

# iocell set vnet=off default results in ERROR: default was not found!

Have tried default, defaults, DEFAULT, and DEFAULTS to ensure there wasn't some case/misspelling issue. No luck with any of them.

@orichoni
Copy link

orichoni commented Jul 4, 2017

I don´t think it is an issue. Jail´s UUID or TAG is expected as the last parameter. The usage is:
iocell [-v] set property=value [property=value] UUID|TAG

@biochemie
Copy link
Author

biochemie commented Jul 4, 2017

@orichoni: I am speaking to setting global (for all jail) defaults for jail initialization with iocell [-v] set property=value default, as documented here:
http://iocell.readthedocs.io/en/latest/basic-use.html#system-wide-defaults

@bartekrutkowski
Copy link
Owner

bartekrutkowski commented Jul 4, 2017

I can confirm this looks like a valid bug, because I can reproduce it on my systems. However, I am not yet sure what is the nature of that issue. I did some preliminary examination and I might have an idea where the problem is, but I don't yet know how it should look like correctly.

@biochemie
Copy link
Author

biochemie commented Jul 4, 2017

@bartekrutkowski: I don't have time/access at work to investigate this much, but I've already rooted around a little bit better than when I first tried to figure out what was wrong here. I can check things a bit better from home this evening when I have access to my box where this was giving me problems.

ioc-common properly flags off the default value as being protected, so attributes avoid using it. However, ioc-cmd doesn't flag that it needs to do something different with _jail being set to default. It just passes it directly to __check_name over in ioc-info, which doesn't do anything unique when passed default, which fails because it does not exist.

@rostwald rostwald mentioned this issue Feb 19, 2024
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants