** Summary changed:
- /MAAS/nodes page needs sorting abilities
+ Nodes listing does not support sorting
** Changed in: maas (Ubuntu)
Status: New => Invalid
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => High
** Tags added: ui
--
You r
Invalidating trunk task since I think this is just a packaging problem.
Feel free to re-open it if discovered otherwise.
** Changed in: maas
Status: New => Invalid
--
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: New => Triaged
** Changed in: maas
Importance: Undecided => High
** Tags added: ui
--
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/994781
Title:
I thought of something you can try - if you change the cobbler settings
to not manage dhcp and set your external dhcp up manually, it might
work. Please let me know.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https
I'm sorry this is troublesome for you. I don't think we ever tested it
with having cobbler manage DHCP or dnsmasq, we just expected people to
set next-server on the existing DHCP.
For timeouts, there's a setting called PSERV_TIMEOUT which is currently
set to 7, try changing that and let me know.
Packaging bug, so re-targeting.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.
*** This bug is a duplicate of bug 972829 ***
https://bugs.launchpad.net/bugs/972829
** This bug has been marked a duplicate of bug 972829
maas-server setting requires port even when using http default
--
You received this bug notification because you are a member of Ubuntu
Server Team, w
Public bug reported:
It has /usr/sbin/maas instead of /usr/bin/maas
** 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/b
** Changed in: maas
Assignee: (unassigned) => Launchpad Red Squad (redsquad)
** Changed in: maas
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/975473
Title
On Saturday 09 Jun 2012 04:31:51 you wrote:
> Is the functionality of the shell documented anywhere? This would be
> VERY useful to know. Given the gui doesn't always work the way it
> should, I could see this as really good and important information.
It's not documented, it's intended as a deve
init: cloud-init-nonet main process (###) killed by TERM signal
is expected. Please see bug 1015223
Please also read all the FAQs and let me know if any of the suggestions help
(there are things mentioned that are not in the bug here).
https://answers.launchpad.net/maas/+faqs
--
You received t
Bootstrapping is not instant, you need to wait for the master node to
install before status works.
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad
Please see the first two questions on
https://answers.launchpad.net/maas/+faqs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1015207
Title:
juju setup fails, ERROR Invalid SSH key - 1
That looks like a connection refused to zookeeper, nothing to do with
maas. I suspect your zk node hasn't come up properly, which might be
related to bug 992075
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bu
The ZK node is the first one to be booted by Juju when you run "juju
bootstrap". Juju installs ZK on it.
Since ZK is not there, you have a problem at that stage. Since you
managed to log in, can you examine the cloud-init logs please? If
there's nothing sensitive in there perhaps attach to the
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** 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/102
On Wednesday 27 June 2012 15:45:17 you wrote:
> Curious. I was able to get one of the servers to actually function
> correctly as the ZK node -- not sure why that one is different since it
> was built just like the other two nodes. Anyway, logs are attached for
> all three as well as the cloud-init
> I think the Problem is a bug because there is no ubuntu User on my
installation:
This is because it didn't finish commissioning. You need to examine the
logs as above to find out where the problem is.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** 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/1021382
Title:
The COMMISSIONING_SCRIPT setting uses a relative path.
T
Adding the above instructions to HACKING.txt is perfectly fine for now.
** Changed in: maas
Importance: Low => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1026857
Title:
I
On Friday 20 Jul 2012 10:50:23 you wrote:
> fwiw, I'm with Gavin on this one, that's a *minor* problem with the
> *dev* environment so that definitely seems like "low priority" to me.
Guys, please look at the description of the priorities.
--
You received this bug notification because you are a
On Friday 20 Jul 2012 10:38:34 you wrote:
> We could add a debconf option which writes another entry to
> /etc/default/bind9 that the init script then checks. But this change
> should probably best go to Debian in the first instance, since it would
> equally apply to them.
>
> How important for th
Can you explain why is this needed please? (so that I can set priority
appropriately)
** Summary changed:
- need way to get system based on mac address
+ Unable to look up a node based on mac address
** Changed in: maas
Status: Triaged => Incomplete
--
You received this bug notificatio
To clarify, why would someone "very likely would want to query by the
mac address". What's the use case?
Thanks.
--
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/1027154
Title:
Unable
Great, thanks guys.
--
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/1027154
Title:
Unable to look up a node based on mac address
To manage notifications about this bug go to:
https://b
** Branch linked: lp:~julian-edwards/maas/bind-hacking
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1026857
Title:
Installing bind9 as per HACKING.txt leaves a running bind daemon
This is indeed one of the many reasons why Cobbler is getting removed.
--
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/1028068
Title:
Enlistment failure leaves node in cobbler, not in M
** Changed in: maas
Assignee: (unassigned) => Julian Edwards (julian-edwards)
** Changed in: maas
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchp
** Summary changed:
- DNS is not enabled.
+ Maas-hosted DNS is not enabled.
--
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/1030860
Title:
Maas-hosted DNS is not enabled.
To manage no
Public bug reported:
curl \
--data
"op=new${mac}&hostname=${hostname}&architecture=${arch}&after_commissioning_action=0"
\
"${serverurl}"/MAAS/api/1.0/nodes/
Currently serverurl is actually a just host name. MAAS should pass the
full string to the enlistment URL
Fantastic thanks Andres.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/1034228
Title:
maas-enlist script hard codes the path to the maas server
To manage notifications about t
This is not yet fixed in MAAS, the preseed template "enlist_userdata"
needs changing.
** Changed in: maas
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas-enlist in Ubuntu.
https://bugs.launch
** Branch linked: lp:~julian-edwards/maas/enlistment-preseed-fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/1034228
Title:
maas-enlist script hard codes the path to the
Public bug reported:
The current packaged one (0.1~bzr31-0ubuntu3) always returns an access
violation when a client connects. There is a fix for this in the maas
trunk.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you a
** 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/994781
Title:
removing a node when it has failed commissioning is not po
** Changed in: maas
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas-provision in Ubuntu.
https://bugs.launchpad.net/bugs/975473
Title:
eliminate cobbler code copy
To manage notificatio
** Changed in: maas
Status: Triaged => Fix Released
** Changed in: maas
Assignee: (unassigned) => Julian Edwards (julian-edwards)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas-enlist in Ubuntu.
This is fixed in trunk with the removal of Cobbler
** Changed in: maas
Status: Triaged => 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/989355
Title:
Unable to cr
** Changed in: maas
Assignee: Andres Rodriguez (andreserl) => Julian Edwards (julian-edwards)
** Changed in: maas
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
I found the problem, the enlist_userdata template is missing from
/usr/share/maas/preseeds/
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas
Status: Incomplete => Invalid
** Branch linked: lp:~andreserl/maas/maas_missing_preseed_setuppy
** Ch
** Changed in: maas
Status: In Progress => Fix Released
** Changed in: maas (Ubuntu)
Status: New => Invalid
--
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/1042864
Title:
Andres said he'd make the directory writable by the package.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
ARGH. The umask is messing us around again, it's the same problem for maas-
import-ephemerals. The reason it changes on an existing file is because it
gets renamed from a temp file (for atomic write purposes).
Do you know where the umask is getting set for the maas user?
--
You received this
On Wednesday 29 August 2012 14:43:31 you wrote:
> Also not that on maas-dns install, I had to fix those permissions, but
> they keep being changed:
>
>
> # fix permissions
> if [ -f /etc/bind/maas/named.conf.maas ]; then
> chmod 644 /etc/bind/maas/named.conf.maas
>
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1028501
Title:
cloud-init s
Packaging is broken here since it installs maas-dhcp when installing
maas. maas-dhcp should be optional.
** 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 i
** Description changed:
- When packaging installs maas-dhcp it will run "maas
- generate_dhcp_config" which also sets up the master nodegroup. This
- will also cause a task to run that generates the dhcpd.conf if the
- enable_dhcp flag is set.
+ When packaging installs maas-dhcp it will run "maas
** Changed in: maas
Assignee: (unassigned) => Julian Edwards (julian-edwards)
** Changed in: maas
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchp
** Branch linked: lp:~julian-
edwards/maas/enable_dhcp_when_setting_up_params
--
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/1044229
Title:
DHCP config doesn't get written unle
** Changed in: maas
Status: In Progress => 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/1044229
Title:
DHCP config doesn't get written unless an inhuman combinati
On Tuesday 04 September 2012 15:48:29 you wrote:
> The installation of maas-dhcp is optional. It is a recommends. However,
> maas installs its recommends by default. maas-dhcp should ask whether we
> want to enable the DHCP server. If so, it will do the configuration.
If someone says "no" initiall
Agreed, and possibly a bug in dnsmasq? Which is not really going to get
fixed in a hurry since the latest version of maas is not using dnsmasq
at all.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchp
To clarify - maas on its own cannot write the dhcpd.conf because it
doesn't have all the data required, only maas-dhcp does.
** 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 m
** 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/1055935
Title:
dhcpd.conf is not updated after package install
To manage no
Public bug reported:
sudoers in the packaging currently looks like
maas ALL= NOPASSWD: /usr/sbin/service isc-dhcp-server restart
maas ALL= NOPASSWD: /usr/sbin/maas-provision
The first line should be:
maas ALL= NOPASSWD: /usr/sbin/service maas-dhcp-server restart
** Affects: maas (Ubuntu)
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: Confirmed => Invalid
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Critical
** Changed in: maas
Assignee: (unassigned) => Jeroen
This is caused because the interfaces file is not written out.
--
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/1055935
Title:
dhcpd.conf is not updated after package install
To manage
** Changed in: maas (Ubuntu)
Status: New => In Progress
--
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/1055951
Title:
maas-dhcp has no sudoers permission to start maas-dhcp-serv
** Branch linked: lp:~jtv/maas/pass-dhcp-interfaces
** Changed in: maas
Status: Triaged => 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/1055935
Title:
dhcpd.conf
Public bug reported:
The maas-dhcp server doesn't start up if there's an existing daemon
running, which is almost certainly going to be the case from a default
installation of the isc-dhcp-server package.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received
Matsubara, that's odd because it worked for me. :/
Scott, ok, thanks.
--
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/1055935
Title:
dhcpd.conf is not updated after package install
To
Ok now I've re-created this on a new canonistack instance. Very odd, I am
investigating.
--
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/1055935
Title:
dhcpd.conf is not updated after
This is the queue name transition problem, I'm linking the branch that
fixes it.
** Changed in: maas
Status: Fix Released => Triaged
** Branch linked: lp:~rvb/maas/packaging.user-master-queue
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is s
** Changed in: maas
Status: Triaged => 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/1055935
Title:
dhcpd.conf is not updated after package install
To manage not
** Changed in: maas (Ubuntu)
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/1055951
Title:
maas-dhcp has no sudoers permission to start maas
I suspect there's a "expect fork" missing in the upstart conf
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Critical
--
You received this bug notification because you are a mem
** Changed in: maas
Status: Fix Committed => Fix Released
** Changed in: maas
Assignee: Jeroen T. Vermeulen (jtv) => Julian Edwards (julian-edwards)
--
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: 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/1050523
Title:
maas kernel cmdline must include iscsi_initiator
To mana
Public bug reported:
When maas-dhcp is installed it sets up the config necessary for maas to
start up its own DHCP server. However the existing one is still running
and conflicts with it.
** Affects: maas
Importance: Critical
Status: Triaged
** Affects: maas (Ubuntu)
Importan
Public bug reported:
root@maas:/etc/init# dpkg -S /etc/init/maas-celery.conf
maas: /etc/init/maas-celery.conf
This causes an extra celeryd to get run which interferes which things.
** Affects: maas
Importance: Critical
Status: Triaged
** Affects: maas (Ubuntu)
Importance: Und
** Branch linked: lp:~julian-edwards/maas/stop-dhcp-bug-1059459
--
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/1059459
Title:
Existing DHCP server not stopped
To manage notifications
** Changed in: maas (Ubuntu)
Status: New => In Progress
** Changed in: maas (Ubuntu)
Assignee: (unassigned) => Julian Edwards (julian-edwards)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Branch linked: lp:~julian-edwards/maas/broken-dns-install-bug-1060549
--
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/1060549
Title:
maas-dns fails to install because maas user
** Changed in: maas (Ubuntu)
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/1060549
Title:
maas-dns fails to install because maas user hasn'
Fair enough. How else could we do this?
** Changed in: maas
Assignee: (unassigned) => Julian Edwards (julian-edwards)
** Changed in: maas
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
On Wednesday 03 October 2012 02:47:05 you wrote:
> Update for the record. As we have since found out, it's much worse than
> just needing an "expect fork." Somewhere along the line, before it gets
> around to running the start-cluster-controller code proper, maas-
> provision does a whole bunch o
I think this is a missing #DEBHELPER# in the cluster's prerm. I'll try
and fix it.
** Changed in: maas (Ubuntu)
Status: New => In Progress
** Changed in: maas (Ubuntu)
Assignee: (unassigned) => Julian Edwards (julian-edwards)
** Branch linked: lp:~julian-edwards/maa
This is fine. The user cannot be removed until all packages that try to
install it are removed. Double check that the user is really gone when
the purge finishes.
** Changed in: maas (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
http://paste.ubuntu.com/1261109/ shows the cloud-init log.
http://paste.ubuntu.com/1261129/ shows the output when running "cloud-init
--debug modules --mode=final" manually. In this case it finishes and
successfully commissions.
Running:
sudo start cloud-final
shows:
start
dmesg: http://paste.ubuntu.com/1261143/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1061977
Title:
Machine fails to commission when console=ttyS0 is present on kernel
opts
Tarball of all of /var/log
** Attachment added: "varlog.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1061977/+attachment/3374165/+files/varlog.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init i
backdoor@10-0-0-100:~$ echo HI MOM | sudo tee /dev/console
sudo: unable to resolve host 10-0-0-100
HI MOM
tee: /dev/console: Input/output error
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad
** Changed in: maas
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/1059556
Title:
/etc/init/maas-celery.conf not removed on
** 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 cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manag
** Changed in: maas
Status: Fix Committed => In Progress
--
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/1059556
Title:
/etc/init/maas-celery.conf not removed on upgrade
To mana
** Changed in: maas (Ubuntu)
Status: New => Fix Committed
** Changed in: maas
Status: In Progress => 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/1059556
Ti
** 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/1059453
Title:
The celery cluster worker is not properly stopped
To man
** 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/975462
Title:
add ability to use over https
To manage notifications abo
** Changed in: maas
Status: In Progress => Fix Released
--
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/1062031
Title:
pserv is oopsing: "exceptions.TypeError: not all
On Wednesday 10 October 2012 19:25:24 you wrote:
> On 10 Oct 2012 20:15, "Andres Rodriguez" wrote:
> > I believe we should be able to add an attribute to the Node model. This
> > way, we can define a global config that will apply to all nodes. If a
> > particular node needs to change the attribute
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New => Confirmed
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: maas
Status: Fix Committed => Fix Released
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Fixing in packaging for now, it's a one-liner.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas (Ubuntu)
Status: New => In Progress
** Changed in: maas (Ubuntu)
Assignee: (unassigned) => Julian Edwards (julian-edwards)
*
** 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/1066958
Title:
DNS config is invalid after a node gets enlisted.
To man
** 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/1066938
Title:
maas-dns changes default bind rndc key and breaks initscr
** 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/1064922
Title:
Enlistment fails with 12.04 ephemeral images
To manage n
** 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/1064672
Title:
Node listing page becomes unusable with increased number
** 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/1064638
Title:
Commissioning is failing to set node memory attribute
To
** 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/1067261
Title:
Web reference in UI points to wrong place
To manage noti
Andres says it was a missing "=". It used to say:
--queues celery,master
and he's fixing it to say:
--queues=celery,master
--
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/1067929
Title
1 - 100 of 632 matches
Mail list logo
