Description of problem:
Systems -> Activation Keys:
Users do not have the ability to specify the architecture of packages to
associate with an Activiation Key. When packages are associated with an
Activation Key via the UI, only the package name is supported/used (e.g.
libjpeg). Since package names do not reflect the architecture, the user cannot
control the specific package that will be installed on the client. If the user
attempts to associate an architecture in the package name (e.g. libjpeg.i386),
the package is added to the list; however, it is ignored when the activation key
is used because a package by that name does not exist.
From initial analysis, impacts to schema, UI, backend and API are anticipated.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. select Systems
2. select Activation Keys
3. update the list of packages associated with the key, attempting to specify
packages by name and arch (e.g. libjpeg, libjpeg.i386, libjpeg.x86_64)
4. re-register the client (rhnreg_ks) using the activation key specified
only those packages that were listed by package name will be installed during
all packages associated with the activation key should be installed
Note: when resolving this BZ, the implementation for communicating package
architecture may be handled differently than mentioned above...
https://fedorahosted.org/spacewalk/wiki/MultiArchEnhancements - Refer to wiki
page for more details on this issue. This page contains proposed solution;
however, since the solution details can change as the issue is further
investigated, it is not being included in the bug report.
Pradeep and I are working on the solution to this one under a remote branch (origin/multiarch).
The initial db and backend changes have been completed. I'm now working on the UI changes which includes porting the page to java.
Changes have been made to UI and backend to address this BZ.
UI commit: 41587d360f56d31991ce20ed0367b81a4d5ffc24.
This commit includes modifications to the UI to:
1. port the Activation Key -> Packages from perl to java
2. enhance the UI to enable users to optionally include a package architecture
when entering packages
If user provides a package name that does not exist in rhnPackageName, it will
If an archLabel is provided, it must be a valid one defined in
rhnPackageArch.label; otherwise, it will be assumed to be part of the package
name (e.g. libjpeg.i333 would generate a new package name by that name).
The XMLRPC APIs for ActivationKey have also been updated an will be documented
by a separate BZ.
https://bugzilla.redhat.com/show_bug.cgi?id=469264 created to address the API modifications. This BZ is not a dependency but include for additional info.
verified with spacewalk-java-0.4.14-1.el5