On Wed, Dec 13, 2017 at 12:37 PM, Michal Skrivanek
<michal.skrivanek(a)redhat.com> wrote:
> On 13 Dec 2017, at 09:58, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote:
>
>
>
> 2017-12-13 9:51 GMT+01:00 Michal Skrivanek <michal.skrivanek(a)redhat.com>:
> Hi Sandro,
> we’ve identified one more blocker for HE installations[1]. We plan getting it in
today if everything goes well, would be great if we can update the RC with new vdsm soon
after.
>
> Thanks,
> michal
>
> [1]
https://bugzilla.redhat.com/show_bug.cgi?id=1524119
>
> We have right now 3 blockers:
> ID▲ oVirt Team Product▲ Component▲ Assignee Status▼ Summary
Severity Priority▲
> 1522641 Node cockpit-ovirt Hosted Engine phbailey(a)redhat.com NEW
Hosted Engine deployment failed, there display 'Timed out... urgent unspecified
seems this still requires clarification. There is some misunderstanding between the
assignee and qe.
> 1525353 Network ovirt-engine BLL.Network eraviv(a)redhat.com NEW
vNIC mapping is broken on import from data domain - vNICs... urgent urgent
Dan, can you update why this is a urgent/urgent blocker? It doesn’t seem to qualify for
that severity. Import VM from SD and end up with empty mapping you can easily fix…that
hardly critically affects running workloads.
My only issue is that this was a P1 feature, and this regression was
reported this morning.
We now believe it does not affect the Ansible-driven disaster-recovery
flow, so we can wait with it to 4.2.1.