Closed 2bithacker closed 4 years ago
I'm not able to reproduce this with the steps outlined above. It seems you need to:
Hello folks @jeremystretch - If the fix is to NOT allow a 0U size on a rack, that will break me.
My use case: I have 10s of Access Points in a particular shelf on a rack. They're really piled up, so they're in a rack but they're 0U. Any suggestion here?
@fsedano 0U devices may be assigned to a rack, just not to a specific position. This has always been the case; this fix merely addresses a condition in which the validation could be bypassed by modifying a device type that was previously 1U+.
Thanks Jeremy - If it's not in a specific position, what do you suggest to use for this use case (i.e. a lot of small devices in a shelf in a position in the rack). I.e. raspberry PIs, access points, etc. We have multiple shelves per Rack, each of them at a given position, so we have like 30 RPis on each shelf.
You could have a Device Type for a generic rack shelf with a number of device bays for the things on the shelf.
You could have a Device Type for a generic rack shelf with a number of device bays for the things on the shelf.
Thanks for the hint!
Environment
Steps to Reproduce
Expected Behavior
Not really sure what the correct representation of a 0U device in an RU should be, but at least it shouldn't alter the rendering of other devices in the rack.
Observed Behavior
The 0U device is rendered oddly, with it's name halfway through a U boundary. 1U devices get duplicated in incorrect RUs. Larger devices get 1U dups.