** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby1.9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1293124
Title:
package ruby1.9.1 1.9.3.194-8.1ubuntu2.1 failed to install/upgrade:
Package
This issue should exit in samba-3.6.3 ubuntu2.9 version, build will fail
using the current 3.6.3 source which get from apt-get source
same issue
Waf: Leaving directory `/tmp/samba-3.6.3/bin'
input file '../heimdal/lib/wind/rfc3454.txt' could not be found
copy the rfc3454.txt to that directory
Issue is same even after replacing .bashrc and .profile file from
/etc/bash.bashrc and /etc/profile .
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1268072
Title:
byobu color prompt
Public bug reported:
Pollen servers should really have real hardware sources of entropy (tpm,
rdrand, and use rng-tools), to create and serve random seeds to its
users, when possible (by default).
** Affects: pollen (Ubuntu)
Importance: Undecided
Status: New
--
You received this
More critically, pollen's apparmor profile needs to whitelist
/dev/random in order for this to work at all!
** Changed in: pollen (Ubuntu)
Importance: Undecided = High
** Changed in: pollen (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: pollen (Ubuntu)
** Branch linked: lp:pollen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pollen in Ubuntu.
https://bugs.launchpad.net/bugs/1293958
Title:
pollen support for /dev/random
To manage notifications about this bug go to:
** Changed in: pollen (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pollen in Ubuntu.
https://bugs.launchpad.net/bugs/1293958
Title:
pollen support for /dev/random
To manage
** Branch linked: lp:ubuntu/trusty-proposed/pollen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pollen in Ubuntu.
https://bugs.launchpad.net/bugs/1293958
Title:
pollen support for /dev/random
To manage notifications about this
Public bug reported:
When I upgraded from Ubuntu 10.04 LTS server- 12.04 LTS server a problem
occurred with installing apache
I started the upgrade with the command: do-release-upgrade
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: apache2.2-common 2.2.22-1ubuntu1.4
Public bug reported:
MRE Justification:
Impact: Upstream Xen has released a stable update to 4.1.6.1. Since
Precise is based on 4.1 it would be gaining us bug fixes without waiting
for people to run into them. Like we do with upstream stable on the
kernel.
Fix: Replaced the orig tarballs with
Quantal has the same Xen version but will be out of support soon. So it
makes no sense to push for a MRE there.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/1293993
Title:
[MRE]
*** This bug is a duplicate of bug 1273272 ***
https://bugs.launchpad.net/bugs/1273272
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1273272, so is being marked as such.
** Summary changed:
- [MIR] juju-quickstart
+ [MIR] juju-quickstart, python-jujuclient, urwid, websocket-client
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1273865
Title:
I'm curious if you ever got to the bottom of this problem, and if it
still exists?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1054996
Title:
Doesn't respect ~/.byobu/backend
To
Public bug reported:
There appears to be several people online reporting issues with php5-gd
in Debian Ubuntu which are complaining about missing functions. I
felt that it was worth captuing as this may be a packaging issue, I've
tested on 14.04 latest and I can replicate the issue... it is
** Description changed:
[juju-quickstart]
Availability: in universe, arch: all.
Rationale: key component for the Juju ecosystem.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. No
privileged ports
Cut/paste fail... clearly you don't need rpm or mc installed to
replicate this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1294074
Title:
php5-gd package missing functions
Update from upstream:
Hi everyone,
It's taken longer than expected, but the tests for v0.78 are calming down
and it looks like we'll be able to get the release out this week.
However, we've decided NOT to make this release firefly. It will be a
normal development release. This will be the
*** This bug is a duplicate of bug 74647 ***
https://bugs.launchpad.net/bugs/74647
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
** Changed in: neutron (Ubuntu Saucy)
Status: Fix Released = Triaged
** Changed in: neutron (Ubuntu Saucy)
Importance: Medium = Wishlist
** Changed in: neutron (Ubuntu Trusty)
Importance: Medium = Wishlist
** Changed in: neutron (Ubuntu Saucy)
Status: Triaged = Won't Fix
--
*** This bug is a duplicate of bug 74647 ***
https://bugs.launchpad.net/bugs/74647
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This is a duplicate of a long-standing Won't Fix issue. As far as I
can determine from the previous comments, PHP upstream
** Changed in: python-jujuclient (Ubuntu)
Status: New = Triaged
** Changed in: python-jujuclient (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-jujuclient in Ubuntu.
** Changed in: juju-core (Ubuntu)
Status: New = Triaged
** Changed in: juju-core (Ubuntu)
Milestone: None = ubuntu-14.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Changed in: python-neutronclient (Ubuntu Trusty)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-neutronclient in Ubuntu.
https://bugs.launchpad.net/bugs/1292661
Title:
neutronclient
** Changed in: neutron (Ubuntu Trusty)
Assignee: (unassigned) = James Page (james-page)
** Changed in: neutron (Ubuntu Trusty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in
** Branch linked: lp:~james-page/neutron/mlnx-plugin-split
--
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/1255420
Title:
Neutron Mellanox plugin package is missing
To manage
** Changed in: ceilometer (Ubuntu Trusty)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceilometer in Ubuntu.
https://bugs.launchpad.net/bugs/1292579
Title:
[FFe] New upstream release
This update will need to be co-ordinated with the 1.18 release when it
arrives.
** Changed in: juju-quickstart (Ubuntu Trusty)
Importance: Undecided = High
** Summary changed:
- feature freeze exception to remove sudo support
+ [FFE] remove sudo support
--
You received this bug
*** This bug is a duplicate of bug 74647 ***
https://bugs.launchpad.net/bugs/74647
** Description changed:
There appears to be several people online reporting issues with php5-gd
in Debian Ubuntu which are complaining about missing functions. I
felt that it was worth captuing as this
** Changed in: neutron (Ubuntu Trusty)
Status: In Progress = Fix Committed
--
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/1255420
Title:
Neutron Mellanox plugin package is
** Branch linked: lp:~ubuntu-server-dev/neutron/icehouse
--
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/1255420
Title:
Neutron Mellanox plugin package is missing
To manage
James, thanks for the update.
Based on this, do you think Trusty should:
- Stick with the current version
Or.
- Target 0.78 for release, but then...
- If 0.79 has minimal changes, and improves stability - get that in prior
to release, if the dates make it suitable.
- Review changes
Also appears to affect Trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/74647
Title:
php5-gd not using bundled GD library
To manage notifications about this bug go to:
Please can you provide more information on the status of the 'fat
initrd', is this feature developing well? Has this concept been proved
against the 12.04 HWE options as reference, in particular arm based
servers. Can you confirm that arm based deploying is no-worse than
current.
Thanks
--
There is no need anymore to use bundled gd as long as gd 2.1 is used. We
have implemented all missing features in the upstream libgd.
On Mar 18, 2014 2:21 PM, James Lewis 74...@bugs.launchpad.net wrote:
Also appears to affect Trusty.
--
You received this bug notification because you are
Public bug reported:
The current Shift-F11 hotkey is redundant; we should do better, and
bind it to 'resize-pane -Z'. Far more useful.
** Affects: byobu (Ubuntu)
Importance: Wishlist
Assignee: Dustin Kirkland (kirkland)
Status: Fix Committed
** Changed in: byobu (Ubuntu)
bzr commit -m '* usr/share/byobu/keybindings/f-keys.tmux,
usr/share/doc/byobu/help.tmux.txt: LP: #1294139
- change Shift-F11 to zoom in/out of splits' --fixes 'lp:1294139'
Committing to: /local/media/src/byobu/byobu/
** Branch linked: lp:byobu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1294139
Title:
Shift-F11 hotkey is redundant, could do better
To manage notifications about this bug go to:
This bug was fixed in the package pollen - 4.11-0ubuntu1
---
pollen (4.11-0ubuntu1) trusty; urgency=medium
* pollen_test.go:
- fix FTBFS
- hardcode device to /dev/urandom in unit tests, otherwise, our
entropy starved vm-based builders will fail the unit tests
** Branch linked: lp:ubuntu/trusty-proposed/byobu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1294139
Title:
Shift-F11 hotkey is redundant, could do better
To manage
This bug was fixed in the package byobu - 5.76-0ubuntu1
---
byobu (5.76-0ubuntu1) trusty; urgency=medium
* usr/share/byobu/profiles/tmux:
- use nice, subtle, thin pane border, a separate color from the active
highlighted one
* usr/share/byobu/keybindings/f-keys.tmux,
Public bug reported:
I have the following in my /etc/network/interfaces to configure a GRE-
TAP tunnel and attach it to a bridge:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 10.11.12.13
netmask 255.255.255.0
gateway 10.11.12.1
auto l2gre0
iface l2gre0 inet
Public bug reported:
Upgraded keystone to 1:2014.1~b3-0ubuntu3~cloud0, get this error when
starting keystone-all:
root@controller:~$ keystone-all
Traceback (most recent call last):
File /usr/bin/keystone-all, line 109, in module
config.set_default_for_default_log_levels()
AttributeError:
Hi, is there anything I can do to help this bug's status?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise and 14.04 Trusty
To
Sorry, that was meant to be reset to New. I'm intending to set up
reproducers today and get to the bottom of it. This definately should
be fixed somehow before release. Thanks for reporting this.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
** Changed in: qemu (Ubuntu)
** Changed in: horizon
Milestone: next = icehouse-rc1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1288245
Title:
mox is needed in requirements
To manage notifications about
** Changed in: horizon
Milestone: None = next
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1288245
Title:
mox is needed in requirements
To manage notifications about this
Public bug reported:
I've taken the libnih source for trusty, and added '--enable-threads' to
the three dh_auto_configure lines in debian/rules, rebuilt ,and
installed the result. Then I took the source for cgmanager package,
rebuilt, and installed.
Finally I took
1) stick with current version
I don't think this is a good idea; the emperor release we have in
archive right now is a stable release but is not schedule for long term
focus from upstream.
2) get to firefly in a sane way
I think this is a better approach; interim releases are generally pretty
Adding ubuntu-sru as they will need to agree to option 2) as laid out in
#5
--
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/1278466
Title:
[FFe] ceph firefly stable release
To manage
James, based on prior history of ceph upstream prior releases and
continuing discussions, can we be confident that 0.79-Firefly will be
bug fix only and not featureful?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
*** This bug is a duplicate of bug 1261873 ***
https://bugs.launchpad.net/bugs/1261873
any solutions or workarounds to this bug yet?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Hi Serge,
Looking at nih's configure.ac, you actually want to use '--enable-
threading' I think. I've never used this option and tbh wasn't even
aware it was there.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: apache2 (Ubuntu Trusty)
Assignee: (unassigned) = Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1288690
Title:
default page is debian branded
Since I am a complete noob and kinda freaked out when I found this page
without simple step-by-step instructions, and since I did figure it out
myself by googling how to edit a .conf file, I figured I'd share with
other potential noobs:
-Open terminal and type sudo gedit /etc/samba/smb.conf
I've just noticed that comment in the following :-
https://bitbucket.org/libgd/gd-libgd/issue/115/backports-php-internal-
functions-to-libgd
Seems like there's a chance of a solution in the medium term, although I
guess it's probably a bit late to get this into 14.04...
--
You received this
D'oh! thanks. the enable-threads= obviously confused me. I'll re-test
with that option.
If that option *does* work, then as xnox suggested yesterday we may need
to have a separate package with threading-enabled libnih.
--
You received this bug notification because you are a member of Ubuntu
You have been subscribed to a public bug:
Upgraded keystone to 1:2014.1~b3-0ubuntu3~cloud0, get this error when
starting keystone-all:
root@controller:~$ keystone-all
Traceback (most recent call last):
File /usr/bin/keystone-all, line 109, in module
I stand corrected on 14.04, it seems that as per the link in my previous
post, only imageantialias is still missing, the rest have been
backported!
$ php -r var_dump(function_exists('imagerotate'));
bool(true)
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This looks like a packaging issue - what version of oslo.config is
installed?
** Project changed: keystone = keystone (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1294215
You have been subscribed to a public bug:
I am using Linux Mint 13 (based on Ubuntu 12.04).
Since upgrading I could not access my workdesktop. This solution uses a F5
firepass plugin in Firefox to create a sslvpn tunnel. Then I connect to my
virtual desktop by VMware View Client.
The F5
sadly that did not help, but actually seemed to make it worse (as in,
crashes faster):
[New Thread 0x76f86700 (LWP 18964)]
*** Error in `/home/serge/cgmanager-0.20/tests/cgm-concurrent[Thread
0x7fffd0ff1700 (LWP 18962) exited]
[New Thread 0x76785700 (LWP 18965)]
*** Error in
Public bug reported:
Now that open-vm-tools is main, we need to add it to the Cloud Image.
The package is benign on non-VMware targets.
** Affects: open-vm-tools (Ubuntu)
Importance: Undecided
Assignee: Ben Howard (utlemming)
Status: Invalid
** Changed in: open-vm-tools
Public bug reported:
I am using Linux Mint 13 (based on Ubuntu 12.04).
Since upgrading I could not access my workdesktop. This solution uses a F5
firepass plugin in Firefox to create a sslvpn tunnel. Then I connect to my
virtual desktop by VMware View Client.
The F5 firepass connection would
Dave: correct. There are a few very minor changes going into 0.79 to
make the final CLI/REST API experience good. We expect nothing but
performance and bug fixes for 0.80.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in
Please append the sanitized /var/log/apt/term.log.
** Changed in: kvm (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1294248
Title:
ubuntu kvm
Public bug reported:
I currently get the following failure when upgrading from havana cloud
archive to icehouse-staging cloud archive:
ubuntu@devstack:~$ dpkg -l| grep kvm
ii qemu-kvm 1.7.0+dfsg-3ubuntu6~cloud0
QEMU Full virtualization on x86 hardware
Public bug reported:
Sometime, after run a `reload tgt`, some LUNs aren't correctly added to
the targets.
The error will be reproduced above:
$ tgt-admin --dump
default-driver iscsi
target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_4
backing-store /dev/vg_vmware/vmware_4
I've prepared a provisional diff and asked the debian-apache list for
feedback: https://lists.debian.org/debian-apache/2014/03/msg00023.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
I think the problem can be related to this fact: the TGT daemon don't
add a block storage to a LUN if some process was accessing it.
The following command show another operation in which a similar problem
occours:
# All block storage added to the targets
$ tgt-admin --dump | grep -o
A do-release-upgrade -d from saucy with kvm installed succeeded fine
here. (I was not using the cloud archive however).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1294248
Title:
Sometimes, the restart operation doesn't works also:
$ tgt-admin --dump
default-driver iscsi
target iqn.2014-03.br.com.2aliancas.storage2:vmware_iscsi_4
backing-store /dev/vg_vmware/vmware_4
initiator-address 192.168.130.0/24
initiator-address 127.0.0.1
/target
target
Please also show 'apt-cache show qemu-kvm' and 'dpkg -l | grep qemu'.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1294248
Title:
ubuntu kvm upgrade failure
To manage notifications
OK - so the proposed plan is as follows:
1) Update to 0.78 release this week; this will be tested in PPA first.
2) Update to 0.79 on the assumption that it appears in +2 weeks; again
this will be tested in PPA first.
3) SRU the firefly 0.80 release into 14.04 post 17th April.
--
You received
Public bug reported:
I have a testing server which I installed Ubuntu 13.10 and then upgraded
to Ubuntu 14.04 beta using do-release-upgrade -d. I do not have the
option to create clean install with 14.04 directly as hosting provider
does not offer it yet (for obvious reasons).
Anyhow, after
*** This bug is a security vulnerability ***
Public security bug reported:
This is CVE-2014-0133.
This is Debian Bug 742059.
--
This was the nginx announcement of this issue:
Hello!
A bug in the experimental SPDY implementation in nginx was found, which
might allow an attacker to cause
Hi Ed
I tried to reproduce this by dist-upgrade'ing a havana compute node to
icehouse and although I see the same error post upgrade, the kvm package
is just a transitional package so it not require for the operation of
the system post upgrade AFAICT.
You can see why it gets un-installed:
Sage, thanks for your input.
James, If we are committing to Firefly for Trusty, I would suggest
getting 0.78 in ASAP to maximise potential exposure. I agree, with
testing 0.79 in PPA first, but again - we probably want to try and get
it in as soon as possible. That said, if 0.79 is looking late
18th Mar 19:00
OK, just downloaded an update and I am now on 2:4.1.3+dfsg-2ubuntu4, I still
cannot get a keytab, same reason. Another user has also reported the same
problem on the samba mailing list. I can confirm that this problem is easily
repeatable, just install a fresh version of Ubuntu
** Changed in: qemu (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise and 14.04 Trusty
To
Adding
-global cirrus-vga.vgamem_mb=10
to the receiving end's qemu command line options brings us past that
error. You may end up with other incompatibilities (I did) but perhaps
libvirt will ensure the rest of the devices match up. Please let us
know how it fares with that option.
--
You
Sorry, I guess that doesn't help much with your use of libvirt.
Can you please show the xml for the original VM you are migrating? It
can and should be specifying a vga ram size.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu
It seems this only requires curl?
If so then this should be fine.
status: confirmed
** Changed in: libvirt (Ubuntu)
Importance: Low = Medium
** Changed in: libvirt (Ubuntu)
Status: Won't Fix = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Thanks for reporting this bug. This is definately very odd.
If you create a container with
sudo lxc-create -t download -n u1 -- -d ubuntu -r trusty -a amd64
sudo lxc-start -n u1
does that container start fine?
Can you do
sudo lxc-start -n ubuntu -l trace -o debug.out
then kill the
Public bug reported:
I have a system with an intel iBMC onboard.
MAAS can successfully create the maas user and add/change the password,
and it also has the correct administrator priviliges.
MAAS also created the user in slot 6, the first available, rather than
choking on slot 4 or 10.
I also manually tried using the ipmipower command in addition to
ipmitool:
ubuntu@critical-maas:~$ ipmipower -h 10.0.0.125 -u maas -p TRRnqoEl9ccQy7 --off
10.0.0.125: ok
ubuntu@critical-maas:~$ ipmipower -h 10.0.0.125 -u maas -p TRRnqoEl9ccQy7
--on-if-off --cycle
10.0.0.125: ok
both of these
Since apport didn't gather any maas logs, here they are...
** Attachment added: maas-logs.tar.gz
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1294332/+attachment/4031166/+files/maas-logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team,
When you add a machine with virt-manager, the display setting is model
type='cirrus' vram='9216' heads='1'/. I tried to set it to 10240 (which
is 10mb) but that didn't help - the error is the same.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fetchmail (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to fetchmail in Ubuntu.
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.
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
BTW, that last test was with the regular qemu-kvm in trusty, which is
1.7.0+dfsg-3ubuntu6. I upgraded to the ppa-version again and ... it
seems to do something. BRB.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
I saw similar issues at IBM on 10 March. Same look to the logs, same
success with ipmitool. After an apt-get upgrade on the 11th (trusty) and
a reboot, the issues did not appear for me. I did not refresh after the
11th, though.
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
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
error: Unable to read from monitor: Connection reset by peer and the machine
crashed :-(
Next try, same as always: Length mismatch: vga.vram: 100 in != 80
That's a weird side effect, sometimes not only migration fails, but the machine
on the source host crashes, too. Did you reproduce
Key thing to check is if all binaries build with the --with-debug
option. If they all build with it, then we are not vulnerable.
(according to the Debian people)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
Quoting Valentijn Sessink (valent...@sessink.nl):
When you add a machine with virt-manager, the display setting is model
type='cirrus' vram='9216' heads='1'/. I tried to set it to 10240 (which
is 10mb) but that didn't help - the error is the same.
Yes, oddly the way to specify this is to add
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.
I'm hitting the same problem at HP. During one maas bring up the SUT did
power on and off as I expected. Since that run it fails as desribed
above.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
1 - 100 of 1375 matches
Mail list logo
