[Bug 1256957] [NEW] AttributeError: 'WSGIRequest' object has no attribute 'raw_post_data' (Django 1.6 incompatibility)
Public bug reported: See details on the upstream issue: https://bitbucket.org/jespern/django- piston/issue/235/attributeerror-wsgirequest-object-has-no ** Affects: python-django-piston (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1256957 Title: AttributeError: 'WSGIRequest' object has no attribute 'raw_post_data' (Django 1.6 incompatibility) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-django-piston/+bug/1256957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065775] Re: dbus and avahi-daemon not started after package install
*** This bug is a duplicate of bug 1221059 *** https://bugs.launchpad.net/bugs/1221059 ** This bug has been marked a duplicate of bug 1221059 MAAS wsgi processes are stuck waiting for a lock which is never released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065775 Title: dbus and avahi-daemon not started after package install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1065775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311151] Re: MAAS imports Trusty's 'rc' images by default.
> 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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311151 Title: MAAS imports Trusty's 'rc' images by default. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1311151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309761] Re: MAAS installing older 14.04 image instead of newer one
*** This bug is a duplicate of bug 1309593 *** https://bugs.launchpad.net/bugs/1309593 ** This bug is no longer a duplicate of bug 1311151 MAAS imports Trusty's 'rc' images by default. ** This bug has been marked a duplicate of bug 1309593 No way to specify which image should be used when similar images with different labels are available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309761 Title: MAAS installing older 14.04 image instead of newer one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1309761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311151] Re: MAAS imports Trusty's 'rc' images by default.
** 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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311151 Title: MAAS imports Trusty's 'rc' images by default. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1311151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310076] Re: lost connectivity to a node when using fastpath-installer with precise+hwe-s
** Changed in: maas Status: New => Triaged ** Changed in: maas Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310076 Title: lost connectivity to a node when using fastpath-installer with precise+hwe-s To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1310076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
@Paul: the problem you're having is that your nodes can't access the
outside world. They are thus unable to fetch the packages needed for
commissioning (see http://paste.ubuntu.com/7195406/).
Unless you changed the http_proxy config option (on the settings page —
or you can configure it using the CLI/API), your nodes are using the
region's proxy to download packages. Have a look at the proxy's log to
check if you can see something suspicious.
Another common problem is when MAAS' DNS server (BIND server installed
on the region) is unable to resolve names such as 'ubuntu.com'. If this
is the problem then the region's /var/log/syslog file will contain
errors like 'error (network unreachable) resolving …'. To solve this:
if you're using Trusty's package, just configure the 'upstream_dns'
option ('settings' page, at the bottom — or using the API/CLI) with your
upstream DNS server address. If you're using another version, you have
to do the config manually: include something like
http://paste.ubuntu.com/7195395/ in /etc/bind/named.conf.options and
restart the maas-dns service.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237364
Title:
Commissioning with a Saucy image sets node status to "Failed tests"
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319600] Re: maas-cli stack trace if .maascli.db unreadable
** 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 to: https://bugs.launchpad.net/maas/+bug/1319600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319717] [NEW] virsh support requires an extra package to be installed
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: power virsh ** Tags added: power virsh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319717 Title: virsh support requires an extra package to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1319717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319717] Re: virsh support requires an extra package to be installed
> 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 progress here. Yes, this sounds like the proper way to fix this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319717 Title: virsh support requires an extra package to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1319717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1182459] Re: clean up root.tar.gz and fast path installer files (mipf rewrite in Python)
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 files (mipf rewrite in Python) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1182459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322151] Re: ImportError: No module named pexpect setting up maas-dns
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. https://bugs.launchpad.net/bugs/1322151 Title: ImportError: No module named pexpect setting up maas-dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1322151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322151] Re: ImportError: No module named pexpect setting up maas-dns
** 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 to Ubuntu. https://bugs.launchpad.net/bugs/1322151 Title: ImportError: No module named pexpect setting up maas-dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1322151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322151] Re: ImportError: No module named pexpect setting up maas-dns
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1322151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948404] Re: unity-2d-shell 5.6.0-0ubuntu1 crashes with symbol lookup error: /usr/lib/libunity-2d-private.so.0: undefined symbol: _ZN5unity4dash16FilesystemLensesC1ERKSs
I'm seeing this too. Unity shell is not there when I log in and launching 'unity-2d-shell' manually triggers the error: unity-2d-shell: symbol lookup error: /usr/lib/libunity-2d-private.so.0: undefined symbol: _ZN5unity4dash16FilesystemLensesC1ERKSs I can't use unity 3d because of the awful performance I get from my GeForce 8400M GS. Now it's difficult to use unity-2d. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948404 Title: unity-2d-shell 5.6.0-0ubuntu1 crashes with symbol lookup error: /usr/lib/libunity-2d-private.so.0: undefined symbol: _ZN5unity4dash16FilesystemLensesC1ERKSs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/948404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948404] Re: unity-2d-shell 5.6.0-0ubuntu1 crashes with symbol lookup error: /usr/lib/libunity-2d-private.so.0: undefined symbol: _ZN5unity4dash16FilesystemLensesC1ERKSs
$ dpkg -l | grep -i libunity-core rc libunity-core-4.0-4 4.28.0-0ubuntu2 Core library for the Unity interface. ii libunity-core-5.0-5 5.6.0-0ubuntu1 Core library for the Unity interface. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948404 Title: unity-2d-shell 5.6.0-0ubuntu1 crashes with symbol lookup error: /usr/lib/libunity-2d-private.so.0: undefined symbol: _ZN5unity4dash16FilesystemLensesC1ERKSs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/948404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 955451] Re: Default Maas name is Www-data's Maas
I don't really like how "My Maas" sounds but maybe that's just me. This is a really easy fix once we agree on what the default should be: "$hostname Maas" … "$Hostname Maas"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955451 Title: Default Maas name is Www-data's Maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/955451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282653] [NEW] Upgrade to Trusty failed.
Public bug reported: Upgrade to Trusty (from Saucy) failed with "Could not calculate the upgrade". ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205.4 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CrashDB: ubuntu Date: Thu Feb 20 16:56:57 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-07-23 (577 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to saucy on 2014-02-20 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282653 Title: Upgrade to Trusty failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1282653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411177] [NEW] `make package` fails (Patch 02-pserv-config.patch does not apply)
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 02-pserv-config.patch does not apply (enforce with -f) It seems revision 339 from the packaging branch caused this. ** Affects: maas Importance: Critical Status: Triaged ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Also affects: maas (Ubuntu) Importance: Undecided Status: New -- 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 02-pserv-config.patch does not apply) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1411177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331214] Re: MAAS (amttool) cannot control AMT version > 8
** 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: https://bugs.launchpad.net/maas/+bug/1331214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331214] Re: MAAS (amttool) cannot control AMT version > 8
** 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/bugs/1331214 Title: MAAS (amttool) cannot control AMT version > 8 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1331214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1428042] Re: Migration hang with defunct process when upgrading from 1.7.1 to 1.7.2rc1
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: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1428042 Title: Migration hang with defunct process when upgrading from 1.7.1 to 1.7.2rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1428042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430025] Re: maas uninstallable on vivid
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 (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled) Active: active (exited) since Tue 2015-03-10 13:03:49 UTC; 13min ago Process: 16884 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 16884 (code=exited, status=0/SUCCESS) Mar 10 13:03:49 server-516c7ee2-8cb6-4c1f-b950-6b6900d74ead systemd[1]: Starting PostgreSQL RDBMS... Mar 10 13:03:49 server-516c7ee2-8cb6-4c1f-b950-6b6900d74ead systemd[1]: Started PostgreSQL RDBMS. $ ps aux | grep postgr -> nothing Did something in postgresql's packaging change drastically with the vivid release? My guess is that this is all related to the switch to systemd. -- 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: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1430025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430025] Re: maas uninstallable on vivid
@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 vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1430025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430025] Re: maas uninstallable on vivid
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 Title: maas uninstallable on vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1430025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431279] Re: MAAS python scripts do not show the line numbers and the script name when errors are encountered
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 to Ubuntu. https://bugs.launchpad.net/bugs/1431279 Title: MAAS python scripts do not show the line numbers and the script name when errors are encountered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1431279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431716] [NEW] "ImportError: cannot import name simplejson" when using piston 0.2.3 with Django 1.7
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 deprecated since Django 1.5 (https://docs.djangoproject.com/en/1.7/releases/1.5/#system- version-of-simplejson-no-longer-used). This patch: https://bitbucket.org/ckarrie/django- piston/commits/024ede7de7179cbe738322f6003c2d8d97d8e2a4 from a fork of piston (AFAIK the "official" upstream piston is unmaintained) fixes the problem. ** Affects: python-django-piston (Ubuntu) Importance: Undecided Status: New -- 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 import name simplejson" when using piston 0.2.3 with Django 1.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-django-piston/+bug/1431716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431789] [NEW] ArrayField created with the wrong dbtype with Django 1.7
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 a field like this: djorm_pgarray.fields.ArrayField(default=None, null=True, blank=True, dbtype="text") One ends up with this in the DB: defined as integer[] instead of text[]. (Note that the project has been renamed to djorm-pgarray in version 1.0.) Support for Django 1.7 was added in version 1.0 (see https://github.com/niwibe/djorm-pgarray/blob/master/CHANGES.md). I can confirm that the fields are created correctly with djorm-pgarray 1.0 and Django 1.7. ** Affects: djorm-ext-pgarray (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431789 Title: ArrayField created with the wrong dbtype with Django 1.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djorm-ext-pgarray/+bug/1431789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431934] [NEW] FFE: Update djorm-ext-pgarray package to version 1.2 in vivid
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: djorm-ext-pgarray (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431934 Title: FFE: Update djorm-ext-pgarray package to version 1.2 in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djorm-ext-pgarray/+bug/1431934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431716] Re: "ImportError: cannot import name simplejson" when using piston 0.2.3 with Django 1.7
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 import name simplejson" when using piston 0.2.3 with Django 1.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-django-piston/+bug/1431716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240652] Re: maas-import-ephemerals crashes with "unexpected checksum 'sha256'" when using a proxy
@smoser, I just tested your most recent fix to simplestreams (revision 319) and it seems to fix the problem. I had a successful run in our lab. Until a package with the fix is published, this can be fixed manually: $ sudo su $ cd /usr/share/pyshared && wget http://bazaar.launchpad.net/~smoser/simplestreams/trunk/diff/319 && patch -p0 < 319 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240652 Title: maas-import-ephemerals crashes with "unexpected checksum 'sha256'" when using a proxy To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181334] Re: i386 required to install amd64
I think we should raise the priority on this bug and possibly fix it for 14.04. I expect a lot of users will want to use amd64 over i386. Being able to not download all the i386 images cuts a third of what maas- import-pxe-files downloads. This mean a significant gain in terms of space and speed of execution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181334 Title: i386 required to install amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240652] Re: maas-import-ephemerals crashes with "unexpected checksum 'sha256'" when using a proxy
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240652 Title: maas-import-ephemerals crashes with "unexpected checksum 'sha256'" when using a proxy To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240652] Re: maas-import-ephemerals crashes with "unexpected checksum 'sha256'" when using a proxy
I've tested this on canonistack and the fix worked: http://paste.ubuntu.com/6278444/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240652 Title: maas-import-ephemerals crashes with "unexpected checksum 'sha256'" when using a proxy To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229275] Re: juju destroy-environment also destroys nodes that are not controlled by juju
One solution to fix this problem would be this: - when the env is bootstrapped: create a tag named after the environment UUID - each time juju takes control of a node: associate that tag with the node - when juju fetches the list of instances it controls, only return the nodes associated with that tag ** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Importance: Undecided => Critical ** Changed in: juju-core Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1229275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229275] Re: juju destroy-environment also destroys nodes that are not controlled by juju
** Also affects: juju Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208497] Re: netboot flag defaults to 'true' on upgrade, even for allocated nodes
** Branch linked: lp:~rvb/maas/netboot-allocated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208497 Title: netboot flag defaults to 'true' on upgrade, even for allocated nodes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1208497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208497] Re: netboot flag defaults to 'true' on upgrade, even for allocated nodes
** Changed in: maas Assignee: (unassigned) => Raphaël Badin (rvb) ** Changed in: maas Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208497 Title: netboot flag defaults to 'true' on upgrade, even for allocated nodes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1208497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208497] Re: netboot flag defaults to 'true' on upgrade, even for allocated nodes
** Branch linked: lp:~rvb/maas/netboot-allocated-fix-mig-10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208497 Title: netboot flag defaults to 'true' on upgrade, even for allocated nodes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1208497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
@tribaal: I think what you're seeing here is bug 1181334 (note the fact that the error you see mentions i386). Can you try changing /etc/maas/import_pxe_files to set ARCHES to "i386/generic amd64/generic", re-run the import script and try again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208497] Re: netboot flag defaults to 'true' on upgrade, even for allocated nodes
** Also affects: maas/1.2 Importance: Undecided Status: New ** Also affects: maas/1.3 Importance: Undecided Status: New ** Also affects: maas/trunk Importance: Critical Assignee: Raphaël Badin (rvb) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208497 Title: netboot flag defaults to 'true' on upgrade, even for allocated nodes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1208497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208497] Re: netboot flag defaults to 'true' on upgrade, even for allocated nodes
** Branch linked: lp:~rvb/maas/netboot-allocated-fix-mig-10-1.3 ** Branch linked: lp:~rvb/maas/netboot-allocated-fix-mig-10-1.2 ** Changed in: maas/1.3 Assignee: (unassigned) => Raphaël Badin (rvb) ** Changed in: maas/1.2 Assignee: (unassigned) => Raphaël Badin (rvb) ** Changed in: maas/1.2 Status: New => In Progress ** Changed in: maas/1.3 Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208497 Title: netboot flag defaults to 'true' on upgrade, even for allocated nodes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1208497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208497] Re: netboot flag defaults to 'true' on upgrade, even for allocated nodes
** Changed in: maas/1.2 Status: In Progress => Fix Committed ** Changed in: maas/1.3 Status: In Progress => Fix Committed ** Changed in: maas/trunk Status: In Progress => Fix Committed ** Changed in: maas/1.3 Importance: Undecided => Critical ** Changed in: maas/1.2 Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208497 Title: netboot flag defaults to 'true' on upgrade, even for allocated nodes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1208497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228360] Re: No clock in menu bar and can't edit Clock settings
I experienced the same thing. "killall unity-panel-service" fixed the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228360 Title: No clock in menu bar and can't edit Clock settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1228360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229275] Re: juju destroy-environment also destroys nodes that are not controlled by juju
This might be a bug in the maas provider of juju-core… it definitely needs investigation… -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1229275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430025] Re: maas uninstallable on vivid
** 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: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1430025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317705] Re: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1317705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317705] Re: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs
** Branch linked: lp:~rvb/maas/tftp-bug-1317705-1.8 ** Also affects: maas/1.8 Importance: Undecided Status: New ** Also affects: maas/trunk Importance: Critical Assignee: Andres Rodriguez (andreserl) Status: In Progress ** Changed in: maas/trunk Milestone: 1.7.3 => 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 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 manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1317705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317705] Re: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs
** 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 to Ubuntu. https://bugs.launchpad.net/bugs/1317705 Title: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1317705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317705] Re: 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 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 manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1317705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
** 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 about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773987] Re: Timezone is not set correctly for some locations
I'm still seeing that issue on precise: this is what I get when I add "New York (United States)": http://people.canonical.com/~rvb/indicator_time.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773987 Title: Timezone is not set correctly for some locations To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/773987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931967] Re: Corrupted graphics after the login until the unity launcher appears
FWIW I'm also getting the corrupted graphic using the *nouveau* video driver (GeForce 8400M GS) on precise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/931967 Title: Corrupted graphics after the login until the unity launcher appears To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/931967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773987] Re: Timezone is not set correctly for some locations
Still seeing this issue today: dpkg -s indicator-datetime | grep Version → Version: 0.3.90-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773987 Title: Timezone is not set correctly for some locations To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/773987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087183] Re: MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1087183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416027] [NEW] Removing MAAS from a system is painful
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 get rid of MAAS (maas-cluster-controller maas-region-controller python-django-maas, etc.) ** Affects: maas (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416027 Title: Removing MAAS from a system is painful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1416027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416026] [NEW] Uninstalling MAAS doesn't remove the postgresql DB
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 removed") ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416026 Title: Uninstalling MAAS doesn't remove the postgresql DB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1416026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416027] Re: Removing MAAS from a system is painful
> 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 installed! I mean, it's okay when a package leaves some libraries installed behind once removed (and I understand it's how API works) but in MAAS' case the *entire service* (region, cluster) is still installed and running after you uninstall the `maas` package. It's really counter-intuitive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416027 Title: Removing MAAS from a system is painful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1416027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416026] Re: Uninstalling MAAS doesn't remove the postgresql DB
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416026 Title: Uninstalling MAAS doesn't remove the postgresql DB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1416026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246236] Re: pxe boot from maas fails due to time out
> 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? (virbr0 -the bridge created by virsh-, br0, ?). Can you please paste the characteristics of the bridge (by running something like "cd /sys/class/net/virbr0/bridge; for f in `ls *`; do echo -n "$f "; cat $f; done). As described on https://bugs.launchpad.net/maas/+bug/116, the default timeout behavior might be the problem here. Can you try changing the RemoteOriginReadSession class in /usr/share/pyshared/tftp/bootstrap.py: change the timeout = (1, 1, 1, 1, 1, 1) to timeout = (1, 3, 7). and then restart the TFTP server? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246236 Title: pxe boot from maas fails due to time out To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1246236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1411177] Re: `make package` fails (Patch 02-pserv-config.patch does not apply)
** 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 02-pserv-config.patch does not apply) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1411177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399016] Re: MAAS failed to respond once libapache2-mod-wsgi upgrade on trusty
** 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 about this bug go to: https://bugs.launchpad.net/maas/+bug/1399016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190986] Re: ERROR Nonce already used
If you're using a earlier version of MAAS that doesn't contain the fix yet, it's easy to reproduce the fix: Save the script from http://paste.ubuntu.com/6762313/ into nonces_cleanup.py and then run it using cron, every 5 minutes: cat nonces_cleanup.py | sudo maas shell Note that the cleanup will not happen the first time you run the script, only the second time (and all the other times after that); Read the script if you want to know why ;). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190986 Title: ERROR Nonce already used To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1190986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311433] Re: REGRESSION: AttributeError: 'functools.partial' object has no attribute '__module__'
** 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 (http://localhost/MAAS) → the home page displays
a 500 error. The log in /var/log/maas/maas.log contains the exception:
http://paste.ubuntu.com/7417954/ (AttributeError: 'functools.partial' object
has no attribute '__module__')
- in the MAAS test suite.
+ With the fix:
+ 1. Install MAAS
+ 2. Access the MAAS home page (http://localhost/MAAS) → see the login home
page.
- Full stack trace:
+ [Description of the problem]
- _StringException: Traceback (most recent call last):
- File "/home/ed/canonical/maas/trunk/src/maasserver/tests/test_api.py", line
477, in test_internal_error_generates_proper_api_response
- response = self.client.post(reverse('nodes_handler'), {'op': 'new'})
- File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line
528, in reverse
- return iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args,
**kwargs))
- File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line
399, in _reverse_with_prefix
- self._populate()
- File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line
286, in _populate
- for name in pattern.reverse_dict:
- File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line
311, in reverse_dict
- self._populate()
- File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line
286, in _populate
- for name in pattern.reverse_dict:
- File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line
311, in reverse_dict
- self._populate()
- File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line
272, in _populate
- lookup_str = callback.__module__ + "." + callback.__class__.__name__
- AttributeError: 'functools.partial' object has no attribute '__module__'
+ This was caused by a regression in python-django introduced by a recent
+ security update (see the bug's comment for details).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311433
Title:
REGRESSION: AttributeError: 'functools.partial' object has no
attribute '__module__'
To manage notifications about this bug go to:
https://bugs.launchpad.net/django/+bug/1311433/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1086162] Re: IPMI based power management default to IPMI 1.5 based authentication
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1086162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301809] Re: Report boot images no directory traceback
Well, it's the reporting task that broke because of the absence of '/var/lib/maas/boot-resources/current/'. The easiest way to fix this is to change the reporting task so that it copes with that. ** Changed in: maas Importance: Undecided => Critical ** Changed in: maas Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301809 Title: Report boot images no directory traceback To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1301809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301809] Re: Report boot images no directory traceback
** Branch linked: lp:~rvb/maas/reporting-bug-1301809 ** Changed in: maas Milestone: None => 14.10 ** Changed in: maas Assignee: (unassigned) => Raphaël Badin (rvb) ** Changed in: maas Status: Triaged => In Progress ** Also affects: maas/1.5 Importance: Undecided Status: New ** Changed in: maas/1.5 Milestone: None => 14.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301809 Title: Report boot images no directory traceback To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1301809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301809] Re: Report boot images no directory traceback
** Branch linked: lp:~rvb/maas/reporting-bug-1301809-1.5 ** Changed in: maas/1.5 Assignee: (unassigned) => Raphaël Badin (rvb) ** Changed in: maas Status: In Progress => Fix Committed ** Changed in: maas/1.5 Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301809 Title: Report boot images no directory traceback To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1301809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240215] Re: changing the default arches in import_pxe_files prevents maas-import-ephemerals from running
** Changed in: maas Assignee: (unassigned) => Andres Rodriguez (andreserl) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240215 Title: changing the default arches in import_pxe_files prevents maas-import- ephemerals from running To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1240215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301809] Re: Report boot images no directory traceback
** 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 to Ubuntu. https://bugs.launchpad.net/bugs/1301809 Title: Report boot images no directory traceback To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1301809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301809] Re: Report boot images no directory traceback
** Changed in: maas/1.5 Milestone: 14.04 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301809 Title: Report boot images no directory traceback To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1301809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301809] Re: Report boot images no directory traceback
** Changed in: maas/1.5 Milestone: None => 14.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301809 Title: Report boot images no directory traceback To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1301809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307415] Re: IntegrityError: duplicate key value violates unique constraint "maasserver_componenterror_component_key"
** 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 to Ubuntu. https://bugs.launchpad.net/bugs/1307415 Title: IntegrityError: duplicate key value violates unique constraint "maasserver_componenterror_component_key" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1307415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302956] Re: maas.ubuntu.com only shows the documentation for the most recent MAAS version
** Changed in: maas Status: In Progress => Fix Committed ** Changed in: maas/1.4 Status: In Progress => Fix Committed ** Changed in: maas/1.5 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/1302956 Title: maas.ubuntu.com only shows the documentation for the most recent MAAS version To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1302956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271188] Re: maas-import-ephermerals provides no feedback on progress
> The bug is really in the simplestreams library, it does all the downloading. Well, simplestreams does only *part* of the downloading: it downloads all the ephemerals all right but the installer files are still downloaded by MAAS' script (./scripts/maas-import-pxe-files). -- 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 no feedback on progress To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1271188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
Another note: to debug commissioning problems, the quickest way is to have a look at the output of the scripts that failed. You can't do that with the UI right now but it's all available if you use the API/CLI: The following CLI command : $ maas-cli maas commissioning-results list will spit out all the result of the commissioning scripts. The 'data', the actual output of the script, is base64-encoded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
Btw, I just found (and fixed) bug 1278895. It means that the list of the failed scripts in the "failed [3/5] …" message is actually wrong: it's the list of the scripts that didn't fail (!). Here is the list of all the scripts that maas has: 00-maas-01-lshw 00-maas-02-virtuality 00-maas-03-install-lldpd 99-maas-01-wait-for-lldpd 99-maas-02-capture-lldp When MAAS says "failed [2/5] 00-maas-01-lshw 00-maas-02-virtuality", it means '00-maas-03-install-lldpd', '99-maas-01-wait-for-lldpd' and '99-maas-02-capture-lldp' failed. This is a nasty bug (!). It's fixed as of revision 1926. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181334] Re: i386 required to install amd64
** Changed in: maas Assignee: (unassigned) => Tycho Andersen (tycho-s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181334 Title: i386 required to install amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253940] Re: The parameters for the ipmi_si kernel module need to be tweaked for IPMI detection to work on certain hardware.
We need to investigate the possibility of having a list of parameters for the ipmi_si kernel module and try doing the IPMI detection for all these parameters in sequence. ** Also affects: maas-enlist (Ubuntu) Importance: Undecided Status: New ** Changed in: maas Milestone: None => 14.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253940 Title: The parameters for the ipmi_si kernel module need to be tweaked for IPMI detection to work on certain hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1253940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1153077] Re: rabbitmq queue fills up and celery stops executing tasks when upload_dhcp_leases is done every minute (by default)
> Maybe RabbitMQ or Celery have a mechanism for ignoring old jobs. If not, we > can add a timestamp check to the job > implementations themselves. That's a good point, there is support in Celery for this: http://celery.github.io/celery/userguide/executing.html#expiration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1153077 Title: rabbitmq queue fills up and celery stops executing tasks when upload_dhcp_leases is done every minute (by default) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1153077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287373] Re: cli 'nodes list-allocated' does not list all nodes allocated
Did you, by any chance, acquire the two nodes using different API keys (both belonging to the user 'smoser')? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287373 Title: cli 'nodes list-allocated' does not list all nodes allocated To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1287373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271188] Re: maas-import-ephermerals provides no feedback on progress
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 no feedback on progress To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1271188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087183] Re: MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1087183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365130] Re: django-admin prints spurious messages to stdout, breaking scripts
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365130 Title: django-admin prints spurious messages to stdout, breaking scripts To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1365130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365130] Re: django-admin prints spurious messages to stdout, breaking scripts
** 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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365130 Title: django-admin prints spurious messages to stdout, breaking scripts To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1365130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381058] Re: Upgrading introduces a spurious cluster controller
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 exactly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381058 Title: Upgrading introduces a spurious cluster controller To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1381058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1087183] Re: MaaS cloud-init configuration specifies 'manage_etc_hosts: localhost'
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1087183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382266] Re: maas-proxy fails to start on freshly installed MAAS
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 about this bug go to: https://bugs.launchpad.net/maas/+bug/1382266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
> 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 the hostname from the IP address "manually", having observed the pattern that MAAS uses. Agreed that the path of least resistance at this stage is to improve the new "reserve IP"API to include a hostname and use that in Juju. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1330498] Re: maas package missing dependency on python-decorator
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), python:any (>= 2.7.1-0ubuntu2), python-django (>= 1.1), python-oauth (>= 1.0.1), python-decorator Utopic: Depends: python (>= 2.7), python (<< 2.8) The upstream version is the same: 0.2.3-1ubuntu5 in Trusty, 0.2.3-2 in Utopic. ** Also affects: python-django-piston (Ubuntu) Importance: Undecided Status: New ** Changed in: maas (Ubuntu) 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/1330498 Title: maas package missing dependency on python-decorator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1330498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1328659] Re: import_boot_images task fails on utopic
** 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 to: https://bugs.launchpad.net/maas/+bug/1328659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314629] Re: AMT support requires an extra package to be installed
> 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. https://bugs.launchpad.net/bugs/1314629 Title: AMT support requires an extra package to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1314629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237364] Re: Commissioning with a Saucy image sets node status to "Failed tests"
** 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/1237364 Title: Commissioning with a Saucy image sets node status to "Failed tests" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1237364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228085] Re: The commissioning script 00-maas-03-install-lldpd outputs to stderr.
** Changed in: maas Assignee: Raphaël Badin (rvb) => Gavin Panella (allenap) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228085 Title: The commissioning script 00-maas-03-install-lldpd outputs to stderr. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1228085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1346279] Re: MAAS requires explicit dependency on python-bson
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 src/provisioningserver/utils/__init__.py must be present as "build dependencies" in the packaging. I see three possible solutions here: - Add all the required dependencies as build dependencies in the packaging. - Move map_enum in a place where it can be imported in isolation without triggering a ton of imports - Add a copy of the code of map_enum in src/maasserver/utils/jsenums.py instead of importing the shared map_enum. ** Summary changed: - MAAS requires explicit dependency on python-bson + Building the MAAS package fails with "ImportError: No module named bson" ** 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/1346279 Title: Building the MAAS package fails with "ImportError: No module named bson" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1346279] Re: Building the MAAS package fails with "ImportError: No module named bson"
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 just a couple of lines) in jsenum. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346279 Title: Building the MAAS package fails with "ImportError: No module named bson" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1346279] Re: Building the MAAS package fails with "ImportError: No module named bson"
> 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: lp:~rvb/maas/fixjsenum -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346279 Title: Building the MAAS package fails with "ImportError: No module named bson" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081660] Re: If maas-enlist fails to reach a DNS server, the node will be named "; ; connection timed out; no servers could be reached"
@Scott. This bug appears everytime the DNS config is wrong and the query issued an enlisting node times out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081660 Title: If maas-enlist fails to reach a DNS server, the node will be named ";; connection timed out; no servers could be reached" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1081660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081660] Re: If maas-enlist fails to reach a DNS server, the node will be named "; ; connection timed out; no servers could be reached"
issued by* an enlisting node -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081660 Title: If maas-enlist fails to reach a DNS server, the node will be named ";; connection timed out; no servers could be reached" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1081660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1090334] [NEW] MAAS (in precise) requires django >= 1.3.1-4ubuntu1.5
Public bug reported: The upcoming SRU maas (in precise) depends on python-django without specifying a particular version but it requires the two backports present in python-django version 1.3.1-4ubuntu1.5 (support for 'theGenericIPAddressField' field and the 'prefetch_related' utility method). Without that, the upgrade from the package in precise to the SRU package fails with ImportError: cannot import name GenericIPAddressField (http://paste.ubuntu.com/1436102/) ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090334 Title: MAAS (in precise) requires django >= 1.3.1-4ubuntu1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1090334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
