Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get latest changes from upstream #23

Merged
merged 26 commits into from Feb 13, 2020

Conversation

Fedosin
Copy link

@Fedosin Fedosin commented Feb 13, 2020

No description provided.

scruplelesswizard and others added 26 commits January 3, 2020 12:56
Removing myself from OWNERS as I am no longer actively participating
All the repos from staging, now come with their own tags.
See #84608
NodeUnpublishVolume and NodeUnstageVolume should just return NotFound if
the volume with the volume_id does not exist. Meaning in this case...
does not exist in openstack any more. Not being mounted any more is a
valid case. Imaging e.g. umount, pv updated, another trigger of umount.

https://github.com/container-storage-interface/spec/blob/master/spec.md#nodeunpublishvolume-errors
https://github.com/container-storage-interface/spec/blob/master/spec.md#nodeunstagevolume-errors
(cherry picked from commit 08e36e4)
Signed-off-by: Bharat Kunwar <brtknr@bath.edu>
* removed hardcoded user agent name from manilaclient

* manila-provisioner refactoring: use pkg/csi/manila/manilaclient as manila client

* fixed tests
…#884)

* CCM: set predicted and proper server ip addresses order

* code review
* added cloud-provider-openstack-acceptance-test-csi-manila

* added trigger whitelist for csi-manila job
…ernetes#908)

* retrieve only public share type extra specs

* updated unit tests
…bernetes#881)

* removed responsebroker

* replaced responsebroker, make use of ABORTED error code

This commit replaces responsebroker with sync.Map as a means of
signaling whether an operation is in progress.

If there's a pending CreateVolume/CreateSnapshot on a volume/snapshot
with the same name, the RPC will now return ABORTED error code.
This means that in any given time there will be only one goroutine
waiting for a particular resource to complete its creation.

* call tryDeleteSnapshot before returning on error
like volume, we need create description and prop for snapshot

(part) of the result looks like:

+--------------------------------------------+----------------------------------------------+
| created_at                                 | 2019-06-28T01:25:10.000000                   |
| description                                | Created by OpenStack Cinder CSI driver       |
| id                                         | 823c9947-b8ee-464a-9413-eff84869b098         |
| properties                                 | cinder.csi.openstack.org/cluster='ClusterID' |
+--------------------------------------------+----------------------------------------------+
during some debug found some logs are not need to be
enabled by default..
* [WIP] Remove inactive reviewers/approvers  from OWNERS

Remove inactive approvers/reviewers from OWNERS
kubernetes/kubernetes#76269
used the script from dims
https://gist.github.com/dims/3261edf075660ad1bf5c338b8794c21b

* Update OWNERS

Added ricolin
When either the volume or the instance in openstack is already gone, the
ControllerUnpublishVolume assumes the volume is not attached any more.

This is is the behavior DO and the GCE controller implement as well, and
a sane implemetation, because between any of the code steps, an out of
cluster process could have delete the volume. E.g. a test case, where
the internal teardown takes longer than reaching out for cinder delete
in the cleanup step.
@openshift-ci-robot openshift-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Feb 13, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 13, 2020
@Fedosin
Copy link
Author

Fedosin commented Feb 13, 2020

/retest

@tomassedovic
Copy link

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 13, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Fedosin, tomassedovic

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [Fedosin,tomassedovic]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit cce55cb into openshift:master Feb 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet