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

salt-cloud proxmox driver ignores some settings when cloning #49254

Closed
BrianSidebotham opened this issue Aug 22, 2018 · 0 comments
Closed

salt-cloud proxmox driver ignores some settings when cloning #49254

BrianSidebotham opened this issue Aug 22, 2018 · 0 comments
Labels
Bug broken, incorrect, or confusing behavior fixed-pls-verify fix is linked, bug author to confirm fix P2 Priority 2 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Milestone

Comments

@BrianSidebotham
Copy link
Contributor

Description of Issue/Question

When using the clone option with the salt-cloud proxmox driver other settings in the profile, such as net0 or ide2 are ignored.

When using something like a cloud-init template, it's useful to be able to clone from a template but then also to adjust the ide2 setting of the clone so that a different cloud-init configuration ISO can be mounted.

Steps to Reproduce Issue

Use the clone and ide2 options in the same profile and notice that the ide2 setting is ignored.

Versions Report

-bash-4.2# salt-cloud --version
salt-cloud 2018.3.2 (Oxygen)
@garethgreenaway garethgreenaway added this to the Approved milestone Aug 22, 2018
@garethgreenaway garethgreenaway added Bug broken, incorrect, or confusing behavior severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around fixed-pls-verify fix is linked, bug author to confirm fix P2 Priority 2 labels Aug 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior fixed-pls-verify fix is linked, bug author to confirm fix P2 Priority 2 severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Projects
None yet
Development

No branches or pull requests

3 participants