Re: [Spacewalk-devel] New serializer returning array of arrays instead of array of hashes
On Tuesday 28 of August 2012 00:56:38 Aron Parsons wrote:
I added the ContentSourceFilterSerializer recently
(fb091b6a20074fc861840952091e36b10c06..78e04edac79095c52849f300f0a3f170d
a0a0db7) for the channel.software.listRepoFilters API function but can't get
it to return exactly what I want. Instead of returning an array of
hashes, it returns an array of arrays.
Returns:
[ [1, '+', 'cobbler'] ]
What I want:
[ {'sortOrder' : 1, 'flag' : '+', 'filter' : 'cobbler'} ]
Any help? In looking at most of the other serializers, I really don't
see what's out of place.
Your problem was that the ContentSourceFilter.findBySourceId query didn't
return objects of the ContentSourceFilter class, so they were not recognized
to be passed to the ContentSourceFilterSerializer.
Fixed in 31fc7f49.
Tomas
--
Tomas Lestach
RHN Satellite Engineering
/aron
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Bootstrap image feature
On Wed, Aug 08, 2012 at 11:29:27AM +0200, Uwe Gansert wrote:
On 02.08.2012 11:15, Jan Pazdziora wrote:
* inventing a new architecture bootstrap-linux that automatically
gets the new entitlement during registration.
Could you please explain some more why new architecture is needed?
Won't we actually need to know what architecture (the physical one)
the machine is?
I wanted to clean up the patch today and noticed, that we still need
the architecture.
The architecture is directly connected to the new
bootstrap-entitlement in the database via
rhnServerServerGroupArchCompat table:
insert into rhnServerServerGroupArchCompat ( server_arch_id,
server_group_type)
values (lookup_server_arch('bootstrap-linux'),
lookup_sg_type('bootstrap_entitled'));
insert into rhnServerServerGroupArchCompat ( server_arch_id,
server_group_type)
values (lookup_server_arch('bootstrap-linux'),
lookup_sg_type('provisioning_entitled'));
if a machine registers with that arch, it'll get the
bootstrap-entitlement automatically.
Please correct me if I'm wrong or misunderstood something but I'm
afraid, we still need the arch.
Well, the question still is, why does it have to exist at all (and be
connected)? We should be able to figure out the real architecture on
the running (bootstrapped) machine just fine.
And if we use the activation key method for adding the entitlement
instead of the bootstrap-linux, it shouldn't be needed.
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] small license issues
On Fri, Aug 03, 2012 at 02:20:20PM +0200, Michael Calmer wrote: Hi, Am Donnerstag, 31. Mai 2012, 14:43:49 schrieb Michael Calmer: Hi, our legal guys reviewed the spacewalk packages and found some small issues which should be easy to verify and fix. We found another issue in the package spacewalk-remote-utils. he spec say GPLv3+ but the COPYING file is a GPLv2 one. Which one is correct? The COPYING file. I've now fixed the .spec in Spacewalk master, tagged as spacewalk-remote-utils-1.8.4-1. Thank you for pointing this out. -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
