unclear, blocking errors when limits are set without tracking

[anderbubble]

• [x] master
• [x] 4-2-stable

---

If we have total_size_in_bytes set but not total_number_of_data_objects, the error message generated is unclear.

[joan5896@admin2 ~]$ iput few.txt
remote addresses: 10.225.160.101 ERROR: putUtil: put error for /curcZone/home/joan5896/few.txt, status = -1205000 status = -1205000 RE_RUNTIME_ERROR
Level 0: unordered_map::at: key not found

This also prevented me from turning off monitoring or making other changes.

[root@irods1 ~]# sudo -u irods python /tmp/ilogiq.py stop-monitoring /curcZone/home/joan5896
Nov  4 16:13:39 pid:20053 remote addresses: 10.225.128.219, 10.225.160.101 ERROR: unordered_map::at: key not found
Nov  4 16:13:39 pid:20053 remote addresses: 10.225.128.219, 10.225.160.101 ERROR: Logical Quotas Policy: Missing key
Nov  4 16:13:39 pid:20053 remote addresses: 10.225.128.219, 10.225.160.101 ERROR: rsExecMyRule : -1205000, [-]  ../src/handler.cpp:301:irods::error (anonymous namespace)::unset_metadata_impl(const std::string &, const irods::instance_configuration_map &, std::list<boost::any> &, irods::callback &, std::function<std::vector<const std::string *> (const irods::attributes &)>) :  status [RE_RUNTIME_ERROR]  errno [] -- message [Logical Quotas Policy: Missing key]

Changes proposed:

• IO attempted during this state should deny write just like any other policy violation, and a warning like "total_size_in_bytes set but total_number_of_data_objects not available" should be logged

• This state should not block other functions that modify tracking, as might be required to recover from a situation like this