Bug? Navtree not displayed in FreenasUI

[xaibex]

Hi Folks,

Since last update (FreeNAS-9.3-STABLE-201510290351) my navtree on the left side within the web based interface of freenas is not displayed.

The Log says:

Code:

manage.py: [freeadmin.navtree:246] Failed to generate navtree for app freenasUI.sharing: 'int' object has no attribute 'lower'

Anybody experience the same?

May this be a bug?

 

[xaibex]

Just found some bug which may be related.

https://bugs.freenas.org/issues/11936

 

[ClayM]

Yep, same error, same message. Updated this morning, much to my chagrin :D

 

[jimmypooh]

Same here. I will roll back to my previous boot. Wonder how they roll out a fix. Do we need to be on this broken build in order to upgrade?

 

[ClayM]

You can still get to the update page, so I don't think it will be a problem to push a fix.

 

[Fraoch]

Just noticed this last night after updating to FreeNAS-9.3-STABLE-201510290351.

It's the bug you listed.

I might not revert to a previous boot environment unless I need something that's only accessible from the left pane. Most of what I normally need is in the top pane, so I'll just wait for a bugfix.

 

[DrKK]

Do we need to be on this broken build in order to upgrade?

No. You can leapfrog from build N-k to build N for reasonable values of k, without a problem.

 

[frankvh]

Thanks for posting this, and for providing a link to the bug report. I just updated today, and now yep I have it too. No menus in the left pane. Waiting for the fix seems like the right idea. No drama.
Frank.
www.frankvh.com

 

[Ramboxman]

Failed to generate navtree for app freenasYU.sharing: 'int' object has not attribute 'lower' build 10/29 and fix?

 

[toadman]

I have two boxes running FreeNAS-9.3-STABLE-201510290351 and everything seems fine with regard to this issue.

 

[xaibex]

Researched and found out this is caused if you for example have some shares Without Name (empty Name).

Adding a Name fixes this Problem.

(Error was: manage.py: [freeadmin.navtree:246] Failed to generate navtree for app freenasUI.sharing: 'int' object has no attribute 'lower')

 

[Yves Bruggeman]

I had the same problem and can confirm that this is indeed the fix.
thanks @xaibex

 

[Joe-freenas]

Thank you, thank you, thank you.

This was driving me crazy since the last update.

Researched and found out this is caused if you for example have some shares Without Name (empty Name).

Adding a Name fixes this Problem.

(Error was: manage.py: [freeadmin.navtree:246] Failed to generate navtree for app freenasUI.sharing: 'int' object has no attribute 'lower')

 

[Ramboxman]

How do you fix empty share or check if you have any?

 

[Ramboxman]

Never mind somehow I had two CIFS share with same directory one without name deleted one and fixed issue thanks to all!!!

 

[Fraoch]

So I see a fix has been released for FreeNAS-9.3-STABLE-201511040813. However the bug report also contains a warning not to delete the blank share:

It is the home share. If you delete it, your home share goes away.

I can't say I've noticed any issues after deleting the share. Should I recreate it? Where does it point to?

I see that there's a checkbox to create a home share. But I already have a named home share, pointing to the same location by default: /mnt/volume1. So I didn't see why I should have a blank one.

 

[xaibex]

I think this blank share was created by checking the homeshare Checkbox in a more recent version while other versions had a name for the Homeshare. I had this duplicate as well. One share without name and one with name "Homes". I never noticed it was duplicated. I just gave the blank duplicate a name, but i think deleting it will not affect anything as it is a duplicate.

 

[Ramboxman]

I had two share same directory like you, and deleting the one without name. Still not sure how it even got created! Hope this helps!