Chassis SN vs System Serial - Which is used

[cyked]

I'm not successfully finding where current.serial_number or serial_number is set on a server CI.   System serial number is being used to populate the serial number field on a server CI rather than Chassis.   Is there a reason discovery prefers system serial number over chassis?   I can think of reasons where you could get in trouble, but know that bios/uuid/chassis/system are all retured from the hardware info probe.  

Where do I need to look to see where serial_number is set on a CI?   Trying to reverse-engineer this to understand the functionality better and determine if we can flip the order (use chassis more prevently) and what sort of issues we'd run into by doing so.

[doug_schulze]

Vaguely I remember us having an issue with those serial number spaces (I think it was with you robin850 Shaun in your previous life) which was many moons ago and aleck.lin may have done some magic for that in that Snc Serial number function to account but just for that type... cool fix regardless...

[cyked]

Looks like its an artifact of the WMI probe.   It gets back the white space and processes it.   I don't believe this is a SNOW issue, its something with HP/Dell, etc.   My HP laptop doesn't have the trailing spaces in any SN, but i'm seeing the spaces on Prioliant systems.

[aleck_lin]

I did make a change so that we automatically trim any white spaces before or after the data when we process it. That was a change I did at least 2-3 years ago. Unless you're a customer before that, your instance should automatically have this enabled by default (there's a property that controls this behavior because I didn't want to change the behavior on existing customer and wreak havoc). I would open up a ticket with support if the white spaces are not trimmed automatically.

[cyked]

We started in 2013 with Calgary.   Thanks for the reply.