Description of problem: ovirt-release-master for centos doesn't contain Marek's people.redhat.com or copr repo, so an old copy of ovirt-web-ui in snapshots-static is used on a fresh c7 machine Version-Release number of selected component (if applicable): 4.2.4
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
I'm not sure adding the centos copr repo from mlibra to master release rpm is the right thing to do. ovirt-web-ui is an oVirt project and should be built nightly in Jenkins or TravisCI go through OST (selenium) testing and land on ovirt-master-snapshot automatically. Last patch tested on Jenkins for this project is from February 2017: https://jenkins.ovirt.org/job/ovirt-web-ui_master_github_check-merged-el7-x86_64/ I see Travis CI is testing this (example: https://travis-ci.org/oVirt/ovirt-web-ui/builds/411249261?utm_source=github_status&utm_medium=notification ) I think that right thing to do here should be add the missing automation piece to get a rpmbuild added to the change queue after merge of the PR. On 4.2/stable we publish the released builds from mlibra copr into 4.2 stable repo. On fedora side we just included the copr repo being fedora not fully supported yet. Marek, you're the maintainer there, what do you think?
I took this over for Marek :) > I think that right thing to do here should be add the missing automation piece to get a rpmbuild added to the change queue after merge of the PR. I agree. But how to do that without having ovirt CI do the builds? We want to keep travis for now.
It was intended to keep ovirt-web-ui as an independent project building on common infrastructure (like travis or github). The project integrates on API level only and from this perspective it is just one of (multiple) clients. Historically, oVirt's automation was added to the project but removed later for the reasons stated above. Builds are published to yum repo under people.redhat.com. Any other stable location (means not copr) should be ok. Selected releases/builds were added to oVirt's releng-tools for their inclusion in particular oVirt releases.
(In reply to Marek Libra from comment #4) > Any other stable location (means not copr) should be ok. I'm going to try copr actually. It's been heavily used for years and really should be stable by now. Thanks!
Any update on this? Is it still considered as a blocker?
Yes, the rpm now exists at https://copr.fedorainfracloud.org/coprs/ovirtwebui/ovirt-web-ui/ IMO it's a 4.2.6 blocker, but it's @Michal's decision
Why a blocker foe 4.2? This is about master only. 4.2 is done differently.
(In reply to Michal Skrivanek from comment #8) > Why a blocker foe 4.2? This is about master only. 4.2 is done differently. Oh, sorry for the noise then.
ovirt-release-master included in master repo contains this fix
Closed by mistake, moving back to qa -> verified
Hi Sandro. How does the current Doc Type and Doc Text look to you? Please feel free to update. Thanks!
(In reply to Rolfe Dlugy-Hegwer from comment #12) > Hi Sandro. How does the current Doc Type and Doc Text look to you? Please > feel free to update. Thanks! Looks good to me, thanks!
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.