[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
This bug was fixed in the package maas - 1.3+bzr1461+dfsg-0ubuntu2.1 --- maas (1.3+bzr1461+dfsg-0ubuntu2.1) raring-proposed; urgency=low * debian/patches: - 99-fix-ipmi-stat-lp1086160.patch: Drop. The following patch removes the need for this fix. (LP: #1171988) - 99-fix-ipmi-lp1171418.patch: Do not check current node state when executing an ipmi command, which ensures that nodes are always turned on/off regardless of their power state. This fixes corner cases found when running automated tests. (LP: #1171418) - 99-fix-comissioning-lp1131418.patch: Fixes the commissioning process, allowing nodes to successfully commission, when tag's with no definition have been created. This issue will only appear when these special tags are created. (LP: #1131418) - 99-import-raring-images-lp1182642.patch: Enables the import of raring images by default (LP: #1182642) - 99-fix-new-image-install-lp1182646.patch: Fixes the installation of new ephemeral images, that fail due to not being able to overwrite a symlink. (LP: #1182646) -- Andres Rodriguez andres...@ubuntu.com Tue, 23 Apr 2013 14:02:33 -0400 ** Changed in: maas (Ubuntu Raring) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
** Changed in: maas/1.2 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
I have tested this and it works as expected. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
Hello Ramon, or anyone else affected, Accepted maas into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/maas/1.3+bzr1461+dfsg- 0ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: maas (Ubuntu Raring) Status: New = Fix Committed ** Tags added: verification-needed -- 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/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
** Branch linked: lp:ubuntu/raring-proposed/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/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
** Changed in: maas Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
** Branch linked: lp:ubuntu/saucy-proposed/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/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
This bug was fixed in the package maas - 1.3+bzr1461+dfsg-0ubuntu3 --- maas (1.3+bzr1461+dfsg-0ubuntu3) saucy; urgency=low * debian/patches: - 99-fix-ipmi-stat-lp1086160.patch: Drop. The following patch removes the need for this fix. (LP: #1171988) - 99-fix-ipmi-lp1171418.patch: Do not check current node state when executing an ipmi command, which ensures that nodes are always turned on/off regardless of their power state. This fixes corner cases found when running automated tests. (LP: #1171418) - 99-fix-comissioning-lp1131418.patch: Fixes the commissioning process, allowing nodes to successfully commission, when tag's with no definition have been created. This issue will only appear when these special tags are created. (LP: #1131418) - 99-import-raring-images-lp1182642.patch: Enables the import of raring images by default (LP: #1182642) - 99-fix-new-image-install-lp1182646.patch: Fixes the installation of new ephemeral images, that fail due to not being able to overwrite a symlink. (LP: #1182646) -- Andres Rodriguez andres...@ubuntu.com Tue, 23 Apr 2013 14:02:33 -0400 ** Changed in: maas (Ubuntu) Status: Confirmed = 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/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
** Branch linked: lp:~rvb/maas/backport-fixes ** Also affects: maas/1.2 Importance: Undecided Status: New ** Changed in: maas Assignee: (unassigned) = Raphaël Badin (rvb) ** Changed in: maas Status: Triaged = Fix Committed ** Changed in: maas/1.2 Assignee: (unassigned) = Raphaël Badin (rvb) -- 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/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
** Changed in: maas/1.2 Importance: Undecided = Critical ** Changed in: maas/1.2 Status: New = 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/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
Hi, this is missing Regression Potential. Please see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for more information. ** Also affects: maas (Ubuntu Raring) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
** Description changed: maas version installed: 1.2+bzr1359+dfsg-0ubuntu1~ppa1 on Ubuntu Precise 12.04.2 We enlist a node, the accept and commission it and the node stays in Commissioning state. We see that after cloud-init the node tries to access maas and gets an internal server error. In the maas.log file we see this: ERROR 2013-02-21 16:11:46,283 maas.maasserver Exception: Invalid expression ERROR 2013-02-21 16:11:46,283 maas.maasserver Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/django/core/handlers/base.py, line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.7/dist-packages/django/views/decorators/vary.py, line 22, in inner_func response = func(*args, **kwargs) File /usr/lib/python2.7/dist-packages/piston/resource.py, line 166, in __call__ result = self.error_handler(e, request, meth, em_format) File /usr/lib/python2.7/dist-packages/piston/resource.py, line 164, in __call__ result = meth(request, *args, **kwargs) File /usr/lib/python2.7/dist-packages/maasserver/api.py, line 308, in dispatch return function(self, request, *args, **kwargs) File /usr/lib/python2.7/dist-packages/metadataserver/api.py, line 230, in signal self._store_commissioning_results(node, request) File /usr/lib/python2.7/dist-packages/metadataserver/api.py, line 191, in _store_commissioning_results node.set_hardware_details(raw_content) File /usr/lib/python2.7/dist-packages/maasserver/models/node.py, line 798, in set_hardware_details update_hardware_details(self, xmlbytes, Tag.objects) File /usr/lib/python2.7/dist-packages/maasserver/models/node.py, line 398, in update_hardware_details has_tag = evaluator(tag.definition) File xpath.pxi, line 321, in lxml.etree.XPathElementEvaluator.__call__ (src/lxml/lxml.etree.c:117734) File xpath.pxi, line 239, in lxml.etree._XPathEvaluatorBase._handle_result (src/lxml/lxml.etree.c:116911) File xpath.pxi, line 225, in lxml.etree._XPathEvaluatorBase._raise_eval_error (src/lxml/lxml.etree.c:116780) XPathEvalError: Invalid expression Maybe related, on juju we set a maas-name constraint to install each service to a particular. node (that worked) and then constraints weren't recognized at some point (we destroyed the juju environment and started again). - [Impact] MAAS machines in the commissioning process fail to successfully commission and be placed into Ready state. This is caused when the user defines tag with no definition. These tag with no definition simply server for node identification purposes. Without this fix, machine wont be able to commission successfully if the user has previously defined a 'no-definition' tag. [Test Case] To reproduce do the following: 1. Install MAAS 2. Enlist machines 3. Define a tag with no definition 4. Try to commission machines, These will fail to commission, or if they do, their hardware requirements wont be appear and juju wont be able to deploy these machines. 5. Try the proposed fix. Machines would be able to commission successfully. + + [Regression Potential] + Minimal, this actually fixes a regression. This has been tested both manually and in automated labs. -- 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/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Changed in: maas (Ubuntu) Status: New = Confirmed ** Changed in: maas (Ubuntu) Importance: Undecided = Critical ** Changed in: maas (Ubuntu) Assignee: (unassigned) = Andres Rodriguez (andreserl) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1131418 Title: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1131418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1131418] Re: Nodes don't go to ready, after commissioning they get a 500 error when reporting back to maas
** Description changed: maas version installed: 1.2+bzr1359+dfsg-0ubuntu1~ppa1 on Ubuntu Precise 12.04.2 We enlist a node, the accept and commission it and the node stays in Commissioning state. We see that after cloud-init the node tries to access maas and gets an internal server error. In the maas.log file we see this: ERROR 2013-02-21 16:11:46,283 maas.maasserver Exception: Invalid expression ERROR 2013-02-21 16:11:46,283 maas.maasserver Traceback (most recent call last): - File /usr/lib/python2.7/dist-packages/django/core/handlers/base.py, line 111, in get_response - response = callback(request, *callback_args, **callback_kwargs) - File /usr/lib/python2.7/dist-packages/django/views/decorators/vary.py, line 22, in inner_func - response = func(*args, **kwargs) - File /usr/lib/python2.7/dist-packages/piston/resource.py, line 166, in __call__ - result = self.error_handler(e, request, meth, em_format) - File /usr/lib/python2.7/dist-packages/piston/resource.py, line 164, in __call__ - result = meth(request, *args, **kwargs) - File /usr/lib/python2.7/dist-packages/maasserver/api.py, line 308, in dispatch - return function(self, request, *args, **kwargs) - File /usr/lib/python2.7/dist-packages/metadataserver/api.py, line 230, in signal - self._store_commissioning_results(node, request) - File /usr/lib/python2.7/dist-packages/metadataserver/api.py, line 191, in _store_commissioning_results - node.set_hardware_details(raw_content) - File /usr/lib/python2.7/dist-packages/maasserver/models/node.py, line 798, in set_hardware_details - update_hardware_details(self, xmlbytes, Tag.objects) - File /usr/lib/python2.7/dist-packages/maasserver/models/node.py, line 398, in update_hardware_details - has_tag = evaluator(tag.definition) - File xpath.pxi, line 321, in lxml.etree.XPathElementEvaluator.__call__ (src/lxml/lxml.etree.c:117734) - File xpath.pxi, line 239, in lxml.etree._XPathEvaluatorBase._handle_result (src/lxml/lxml.etree.c:116911) - File xpath.pxi, line 225, in lxml.etree._XPathEvaluatorBase._raise_eval_error (src/lxml/lxml.etree.c:116780) + File /usr/lib/python2.7/dist-packages/django/core/handlers/base.py, line 111, in get_response + response = callback(request, *callback_args, **callback_kwargs) + File /usr/lib/python2.7/dist-packages/django/views/decorators/vary.py, line 22, in inner_func + response = func(*args, **kwargs) + File /usr/lib/python2.7/dist-packages/piston/resource.py, line 166, in __call__ + result = self.error_handler(e, request, meth, em_format) + File /usr/lib/python2.7/dist-packages/piston/resource.py, line 164, in __call__ + result = meth(request, *args, **kwargs) + File /usr/lib/python2.7/dist-packages/maasserver/api.py, line 308, in dispatch + return function(self, request, *args, **kwargs) + File /usr/lib/python2.7/dist-packages/metadataserver/api.py, line 230, in signal + self._store_commissioning_results(node, request) + File /usr/lib/python2.7/dist-packages/metadataserver/api.py, line 191, in _store_commissioning_results + node.set_hardware_details(raw_content) + File /usr/lib/python2.7/dist-packages/maasserver/models/node.py, line 798, in set_hardware_details + update_hardware_details(self, xmlbytes, Tag.objects) + File /usr/lib/python2.7/dist-packages/maasserver/models/node.py, line 398, in update_hardware_details + has_tag = evaluator(tag.definition) + File xpath.pxi, line 321, in lxml.etree.XPathElementEvaluator.__call__ (src/lxml/lxml.etree.c:117734) + File xpath.pxi, line 239, in lxml.etree._XPathEvaluatorBase._handle_result (src/lxml/lxml.etree.c:116911) + File xpath.pxi, line 225, in lxml.etree._XPathEvaluatorBase._raise_eval_error (src/lxml/lxml.etree.c:116780) XPathEvalError: Invalid expression Maybe related, on juju we set a maas-name constraint to install each service to a particular. node (that worked) and then constraints weren't recognized at some point (we destroyed the juju environment and started again). + + + [Impact] + MAAS machines in the commissioning process fail to successfully commission and be placed into Ready state. This is caused when the user defines tag with no definition. These tag with no definition simply server for node identification purposes. Without this fix, machine wont be able to commission successfully if the user has previously defined a 'no-definition' tag. + + [Test Case] + To reproduce do the following: + + 1. Install MAAS + 2. Enlist machines + 3. Define a tag with no definition + 4. Try to commission machines, + These will fail to commission, or if they do, their hardware requirements wont be appear and juju wont be able to deploy these machines. + 5. Try the proposed fix. + Machines would be able to commission successfully. -- You received this bug notification because
