[katello-devel] katello-upgrade restarting services

[Sam Kottler]

How about checking if the service is running and then reacting based on
that. If the service is running then katello-upgrade command will exit and
alert the sysadmin that he/she should stop the service. If not, then
upgrade can continue.

Thoughts?

On Tue, Jul 24, 2012 at 9:27 AM, Jordan OMara <jomara at redhat.com> wrote:

> eric filed this bug: https://bugzilla.redhat.com/**show_bug.cgi?id=820280<https://bugzilla.redhat.com/show_bug.cgi?id=820280>
> og filed a similar one: https://bugzilla.redhat.com/**
> show_bug.cgi?id=837866<https://bugzilla.redhat.com/show_bug.cgi?id=837866>
> a pull request: https://github.com/Katello/**katello/pull/331<https://github.com/Katello/katello/pull/331>
>
> However, lzap & msuchy have brought up that this might be poor
> behavior or very confusing to a sysadmin and that they would want to
> almost always stop services themselves before starting the upgrade
> process. I don't have enough sysadmin experience to make a good
> decision so I wanted to bring it up to the list.
>
> tl;dr: katello-upgrade currently fails if you haven't stopped your
> services. the pull requests makes the script stop them for you
>
> my uninformed 2c: the patch is fairly innocuous because you can
> decline to have the script stop anything and exit
>
> DISCUSS
> --
> Jordan O'Mara <jomara at redhat.com>
> Red Hat Engineering, Raleigh
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/katello-devel/attachments/20120724/a497afc3/attachment.htm>