** Tags added: hwcert-server
--
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/1379567
Title:
maas-proxy is an open proxy with no ACLs; it should add networks
automatically
To manage n
This also needs a 1.9 target as well. I just discovered this while
investigating proxy issues on a customer MAAS server and found that they
have an open maas proxy with a ton of external connections to it :/
--
You received this bug notification because you are a member of Ubuntu
Server Team, wh
Unblocking cert on this since we can now deploy using HWE-V or later via
MAAS
** Tags removed: blocks-hwcert-server
--
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/1508565
Title:
maas
Public bug reported:
Installed a VM with 14.04.3, did a full dist-upgrade and then installed
maas from the Trusty repos.
Since no newer maas has been SRUd yet, 1.7.6 is the only MAAS available
to trusty unless you know about the PPAs. So normal users would end up
with 1.7.6, not 1.9 by default.
Any ETA on a port to Debian-ARM?
Currently using Linux version 4.1.15+ (dc4@dc4-XPS13-9333) (gcc
version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650
- Linaro GCC 2014.03) ) #830 Tue Dec 15 16:58:28 GMT 2015
Thanks.
Jeff Anttila
--
You received this bug notification
I have seen this issue as well, after being pointed to problems booting
Xen w/ Ubuntu by a colleague.
To recreate this I did the following:
Deployed a server in UEFI mode via MAAS 1.9 using the latest Xenial images from
the MAAS daily image stream.
After deployment, SSH'd to the server and insta
Removing the blocker tag since this is no longer reproducible.
** Tags removed: blocks-hwcert-server
--
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/1484268
Title:
MAAS not auto-detect
Will this be fixed in the 1.9 release?
--
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/1508565
Title:
maas uses 3.13 (hwe-t) kernel which does not work on non-virtual IBM
power
To ma
Hi,
Not sure this is still an issue, Stephane informed me that those tests
are not meant to be run stand alone and could fail in spectacular ways
when run outside of autopkgtest.
if this is not the case, let me know and when I'm home next week,
I'll dig into this further... otherwise, you can mar
On Fri, May 29, 2015 at 7:32 AM, Mario Splivalo
wrote:
> Hi, Jeff.
>
> Is this still the issue? I just tried deploying maas with ubuntu trusty,
> installing just 'maas' package, which then install everything that was
> needed (incuding maas-dns). The maas version in trus
Public bug reported:
Ran the ste lxc-test-checkpoint-restore and that failed, but there is no
explanation in the output as to why it failed. All the output I was
able to create says it created the container fine, but then just failed
for some reason:
I: Configuring libsemanage1:amd64...
I: Confi
Public bug reported:
I ran lxc-test-checkpoint-restore and it failed. So I decided to try
one additional attempt to verify the failure. However now I am unable
to re-run the test because apparently the container already exists
(previous test did not clean up after itself), however, lxc list does
Public bug reported:
on a default 15.10 installation, I have installed lxc-tests and am
running through them individually.
lxc-test-checkpoint-restore fails to run because the package criu is not
installed
ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
/usr/bin/lxc-test-checkpoint-restore: 22:
Public bug reported:
I'm investigating lxc-tests and have very little idea what they actually
do. I had hoped to read a man page, or even just pass --help to them to
get some idea of what each is actually doing.
For example, lxc-test-apparmor, I know it does something with apparmor,
but no idea
It turns out that the host command will do what you want.
jeffs@jeffs-desktop:~$ host www.g00gle.com 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
Host www.g00gle.com not found: 2(SERVFAIL)
jeffs@jeffs-desktop:~$ echo $?
1 <==
** Tags added: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1468897
Title:
multipath creates binding for Removable(USB) drives
To manage notifications about
Sorry for the vague comment earlier. What I meant was that, from a
certification point of view, I can't certify a system that ships by
default with dual RAID cards in a multipath configuration when
Multipathing in Ubuntu doesn't work. That leads to a scenario where,
out of the box on a fresh inst
I'm setting this to High for now... I really think this is critical as
it is gating the PowerNV certification work.
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided => High
** Changed in: curtin (Ubuntu)
Importance: Undecided => High
** Changed in: curtin (Ubuntu)
Importanc
Actually, on advice of Andy C, lets go ahead and consider this
critical... this cert needs to be completed as soon as possible and we
can't do that without multipathing working properly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to m
Sounds good. Thanks, Robie.
--
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/1448800
Title:
Please update iproute2 to the latest version
To manage notifications about this bug go to:
ht
Public bug reported:
That iproute2 version does not match kernel version 3.19 prevents users
from using new features in kernel 3.19 such as ipvlan.
jeffl@ubuntu:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.04
DISTRIB_CODENAME=vivid
DISTRIB_DESCRIPTION="Ubuntu 15.04"
jeffl@ubuntu:~
Other logs (pserv and maas-django) rotate, why not maas.log:
drwxr-xr-x 5 maas maas 4096 Apr 19 07:59 ./
drwxrwxr-x 24 root syslog 4096 Apr 22 07:55 ../
lrwxrwxrwx 1 root root 16 Apr 8 15:01 apache2 -> /var/log/apache2/
-rw-r--r-- 1 maas maas1092531 Apr 22 08:59 m
Public bug reported:
sudo apt-get upgrade trying to install clamav and failing
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: clamav-daemon (not installed)
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic i686
ApportVersion: 2.17.2-0ubuntu1
Archit
Public bug reported:
It looks like the location of the files is wrong in the installer. Is
there an updated source perhaps?
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: clamav-daemon 0.98.6+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10
Just a follow up, when can we expect to see this resolved in Trusty as
we move users/testers over to MAAS 1.7.1 in Trusty?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1383727
Title:
Public bug reported:
Config:
Three MySQL nodes using percona (percona-cluster charm vai juju)
Two Neutron nodes providing network services to an openstack HA deployment (all
done via juju).
Issue:
While testing failover of MySQL, we noticed that we could no longer
create instances of any sort.
I've just stumbled into this bug on 14.04.1. Worked around by commenting
out "auth required pam_shells.so" in /etc/pam.d/vsftpd and restarting
vsftpd as mentioned in 869684.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubun
I've had this error since installing the Beta of 14.04 Server, upgrading
it periodically to current release.
Using Thomas' suggestion, I ran "sudo pam-auth-update" and unchecked
"SMB Password Synchronization".
Did a test and found the problem disappeared. Good stuff.
I then decided to re-run "su
So this bit us again when trying to deploy LDS. The process there is:
Install/configure MAAs
Populate MAAS
on MAAS, install juju
Juju bootstrap
juju-deployer install LDS
then go to LDS and it does more stuff.
In this case it really caused pain in several cases where juju would say
bootstrap fail
It's beginning to look like a stack overflow segfault caused by
recursion or infinite loop. I'll turn off the security switch for now.
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
Steps to reproduce would depend on a private (Drupal-based) codebase and
database. I'll go upstream, and report back.
--
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/1385050
Title:
segf
** Information type changed from Public to Public Security
--
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/1385050
Title:
segfault and apparent memory corruption in tsrm_virtual_cwd.c
I have a test system on which I can reproduce the issue and do
additional investigation. Given the memory corruption, this may well be
a security issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launch
This is the core dump.
** Attachment added: "core-php5-fpm.16825.bz2"
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1385050/+attachment/4243073/+files/core-php5-fpm.16825.bz2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ph
Public bug reported:
I have an utterly reproducible segfault with php5-fpm 5.5.9+dfsg-
1ubuntu4.4.
Here are the top 4 backtrace frames. It looks to these relatively naive
eyes like there's memory corruption in cwd, resolved_path, trypath, and
actual_path.
This trace was generated with realpath c
Just adding more griping :) would be nice to see this fixed in Trusty
sometime before next February
bladernr@klaatu:~$ ftp transit
Connected to transit.lanes.
220 (vsFTPd 3.0.2)
Name (transit:bladernr): bladernr
331 Please specify the password.
Password:
no talloc stackframe at ../source3/param/lo
I was able to correct the issue by applying the patch at
https://bugs.archlinux.org/task/39495.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quagga in Ubuntu.
https://bugs.launchpad.net/bugs/1300940
Title:
vtysh fails to compile i
ticed that mattn’s current go-gtk package examples work :
https://github.com/mattn/go-gtk
while the Adam Langely’s go-gtk package examples do not :
https://github.com/agl/go-gtk/
So maybe that’s a useful target for git blame or something.
Best, Jeff
** Affects: golang (Ubuntu)
Impor
ticed that mattn’s current go-gtk package examples work :
https://github.com/mattn/go-gtk
while the Adam Langely’s go-gtk package examples do not :
https://github.com/agl/go-gtk/
So maybe that’s a useful target for git blame or something.
Best, Jeff
** Affects: golang (Ubuntu)
Impor
ticed that mattn’s current go-gtk package examples work :
https://github.com/mattn/go-gtk
while the Adam Langely’s go-gtk package examples do not :
https://github.com/agl/go-gtk/
So maybe that’s a useful target for git blame or something.
Best, Jeff
** Affects: golang (Ubuntu)
Impor
Maybe I misunderstand the "region controller" concept or my
understanding of the MAAS ecosystem is outdated.
AIUI there is a "region controller" that communicates with multiple
"cluster controllers" that further manage multiple "nodes":
/-- cluster foo -> node1.foo, node2.foo, node
Hrmmm... it just bit me while trying to test out the checkbox charm on
bare metal from my private maas server. and it's not just a matter of
juju.
for example, MAAS is successfully updating the zone files:
npdxh IN CNAME 10-0-0-123
and I can't ssh to my node by hostname:
ubuntu@critical-maas:/e
Additionally, do we not also use juju, region and cluster on the same
NUC inside the Orange Box? So it seems like it would be important from
the OB perspective to fix this as well. Just an additional use case.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
FWIW, this does not seem to be universal to UEFI systems. I've
performed enlistment and commissioning on several IBM systems in full
UEFI mode that behaved just fine (and a couple new density systems that
showed the same sort of issue Narninder mentions here).
--
You received this bug notificati
The init script bails out if the system is using upstart, so anything
that expects sysvinit compatibility won't work.
# Don't run if we are running upstart
if init_is_upstart; then
exit 1
fi
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscr
Looks like we've conflated two problems here -- ignoring options and the
init script not working. Would it be inappropriate for me to rename this
to focus on the init script issue?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in
This is quite a serious regression because it badly impacts integration
with other systems that depend on sysvinit compatibility.
My use case: AWS::CloudFormation::Init (cfn-init) understands sysvinit
services, but not upstream services. On Trusty, I can't restart php5-fpm
with the init script due
Bug is specific to php5-fpm.
--
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/1319595
Title:
upstart script ignores some php-fpm.conf parameters, cannot be
bypassed in preference of Sy
I have resolved my problem by running kernel 3.14.1-031401 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/, Ubuntu
14.04 LTS. The host has been running solid for a good 24 hours with 1
Windows Server 2008 R2, 2 cpu, VM running and two additional VMs running
for three hours.
The
I have a similar or the same problem with my Windows Server 2008 R2
virtual machines. The virtual machine stops with a Blue Screen error
101, clock interrupt was not received on a secondary processor. The
error only occurs when the VM has 2 cpus. The error seems to occur when
the VM is some load
Thanks for picking this up!
--
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/1334337
Title:
Regression: php5-fpm's socket should be accessible by www-data by
default
To manage notific
Yep, reproduced it on another system.
Temporary fix: sudo chown :www-data /var/run/php5-fpm.sock
Configuration fix: Uncomment "listen.group = www-data" in
/etc/php5/fpm/pool.d/www.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to p
I'm worried this fix might be broken: I upgraded php5-fpm on my 14.04
system, and the socket was changed to root:root rather than root:www-
data, so nginx could no longer connect to it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ph
Yeah, that could work.
** Changed in: maas
Status: Incomplete => 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/1304518
Title:
Confusing wording in the IPMI section o
Then again, perhaps something as simple as a 'maas-enable-nat' command
for these simple cases would be sufficient so new users don't have to
also understand iptables... and makes it optional on the maas server so
you can or can not enable it... maybe it is a per-cluster-controller
thing, as my und
As for your question about the region... I don't know... that's
operating at scale. The question there is probably one of hierarchy...
for example, would you have multiple, linked region controllers, or more
like a few region controllers and several cluster controllers under
each?
And in that cas
Hi Julian,
I've got several MAAS servers that seem to suffer the same fate,
depending on what your definition of "Access the internet" is.
We first saw this at the Orange Box sprint in london where nodes could
be deployed via d-i which was pulling packages from MAAS's squid-deb-
proxy, IIRC, howe
Julian: THAT makes more sense... perhaps this would be less confusing,
from a user standpoint:
MAC Address - Enter the BMC's MAC Address here if you are NOT using DHCP
to assign BMC IP Addresses
** Changed in: maas
Status: Incomplete => New
--
You received this bug notification because
So it would seem to confirm that MAAS is choosing the older 20140410
images over the 20140416.1 images when installing.
This is my bootresources.yaml: (The only changes I made were commenting
out older versions I didn't want to pull down)
ubuntu@critical-maas:/var/lib/maas/boot-resources$ cat
/e
I went through and deleted the rc directory from *current, and also
deleted the individual images themselves (had to compare inode numbers
in rc/ to the images in cache and deleted the images individually by
inode.
Then I did an install and it installed the correct image by default:
ubuntu@superm
Public bug reported:
I have a NUC with the current version of 14.04 and MAAS installed on it.
Today, I completely removed the contents of boot-resources and re-
imported the various boot/image files to remove old daily images and
older versions I didn't need.
If you look at the current image str
Public bug reported:
by default, there's no way for a node started by maas to talk to the
internet. There is also no way on the maas dashboard that I can see
that allows me to control this sort of network behaviour either.
For now, we are using a shell script to start NAT rules in iptables so
t
Public bug reported:
New to the power management part of node info is this text:
"MAC address - the IP is looked up with ARP and is used if IP address is
empty. This is better when the BMC uses DHCP."
What is better when the BMC uses DHCP? Does using DHCP make using ARP
better? or more accurat
Still exists in Trusty Beta 2.
--
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/1037607
Title:
vmbuilder completely fails on Quantal due to kernel pae detection
failure
To manag
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 com
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, whi
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.
HOWEVER,
Public bug reported:
?
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: libapache2-mod-python 3.3.1-11ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic i686
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
Date: Mon Jan 20 11:31:39 2014
D
Public bug reported:
I had three servers connected to my MAAS server. All three were
successfully enlisted, commissioned and in the "Ready" state.
I did a juju bootstrap which grabbed one server, powered it on and
installed and completed Juju's bootstrap bringup. This was confirmed by
running j
Yep, that was the workaround I used.
--
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
Public bug reported:
On my MAAS box running trusty:
In the MAAS UI, we created a node entry for a server, choosing IPMI and
passing the login credentials, IP for the BMC and the MAC address. On
saving the node, MAAS issued the IPMI command to turn the server on.
The server successfully powered
Public bug reported:
I have connected a Cisco UCS C220 M3 system to my MAAS server.
I have tried and succeeded in enlisting the server both automatically by
powering the server on manually, and via the UI by feeding maas the
server CIMC information and have MAAS automatically power the server on
Public bug reported:
Using latest trusty bits I manually created a node in the MAAS UI. On
setting the node, MAAS successfully powered the node on via IPMI. The
node booted and got an IP address but then failed to PXE due to PXE
timeout errors. While all this is going on, each retry prompted a
Public bug reported:
Following the docs, I did the following on a system running the latest
Trusty image with the latest MAAS packages for trusty:
$ maas-cli maas node-groups import-boot-images
On Saucy or earlier (and I believe on earlier versions of Trusty), this
would launch the olders script
https://bugs.launchpad.net/maas/+bug/1035998/comments/2
Reading that comment, it suggests that the named.conf.maas file should
be empty by design so I created one like so:
sudo touch /etc/named/maas/named.conf.maas
and restarted bind and apache.
Then, I deleted my node and retried and it su
Public bug reported:
My setup:
Trusty on an IBM Thinkpad x201.
Onboard Gigabit is static on 10.0.0.0 (The private MAAS lan)
Internet connectivity is via an 802.11n WiFi dongle
My internet connection is a 10Mbit ADSL line
I have installed and configured maas. The next step, per the
instructions h
Looked into syslog when manually restarting bind9 and it seems to hang on the
maas zone file:
Jan 7 11:28:16 critical-maas named[29464]: starting BIND
9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu2 -u bind
Jan 7 11:28:16 critical-maas named[29464]: built with '--prefix=/usr'
'--mand
Public bug reported:
Installed maas packages on a fresh trusty install like so:
$ sudo apt-get install maas maas-region-controller maas-cluster-
controller maas-dhcp maas-dns
Installation proceeded successfully until maas-dns. maas-dns errored
out:
Setting up maas (1.4+bzr1789+dfsg-0ubuntu1) .
Adding juju-core back because the bug still does affect functionality of
juju-core and needs to be tracked in juju-core project, regardless of
where/how the fix is applied.
** Also affects: lxc
Importance: Undecided
Status: New
** No longer affects: lxc
** Also affects: juju-core
Im
** Also affects: linux
Importance: Undecided
Status: New
** Project changed: linux => ubuntu
** Package changed: ubuntu => linux (Ubuntu)
** No longer affects: freeipmi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
BMC info:
IPMI SMIC interface
Broadcom Corporation
Broadcom Corporation
0.6
pci@:01:00.6
00
64
3300
Power Management
PCI Express
bus m
This error is present regardless whether maas is in use. Even using
freeipmi locally fails to set ipmi parameters or get sdr readings with
an error similar to:
map pfn expected mapping type uncached-minus for d7fa-d7fa1000, got
write-back
This is present in saucy using openipmi and freeipmi.
* Stopping target framework daemon tgtd ESC[80G
^MESC[74G[ESC[31mfailESC[39;49m]
invoke-rc.d: initscript tgt, action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
* Stopping target framework
Public bug reported:
Did a general dist-upgrade on saucy. I have TGT installed for some work
with devstack. For some reason, tgt failed to upgrade and that caused
apt to throw an error.
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: tgt 1:1.0.37-0ubuntu1
ProcVersionSignature: Ubuntu
> Could you comment on that?
It's not a trivial fix for 2.7.x. Sorry for the late reply.
-Jeff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1068145
Title:
Fix for CVE-2
Public bug reported:
.
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: open-vm-dkms 2013.04.16-1098359-0ubuntu1
ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
Uname: Linux 3.9.0-7-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.10.2-0ubuntu3
Architecture: i386
DKMSKernelVe
*** This bug is a duplicate of bug 1073238 ***
https://bugs.launchpad.net/bugs/1073238
I don't believe that this is a duplicate of Bug #1073238.
I'm able to replicate this relatively often on 3.5 and (I believe 3.8
from 13.04). lvremove remains unkillalble. I'm not using cgroups so I
don't t
On Fri, May 10, 2013 at 11:51 AM, Adam Stokes
wrote:
> Jeff,
>
> I've been searching through the documentation on puppet labs wiki but I
> am unable to find a tentative release date for 3.2.0. Do you have that
> information and if the date is set do you mind sharing that
Public bug reported:
When poking around today I saw that Dovecot is scheduled to remain at
2.1.7 for Raring. I'd been hoping that Raring would provide a newer 2.1
series build, as there have been some severe bugs fixed in 2.1.8+ and
upstream support is not too forthcoming for a release that is alm
u have any questions or concerns please let me know, I'm
getting all the updates on this issue directly to my inbox.
-Jeff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1068145
Title
d:
qemu-system-x86_64 -machine accel=kvm:tcg -m 256 -net nic -net
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -drive
file=/home/jeff/git_checkbox_dev/checkbox/scripts/precise-server-
cloudimg-amd64-disk1.img.2,if=virtio -display none -nographic
** Affects: cloud-init (Ubuntu)
Import
Maverick is dead. Closing bug properly.
** Changed in: openssh (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/641657
Title:
SSH connectio
Old bug
** Changed in: chkrootkit (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to chkrootkit in Ubuntu.
https://bugs.launchpad.net/bugs/565578
Title:
chkutmp crashed with SIGSEGV in _Unwind
Over a year old, never addressed. Closing.
I think it eventually went away so probably fixed.
** Changed in: chkrootkit (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to chkrootkit in Ubuntu.
http
I figured it out:
This documenation here: http://docs.openstack.org/trunk/openstack-
compute/admin/content/configuring-openstack-compute-basics.html has an
authentication section that has a [keystone_authtoken] group near the
top of the file.
Unfortunately, that means that the rest of the file is
I'm hitting this bug, but I both have enabled_apis defined in my
nova.conf and I don't have osapi_volume in there:
enabled_apis=ec2,osapi_compute,metadata
Could there be some other issue specific to the Ubuntu packages?
--
You received this bug notification because you are a member of Ubuntu
Se
In my case the libnss-ldapd appears to have fixed the problem... Now I
need to investigate a bit more. it also removed nscd and replaced with
nslcd. From what I'm reading so far libnss-ldapd is more robust and
causes fewer issues. Would be curious if anyone else's experience is
similar.
--
Yo
I have a similar issue, in my case it is related to ldap automount maps.
We ran into this same issue in 10.04 and ended up adding a condition in
the autofs upstart script to wait for a network connection, as well as
in the gdm (now lightdm) upstart script.
Bottom line is that the autofs startup is
Oops, did not spot that. Thanks for your help!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
https://bugs.launchpad.net/bugs/904410
Title:
Mailman configuration script causes syntax error in
"/var/lib/mailman/M
Sorry, my version as well
mailman:
Installed: 1:2.1.14-3
Candidate: 1:2.1.14-3
Version table:
*** 1:2.1.14-3 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
100 /var/lib/dpkg/status
--
You received this bug notification because you are a member of Ubu
1 - 100 of 179 matches
Mail list logo
