For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Angelo_Turetta1's avatar
Angelo_Turetta1
Icon for Nimbostratus rankNimbostratus
Sep 04, 2014

Annoying bug on LTM nodes/pools list (11.5.1 HF4)

Hi all,

 

I just replaced our 11.2.1 8900 pair with a brand new pair of 11.5.1 7250v

 

I noticed a very repeatable bug on the web interface. I go to "Local traffic/Nodes" and click on the 'Address' column header to change the sort order, from now on the page "Local traffic/Pools" shows only an error "General database error retrieving information."

 

 

If I restore the sort order of the Nodes list by clicking on the 'Name' column heading, the 'Pools' page resumes working.

 

My system has 104 pools and 168 nodes, and I have set to 300 the list length in preferences.

 

It seems a rather simple bug somewhere in the web interface code.

 

Thanks, Angelo.

 

37 Replies

  • Same issue on 11.5.4 HF 2. As mentioned above, re-sorting the nodes corrects the issue.

     

  • Same issue on 11.5.4 HF 2. As mentioned above, re-sorting the nodes corrects the issue.

     

  • Same issue on 11.5.4 HF 2. As mentioned above, re-sorting the nodes corrects the issue.

     

  • Same issue on 11.5.4 HF 2. As mentioned above, re-sorting the nodes corrects the issue.

     

  • could you open a case with F5 support??

     

    This is now tracked under Bug ID481003 - TMUI -- Browsing to "Pool List" menu throws SQL Exception because of invalid column

     

    Tested against versions we had in handy: •11.5.1-final failed (problem repro-ed), •11.5.1-hf5 failed •11.5.1-hf7 failed • 11.5.1-hf8 failed •11.6.0-final passed •11.6.0-hf1 passed

     

    Please continue to open a support case so the issue is logged in F5's system. Then F5 Support can then add/link your case to the bug ID.

     

    Cheers,

     

    Kees

     

  • I don't see any value in keep adding notes here saying that you are facing this bug. Please read iamczar post above, and open a case so more case gets assigned to that bug id. As the bug is identified, also the workaround, the only next action is to open a case with F5.