Blueprint changed by Dave Walker:
Definition Status: New = Discussion
--
MAAS next steps
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-maas-next-steps
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
Blueprint changed by Antonio Rosales:
Drafter: (none) = Ubuntu Server Team
--
Juju GUI
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-gui
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
Blueprint changed by Antonio Rosales:
Approver: (none) = Antonio Rosales
--
Juju GUI
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-gui
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
** Branch linked: lp:~julian-edwards/maas/start-node-error-bug-1069603
** Branch linked: lp:~julian-edwards/maas/1.2-start-node-error-
bug-1069603
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: maas
Status: In Progress = Fix Committed
** Changed in: maas
Status: Fix Committed = Fix Released
--
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/1069603
Hello Thiago
It is incomplete because we cannot recreate it. Hence we're waiting for
you to provide the information requested in comment #15.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: maas
Assignee: (unassigned) = John A Meinel (jameinel)
** Changed in: maas/1.2
Assignee: (unassigned) = John A Meinel (jameinel)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: maas/1.2
Assignee: (unassigned) = Nick Veitch (evilnick)
--
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/975454
Title:
complete documentation and man pages
To
** Changed in: maas/1.2
Status: In Progress = Fix Committed
--
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/1069603
Title:
Error in log when using 'Start node' button:
Hi Thomas, why the prefix
Because if I am looking at the list of bind9 bugs it isn't obvious from
the title what bind is supposed to be integrated with. :)
** Summary changed:
- integrate with bind package
+ Please integrate Samba 4 with bind9 package
--
You received this bug notification
Another daylight savings change has just happened, and once again our
Nagios monitoring system silently failed to run any checks after the
change, needing to be restarted.
Why does nobody out there care that the repositories for an LTS release
of Ubuntu STILL only offer the same buggy version of
Blueprint changed by James Page:
Drafter: koolhead17 = Ubuntu Server Team
--
Improving Openstack Documentation for Ubuntu
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-openstack-docs
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or
Blueprint changed by James Page:
Assignee: Ubuntu Server Team = koolhead17
--
Improving Openstack Documentation for Ubuntu
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-openstack-docs
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or
You have been subscribed to a public bug:
The cluster controller does not need rabbitmq: it simply connects to the
region's rabbitmq server.
** Affects: maas (Ubuntu)
Importance: Low
Status: Triaged
--
maas-cluster-controller depends on rabbitmq-server.
Public bug reported:
The cluster controller does not need rabbitmq: it simply connects to the
region's rabbitmq server.
** Affects: maas (Ubuntu)
Importance: Low
Assignee: Andres Rodriguez (andreserl)
Status: Triaged
** Affects: maas (Ubuntu Quantal)
Importance:
** Also affects: maas (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Raring)
Importance: Low
Assignee: Raphaël Badin (rvb)
Status: Triaged
** Changed in: maas (Ubuntu Quantal)
Assignee: (unassigned) = Andres Rodriguez (andreserl)
You have been subscribed to a public bug:
When upgrading from precise to quantal, the maas_workers rabbitmq user
got its password changed (in rabbitMQ) but the configuration file
/etc/maas/maas_local_celeryconfig.py was not upgraded accordingly.
** Affects: maas (Ubuntu)
Importance:
Public bug reported:
When upgrading from precise to quantal, the maas_workers rabbitmq user
got its password changed (in rabbitMQ) but the configuration file
/etc/maas/maas_local_celeryconfig.py was not upgraded accordingly.
** Affects: maas (Ubuntu)
Importance: Critical
Assignee:
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Andres Rodriguez (andreserl)
--
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/1072772
Title:
Package upgrade breaks rabbitmq
Public bug reported:
A bug in puppet, which was already fixed upstream in 2.7.11, can cause
occasional hangs in one-time mode and slow downs in general, caused by a
bug in the file
lib/puppet/util/instrumentation/listeners/process_name.rb
Upstream bugs describing the problem
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: puppet (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
Public bug reported:
I tried to report this bug using ubuntu-bug dnsmasq-base but that
process repeatably crashes :-( I've filed a separate bug report on that
issue but therefore there is no information automatically appended. The
output of lsb_release -a is:
No LSB modules are available.
** Changed in: cinder
Milestone: None = grizzly-1
--
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/1065702
Title:
After folsom upgrade, instances can no longer access existing
[Expired for nova (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nova (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
24 matches
Mail list logo