iocage upgrade is looping: src component not installed, skipped #399
Just upgraded from non-python version. Host is on FreeBSD 11.1 and want to upgrade the jails from 10.3 to 11.1
Issued this command: iocage upgrade clavin2 -r 11.1-RELEASE
It is now looping on that command
After building head:
The usual files were manually updated.
Then it started wanted to remove files:
I am rather sure those files should not be removed.
I figured the previous upgrade attempt failed, the next attempt via HEAD got confused, or something.
I have since rolled back that jail to the snapshots I had:
Now when I attempt to upgrade:
Recall, I had just upgraded from iocage-1.7.6
I suspect iocage HEAD thinks this jail is modern, but it is not.
What do you think?
Indeed it looks like it’s trying to find the config.json for that jail. As for the file removal, I’m perplexed. I’ve seen this only 2 times and I haven’t been able to replicate it.
If you are able to I would greatly appreciate it, as of now I’m not sure where we need to fix things. Perhaps Colin would have an idea, as it may be freebsd-update related.
Looking at the other jails, each config.json file was created at about 15:13 UTC.
I have no doubt that it disappeared because of, and only because of, my zfs rollback.
i.e. it did not disappear because of freebsd-update
How can I create that file?
I have taken the file from one of the other jails, and created something close. I grabbed the value for jail_zfs_dataset from a prior 'iocage list' output.
The ip4_addr values I adjusted based on DNS entries.
What I don't know is the proper value for hostid
EDIT: It looks like hostid relates to the jail host and is the same for all jails on this box.
Ok good. I think you ran into #373, so you reverted, tried upgrading again and besides the JSON configuration, it all worked? It didn't try to remove files?
Do you happen to have any idea what might have changed since that snapshot and your attempt with the original upgrade that wanted to nuke those files?
This may help:
That jail lost the config.json, none of the others did.
It lost it because the snapshot was taken before it was created.