Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

iocage rulesets appears to have changed

Description

Appears to affect some, but not all of my iocages installed from plugins, since others work and I haven't set the rulesets for these manually, not sure where problem lies.

Have been no issues for 11.2\11.3, appears after upgrading to 12BETA

mirai% sudo iocage start ALL

shino (shino) is already running!
HA-Dev-instance (HA-Dev-instance) is already running!
Homeassistant (Homeassistant) is already running!
Plex (Plex) is already running!
choji (choji) is already running!
kiba (kiba) is already running!
konohamaru (konohamaru) is already running!
lidarr (lidarr) is already running!
naruto (naruto) is already running!
No default gateway found for ipv6.

  • Starting nextcloud
    nextcloud devfs_ruleset 8 does not exist! - Not starting jail
    No default gateway found for ipv6.

  • Starting qbittorrent
    qbittorrent devfs_ruleset 7 does not exist! - Not starting jail
    No default gateway found for ipv6.

  • Starting radarr
    radarr devfs_ruleset 8 does not exist! - Not starting jail
    No default gateway found for ipv6.

  • Starting sabnzbdplus
    sabnzbdplus devfs_ruleset 8 does not exist! - Not starting jail
    sakura (sakura) is already running!
    shikamaru (shikamaru) is already running!
    No default gateway found for ipv6.

  • Starting sonarr
    sonarr devfs_ruleset 7 does not exist! - Not starting jail

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Waqar July 9, 2020 at 1:15 PM

I have looked around and not sure what might have been the cause for this. It looks highly likely that we had a bug for this in the past where users had a devfs ruleset other then the default one.

If you are able to reproduce that with current plugin/jails, please let us know. I'll be closing this for now as I am unable to reproduce and this seems like a consequence of an old bug which does not exist right now. ( we have had another user report this too a few months back - https://github.com/iocage/iocage/issues/1140 )

Eirik Zakariassen July 9, 2020 at 6:05 AM

Interesting! The ones that failed were all created on 11.2 I believe, not sure what U off the top of my head unfortunately

Waqar July 9, 2020 at 3:31 AM

Hi , in 11.3 and before if a jail had a devfs ruleset configured which did not exist, we did not make that error fatal and still allowed the jail to start with default ruleset. However in 12, that behaviour was changed and if a jail has specified a devfs ruleset which does not exist, it won't start with the default one automatically.

Moving on, from the debug I see that all your jails which did not start automatically on boot are running now. I am not sure how your plugin jails got a devfs ruleset other then the default one. If I create them now, I get the default devfs ruleset configured for them which is as it should be.

Can you please let me know how old these jails are ? I am not sure but it looks like we might have had a bug in the past which led to this.

Eirik Zakariassen July 8, 2020 at 5:41 PM
Edited

 

Waqar July 6, 2020 at 12:52 PM

can you please attach a debug of the system ( System -> Advanced -> Save Debug ) ? Thank you

Cannot Reproduce

Details

Assignee

Reporter

Labels

Impact

Medium

Components

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created July 1, 2020 at 11:11 AM
Updated July 1, 2022 at 4:52 PM
Resolved July 9, 2020 at 1:15 PM