[Bug 1309860] Re: missing ipmi module
Verified on precise with both the stock precise kernel as well as the hwe-Trusty kernel. In both cases the openipmi service started without issues. Thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1309860 Title: missing ipmi module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1343407] Re: Add support for Dell PowerEdge 13G servers
To clarify further this was tested on 13G hardware as well as 12G. My mention of 12G was to ensure that there were no regressions with existing hardware. 13G hardware is also working fine with the patched package. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1343407 Title: Add support for Dell PowerEdge 13G servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1343407] Re: Add support for Dell PowerEdge 13G servers
Tested on Dell Hardware, paying particular attention to existing 12G systems so that nothing 'broke' with the update. Looking good. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1343407 Title: Add support for Dell PowerEdge 13G servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1343407] Re: Add support for Dell PowerEdge 13G servers
Updated description with required SRU fields. Please let me know if I
need to add anything else. Thanks for your help, Robie!
** Description changed:
The 13G line of Dell PowerEdge servers will be rolling out later this
year.
A patch was submitted upstream recently to add support into ipmitool for
these new servers:
http://sourceforge.net/p/ipmitool/patches/102/
We need to get this into ipmitool for Trusty and Utopic so that we are
ready for 13G.
+
+
+ [IMPACT]
+ The upstream patch is needed to support the Dell 13G line of servers,
shipping soon. They include a new version of the Dell iDRAC adapter, so,
ipmitool needs to be aware of it. 14.04 LTS needs this especially since that's
what most customers will run on their new servers.
+
+ [TEST CASE]
+ On a 13G system, make sure the following commands return sane values and/or
complete successfully
+
+ sudo ipmitool delloem mac
+ (should see all available macs in the server plus the iDRAC8 MAC address)
+
+ sudo ipmitool delloem lan
+ (should return instructions for running the command, 13G should be listed in
the instructions now)
+
+ sudo ipmitool delloem lan set dedicated
+ sudo ipmitool delloem lan set shared with lom1 (as well as lom2, lom3, etc)
+ (commands set the lan interface location which is either dedicated or shared
with a LOM)
+
+ sudo ipmitool delloem lan get
+ (should return whether the ipmi lan interface is dedicated or shared
correctly based on lan set commands above)
+
+ sudo ipmtool delloem lcd
+ (should return usage instructions and should see that 13g is included in them)
+
+ sudo ipmitool delloem lcd info
+ sudo ipmitool delloem lcd status
+ (display information about current lcd settings)
+
+ succesfully set modes on the lcd display using commands such as:
+
+ sudo ipmitool delloem lcd set mode modelname
+ sudo ipmitool delloem lcd set ipv4address
+ sudo ipmitool delloem lcd set systemname
+ sudo ipmitool delloem lcd set errordisplay sel (or simple)
+
+ ...verify the above with the 'sudo ipmitool delloem lcd info' command or
+ by physically looking at the LCD display on the server.
+
+ sudo ipmitool delloem powermonitor
+ (return sane values for power stats on the server)
+
+
+
+ [Regression Potential]
+
+ Low - the patch affects ipmi_delloem.{c,h} only. Commands handle 13G in
+ the same way that other known hardware is handled (11g, 12g, etc) - no
+ feature changes at all. Everything that worked on 12G works also on
+ 13G.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1343407
Title:
Add support for Dell PowerEdge 13G servers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1343407] Re: Add support for Dell PowerEdge 13G servers
Yes, I have done some testing on new generation as well as current generation systems with the patch, with emphasis on the delloem commands, since that's what the patches touch the most. Everything seems to be working fine on both sets of hardware. I'm fine with whatever direction ulitmately gets taken, but, keep in mind that the initial 13G rollout will be very soon (without giving away too much). Thanks for all your help! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1343407 Title: Add support for Dell PowerEdge 13G servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1343407] [NEW] Add support for Dell PowerEdge 13G servers
Public bug reported: The 13G line of Dell PowerEdge servers will be rolling out later this year. A patch was submitted upstream recently to add support into ipmitool for these new servers: http://sourceforge.net/p/ipmitool/patches/102/ We need to get this into ipmitool for Trusty and Utopic so that we are ready for 13G. ** Affects: ipmitool (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1343407 Title: Add support for Dell PowerEdge 13G servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1343407] Re: Add support for Dell PowerEdge 13G servers
Debdiff for trusty ** Patch added: ipmitool-trusty.debdiff https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+attachment/4154821/+files/ipmitool-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1343407 Title: Add support for Dell PowerEdge 13G servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1343407] Re: Add support for Dell PowerEdge 13G servers
Utopic Debdiff ** Patch added: ipmitool-utopic.debdiff https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+attachment/4154831/+files/ipmitool-utopic.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1343407 Title: Add support for Dell PowerEdge 13G servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1343407/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321885] Re: IPMI detection and automatic setting fail in ubuntu 14.04 maas
Try the script mentioned above and post the output: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1321885/comments/22 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1321885 Title: IPMI detection and automatic setting fail in ubuntu 14.04 maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1321885/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321885] Re: IPMI detection and automatic setting fail in ubuntu 14.04 maas
Took a shot at trying to address this. We'll see what the maintainers say. ** Branch linked: lp:~kentb/maas/bug-1321885 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1321885 Title: IPMI detection and automatic setting fail in ubuntu 14.04 maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1321885/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321885] Re: IPMI detection and automatic setting fail in ubuntu 14.04 maas
Fixed the bug title from the original reporter so that it's easier to find. ** Summary changed: - IMPI detection and automatic setting fail in ubuntu 14.4 maas + IPMI detection and automatic setting fail in ubuntu 14.04 maas -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1321885 Title: IPMI detection and automatic setting fail in ubuntu 14.04 maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1321885/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321885] Re: IPMI detection and automatic setting fail in ubuntu 14.04 maas
grick23's workaround also seems to 'fix' this for a PowerEdge R805. Previously, this machine also had trouble with MAAS auto-detecting the IPMI settings with 14.04. So, it looks like many Dell 10th generation (10G) and older machines will run into problems based on the type of DRAC / BMC installed in them. As was stated in comment #33, the more modern 11G and 12G systems have no issues with the IPMI auto-detection. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1321885 Title: IPMI detection and automatic setting fail in ubuntu 14.04 maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1321885/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321885] Re: IMPI detection and automatic setting fail in ubuntu 14.4 maas
If the 1950's and 1750's are having problems, what type of response do you get from this command?: ipmipower -h bmc ip address -u bmc username -p bmc password --stat Preferably you'll want to run that from the maas server running 14.04. On a very basic level, that's what MAAS is using to bring the nodes up and down. If your MAAS server is not running 14.04 then install freeipmi-tools on another system running 14.04 and see if you can contact the 1950's BMC with it. In my lab I have an old R805 that was doing simliar things with regard to MAAS picking up the BMC properly. Adding in the ipmi v1.5, ip address, username and password got it working with 14.04 maas. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1321885 Title: IMPI detection and automatic setting fail in ubuntu 14.4 maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1321885/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1321885] Re: IMPI detection and automatic setting fail in ubuntu 14.4 maas
..and if that doesn't work, then try: ipmipower -D LAN -h bmc ip address -u bmc username -p bmc password --stat Plus, I know these machines are older, but, is the latest BMC firmware installed on these affected systems? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1321885 Title: IMPI detection and automatic setting fail in ubuntu 14.4 maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1321885/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1294332] Re: MAAS fails to manage power for system with Intel Integrated BMC
Also broken on at least two Dell PowerEdge servers: The R820 and R620. I can also use the commands by hand and they work...but commissioning via the web UI doesn't work at all. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1294332 Title: MAAS fails to manage power for system with Intel Integrated BMC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1294332/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1294332] Re: MAAS fails to manage power for system with Intel Integrated BMC
Same traceback in celery.log as well. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1294332 Title: MAAS fails to manage power for system with Intel Integrated BMC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1294332/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1294332] Re: MAAS fails to manage power for system with Intel Integrated BMC
Jason, I commented those lines out in an earlier attempt to see if that would fix things, but, my nodes still won't power up when clicking commission node -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1294332 Title: MAAS fails to manage power for system with Intel Integrated BMC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1294332/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1294332] Re: MAAS fails to manage power for system with Intel Integrated BMC
*** This bug is a duplicate of bug 1293791 *** https://bugs.launchpad.net/bugs/1293791 Ok. blanking out the lines completely via the patch in bug 1293791 did the trick. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1294332 Title: MAAS fails to manage power for system with Intel Integrated BMC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1294332/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
I tried 1.5+bzr1977+2072+245~ppa0~ubuntu14.04.1 just now today and the results were no different for the M610 or the R805. For the M610 I had to power the system up manually or change the username and password parameters in the UI to get the system to commission, etc. The logs don't show anything that jumps out on systems that behave this way. MAAS appears to be OK with the settings it passes to the BMC. Today, I found that I can run the ipmipower command manually with the generated maas username and password and that works on the M610: $ sudo ipmipower -h 10.0.0.39 -u maas -p Hg6awJQtZ --stat 10.0.0.39: off $ sudo ipmipower -h 10.0.0.39 -u maas -p Hg6awJQtZ --on 10.0.0.39: ok $ sudo ipmipower -h 10.0.0.39 -u maas -p Hg6awJQtZ --off 10.0.0.39: ok ..the Web UI, for some reason, when clicking 'commission node' or 'start node' won't power up the machine unless I pass the username and password that's already on the BMC (i.e. root/calvin). For the R805, the same traceback occurs at enlistment time (which is no surprise given what Jason had said yesterday). I'll also try the version of maas that's in the main trusty repos that Andres uploaded (1.5+bzr1977-0ubuntu3) to see if things are any different. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
Also tested with a freshly-installed maas server using 1.5+bzr1977-0ubuntu3 on Trusty. I am also seeing the same symptoms as originally reported. The power settings fail to get configured for the R805 and the M610 also displays the same behaviors as listed in the previous comment. I will also test out a few more sample systems to see what things look like. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
I have one machine that actually gets set up correctly so far. The PowerEdge T410 is the system. After enlistment, MAAS assigns the maas username and password and sets the driver type to IPMI 2.0. On this system, I can actually click commission node and it powers on without issues via the Web UI. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
The PowerEdge R620 also works fine with regard to enlisting and commissioning. At the end of enlistment it's also set to IPMI 2.0 and I can power it up from the WebUI. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
For the M610 using version 1.5+bzr1977-0ubuntu3 I think I found a reason why it refused to power up via the UI after enlistment. At enlistment time, the Power Driver settings for that BMC are improperly being identified as IPMI 2.0, when they should be IPMI 1.5. If I go and set the IPMI Power Driver in the UI for the node to 1.5 and leave the maas-generated username and password alone, then the machine will power up when I click commission node. The odd thing, though, seems to be that after commissioning the node, the IPMI power settings do not stick...they fall back to IPMI 2.0 from 1.5 and it looks like I have a new maas-generated password on the BMC. I have to set it back to 1.5 every time before trying to power the node up again via the UI. I also saw this with a PowerEdge M915. So, it looks as if MAAS is setting the BMCs to IPMI 2.0 no matter what? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
PowerEdge R710 also works fine with the IPMI driver defaulted to 2.0 after enlistment. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
Here you go. Attaching output from M610 and M915. Both are blades sitting in the same chassis. Each server has its own dedicated BMC and both look to be advertising IPMI 2.0. However, unless I select auto- detect or IPMI 1.5 from the UI, the systems will not power up when selecting 'commission node' or 'start node'. This ipmipower command works: $ sudo ipmipower -h 10.0.0.39 -u maas -p Hg6awJQtZ --on 10.0.0.39: ok but the same command when I use the LAN_2_0 parameter doesn't: $ sudo ipmipower -D LAN_2_0 -h 10.0.0.39 -u maas -p Hg6awJQtZ --on 10.0.0.30: BMC Error So, for some reason even though the BMC says it can do IPMI 2.0 I can't run any commands against it using IPMI 2.0 ?field.comment=Here you go. Attaching output from M610 and M915. Both are blades sitting in the same chassis. Each server has its own dedicated BMC and both look to be advertising IPMI 2.0. However, unless I select auto-detect or IPMI 1.5 from the UI, the systems will not power up when selecting 'commission node' or 'start node'. This ipmipower command works: $ sudo ipmipower -h 10.0.0.39 -u maas -p Hg6awJQtZ --on 10.0.0.39: ok but the same command when I use the LAN_2_0 parameter doesn't: $ sudo ipmipower -D LAN_2_0 -h 10.0.0.39 -u maas -p Hg6awJQtZ --on 10.0.0.30: BMC Error So, for some reason even though the BMC says it can do IPMI 2.0 I can't run any commands against it using IPMI 2.0 ** Attachment added: M610-info.txt https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+attachment/4008943/+files/M610-info.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
** Attachment added: M915.txt https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+attachment/4008944/+files/M915.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
Ok. WIth the addition of the -W opensesspriv parameter to the command for that blade I finally get a sane status back from the BMC. On the node in question I can run --stat, --on, or --off and all three commands now work when they didn't before. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
Same here. I just tested on a machine that didn't need the parameter and didn't seem to have a negative impact. I will leverage this workaround until you guys decide the final fix / resolution. I'll let you know if there are any negative side effects along the way. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] [NEW] MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
Public bug reported: Beginning with MAAS 1.5+bzr1977-0ubuntu2 and up to today's daily builds (1.5+bzr1977+2064+245~ppa0~ubuntu14.04.1), maas no longer seems to either detect or properly configure the BMCs on Dell PowerEdge servers during enlistment. I've noticed two scenarios: 1) When the system enlists, the enlistment itself appears to work OK, but, when I look at the node in the MAAS WebUI, MAAS tells me that there is no power type set and that I need to set one. 2) The system enlists OK, and node's Power Parameters in the UI appear to be filled out fine. In other words, the correct Power driver is populated as well as the correct IP address for the BMC. I also have a 'maas' power user and generated password. However, if I click 'commission node' nothing happens (i.e. the node doesn't power on). Workarounds: In scenario #1 if I go and fill out the IPMI information by hand for an affected node, then commissioning, etc. works fine after that. In scenario #2 if I change the Power User and Power Password parameters in the UI to what's already on the BMC (i.e. root/calvin), then commissioning, etc. works fine after that. This is the first time in a while that PowerEdge didn't 'just work' with MAAS with regard to power settings. I know there has been some churn in the IPMI department lately for MAAS. I'll be attaching logs for each one of the PowerEdges affected by the respective scenarios. ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
Here are the logs from a PowerEdge M610, which exhibits scenario #2. Scenario #2 seems to be the most common problem I've been having as of late. If you need logs from the commissioning phase on one of these I can try and grab those, too. ** Attachment added: M610-cloud-init.tar.gz https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+attachment/4007488/+files/M610-cloud-init.tar.gz ** Description changed: Beginning with MAAS 1.5+bzr1977-0ubuntu2 and up to today's daily builds (1.5+bzr1977+2064+245~ppa0~ubuntu14.04.1), maas no longer seems to either detect or properly configure the BMCs on Dell PowerEdge servers during enlistment. I've noticed two scenarios: 1) When the system enlists, the enlistment itself appears to work OK, but, when I look at the node in the MAAS WebUI, MAAS tells me that there is no power type set and that I need to set one. - - 2) The system enlists OK, and node's Power Parameters in the UI appear to be filled out fine. In other words, the correct Power driver is populated as well as the correct IP address for the BMC. I also have a 'maas' power user and generated password. However, if I click 'commission node' nothing happens (i.e. the node doesn't power on). + 2) The system enlists OK, and node's Power Parameters in the UI appear + to be filled out fine. In other words, the correct Power driver is + populated as well as the correct IP address for the BMC. I also have a + 'maas' power user and a pre-generated password. However, if I click + 'commission node' nothing happens (i.e. the node doesn't power on). Workarounds: - In scenario #1 if I go and fill out the IPMI information by hand for an - affected node, then commissioning, etc. works fine after that. + In scenario #1 if I go and fill out all of the IPMI information by hand + for an affected node, then commissioning, etc. works fine after that. In scenario #2 if I change the Power User and Power Password parameters - in the UI to what's already on the BMC (i.e. root/calvin), then - commissioning, etc. works fine after that. + in the UI from 'maas' and the pre-generated password to what's already + on the BMC (i.e. root/calvin), then commissioning, etc. works fine after + that. This is the first time in a while that PowerEdge didn't 'just work' with MAAS with regard to power settings. I know there has been some churn in the IPMI department lately for MAAS. I'll be attaching logs for each one of the PowerEdges affected by the respective scenarios. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1287964] Re: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers
I'm attaching the cloud-init logs from a PowerEdge R805, which exhibits scenario #1. ** Attachment added: R805-cloud-init.tar.gz https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+attachment/4007487/+files/R805-cloud-init.tar.gz -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1287964 Title: MAAS incorrectly detects / sets-up BMC information on Dell PowerEdge servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1287964/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274443] [NEW] Retro-fit support for picking up package mirror settings onto Precise for Fastpath Installer
Public bug reported: In a bug report from earlier this week: https://bugs.launchpad.net/maas/+bug/1273650 ..some work was done in MAAS so that images being deployed via fastpath would honor package archive settings. In other words, this would allow you to leverage your local mirrors instead of archive.ubuntu.com. We found out that this works for Trusty, but not Precise. If possible, it'd be nice to try and retro-fit the things that worked for Trusty onto Precise. ** Affects: curtin (Ubuntu) Importance: Undecided Assignee: Adam Stokes (adam-stokes) Status: New ** Affects: curtin (Ubuntu Precise) Importance: Undecided Assignee: Adam Stokes (adam-stokes) Status: New ** Tags: micro-cluster ** Summary changed: - Retro-fit support for picking up package mirror settings onto Precisef + Retro-fit support for picking up package mirror settings onto Precise for Fastpath Installer -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1274443 Title: Retro-fit support for picking up package mirror settings onto Precise for Fastpath Installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1274443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274443] Re: Retro-fit support for picking up package mirror settings onto Precise for Fastpath Installer
closing out. The fixes that Graham applied yesterday to the bug I mentioned do indeed work for Precise AND Trusty. We just confirmed that. False alarm on this one. ** Changed in: curtin (Ubuntu) Status: New = Invalid ** Changed in: curtin (Ubuntu Precise) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1274443 Title: Retro-fit support for picking up package mirror settings onto Precise for Fastpath Installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1274443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1266840] Re: maas-dns failed to install completely on Trusty
I hit this as well. To get around it (at least for me), I ran: sudo apt-get purge maas-dns sudo apt-get install maas-dns ...then maas-dns started working again. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1266840 Title: maas-dns failed to install completely on Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1266840/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1244292] [NEW] Sync ipmitool 1.8.13-1 (universe) from Debian unstable (main)
Public bug reported: Please sync ipmitool 1.8.13-1 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * d/p/revert_default_cipher_suite_id: cherry-pick upstream reversion of regressed default protocol selection (LP: #1176202). * d/p/revert_default_cipher_suite_id: cherry-pick upstream reversion of regressed default protocol selection (LP: #1176202). 1.8.13-1 should already have these fixes in it. Changelog entries since current trusty version 1.8.12-1ubuntu1: ipmitool (1.8.13-1) unstable; urgency=low * New upstream release - Fixes regression in default cipher suite selection (Closes: #708621). -- Luk Claes l...@debian.org Wed, 18 Sep 2013 07:45:10 +0200 ** Affects: ipmitool (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1244292 Title: Sync ipmitool 1.8.13-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1244292/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1218852] Re: [SRU] hostnames with upper case letters don't make good MON's
Looks like it fixes it for me. I installed the new ceph package then restarted ceph-mon-all and the charm status went from being stuck at installed to started. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1218852 Title: [SRU] hostnames with upper case letters don't make good MON's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1218852/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1204507] Re: MAAS rejects empty files
I can also verify that the -proposed set allows me to avoid the bootstrap issues on Precise and juju-core 1.13. So far no new breakage / regressions have occurred with this update. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1204507 Title: MAAS rejects empty files To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1204507/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074443] Re: Please upgrade ipmitool to 1.8.12 for 13.04
** Changed in: dell-poweredge Assignee: Kent Baxley (kentb) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1074443 Title: Please upgrade ipmitool to 1.8.12 for 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1074443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074443] Re: Please upgrade ipmitool to 1.8.12 for 13.04
** Changed in: dell-poweredge Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1074443 Title: Please upgrade ipmitool to 1.8.12 for 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1074443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074443] Re: Please upgrade ipmitool to 1.8.12 for 13.04
Hi Robie, I tested your ipmitool package today on a Dell PowerEdge R820. I installed ipmitool, rebooted, and was able to run several commands successfully. The delloem commands all seemed to work fine, too. I was also able to successfully perform a BMC firmware update with this new version of the package. If you need anything else, please let me know. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1074443 Title: Please upgrade ipmitool to 1.8.12 for 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1074443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074443] Re: Please upgrade ipmitool to 1.8.12 for 13.04
I've built 1.8.12 and have a copy of it for precise stored here: https://launchpad.net/~kentb/+archive/ipmitool-latest This is based on the released tarball from: http://sourceforge.net/projects/ipmitool/files/ipmitool/1.8.12/ipmitool-1.8.12.tar.gz/download It's been installed and tested on a PowerEdge T410 running 12.04.2. So far the commands seem to be working fine. There are, however, some additional features that may be required in impitool that aren't in an official release yet. Many of those features are listed here: https://fedoraproject.org/wiki/Features/AgentFreeManagement For example, the ipmitool mc setsysinfo commands to publish OS information to service processor aren't in the released version of the code, but, they are in the cvs repository.Fedora 18 looks to have already pulled this in: https://bugzilla.redhat.com/show_bug.cgi?id=857878 ** Bug watch added: Red Hat Bugzilla #857878 https://bugzilla.redhat.com/show_bug.cgi?id=857878 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1074443 Title: Please upgrade ipmitool to 1.8.12 for 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1074443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074443] Re: Please upgrade ipmitool to 1.8.12 for 13.04
Hi Jose, Our first attempt was to try and get the updated version into upstream Debian, but the request has stalled out: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692292 Getting into debian-unstable would make it easeir to pull into Raring, then backport down into Quantal and Precise. Since things are moving slow here, we're going to look at another means of getting this out faster for PowerEdge users in the meantime. I'll come talk to you about what we've got in mind. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1074443 Title: Please upgrade ipmitool to 1.8.12 for 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1074443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074443] Re: Please upgrade ipmitool to 1.8.12 for 13.04
** Also affects: dell-poweredge Importance: Undecided Status: New ** Changed in: dell-poweredge Importance: Undecided = Wishlist ** Changed in: dell-poweredge Assignee: (unassigned) = Kent Baxley (kentb) ** Changed in: dell-poweredge Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1074443 Title: Please upgrade ipmitool to 1.8.12 for 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1074443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074443] Re: Please upgrade ipmitool to 1.8.12 for 13.04
Once this is updated, then we will need to backport it to Quantal and Precise. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1074443 Title: Please upgrade ipmitool to 1.8.12 for 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1074443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074443] Re: Please upgrade ipmitool to 1.8.12 for 13.04
I could get the source package from the URL in the description to build by making the following modifications: http://bazaar.launchpad.net/~kentb/+junk/ipmitool-1.8.12/revision/2 This package also installed / updated cleanly on a server running the current version of ipmitool for precise. The ipmi dell oem commands (which is a new feature with this update) also seem to work without issue so far on a PowerEdge R420. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1074443 Title: Please upgrade ipmitool to 1.8.12 for 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1074443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1074443] [NEW] Please upgrade ipmitool to 1.8.12 for 13.04
Public bug reported: Please consider upgrading ipmitool to 1.8.12 for the next Ubuntu release. 1.8.11 has been out for 3 years now. 1.8.12 has numerous bug fixes and includes the new DELL OEM commands for the 12G PowerEdge Servers. The ChangeLog is pretty big so I'm including it as an attachment. This package is currently not in debian-unstable. http://sourceforge.net/projects/ipmitool/files/ipmitool/1.8.12/ipmitool-1.8.12.tar.gz/download ** Affects: ipmitool (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version ** Attachment added: ChangeLog https://bugs.launchpad.net/bugs/1074443/+attachment/3421913/+files/ChangeLog -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1074443 Title: Please upgrade ipmitool to 1.8.12 for 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1074443/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 974450] Re: irqbalance classifies network interfaces with custom/renamed interfaces as class other
I'd like to second the importance of having a working irqbalance now rather than later now that biosdevname is available in 12.10. I think it'd be worth it to try and get a feature freeze exception for this. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/974450 Title: irqbalance classifies network interfaces with custom/renamed interfaces as class other To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/974450/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
