** 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
** 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:
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
** 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
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:
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.
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
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
** 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
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
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
** 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
** 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
** 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
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
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
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
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
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.
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.
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
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
*** 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
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
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,
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
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.
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
** 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
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
** 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
** 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
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.
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
** 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
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
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
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
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
39 matches
Mail list logo
