Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1057360 - PRD34 - [RFE] remove ppc architecture
Summary: PRD34 - [RFE] remove ppc architecture
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.4.0
Assignee: Roy Golan
QA Contact: Ilanit Stein
URL:
Whiteboard: virt
Depends On:
Blocks: rhev3.4beta 1142926
TreeView+ depends on / blocked
 
Reported: 2014-01-23 22:07 UTC by Itamar Heim
Modified: 2014-09-18 12:24 UTC (History)
16 users (show)

Fixed In Version: 3.4.0-0.15.beta3.el6ev.noarch
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-09 15:09:37 UTC
oVirt Team: ---
Target Upstream Version:
sherold: Triaged+


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:0506 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Virtualization Manager 3.4.0 update 2014-06-09 18:55:38 UTC
oVirt gerrit 26078 None None None Never
oVirt gerrit 26105 None None None Never

Description Itamar Heim 2014-01-23 22:07:18 UTC
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

Comment 1 Sandro Bonazzola 2014-03-04 11:46:14 UTC
Hi Meital, can you grant QA ack? Thanks

Comment 2 Ilanit Stein 2014-03-17 17:31:54 UTC
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

Comment 3 Kiril Nesenko 2014-03-17 18:51:57 UTC
Eyal, Sandro should we ship correct pkg in av3.1 or av4 ?

- Kiril

Comment 4 Eyal Edri 2014-03-17 19:07:09 UTC
no, av3 has latest pkg:  3.4.0-0.1.beta.el6ev.noarch
see: http://bob.eng.lab.tlv.redhat.com/builds/latest_av/av3_version_info.html

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.
version  3.4.0-0.1.beta.el6ev.noarch

Comment 5 Ilanit Stein 2014-03-18 08:05:17 UTC
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)

Comment 6 Eyal Edri 2014-03-18 08:10:39 UTC
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.

Comment 7 Sandro Bonazzola 2014-03-18 08:18:54 UTC
(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.

Comment 8 Ilanit Stein 2014-03-19 08:12:50 UTC
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.

Comment 9 Roy Golan 2014-03-19 15:08:02 UTC
(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?

Comment 10 Roy Golan 2014-03-20 13:39:51 UTC
I saw on Artyom av3 setup there are no PPC entries. 
Artyom can you confirm?

Comment 11 Artyom 2014-03-20 13:44:05 UTC
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.

Comment 12 Artyom 2014-03-20 13:49:52 UTC
Verified on av3

Comment 13 Ilanit Stein 2014-03-23 07:52:10 UTC
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.

Comment 14 Ilanit Stein 2014-03-25 10:44:11 UTC
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.

Comment 15 Roy Golan 2014-03-25 12:01:14 UTC
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.

Comment 16 Ilanit Stein 2014-04-29 12:44:22 UTC
Verified on av7.
no ppc option under cpu architecture any more.

Comment 18 errata-xmlrpc 2014-06-09 15:09:37 UTC
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.

http://rhn.redhat.com/errata/RHSA-2014-0506.html


Note You need to log in before you can comment on or make changes to this bug.