Skip to content

slcli vs capture --all and metadata #723

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

Closed
owinfrey opened this issue Apr 27, 2016 · 0 comments · Fixed by #776
Closed

slcli vs capture --all and metadata #723

owinfrey opened this issue Apr 27, 2016 · 0 comments · Fixed by #776

Comments

@owinfrey
Copy link

Expected Behavior:

Capture all disks including metadata

Actual Behavior

Invalid block device supplied. Please be sure to not include any metadata disk block devices.

Environment Information

Operating System:
RHEL 6.7
softlayer-python version (slcli --version):
slcli (SoftLayer Command-line), version 4.1.1

Hello,
I am trying to automate the capture of several VSIs. I have two devices with multiple disks and a metadata block device.

The following slcli cmd is failing with the behavior above:
slcli vs capture --name="description" --note="additional notes" 17800945 --all True

Is it possible to identify only the disks I want to capture? Example Disk, 0,2,4 and exclude disk 7 (metadata)

Thanks

@sudorandom sudorandom added the Bug label Aug 3, 2016
@sudorandom sudorandom assigned sudorandom and unassigned sudorandom Aug 3, 2016
@sudorandom sudorandom modified the milestone: Next Release Aug 27, 2016
aquishix added a commit to aquishix/softlayer-python that referenced this issue Sep 6, 2016
sudorandom added a commit that referenced this issue Oct 13, 2016
* Fixed metadata disk exclusion issue in vs capture command.  (#723)

* Always excludes metadata disks from image capturing (fixes #723)

* Fix a test issue where the types might not match in reality

* Filter caputer images by type being SWAP
@sudorandom sudorandom modified the milestones: Next Release, v5.2.1 Nov 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants