Bulk Import behavior

[sepetuks]

Deployment Type

Self-hosted

NetBox Version

v.4.2.6

Python Version

3.12

Steps to Reproduce

1. Select IPAM-> prefixes and bulk import
2. put your bulk import data.
3. In the middle of data make a mistake that the import would fail (lets say define wrong VRF)

The same applies to some other objects where name/item uniqueness is not being checked (VRFs, Chassis and etc.)
Issue was noticed to happen when we upgraded to 4.2.1 (on some earlier version 4.1.7 it was behaving ok), and still persists in 4.2.6

Expected Behavior

None of the data should imported if there are any errors on data.

Observed Behavior

Data up to the the failing line was imported.
Error where the failure occurred is shown for some time and then disappears.
It is not clear which part of data import was successful (especially if you miss that error popup).
If you try to load data again you get duplicate records (in this case prefixes) again till the failing line.

[arthanson]

@sepetuks Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v4.3.6. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.

I tried the following with the second line being incorrect and I received the correct error and nothing was imported. Can you please provide the reproduction steps and very short sample css that can replicate the issue.

prefix,status,vrf
11.100.0.0/15,active,Alpha
12.100.0.0/15,active,XEEEE

[TadasNRK]

Hello all,

I'm able to reproduce this issue in NetBox Community v4.2.6 by adding "vlan_group" to an import data.

prefix status vrf vlan_group
192.168.100.0/22 active abc mygroup1
10.113.128.128/29 active dbc mygroup1
10.116.0.129/29 active efg mygroup1
10.1.29.0/24 active ghj mygroup1

In the third line I did add wrong prefix to have an error. After doing bulk import the first 2 prefixes were created.

Regards,
Tadas

[sepetuks]

I want to know that this behavior (importing part of data till first error) is happening in other places as well (I also observed that in devices import). Of course device import checks device name existance and second try to import gives error that some part of devices from import already exists. In any case that is very complicated to track which part of data was imported.