You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: