@Gunnar: if you're still getting that traceback you may want to check
out your loop devices using "losetup -a", deleting any unused ones with
"losetup -d" then try again
Is this SRU still in progress? I really need this fix and avoided
patching locally because I saw the SRU had started. Is there a
** Summary changed:
- Bulit vm image file retains random temp filename
+ Built vm image file retains random temp filename
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/568687
Tit
** Changed in: ceph (Juju Charms Collection)
Assignee: (unassigned) => Chris Glass (tribaal)
--
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/1475247
Title:
ceph-disk-prepare --zap-
** Branch linked: lp:~tribaal/charms/trusty/ceph/ceph-zap-fix
** Branch linked: lp:~tribaal/charms/trusty/ceph-osd/ceph-zap-fix
** Also affects: ceph-osd (Juju Charms Collection)
Importance: Undecided
Status: New
** Changed in: ceph-osd (Juju Charms Collection)
Assignee: (unassign
** Changed in: maas (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1474417
Title:
squid-deb-proxy does not refresh translat
** Tags added: landscape-release-29
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1490727
Title:
"Invalid IPC credentials" after corosync, pacemaker service restarts
To manage n
) => Adam Collard (adam-collard)
** Changed in: swift-proxy (Juju Charms Collection)
Milestone: None => 15.10
** Changed in: swift-proxy (Juju Charms Collection)
Status: New => In Progress
** Changed in: swift-proxy (Juju Charms Collection)
Importance: Undecided => Medium
**
** Tags added: kanban-cross-team
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1516085
Title:
quotas calls fail when CONF.keymgr.encryption_auth_url is not
configured
To manage n
Public bug reported:
When lxc-net fails (because dnsmasq failed to bind on an interface), it
claims to actually be running (the /var/run/lxc/network_up file is
present)
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: lxc 1.1.5-0ubuntu0.15.10.3
ProcVersionSignature: Ubuntu 4.2.0-23.28-generi
** Also affects: haproxy (Juju Charms Collection)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1477198
Title:
Stop doesn't work on 14.0
** Changed in: haproxy (Juju Charms Collection)
Status: New => Invalid
** No longer affects: haproxy (Juju Charms Collection)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/147
** Changed in: postgresql-common (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/1382774
Title:
Postgresql installation for MAAS fai
** Package changed: ubuntu => qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1413540
Title:
qemu-kvm package enables KSM on VMs
To manage notifications about thi
Public bug reported:
There's a stated dependency in both debian/control and setup.py on
python-oops-amqp but a simple grep shows that this package is unused.
⟫ rgrep oops_amqp
setup.py:'oops_amqp',
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-txlongpoll 0.3.1+bzr86-0ubunt
Public bug reported:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
python-oops python-oops-datedir-repo python-oops-twisted python-oops-wsgi
Use 'apt-get autoremove'
*** This bug is a duplicate of bug 1438808 ***
https://bugs.launchpad.net/bugs/1438808
** This bug has been marked a duplicate of bug 1438808
1.8a9: Network and storage tables on node details page mis-aligned in Firefox
--
You received this bug notification because you are a member of Ubu
** Tags added: landscape
--
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/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go to:
https://b
> Are you still seeing this problem?
I'm seeing this problem now. For me it only started occurring after
upgrading MAAS from 1.5+bzr1977-0ubuntu3 to 1.5+bzr1977-0ubuntu4. MAAS
is no longer able to PXE boot.
To rule out any upgrade/configuration concerns I purged and reinstalled
MAAS (wiping out t
** Tags added: landscape
--
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 noti
I was adviced to try rebooting the MAAS server (region and cluster
controller on one box) which fixed the problem. But a subsequent reboot
brought it back :/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.l
So in my case, the problem was PEBKAC and networking. Specifically I had
two interfaces on my MAAS server that were connected to the same
network, both had equally weighted routes to the gateway. Only one of
them was configured in MAAS for the cluster controller. It was
(seemingly) by chance that t
On 17 March 2014 00:39, Julian Edwards <1246...@bugs.launchpad.net>
wrote:
> On Friday 14 Mar 2014 09:37:18 you wrote:
> > I was adviced to try rebooting the MAAS server (region and cluster
> > controller on one box) which fixed the problem. But a subsequent reboot
> > brought it back :/
>
> The t
The reason why the test in comment 8 was passing but we were still
seeing errors is that the APT index was up to date for Wayne, but not
for us - debootstrap vs. fastpath installer.
This might be worth noting for any future MAAS bugs, to be sure to test
it in both scenarios.
--
You received this
After I asked the cluster controller to import boot images, the
directory was created and report_boot_images tasks are now reported as
successful.
Perhaps this is a packaging bug to create that directory upfront? Not
sure whose responsibility it is, but marking as affecting Ubuntu MAAS
too.
** Al
I can confirm that this is reproducible with the steps in comment 9 with
an additional step of choosing Screen escape key (e.g. Ctrl-A).
--
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/12
** Tags added: cloud-installer
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/1303903
Title:
sgdisk zap/clear doesn't wipe all GPT tables
To manage notifications about this bug go to
I just hit this on a much smaller deploy: bootstrap with 9 LXC
containers and a hulk smashed unit on machine 0 with 4 other physical
machines.
Note that there have been many, many such deployments with the exact
same configuration, but this time it failed with a "panic: rescanned
document misses t
** Summary changed:
- provisioning large environments with complex relations caused jujud on
bootstrap node to fail
+ jujud on state server panic misses transaction in queue
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in
Note my panic was from Juju 1.20.1, I have the full log, am worried
about leaking sensitive information though.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1318366
Title:
jujud
Please see attached mongo log, it seems to be dying lots.
** Attachment added: "grep for mongod in syslog"
https://bugs.launchpad.net/juju-core/+bug/1318366/+attachment/4160060/+files/mongod-syslog
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
The recent change to lxc-templates in an attempt to fix bug #1236577
introduced a bogus flag to tar "--numeric-uid" which should be
"--numeric-owner".
⟫ sudo lxc-create -t ubuntu-cloud --name foo
2013-10-08 10:36:44 (6.13 MB/s) -
‘ubuntu-13.10-beta2-server-cloudimg-amd64-r
** Tags added: landscape
--
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/1181334
Title:
i386 required to install amd64
To manage notifications about this bug go to:
https://bugs.launch
** Tags added: micro-cluster
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-tx-tftp in Ubuntu.
https://bugs.launchpad.net/bugs/1250491
Title:
pserv log is cluttered with tftp "datagram received" messages
To manage notificati
** Tags added: landscape
--
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/1172583
Title:
maas-region-controller.config fails to preconfigure: dbc_go: not found
To manage notifications a
*** This bug is a duplicate of bug 1172583 ***
https://bugs.launchpad.net/bugs/1172583
** This bug has been marked a duplicate of bug 1172583
maas-region-controller.config fails to preconfigure: dbc_go: not found
--
You received this bug notification because you are a member of Ubuntu
Ser
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Tags added: amd64 trusty
--
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/1285567
Title:
maas-ipmi-autodete
Whoops. nagios2 not nagios
** Changed in: nagios2 (Ubuntu)
Sourcepackagename: nagios => nagios2
--
Reload action on init script kills daemon
https://bugs.launchpad.net/bugs/252686
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios2 in
** Tags added: orange-box
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1318366
Title:
jujud on state server panic misses transaction in queue
To manage notifications about this
If anyone hits this again, you should grab a dump of the Mongo db
(mongodump pointed at juju-db address)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1318366
Title:
jujud on sta
On 29 July 2014 20:12, Mark Shuttleworth <1318...@bugs.launchpad.net>
wrote:
>
> Gustavo and I are wondering whether the numactl advice might be
> relevant.
I humbly suggest that's a red herring. Note this happened on an Orange Box
(see log attached in
https://bugs.launchpad.net/juju-core/+bug/1
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1368403
Title:
juju-deployer traceback AttributeError: 'NoneType' object has no
attribute 'get_stat'
To manag
Strangely this seems to go away after I run juju status.
If I juju bootstrap, then run deployer I hit this (regularly, not
confident enough to say everytime, but certainly more times than not). I
then run juju status and run it again and it's fine.
** Changed in: juju-deployer
Status: New
Why doesn't juju-deployer talk to Juju over the API (and through
implication use "juju api-endpoints")?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1368403
Title:
juju-deployer trac
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1372977
Title:
1.7.0~beta3+bzr3043-0ubuntu1~ppa3 upgrade break
Public bug reported:
Upgrading from 1.7.0~beta5+bzr3198-0ubuntu1~trusty1 to
1.7.0~beta6+bzr3246-0ubuntu1~trusty1 gave me an extra cluster.
Cluster 9d39d468-1e68-4ed6-9cb2-8c8112378f90✓ 0 0 Synced
edit delete
Cluster master [Warning: this cluster is disconnected.]
** Aff
I believe this fix in MAAS to be wrong :/
If we look in /etc/hosts after this fix landed there is no entry for the
node's name
http://paste.ubuntu.com/8600284/
This breaks juju bootstrap:
http://paste.ubuntu.com/8600331/
--
You received this bug notification because you are a member of Ubuntu
Just did another bootstrap and it went without issue. Continuing to
investigate...
--
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/1087183
Title:
MaaS cloud-init configuration specifies
So it seems that I was actually hitting bug 1383329 - because there is
no entry in /etc/hosts anymore (fine) juju bootstrap is relying on DNS,
which was flaky (as per bug).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Tags added: landscape
--
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/1070413
Title:
MaaS http config generates warnings about missing /home/maas
To manage notifications about this
I doubt this is a dbconfig-common issue - note that the issue is that
the PostgreSQL *cluster* is missing, not the databases.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/138
Seems like the workaround described in #7 is not working, and it's
nothing to do with dbconfig-common:
ubuntu@darby:~$ locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_GB.UTF-8
LC_TIME=en_GB.UTF-8
LC_COLLA
On 12 November 2014 14:00, Martin Pitt wrote:
> Adam, what are your settings in /etc/default/locale ?
>
$ cat /etc/default/locale
# Created by cloud-init v. 0.7.5 on Wed, 12 Nov 2014 13:51:27 +
LANG="en_US.UTF-8"
I wonder if the issue here is that it's /just/ LANG being set there and not
LC
On 12 November 2014 14:17, Adam Collard
wrote:
> On 12 November 2014 14:00, Martin Pitt wrote:
>
>> Adam, what are your settings in /etc/default/locale ?
>>
>
> $ cat /etc/default/locale
> # Created by cloud-init v. 0.7.5 on Wed, 12 Nov 2014 13:51:27 +
> LANG
specifically a missing home dir is now fatal following
https://github.com/GrahamDumpleton/mod_wsgi/commit/545354a80b9cc20d8b6916ca30542eab36c3b8bd
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.ne
** Changed in: maas
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/1399016
Title:
MAAS failed to respond once libapache2-mod-wsgi upgrade on trusty
To
55 matches
Mail list logo