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

Read PowerVS Boot Image Name and Disk ID also Boot Volume not Replicated #5753

Open
narendermann opened this issue Oct 29, 2024 · 2 comments
Labels
enhancement service/Power Systems Issues related to Power Systems

Comments

@narendermann
Copy link

I am planning to enable GRS replication for powervs instance and I want to add my boot image as well as part of the same VG (Volume Group) or CG (Consistency Group). But I am not able to read the boot image informationof the powervs instance and hence not able to update the bot image GRS replication to the target VG (Volume Group) or CG (Consistency Group).

Hence, I would like to add this as feature to the next IBM Provider release.

Additionally, pi_boot_volume_replication_enabled under ibm_pi_instance should have sub points to define the VG/CG and additional information required to add the Boot Volume to the existing VG/CG.

@narendermann
Copy link
Author

Tried with below provider versions:

version = "~>1.70.0"
version = "1.71.0-beta1"
version = "1.71.0-beta0"

@narendermann
Copy link
Author

Today tried with version = "~>1.71.1" - Still the boot volumes are not getting replicated even after defining pi_boot_volume_replication_enabled = true

@narendermann narendermann changed the title Read PowerVS Boot Image Name and Disk ID Read PowerVS Boot Image Name and Disk ID also Boot Volume not Replicated Nov 11, 2024
@Alexander-Kita Alexander-Kita added the service/Power Systems Issues related to Power Systems label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement service/Power Systems Issues related to Power Systems
Projects
None yet
Development

No branches or pull requests

2 participants