Rudder

With commit 988f591a, the log now display:

[2012-09-16 17:21:56] ERROR com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Exception when processing report 'rudderagent.freedomit.co.za-2012-09-14-19-43-30.ocs'
[2012-09-16 17:21:56] ERROR com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Reported exception is:
java.lang.IllegalArgumentException: The report does not have a non-empty <HARDWARE><UUID> tag, this is not supported
at com.normation.inventory.provisioning.fusion.FusionReportUnmarshaller.processHardware(FusionReportUnmarshaller.scala:289) ~[FusionReportUnmarshaller.class:na]
----

We still have to handle correctly the case, but at least, we know where to look from the log.

Thanks for the explanation. How can I work around this in the meantime?

Just adding a <UUID>26d8f47a-003a-11e2-a6e0-0024e8cdea1f</UUID> tag into the <HARDWARE> should make the report being accepted (with 26d8f47a-003a-11e2-a6e0-0024e8cdea1f being replaced by some UUID, for example generated by the "uuid" command).
[EDIT: Or even better, now that I linked that to #1845, you could just use the UUID provided by "/usr/bin/xenstore-read vm" command for the VM - I still don't understand why the host does not have an UUID]

The not-so-nice thing is that following report will be rejected for the same reason as the first ones, and so you won't have any update about node details. That should not be a problem as long as hostname information from the first report are ok.

Even less nice, when the bug is corrected, the UUID is likelly to be different, and so the machine will be considered different, and added again.

All of that should not prevent to manage the nodes with CFEngine.

I also commented on bug #1845 that seems to be directly related.

Thanks for reporting, and sorry for the inconvenience.

Note for the bug owner:
1/ why are we using <HARDWARE><UUID> at all if we set our <MACHINEID> tag ? (ok, in that case, it won't have help)
2/ why MACHINEID is not part of the mandatory-non-empty tags (alike our UUID, HOSTNAME, etc) ?

We can't get your machine ID on your physical machine ('prometheus') because its motherboard doesn't have a proper UUID (value is "not present")

For the two other case, as they are xen VMs, they don't have a Machine ID.

As François said before, we'll handle both case in ticket #2899 (for missing machine ID) and #1845 (for Xen VMs).

Thank you for reporting Colin!

Note for developers: all the code introduced in 988f591a was deleted and/or modified in 3b53dab6 for #2899, so that commit should just be ignored. It should have been reverted as a first step of correcting #2899.