irods_rule_engine_plugin_logical_quotas rules triggered by rodsuser

[L. Le Preux]

Hello,

As RDSM at the University of Groningen we are currently working on integrating the irods_rule_engine_plugin_logical_quotas plugin in our processes.

The plugin README states that:


Despite our understanding of the functionality, we have been able to use a "rodsuser" user to trigger the rules provided by the plugin. We couldn't find any references to this issue and it seems to affect only rules as triggered via  irods_rule_engine_plugin-irods_rule_language-instance and not when using irods_rule_engine_plugin-logical_quotas-instance directly.

Is this expected behaviour?
Thank you in advance,
Luca

More information and steps:
We have identified the issue in our development environment:
irods@rdms-irods:~$ imiscsvrinfo
RCAT_ENABLED
relVersion=rods4.3.4
apiVersion=d
rodsZone=rugZone
up 0 days, 2:25
SSL/TLS Info:
    enabled: false

In particular, using this user:
user@rdms-irods:~$ iuserinfo
name: user
id: 10015
type: rodsuser
zone: rugZone
info:
comment:
create time: 01750170429: 2025-06-17.14:27:09
modify time: 01750170735: 2025-06-17.14:32:15
member of group: public
member of group: user

We can successfully run:
user@rdms-irods:~$ irule "logical_quotas_start_monitoring_collection(\"/rugZone/home/user/test_collection\")" null ruleExecOut
rcExecMyRule: rule { logical_quotas_start_monitoring_collection("/rugZone/home/user/test_collection") }
outParamDesc: ruleExecOut
ExecMyRule completed successfully.    Output 

As well as verifying the status of the collection after starting monitoring:
user@rdms-irods:~$ irule "logical_quotas_get_collection_status(\"/rugZone/home/user/test_collection\", *out)" *out= *out
rcExecMyRule: rule { logical_quotas_get_collection_status("/rugZone/home/user/test_collection", *out) }
outParamDesc: *out
ExecMyRule completed successfully.    Output

*out = {"irods::logical_quotas::maximum_number_of_data_objects":"","irods::logical_quotas::maximum_size_in_bytes":"","irods::logical_quotas::total_number_of_data_objects":"0","irods::logical_quotas::total_size_in_bytes":"0"}

Also, here is the list of the available rule engine plugin instances in our dev environment:
        irods_rule_engine_plugin-metadata_guard-instance
        irods_rule_engine_plugin-logical_quotas-instance
        irods_rule_engine_plugin-irods_rule_language-instance
        irods_rule_engine_plugin-audit_amqp-instance
        irods_rule_engine_plugin-python-instance
        irods_rule_engine_plugin-cpp_default_policy-instance

[Kory Draughn]

Hi,

That is a bug.

I've opened https://github.com/irods/irods_rule_engine_plugin_logical_quotas/issues/132 to address the problem.

Please direct further conversations about this to that issue.

Thanks,

Kory Draughn

Chief Technologist

iRODS Consortium

--
--
The Integrated Rule-Oriented Data System (iRODS) - https://irods.org
 
iROD-Chat: http://groups.google.com/group/iROD-Chat
---
You received this message because you are subscribed to the Google Groups "iRODS-Chat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to irod-chat+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/irod-chat/8b0dc675-ec0f-475b-b763-603fd56cdcccn%40googlegroups.com.