Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not run the jamf2snipe to update the information from Jamf #114

Open
TungLe93 opened this issue Jul 27, 2023 · 1 comment
Open

Could not run the jamf2snipe to update the information from Jamf #114

TungLe93 opened this issue Jul 27, 2023 · 1 comment

Comments

@TungLe93
Copy link

TungLe93 commented Jul 27, 2023

Hi everyone,

I'm the non-code person here and I'm trying to follow the docx to get the jamf2snipe is running to sync device's information from Jamf to SnipeIT.

The jamf2snipe is run successfully at the first time. All data has been sync from Jamf to SnipeIT as expected.

But when I re-run the script to update the new data from Jamf. It's returned the error:

Please note that I do not make any changes in jamf2snipe file.

Traceback (most recent call last):
  File "/opt/jamf2snipe/jamf2snipe", line 901, in <module>
    jamf_value = jamf_value[item]
                 ~~~~~~~~~~^^^^^^
TypeError: list indices must be integers or slices, not str

When I added --debug it is returned:

DEBUG:root:general is not an integer
DEBUG:root:name is not an integer
DEBUG:root:Skipping the payload, because it already exits.
DEBUG:root:general is not an integer
DEBUG:root:mac_address is not an integer
DEBUG:root:The snipekey lookup failed, which means it's a custom field. Parsing those to see if it needs to be updated or not.
DEBUG:root:Skipping the payload, because it already exists, or the Snipe key we're mapping to doesn't.
DEBUG:root:hardware is not an integer
DEBUG:root:total_ram_mb is not an integer
DEBUG:root:The snipekey lookup failed, which means it's a custom field. Parsing those to see if it needs to be updated or not.
DEBUG:root:Skipping the payload, because it already exists, or the Snipe key we're mapping to doesn't.
DEBUG:root:hardware is not an integer
DEBUG:root:storage is not an integer
DEBUG:root:drive_capacity_mb is not an integer
Traceback (most recent call last):
  File "/opt/jamf2snipe/jamf2snipe", line 901, in <module>
    jamf_value = jamf_value[item]
                 ~~~~~~~~~~^^^^^^
TypeError: list indices must be integers or slices, not str

Thank you !!!

@casban
Copy link

casban commented Aug 28, 2023

I have a similar issue; drive_capacity_mb appears in the XML api tester under hardware -> storage -> device-> drive_capacity_mb, however the documentation indicates that capacity should be 1 level higher: hardware -> storage -> drive_capacity_mb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants