Re: [Spacewalk-list] update hostname identifiers
Thanks. Is correct the solution, in SpaceWalk update hardware/packages profiles. regards Javier Valencia. De: Robert Paschedag Enviado: martes, 29 de agosto de 2017 11:55 p. m. Para: spacewalk-list@redhat.com; Valencia ...; spacewalk-list@redhat.com Asunto: Re: [Spacewalk-list] update hostname identifiers Am 30. August 2017 01:07:54 MESZ schrieb "Valencia ..." : >Hello, > >We need to update the host identifiers of the client computers >registered in SpaceWalk, I need to update them, but in SpaceWalk I can >not find update the hostname, and in database it has triggers. > >is there any way update the hostnames? > >regards > >Javier Valencia. I think a "rhn-profile-sync" on the clients should update that information. Robert ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] bug in channel.software.mergeErrata?
Am 30. August 2017 15:33:37 MESZ schrieb "Lichtinger, Bernhard" : >Hello, > >I see a strange behavior of spacewalk using >spacewalk-manage-channel-lifecycle: >Everytime I promote a channel all erratas which source and destination >channel have in common are removed from the source channel. > >For example: source channel has 4 (newer) errata more than the >destination channel. Then after running >"spacewalk-manage-channel-lifecycle -c source_channel --promote" my >destination channel has all old errata plus the 4 new ones, but my >source channel has only the 4 new errata left. > >The rpm packages in each channel are still linked to the errata, but >the source channel looses all "old" erratas. > >It happens with all my channels, RHEL-6,7 and SLES-11,12. > >I have spacewalk-2.6 on centos-7. I can also reproduce the behavior on >my test machine with spacewalk-2.6 on centos-6: >I have 2 phases for spacewalk-manage-channel-lifecycle defined: test >and prod. >So I have 3 baselines of channels: daily (is synced daily with upstream >repos), test and prod. > >For a fresh start I clear all erratas from the database: >rhnschema=# truncate rhnErrata CASCADE;; > >After a full sync of daily with upstream repo, errata count for my >channels: >daily: 590 >test: 0 >prod: 0 > >After "spacewalk-manage-channel-lifecycle -c daily --promote" errata >count for my channels: >daily: 590 >test: 590 >prod: 0 > >After "spacewalk-manage-channel-lifecycle -c test --promote" errata >count for my channels: >daily: 590 >test: 590 >prod: 590 > >So far everything is ok. > >Now I after a second "spacewalk-manage-channel-lifecycle -c daily >--promote" errata count for my channels: >daily: 0 >test: 590 >prod: 590 > >And after a second "spacewalk-manage-channel-lifecycle -c test >--promote" errata count for my channels: >daily: 0 >test: 0 >prod: 590 > >With the next sync of daily with upstream daily gets again all erratas: >daily: 590 >test: 0 >prod: 590 > >And this cycle can go on and on. > >I am not sure, but I think this started after the upgrade from 2.5 to >2.6, but I could not find any relevant changes in the source code of >the channel.software.mergeErrata API call. This is all code which was >not touched in recent times. > >So, is this a bug in spacewalk or did I only break my installations? > > >Regards, >Bernhard Sounds like an intersection instead of a union. Robert ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
[Spacewalk-list] bug in channel.software.mergeErrata?
Hello, I see a strange behavior of spacewalk using spacewalk-manage-channel-lifecycle: Everytime I promote a channel all erratas which source and destination channel have in common are removed from the source channel. For example: source channel has 4 (newer) errata more than the destination channel. Then after running "spacewalk-manage-channel-lifecycle -c source_channel --promote" my destination channel has all old errata plus the 4 new ones, but my source channel has only the 4 new errata left. The rpm packages in each channel are still linked to the errata, but the source channel looses all "old" erratas. It happens with all my channels, RHEL-6,7 and SLES-11,12. I have spacewalk-2.6 on centos-7. I can also reproduce the behavior on my test machine with spacewalk-2.6 on centos-6: I have 2 phases for spacewalk-manage-channel-lifecycle defined: test and prod. So I have 3 baselines of channels: daily (is synced daily with upstream repos), test and prod. For a fresh start I clear all erratas from the database: rhnschema=# truncate rhnErrata CASCADE;; After a full sync of daily with upstream repo, errata count for my channels: daily: 590 test: 0 prod: 0 After "spacewalk-manage-channel-lifecycle -c daily --promote" errata count for my channels: daily: 590 test: 590 prod: 0 After "spacewalk-manage-channel-lifecycle -c test --promote" errata count for my channels: daily: 590 test: 590 prod: 590 So far everything is ok. Now I after a second "spacewalk-manage-channel-lifecycle -c daily --promote" errata count for my channels: daily: 0 test: 590 prod: 590 And after a second "spacewalk-manage-channel-lifecycle -c test --promote" errata count for my channels: daily: 0 test: 0 prod: 590 With the next sync of daily with upstream daily gets again all erratas: daily: 590 test: 0 prod: 590 And this cycle can go on and on. I am not sure, but I think this started after the upgrade from 2.5 to 2.6, but I could not find any relevant changes in the source code of the channel.software.mergeErrata API call. This is all code which was not touched in recent times. So, is this a bug in spacewalk or did I only break my installations? Regards, Bernhard smime.p7s Description: S/MIME cryptographic signature ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
