Patching a Linux modeling issue
In a small number of environments, Zenoss Support has observed
that Linux modeling runs can fail with tracebacks that end
KeyError: 'rebuild' (ZEN-32175). Installing this patch is optional,
because you may not experience the failure. You can install it at any
Perform this procedure after installing (or updating to) Resource Manager 6.4.1.
This patch is only for Resource Manager 6.4.1. Do not install it in prior or subsequent releases.
Follow these steps:
ZEN-32175.patchfile from the Resource Manager 6.4.1 folder on delivery.zenoss.io. Customers can request permission to gain access to delivery.zenoss.io by filing a ticket at the Zenoss Support site.
Copy the file to a directory the Control Center master host.
Log in to the Control Center master host as a user with
Create a directory for the patch file, if one does not already exist.
test -d /tmp/rmpatch || mkdir /tmp/rmpatch
ZEN-32175.patchfile into the new directory.
Set global read-write-execute permissions on the directory and its contents.
chmod -R 0777 /tmp/rmpatch
Change directory to the
Start an interactive shell in a new Zope container as user
zenoss. The following invocation also saves the Zope container with the name
serviced service shell -i -s ZEN-32175 zope su - zenoss
Change directory to
Copy the patch file to
cp /mnt/pwd/ZEN-32175.patch .
Patch the system.
patch -p0 < ZEN-32175.patch
On success, the patch utility displays the following output:
patching file Products/DataCollector/ApplyDataMap/reporter.py patching file Products/DataCollector/ApplyDataMap/tests/test_reporter.py patching file Products/ZenEvents/ZenEventClasses.py
If you do not see the preceding output, do not complete this procedure. Contact Zenoss Support.
Exit the Zope container.
Commit the Zope container.
serviced snapshot commit ZEN-32175
Restart Resource Manager.
serviced service restart Zenoss.resmgr