+1 Mike. I agree it's a bug, but it there isn't real evidence that
it's what causes the long delay.
On Mon, Feb 5, 2018 at 7:12 PM, Mike Pontillo
wrote:
> Ah, I see what you mean there; I used the following filter in Wireshark:
>
> udp.dstport == 25305 or udp.srcport == 25305
>
> This is not
- the MAC
specific file has to be generated before grub times out. It could
instead be generated before the node ever starts booting, allowing it
to be served just as fast as the -default-amd64 file is, eliminating
that race condition.
Jason
> On Mon, Feb 5, 2018 at 4:30 PM, Jason Hobbs
>
Andres,
I ran the test with VMs limited to 9 of 20 cores (cut the core limit
in half for VMs). The first time range from this dump is with the
cores at their normal limit (18).
As you can see, the behavior didn't change much from one set to the
other. Both sets had instances where grub started
Can you please comment on the deadlock detected error from the db log in
posted in #36
http://paste.ubuntu.com/26530761/
That is not expected behavior is it? Also the fact that MAAS thinks its
losing rack/region connections seems like it could be related to this
behavior.
--
You received this
On Tue, Feb 6, 2018 at 10:40 AM, Andres Rodriguez
wrote:
> On Tue, Feb 6, 2018 at 11:24 AM, Jason Hobbs
> wrote:
>
>> On Mon, Feb 5, 2018 at 4:07 PM, Andres Rodriguez
>> wrote:
>> > I think there's a misunderstanding on how the network boot process
>> ha
*dhcp* changes, so this is not at
> all related to the RPC boot requests for pxe.
>
> On Tue, Feb 6, 2018 at 11:43 AM, Jason Hobbs
> wrote:
>
>> Can you please comment on the deadlock detected error from the db log in
>> posted in #36
>>
>> http://paste.ub
The patch from #84 is adding a cache for reading the template file on
the rack controller. I don't understand why this change is being made.
This file will almost certainly be in the page cache anyhow as these
systems have a lot of free ram. Usually it's best to just let the page
cache do its th
Anyhow, I tested with the patch from #84 as requested, here are the
results: http://paste.ubuntu.com/26531873/
We're still seeing some retries with it, same as before.
But, I think the test is of limited value. It didn't make things worse
but we don't have any evidence from the test that it made
Blake, that's great. Do you have before and after numbers showing the
improvement this change made?
Do you have any data or logs that led you to believe this was the
culprit in the slow responses I saw on my cluster?
On Tue, Feb 6, 2018 at 3:12 PM, Blake Rouse wrote:
> Actually caching does mak
Andres, it was a single test in both cases, and in both cases there was
almost no delay from MAAS. It's not significant enough to call it
positive results.
Since neither of you answered yes, I'll assume the answer was no to my
question of whether there was anything in my logs or data that showed
n Tue, Feb 6, 2018 at 5:17 PM, Jason Hobbs
> wrote:
>
>> Andres, it was a single test in both cases, and in both cases there was
>> almost no delay from MAAS. It's not significant enough to call it
>> positive results.
>>
>>
> Comment #93 shows there are /
dm-delay looks very interesting along those lines.
https://www.enodev.fr/posts/emulate-a-slow-block-device-with-dm-
delay.html
https://www.kernel.org/doc/Documentation/device-mapper/delay.txt
On Tue, Feb 6, 2018 at 5:06 PM, Jason Hobbs wrote:
> On Tue, Feb 6, 2018 at 4:50 PM, Andres Rodrig
where it's getting hung up.
Jason
On Tue, Feb 6, 2018 at 5:09 PM, Jason Hobbs wrote:
> dm-delay looks very interesting along those lines.
>
> https://www.enodev.fr/posts/emulate-a-slow-block-device-with-dm-delay.html
>
> https://www.kernel.org/doc/Documentation/device-mapper/del
Andres, there is more to this bug than just the slow grub response.
MAAS could do more after the fact to recover in this situation. For
example, once a machine boots to the ephemeral environment, it has
plenty of time to talk to MAAS and find out it's not actually supposed
to be enlisting, and to
Public bug reported:
In bug 1743249, grub sometimes would hang waiting for user input on the
keyboard. This is never an appropriate action for a net booting server,
at least not one booting under MAAS direction. It may be appropriate to
pause for 30 seconds or something so someone can see the err
** Summary changed:
- when net booting servers, grub should never wait for user input to reboot
+ when net booting servers with MAAS, grub should never wait for user input to
reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Ok - I filed a few more bugs to cover the aspects of this failure other
than the slow response for grub.cfg.
bug 1747927 - grub should not hang waiting for user input when booting
from MAAS.
bug 1747928 - When a known server in Deploying state boots to the
enlisting environment, it should not jus
Steve,
Sorry, I missed comment #65 on the original bug.
I think this is a bit different question than what to do when it can't
find the file.
In that bug, grub has been instructed to fall back to
grub.cfg-default-amd64 if it can't find the file. In some cases it
does, but in others it displays t
I tested ipxe-qemu 1.0.0+git-20150424.a25a16d-1ubuntu1.2 overnight on a
xenial system by repeatedly deploying and releasing about 15 VMs.
I reproduced the original failure case and the fixed package handled it
appropriately.
Example results: http://paste.ubuntu.com/26028916/
** Tags removed: ve
The package build for zesty failed. It needs to be rebuilt. However,
since it's the exact same package as for xenial, I'm not sure it needs
separate verification.
I'm going to mark it failed for now though and get more input from more
SRU experienced folks.
** Tags removed: verification-needed
>From our perspective we don't intend to use zesty ever, so the zesty SRU
is not required. I would love for this to just go into xenial ASAP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707999
Tit
Then we would need a new version for xenial too right, and have to
re-verify it? Can we just skip zesty?
On Wed, Nov 29, 2017 at 5:45 PM, Steve Langasek <
steve.langa...@canonical.com> wrote:
> No, you need to upload with a new version number. You can't reuse a
> version number in launchpad.
>
>
@james-page When will the 2.8.1 release be?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742505
Title:
gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x
To manage notification
Attaching a pcap from a failure case. In this case, grub tried for 30
seconds to retrieve the interface specific grub.cfg, but never got a
response from MAAS. It then gave up and got the amd64-default one
instead, which caused the machine to try to enlist and then power off,
leading to a failed d
In the pcap from comment #35, MAAS eventually does respond to the
interface specific grub request, 61 seconds after the request, after
it's already sent the grub.cfg-default-amd64, kernel, and initrd. You
can see the responses to the interface specific grub.cfg requests coming
back starting at pack
** Changed in: maas
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743249
Title:
Failed Deployment after timeout trying to retrieve grub cfg
To manage notifications
Andres,
You can tell packet 90573 is a response to the requests for
grub.cfg- because its destination port (25305) is the src port the
request for grub.cfg- was coming from (packets 2 through 38).
We're running another test now to collect load information.
--
You received this bug notification
FYI those minimum requirements don't mention anything about core/thread
count.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743249
Title:
Failed Deployment after timeout trying to retrieve grub cf
I collected top output from a run (this run did not exhibit this
failure):
http://paste.ubuntu.com/26502311/
The highest the load average ever gets is 11.85, and it's usually around
3-4. This is a 20 thread system, so it doesn't look like CPU contention
is the problem.
--
You received this bug
I also collected iotop output from the same run:
http://paste.ubuntu.com/26502363/
The storage setup on these nodes is writethrough bcache with a 400 GB
nvme in front of a 1TB spinning disk. Since it's writethrough, writes
have to make it to the spinning disk before being counted as sync'd.
The
here is the complete output of top from comment #48
** Attachment added: "top.txt.gz"
https://bugs.launchpad.net/maas/+bug/1743249/+attachment/5047072/+files/top.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Here is part of a packet capture on my environment:
http://paste.ubuntu.com/26509374/
>From the other tftp server on the deploy:
http://paste.ubuntu.com/26509386/
The whole pcap is prohibitively large because it's for multiple hosts.
You can see from this that grub is only reading the file once
** Changed in: maas (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287964
Title:
MAAS incorrectly detects / sets-up BMC information on Dell Powe
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: opencompute
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210393
Title:
** Changed in: maas (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268795
Title:
unable to automatically commission Cisco UCS server due to BMC us
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+bzr226
** Also affects: python-glanceclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579768
Title:
CLI endpoint type handling broken
To manage no
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665565
Title:
python-paramiko 1.16.0-1 incompatible with python-crypto
2.6.1-6ubuntu0.16.04.1
To manage notifications about this
Here's the requested xml from an arm64 newton instance:
https://pastebin.ubuntu.com/24230654/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673467
Title:
[ocata] unsupported configuration: CPU mod
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659648
Title:
Instance hung on first start, but works after being killed and
** Also affects: percona-galera-3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606102
Title:
ppc64le - GU_PAGE_SIZE(4096) does not maptch real
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606102
Title:
ppc64le - GU_PAGE_SIZE(4096) does not maptch real system page
size(65536)
To manage notifications about this bug g
** Description changed:
I'm using MAAS to enable the following kernel flags on install/boot:
iommu=pt intel_iommu=on
in order to be able to passthrough SR-IOV VF functions to KVM guess;
however when these options are enabled, the servers fail to install (see
attached screenshot).
I think it's always been broken for us in OIL, I don't know if it ever
worked on ppc64le.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606102
Title:
ppc64le - GU_PAGE_SIZE(4096) does not maptch r
We found testing with the latest Xenial kernel (4.4.0.62.65) from
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/11278866 fixes this issue - no firmware
updates required. We did also test with just the latest firmware
updates, and that did not fix the issue. Latest firmwa
been up for 40 minutes and is getting
I/O errors now.
I'm also seeing a system with 4.4.0-59-generic #80 and no firmware updates
boot up with iommu enabled, I will see how long it stays up..
I'll also test with 4.4.0-59-generic #80 and the firmware updates.
On Mon, Jan 30, 2017 at 6:13
y up
using either 4.4.0-59-generic #80 or 4.4.0-62-generic #83, and haven't gone
offline yet from the "cat /dev/urandom > /dev/sdb" test. I will leave them
running over night.
On Mon, Jan 30, 2017 at 6:51 PM, Jason Hobbs
wrote:
> So, I appear to have spoken too soon on ex
maas 2.2.0~beta3+bzr5787-0ubuntu1~16.04.1
python3-curtin 0.1.0~bzr460-0ubuntu1~16.04.1
curtin config: http://paste.ubuntu.com/24146369/
There is nothing in /etc/network/interfaces.d/*.cfg
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notif
** Attachment added: "grepinfocloudinit.png"
https://bugs.launchpad.net/maas/+bug/1671274/+attachment/4834682/+files/grepinfocloudinit.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671274
Tit
** Attachment added: "ifupvvv.png"
https://bugs.launchpad.net/maas/+bug/1671274/+attachment/4834681/+files/ifupvvv.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671274
Title:
network interf
** Attachment added: "ipaddrdelifup.png"
https://bugs.launchpad.net/maas/+bug/1671274/+attachment/4834700/+files/ipaddrdelifup.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671274
Title:
ne
** Tags added: cdo-qa cdo-qa-blocker foundations-engine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
no matching agent binaries available with 2.2.5
To manage notifications about th
Public bug reported:
There is an nvme device on my system, at PCI::05:00.0.
Here is the lshw output:
https://pastebin.com/9t7Pj2pH
There is no 'logicalname', 'serial', or 'size' field given for the
device.
lsblk output includes all of that info:
https://pastebin.com/P2PtZ2Rn
** Affects: l
marked as invalid since we were using the wrong port.
** Changed in: maas
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628535
Title:
AH00493: SIGUSR1 received
Blake, nice work on the patch, it appears that it worked!
Here's a snippet of my syslog where you can see the machine requesting
an IP, getting NAK'd, then going back to discover state and successfully
completing dhcp with a new ip.
http://paste.ubuntu.com/25728345/
--
You received this bug not
The patch is built in ppa:blake-rouse/ipxe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707999
Title:
pod VM fails to PXE boot after receiving multiple DHCP offers, for
different IPs, from the d
Will this be fixed in xenial too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569400
Title:
mk-sbuild fails with cp: /etc/localtime... are the same file
To manage notifications about this bug go
I verified this fixes the bug with package version
0.1.0~bzr399-0ubuntu1~16.04.1
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/159
I tested tgt 1:1.0.63-1ubuntu1.1 on xenial and it fixed this bug for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547060
Ti
Public bug reported:
I want to reinit lxd with a new zfs pool. I destroyed all containers
and then used "zpool destroy lxd" to remove the original zpool. Then I
tried to use "sudo lxd init" but wasn't able to due to an existing
image.
When I try to delete the image I get:
jason@inire:~$ sudo
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618572
Title:
apt-key add fails in overlayfs
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+b
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
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: pyt
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-
Steve's suggested work around:
> # dpkg-divert --rename --add /sbin/telinit
> # cat > /sbin/telinit
> #!/bin/sh
> exit 0
> ^D
> # apt-get install [...]
> # dpkg-divert --rename --remove /sbin/telinit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1342080
Title:
glance api is tracebacking with "error: [Errno 32] Broken pipe"
To manage notifications about this bug go to:
https:/
** Changed in: maas
Milestone: None => 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210393
Title:
MAAS ipmi fails on OCPv3 Roadrunner
To manage notifications about this bug go to:
https
** Branch linked: lp:~jason-hobbs/maas/lp-1210393
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210393
Title:
MAAS ipmi fails on OCPv3 Roadrunner
To manage notifications about this bug go to
I've posted a branch with a fix to lp:~jason-hobbs/maas/lp-1210393
I've manually tested this, but for lack of access, not on OCPv3
Roadrunner.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Cool David - let me know how it works out. The branch is otherwise
complete/reviewed and ready to land.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210393
Title:
MAAS ipmi fails on OCPv3 Roadrunn
Hey Dustin - I reassigned to David since I'm not sure who will be
testing it. David/Samantha/Rod - please reassign to whoever is doing
the test!
** Changed in: maas
Status: Triaged => In Progress
** Changed in: maas
Assignee: Jason Hobbs (jason-hobbs) => David Duffey (d
** Changed in: maas (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268795
Title:
unable to automatically commission Cisco UCS server due to BMC user
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444003
Title:
BUG: soft lockup - CPU#6 stuck for 22s! [systemd-udevd:166]
To manage not
** No longer affects: cloud-archive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429739
Title:
neutron-server does not start: OperationalError: (OperationalError) no
such table: ml2_vlan_allocat
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429739
Title:
neutron-server does not start: OperationalError: (OperationalE
I tested this also and it works for me. When will this get released to
updates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518023
Title:
pip3 installs under python3.5
To manage notifications a
MAAS Team discussed this today and agreed the fix should be in lshw, not
in MAAS.
** Changed in: maas
Status: In Progress => Won't Fix
** Changed in: maas
Milestone: 1.7.0 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Tags added: oil
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381603
Title:
Log rotation for maas.log seems broken or non exist
I don't believe there are plans to fix this against Saucy.
** Changed in: linux (Ubuntu Saucy)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210393
Title:
MA
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
Bugs, which is subscribed to Ubuntu.
https://b
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305102
Title:
celeryd 100% cpu when large dhcpd lease file
To manage notificatio
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325038
Title:
Hardware enablement support for PowerKVM
To ma
Public bug reported:
The sound indicator icon is missing from the bar on the top of my
screen.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion:
blah - the "show volume in menu bar" checkbox was unchecked.
** Changed in: unity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349412
Title:
Sound indicator
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305839
Title:
FFe: Support for Third Party Driver Installation
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305839
Title:
FFe: Support for Third Pa
** Changed in: maas (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287964
Title:
MAAS incorrectly detects / sets-up BMC information on Dell PowerEd
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
Private bug reported:
please ignore for now - filling out details in a minute
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294332
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294332
Ti
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294332
Title:
MAAS fails to manage power for
Michael, please try the fix from bug 1293791.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294332
Title:
MAAS fails to manage power for system with Intel Integrated BMC
To manage notifications a
*** 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 Ubu
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12687
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
Bugs, which is subscribed to Ubun
** Branch linked: lp:~jason-hobbs/maas/lp-1279107
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268795
Title:
unable to automatically commission Cisco UCS server due to BMC user
permissions
To
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
101 - 200 of 229 matches
Mail list logo
