On Fri, Sep 23, 2011 at 12:09:39PM -0300, Marcelo Moreira de Mello wrote:
>
> Yes. rhncfg-client get complains and print into the screen the files which
> were not able to be deployed. Although, we can see a lot of sysadmin using
> the rhncfg-client get at %post section in their kickstart, where they will
> not be able to see such warning too. In this case per example, we have a
> customer which expects that rhn_check works deploying half of files, but I do
> agree with you that in some other cases, we don't want the machine to be
> left in an inconsistent state.
>
> I think that we can offer to the users an option to make such behavior with a
> tunable parameter. Per example, we can add a new option at
> rhn-actions-control --enable-half-deploy or --enable-unbatch which turns
> rhn_check able to perform unbatched deployments. Please, check the comment
> https://bugzilla.redhat.com/show_bug.cgi?id=737698#c1 regarding the
> customer's expectations.
>
> What do you think?
My preference would be to keep the current rhn_check (strict)
behaviour and change the rhncfg-client get behaviour to
- default to the current behaviour on terminal and to
strict behaviour of stdout is not a terminal;
- have command-line option to force either the strict or
non-strict behaviour.
--
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
