Sandro, after my mention my two bugs was closed as deprecated feature of "old Cinder integration". But actually no one oVirt 4.4 doc mentioned about deprecations/cautions/warnings.
How do you think, as manager of project, it's okay to just broke working code due loose tests and then deprecate it just by wave a hand?🤷♂️
Thanks,kSent from my iPhoneOn 21 Dec 2020, at 18:09, Sandro Bonazzola <sbonazzo@redhat.com> wrote:_______________________________________________Il giorno lun 21 dic 2020 alle ore 15:57 Konstantin Shalygin <k0ste@k0ste.ru> ha scritto:On 21.12.2020 16:22, Sandro Bonazzola wrote:
The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020.
Sandro, is any plans to fix for OpenStack provider regressions for 4.4 release?
I see you opened two bugs about it:Bug 1904669 - oVirt 4.3 -> 4.4 production upgrade: OpenStack Block Storage Provider (Cinder) regressionPlease consider most of the developers are going to be on vacation due to the upcoming holidays.I think storage team is looking into this but I see above bugs have not been targeted yet so a deeper investigation may be needed.
Thanks,
k
--Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GYAVGLTXHRGK27LWCGDAVFQGAIZMY2FC/
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV