Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-13.11:
Setup Trusty Icehouse in Openstack-CI: DONE
Setup Precise Icehouse in Openstack-CI: DONE
Write MIR report for httpretty: INPROGRESS
Write MIR report for mox3: INPROGRESS
Setup staging PPA for precise
Great! Many thanks Chuck :-)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1264815
Title:
nova-compute can't be setting up during install on trusty
To manage notifications about
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-13.11:
Setup Trusty Icehouse in Openstack-CI: DONE
Setup Precise Icehouse in Openstack-CI: DONE
Write MIR report for httpretty: INPROGRESS
Write MIR report for mox3: INPROGRESS
Setup staging PPA for precise
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-13.11:
Setup Trusty Icehouse in Openstack-CI: DONE
Setup Precise Icehouse in Openstack-CI: DONE
Write MIR report for httpretty: INPROGRESS
Write MIR report for mox3: INPROGRESS
Setup staging PPA for precise
Blueprint changed by James Page:
Work items changed:
Work items for ubuntu-13.11:
Setup Trusty Icehouse in Openstack-CI: DONE
Setup Precise Icehouse in Openstack-CI: DONE
Write MIR report for httpretty: INPROGRESS
Write MIR report for mox3: INPROGRESS
Setup staging PPA for precise
#13 contained the fix for me. commenting out the following gave ypbind
enough time to start so autofs correctly started as well
#if status ypbind | grep -q start/respawn; then
# # something killed ypbind; short-circuit here instead
# # of continuing to try to call ypwhich, since
I have noticed the same problem when using gnome-terminal + mosh = mouse
scroll goes trough command history (like pressing keys up and down)
instead of scrolling the (as would be correct in that situation and what
e.g. xterm does).
--
You received this bug notification because you are a member
Public bug reported:
If I install (or reinstall) the mongodb-server package everything is
fine.
At the end of the installation the server is properly started and
clients can connect to it.
At that time, the owner of the /var/log/mongodb folder is 'mongodb'.
But as soon as the machine is
Ok, the patch is now applied in gnome-terminal and I disabled in the
profile the option 'Whether to send keystrokes for alternate screen
scrolling' to fix this annoying behaviour for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Description changed:
If I install (or reinstall) the mongodb-server package everything is
fine.
- At the end of the installation the server is properly started and
+ At the end of the installation the server is properly started and
clients can connect to it.
At that time, the
Public bug reported:
Currently, if one sets START=no in /etc/default/puppetmaster, the init
script will exit with exit-code 0, regardless of whether the service is
running or not. In the case where you have a puppet manifest like:
service { 'puppetmaster': ensure = stopped }
Puppet will try to
Since some deployments will want the global default group added to Juju
machines and others not, we've decided to make it configurable - the
default is false so existing behaviour is preserved. But deployments
that want to use the default group can do so but changing the config
option to true.
--
Hello,
please attach your
/etc/mongodb.conf
/etc/init/mongodb.conf
Thanks
** Changed in: mongodb (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
** Attachment added: /etc/init/mongodb.conf
https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+attachment/3945376/+files/mongodb.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This sounds reasonable. Please see
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for the process.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Attachment added: /etc/mongodb.conf
https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1267791/+attachment/3945375/+files/mongodb.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
Public bug reported:
I booted the 13.10 live cd using -vga std ( since the default cirrus no
longer works correctly ) and it comes up using the full resolution of my
real screen, which is annoying since the window does not fit no the
screen. I went into the display control pannel to switch to a
Hello Nico,
please test this hotfix:
In file /etc/init/mongodb.conf
[...]
pre-start script
mkdir -p /var/lib/mongodb/
mkdir -p /var/log/mongodb/
+touch /var/log/mongodb/mongodb.log
+chown -R mongodb /var/lib/mongodb/
+chown -R mongodb /var/log/mongodb/
end script
[...]
and
** Changed in: walinuxagent (Ubuntu)
Milestone: None = ubuntu-14.04-beta-1
** Changed in: walinuxagent (Ubuntu)
Assignee: (unassigned) = Ben Howard (utlemming)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in
Public bug reported:
Testing rabbit active/active charm, found an issue. I add some clustered rabbit
units, for example 4 units. When i list all the relations with relation-list i
get the correct list:
INFO got units: ['rabbitmq-server/0', 'rabbitmq-server/1',
'rabbitmq-server/2']]
Then i
Blueprint changed by Chuck Short:
Work items changed:
Work items for ubuntu-13.11:
Setup Trusty Icehouse in Openstack-CI: DONE
Setup Precise Icehouse in Openstack-CI: DONE
Write MIR report for httpretty: INPROGRESS
Write MIR report for mox3: INPROGRESS
Setup staging PPA for precise
Hello Jörg,
I tried the hotfix you suggested and it works.
At the same time I tried a fresh install in a virtualbox and mongodb-
server works out of the box.
It seems I'm the only one to have this problem so it might come from
something specific in my installation.
Thanks for your help,
Thanks for reporting this bug. Please do give the full qemu command
line you used. I assume this was on an uptodate saucy host?
** Changed in: qemu (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
The following error occurs when starting Xen with Nvidia Optimus
graphics cards:
ERROR (SrvDaemon:349) Exception starting xend (Looped capability chain:
:01:00.0)
Traceback (most recent call last):
File /usr/lib/xen-4.3/bin/../lib/python/xen/xend/server/SrvDaemon.py,
Hi Scott,
I'm not able to repro this using the current dev branch of the CLI tools
and the latest CustomData patches. Can you take a look at the latest
CustomData patches at the pull requests below. They are mostly similar
to yours and should port easily into the version of the xplat tools and
The full command line was:
qemu-system-x86_64 --enable-kvm -m 1200 -drive
if=virtio,file=img,cache=unsafe -drive if=ide,file=Downloads/trusty-
desktop-amd64.iso,media=cdrom -vga std -boot d
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
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
Hmm.. forget it. The upgrade went fine after all. Only the changes in
etc had to be committed manually.
I mark this as Invalid, since the problem can be avoided by changing the
configuration.
** Changed in: etckeeper (Ubuntu)
Status: New = Invalid
--
You received this bug notification
How can I reproduce this? It sounds like a bad configuration somewhere,
but without further information I am not sure.
** Changed in: nova
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in
You have been subscribed to a public bug:
Hello,
This is a request to please backport this patch from the 1.4.1 agent:
https://github.com/WindowsAzure/WALinuxAgent/commit/375f1ede38fd323c2560e7e21ba99ac50bc66acd
Summary
The Ubuntu images in the Windows Azure gallery (except for 12.10) all use
Are a1/a2 on the same host? what version of nova etc?
** Changed in: nova
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1022612
Title:
private
Moving bug from private to public.
** Information type changed from Proprietary to Public
** Project changed: lansing = walinuxagent (Ubuntu)
** Changed in: walinuxagent (Ubuntu)
Assignee: (unassigned) = Ben Howard (utlemming)
** Changed in: walinuxagent (Ubuntu)
Importance: Undecided
For the record, I can't reproduce this issue here with my existing VMs.
It's possible this is a bug with virt-manager, configuring newly-created
VMs with wrong commandlines in trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: nova
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1264816
Title:
Unable to instantiate unregistered object type SecurityGroupRuleList
Folsom has been 'end of llife'-ed and isn't supported upstream.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1208880
Title:
Adding
PROBLEM STILL EXISTS ON 14.04 LTS!!!
please either fix chkrootkit or change /sbin/init - I hope in a more
security aware post snowden era this will now trigger some more action -
certainly many users will be very irritated about this.
This does not happen on other distros. Must be fixed before
** Bug watch added: Debian Bug tracker #704115
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704115
** Also affects: whois (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704115
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Bug watch added: Debian Bug tracker #699928
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699928
** Also affects: whois (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699928
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: whois (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to whois in Ubuntu.
https://bugs.launchpad.net/bugs/967311
Title:
Incorrect 6to4 handling
To manage notifications
** Changed in: whois (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to whois in Ubuntu.
https://bugs.launchpad.net/bugs/1203647
Title:
whois domain .id Not found: -V Md5.0
To manage
[Expired for mysql-5.5 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-5.5 (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.5 in Ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
42 matches
Mail list logo
