Issue with Child Prefix since upgrading to 3.0.0

[aquelf]

I have recently upgraded from 2.11.7 to 3.0.0.

What I have noticed that under Sites > Prefixes > Child Prefixs I get the following Server Error?

This was how I nested the subnets prior to upgrade, has something changed or broken after the upgrade, thanks?

[Bloodiko]

pls see Issue #7072 for Reference.

This was a bug in 3.0.0 - and was fixed in yesterdays Release 3.0.1

Bloodiko

[candlerb]

I don't understand "Sites > Prefixes". Do you mean "IPAM > Prefixes" in the left hand navigation panel, or something else?

[aquelf]

Yes, the same thing. On the left hand panel.

[candlerb]

OK, thank you, I reproduced this way:

• IPAM > Prefixes
• Configure Table
• Add column "Prefix (Flat)"
• Save
• Navigate to some prefix which has child prefixes
• Click on "child prefixes" tab: in my case/ipam/prefixes/17/prefixes/

Unfortunately it's not E-mailing the exception, I need to dig to find out why.

Removing the extra column (via Configure Table) fixes it.

[candlerb]

via DEBUG=True:

/opt/netbox/netbox/netbox/views/generic.py, line 70, in get
        return render(request, self.get_template_name(), { 
......
/opt/netbox/venv/lib/python3.8/site-packages/django_tables2/columns/base.py, line 147, in get_attrs
        attrs["href"] = self.compose_url(**kwargs) 
/opt/netbox/venv/lib/python3.8/site-packages/django_tables2/columns/base.py, line 119, in compose_url
        return context.get_absolute_url() 
/opt/netbox/netbox/ipam/models/ip.py, line 305, in get_absolute_url
        return reverse('ipam:prefix', args=[self.pk]) 

[aquelf]

No problem, I don't seem to be getting the e-mail but yes that sounds exactly like the issue.