** Branch linked: lp:~rvb/maas/lp-1313550
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313550
Title:
ping does not work as a normal user on trusty tarball cloud images.
To manage notifications
** Branch linked: lp:~rvb/maas/lp-1313550
--
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/1313550
Title:
ping does not work as a normal user on trusty tarball cloud images.
To manage
** Changed in: maas/1.8
Milestone: None = 1.8.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317705
Title:
Commissioning x86_64 node never completes, sitting at grub prompt,
pserv py tbs
** Changed in: maas/1.8
Milestone: None = 1.8.1
--
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/1317705
Title:
Commissioning x86_64 node never completes, sitting at grub
** Branch linked: lp:~rvb/maas/tftp-bug-1317705
--
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/1317705
Title:
Commissioning x86_64 node never completes, sitting at grub
** Branch linked: lp:~rvb/maas/tftp-bug-1317705
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317705
Title:
Commissioning x86_64 node never completes, sitting at grub prompt,
pserv py tbs
To
= next
** Changed in: maas/trunk
Status: In Progress = Fix Committed
** Changed in: maas/trunk
Assignee: Andres Rodriguez (andreserl) = (unassigned)
** Changed in: maas/trunk
Assignee: (unassigned) = Raphaël Badin (rvb)
--
You received this bug notification because you
= next
** Changed in: maas/trunk
Status: In Progress = Fix Committed
** Changed in: maas/trunk
Assignee: Andres Rodriguez (andreserl) = (unassigned)
** Changed in: maas/trunk
Assignee: (unassigned) = Raphaël Badin (rvb)
--
You received this bug notification because you
** Changed in: maas/1.8
Assignee: (unassigned) = Raphaël Badin (rvb)
** Changed in: maas/1.8
Importance: Undecided = Critical
** Changed in: maas/1.8
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: maas/1.8
Assignee: (unassigned) = Raphaël Badin (rvb)
** Changed in: maas/1.8
Importance: Undecided = Critical
** Changed in: maas/1.8
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: juju-net
--
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/1430025
Title:
maas uninstallable on vivid
To manage notifications about this bug go to:
** Tags added: juju-net
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430025
Title:
maas uninstallable on vivid
To manage notifications about this bug go to:
Looks like this is already fixed, my bad.
** Changed in: python-django-piston (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django-piston in Ubuntu.
Looks like this is already fixed, my bad.
** Changed in: python-django-piston (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431716
Title:
ImportError: cannot
Public bug reported:
Vivid contains Django 1.7 and djorm-ext-pgarray 0.8.
djorm-ext-pgarray version 0.8 is not compatible with Django 1.7
migration module. One of the symptoms is that the dbtype of an
ArrayField is ignored (and the default dbtype 'int' is used).
In other words, when declaring
Public bug reported:
Vivid contains Django 1.7 and djorm-ext-pgarray 0.8.
djorm-ext-pgarray version 0.8 is not compatible with Django 1.7
migration module. One of the symptoms is that the dbtype of an
ArrayField is ignored (and the default dbtype 'int' is used).
In other words, when declaring
Public bug reported:
In vivid, we have Django 1.7 and piston 0.2.3.
Piston 0.2.3 breaks with Django 1.7 because the module
django.utils.simplejson has been removed from Django 1.7
(https://docs.djangoproject.com/en/1.7/internals/deprecation
/#deprecation-removed-in-1-7). Note that it has been
Public bug reported:
In vivid, we have Django 1.7 and piston 0.2.3.
Piston 0.2.3 breaks with Django 1.7 because the module
django.utils.simplejson has been removed from Django 1.7
(https://docs.djangoproject.com/en/1.7/internals/deprecation
/#deprecation-removed-in-1-7). Note that it has been
Public bug reported:
The version currently available in Vivid for djorm-ext-pgarray (0.8)
doesn't work with Django 1.7 (the version in Vivid). See bug 1431789
for details.
I'd like to get the version 1.2 of djorm-ext-pgarray
(https://github.com/niwibe/djorm-pgarray/) into Vivid.
** Affects:
Public bug reported:
The version currently available in Vivid for djorm-ext-pgarray (0.8)
doesn't work with Django 1.7 (the version in Vivid). See bug 1431789
for details.
I'd like to get the version 1.2 of djorm-ext-pgarray
(https://github.com/niwibe/djorm-pgarray/) into Vivid.
** Affects:
Can you please provide the full stacktrace (it should be in the logs in
/var/log/maas) and tell us which version you're using exactly?
** Changed in: maas (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Can you please provide the full stacktrace (it should be in the logs in
/var/log/maas) and tell us which version you're using exactly?
** Changed in: maas (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Couldn't this be bug 1424509? (Because after installing `postgresql` on
vivid, the main cluster is down, see http://paste.ubuntu.com/10579015/)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Couldn't this be bug 1424509? (Because after installing `postgresql` on
vivid, the main cluster is down, see http://paste.ubuntu.com/10579015/)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430025
@Andres, the crash you're seeing is bug 1430324.
** 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/1430025
Title:
maas
@Andres, the crash you're seeing is bug 1430324.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430025
Title:
maas uninstallable on
I get the same crash (as described on the bug) when I installing 1.7 on Vivid.
It seems the DB is down:
$ sudo service postgresql status
sudo: unable to resolve host server-516c7ee2-8cb6-4c1f-b950-6b6900d74ead
● postgresql.service - PostgreSQL RDBMS
Loaded: loaded
I get the same crash (as described on the bug) when I installing 1.7 on Vivid.
It seems the DB is down:
$ sudo service postgresql status
sudo: unable to resolve host server-516c7ee2-8cb6-4c1f-b950-6b6900d74ead
● postgresql.service - PostgreSQL RDBMS
Loaded: loaded
Looks like a packaging problem: the migrations in question are *not*
present in the package that used to be (?) in the testing PPA
(1.7.2~rc1+bzr3350-0ubuntu1~trusty2) but they *are* present in the
upstream code (1.7 revision 3350).
** Also affects: ubuntu
Importance: Undecided
Status:
** Branch linked: lp:~rvb/maas/amt_wsman-1.7
--
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/1331214
Title:
MAAS (amttool) cannot control AMT version 8
To manage notifications about
** Branch linked: lp:~rvb/maas/amt_wsman-1.7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331214
Title:
MAAS (amttool) cannot control AMT version 8
To manage notifications about this bug go to:
** Changed in: maas/1.7
Assignee: Newell Jensen (newell-jensen) = Raphaël Badin (rvb)
** Changed in: maas/1.7
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
** Changed in: maas/1.7
Assignee: Newell Jensen (newell-jensen) = Raphaël Badin (rvb)
** Changed in: maas/1.7
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
When we start transferring the kernel over, the machine on the other
side stops responding
This is indeed what seems to be causing the problem. Note that we're
seeing (a worrying number of) retries in some of the earlier (and
successful) transfers.
What kind of bridge is being used here?
When we start transferring the kernel over, the machine on the other
side stops responding
This is indeed what seems to be causing the problem. Note that we're
seeing (a worrying number of) retries in some of the earlier (and
successful) transfers.
What kind of bridge is being used here?
This is how APT work. If you want to remove the dependencies that were
automatically installed by 'maas;, you need to: `sudo apt-get autoremove
--purge`
Well, I understand your point but you'll admit that it's strange to do this:
`sudo apt-get purge maas`
And after that, to still have MAAS fully
This is how APT work. If you want to remove the dependencies that were
automatically installed by 'maas;, you need to: `sudo apt-get autoremove
--purge`
Well, I understand your point but you'll admit that it's strange to do this:
`sudo apt-get purge maas`
And after that, to still have MAAS fully
Hum, I tested again this morning (and answered yes to the two uninstall
questions, as I did before) and this time the DB got removed okay.
Maybe it's because the first time, I installed the packages differently
(with dpkg -i *.deb).
--
You received this bug notification because you are a member
Hum, I tested again this morning (and answered yes to the two uninstall
questions, as I did before) and this time the DB got removed okay.
Maybe it's because the first time, I installed the packages differently
(with dpkg -i *.deb).
--
You received this bug notification because you are a member
Public bug reported:
I just removed MAAS 1.7 from my system (apt-get purge maas maas...) and
the maasdb hasn't been removed although I answered 'yes' to the two
questions that I got from dpkg during the installation process (the last
one being something like : Do you want the MAAS' DB to be
Public bug reported:
One would expect `sudo apt-get purge maas` (or something simple like
that) to be enough to completely remove a MAAS installation from a
system. But this doesn't work. Because of the structure of the
different MAAS packages, one needs to remove a lot of packages to
finally
Public bug reported:
I just removed MAAS 1.7 from my system (apt-get purge maas maas...) and
the maasdb hasn't been removed although I answered 'yes' to the two
questions that I got from dpkg during the installation process (the last
one being something like : Do you want the MAAS' DB to be
Public bug reported:
One would expect `sudo apt-get purge maas` (or something simple like
that) to be enough to completely remove a MAAS installation from a
system. But this doesn't work. Because of the structure of the
different MAAS packages, one needs to remove a lot of packages to
finally
** Changed in: maas (Ubuntu)
Status: New = Fix Committed
** No longer affects: maas
--
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/1411177
Title:
`make package` fails (Patch
** Changed in: maas (Ubuntu)
Status: New = Fix Committed
** No longer affects: maas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411177
Title:
`make package` fails (Patch
Public bug reported:
`make package` fails with:
Applying patch 02-pserv-config.patch
patching file etc/maas/pserv.yaml
Hunk #1 succeeded at 6 with fuzz 2.
Hunk #2 FAILED at 15.
Hunk #3 succeeded at 18 (offset -20 lines).
1 out of 3 hunks FAILED -- rejects in file etc/maas/pserv.yaml
Patch
Public bug reported:
`make package` fails with:
Applying patch 02-pserv-config.patch
patching file etc/maas/pserv.yaml
Hunk #1 succeeded at 6 with fuzz 2.
Hunk #2 FAILED at 15.
Hunk #3 succeeded at 18 (offset -20 lines).
1 out of 3 hunks FAILED -- rejects in file etc/maas/pserv.yaml
Patch
** Branch linked: lp:~rvb/maas/maas-1.7-3399
--
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 manage
** Branch linked: lp:~rvb/maas/maas-1.7-3399
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1399016
Title:
MAAS failed to respond once libapache2-mod-wsgi upgrade on trusty
To manage notifications
Looks similar to bug 1377964, but for a different file.
--
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/1382266
Title:
maas-proxy fails to start on freshly installed MAAS
To manage
Out of curiosity, how did the existing setup(s) obtain these generated
hostnames in the first place? To my knowledge they were
neither exposed nor documented.
As Jeroen said, we need to understand this in order to suggest a
solution that fits CTS' needs. My guess is that they where deriving
Looks similar to bug 1377964, but for a different file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382266
Title:
maas-proxy fails to start on freshly installed MAAS
To manage notifications
Out of curiosity, how did the existing setup(s) obtain these generated
hostnames in the first place? To my knowledge they were
neither exposed nor documented.
As Jeroen said, we need to understand this in order to suggest a
solution that fits CTS' needs. My guess is that they where deriving
** Changed in: maas
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/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts:
** Changed in: maas
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
To
I can't reproduce this so far, I've upgraded from
1.7.0~beta5+bzr3198-0ubuntu1~trusty1 to a package built from trunk; I've
seen bug 1380805 (i.e. the cluster got renamed) but I didn't see a new
cluster being created.
You said on IRC the upgrade wasn't smooth… can you describe what
happened
I can't reproduce this so far, I've upgraded from
1.7.0~beta5+bzr3198-0ubuntu1~trusty1 to a package built from trunk; I've
seen bug 1380805 (i.e. the cluster got renamed) but I didn't see a new
cluster being created.
You said on IRC the upgrade wasn't smooth… can you describe what
happened
** Branch linked: lp:~rvb/maas/fix-etc-hosts-bug-1087183-2
--
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 'manage_etc_hosts:
** Branch linked: lp:~rvb/maas/fix-etc-hosts-bug-1087183-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
To
As of MAAS 1.7, maas-import-ephermerals is gone.
** Changed in: maas
Status: Triaged = 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/1271188
Title:
** Changed in: maas
Importance: High = Critical
--
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 'manage_etc_hosts: localhost'
As of MAAS 1.7, maas-import-ephermerals is gone.
** Changed in: maas
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271188
Title:
maas-import-ephermerals provides
** Changed in: maas
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087183
Title:
MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
To manage
** Changed in: python-django (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: maas
Assignee: (unassigned) = Raphaël Badin (rvb)
** Changed in: maas
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team
** Changed in: python-django (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: maas
Assignee: (unassigned) = Raphaël Badin (rvb)
** Changed in: maas
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Branch linked: lp:~rvb/maas/fix-region-admin-cli
** Changed in: python-django (Ubuntu)
Status: New = In Progress
** Changed in: python-django (Ubuntu)
Assignee: (unassigned) = Raphaël Badin (rvb)
--
You received this bug notification because you are a member of Ubuntu
Server
** Branch linked: lp:~rvb/maas/fix-region-admin-cli
** Changed in: python-django (Ubuntu)
Status: New = In Progress
** Changed in: python-django (Ubuntu)
Assignee: (unassigned) = Raphaël Badin (rvb)
--
You received this bug notification because you are a member of Ubuntu
Bugs
jsenum has no place in provisioning server, can't you extract that
part?
jsenum is *not* in provisioningserver, as I said above it's in
src/maasserver/utils/, where it should be. The problem is that it's
*using things* (well, one thing: map_enum) from provisioningserver
** Branch linked:
jsenum has no place in provisioning server, can't you extract that
part?
jsenum is *not* in provisioningserver, as I said above it's in
src/maasserver/utils/, where it should be. The problem is that it's
*using things* (well, one thing: map_enum) from provisioningserver
** Branch linked:
The utility in src/maasserver/utils/jsenums.py is used when building the
package. It uses the map_enum utility that recently from moved over to
src/provisioningserver/utils/__init__.py. The problem with that is that
is means that all the modules imported by
The logical place for map_enum really is
src/provisioningserver/utils/__init__.py since it's used by both
maasserver and pserv so I really don't want to put it somewhere else.
Since jsenum is special in the sense that it's used by the packaging,
I'd favor option 3: add a copy of map_enum (it's
The utility in src/maasserver/utils/jsenums.py is used when building the
package. It uses the map_enum utility that recently from moved over to
src/provisioningserver/utils/__init__.py. The problem with that is that
is means that all the modules imported by
The logical place for map_enum really is
src/provisioningserver/utils/__init__.py since it's used by both
maasserver and pserv so I really don't want to put it somewhere else.
Since jsenum is special in the sense that it's used by the packaging,
I'd favor option 3: add a copy of map_enum (it's
From a packaging perspective, all that we can do here is the MIR,
right?
Yes. although now we're talking about using a different package: see bug
1331214.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
From a packaging perspective, all that we can do here is the MIR,
right?
Yes. although now we're talking about using a different package: see bug
1331214.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~rvb/maas/fix-bootloader-path
--
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/1328659
Title:
import_boot_images task fails on utopic
To manage notifications about
** Branch linked: lp:~rvb/maas/fix-bootloader-path
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328659
Title:
import_boot_images task fails on utopic
To manage notifications about this bug go
Looks like this is a problem with python-django-piston's packaging:
Result of `apt-cache show python-django-piston` in trusty:
http://paste.ubuntu.com/7653328/ and in utopic:
http://paste.ubuntu.com/7653329/
Note the difference in 'Depends':
Trusty:
Depends: python (= 2.7), python ( 2.8),
Looks like this is a problem with python-django-piston's packaging:
Result of `apt-cache show python-django-piston` in trusty:
http://paste.ubuntu.com/7653328/ and in utopic:
http://paste.ubuntu.com/7653329/
Note the difference in 'Depends':
Trusty:
Depends: python (= 2.7), python ( 2.8),
** 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/1322151
Title:
ImportError: No module named pexpect setting up
** Changed in: maas (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322151
Title:
ImportError: No module named pexpect setting up maas-dns
To
mipf has been rewritten in Python.
** Changed in: maas
Status: Triaged = 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/1182459
Title:
clean up root.tar.gz and fast
A new dependency on python-pexpect was introduced in revision 2353.
python-pexpect is in main so fixing this is as simple as adding a
dependency in the packaging.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Branch linked: lp:~rvb/maas/add-pexpect
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Raphaël Badin (rvb)
** Changed in: maas (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
mipf has been rewritten in Python.
** Changed in: maas
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182459
Title:
clean up root.tar.gz and fast path installer
A new dependency on python-pexpect was introduced in revision 2353.
python-pexpect is in main so fixing this is as simple as adding a
dependency in the packaging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~rvb/maas/add-pexpect
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Raphaël Badin (rvb)
** Changed in: maas (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I can see that libvirt might be installed on a different machine though, so
perhaps we want virsh available but not libvirtd
installed and configured.
Raphaël, does this sound reasonable and is this what you need? If so, I guess
we'll need to split libvirt-bin in order to make
any
I can see that libvirt might be installed on a different machine though, so
perhaps we want virsh available but not libvirtd
installed and configured.
Raphaël, does this sound reasonable and is this what you need? If so, I guess
we'll need to split libvirt-bin in order to make
any
** Tags removed: maas-cli
** Tags added: cli
--
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/1319600
Title:
maas-cli stack trace if .maascli.db unreadable
To manage notifications
Public bug reported:
In order to manage a virsh node, MAAS needs the libvirt-bin package
(which contains `virsh`). libvirt-bin is only a suggested dependency so
the virsh power type doesn't work out of the box.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Tags:
** Tags removed: maas-cli
** Tags added: cli
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319600
Title:
maas-cli stack trace if .maascli.db unreadable
To manage notifications about this bug go
Public bug reported:
In order to manage a virsh node, MAAS needs the libvirt-bin package
(which contains `virsh`). libvirt-bin is only a suggested dependency so
the virsh power type doesn't work out of the box.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Tags:
** 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/1086162
Title:
IPMI based power management default to IPMI 1.5 based
** Changed in: maas
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1086162
Title:
IPMI based power management default to IPMI 1.5 based authentication
To
** Description changed:
- This seems to be a regression introduced in the latest security update
- which is causing the error
+ [Test case]
- AttributeError: 'functools.partial' object has no attribute
- '__module__'
+ Without the fix:
+ 1. Install MAAS
+ 2. Access the MAAS home page
** Description changed:
- This seems to be a regression introduced in the latest security update
- which is causing the error
+ [Test case]
- AttributeError: 'functools.partial' object has no attribute
- '__module__'
+ Without the fix:
+ 1. Install MAAS
+ 2. Access the MAAS home page
** Changed in: maas/1.5
Assignee: (unassigned) = Raphaël Badin (rvb)
** Changed in: maas/1.5
Importance: Undecided = Critical
** Changed in: maas/1.5
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: maas/1.5
Assignee: (unassigned) = Raphaël Badin (rvb)
** Changed in: maas/1.5
Importance: Undecided = Critical
** Changed in: maas/1.5
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
All this fix in the merge proposal will do is delay the problem until there
are 2 images named 'release' with different version
numbers on them.
The idea is to buy time to SRU a fix to let a user select which image to
use when there is a choice.
--
You received this bug notification
1 - 100 of 469 matches
Mail list logo
