[Bug 832507] Re: console.log grows indefinitely
Fix proposed to branch: master Review: https://review.openstack.org/39048 ** Changed in: nova Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+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 1190036] Re: default cinder database is /usr/lib/python2.7/dist-packages/cinder/openstack/common/db/cinder.sqlit
Reviewed: https://review.openstack.org/32646 Committed: http://github.com/openstack/cinder/commit/57cdb8f8c36a4835c918d9644bc26f41d0c0045a Submitter: Jenkins Branch:master commit 57cdb8f8c36a4835c918d9644bc26f41d0c0045a Author: Adam Gandelman Date: Tue Jun 11 14:50:01 2013 -0700 Re-set default sql_connection and sqlite_db. The defaults seem to have been lost in the migration to Oslo's DB code. Re-set them to pre-grizzly defaults. Fixes bug: #1190036 Change-Id: I7fca70e67d67905b15c2faaa745a86e957bec06e ** Changed in: cinder Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1190036 Title: default cinder database is /usr/lib/python2.7/dist- packages/cinder/openstack/common/db/cinder.sqlit To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1190036/+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 1190036] Re: default cinder database is /usr/lib/python2.7/dist-packages/cinder/openstack/common/db/cinder.sqlit
Fix proposed to branch: master Review: https://review.openstack.org/32646 ** Changed in: cinder Status: New => In Progress ** Changed in: cinder Assignee: (unassigned) => Adam Gandelman (gandelman-a) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1190036 Title: default cinder database is /usr/lib/python2.7/dist- packages/cinder/openstack/common/db/cinder.sqlit To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1190036/+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 1185178] Re: glanceclient tests failing on fake_host
Reviewed: https://review.openstack.org/30795 Committed: http://github.com/openstack/cinder/commit/1365ada3bcd8b9f7f4c1c7f7c9f158fc9ae867b3 Submitter: Jenkins Branch:master commit 1365ada3bcd8b9f7f4c1c7f7c9f158fc9ae867b3 Author: Adam Gandelman Date: Tue May 28 14:34:30 2013 -0700 test_glance.py: Stub out _get_member_model as well. glanceclient's v2 client needs to also have its _get_member_model() stubbed out as well, to avoid attempts to reach 'fake_host' during client instantiation. Update: Only stub when _get_member_model() when required. Change-Id: I943cbb017ccdbe4f6c994bc83cbefe8693f4672b Fixes: bug #1185178. ** Changed in: cinder Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1185178 Title: glanceclient tests failing on fake_host To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1185178/+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 1182624] Fix proposed to nova (stable/folsom)
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/29982 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1182624 Title: Uncached instance builds fail with non-zero root disk sizes To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1182624/+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 1032633] Re: Keystone's token table grows unconditionally when using SQL backend.
Reviewed: https://review.openstack.org/28133 Committed: http://github.com/openstack/keystone/commit/ff76a1b5cd3308cfb0ce936800364e27413ed946 Submitter: Jenkins Branch:master commit ff76a1b5cd3308cfb0ce936800364e27413ed946 Author: Jamie Lennox Date: Fri May 3 14:04:09 2013 +1000 Implement Token Flush via keystone-manage. Creates a cli entry 'token_flush' which removes all expired tokens. Fixes: bug 1032633 Implements: blueprint keystone-manage-token-flush Change-Id: I47eab99b577ff9e9ee74fee08e18fd07c4af5aad ** Changed in: keystone Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1032633 Title: Keystone's token table grows unconditionally when using SQL backend. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1032633/+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 1078497] Fix merged to keystone (master)
Reviewed: https://review.openstack.org/27104 Committed: http://github.com/openstack/keystone/commit/08aaeb081958b05124ee60a0a9d34797b1f2c364 Submitter: Jenkins Branch:master commit 08aaeb081958b05124ee60a0a9d34797b1f2c364 Author: Bernhard M. Wiedemann Date: Thu Apr 18 10:39:15 2013 +0200 Test listing of tokens with a null tenant Test for fix of bug 1078497 Change-Id: I5cd28b38111f3e80adbb33ef1b1c8db7630d75f8 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1078497 Title: keystone throws error when removing user from tenant. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1078497/+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 1032633] Re: Keystone's token table grows unconditionally when using SQL backend.
Fix proposed to branch: master Review: https://review.openstack.org/28133 ** Changed in: keystone Status: Invalid => In Progress ** Changed in: keystone Assignee: (unassigned) => Jamie Lennox (jamielennox) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1032633 Title: Keystone's token table grows unconditionally when using SQL backend. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1032633/+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 1155458] Re: 500 response when trying to create a server from a deleted image
Reviewed: https://review.openstack.org/27790 Committed: http://github.com/openstack/nova/commit/7fa5e7f06cc767e523c79b39295b847256bbc9d8 Submitter: Jenkins Branch:master commit 7fa5e7f06cc767e523c79b39295b847256bbc9d8 Author: Matthew Sherborne Date: Tue Apr 30 07:19:03 2013 +1000 Create instance with deleting image If we attempt to create a new instance with an image that has just now been deleted in glance, (ie. status="DELETED", but deleted=False). The server should throw a 4XX error rather than a 5XX error. This commit just adds tests. Tests bug 1155458 Change-Id: Ifae470e96ddc4526ef67581a1d7171ccc5fd32b7 ** Changed in: nova Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1155458 Title: 500 response when trying to create a server from a deleted image To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1155458/+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 1078497] Fix proposed to keystone (stable/essex)
Fix proposed to branch: stable/essex Review: https://review.openstack.org/27406 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1078497 Title: keystone throws error when removing user from tenant. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1078497/+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 1167421] Re: Upgrading from folsom to grizzly results in all tenants/users being disabled
Reviewed: https://review.openstack.org/26857 Committed: http://github.com/openstack/keystone/commit/717f1aa7f6cb5f01fe16a516644c96419c6900c5 Submitter: Jenkins Branch:stable/grizzly commit 717f1aa7f6cb5f01fe16a516644c96419c6900c5 Author: Dolph Mathews Date: Wed Apr 10 10:04:16 2013 -0500 Use is_enabled() in folsom->grizzly upgrade (bug 1167421) Change-Id: Iddc10167c94deacec07cab7ec9316849263fb462 ** Changed in: keystone/grizzly Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1167421 Title: Upgrading from folsom to grizzly results in all tenants/users being disabled To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1167421/+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 1166455] Re: nova flavor-list only shows 1000 flavors
Reviewed: https://review.openstack.org/27060 Committed: http://github.com/openstack/python-novaclient/commit/339689483da3c1591211762ef631d432844ff9ef Submitter: Jenkins Branch:master commit 339689483da3c1591211762ef631d432844ff9ef Author: Ubuntu Date: Wed Apr 17 13:12:36 2013 + Make list flavor show extra specs optional. Flavor list will get each flavors extra_specs by making fresh requests to nova. When there are lots of flavors, the flavor list will take a while to run. So let us make show extra-specs optional. Fix bug: #1166455 Change-Id: I86aef1035be6a88b8d9fb49a89f5a608a72589dd ** Changed in: python-novaclient Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1166455 Title: nova flavor-list only shows 1000 flavors To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1166455/+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 1078497] Fix proposed to keystone (master)
Fix proposed to branch: master Review: https://review.openstack.org/27104 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1078497 Title: keystone throws error when removing user from tenant. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1078497/+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 1166455] Re: nova flavor-list only shows 1000 flavors
Fix proposed to branch: master Review: https://review.openstack.org/27060 ** Changed in: python-novaclient Status: Confirmed => In Progress ** Changed in: python-novaclient Assignee: (unassigned) => TianTian Gao (gtt116) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1166455 Title: nova flavor-list only shows 1000 flavors To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1166455/+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 985489] Re: nova-compute stops processing compute.$HOSTNAME occasionally on libvirt
** Changed in: nova Status: Confirmed => In Progress ** Changed in: nova Assignee: (unassigned) => wangpan (hzwangpan) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/985489 Title: nova-compute stops processing compute.$HOSTNAME occasionally on libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/985489/+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 985489] Re: nova-compute stops processing compute.$HOSTNAME occasionally on libvirt
** Changed in: nova Status: Confirmed => In Progress ** Changed in: nova Assignee: Michael H Wilson (geekinutah) => wangpan (hzwangpan) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/985489 Title: nova-compute stops processing compute.$HOSTNAME occasionally on libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/985489/+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 1165059] Re: Grizzly testing packages : python-quantumclient installation/upgrade fails
Fix proposed to branch: master Review: https://review.openstack.org/26306 ** Changed in: python-quantumclient Status: Confirmed => In Progress ** Changed in: python-quantumclient Assignee: (unassigned) => Chuck Short (zulcss) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-quantumclient in Ubuntu. https://bugs.launchpad.net/bugs/1165059 Title: Grizzly testing packages : python-quantumclient installation/upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/python-quantumclient/+bug/1165059/+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 1088411] Fix proposed to cinder (stable/folsom)
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/26008 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1088411 Title: Cannot attach volumes to instances if using NexentaStor driver To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1088411/+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 1158247] Re: test_server_monkey_patch leaves orphaned process
Reviewed: https://review.openstack.org/25635 Committed: http://github.com/openstack/glance/commit/13f8f0082faf70debb3c56e01e7492f29913e783 Submitter: Jenkins Branch:milestone-proposed commit 13f8f0082faf70debb3c56e01e7492f29913e783 Author: John Bresnahan Date: Fri Mar 22 11:26:12 2013 -1000 Directly verifying that time and socket are monkey patched This tests makes sure that thew wsgi object properly monkey patched two needed modules, socket and time. In bug 988099 it was noted that the time module was not being monkey patched. A test was added that unfortunately introduced a bug and a patch to revert it is here: https://review.openstack.org/#/c/25107/ in order to fix bug 1158247. This patch allows for test_server_monkey_patch.py to be removed without losing the verification of that functionality. Fixes bug 1158247 Change-Id: I8da6b04d0cc0dae00ba52e5b7350a5e01a76cadb ** Changed in: glance Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1158247 Title: test_server_monkey_patch leaves orphaned process To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1158247/+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 1150720] Re: [SRU] There is now a dependency on paramiko v1.8.0
Reviewed: https://review.openstack.org/24756 Committed: http://github.com/openstack/cinder/commit/db0595a4c516738f110482396e0fe90ecaf71b38 Submitter: Jenkins Branch:stable/folsom commit db0595a4c516738f110482396e0fe90ecaf71b38 Author: Avishay Traeger Date: Tue Mar 19 08:24:50 2013 +0200 Backport paramiko 1.8.0 requirement to Folsom. Require paramiko >= 1.8.0 There is a well-known bug in the Paramiko SSH library that causes these Exceptions: SSHException: Error connecting via ssh: PID check failed. RNG must be re-initialized after fork(). Hint: Try Random.atfork() This bug has been fixed in Paramiko, and therefore we should require the newer version for Cinder drivers that use Paramiko to function properly. Change-Id: Ia14b7b72393e2a2482ebde418b5477934779bf13 Fixes: bug 1150720 ** Tags added: in-stable-folsom -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1150720 Title: [SRU] There is now a dependency on paramiko v1.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1150720/+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 1150720] Fix proposed to cinder (stable/folsom)
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/24756 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1150720 Title: [SRU] There is now a dependency on paramiko v1.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1150720/+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 1078497] Fix proposed to keystone (stable/essex)
Fix proposed to branch: stable/essex Review: https://review.openstack.org/24449 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1078497 Title: keystone throws error when removing user from tenant. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1078497/+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 1073569] Fix merged to nova (stable/essex)
Reviewed: https://review.openstack.org/22943 Committed: http://github.com/openstack/nova/commit/87361d34878618a0ffb1cb79bb8ec5a022c82d5f Submitter: Jenkins Branch:stable/essex commit 87361d34878618a0ffb1cb79bb8ec5a022c82d5f Author: Jeremy Stanley Date: Tue Feb 26 02:51:48 2013 + Force earlier version of sqlalchemy Fixes bug 1073569 Backported from https://review.openstack.org/15097 Set the version of sqlalchemy to be earlier than the 0.8 beta as it is incompatible with the latest available sqlalchemy-migrate and as a result run_tests.sh does not run any tests. Change-Id: I3cb367306c4e3801c9979bba0bd03a11fcea9aa2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1073569 Title: Jenkins jobs fail because of incompatibility between sqlalchemy- migrate and the newest sqlalchemy-0.8.0b1 To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1073569/+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 1073569] Fix proposed to nova (stable/essex)
Fix proposed to branch: stable/essex Review: https://review.openstack.org/22943 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1073569 Title: Jenkins jobs fail because of incompatibility between sqlalchemy- migrate and the newest sqlalchemy-0.8.0b1 To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1073569/+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 1061665] Re: Filter scheduler not respecting the force_hosts hint
Reviewed: https://review.openstack.org/21018 Committed: http://github.com/openstack/openstack-manuals/commit/d9b0e389b94ae8972ba3404069bcb0866c53e26c Submitter: Jenkins Branch:stable/folsom commit d9b0e389b94ae8972ba3404069bcb0866c53e26c Author: atul jha Date: Tue Nov 13 21:10:11 2012 +0530 Cherry picked from https://review.openstack.org/#/c/15983/ Fix bug 1061665, --force_hosts hint for launching instance updates --force_hosts no longer available in Folsom, have to indicate an availability zone instead. Patchset attempts to explain how to get the availability zone name that you want. Please review. Patchset addresses comments about zone versus host, adding new section rather than replacing host section completely. Change-Id: Ifea0df3dc950c165718fa160bc08f1b1487c3f82 ** Tags added: in-stable-folsom -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1061665 Title: Filter scheduler not respecting the force_hosts hint To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1061665/+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 1061665] Fix proposed to openstack-manuals (stable/folsom)
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/21018 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1061665 Title: Filter scheduler not respecting the force_hosts hint To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1061665/+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 1029430] Re: KVM guests networking issues with no virbr0 and with vhost_net kernel modules loaded
Reviewed: https://review.openstack.org/18450 Committed: http://github.com/openstack/nova/commit/4bfc8f1165b05c2cc7c5506641b9b85fa8e1e144 Submitter: Jenkins Branch:stable/folsom commit 4bfc8f1165b05c2cc7c5506641b9b85fa8e1e144 Author: Adam Gandelman Date: Tue Dec 18 09:50:46 2012 -0800 Add an iptables mangle rule per-bridge for DHCP. When vhost-net is present on a host, and DHCP services are run on the same system as guests (multi_host), an iptables rule is needed to fill packet checksums. This adds a rule per-bridge for multi_host networks when vhost-net is present, similar to how newer versions of libvirt handle the issue for bridges/networks that it manages. Fixes LP: #1029430 EDIT: Updated tests and pep8. (Backported from commit 901a3dacb6f2d36cbe8d23707dba75452e91df33) Change-Id: I1a51c1d808fa47a77e713dbfe384ffad183d6031 ** Changed in: nova/folsom Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1029430 Title: KVM guests networking issues with no virbr0 and with vhost_net kernel modules loaded To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1029430/+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 1083155] Re: Unable to set Content-MD5 header when using chunked transfer encoding
Reviewed: https://review.openstack.org/17926 Committed: http://github.com/openstack/glance/commit/cb54b00873e1c72c481d30fc8aef5e8c51d5e964 Submitter: Jenkins Branch:master commit cb54b00873e1c72c481d30fc8aef5e8c51d5e964 Author: Sascha Peilicke Date: Wed Dec 12 11:36:14 2012 +0100 Set Content-MD5 after calling webob.Response._app_iter__set. Discussed upstream at https://github.com/Pylons/webob/issues/86 Fixes bug 1083155 Change-Id: I75c634880e7abaacdcd416c27391e9fdc4874049 ** Changed in: glance Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-webob in Ubuntu. https://bugs.launchpad.net/bugs/1083155 Title: Unable to set Content-MD5 header when using chunked transfer encoding To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1083155/+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 1088295] Re: lxc container can control other container's cpu share, memory limit, or access of block and character devices
Reviewed: https://review.openstack.org/18788 Committed: http://github.com/openstack/openstack-manuals/commit/6b188da11ca022a98463cdcd1652b919c5db74dc Submitter: Jenkins Branch:master commit 6b188da11ca022a98463cdcd1652b919c5db74dc Author: annegentle Date: Mon Dec 31 14:38:36 2012 -0600 Adds fair warnings about LXC not recommended for use in production. Fix bug 1088295 Patch set adds Thierry's suggested edits. Change-Id: If9a215b90649110aaee8a5095c3874ad22a9f8f8 ** Changed in: openstack-manuals Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1088295 Title: lxc container can control other container's cpu share,memory limit,or access of block and character devices To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1088295/+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 1045152] Fix proposed to nova (master)
Fix proposed to branch: master Review: https://review.openstack.org/18532 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1045152 Title: Heavily loaded nova-compute instances don't sent reports frequently enough To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1045152/+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 1029430] Re: KVM guests networking issues with no virbr0 and with vhost_net kernel modules loaded
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/18450 ** Changed in: nova/folsom Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1029430 Title: KVM guests networking issues with no virbr0 and with vhost_net kernel modules loaded To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1029430/+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 1029430] Re: KVM guests networking issues with no virbr0 and with vhost_net kernel modules loaded
Reviewed: https://review.openstack.org/18336 Committed: http://github.com/openstack/nova/commit/901a3dacb6f2d36cbe8d23707dba75452e91df33 Submitter: Jenkins Branch:master commit 901a3dacb6f2d36cbe8d23707dba75452e91df33 Author: Adam Gandelman Date: Tue Dec 18 09:50:46 2012 -0800 Add an iptables mangle rule per-bridge for DHCP. When vhost-net is present on a host, and DHCP services are run on the same system as guests (multi_host), an iptables rule is needed to fill packet checksums. This adds a rule per-bridge for multi_host networks when vhost-net is present, similar to how newer versions of libvirt handle the issue for bridges/networks that it manages. Fixes LP: #1029430 EDIT: Updated tests and pep8. Change-Id: I1a51c1d808fa47a77e713dbfe384ffad183d6031 ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1029430 Title: KVM guests networking issues with no virbr0 and with vhost_net kernel modules loaded To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1029430/+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 1029430] Re: KVM guests networking issues with no virbr0 and with vhost_net kernel modules loaded
Fix proposed to branch: master Review: https://review.openstack.org/18336 ** Changed in: nova Status: Triaged => In Progress ** Changed in: nova Assignee: Jian Wen (wenjianhn) => Adam Gandelman (gandelman-a) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1029430 Title: KVM guests networking issues with no virbr0 and with vhost_net kernel modules loaded To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1029430/+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 861504] Re: nova-compute-lxc limited by available nbd devices to 16 instances
Reviewed: https://review.openstack.org/17886 Committed: http://github.com/openstack/nova/commit/ab3c602ac5456a509057f915a741970afeab0d4b Submitter: Jenkins Branch:master commit ab3c602ac5456a509057f915a741970afeab0d4b Author: Michael Still Date: Mon Dec 10 15:17:12 2012 +1100 Autodetect nbd devices. This means we don't need to the max_nbd_devices flag any more at all. This patch also moves the internal representation of the list of available nbd devices to not including the leading /dev/, but that is not exposed as a change in the interface to the class. Resolves bug 861504 and its duplicate 1088339. DocImpact. Change-Id: I5c6218122ab09781d8a2ecd6d8b76a74be4a6e91 ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/861504 Title: nova-compute-lxc limited by available nbd devices to 16 instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/861504/+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 861504] Re: nova-compute-lxc limited by available nbd devices to 16 instances
** Changed in: nova Status: Confirmed => In Progress ** Changed in: nova Assignee: (unassigned) => Michael Still (mikalstill) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/861504 Title: nova-compute-lxc limited by available nbd devices to 16 instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/861504/+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 1083155] Re: Unable to set Content-MD5 header when using chunked transfer encoding
Fix proposed to branch: master Review: https://review.openstack.org/17926 ** Changed in: glance Status: New => In Progress ** Changed in: glance Assignee: (unassigned) => Sascha Peilicke (saschpe) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-webob in Ubuntu. https://bugs.launchpad.net/bugs/1083155 Title: Unable to set Content-MD5 header when using chunked transfer encoding To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1083155/+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 1075859] Re: use_single_default_gateway does not function correctly
Reviewed: https://review.openstack.org/16722 Committed: http://github.com/openstack/nova/commit/80fefe5d2b030ff9a6429b84ef9761f85b5ddc99 Submitter: Jenkins Branch:stable/essex commit 80fefe5d2b030ff9a6429b84ef9761f85b5ddc99 Author: Joseph W. Breu Date: Thu Nov 15 14:25:50 2012 -0600 Fix use_single_default_gateway With FlatDHCP and use_single_default_gateway nova-network creates an invalid entry in the dnsmasq .opts file for the network that contains a blank router option. New instances will not receive a default gateway. Change-Id: I4c2da61def0681b7b253ae387bf83c069484e28b Fixes: bug #1075859 (cherry picked from commit 1b455923446de6fcfee7166059db72b80ff51dfe) ** Changed in: nova/essex Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1075859 Title: use_single_default_gateway does not function correctly To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1075859/+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 1084261] Re: 'nova-manage project quota' command fails with 'nova-manage: error: no such option: --project'
Reviewed: https://review.openstack.org/17603 Committed: http://github.com/openstack/nova/commit/963fcdb6738cc2eb59aaa4edec5d8541fef4c9e4 Submitter: Jenkins Branch:master commit 963fcdb6738cc2eb59aaa4edec5d8541fef4c9e4 Author: Andrew Glen-Young Date: Thu Dec 6 10:22:35 2012 -0500 Fix regression allowing quotas to be applied to projects. Change-Id: I9c7dfa7664badcafb800c02ee608699e56b344ab Fixes: bug #1084261 ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1084261 Title: 'nova-manage project quota' command fails with 'nova-manage: error: no such option: --project' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1084261/+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 1084261] Re: 'nova-manage project quota' command fails with 'nova-manage: error: no such option: --project'
Fix proposed to branch: master Review: https://review.openstack.org/17603 ** Changed in: nova Status: Confirmed => In Progress ** Changed in: nova Assignee: (unassigned) => Andrew Glen-Young (aglenyoung) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1084261 Title: 'nova-manage project quota' command fails with 'nova-manage: error: no such option: --project' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1084261/+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 1081836] Fix proposed to nova (stable/folsom)
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/16773 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1081836 Title: nova-compute (folsom) fails to start, compute_driver is None To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1081836/+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 1081836] Re: nova-compute (folsom) fails to start, compute_driver is None
Reviewed: https://review.openstack.org/16711 Committed: http://github.com/openstack/nova/commit/7e8a1662577bc86e873f9f957e74076ac89eb80b Submitter: Jenkins Branch:stable/folsom commit 7e8a1662577bc86e873f9f957e74076ac89eb80b Author: Adam Gandelman Date: Wed Nov 21 16:13:29 2012 -0800 Reinstate default FLAGS.compute_driver for folsom A previous cherry-picked commit moved the compute_driver flag from the compute manager to the global flags file, but did not take the flags default value along. This breaks existing Folsom installations that still use connection_type. Note, this is only proposed to stable/folsom to fix a regression. Not applicable to master as connection_type is gone in Grizzly. Fixes bug 1081836. Change-Id: I135d6adc215c40fb9f46f382dbe22fb38b413ff8 ** Changed in: nova/folsom Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1081836 Title: nova-compute (folsom) fails to start, compute_driver is None To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1081836/+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 1061665] Re: Filter scheduler not respecting the force_hosts hint
Reviewed: https://review.openstack.org/15983 Committed: http://github.com/openstack/openstack-manuals/commit/3faca61ce3c20aea60d900afaaf9a9c7a19342d6 Submitter: Jenkins Branch:master commit 3faca61ce3c20aea60d900afaaf9a9c7a19342d6 Author: atul jha Date: Tue Nov 13 21:10:11 2012 +0530 Fix bug 1061665, --force_hosts hint for launching instance updates --force_hosts no longer available in Folsom, have to indicate an availability zone instead. Patchset attempts to explain how to get the availability zone name that you want. Please review. Patchset addresses comments about zone versus host, adding new section rather than replacing host section completely. Change-Id: Ifea0df3dc950c165718fa160bc08f1b1487c3f82 ** Changed in: openstack-manuals Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1061665 Title: Filter scheduler not respecting the force_hosts hint To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1061665/+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 1031119] Re: nova: proxy floating ip calls to quantum
Reviewed: https://review.openstack.org/16193 Committed: http://github.com/openstack/nova/commit/3f7788ca4310a7fa34b7687ff6e41f8de4d2cadc Submitter: Jenkins Branch:stable/folsom commit 3f7788ca4310a7fa34b7687ff6e41f8de4d2cadc Author: Akihiro MOTOKI Date: Thu Sep 13 21:22:33 2012 +0900 Proxy floating IP calls to quantum Fixes bug 1023169. Also fixes bug 1031119. In Folsom, floating IP support is moved to Quantum. By this commit floating IP calls to nova are proxied to Quantum and nova command can be used to manage floating IPs. pip-requires is also updated and now requires python-quantumclient >=2.1 which supports floating IP feature in Quantum. Change-Id: I2c32948a8fe291601216dc62d546da64a8fb8428 (cherry picked from commit 7948b7a572e33e3fd541e27f2617d832eb43b504) ** Tags added: in-stable-folsom -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1031119 Title: nova: proxy floating ip calls to quantum To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1031119/+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 1031119] Fix proposed to nova (stable/folsom)
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/16193 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1031119 Title: nova: proxy floating ip calls to quantum To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1031119/+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 1065702] Fix merged to nova (stable/folsom)
Reviewed: https://review.openstack.org/15005 Committed: http://github.com/openstack/nova/commit/e3d7f8c7de9bad73bf1f9b5ee9b2cf46eb452351 Submitter: Jenkins Branch:stable/folsom commit e3d7f8c7de9bad73bf1f9b5ee9b2cf46eb452351 Author: John Griffith Date: Mon Oct 29 17:57:40 2012 -0600 Detect and fix issues caused by vol ID migration The migration from volume ID to UUID neglected to update the provider_location field on the volume. As a result the iqn and volume name no long match and existing volumes are no longer able to be attached after an upgrade (essex -> folsom and then nova-vol->cinder). This patch adds a method to the volume driver that will check for the mismatch of volume name in the iqn during service start up. If detected it will update the provider_location field in the database to include the new ID. Also it will create a symlink to the device backing file that also has the correct naming convention. Note: We don't disturb an connections that are currently attached. For this case we add a check in manager.detach and do any provider_location cleanup that's needed at that time. This ensures that connections persist on restarts of tgtd and reboot. Change-Id: Ib41ebdc849ebc31a9225bdc4902209c5a23da104 Fixes: bug 1065702 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+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 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
Reviewed: https://review.openstack.org/15157 Committed: http://github.com/openstack/cinder/commit/7f34ba39abcaa4f885d7448b427148fab4e49892 Submitter: Jenkins Branch:stable/folsom commit 7f34ba39abcaa4f885d7448b427148fab4e49892 Author: John Griffith Date: Wed Oct 31 16:43:09 2012 -0600 Detect and fix issues caused by vol ID migration The migration from volume ID to UUID neglected to update the provider_location field on the volume. As a result the iqn and volume name no long match and existing volumes are no longer able to be attached after an upgrade (essex -> folsom and then nova-vol->cinder). This patch adds a method to the volume driver that will check for the mismatch of volume name in the iqn during service start up. If detected it will update the provider_location field in the database to include the new ID. Also it will create a symlink to the device backing file that also has the correct naming convention. Note: We don't disturb an connections that are currently attached. For this case we add a check in manager.detach and do any provider_location cleanup that's needed at that time. This ensures that connections persist on restarts of tgtd and reboot. Change-Id: I4683df4ef489972752dc58cb4e91d458a79a8ef2 Fixes: bug 1065702enter the commit message for your changes. Lines starting ** Tags added: in-stable-folsom -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+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 1065702] Fix proposed to cinder (stable/folsom)
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/15157 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+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 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
Reviewed: https://review.openstack.org/14790 Committed: http://github.com/openstack/cinder/commit/524c7fa6dfade6efcabda19b105d58cab8c434e2 Submitter: Jenkins Branch:master commit 524c7fa6dfade6efcabda19b105d58cab8c434e2 Author: John Griffith Date: Wed Oct 24 16:28:02 2012 -0600 Detect and fix issues caused by vol ID migration The migration from volume ID to UUID neglected to update the provider_location field on the volume. As a result the iqn and volume name no long match and existing volumes are no longer able to be attached after an upgrade (essex -> folsom and then nova-vol->cinder). This patch adds a method to the volume driver that will check for the mismatch of volume name in the iqn during service start up. If detected it will update the provider_location field in the database to include the new ID. Also it will create a symlink to the device backing file that also has the correct naming convention. Note: We don't disturb an connections that are currently attached. For this case we add a check in manager.detach and do any provider_location cleanup that's needed at that time. This ensures that connections persist on restarts of tgtd and reboot. Change-Id: I8224824b793c98a9767c5d8dd741d892be720c4f Fixes: bug 1065702 ** Changed in: cinder Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+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 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
Reviewed: https://review.openstack.org/14368 Committed: http://github.com/openstack/nova/commit/86a59376c6d4d2ec5a05c8b63a419d0374e9d9c9 Submitter: Jenkins Branch:stable/essex commit 86a59376c6d4d2ec5a05c8b63a419d0374e9d9c9 Author: Michael Still Date: Thu Oct 11 15:46:11 2012 +1100 Avoid RPC calls while holding iptables lock. This exhibitied itself as very slow instance starts on a Canonical test cluster. This was because do_referesh_security_group_rules() was making rpc calls while holding the iptables lock. This refactor avoids that while making no functional changes (I hope). Fixes bug: 1062314 Change-Id: I36f805bd72f7bd06082cfe96c58d637203bcffb7 Cherry-picked: ba585524e32965697c1a44c8fd743dea060bb1af Conflicts: nova/virt/firewall.py ** Changed in: nova/essex Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+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 1065702] Fix proposed to nova (stable/folsom)
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/15005 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+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 1065702] Fix proposed to cinder (master)
Fix proposed to branch: master Review: https://review.openstack.org/14790 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+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 1065785] Re: volume and snapshot IDs do not correctly map to UUIDs after folsom upgrade
Reviewed: https://review.openstack.org/14416 Committed: http://github.com/openstack/nova/commit/32d8722d3bf86946a56afc74b9cc301a39a2bef1 Submitter: Jenkins Branch:stable/folsom commit 32d8722d3bf86946a56afc74b9cc301a39a2bef1 Author: Adam Gandelman Date: Thu Oct 11 18:49:54 2012 -0700 read_deleted snapshot and volume id mappings. Since the migration that creates the volume_id_mappings and snapshot_id_mappings tables does not populate the 'deleted' column, queries to this table should not limit results to 'deleted=0'. Limiting to non-deleted rows results in duplicate mappings being created for existing instance mappings after an upgrade, and throws off volume and snapshot ID to UUID mapping. This is a stop-gap measure to ensure avoid serious breakage during an upgrade. The NULL columns in this table are actually unused currently and can be populated in later grizzly migrations, if they end up being used. Fixes bug 1065785. Change-Id: I893c994362a203288b9984f0ede24cbb274bfcc5 (cherry picked from commit 43bf8344488a6af1046344c255bdb2edd7450475) ** Changed in: nova/folsom Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065785 Title: volume and snapshot IDs do not correctly map to UUIDs after folsom upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1065785/+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 1062277] Re: 092_add_instance_system_metadata migration fails when upgrading
Fix proposed to branch: master Review: https://review.openstack.org/14617 ** Changed in: nova Status: Confirmed => In Progress ** Changed in: nova Assignee: (unassigned) => Sam Morrison (sorrison) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062277 Title: 092_add_instance_system_metadata migration fails when upgrading To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062277/+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 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
Fix proposed to branch: master Review: https://review.openstack.org/14615 ** Changed in: nova Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+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 1065883] Re: ceph rbd username and secret should be configured in nova-compute, not passed from nova-volume/cinder
Reviewed: https://review.openstack.org/14458 Committed: http://github.com/openstack/nova/commit/af51b46b1e08b26c07bd32019e54b9c521cb7813 Submitter: Jenkins Branch:master commit af51b46b1e08b26c07bd32019e54b9c521cb7813 Author: James Page Date: Mon Oct 15 13:21:55 2012 +0100 Allow local rbd user and secret_uuid configuration By default, the rbd_user and rbd_secret_uuid are specified in the nova-volume/cinder configuration and passed to nova-compute when volumes are attached to instances. This change allows these values to be specified locally in nova-compute which means access control to RADOS devices in ceph can be managed independently from nova-volume/cinder with no requirement for consistent uuid's for libvirt secrets. Fixes bug 1065883. Change-Id: I9f07d040ae267bfbe8f794a5d22d327106314cc6 ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065883 Title: ceph rbd username and secret should be configured in nova-compute, not passed from nova-volume/cinder To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065883/+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 1064835] Re: keystoneclient fails on SSL certificates that work for other services
Fix proposed to branch: master Review: https://review.openstack.org/14572 ** Changed in: python-keystoneclient Status: Confirmed => In Progress ** Changed in: python-keystoneclient Assignee: (unassigned) => Sam Morrison (sorrison) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1064835 Title: keystoneclient fails on SSL certificates that work for other services To manage notifications about this bug go to: https://bugs.launchpad.net/python-keystoneclient/+bug/1064835/+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 1065785] Fix proposed to nova (stable/folsom)
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/14416 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065785 Title: volume and snapshot IDs do not correctly map to UUIDs after folsom upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1065785/+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 1065785] Re: volume and snapshot IDs do not correctly map to UUIDs after folsom upgrade
Reviewed: https://review.openstack.org/14372 Committed: http://github.com/openstack/nova/commit/43bf8344488a6af1046344c255bdb2edd7450475 Submitter: Jenkins Branch:master commit 43bf8344488a6af1046344c255bdb2edd7450475 Author: Adam Gandelman Date: Thu Oct 11 18:49:54 2012 -0700 read_deleted snapshot and volume id mappings. Since the migration that creates the volume_id_mappings and snapshot_id_mappings tables does not populate the 'deleted' column, queries to this table should not limit results to 'deleted=0'. Limiting to non-deleted rows results in duplicate mappings being created for existing instance mappings after an upgrade, and throws off volume and snapshot ID to UUID mapping. This is a stop-gap measure to ensure avoid serious breakage during an upgrade. The NULL columns in this table are actually unused currently and can be populated in later grizzly migrations, if they end up being used. Fixes bug 1065785. Change-Id: I893c994362a203288b9984f0ede24cbb274bfcc5 ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065785 Title: volume and snapshot IDs do not correctly map to UUIDs after folsom upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1065785/+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 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
Reviewed: https://review.openstack.org/14367 Committed: http://github.com/openstack/nova/commit/eee4dbb07e88e19ca891275f5ba1d381bd98b4e5 Submitter: Jenkins Branch:stable/folsom commit eee4dbb07e88e19ca891275f5ba1d381bd98b4e5 Author: Michael Still Date: Thu Oct 11 15:46:11 2012 +1100 Avoid RPC calls while holding iptables lock. This exhibitied itself as very slow instance starts on a Canonical test cluster. This was because do_referesh_security_group_rules() was making rpc calls while holding the iptables lock. This refactor avoids that while making no functional changes (I hope). Fixes bug: 1062314 Change-Id: I36f805bd72f7bd06082cfe96c58d637203bcffb7 Cherry-picked: ba585524e32965697c1a44c8fd743dea060bb1af ** Changed in: nova/folsom Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+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 1065785] Re: volume and snapshot IDs do not correctly map to UUIDs after folsom upgrade
Fix proposed to branch: master Review: https://review.openstack.org/14372 ** Changed in: nova Status: New => In Progress ** Changed in: nova Assignee: (unassigned) => Adam Gandelman (gandelman-a) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065785 Title: volume and snapshot IDs do not correctly map to UUIDs after folsom upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1065785/+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 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
Fix proposed to branch: stable/essex Review: https://review.openstack.org/14368 ** Changed in: nova/essex Status: New => In Progress ** Changed in: nova/essex Assignee: (unassigned) => Pádraig Brady (p-draigbrady) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+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 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/14367 ** Changed in: nova/folsom Status: New => In Progress ** Changed in: nova/folsom Assignee: (unassigned) => Pádraig Brady (p-draigbrady) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+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 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
Reviewed: https://review.openstack.org/14326 Committed: http://github.com/openstack/nova/commit/ba585524e32965697c1a44c8fd743dea060bb1af Submitter: Jenkins Branch:master commit ba585524e32965697c1a44c8fd743dea060bb1af Author: Michael Still Date: Thu Oct 11 15:46:11 2012 +1100 Avoid RPC calls while holding iptables lock. This exhibitied itself as very slow instance starts on a Canonical test cluster. This was because do_referesh_security_group_rules() was making rpc calls while holding the iptables lock. This refactor avoids that while making no functional changes (I hope). This should resolve bug 1062314. Change-Id: I36f805bd72f7bd06082cfe96c58d637203bcffb7 ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+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 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
Fix proposed to branch: master Review: https://review.openstack.org/14326 ** Changed in: nova Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+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 1061166] Re: ec2 instance IDs are broken after folsom upgrade
Reviewed: https://review.openstack.org/14240 Committed: http://github.com/openstack/nova/commit/b7e509af5d8bc3f9e26dea5cf5121c0f62348dc0 Submitter: Jenkins Branch:stable/folsom commit b7e509af5d8bc3f9e26dea5cf5121c0f62348dc0 Author: Adam Gandelman Date: Thu Oct 4 14:10:32 2012 -0700 Set read_deleted='yes' for instance_id_mappings. Since the migration that creates the instance_id_mappings does not populated the 'deleted' column, queries to this table should not limit results to 'deleted=0'. Limiting to non-deleted rows results in duplicate mappings being created for existing instance mappings after an upgrade, and throws off the entire EC2 instance ID to UUID mapping. Fixes LP: #1061166 Change-Id: I8893954fcae94a71dcc284c1b3b23b53901437eb (cherry picked from commit 1d0402cf65458c941639f01334a996c11e592018) ** Tags added: in-stable-folsom -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1061166 Title: ec2 instance IDs are broken after folsom upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1061166/+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 1061166] Fix proposed to nova (stable/folsom)
Fix proposed to branch: stable/folsom Review: https://review.openstack.org/14240 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1061166 Title: ec2 instance IDs are broken after folsom upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1061166/+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 925609] Re: install throws errors about SADeprecationWarning
** Changed in: glance Status: Fix Released => In Progress ** Changed in: glance Assignee: Chuck Short (zulcss) => David Ripton (dripton) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/925609 Title: install throws errors about SADeprecationWarning To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/925609/+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 1061166] Re: ec2 instance IDs are broken after folsom upgrade
Reviewed: https://review.openstack.org/14063 Committed: http://github.com/openstack/nova/commit/1d0402cf65458c941639f01334a996c11e592018 Submitter: Jenkins Branch:master commit 1d0402cf65458c941639f01334a996c11e592018 Author: Adam Gandelman Date: Thu Oct 4 14:10:32 2012 -0700 Set read_deleted='yes' for instance_id_mappings. Since the migration that creates the instance_id_mappings does not populated the 'deleted' column, queries to this table should not limit results to 'deleted=0'. Limiting to non-deleted rows results in duplicate mappings being created for existing instance mappings after an upgrade, and throws off the entire EC2 instance ID to UUID mapping. Fixes LP: #1061166 Change-Id: I8893954fcae94a71dcc284c1b3b23b53901437eb ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1061166 Title: ec2 instance IDs are broken after folsom upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1061166/+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 1061166] Re: ec2 instance IDs are broken after folsom upgrade
Fix proposed to branch: master Review: https://review.openstack.org/14063 ** Changed in: nova Status: New => In Progress ** Changed in: nova Assignee: (unassigned) => Adam Gandelman (gandelman-a) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1061166 Title: ec2 instance IDs are broken after folsom upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1061166/+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 1052522] Re: L3 plugin exists / dies when external bridge isn't up
Reviewed: https://review.openstack.org/13457 Committed: http://github.com/openstack/quantum/commit/1aa2ac5d791cb1d0738f7a61ea6fd50721bec8a8 Submitter: Jenkins Branch:milestone-proposed commit 1aa2ac5d791cb1d0738f7a61ea6fd50721bec8a8 Author: Dan Wendlandt Date: Thu Sep 20 23:52:52 2012 -0700 l3-agent: move check if ext-net bridge exists within daemon loop bug 1052522 the l3 agent checked if the external network bridge exists in its constructor, raising an uncaught exception if it did not. this does not make much sense when running the l3-agent as a deamon, especially since it can be the case that the l3-agent starts before open vswitch. Change-Id: Ie1717b2c02c9f0bc0caf34a6fdb0dc3a930123c0 ** Changed in: quantum Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to quantum in Ubuntu. https://bugs.launchpad.net/bugs/1052522 Title: L3 plugin exists / dies when external bridge isn't up To manage notifications about this bug go to: https://bugs.launchpad.net/quantum/+bug/1052522/+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 833499] Re: virt/disk.py unconditionally inserts public_keys into /root/.ssh/authorized_keys
Fix proposed to branch: master Review: https://review.openstack.org/12455 ** Changed in: nova Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/833499 Title: virt/disk.py unconditionally inserts public_keys into /root/.ssh/authorized_keys To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/833499/+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 1032405] Re: RBDDriver does not support volume creation from snapshots
Fix proposed to branch: master Review: https://review.openstack.org/12192 ** Changed in: nova Status: New => In Progress ** Changed in: nova Assignee: (unassigned) => Chuck Short (zulcss) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1032405 Title: RBDDriver does not support volume creation from snapshots To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1032405/+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 1035428] Re: authenticate in ldap backend doesn't return a list of roles
Reviewed: https://review.openstack.org/11776 Committed: http://github.com/openstack/keystone/commit/af52ef1479861ffdf3aa3a334fc9fffc8faa8843 Submitter: Jenkins Branch:master commit af52ef1479861ffdf3aa3a334fc9fffc8faa8843 Author: Andrew Bogott Date: Tue Aug 21 17:52:58 2012 -0500 Demonstrate that authenticate() returns roles. This is related to lp 1035428; that bug is fixed in folsom, but this test is also about to appear in stable/essex. Change-Id: Iadd4091339aab2c3a8d474b44dcd11f8bfd1d510 ** Changed in: keystone Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1035428 Title: authenticate in ldap backend doesn't return a list of roles To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1035428/+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 1001088] Fix proposed to nova (stable/essex)
Fix proposed to branch: stable/essex Review: https://review.openstack.org/11303 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1001088 Title: iSCSI targets are not restored following a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1001088/+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 1011640] Re: network configuration is not restored after host reboot
Reviewed: https://review.openstack.org/10607 Committed: http://github.com/openstack/nova/commit/eab5851b0b55c4230cc11460f9efc6b617ae2e68 Submitter: Jenkins Branch:master commit eab5851b0b55c4230cc11460f9efc6b617ae2e68 Author: Chuck Short Date: Tue Jul 31 11:49:58 2012 -0400 Add check exit codes for vlans Add check_exit_code to check the ip address creation in ensure_vlan. Ignores error code '2' and '0' and '254' from iproute2, which means the address has been added or removed. A further audit of return codes will come later. LP: #1011640 Change-Id: Ie95b106446c9f136fa079d95df7a14fe50046696 Signed-off-by: Chuck Short ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1011640 Title: network configuration is not restored after host reboot To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1011640/+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 1011640] Re: network configuration is not restored after host reboot
Fix proposed to branch: master Review: https://review.openstack.org/10607 ** Changed in: nova Status: New => In Progress ** Changed in: nova Assignee: (unassigned) => Chuck Short (zulcss) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1011640 Title: network configuration is not restored after host reboot To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1011640/+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 1014925] Re: API 'v1.1/{tenant_id}/os-hosts' does not return a list of hosts
Reviewed: https://review.openstack.org/10168
Committed:
http://github.com/openstack/nova/commit/08e5128ffd63acd14249db3930f05753abb8f848
Submitter: Jenkins
Branch:stable/essex
commit 08e5128ffd63acd14249db3930f05753abb8f848
Author: Adam Gandelman
Date: Mon Jul 23 13:16:46 2012 -0700
Backport fix for API listing of os-hosts.
Backports fix for bug 1014925 to stable/essex, which resolves issue
where querying /v1.1/$tenant/os-hosts returns an empty list.
Original fix by Joe Gordon reviewed into Folsom at:
https://review.openstack.org/#/c/8682/2
Change-Id: I44ac2e519b7af9b8f3b37a42280ac6fe71c31a1c
** Changed in: nova/essex
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1014925
Title:
API 'v1.1/{tenant_id}/os-hosts' does not return a list of hosts
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1014925/+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 1002111] Re: iptables being run on a nova-api server
Reviewed: https://review.openstack.org/10222
Committed:
http://github.com/openstack/nova/commit/6c888001f15fba44af367757dd81b8512f65
Submitter: Jenkins
Branch:master
commit 6c888001f15fba44af367757dd81b8512f65
Author: Thierry Carrez
Date: Tue Jul 24 17:03:13 2012 +0200
Provide rootwrap filters for nova-api-metadata
The metadata service in nova-api needs access to
ip[6]tables-{save-restore} to accept connections to the
metadata service. This change adds an api-metadata.filters file
that needs to be deployed on setups running nova-api-metadata
or nova-api with "metadata" in enabled_apis.
Fixes bug 1002111.
Change-Id: I5aecb223876e12550394f31dbc7df893868baa8b
** Changed in: nova
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1002111
Title:
iptables being run on a nova-api server
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1002111/+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 1021810] Re: `nova-manage fixed list` fails if network has been deleted
Reviewed: https://review.openstack.org/9967 Committed: http://github.com/openstack/nova/commit/458a5d61eac5eb5cef34ab301b67fa37271ba407 Submitter: Jenkins Branch:master commit 458a5d61eac5eb5cef34ab301b67fa37271ba407 Author: Tong Li Date: Wed Jul 18 11:26:12 2012 -0400 fixes for nova-manage network list if network has been deleted this fix addresses the bug #1021810 Currently command 'nova-manage network list' or 'nova-manage fixed list' will return 'Command failed.' message when there is no network defined or networks get deleted. This fix combined with fixes to bug 1025827 will fix both command problem. also change the print out message so that it can be translated. code structure changes according to the suggestion from comments. Change-Id: Id9a1a10217aac971cbbba9db5829c8478892db1a ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1021810 Title: `nova-manage fixed list` fails if network has been deleted To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1021810/+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 1021810] Re: `nova-manage fixed list` fails if network has been deleted
Fix proposed to branch: master Review: https://review.openstack.org/9967 ** Changed in: nova Status: Confirmed => In Progress ** Changed in: nova Assignee: (unassigned) => Tong Li (litong01) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1021810 Title: `nova-manage fixed list` fails if network has been deleted To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1021810/+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 1009974] Re: "nova live-migration" fails silently
Reviewed: https://review.openstack.org/9179 Committed: http://github.com/openstack/openstack-manuals/commit/da29b30ead43a3b53d8092f63f3b2aaa5761d32a Submitter: Jenkins Branch:stable/essex commit da29b30ead43a3b53d8092f63f3b2aaa5761d32a Author: Lorin Hochstein Date: Mon Jun 25 09:16:38 2012 -0400 Documents vncserver_listen flag when used with live migrations Live migration breaks if vncserver_listen is set to a specific host IP address. Documentation based on this comment from the openstack-operators mailing list: http://lists.openstack.org/pipermail/openstack-operators/2012-June/000965.html See also comments in bug 1009974. Cherry picked from https://review.openstack.org/8923 Change-Id: I21b1d3eb5380effda3e2bfcd4f3ea15ea43f096a ** Tags added: in-stable-essex -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1009974 Title: "nova live-migration" fails silently To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1009974/+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 1009974] Fix proposed to openstack-manuals (stable/essex)
Fix proposed to branch: stable/essex Review: https://review.openstack.org/9179 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1009974 Title: "nova live-migration" fails silently To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1009974/+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 1009974] Fix merged to openstack-manuals (master)
Reviewed: https://review.openstack.org/8923 Committed: http://github.com/openstack/openstack-manuals/commit/306347d87079ae656a91b36c281a03125712e960 Submitter: Jenkins Branch:master commit 306347d87079ae656a91b36c281a03125712e960 Author: Lorin Hochstein Date: Mon Jun 25 09:16:38 2012 -0400 Documents vncserver_listen flag when used with live migrations Live migration breaks if vncserver_listen is set to a specific host IP address. Documentation based on this comment from the openstack-operators mailing list: http://lists.openstack.org/pipermail/openstack-operators/2012-June/000965.html See also comments in bug 1009974. Change-Id: I21b1d3eb5380effda3e2bfcd4f3ea15ea43f096a -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1009974 Title: "nova live-migration" fails silently To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1009974/+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 1013782] Re: Stop/start a KVM instance with volumes attached produces an error state
Reviewed: https://review.openstack.org/8950 Committed: http://github.com/openstack/nova/commit/33c2575ebf9c8022521d36f51b9b31cd41f7f74f Submitter: Jenkins Branch:stable/essex commit 33c2575ebf9c8022521d36f51b9b31cd41f7f74f Author: Vishvananda Ishaya Date: Thu Jun 21 13:25:57 2012 -0700 Call libvirt_volume_driver with right mountpoint * fixes bug 1013782 * fixes tests for live migration * removed test which doesn't apply (cherry picked from commit 96c86336c69b9d456e43234e3fe315bd3b101045) Change-Id: I8f95c6baa7aad878af19d5d8b8b34531a4a43885 ** Changed in: nova/essex Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1013782 Title: Stop/start a KVM instance with volumes attached produces an error state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1013782/+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 1013782] Re: Stop/start a KVM instance with volumes attached produces an error state
Fix proposed to branch: stable/essex Review: https://review.openstack.org/8953 ** Changed in: nova/essex Assignee: Vish Ishaya (vishvananda) => Dave Walker (davewalker) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1013782 Title: Stop/start a KVM instance with volumes attached produces an error state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1013782/+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 1013782] Fix merged to nova (master)
Reviewed: https://review.openstack.org/8823 Committed: http://github.com/openstack/nova/commit/96c86336c69b9d456e43234e3fe315bd3b101045 Submitter: Jenkins Branch:master commit 96c86336c69b9d456e43234e3fe315bd3b101045 Author: Vishvananda Ishaya Date: Thu Jun 21 13:25:57 2012 -0700 Call libvirt_volume_driver with right mountpoint * fixes bug 1013782 * includes failing test * fixes tests for live migration Change-Id: I8f95c6baa7aad878af19d5d8b8b34531a4a43885 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1013782 Title: Stop/start a KVM instance with volumes attached produces an error state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1013782/+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 1013782] Re: Stop/start a KVM instance with volumes attached produces an error state
Fix proposed to branch: stable/essex Review: https://review.openstack.org/8950 ** Changed in: nova/essex Status: New => In Progress ** Changed in: nova/essex Assignee: (unassigned) => Vish Ishaya (vishvananda) ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1013782 Title: Stop/start a KVM instance with volumes attached produces an error state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1013782/+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 1016111] Re: Passing an incorrect zone name to euca-create-volume results in a volume stuck in the "creating" state
Fix proposed to branch: master Review: https://review.openstack.org/8875 ** Changed in: nova Status: New => In Progress ** Changed in: nova Assignee: (unassigned) => Chuck Short (zulcss) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1016111 Title: Passing an incorrect zone name to euca-create-volume results in a volume stuck in the "creating" state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1016111/+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 1013782] Re: Stop/start a KVM instance with volumes attached produces an error state
Fix proposed to branch: master Review: https://review.openstack.org/8823 ** Changed in: nova Status: Confirmed => In Progress ** Changed in: nova Assignee: (unassigned) => Vish Ishaya (vishvananda) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1013782 Title: Stop/start a KVM instance with volumes attached produces an error state To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1013782/+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 939122] Re: floating ips do not display in 'nova list' after association to instance
Reviewed: https://review.openstack.org/8581 Committed: http://github.com/openstack/nova/commit/caae0e9ca3abaad1d17d995f66195ea62fe2e59a Submitter: Jenkins Branch:stable/essex commit caae0e9ca3abaad1d17d995f66195ea62fe2e59a Author: deevi rani Date: Thu May 3 06:42:47 2012 -0400 Updates the cache fixes bug 939122 Following are the changes done: 1. in compute/api.py to display the floating ip in nova list command upon its association with an instance. 2. in network/api.py to solve the similar issue upon the floating ip disassocaition Updated version of: https://review.openstack.org/#/c/7059 Change-Id: Ief1a3f544c3d14bd61cc0814612df3ee521ddec2 (cherry picked from commit 7097e01a15ecd5c28b6b771e5043f18da243607e) ** Changed in: nova/essex Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/939122 Title: floating ips do not display in 'nova list' after association to instance To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/939122/+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 939122] Re: floating ips do not display in 'nova list' after association to instance
Fix proposed to branch: stable/essex Review: https://review.openstack.org/8581 ** Changed in: nova/essex Status: New => In Progress ** Changed in: nova/essex Assignee: (unassigned) => Vish Ishaya (vishvananda) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/939122 Title: floating ips do not display in 'nova list' after association to instance To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/939122/+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 939122] Re: floating ips do not display in 'nova list' after association to instance
Reviewed: https://review.openstack.org/8571 Committed: http://github.com/openstack/nova/commit/7097e01a15ecd5c28b6b771e5043f18da243607e Submitter: Jenkins Branch:master commit 7097e01a15ecd5c28b6b771e5043f18da243607e Author: deevi rani Date: Thu May 3 06:42:47 2012 -0400 Updates the cache fixes bug 939122 Following are the changes done: 1. in compute/api.py to display the floating ip in nova list command upon its association with an instance. 2. in network/api.py to solve the similar issue upon the floating ip disassocaition Updated version of: https://review.openstack.org/#/c/7059 Change-Id: Ief1a3f544c3d14bd61cc0814612df3ee521ddec2 ** Changed in: nova Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/939122 Title: floating ips do not display in 'nova list' after association to instance To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/939122/+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 939122] Re: floating ips do not display in 'nova list' after association to instance
Fix proposed to branch: master Review: https://review.openstack.org/8571 ** Changed in: nova Assignee: D LALITHA RANI (deevi-rani) => Vish Ishaya (vishvananda) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/939122 Title: floating ips do not display in 'nova list' after association to instance To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/939122/+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 1009974] Re: "nova live-migration" fails silently
Reviewed: https://review.openstack.org/8383 Committed: http://github.com/openstack/openstack-manuals/commit/e5e6e85ccef04063c275b4fd420ebb4477325bb5 Submitter: Jenkins Branch:master commit e5e6e85ccef04063c275b4fd420ebb4477325bb5 Author: Florian Haas Date: Sun Jun 10 22:32:43 2012 +0200 Remove double quotes from nova.conf options reference Using double quotes in nova.conf can seriously mess up Nova in all sorts of ways. Remove their erroneous use from the config documentation, and also emphasize that using them is a bad idea. bug 1009974 Change-Id: I6b8423739ce19e7dd9ab426ea70bc8c330b2455a ** Changed in: openstack-manuals Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1009974 Title: "nova live-migration" fails silently To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1009974/+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 998137] Re: Keystone user tenant membership not always removed
Reviewed: https://review.openstack.org/8403 Committed: http://github.com/openstack/keystone/commit/d0a73669369d86ff4c7b9de715fa4eec9bc58b59 Submitter: Jenkins Branch:stable/essex commit d0a73669369d86ff4c7b9de715fa4eec9bc58b59 Author: Adam Gandelman Date: Mon Jun 11 10:35:16 2012 -0700 Flush tenant membership deletion before user Ensure user tenant membership is *actually* removed before deleting user. Applied to 'stable/essex', originally committed to trunk via https://review.openstack.org/#/c/7353/ Fixes bug 998137. Change-Id: Ib52970d68f288b8742c3e060c7040838a1c738c2 ** Tags added: in-stable-essex -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/998137 Title: Keystone user tenant membership not always removed To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/998137/+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 998137] Fix proposed to keystone (stable/essex)
Fix proposed to branch: stable/essex Review: https://review.openstack.org/8403 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/998137 Title: Keystone user tenant membership not always removed To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/998137/+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 998137] Re: Keystone user tenant membership not always removed
Reviewed: https://review.openstack.org/7353 Committed: http://github.com/openstack/keystone/commit/2e912f4b91b57c060c2363c067125276a92457d2 Submitter: Jenkins Branch:master commit 2e912f4b91b57c060c2363c067125276a92457d2 Author: Adam Gandelman Date: Fri May 11 09:49:39 2012 -0700 Flush tenant membership deletion before user Ensure user tenant membership is *actually* removed before deleting user. Fixes bug 998137. This should be proposed to stable/essex as well. Change-Id: I097456e603177646d62ebf08ca71af1fd7f787bf ** Changed in: keystone Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/998137 Title: Keystone user tenant membership not always removed To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/998137/+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 998137] Fix proposed to keystone (master)
Fix proposed to branch: master Review: https://review.openstack.org/7353 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/998137 Title: Keystone user tenant membership not always removed To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/998137/+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 977765] Re: Image registration (ec2) is broken using deprecated auth
Reviewed: https://review.openstack.org/6431 Committed: http://github.com/openstack/nova/commit/6e988ed75c5ba507d79818bc24a1bd2f8250ce2b Submitter: Jenkins Branch:stable/essex commit 6e988ed75c5ba507d79818bc24a1bd2f8250ce2b Author: Adam Gandelman Date: Tue Apr 10 16:44:27 2012 -0700 Populate image properties with project_id again This allows ec2 image publishing to function on Essex for users who are still using deprecated auth. This isn't targetted toward master and is proposed to stable/essex for the sake of aiding users transition to Keystone during upgrades from diablo + deprecated_auth. Fixes bug 977765 Change-Id: I809b669e88fe25234569d0c744d14aff6bbd4713 ** Tags added: in-stable-essex -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/977765 Title: Image registration (ec2) is broken using deprecated auth To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/977765/+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 977765] Fix proposed to nova (stable/essex)
Fix proposed to branch: stable/essex Review: https://review.openstack.org/6431 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/977765 Title: Image registration (ec2) is broken using deprecated auth To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/977765/+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
