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

Release v2.3.4 #2152

Merged
merged 21 commits into from
Jun 7, 2018
Merged

Release v2.3.4 #2152

merged 21 commits into from
Jun 7, 2018

Conversation

jeremystretch
Copy link
Member

Bug Fixes

  • #2066 - Catch AddrFormatError exception on invalid IP addresses
  • #2075 - Enable tenant assignment when creating a rack reservation via the API
  • #2083 - Add missing export button to rack roles list view
  • #2087 - Don't overwrite existing vc_position of master device when creating a virtual chassis
  • #2093 - Fix link to circuit termination in device interfaces table
  • #2097 - Fixed queryset-based bulk deletion of clusters and regions
  • #2098 - Fixed missing checkboxes for host devices in cluster view
  • #2127 - Prevent non-connectable interfaces from being connected
  • #2143 - Accept null value for empty time zone field
  • #2148 - Do not force timezone selection when editing sites in bulk
  • #2150 - Fix display of LLDP neighbors when interface name contains a colon

dougthor42 and others added 21 commits March 1, 2018 15:05
The `upgrading.md` file does not mention reports. If the user created reports in the old version's default directory (`./netbox/reports`), then the reports will not be transferred to the new version.
Fixing typo in permission check for ClusterView.
Add missing export button to rack roles list view.
Add note about copying reports to `upgrading.md`
Those error messages looked a bit strange when I got them, hence the
fix.
Allow null values for `time_zone` field in the writeable serializer for the sites endpoint.
Fixes #2143 - PUTs to Site Endpoint Requires Value for time_zone
@jeremystretch jeremystretch merged commit a1f624c into master Jun 7, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants