This is a tracker bug for all bugs blocking the 3.4 release of oVirt.
I suggest https://bugzilla.redhat.com/show_bug.cgi?id=1045350 as a blocker
(REST error during VM creation via API).
I suggest 1038053 as a blocker.
I'd even implement the patches myself if no one else can do it.
But I'd need some guidance what needs to get changed.
I'd like to suggest https://bugzilla.redhat.com/show_bug.cgi?id=987832 as a blocker.
with static ip assignment to a host the ovirtmgmt bridge can not be added to
This is basic functionality imho, which should just work.
I'd also like to suggest Bug 1038121 as a blocker.
There are two issues:
1. When you boot ubuntu via "run once" with cloud init
data, the vm does not boot completely unless you provide special kernel
2. when you reboot the vm the iso payload with cloud init data is still attached
to the vm, thus preventing correct booting (except when you set the kernel parameter).
Can this one get included in 3.4? I think the fix for it might be really simple:
(In reply to Sven Kieske from comment #5)
depending on the fix…it may be too late for 3.4. However I agree on the importance.
(In reply to Michal Skrivanek from comment #6)
> (In reply to Sven Kieske from comment #5)
> depending on the fix…it may be too late for 3.4. However I agree on the
Michal, it's not an automation blocker so no need to postpone RC for it.
- you think it's important
- you can fix it before GA
- you're sure the patch is not risky and won't hurt the stability of the release
Feel free to add it to blockers for 3.4.0 GA.
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released