{"push_id":738470520,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"57ba737a0a3de7f221ed86d1e872f376a3de6c6b","before":"6d0b07d9266dbdd268cc2a55fd400a1ad068a3c5","commits":[{"sha":"790111e855b33c781ad7a6d5961d12732e33340f","author":{"email":"73262ad0334ab37227b2f7a0205f51db1e606681@hastexo.com","name":"Florian Haas"},"message":"iSCSILogicalUnit: add check for leftover target/core entries for lio-t\n\nApply the same checking behavior to the lio-t target as the RA\npreviously already did for lio: do not report the resource as being\ngracefully stopped if it still has iblock handles open.\n\nWith lio-t, we cannot specify the iblock number, but since we're using\n$OCF_RESOURCE_INSTANCE as the backstore key here (which is unique\nacross the cluster), the more inclusive file glob is still safe.\n\nFixes ClusterLabs/resource-agents#640.","distinct":true,"url":"https://api.github.com/repos/ClusterLabs/resource-agents/commits/790111e855b33c781ad7a6d5961d12732e33340f"},{"sha":"893fa0630231cb84108be6e0b3c05c760ff238f5","author":{"email":"73262ad0334ab37227b2f7a0205f51db1e606681@hastexo.com","name":"Florian Haas"},"message":"iSCSILogicalUnit: return OCF_NOT_RUNNING on monitor if backing path does not exist\n\nIf iSCSILogicalUnit exposes a local LVM logical volume or even a\nhardware drive, then it is safe to assume that the device will\n\"always\" be there. However, if what we are exposing is itself a\ncluster resource, such as an RBD volume or a DRBD device, then the\nbacking device will appear and disappear as needed.\n\nIt is safe to assume that if the backing file or block device does not\nexist, then it cannot be exported as an iSCSILogicalUnit. Even if it\n*has* been previously exported as an iSCSILogicalUnit, then it should\nbe impossible for it to just disappear or be removed while open, as\nsuch an action would return -EBUSY while the device is open. If it\ndisappears because the drive has physically been yanked, then that is\na condition in which throwing up our hands and fencing the node is the\nproper action.\n\nThus, if during monitor the backing device does not exist, return\nOCF_NOT_RUNNING.\n\nFixes ClusterLabs/resource-agents#641.","distinct":true,"url":"https://api.github.com/repos/ClusterLabs/resource-agents/commits/893fa0630231cb84108be6e0b3c05c760ff238f5"},{"sha":"57ba737a0a3de7f221ed86d1e872f376a3de6c6b","author":{"email":"73262ad0334ab37227b2f7a0205f51db1e606681@hastexo.com","name":"Florian Haas"},"message":"iSCSILogicalUnit: when deleting a LUN or initiator fails with lio-t, proceed with warning\n\nDuring the stop operation, \"targetcli delete\" returns an error if the\nobject we're about to delete already no longer exists. Since stop is a\nforce operation and we must do anything we can to clean up the\nresource, don't exit on that condition but log a warning and proceed\nto removal of the backstore. If *that* fails, then we error out and\npotentially cause the node to be fenced.\n\nFixes ClusterLabs/resource-agents#642.","distinct":true,"url":"https://api.github.com/repos/ClusterLabs/resource-agents/commits/57ba737a0a3de7f221ed86d1e872f376a3de6c6b"}]}