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

NextDevice Fix #268

Merged
merged 1 commit into from
Sep 14, 2016
Merged

NextDevice Fix #268

merged 1 commit into from
Sep 14, 2016

Conversation

akutz
Copy link
Collaborator

@akutz akutz commented Sep 14, 2016

This patch fixes an issue where the NextDevice function of the Executor
was not being invoked prior to calling VolumeAttach. No value was being
provided in the VolumeAttachOpts.NextDevice field. Now the executor
should properly gather that information and provide it to the server in
the event of an attach call.

This patch fixes an issue where the NextDevice function of the Executor
was not being invoked prior to calling VolumeAttach. No value was being
provided in the VolumeAttachOpts.NextDevice field. Now the executor
should properly gather that information and provide it to the server in
the event of an attach call.
@akutz akutz added the bug label Sep 14, 2016
@akutz akutz self-assigned this Sep 14, 2016
@codecov-io
Copy link

codecov-io commented Sep 14, 2016

Current coverage is 26.03% (diff: 0.00%)

Merging #268 into master will decrease coverage by 0.04%

@@             master       #268   diff @@
==========================================
  Files            39         39          
  Lines          2420       2420          
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
- Hits            631        630     -1   
- Misses         1721       1722     +1   
  Partials         68         68          

Powered by Codecov. Last update f072fd1...f4960be

@akutz akutz merged commit 030b994 into thecodeteam:master Sep 14, 2016
@akutz akutz deleted the bugfix/next-device-path branch September 14, 2016 01:12
@akutz akutz removed the in progress label Sep 14, 2016
@cduchesne cduchesne modified the milestone: 0.2.1 Sep 14, 2016
proudh added a commit to proudh/libstorage that referenced this pull request Sep 14, 2016
Courtesy of akutz's latest libstorage commit (PR thecodeteam#268) the device
path of the next available device is now retrieved from the executor
and not the storage driver.

The device names for EBS are now /dev/xvd[f-p] as opposed to
/dev/xvd[a-z], since EBS has suddenly begun to rebel against device
names that are not of the pattern [f-p].

Also added some comments to the executor
proudh added a commit to proudh/libstorage that referenced this pull request Sep 14, 2016
Courtesy of akutz's latest libstorage commit (PR thecodeteam#268) the device
path of the next available device is now retrieved from the executor
and not the storage driver.

The device names for EBS are now /dev/xvd[f-p] as opposed to
/dev/xvd[a-z], since EBS has suddenly begun to rebel against device
names that are not of the pattern [f-p].

Also added some comments to the executor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants