1. rhev-4.0.0-10 doesn't have rhevm-spice-client-xxx packages. 2. Console Client Resources at webportal leads to page that shows : Internal Server Error This packages provide essential software for client. SpiceQE tests for RHEVM4.0 depend on those packages.
Not sure if I understand the issue. Maybe Uri can help here as well. Taking a look on brew (https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=494709) I can see the rhevm-spice-client-xxx and download them. So, I'm not exactly sure how you guys are blocked or whether this is the right component for your issue.
Andrei, can you manually install the packages on the RHEV-M server: yum install rhevm-spice-client*4.0* If you can, does that work around the problem ?
Let us take a look at RHEVM 3.6: # rpm -q --whatrequires rhevm-spice-client-x64-msi rhevm-3.6.4.1-0.1.el6.noarch At RHEVM 4.0: # rpm -qR rhevm | grep spice nothing # rpm -qa | grep spice nothin Console Client Resources at webportal leads to page that shows : Internal Server Error I think that this is a big issue. I would suggest to close this bug as those packages are automatically installed with RHEV-M.
That's what I suspected, which is why I asked about manual installation of the rhevm-spice-client packages. It seems the problem is in rhevm rpm/spec.
1. Marking as a regression. 2. Who's taking care of this?
(In reply to Yaniv Kaul from comment #6) > 2. Who's taking care of this? The person who maintains the rhevm package
Ticket is still under Spice team... Sandro - any idea who's taking care of those deps?
(In reply to Yaniv Kaul from comment #8) > Ticket is still under Spice team... Component: ovirt-engine, assigned to nobody/nobody, definitely something the spice team handles.
Created attachment 1163298 [details] A patch for ovirt-engine.spec to require rhevm-spice-client rpms
(In reply to Christophe Fergeau from comment #9) > (In reply to Yaniv Kaul from comment #8) > > Ticket is still under Spice team... > > > Component: ovirt-engine, assigned to nobody/nobody, definitely something the > spice team handles. Gluster is unlikely to handle this...
(In reply to Yaniv Kaul from comment #11) > Gluster is unlikely to handle this... I have no idea (as most external people) which team is going to handle this, and I could not find a "I don't know" team. At least, it clears up some confusion that it's still in the hands of the spice team as moving the bug to ovirt-engine was not enough for that.
IMO rhevm-branding-rhev it the correct package to require the installers as the upstream doesn't need them. Let's try Integration team in absence of Generic/NeedsTriage/... team, it's surely better choice than Gluster. :)
(In reply to Uri Lublin from comment #10) > Created attachment 1163298 [details] > A patch for ovirt-engine.spec to require rhevm-spice-client rpms Uri, thank you for the patch, I think it makes sense and it was not supposed to be dropped in the first place. "Integration" is indeed the right team for this. However, don't you also need to address bug 1342087 to completely resolve this?
(In reply to Uri Lublin from comment #10) > Created attachment 1163298 [details] > A patch for ovirt-engine.spec to require rhevm-spice-client rpms The patch that removed these [1] removed also -cab. Do we have these two again and can be restored too? [1] https://code.engineering.redhat.com/gerrit/71316
(In reply to Yedidyah Bar David from comment #16) > The patch that removed these [1] removed also -cab. Do we have these two > again and can be restored too? We do not have -cab rpms anymore (see bug 1324885), only MSI installers are to be used.
Linking to patch, but won't be merged (imo) before bug 1342087 is fixed.
Should this be MODIFIED?
(In reply to Yaniv Dary from comment #19) > Should this be MODIFIED? No. Was merged on master but not on 4.0 branch. Eyal asked to delay this. Now added link to 4.0 patch. Sorry for not doing this earlier.
verified on rhevm-4.0.0.6-0.1.el7ev.noarch [root@qe-xio1 ~]# rpm -qa | grep rhevm-spice rhevm-spice-client-x64-msi-4.0-2.el7ev.noarch rhevm-spice-client-x86-msi-4.0-2.el7ev.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1743.html