-
Notifications
You must be signed in to change notification settings - Fork 898
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
Disks should be added as 'active' in RHV #13913
Disks should be added as 'active' in RHV #13913
Conversation
PR ManageIQ#13318 introduced a new class to handle disk attachments. A disk should be added to RHV as 'active' since there is no method to modify it afterward. DiskAttachmentBuilder class will set the 'active' as the default status of the new disk, so any scenario which adds disks (vm reconfigure, automation request, provision request) will share the same behavior. https://bugzilla.redhat.com/show_bug.cgi?id=1422145
@miq-bot add_label blocker euwe/yes providers/rhevm |
@masayag Cannot apply the following label because they are not recognized: blocker euwe/yes providers/rhevm |
@miq-bot add_label blocker, euwe/yes. providers/rhevm |
@masayag Cannot apply the following label because they are not recognized: euwe/yes. providers/rhevm |
looks good to me. |
@miq-bot add_label euwe/yes, providers/rhevm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@agrare can you merge this please?
Checked commit masayag@8fdeaad with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
👍 will merge when green |
…e_in_rhv Disks should be added as 'active' in RHV (cherry picked from commit a094a95) https://bugzilla.redhat.com/show_bug.cgi?id=1422178
Euwe backport details:
|
PR #13318 introduced a new
class to handle disk attachments. A disk should be added to RHV as
'active' since there is no method to modify it afterward.
DiskAttachmentBuilder class will set the 'active' as the default
status of the new disk, so any scenario which adds disks (vm
reconfigure, automation request, provision request) will share the same
behavior.
https://bugzilla.redhat.com/show_bug.cgi?id=1422145