Replies: 1 comment 1 reply
-
Note that if using scope_type then you'd also need to provide scope_id. The first is the type of object and the second is the numeric ID of that object type. It's annoying because a CSV export shows scope_type as "dcim.site", but that doesn't work in CSV import. The actual allowed values are supposedly here. However the following CSV import of vlangroups fails, even if you have a site with ID 1:
I suggest you report it as a bug. I also notice that the vlangroup upload page shows "site" as an available column. As far as I can see, that doesn't work at all (it ignored the value I put in there). So that looks like a second bug. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
After upgrade to 2.11 I have problem with my own address management script.
The problem is with scope_type in vlan_group. I'm trying to add new Vlan Group using VLAN Group Bulk Import but I am getting an error:
"Row 1 scope_type: Select a valid choice. That choice is not one of the available choices."
My input data:
name,slug,scope_type
Example,example,dcim.sites
What am I doing wrong?
I've tried using different variables like:
('dcim.region', 'Region'),
('dcim.sitegroup', 'Site group'),
('dcim.site', 'Site'),
('dcim.location', 'Location'),
('dcim.rack', 'Rack'),
('virtualization.clustergroup', 'Cluster group'),
('virtualization.cluster', 'Cluster'),
But still not working.
Beta Was this translation helpful? Give feedback.
All reactions