while ovirt has the PPC architecture, downstream rhevm builds should not include it.
no need to remove osinfo, etc. - just the config for the arch and cpu families should suffice
Hi Meital, can you grant QA ack? Thanks
Failed testing in av3, the cpu arch options still include ppc.
Further investigation on this problem with mskrivan, brought us to the conclusion that the problem is the rhevm-setup-plugins package is not updated.
av3 includes package rhevm-setup-plugins-3.4.0-0.0.master.20140207125249.el6_5
while it should have included rhevm-setup-plugins-3.4.0-0.0.master.20140304104652.el6ev
Eyal, Sandro should we ship correct pkg in av3.1 or av4 ?
no, av3 has latest pkg: 3.4.0-0.1.beta.el6ev.noarch
also verified on integration system this is the rpm that was taken.
so ilanit might have taken it from av2 or an old repo.
moving back to on_qa, please verify with version from AV3.
I had a rhevm, installed with av2, and then I run engine-cleanup.
The rhevm repo was changed from av2 to av3.
and then I run yum install rhevm, and engine-setup.
Since the rhevm-setup-plugins package was not updated, as it should have,
I suppose there is a problem with engine-cleanup\engine-setup, and not with the repos.
Can you please check (Please contact me for my setup details, if required)
adding sandro as need info on this verification.
this worked on integration tests as expected.
but sounds to me that you didn't upgrade the system.
(In reply to Ilanit Stein from comment #5)
> I had a rhevm, installed with av2, and then I run engine-cleanup.
> The rhevm repo was changed from av2 to av3.
> and then I run yum install rhevm, and engine-setup.
> Since the rhevm-setup-plugins package was not updated, as it should have,
> I suppose there is a problem with engine-cleanup\engine-setup, and not with
> the repos.
> Can you please check (Please contact me for my setup details, if required)
rhevm-setup-plugins was not updated due to bug #1076046 missing the yum group branding and due to av3 repodata/rhevmgroup.xml using <id>rhevm33</id> instead of <id>rhevm34</id>
as workaround, please run yum update.
On rhevm av3.1, with rhevm-setup-plugins-3.4.0-0.1.beta.el6ev.noarch,
for a new cluster, cpu architecture 'ppc64' is still available.
(In reply to Ilanit Stein from comment #8)
> On rhevm av3.1, with rhevm-setup-plugins-3.4.0-0.1.beta.el6ev.noarch,
> for a new cluster, cpu architecture 'ppc64' is still available.
did you run the setup again?
I saw on Artyom av3 setup there are no PPC entries.
Artyom can you confirm?
Checked on av3, when I update cluster it no ppc entries, also when I create new cluster until I choose CPU Name I have Cpu Architecture field visible, after that I choose CPU Name(no matter Intel or Amd), Cpu Architecture field disappear.
Verified on av3
My verification, on rhevm 3.4 (av3.1), refer to that when open a new cluster, the architecture drop down, still show the ppc option.
This option can be chosen, and a new cluster can be created successfully with it.
The bug was moved to failed_qa from the following reasons:
1. The cpu architecture option is still visible to the customer, while it shouldn't in rhevm.
2. Under cpu architecture the ppc option available, and can be chosen.
3. It is possible to choose the ppc option, and once the cpu name is set, the architecture field vanishes, the cluster is created,
but when we check in REST, the cluster architecture was set to X86_64.
So a customer may think he chose ppc arch, but in fact it didn't.
I had a constraint to remove/hide ppc only using setup plugin.
so to hide PPC from the drop down, I'll filter it out if there is no corresponding CPU type. this make sense everywhere.
Verified on av7.
no ppc option under cpu architecture any more.
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.