Why is the following log not generated:
INFO: Running start for /opt/platform/iso on /www/pages/iso
...for the dc-iso-fs enable done here?
2020-03-21T09:20:16.000 controller-0 sm: debug time[613.439] log<1945> INFO: sm[18147]: sm_service_fsm.c(1032): Service (dc-iso-fs) received event (enable-throttle) was in the enabling-throttle state and is now in the enabling state.
How is the fix for bug 715018 going to make any difference? The dc-iso-fs does not have any dependencies that would be impacted by that fix.
The dc-iso-fs timeouts seem to be shorter than the ones for other filesystems (e.g. helmrepository-fs) - is that a mistake?
Bin - some questions for you...
Why is the following log not generated:
INFO: Running start for /opt/platform/iso on /www/pages/iso
...for the dc-iso-fs enable done here? 21T09:20: 16.000 controller-0 sm: debug time[613.439] log<1945> INFO: sm[18147]: sm_service_ fsm.c(1032) : Service (dc-iso-fs) received event (enable-throttle) was in the enabling-throttle state and is now in the enabling state.
2020-03-
How is the fix for bug 715018 going to make any difference? The dc-iso-fs does not have any dependencies that would be impacted by that fix.
The dc-iso-fs timeouts seem to be shorter than the ones for other filesystems (e.g. helmrepository-fs) - is that a mistake?