Project

General

Profile

Bug #78097

Ensure iocage uses pathlib to accurately track if freebsd-version exists

Added by Kevin Windham almost 3 years ago. Updated over 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
Brandon Schneider
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

My jails both show up as corrupt after the update. The settings have been mangled somehow and they don't start.

Screen Shot 2019-03-01 at 9.42.20 AM.png (56.9 KB) Screen Shot 2019-03-01 at 9.42.20 AM.png CORRUPT jails Kevin Windham, 03/01/2019 07:47 AM
Screenshot 2019-03-05 at 21.24.52.png (52.2 KB) Screenshot 2019-03-05 at 21.24.52.png Rafal Lukawiecki, 03/05/2019 01:32 PM
57306
58638

Related issues

Has duplicate FreeNAS - Bug #78267: Jail cannot start, status shown as "corrupted"Closed
Has duplicate FreeNAS - Bug #81075: [HIGH] Multiple iocage jails are reporting a "CORRUPT" state, can't be started?Closed

History

#1 Updated by Kevin Windham almost 3 years ago

  • File debug-freenas-20190301071245.txz added
  • Private changed from No to Yes

#2 Updated by Dru Lavigne almost 3 years ago

  • Reason for Blocked set to Need additional information from Author

Kevin: please also attach a screenshot to this ticket of the screen (or error) you're seeing that indicates that your jails are corrupt.

Also, does the Important note in the Release Notes apply to your situation? https://www.ixsystems.com/blog/library/freenas-11-2-u2.1/

#3 Updated by Kevin Windham almost 3 years ago

It might be a little while before I can get a screenshot. The word CORRUPT in all caps was displayed in the jail list. I think it showed up instead of the status or release info.

https://www.ixsystems.com/documentation/freenas/11.2/_images/jails-actions.png

I do have none listed like the release notes say, but I don't recall actually needing to set that. Maybe I did. Seems like there was something I had to do to get the network working after upgrading to 11.2. Would that actually cause all the rest of the settings to wig out? Do I need to change that before running the update to U2.1? If so what should I set it to?

If you have any more suggestions I can try to test again late on Sunday I think. Thanks.

#4 Updated by Dru Lavigne almost 3 years ago

  • Status changed from Unscreened to Blocked

Go ahead and try these instructions on Sunday to see if they make a difference and leave a comment on this ticket:
Click the 3 button menu for that jail, click Edit, click Network Properties, and change the vnet_default_interface property to “auto”. If that does not resolve the issue, try checking and unchecking the DHCP box.

That will give us a better idea if it's vnet that is biting you or something else is going on.

#5 Updated by Kevin Windham almost 3 years ago

57306

I managed to get a few minutes to reboot quickly when no one was connected. In U2.1 all the jail settings are N/A except for fields that parse the / and they are just N.

In my existing jails only one had the vnet_default_interface changed from auto.

Here's a screenshot.

#6 Updated by Dru Lavigne almost 3 years ago

  • Category changed from Plugins to Middleware
  • Status changed from Blocked to Unscreened
  • Assignee changed from Release Council to William Grzybowski
  • Reason for Blocked deleted (Need additional information from Author)

#7 Updated by William Grzybowski almost 3 years ago

  • Assignee changed from William Grzybowski to Brandon Schneider
  • Target version changed from Backlog to 11.2-U3

#8 Updated by Brandon Schneider almost 3 years ago

  • Status changed from Unscreened to Blocked
  • Target version changed from 11.2-U3 to 11.2-U4
  • Reason for Blocked set to Need verification

Kevin: This is odd, your configuration checks out here, I suspect this is related to the fact you have two identically named jails on two different pools, and possibly the wrong pool is activated.

Which pool is the pool you expected iocage to use?

#9 Updated by Dru Lavigne almost 3 years ago

#10 Updated by Kevin Windham almost 3 years ago

I didn't realize I had identical jails. I have one named webserver and one named streambaby. The pool that is activated in jails is tank. It should use that one just like it does in U2 shouldn't it?

Unless you are thinking it has something to do with my backup.

#11 Updated by Kevin Windham almost 3 years ago

My jails were migrated using the script mentioned in the forums to go from warden to iocage. So they were definitely created before 11.2. But they have been working fine until this U2.1

#12 Updated by Dru Lavigne almost 3 years ago

  • Target version changed from 11.2-U4 to 11.2-U3

#14 Updated by Brandon Schneider almost 3 years ago

Kevin: Can you go to the command line and type iocage fetch -r 11.0-RELEASE, and see if that resolves your issue when it's complete.

#15 Updated by Kevin Windham almost 3 years ago

Good call. After fetching the 11.0-RELEASE my jails now say 11.0-RELEASE-p1 and they are working normally as far as I can tell. Is it the newer patches that fixed it or did something happen to them during the upgrade?

#16 Updated by Brandon Schneider almost 3 years ago

  • File deleted (debug-freenas-20190301071245.txz)

#17 Updated by Brandon Schneider almost 3 years ago

  • Status changed from Blocked to In Progress
  • Private changed from Yes to No
  • Reason for Blocked deleted (Need verification)

#18 Updated by Rafal Lukawiecki almost 3 years ago

I seem to have the same issue, as per my last comment 79 in #75648, with the same path of how the jails got created and updated. Before I apply the suggested iocage fetch -r 11.0-RELEASE, I have just one question—is that the version I should be using, considering that two of my jails use 11.2-RELEASE-p6 but only one is on 11.0? They all say "CORRUPT" when I update to U2.1. Many thanks.

#19 Updated by Brandon Schneider almost 3 years ago

Were all your jails migrated from Warden jails that were originally 11.0-RELEASE?

#20 Updated by Rafal Lukawiecki almost 3 years ago

Yes, they were. Subsequently they were updated to 11.2 using the newer version of FreeNAS.

#21 Updated by Brandon Schneider almost 3 years ago

Great! Then the same solution should solve your problem as well

#22 Updated by Rafal Lukawiecki almost 3 years ago

Thank you Brandon. I will go back to U2.1 and try it out. Am I using the iocage fetch from the shell prompt of each jail, or doing this via ssh to the FreeNAS host itself?

#23 Updated by Brandon Schneider almost 3 years ago

Rafal: Via the host itself, not per jail.

#24 Updated by Rafal Lukawiecki almost 3 years ago

I am afraid this has only worked for the one jail that was still on 11.0. It is working and shows as 11.0-RELEASE-p16. The remaining ones (which were originally 11.0 but upgraded since to 11.2) are showing as CORRUPT. See screenshot.

I am trying to iocage fetch 11.2-RELEASE to see if that helps, despite that source being already there. Will report back.

#26 Updated by Rafal Lukawiecki almost 3 years ago

Fetching 11.2-RELEASE helped resolve the issue for the remaining jails. Many thanks for your help, Brandon.

#27 Updated by William Grzybowski almost 3 years ago

  • Has duplicate Bug #78267: Jail cannot start, status shown as "corrupted" added

#28 Updated by Bug Clerk almost 3 years ago

  • Status changed from In Progress to Ready for Testing

#29 Updated by Brandon Schneider almost 3 years ago

Test case
---

iocage create -n foo -r 11.2-RELEASE -T ; iocage destroy -rd 11.2-RELEASE ; iocage list

should show a complete jail in the list output

#30 Updated by Dru Lavigne almost 3 years ago

  • Subject changed from Jails corrupt after 11.2-U2.1 update to Ensure iocage uses pathlib to accurately track if freebsd-version exists
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#31 Updated by Bonnie Follweiler over 2 years ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No

Test Passed in FreeNAS-11.2-U2-INTERNAL97

#32 Updated by Dru Lavigne over 2 years ago

  • Status changed from Passed Testing to Done

#33 Updated by Dru Lavigne over 2 years ago

  • Has duplicate Bug #81075: [HIGH] Multiple iocage jails are reporting a "CORRUPT" state, can't be started? added

Also available in: Atom PDF