On Fri, Jul 15, 2011 at 11:16:11AM -0300, Marcelo Moreira de Mello wrote:
> > * Will the new code work with kickstarts from current spacewalk which
> > contain 'touch .../script/all'? I mean if new rhncfg-* is installed so
> > it looks for .../script/run but no %postinst which renames
> > .../script/all to .../script/run has fired.
> Yes. If customer upgrade the rhncfg* packages, at the %post section, the
> file will be automatically renamed to 'run' if ../script/'all' exists.
> 
> rhncfg.spec
> 107 %post
> 108 test -f /etc/sysconfig/rhn/allowed-actions/script/all \
> 109     && mv /etc/sysconfig/rhn/allowed-actions/script/all
> /etc/sysconfig/rhn/allowed-actions/script/run
> 
> To new kickstarts, this the file will be deployed as expected.
> 
> KickstartFormatter.java
> 123         "touch /etc/sysconfig/rhn/allowed-actions/script/run";
> 
> Please, let me know if you have further questions.

It's the combination of Spacewalk 1.4 (or Satellite 5.3, 5.4) and new
rhncfg* being kickstarted.

The file is touched in the kickstart file only after the rhncfg*
packages were installed. So the %post scriptlet trick does not apply
(there is no file there when the package is being installed) and then
the script/all gets created and the package never sees it because it
was modified to only assume and use script/run.

-- 
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

Reply via email to