[Bug 1429739] Re: neutron-server does not start: OperationalError: (OperationalError) no such table: ml2_vlan_allocations
** No longer affects: cloud-archive -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1429739 Title: neutron-server does not start: OperationalError: (OperationalError) no such table: ml2_vlan_allocations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1429739/+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 1429739] Re: neutron-server does not start: OperationalError: (OperationalError) no such table: ml2_vlan_allocations
** Also affects: cloud-archive Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1429739 Title: neutron-server does not start: OperationalError: (OperationalError) no such table: ml2_vlan_allocations To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1429739/+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
Re: [Bug 1410876] Re: Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a directory - Could not destroy snapshot %s - failed to allocate a pty; Insufficent privileges to control juju-
This bug is hit very rarely - we deploy thousands of containers a day and
see it a few times a week. I don't have a way to reproduce it reliably
other than waiting to hit it in OIL.
On Fri, Aug 21, 2015 at 12:22 PM, Serge Hallyn 1410...@bugs.launchpad.net
wrote:
@jason-hobbs or @lmic,
can you provide a concise recipe for reproducing this in the
Description?
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1410876
Title:
Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a
directory - Could not destroy snapshot %s - failed to allocate a pty;
Insufficent privileges to control juju-trusty-lxc-template
Status in juju-core:
Invalid
Status in lxc:
Fix Released
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Trusty:
Fix Committed
Bug description:
This is for:
++ export OPENSTACK_RELEASE=juno
++ OPENSTACK_RELEASE=juno
++ export COMPUTE=nova-lxc
++ COMPUTE=nova-lxc
++ export UBUNTU_RELEASE=trusty
++ UBUNTU_RELEASE=trusty
Tool version is 1.20.14:
Launching instance
WARNING picked arbitrary tools {1.20.14-precise-amd64
https://streams.canonical.com/juju/tools/releases/juju-1.20.14-precise-amd64.tgz
932640702b5d9f08a312118a4afe330444308f92b7de350de9e547719f084bd9 8130412}
- /MAAS/api/1.0/nodes/node-5f9c14e6-ae98-11e3-b194-00163efc5068/
and agent-version on node says 1.20.13.
Juju-status.yaml:
'5':
agent-state: started
agent-version: 1.20.13
containers:
5/lxc/0:
agent-state-info: 'error executing lxc-clone: lxc_container:
utils.c: mkdir_p:
220 Not a directory - failed to create directory
''/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'';
lxc_container: lxccontainer.c: do_snapshot_destroy: 3272 Could
not destroy
snapshot %s - failed to allocate a pty; Insufficent privileges
to control
juju-trusty-lxc-template'
instance-id: pending
series: trusty
5/lxc/1:
agent-state-info: cannot clone a running container
instance-id: pending
series: trusty
dns-name: apsaras.oil
hardware: arch=amd64 cpu-cores=4 mem=32768M
tags=hw-ok,oil-slave-1,hardware-dell-poweredge-R210
instance-id:
/MAAS/api/1.0/nodes/node-5f9c14e6-ae98-11e3-b194-00163efc5068/
series: trusty
and from log:
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:150 - [7C] unit-swift-storage-1
{RequestId:42,Type:Uniter,Request:CharmURL,Params:{Entities:[{Tag:service-swift-storage}]}}
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:157 - [7C] unit-swift-storage-1 383.812us
{RequestId:42,Response:{Results:[{Error:null,Result:local:trusty/swift-storage-90,Ok:false}]}}
Uniter[].CharmURL
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:150 - [7C] unit-swift-storage-1
{RequestId:43,Type:Uniter,Request:CharmArchiveSha256,Params:{URLs:[{URL:local:trusty/swift-storage-90}]}}
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:157 - [7C] unit-swift-storage-1 777.029us
{RequestId:43,Response:{Results:[{Error:null,Result:b8aac93898c3cc661c0804613e5cce79a402fbe596400e8e80e8a3a1bb16c577}]}}
Uniter[].CharmArchiveSha256
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:150 - [61] machine-2
{RequestId:57,Type:Provisioner,Request:SetStatus,Params:{Entities:[{Tag:machine-2-lxc-0,Status:error,Info:error
executing \lxc-clone\: lxc_container: utils.c: mkdir_p: 220 Not a
directory - failed to create directory
'/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'; lxc_container:
lxccontainer.c: do_snapshot_destroy: 3272 Could not destroy snapshot %s -
failed to allocate a pty; Insufficent privileges to control
juju-trusty-lxc-template,Data:null}]}}
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:150 - [7C] unit-swift-storage-1
{RequestId:44,Type:Uniter,Request:SetCharmURL,Params:{Entities:[{Tag:unit-swift-storage-1,CharmURL:local:trusty/swift-storage-90}]}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1410876/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1410876
Title:
Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a
directory - Could not destroy snapshot %s - failed to allocate a pty;
Insufficent privileges to control juju-trusty-lxc-template
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1410876/+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 1381603] Re: Log rotation for maas.log seems broken or non existent
** Tags added: oil ** Also affects: maas 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/1381603 Title: Log rotation for maas.log seems broken or non existent To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1381603/+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 1363348] Re: Image uploads from the cli fail when file size is greater than 47406
I filed a bug and submitted a patch to fix this to the django upstream. Bug: https://code.djangoproject.com/ticket/23397 Pull request: https://github.com/django/django/pull/3151/files ** Bug watch added: Django Bug Tracker #23397 http://code.djangoproject.com/ticket/23397 ** Also affects: python-django (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-django in Ubuntu. https://bugs.launchpad.net/bugs/1363348 Title: Image uploads from the cli fail when file size is greater than 47406 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1363348/+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 1363348] Re: Image uploads from the cli fail when file size is greater than 47406
The pull request linked above also includes a unit test to reproduce the django issue, which is much easier than setting up MAAS to reproduce the django issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-django in Ubuntu. https://bugs.launchpad.net/bugs/1363348 Title: Image uploads from the cli fail when file size is greater than 47406 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1363348/+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
Juan, Can you try running this script http://bazaar.launchpad.net/~maas- maintainers/maas/trunk/view/head:/etc/maas/templates/commissioning-user- data/snippets/maas_ipmi_autodetect.py on one of the servers you're having problems with? You'll need to install freeipmi-utils first, and run it as root. This is the script that discovers and configures IPMI for MAAS. Please post its output back to this bug. Thanks, Jason -- 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 1305102] Re: celeryd 100% cpu when large dhcpd lease file
I tested an upgrade from 1.5.1 - upgraded, started an existing node, recommissioned an existing node, deleted the node, then enlisted/commissioned/installed to it without issue. -- 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/1305102 Title: celeryd 100% cpu when large dhcpd lease file To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1305102/+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 1305102] Re: celeryd 100% cpu when large dhcpd lease file
** 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 maas in Ubuntu. https://bugs.launchpad.net/bugs/1305102 Title: celeryd 100% cpu when large dhcpd lease file To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1305102/+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 1325038] Re: Hardware enablement support for PowerKVM
I found a bug related to this code in 1.5.2: https://bugs.launchpad.net/maas/+bug/1328231 -- 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/1325038 Title: Hardware enablement support for PowerKVM To manage notifications about this bug go to: https://bugs.launchpad.net/maas/1.5/+bug/1325038/+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 1317601] Re: [SRU] SRU New upstream bugfix release of MAAS
I tested 1.5.1+bzr2269-0ubuntu0.1 (from trusty-proposed) by doing a clean install, and enlisting/commissioning/stopping a node. I also tested the upgrade path by installing the current trusty release (1.5+bzr2252-0ubuntu1), enlisting/commissioning/starting a node, and then upgrading to 1.5.1+bzr2269-0ubuntu0.1, and stopping/restarting that node, and enlisting/commissioning/starting a new 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/1317601 Title: [SRU] SRU New upstream bugfix release of MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1317601/+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 1268795] Re: unable to automatically commission Cisco UCS server due to BMC user permissions
** Changed in: maas (Ubuntu) Status: In Progress = Fix Released -- 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/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1268795/+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
** Changed in: maas (Ubuntu) Status: Fix Committed = Fix Released -- 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
** Changed in: maas (Ubuntu) Status: Confirmed = Fix Committed -- 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 1305839] Re: FFe: Support for Third Party Driver Installation
Some responses to Dave's comments: * Yes, it was done quickly and isn't perfect. It's a minimum useful set of functionality to address a real use case and that improvements can be added iteratively with the benefit of getting feedback from users in the meanwhile. * fastpath can be added without a lot of extra work; we're not doing anything that prevents it from being added, I'd just rather get one install path working reasonably well before trying to get two working. * The yaml file can be edited by an admin to add additional drivers. Yes, some sort of simplestreams like approach will probably be used to replace or augment the yaml file in the future, and yes, there will be some complication in the upgrade to whatever the new source is as we'll have to maintain user additions/edits. I don't see that as insurmountable though. * I've posted a branch now that inserts the key directly into the yaml instead of retrieving it via http. Still working on a way to securely retrieve the udeb. The repo has a sha1 on the udeb; just need to work out how to validate the repo's sha1 now. * There's always a possibility for multiple drivers to be required. We've done nothing that precludes adding that capability in the future, but it isn't a supported use case for today (and I haven't seen any real use cases that require it yet). * Other arches could require it - adding support for other arches shouldn't be very difficult, but wasn't required to be useful here and is something that can added iteratively. * HWE Kernel FFe bug 1281765: I don't know what the plans are here. -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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
Re: [Bug 1305839] Re: FFe: Support for Third Party Driver Installation
On 04/14/2014 08:45 AM, Adam Conrad wrote: The whole point of having the key is to give you a trusty path to the (u)debs, surely? Yes - we need it for the udebs, and for setting up the repository in the installed system. I'm still trying to work out the details on how to verify the udebs given the public key. The installer initrd includes gpgv to verify files/sigs against a keyring; I have a public key and need to turn that into a keyring. The public key is ascii armored and so it's easy to include it in a shell script. gpgv seems to expect a non ascii armored keyring, which can't be easily included in a shell script. There are no text-binary decoders included in the installer image, afaict (cjwatson agrees). Jason -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1305839] Re: FFe: Support for Third Party Driver Installation
Looks like ash can support hexadecimal escaped strings - so that's a way forward for me. -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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 1305839] Re: FFe: Support for Third Party Driver Installation
For context, here's the branch I'm working on. It handles the insecure key retrieval problem. I plan on handling the udeb problem by inserting the keyring into the preseed, retrieving Release/Release.gpg for the repo, using the keyring to verify the Release file, then using the sha sums to verify the Packages and udeb files. https://code.launchpad.net/~jason-hobbs/maas/use-key-text/+merge/215517 -- 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/1305839 Title: FFe: Support for Third Party Driver Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1305839/+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
Can you test that it works with this: ipmipower -D LAN_2_0 -W opensesspriv -h 10.0.0.125 -u maas -p TRRnqoEl9ccQy7 --on-if-off --cycle -- 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
I think this is bug 1293791 Please try the suggested patch: http://paste.ubuntu.com/7113619/ If it works, this can be marked as a duplicate. -- 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
Kent - you may be hitting some other issue - Jeff reports that the patch from bug 1293791 fixes it for him -- 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
Michael, please try the fix from bug 1293791. -- 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 ** This bug has been marked a duplicate of bug 1293791 ipmi template tries to apply ipmi to *hosts* address rather than ipmi address -- 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 read freeipmi's code to see what the workaround does - it's very innocuous. It boils down to IPMI sessions being opened with the privilege level required for the command being used, rather than the maximum privilege level available for the user/ciphers available. For ipmipower, freeipmi uses the OPERATOR privilege level, which matches the IPMI spec's privilege level for the chassis control commands, which are used to to do on/off operations. So, this workaround shouldn't have any impact on a system that don't require it, unless the system breaks IPMI compliance by requiring a privilege level higher than OPERATOR for power commands. -- 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
MAAS should only be setting the BMCs to 2.0 if the BMC claims it has 2.0 support. IPMI settings are updated after commissioning based on what settings are changed/discovered in commissioning - see lp #1287828. -- 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
Kent, Can you please get the output of the bmc-info command, from freeipmi- utils, for one of the BMCs that isn't working? You can run it remotely like this: bmc-info -h 192.168.12.34 -u xxx -p xxx Or locally like this: bmc-info -- 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
Kent, This looks like bug 1288297. Can you try this: sudo ipmipower -W opensesspriv -D LAN_2_0 -h 10.0.0.39 -u maas -p Hg6awJQtZ --on Thanks, Jason -- 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
If you're blocked by this issue, you can workaround it by editing
/etc/maas/templates/power/ipmi.template to add use of -W opensesspriv.
I've tested this on a handful of systems that don't require the
workaround and it seems to work fine everywhere so far.
=== modified file 'etc/maas/templates/power/ipmi.template'
--- etc/maas/templates/power/ipmi.template 2014-02-26 07:05:31 +
+++ etc/maas/templates/power/ipmi.template 2014-03-05 23:12:24 +
@@ -55,9 +55,9 @@
fi
echo workaround |\
-${ipmi_chassis_config} ${driver_option} -h ${power_address} -u
${power_user} -p ${power_pass} --commit --filename ${config}
+${ipmi_chassis_config} -W opensesspriv ${driver_option} -h
${power_address} -u ${power_user} -p ${power_pass} --commit --filename ${config}
echo workaround |\
-${ipmipower} ${driver_option} -h ${power_address} -u ${power_user} -p
${power_pass} $@
+${ipmipower} -W opensesspriv ${driver_option} -h ${power_address} -u
${power_user} -p ${power_pass} $@
}
# This script deliberately does not check the current power state
--
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
** Changed in: maas (Ubuntu) Assignee: (unassigned) = Jason Hobbs (jason-hobbs) -- 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 see this on the cloud-init-output.log for the R805: Traceback (most recent call last): File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 309, in module main() File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 276, in main apply_ipmi_user_settings(user_settings) File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 194, in apply_ipmi_user_settings verify_ipmi_user_settings(ipmi_user_number, user_settings) File /tmp/sh.zyCerh/bin/maas-ipmi-autodetect, line 183, in verify_ipmi_user_settings raise IPMIError(message) __main__.IPMIError: IPMI user setting verification failures: for 'Enable_User', expected 'Yes', actual 'None'. This isn't anything that I've seen before and won't be fixed by any recent fixes. I don't see anything immediately wrong in the R610 log - please try that again with tomorrow's daily. ** Changed in: maas (Ubuntu) Status: New = In Progress -- 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 1268795] Re: unable to automatically commission Cisco UCS server due to BMC user permissions
** Tags added: server-hwe -- 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/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268795/+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 1268795] Re: unable to automatically commission Cisco UCS server due to BMC user permissions
** Changed in: maas (Ubuntu) Status: Confirmed = In Progress -- 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/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268795/+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 1268795] Re: unable to automatically commission Cisco UCS server due to BMC user permissions
I've been able to reproduce this bug using maas_ipmi_autodetect.py running on the system. Looking into why the privs aren't getting set properly now. -- 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/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268795/+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 1268795] Re: unable to automatically commission Cisco UCS server due to BMC user permissions
Seems like it doesn't happen every time - I've been able to reproduce it once, but not again. Going to write a script to repeat the user setup over and over to see if I can trigger it 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/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268795/+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 1268795] Re: unable to automatically commission Cisco UCS server due to BMC user permissions
** Branch linked: lp:~jason-hobbs/maas/lp-1279107 -- 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/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268795/+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 1268795] Re: unable to automatically commission Cisco UCS server due to BMC user permissions
I've been unable to reproduce the failure again over hundreds of tries. I ran a script that repeatedly that reset's the user in slot 10's settings, runs the maas_ipmi_autodetect.py script, and checks for the correct user permissions. It worked every time. At this point, I plan to write a patch for maas_ipmi_autodetect.py that verifies the correctness of settings after applying them. If settings are incorrect, a retry could be performed, or an error could be raised immediately. IPMI has retries built in, so if a setting isn't applied when freeipmi claims to have applied it successfully, raising an error seems like the right thing to do. This should help find the error sooner and hopefully make it easier to debug. Another thing to note is that maas_ipmi_autodetect.py doesn't check if bmc-config (freeipmi) returned an error after applying settings. I created a separate bug and merge proposal for that here https://bugs.launchpad.net/maas/+bug/1279107. The settings verification patch for this bug will depend on that patch. -- 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/1268795 Title: unable to automatically commission Cisco UCS server due to BMC user permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1268795/+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
[Blueprint servercloud-p-arm-system-management] Server System Mangement for ARM
Blueprint changed by Jason Hobbs: Whiteboard changed: - WE NEED HARDWARE!! - - * IPMI - - ipmi tool / openipmi - do we need support for both? - * Yes, but in terms of priority, OpenIPMI is higher - - No DMI - Intel only for PCI - not available on ARM? + WE NEED HARDWARE!! + + * IPMI + + ipmi tool / openipmi - do we need support for both? + * Yes, but in terms of priority, OpenIPMI is higher + [jason-hobbs 11/11/03 - What is driving OpenIPMI being a higher priority? Is there some demand from some end users or other applications for OpenIPMI over ipmitool?] + + No DMI - Intel only for PCI - not available on ARM? DMI consumers: - Landscape - serial number - libvirt requires DMI - monit - Facter? - SNMP - lshw - Any others? - + Landscape - serial number + libvirt requires DMI + monit + Facter? + SNMP + lshw + Any others? + DMI emulation will be out of scope for Precise. IPMI consumers: - Orchestra - Cobbler - Nagios - SNMP - Cluster stack / STONITH - Any others? + Orchestra + Cobbler + Nagios + SNMP + Cluster stack / STONITH + Any others? Work Items: 1. Test OpenIPMI on ARM, including Orchestra and Cobbler which are IPMI consumers. Also consider Nagios. FreeIPMI, ipmitool 2. Equivalent of DMI for ARM (for serial number etc) 3. Upstart job for running serial login on correct serial port ttyS0 + ttyAMA (linaro builds have auto serial console) - * http://comments.gmane.org/gmane.linux.linaro.devel/7939 + * http://comments.gmane.org/gmane.linux.linaro.devel/7939 4. Calxeda to verify that OpenIPMI works on current hardware so this can be verified as early as possible in this cycle. - + All of this is dependent on hardware. -- Server System Mangement for ARM https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-arm-system-management -- 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
[Blueprint servercloud-p-arm-system-management] Server System Mangement for ARM
Blueprint changed by Jason Hobbs: Whiteboard changed: WE NEED HARDWARE!! * IPMI ipmi tool / openipmi - do we need support for both? * Yes, but in terms of priority, OpenIPMI is higher - [jason-hobbs 11/11/03 - What is driving OpenIPMI being a higher priority? Is there some demand from some end users or other applications for OpenIPMI over ipmitool?] + [jason-hobbs 11/11/03 - What is driving OpenIPMI being a higher priority? Is there some demand from some end users or other applications for OpenIPMI over ipmitool? From a quick look, cobbler and nagios support ipmitool, but I'm not sure they support OpenIPMI's ipmicmd. Maybe OpenIPMI here is referring to the kernel driver that gives access to a local BMC?] No DMI - Intel only for PCI - not available on ARM? DMI consumers: Landscape - serial number libvirt requires DMI monit Facter? SNMP lshw Any others? DMI emulation will be out of scope for Precise. IPMI consumers: Orchestra Cobbler Nagios SNMP Cluster stack / STONITH Any others? Work Items: 1. Test OpenIPMI on ARM, including Orchestra and Cobbler which are IPMI consumers. Also consider Nagios. FreeIPMI, ipmitool 2. Equivalent of DMI for ARM (for serial number etc) 3. Upstart job for running serial login on correct serial port ttyS0 + ttyAMA (linaro builds have auto serial console) * http://comments.gmane.org/gmane.linux.linaro.devel/7939 4. Calxeda to verify that OpenIPMI works on current hardware so this can be verified as early as possible in this cycle. All of this is dependent on hardware. -- Server System Mangement for ARM https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-arm-system-management -- 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 845068] [NEW] ipmitool is not packaged for ARM
Public bug reported: There is no ARM version of this package. ipmitool is commonly used for managing servers. Please build an ARM version of ipmitool. ** 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/845068 Title: ipmitool is not packaged for ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/845068/+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
