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

Replace a VM playbook should add correct number of disks #5496

Open
VickieKarasic opened this issue Oct 31, 2024 · 0 comments
Open

Replace a VM playbook should add correct number of disks #5496

VickieKarasic opened this issue Oct 31, 2024 · 0 comments
Assignees
Labels

Comments

@VickieKarasic
Copy link
Contributor

User story

As an Ops person, I want to make sure that when I run the Replace a VM playbook, it replicates the number of attached hard disks, not just the total amount of disk space.

Acceptance criteria

The playbook should add the same number of disks as the original machine had.

Implementation notes, if any

The original catalog-qa1 had 2 disks of 30GB each. When we replaced catalog-qa1, we noticed that it only came up with one disk at 60GB. When we expanded the logical volume, it only expanded to 30GB. (For example, if you look in vSphere, you see one hard disk at 60GB, whereas in the original machine, there were 2 hard disks with 30GB each).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants