Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

[v2v] Fail migration if no conversion host configured #739

Closed
bthurber opened this issue Oct 25, 2018 · 3 comments
Closed

[v2v] Fail migration if no conversion host configured #739

bthurber opened this issue Oct 25, 2018 · 3 comments
Assignees
Labels

Comments

@bthurber
Copy link

BZ link: https://bugzilla.redhat.com/show_bug.cgi?id=1640816

Issue:
When initiating a migration plan, if there are no conversion hosts available the migration plan spins until the 40K timeout has been reached.

Resolution:
If there is no conversion host available fail the migration and provide a reason why in the UI.

@kedark3
Copy link

kedark3 commented Oct 26, 2018

👍

@vconzola vconzola added the bug label Nov 15, 2018
@michaelkro
Copy link
Contributor

Case where there are no configured conversion hosts. The request will be denied.

@michaelkro michaelkro changed the title [v2v] Fail migration if no conversion host available [v2v] Fail migration if no conversion host configured Nov 16, 2018
@mturley
Copy link
Contributor

mturley commented Nov 20, 2018

I think this is a duplicate of #786 (or that is a duplicate of this). Since we've referenced #786 in my WIP PR (#798) and elsewhere already, I'll put the BZ link over there and mark the PR as closing both issues.

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

No branches or pull requests

5 participants