{"push_id":787189594,"size":24,"distinct_size":24,"ref":"refs/heads/nectar/kilo","head":"4c3ea469351c40e8e68d80878b17594d04a130ab","before":"26267dcbf70df4f32e0f5872162369da955fdc9b","commits":[{"sha":"cbf73b8de90157f4a5ed2a6ba8abc0b4be1b6022","author":{"email":"659efd8267cf72fa6ad236bde4468b8debfc1007@gmail.com","name":"Sam Morrison"},"message":"Revert \"Don't check flavor disk size when booting from volume\"\n\nThis reverts commit 85ca946e836f5349911667cea2652297d7c21c06.\n\nChange-Id: I37698ef863f51c3e4498bc7536ce1b563868df81","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/cbf73b8de90157f4a5ed2a6ba8abc0b4be1b6022"},{"sha":"799a6f4c1d446e81828115bfc11f937b9b5e6ed5","author":{"email":"17a59e873133af25bef9d8a9fdaa6c3a6b7eebd2@nectechnologies.in","name":"ghanshyam"},"message":"Kilo-Removing extension \"OS-EXT-VIF-NET\" from v2.1 ext list\n\nExtension \"OS-EXT-VIF-NET\" is not ported to v2.1, due to that\nthere is difference between v2 and v2.1 as mentioned in bug#1470690.\n\nBut v2.1 extension-list has \"OS-EXT-VIF-NET\" extension which convey that\nthis extension is also loaded for v2.1 and user will get the expected response\naccording to \"OS-EXT-VIF-NET\" extension which is not true as this extension\nis not actually ported to v2.1.\n\nIt is decided that fix for that difference should go in microversion not\nin base v2.1 as it is already released.\n\nThis patch remove extension \"OS-EXT-VIF-NET\" from v2.1 extension-list which\nwill actually convey that this extension is missing in v2.1.\n\nThis is back-porting Ic99ac1179d02d907422911fe1369b64479fd5f33 in Kilo stable\nbranch.\n\nPartial-Bug: 1470690\n\nChange-Id: Ic590bb5df2b2df917af9ce9941da6afba4e382a5","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/799a6f4c1d446e81828115bfc11f937b9b5e6ed5"},{"sha":"7f0ca80ff2d10ad2bb03bab955945b5fc96fd913","author":{"email":"59dfe7e004393a2f89ad78e3a810b4cb6d0cd637@redhat.com","name":"Victor Stinner"},"message":"Support ssh-keygen of OpenSSH 6.8\n\nOpenSSH 6.8 changed the default hash method to SHA256. OpenSSH 6.7 and\nolder don't support the -E command line option to specify the hash\nmethod.\n\nFirst try without -E since most Linux distribution for OpenStack Kilo\nstill use OpenSSH 6.7. If OpenSSH 6.8 and newer is detected (hash method\nspecified in the output), call again ssh-keygen with -E md5 to hash the\nfingerprint using MD5.\n\nThis change fixes the two following tests on Fedora 22:\n\n* nova.tests.unit.api.ec2.test_cloud.CloudTestCase.test_import_key_pair\n* nova.tests.unit.compute.test_keypairs.ImportKeypairTestCase.test_success_ssh\n\nAdd two unit tests mocking OpenSSH 6.7 and 6.8 outputs.\n\nCloses-bug: #1464298\nChange-Id: I867684c36377e5c1e5ca5d33e3fc2f1795f44e06","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/7f0ca80ff2d10ad2bb03bab955945b5fc96fd913"},{"sha":"cefda56cb10af546cf9e9a8f0bd8ec5cfb21b246","author":{"email":"f1faf9d84fc2d4015d4e0fa65427b9f0d540b42d@zurich.ibm.com","name":"Zoltan Arnold Nagy"},"message":"Handle unexpected clear events call\n\nCurrently we don't check if we have access to events at the time of\ncalling clear_events for an instance. This could result in operations\nfailing (like deleting an instance) for the user.\n\nAdd a check and a log message that this shouldn't happen (but it does).\n\nChange-Id: I29852662cbfe38f37f9d5154147e6b17b7b8b454\nCloses-Bug: 1454149\n(cherry picked from commit bb4511b4d0550aa4c41a42d07ce9b8af4f867362)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/cefda56cb10af546cf9e9a8f0bd8ec5cfb21b246"},{"sha":"6ecb384584c5d12223f1296bc757e25c16b6b103","author":{"email":"e54ac0254958210cc7aaf4795d156f3b6e6ea9e1@mirantis.com","name":"Roman Podoliaka"},"message":"Fix rebuild of an instance with a volume attached\n\nWhen detaching block devices on rebuild we only notify Cinder it's\nsafe to detach a volume, but don't actually tell the driver to do\nthat first.\n\nCloses-Bug: #1440762\n\nChange-Id: I017bf749f426717dc76cf99a387102848fb1c541\n(cherry picked from commit 337471bc71cbdabe6b492379c81470abac8040d2)\n\n---------------------------------------------------------------------\nsquashed with another change that fixes a bug introduced in the first\n---------------------------------------------------------------------\n\nrebuild: fix rebuild of server with volume attached\n\nThis was meant to be fixed by I017bf749f426717dc76cf99a387102848fb1c541 ,\nbut it didn't take into account that BDM entry was destroyed, which\ncaused the rebuild to fail when spawning the instance.\n\nAdd a new parameter to detach_volume() to bypass destroying of BDM,\nas we just want to detach a volume first and then re-attach it again.\n\nA Tempest test is added in I50557c69b54003d3409c8e977966f5332f4fe690\nto make sure this is actually tested in the gate.\n\nCloses-Bug: #1440762\n\nCo-Authored-By: melanie witt <melwitt@yahoo-inc.com>\n\nConflicts:\n        nova/compute/manager.py\n\nNOTE(mriedem): In Kilo the detach_volume method was still using the\n@object_compat decorator.\n\nChange-Id: I9134fbf5ce72c32cca91de90001c09e00b4e19e8\n(cherry picked from commit 25f15b0bc3bd1971fd29062a7a001f8007485636)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/6ecb384584c5d12223f1296bc757e25c16b6b103"},{"sha":"6292904a4b5f41b654eae4dbd5cf7f14cad0aada","author":{"email":"d747e9f7c331a977bd04ce8594b48e0519abc60e@nttdata.com","name":"abhishekkekane"},"message":"Execute _poll_shelved_instances only if shelved_offload_time is > 0\n\nshelved_offload_time -1 means never offload shelved instance. Currently,\nthe periodic task \"_poll_shelved_instances\" changes the vm state from\nSHELVED to SHELVED_OFFLOAD even when the shelved_offload_time is set to -1.\n\nAdded check in _poll_shelved_instances to offload instances only if\nshelved_offload_time is greater than 0.\n\nDocImpact\nCloses-bug: #1472946\nChange-Id: I55368e961b65a5ca73718fdcd42823680f7cbfa4\n(cherry picked from commit abf20cd57023039958091c39f6cdb775c912c9ac)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/6292904a4b5f41b654eae4dbd5cf7f14cad0aada"},{"sha":"fc4beb1dc46d9fdcffe76d3052c1539fcaa0dc4d","author":{"email":"95c90c669677ccb62c95b44eb5e0545208a626e3@danplanet.com","name":"Dan Smith"},"message":"Fix serializer supported version reporting in object_backport\n\nThe serializer needs to report the version of the toplevel object\nthat we were trying to deserialize when we encountered the incompatible\nversion. We depend on the implementor of the indirection_api to use\nthe object relationship mappings to return to us a fully-supported\nobject tree based on the version at the top.\n\nThis patch fixes the serializer to report the toplevel version instead\nof the one that caused the fault.\n\nConflicts:\n        nova/objects/base.py\n        nova/tests/unit/objects/test_objects.py\n\nNOTE(mriedem): The conflicts are due to the NovaObjectRegistry not\nexisting in Kilo.\n\nChange-Id: I7ac03717e17cd7229abfeef6d9c7d9d8ec9be27a\nCloses-Bug: #1475356\n(cherry picked from commit 7c0e2238eb003ac0c620f4b63fa92baa6675e724)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/fc4beb1dc46d9fdcffe76d3052c1539fcaa0dc4d"},{"sha":"39b8b5c773436250dc264619aa4dabb4bcabdbea","author":{"email":"2f4df71b64d5809dd813a20c9f7aacdb9688d5d0@de.ibm.com","name":"Markus Zoeller"},"message":"Support host type specific block volume attachment\n\n----\nNOTE(markus_z): Nova uses os-brick since commit\ne6cdd1693ba843e1c8dcccbde3af20f62eb0b5a2. That's the reason why I\ncannot backport a valid nova patch from master. There is an abandoned\nchange with commit 7357f9691123f7736b60bf2b4a86b479c974bdc7 which\ncontains the needed change, but that would cause confusion.\n\nos-brick contains this change with commit\nb1a8c2e1f18d424adfdfa29bae47cafa4700dcee which is marked as\nimplementing a blueprint, but should have been a bug in the first\nplace.\n----\n\nAdd the platform and operating system type to the connector to allow a\nCinder driver to set host type specific configuration attributes when\nattaching a Fibre-Channel volume.\n\nCloses-Bug: #1471810\n\nChange-Id: I74bdc527f94b5f4eefd4341d0bf9aa754a8a140b","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/39b8b5c773436250dc264619aa4dabb4bcabdbea"},{"sha":"6dc2aa595510c74c7037cc20fb81727dd52f3154","author":{"email":"d747e9f7c331a977bd04ce8594b48e0519abc60e@nttdata.com","name":"abhishekkekane"},"message":"libvirt: Kill rsync/scp processes before deleting instance\n\nIn the resize operation, during copying files from source to\ndestination compute node scp/rsync processes are not aborted after\nthe instance is deleted because linux kernel doesn't delete instance\nfiles physically until all processes using the file handle is closed\ncompletely. Hence rsync/scp process keeps on running until it\ntransfers 100% of file data.\n\nAdded new module instancejobtracker to libvirt driver which will add,\nremove or terminate the processes running against particular instances.\nAdded callback methods to execute call which will store the pid of\nscp/rsync process in cache as a key: value pair and to remove the\npid from the cache after process completion. Process id will be used to\nkill the process if it is running while deleting the instance. Instance\nuuid is used as a key in the cache and pid will be the value.\n\nConflicts:\n        nova/virt/libvirt/driver.py\n\nSecurityImpact\n\nCloses-bug: #1387543\nChange-Id: Ie03acc00a7c904aec13c90ae6a53938d08e5e0c9\n(cherry picked from commit 7ab75d5b0b75fc3426323bef19bf436a258b9707)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/6dc2aa595510c74c7037cc20fb81727dd52f3154"},{"sha":"423aa598275ead35a7b4ad4b21ec354654370fd1","author":{"email":"aa1cce1166aaa7b9b18552587877987501e5a76e@cn.ibm.com","name":"ZHU ZHU"},"message":"Don't pass the service catalog when making glance requests\n\nIf your service catalog has too many endpoints in it, passing this in\nthe request to glance can result in a 400 because the header is too big.\n\nThis isn't even necessary to pass to glance since we use the auth_token\nmiddleware.\n\nPer bknudson: \"Any service using the auth_token middleware has no use\nfor the x-service-catalog header. All that auth_token middleware uses is\nx-auth-token. The auth_token middleware will actually strip the\nx-service-catalog from the request before it sends the request on to the\nrest of the pipeline, so the application will never see it.\"\n\nCloses-Bug: #1482699\n\nChange-Id: I204c6f61194bef6eba01ab0525bc80fa2e323acd\n(cherry picked from commit 4fa9bc1c544af30f167499284fc3e8ff6b65d23f)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/423aa598275ead35a7b4ad4b21ec354654370fd1"},{"sha":"0a8113134d963f7d6f0d659a7f5abfd4054d6003","author":{"email":"aa71f94694e581551b4f662abcc23a9271bdb41d@vmware.com","name":"Gary Kotton"},"message":"Compute: replace incorrect instance object with dict\n\nCommit 171e5f8b127610d93a230a6f692d8fd5ea0d0301 updated security\ngroups instances to be instance objects. These are not instance objects\nand are the instances stored in the database.\n\nChange-Id: If79b5d4592e1ecbd860aa53e2d976b658c9227d0\nCloses-bug: #1461065\n(cherry picked from commit 99b56a47a3654590a7fdabfb34f073911393c471)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/0a8113134d963f7d6f0d659a7f5abfd4054d6003"},{"sha":"3bfa2125a25f05f0abe4314a9ff79cd1e71fd5dc","author":{"email":"934369a96ec7951e6b5c2a5d93ac570f8bd16c80@lists.openstack.org","name":"OpenStack Proposal Bot"},"message":"Updated from global requirements\n\nChange-Id: I318907618da3f531a551a9cf3416e9f4bbe0cafe","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/3bfa2125a25f05f0abe4314a9ff79cd1e71fd5dc"},{"sha":"5086f52e57a6aa8d709746d2c328003520439d8d","author":{"email":"1f51e5fb9ae20c779d009dfb6c025548f76abc6b@cloudbasesolutions.com","name":"Lucian Petrut"},"message":"Hyper-V: Fix virtual hard disk detach\n\nNova Hyper-V driver fails to detach virtual hard disks when using\nthe virtualizaton v1 WMI namespace. This affects Windows Server\n2008 as well as Windows Server 2012 when the old namespace is used.\n\nThe reason is that it cannot find the attached resource,\nusing the wrong resource object connection attribute.\n\nThis patch fixes the issue by using the right resource connection\nattribute when attempting to find an attached virtual disk resource\nby its path.\n\nChange-Id: Ic1b8eaec8d3f5093c6d518a305fd0d40045030c1\nCloses-Bug: 1467451\n(cherry picked from commit a02deffcfab6cc9a7b0764dd36b8514f6cb1a108)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/5086f52e57a6aa8d709746d2c328003520439d8d"},{"sha":"6ab2ffd9a931ebd99f31d94b630123548f69a431","author":{"email":"1f51e5fb9ae20c779d009dfb6c025548f76abc6b@cloudbasesolutions.com","name":"Lucian Petrut"},"message":"Hyper-V: Fix missing WMI namespace issue on Windows 2008 R2\n\nThe Hyper-V driver uses the Microsoft\\Windows\\SMB WMI namespace\nin order to handle SMB shares. The issue is that this namespace is\nnot available on Windows versions prior to Windows Server 2012.\n\nFor this reason, the Hyper-V driver fails to initialize on Windows\nServer 2008 R2.\n\nThis patch fixes the issue by properly handling the PathUtils\ninitialization.\n\nCloses-Bug: #1463044\nChange-Id: Ia99576589af6049ee07337c631ed7d5d6cf602d9\n(cherry picked from commit 0625df995629291a6112197f61099cd82b31679b)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/6ab2ffd9a931ebd99f31d94b630123548f69a431"},{"sha":"f764a00873302a966a335520b8ef315e3a0be919","author":{"email":"1f51e5fb9ae20c779d009dfb6c025548f76abc6b@cloudbasesolutions.com","name":"Lucian Petrut"},"message":"Hyper-V: Fix SMBFS volume attach race condition\n\nWhen the SMBFS volume backend is used and a volume is detached,\nthe according SMB share is unmounted if no longer used.\n\nThis can cause issues if at the same time, a different volume\nstored on the same share is being attached as the according\ndisk image will not be available.\n\nThis patch fixes the issue by synchronizing volume attach and share\nunmount operations based on the share path.\n\nCloses-Bug: #1461081\n\nChange-Id: I45f202ad6ada0c472759e8ba3c122f3cfbeee7cc\n(cherry picked from commit 5aac3cd675af87b053e1a69d822b5f3bfdab5257)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/f764a00873302a966a335520b8ef315e3a0be919"},{"sha":"ea423c440a664a9b409c201cf3203f3a183624c1","author":{"email":"af739d2f4a05c59b6221d22d4e3a86ff2cbe39c4@cloudbasesolutions.com","name":"Claudiu Belu"},"message":"Hyper-V: Fixes live migration configdrive copy operation\n\nFixes the configdrive copy destination.\n\nChange-Id: I0a8d0b5cac99bef4c32959d7dff3117a9bb3c61d\nCloses-Bug: #1465443\n(cherry picked from commit 615d8682bbae443b679b010973d6d9b1ed489328)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/ea423c440a664a9b409c201cf3203f3a183624c1"},{"sha":"dbad3ff05626cbc58606ea3cc379078bad47e1c3","author":{"email":"af739d2f4a05c59b6221d22d4e3a86ff2cbe39c4@cloudbasesolutions.com","name":"Claudiu Belu"},"message":"Hyper-V: Removes old instance dirs after live migration\n\nRemoves old instance dirs after live migration completed\nsuccessfully.\n\nChange-Id: I0b67fdfe12d20cf8322ec3ee6f22abb48bc4f7e4\nCloses-Bug: #1465446\n(cherry picked from commit 6df24c0f50bdcd49396239533beb8406bfdd979e)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/dbad3ff05626cbc58606ea3cc379078bad47e1c3"},{"sha":"31a96c80252f77a394e2b5e0965c3f3097fc3ea9","author":{"email":"934369a96ec7951e6b5c2a5d93ac570f8bd16c80@lists.openstack.org","name":"OpenStack Proposal Bot"},"message":"Updated from global requirements\n\nChange-Id: I8642b947f400b87c014073eb38665ca9cd2a5853","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/31a96c80252f77a394e2b5e0965c3f3097fc3ea9"},{"sha":"68a6447a8705fa844a936f8372e1aa4392bd4cf9","author":{"email":"b7a5da1e6209f9510c07a03f0423c37727add225@redhat.com","name":"Matthew Booth"},"message":"Don't check flavor disk size when booting from volume\n\nWhen creating a volume from an image, cinder copies the image metadata\ninto volume properties. When booting from the volume, we read this\nmetadata from the volume and use it as image metadata once again.\n\nWhile fixing the check against min_ram,\nchange I861a78b5c7efa71e4bf7206d388b8d0d8048c78e introduced a\nregression which prevents a user from booting a volume which is larger\nthan the flavor's disk. As we are not creating this disk, this check\ndoes not make sense. Similarly, it checks the image metadata's\nmin_disk against the flavor disk size, which is not being used.\n\nThis change leaves the image metadata check unaltered when creating a\nflavor disk. When booting from a volume, we check min_disk from image\nmetadata against the actual size of the volume. We don't check the\nvolume size at all. The check against min_ram is retained unaltered.\n\nCloses-Bug: #1457517\nCloses-Bug: #1459491\nCloses-Bug: #1466305\nChange-Id: I264493172da20b664df571e32876030246c2a87c\n(cherry picked from commit 642c986f0636d52a9ba279c87e25082b4aa9b3b8)","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/68a6447a8705fa844a936f8372e1aa4392bd4cf9"},{"sha":"a05c15743b629c3f4551b53ab526cb8f0e232c37","author":{"email":"db2681fd58b9be02200f0638dc493455dccb644d@hp.com","name":"Anthony Lee"},"message":"Fix live-migrations usage of the wrong connector information\n\nDuring the post_live_migration step for the Nova libvirt driver\nan incorrect assumption is being made about the connector\ninformation being sent to _disconnect_volume. It is assumed that\nthe connection information on the source and destination is the\nsame but that is not always the case. The BDM, where the\nconnector information is being retrieved from only contains the\nconnection information for the destination. This will not work\nwhen trying to disconnect volumes from the source during live\nmigration as the properties such as the target_lun and\ninitiator_target_map could be different. This ends up leaving\nbehind dangling LUNs and possibly removing the incorrect\nvolume's LUNs.\n\nThe solution proposed here utilizes the connection_info that\ncan be retrieved for a host from Cinder's initialize_connection\nAPI. This connection information contains the correct data for\nthe source host and allows volume LUNs to be removed properly.\n\n--\n\nNOTE(sahid): The TODO comment in the original change on master is\nomitted here since os-brick wasn't used by nova in kilo so leaving\nit in the backport would be confusing.\n\nChange-Id: I3dfb75eb58dfbc66b218bcee473af4c2ac282eb6\nCloses-Bug: #1475411\nCloses-Bug: #1288039\nCloses-Bug: #1423772","distinct":true,"url":"https://api.github.com/repos/NeCTAR-RC/nova/commits/a05c15743b629c3f4551b53ab526cb8f0e232c37"}]}