The CPU flag table has the flag name defined as a String(10), which results in truncation of several flags including 'constant_tsc' and 'flexpriority'. This affects systems search results when searching on those flags.
Bumping to 0.9.1 as this doesn't seem to be too serious.
On Gerrit: http://gerrit.beaker-project.org/1077
Would it be worth fixing up the truncated cpu flags?
How do we know what the original was supposed to be? They will be fixed the next time inventory is re-run on each system anyway.
This cannot be verified properly due to 841398
Actually I was able to verify this by making the rpc directly >>> s.push('mymainframe.funtimes.invalid', {'Cpu': {'CpuFlags': ['thisislongerthan11characters'], 'vendor': 'vendorname', 'model': 'model', 'modelName': 'modeltest', 'family': 'familyname', 'stepping': '1', 'speed': '100', 'processors': '1', 'cores': '1', 'sockets': '1'}}) 0 >>>
Beaker 0.9.1 has been released.