Hi
On Tue, Jul 22, 2014 at 02:41:53PM -0700, Michael Palumbo wrote:
> So there is no solution to avoid being stuck on the following? It happens to
> me
> often when I am upgrading the system!
> - name: upgrade all safe packages
> sudo: yes
> apt: upgrade=safe
>
> Is there at least a way to s
I use a screen trick but mostly useful when using commands modules.
Anyway, if it hangs doing apt upgrade, the behavior should be the same
if your run it as a command.
- debug: msg="Please, connect to {{ inventory_hostname }}, screen -r,
and respond the possible questions."
when: ansible_h
This is a misunderstanding of force-handler behavior.
You would run-it again with --force-handlers, and any handlers would run,
whether notified or not.
Don't control-C the second run :)
On Wed, Jul 23, 2014 at 1:20 PM, Michael Palumbo <
michael.palumb...@gmail.com> wrote:
> I just tried to
I just tried to run my playbook with --force-handlers and did CTRL+C: it
stopped it right away and the handlers were not notified.
Does it work for you?
I use ansible 1.6.7
Thanks.
On Wed, Jul 23, 2014 at 9:53 AM, Michael Palumbo <
michael.palumb...@gmail.com> wrote:
> Does that also work when
Does that also work when one task fails and the playbook stops?
Does it work with the tasks of the roles as well?
On Wed, Jul 23, 2014 at 8:30 AM, Michael DeHaan wrote:
> When you kill a playbook you can use --force-handlers to make sure
> handlers on a repeated runs.
>
>
> On Tue, Jul 22, 201
When you kill a playbook you can use --force-handlers to make sure handlers
on a repeated runs.
On Tue, Jul 22, 2014 at 5:41 PM, Michael Palumbo <
michael.palumb...@gmail.com> wrote:
> So there is no solution to avoid being stuck on the following? It happens
> to me often when I am upgrading the
So there is no solution to avoid being stuck on the following? It happens
to me often when I am upgrading the system!
- name: upgrade all safe packages
sudo: yes
apt: upgrade=safe
Is there at least a way to see the progress? Looking at some logs on the
machine?
The state of my machine is me
apt should never need a parameter to not hang, however some *specific*
packages can sometimes be poorly coded.
Not saying that's the case here.
I'd first check your ansible version and then file a bug with steps to
reproduce.
On Thu, Jul 10, 2014 at 7:45 PM, Michael Palumbo <
michael.palumb...@
What is the parameter of the apt module to use to avoid that?
I run the following and it hangs...
- name: update APT package cache
sudo: yes
apt: update_cache=yes
- name: upgrade all safe packages
sudo: yes
apt: upgrade=safe
Thanks
--
You received this message because you are subscribed to t
Thank you for your answers. I will use your apt module.
But just for the record - I always rollback to fresh virtual machine, so
the reason for hanging is not double task execution for sure.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
You should absolutely use the apt module.
You can install multiple packages in a single step by using "with_items"
and there's a flag for controlling whether recommended packages are
installed (see module docs).
I suspect as for the commands not being interactive the second time it was
because yo
you can execute shell commands, just not ones that expect interactivity as
they hold the tty (this happens with any background ssh execution).
for apt commands, yes use the apt module, it takes care of 99% f these
issues.
--
You received this message because you are subscribed to the Google Grou
Thanks for answer.
However, apt is not the only task that hangs without ANY information why.
Another example:
shell: apt-get install --no-install-recommends virtualbox-guest-utils &&
sudo apt-get install virtualbox-guest-dkms
Should I always use your apt module? Why can't I just execute simple
13 matches
Mail list logo
