Opened 2 years ago
Closed 2 years ago
#344 closed defect (fixed)
FreeNAS 8 RELEASE Unable to Edit LAGG Member Startup Options
| Reported by: | kevanbrown | Owned by: | jpaetzel |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | GUI | Version: | 8.0-RELEASE |
| Keywords: | Cc: |
Description
As of FreeNAS 8 RC4 (I'm unsure of RC3, but I know the condition did not existin RC2), the GUI has a bug in it that prevents you from editing the startup parameters for LAGG member interfaces.
When you click the "Edit Members" button on a LAGG, then click the "Edit" button on one of the members, the "Physical Interface" drop-down is not pre-populated and there are no values in it to select. However, the dialog won't allow you to save your changes without a value in this drop-down. As these settings appear to be stored in a database which is then used to generate a custom configuration on boot, I don't really see a workaround for this for now. In prior builds that didn't experience this bug, I used this feature to enable jumbo frames on the LAGG member interfaces.
Attachments (4)
Change History (8)
comment:1 Changed 2 years ago by kevanbrown
Changed 2 years ago by jpaetzel
Changed 2 years ago by jpaetzel
Changed 2 years ago by jpaetzel
Changed 2 years ago by jpaetzel
comment:2 Changed 2 years ago by jpaetzel
- Owner set to jpaetzel
- Status changed from new to accepted
Attached are some screenshots of 8.0-RELEASE.
There were database schema changes involving lagg interfaces in the RC's. Is this a lagg you created in an RC and then upgraded the install? It's possible the migrations did not work properly.
comment:3 Changed 2 years ago by kevanbrown
I don't upgrade; I only use full reloads when moving between versions. So these LAGG's were created anew in the respective version where I experience the strange UI behavior.
I tested this in RC4, RC5, and RELEASE; manually creating the LAGG in each version after "clean install" (full reload) and experienced the problem in each of those builds.
comment:4 Changed 2 years ago by jpaetzel
- Resolution set to fixed
- Status changed from accepted to closed
Ok, this is sorted. I took the screenshots I did before rebooting the box. The bug was django was seeing the interfaces when django started, so until you rebooted everything worked fine. Once you restarted django the available interfaces would vanish and you'd get the behavior you were reported. This is fixed in r6475

When I say "as of RC4", I mean RC4, RC5, and RELEASE builds.