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

Reply to initiator with LUN busy when there is a read/write error from backend #15

Merged
merged 2 commits into from Jun 8, 2018

Conversation

Projects
None yet
2 participants
@payes
Copy link
Member

payes commented Jun 7, 2018

If a check condition is returned with medium error, the iscsi initiator marks the volume as read only.
Errors with no space left on disk will be addressed later.
Manual testing was performed by attaching the volume to applications running on kubernetes pods.
After these fixes the Read Only state is avoided if there are network fluctuations or the replica is down for short period of time.
Signed-off-by: Payes payes.anand@cloudbyte.com

Reply to initiator with LUN busy when there is a read/write error fro…
…m backend

Signed-off-by: Payes <payes.anand@cloudbyte.com>

@payes payes requested review from kmova , vishnuitta and ksatchit Jun 7, 2018

Update with review comments
Signed-off-by: Payes <payes.anand@cloudbyte.com>
@vishnuitta
Copy link
Member

vishnuitta left a comment

changes are good.

@payes payes merged commit 51112f4 into openebs:master Jun 8, 2018

1 check failed

continuous-integration/travis-ci/pr The Travis CI build failed
Details

muratkars added a commit to muratkars/trusted-charts that referenced this pull request Jul 20, 2018

Update OpenEBS to 0.6.0
What's new in this release:
- Integrate the Volume Snapshots capabilities with Kubernetes Snapshot controller
- Enhance maya-apiserver to use CAS Templates for orchestrating new Storage Engines
- Enhance mayactl to provide additional details about volume such as - replica status, node details where replicas are running.
- Enhance maya-apiserver to schedule Replica Pods on specific nodes using nodeSelector
- Enhance provisioner and maya-apiserver to allow specifying cross AZ scheduling of Replica Pods.
- Support for deploying OpenEBS via Kubernetes stable Helm Charts
- openebs-operator.yaml is modified to run OpenEBS pods in its own namespace openebs
- Enhance e2e tests to simulate chaos at different layers like - CPU, RAM, Disk, Network, and Node

Major Issues Fixed
- Fixed an issue where intermittent connectivity errors between controller and replica caused iSCSI initiator to mark the volume as read-only. openebs/gotgt#15
- Fixed an issue where intermittent connectivity errors were causing the controller to silently drop the replicas and mark the Volumes as read-only. The replicas dropped in this way were not getting re-added to the Controller. openebs/jiva#45
- Fixed an issue where volume would be marked as read-only if one of the three replicas returned an error to IO. openebs/jiva#56
- Fixed an issue where replica fails to register back with the controller if the attempt to register occurred before the controller cleared the replica's previous state. openebs/jiva#56
- Fixed an issue where a volume with a single replica would get stuck in the read-only state once the replica was restarted. openebs/jiva#45

muratkars added a commit to muratkars/trusted-charts that referenced this pull request Jul 20, 2018

Update OpenEBS to 0.6.0
What's new in this release:
- Integrate the Volume Snapshots capabilities with Kubernetes Snapshot controller
- Enhance maya-apiserver to use CAS Templates for orchestrating new Storage Engines
- Enhance mayactl to provide additional details about volume such as - replica status, node details where replicas are running.
- Enhance maya-apiserver to schedule Replica Pods on specific nodes using nodeSelector
- Enhance provisioner and maya-apiserver to allow specifying cross AZ scheduling of Replica Pods.
- Support for deploying OpenEBS via Kubernetes stable Helm Charts
- openebs-operator.yaml is modified to run OpenEBS pods in its own namespace openebs
- Enhance e2e tests to simulate chaos at different layers like - CPU, RAM, Disk, Network, and Node

Major Issues Fixed
- Fixed an issue where intermittent connectivity errors between controller and replica caused iSCSI initiator to mark the volume as read-only. openebs/gotgt#15
- Fixed an issue where intermittent connectivity errors were causing the controller to silently drop the replicas and mark the Volumes as read-only. The replicas dropped in this way were not getting re-added to the Controller. openebs/jiva#45
- Fixed an issue where volume would be marked as read-only if one of the three replicas returned an error to IO. openebs/jiva#56
- Fixed an issue where replica fails to register back with the controller if the attempt to register occurred before the controller cleared the replica's previous state. openebs/jiva#56
- Fixed an issue where a volume with a single replica would get stuck in the read-only state once the replica was restarted. openebs/jiva#45

@muratkars muratkars referenced this pull request Jul 20, 2018

Merged

Update OpenEBS to 0.6.0 #122

baldwinSPC added a commit to StackPointCloud/trusted-charts that referenced this pull request Aug 2, 2018

Update OpenEBS to 0.6.0 (#122)
* Update OpenEBS to 0.6.0

What's new in this release:
- Integrate the Volume Snapshots capabilities with Kubernetes Snapshot controller
- Enhance maya-apiserver to use CAS Templates for orchestrating new Storage Engines
- Enhance mayactl to provide additional details about volume such as - replica status, node details where replicas are running.
- Enhance maya-apiserver to schedule Replica Pods on specific nodes using nodeSelector
- Enhance provisioner and maya-apiserver to allow specifying cross AZ scheduling of Replica Pods.
- Support for deploying OpenEBS via Kubernetes stable Helm Charts
- openebs-operator.yaml is modified to run OpenEBS pods in its own namespace openebs
- Enhance e2e tests to simulate chaos at different layers like - CPU, RAM, Disk, Network, and Node

Major Issues Fixed
- Fixed an issue where intermittent connectivity errors between controller and replica caused iSCSI initiator to mark the volume as read-only. openebs/gotgt#15
- Fixed an issue where intermittent connectivity errors were causing the controller to silently drop the replicas and mark the Volumes as read-only. The replicas dropped in this way were not getting re-added to the Controller. openebs/jiva#45
- Fixed an issue where volume would be marked as read-only if one of the three replicas returned an error to IO. openebs/jiva#56
- Fixed an issue where replica fails to register back with the controller if the attempt to register occurred before the controller cleared the replica's previous state. openebs/jiva#56
- Fixed an issue where a volume with a single replica would get stuck in the read-only state once the replica was restarted. openebs/jiva#45

* Update OpenEBS to 0.6.0

What's new in this release:
- Integrate the Volume Snapshots capabilities with Kubernetes Snapshot controller
- Enhance maya-apiserver to use CAS Templates for orchestrating new Storage Engines
- Enhance mayactl to provide additional details about volume such as - replica status, node details where replicas are running.
- Enhance maya-apiserver to schedule Replica Pods on specific nodes using nodeSelector
- Enhance provisioner and maya-apiserver to allow specifying cross AZ scheduling of Replica Pods.
- Support for deploying OpenEBS via Kubernetes stable Helm Charts
- openebs-operator.yaml is modified to run OpenEBS pods in its own namespace openebs
- Enhance e2e tests to simulate chaos at different layers like - CPU, RAM, Disk, Network, and Node

Major Issues Fixed
- Fixed an issue where intermittent connectivity errors between controller and replica caused iSCSI initiator to mark the volume as read-only. openebs/gotgt#15
- Fixed an issue where intermittent connectivity errors were causing the controller to silently drop the replicas and mark the Volumes as read-only. The replicas dropped in this way were not getting re-added to the Controller. openebs/jiva#45
- Fixed an issue where volume would be marked as read-only if one of the three replicas returned an error to IO. openebs/jiva#56
- Fixed an issue where replica fails to register back with the controller if the attempt to register occurred before the controller cleared the replica's previous state. openebs/jiva#56
- Fixed an issue where a volume with a single replica would get stuck in the read-only state once the replica was restarted. openebs/jiva#45

baldwinSPC added a commit to StackPointCloud/trusted-charts that referenced this pull request Aug 2, 2018

Moving to staging. (#129)
* Update OpenEBS to 0.6.0 (#122)

* Update OpenEBS to 0.6.0

What's new in this release:
- Integrate the Volume Snapshots capabilities with Kubernetes Snapshot controller
- Enhance maya-apiserver to use CAS Templates for orchestrating new Storage Engines
- Enhance mayactl to provide additional details about volume such as - replica status, node details where replicas are running.
- Enhance maya-apiserver to schedule Replica Pods on specific nodes using nodeSelector
- Enhance provisioner and maya-apiserver to allow specifying cross AZ scheduling of Replica Pods.
- Support for deploying OpenEBS via Kubernetes stable Helm Charts
- openebs-operator.yaml is modified to run OpenEBS pods in its own namespace openebs
- Enhance e2e tests to simulate chaos at different layers like - CPU, RAM, Disk, Network, and Node

Major Issues Fixed
- Fixed an issue where intermittent connectivity errors between controller and replica caused iSCSI initiator to mark the volume as read-only. openebs/gotgt#15
- Fixed an issue where intermittent connectivity errors were causing the controller to silently drop the replicas and mark the Volumes as read-only. The replicas dropped in this way were not getting re-added to the Controller. openebs/jiva#45
- Fixed an issue where volume would be marked as read-only if one of the three replicas returned an error to IO. openebs/jiva#56
- Fixed an issue where replica fails to register back with the controller if the attempt to register occurred before the controller cleared the replica's previous state. openebs/jiva#56
- Fixed an issue where a volume with a single replica would get stuck in the read-only state once the replica was restarted. openebs/jiva#45

* Update OpenEBS to 0.6.0

What's new in this release:
- Integrate the Volume Snapshots capabilities with Kubernetes Snapshot controller
- Enhance maya-apiserver to use CAS Templates for orchestrating new Storage Engines
- Enhance mayactl to provide additional details about volume such as - replica status, node details where replicas are running.
- Enhance maya-apiserver to schedule Replica Pods on specific nodes using nodeSelector
- Enhance provisioner and maya-apiserver to allow specifying cross AZ scheduling of Replica Pods.
- Support for deploying OpenEBS via Kubernetes stable Helm Charts
- openebs-operator.yaml is modified to run OpenEBS pods in its own namespace openebs
- Enhance e2e tests to simulate chaos at different layers like - CPU, RAM, Disk, Network, and Node

Major Issues Fixed
- Fixed an issue where intermittent connectivity errors between controller and replica caused iSCSI initiator to mark the volume as read-only. openebs/gotgt#15
- Fixed an issue where intermittent connectivity errors were causing the controller to silently drop the replicas and mark the Volumes as read-only. The replicas dropped in this way were not getting re-added to the Controller. openebs/jiva#45
- Fixed an issue where volume would be marked as read-only if one of the three replicas returned an error to IO. openebs/jiva#56
- Fixed an issue where replica fails to register back with the controller if the attempt to register occurred before the controller cleared the replica's previous state. openebs/jiva#56
- Fixed an issue where a volume with a single replica would get stuck in the read-only state once the replica was restarted. openebs/jiva#45

* Harbor helm chart (#128)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment