Using ioc start creates iocage/log dataset and iocage_legacy can't handle this

[bsdci]

Using ioc start creates iocage/log dataset and iocage_legacy can't handle this

[gronke]

https://github.com/iocage/iocage_legacy/blob/7c712bda3ca1cfd9b5d93dbe57efa75fc1c54c1b/lib/ioc-common#L39-L41 seems to be causing the issue. I'm thinking of moving the logs into the jail datasets.

[urosgruber]

Any news on this one. Can you actually replicate it or it's some local issue on my machine?

[igalic]

I'm quite certain that a definite goal is to remain backwards compatible with iocage, and iocage_legacy, but i'm not sure how we could remain forward compatible.??

[urosgruber]

@igalic but is there a reason that sys/iocage/log dataset is created. Always empty and unused. And I can't find any reference to this.

[igalic]

@gronke, would you mind weighing in?

[gronke]

@urosgruber this dataset should not be created. We should address file logging, but this is a fragment from rebuilding the previous version's behavior. Will remove it and open a ticket for event logging.

[gronke]

@urosgruber I've checked iocage_legacy (1.7.6 and master) list output of after using libiocage e128741 (from master). The log dataset will still be created but should not cause any trouble with iocage_legacy.

[gronke]

Was able to reproduce this issue with the latest libiocage. Will be fixed in #204

[urosgruber]

All good now except .default dataset is now causing same issue. The thing is any dataset found inside tank/iocage that iocage_legacy does not recognise causes it to misbehave.

I'm also not sure what is the plan about transition. Is it like using both iocage_legacy and ioc untill all jails migrated or just start using ioc (when released) and migrate jails. If the last is the case then I guess I don't care about this issue and I'll patch iocage_legacy to handle this kind of datasets.

[gronke]

@urosgruber a migration command is planned. Anyhow the focus is to be compatible with all existing iocage versions first and then aim to migrate across the formats. You can already mix them if you like (e.g. jails newly created with ioc have JSON config format). Jails that are in JSON format are not seen by the iocage version you are using right now.

I need to investigate why the .defaults dataset is causing trouble. It should never be created from ioc in case it was not existing before. In this case the preferred defaults storage is JSON. (The order of preference is JSON, UCL, ZFS).