Bug 1296232
Summary: | EBS volume remains in 'detached' state | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jan Safranek <jsafrane> | |
Component: | Storage | Assignee: | Mark Turansky <mturansk> | |
Status: | CLOSED ERRATA | QA Contact: | Chao Yang <chaoyang> | |
Severity: | medium | Docs Contact: | ||
Priority: | urgent | |||
Version: | 3.1.0 | CC: | aos-bugs, bchilds, chaoyang, pep, tdawson | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1304752 (view as bug list) | Environment: | ||
Last Closed: | 2016-05-12 16:26:27 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1267746, 1304752 |
Description
Jan Safranek
2016-01-06 16:27:50 UTC
Upstream work on an attach/detach controller is in progress. This controller will provide fencing so that volumes will first be detached before another node can have that same volume attached. Fixed in kube and will be part of origin rebase. Verification is passed on devenv-rhel7_3313 1. create a volume from web console 2. create a pod apiVersion: v1 kind: Pod metadata: name: aws-web spec: containers: - name: web image: jhou/hello-openshift ports: - name: web containerPort: 80 protocol: tcp volumeMounts: - name: html-volume mountPath: "/usr/share/nginx/html" volumes: - name: html-volume awsElasticBlockStore: volumeID: aws://us-east-1d/vol-02927ba1 fsType: ext4 3. after the pod is running, delete the pod and re-create it 4. the pod is still in running status will test this bug on ose env Verification is passed on atomic-openshift-3.1.1.902-1.git.0.d625c01.el7.x86_64 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2016:1064 |