Conflict with Model Names & Different Model Identifiers

[smatthews0]

I've noticed an issue where Model Names can cause conflicts where the Model Identifier differ and was failing the script out.

Model:MacBook Pro (16-inch, 2023)
Model Identifier:Mac14,10
M2 Pro

Model:MacBook Pro (16-inch, 2023)
Model Identifier:Mac14,6
M2 Max

I was getting the failure
2024-09-23 16:51:44 - INFO - Processing entry 3 out of 151 - Device Name: *** - Device ID: ****
2024-09-23 16:51:44 - INFO - Could not find a model ID in Snipe-IT for: MacBook Pro (16-inch, 2023)
Traceback (most recent call last):
File "", line 790, in
create_snipe_model(newmodel)
File "", line 558, in create_snipe_model
modelnumbers[jsonresponse['payload']['model_number']] = jsonresponse['payload']['id']
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
TypeError: 'NoneType' object is not subscriptable

Adding a new Model with the Model Identifier bypassed the error

[smatthews0]

Looks like it's something that specifically started happening with M2+? Happens with M3s as well.

2024-09-23 17:44:59 - INFO - Could not find a model ID in Snipe-IT for: MacBook Pro (16-inch, Nov 2023)
Traceback (most recent call last):
File "", line 790, in
create_snipe_model(newmodel)
File "", line 558, in create_snipe_model
modelnumbers[jsonresponse['payload']['model_number']] = jsonresponse['payload']['id']
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
TypeError: 'NoneType' object is not subscriptable

Model Name: MacBook Pro (16-inch, Nov 2023)
Model Identifier: Mac15,9

Model Name: MacBook Pro (16-inch, Nov 2023)
Model Identifier: Mac15,7

[snipe]

That validation bug was fixed in Snipe-IT already. If you update to latest on master Snipe-IT, can you let me know if you're still seeing this issue?

[smatthews0]

That validation bug was fixed in Snipe-IT already. If you update to latest on master Snipe-IT, can you let me know if you're still seeing this issue?

Our Snipe Instance is on Snipe-IT version:v7.0.11 build 14904 (g6c0cf9447) but it's hosted for us So I'll need to take a look. It is fixed in 7.0.12?

[snipe]

It is fixed in 7.0.12?

Yep - should be. Can you send an email to support@snipeitapp.com with your hosted subdomain so we can get you updated to latest?

[abranc94]

Hello, sorry to bring something back up from the past but I believe I am running into the same issue.

My org was testing Snipe out last year and we were running one of the versions in the 6.X range. We moved to Kandji in the last few weeks from JAMF so we were looking to get this going. After coming across this I've upgraded to Version v8.0.4 - build 17704 (master) and am still experiencing the same issue as the above. Wondering if there's anything more I may need to adjust?

[kMikaZu]

I have a similar problem...

Snipe IT version: v8.1.2 - build 17914 (master)

We've imported a fresh list of new Mac minis 2024 from a .csv (exported from Apple Business Manager). The Model Number was not inserted though. Reason: To be able to create labels and label the devices before rolling out.

The Kandji2Snipe script creates a new Model during sync with the Model Number included Mac16,10

Existing Mac minis are untouched and the sync returns an error:

2025-05-21 11:50:25 - INFO - Processing entry 4 out of 173 - Device Name: SN-Name - Device ID: <hidden>
2025-05-21 11:50:26 - INFO - No assets match <SN>
2025-05-21 11:50:26 - INFO - Creating a new asset in Snipe-IT for Kandji ID <Kandji ID-SN>
2025-05-21 11:50:26 - ERROR - Asset creation failed for asset <Kandji ID - SN> with error {'serial': ['The serial must be unique.']}

So the sync doesn't find the existing serial numbers and it tries to create new assets. The creation of those assets then of course fails, because the SN Asset Field must be unique.

Even after deleting the created Model (created by the script) and entering the Model Number to the imported Model, the errors are the same.

It looks definitely as if the script doesn't look up existing SN's and syncs them. It looks like a one-directional sync. There config has a use_custom_pattern = no value.

[snipe]

Can you try pulling latest from master of snipe-it? I think you may be running into an api issue we already fixed

[kMikaZu]

We will need to wait for PikaPods to release the update then. Is that the 8.1.3 you are referring to?

Thanks!

[snipe]

I still don’t know pikapods are - I still think they’re a Pokémon I have not yet caught.

But yes.

I don’t know who or what Pikapods are, but more importantly, I don’t know how or when they provide those updates. They unfortunately don’t tell us anything. A new snipe-it release will be tagged in the next day or so, but I cannot speak to the lag time for pika.

[kMikaZu]

These are PikaPods. It's a European Docker Hub hosting provider.

[kMikaZu]

@snipe The version on DockerHub is still version 8.1.2, while the latest should be 8.1.16 . Why are these versions not in sync?
In order for us to get the latest version on PikaPods, we need to have that latest version available on DockerHub as well.

Thanks

[snipe]

You're looking in the wrong place. https://hub.docker.com/r/snipe/snipe-it/tags

[kMikaZu]

Hmm, I didn't find the latest versions but now I do. I've must have missed it. Thanks and sorry about that!

[snipe]

@kMikaZu no worries!