892144 - IPMI console does not display all buttons and features with update 22

Status: RESOLVED WORKSFORME

(Firefox :: Untriaged, defect)

Description

[john.screwtape]

Attachment: ipmi_console.jpg

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101 Firefox/21.0 (Beta/Release)
Build ID: 20130511120803

Steps to reproduce:

Log into an IPMI console


Actual results:

Only the navigation displays, none of the buttons show up. 


Expected results:

should see buttons. Reverted to build 21 and all works again.

Comment 1

[Loic]

Provide URL to test (online demo or similar) or a testcase (like HTML source code of the page) showing the issue.

If you save locally the page, be sure it's reprducible.

Comment 2

[temptemptemp]

Also have encountered this problem, as well as some other colleagues I've discussed this issue with. Other browsers can seem to work, but this issue seems to be an issue with the most recent releases of Firefox (previous versions worked OK; save for some delinquencies in being able to utilize the virtual-media functionality of the IPMI [at least on non-windows hosts]).

Go java/jnlp - write once, run some places, on occasion, but not if other contingent software shifts and breaks things. (sarcasm)

Having usable IPMI access is a bit fundamental to server bring up. Not all the world is running macs or AWS for their server infrastructure; and the folks who write the software for Supermicro's IPMI are not too dissimilar from what is found in other vendors either, just branded a bit differently (e.g. some Dell DRACs I suspect are also problematic with this change).

Comment 3

[john.screwtape]

I was unable to find a demo online or retrieve enough of the "website" to provide a sample. I am doubting a "real" IPMI console would be available on a public network.

Comment 4

[Loic]

Is it possible to have a testcase online? Maybe with a guest account and limited rights, just a testing server with this IMPI console.

Comment 5

[Matthias Versen [:Matti]]

nothing that we can without a testcase.
There is only one way that could help: Find the regression range with our mozregression tool.

Comment 6

[john.screwtape]

This works with build 32, so evidently was fixed along with another issue.