'common' role updates my app RPM and prevents a handler to execute later on

[Azul Inho]

In my role "common" I have:

- name: yum install OS updates                                                                                                                  
   shell: yum update -y                                                                                                                        

and then in my "application" role I have:

- name: install app1                               
  yum: name=app1 state=present
  notify:
     - restart app1


This app1 is built in house and deployed to a local yum repo managed by jenkins, so every time I run the "common" role it gets updated to the latest version. As a result when the 'application' role runs my 'app1' no longer needs to be updated so my restart app1 handler never gets executed.

Any ideas how to 'fix this' ?
Today I am simply restarting app1 every time I run ansible on this host which is not ideal.

[Petros Moisiadis]

> --
> You received this message because you are subscribed to the Google
> Groups "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to ansible-proje...@googlegroups.com.
> To post to this group, send email to ansible...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/47f7a6df-7d9c-423f-9d24-d72c20450084%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

Exclude your app from 'yum update' like this: 'yum -x app1 -y update'

[Azul]

that's an approach,
however that '-x list' is likely to grow really quickly as it will require every service list which I restart after an update.

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/sY63qib6f9c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/5314A939.8090709%40yahoo.gr.

[Petros Moisiadis]

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAMP%3DowhVtO6mWT%3DUL5Lw2JAEWqZ5F3e1dgbtHw3wnCu9z9sDpQ%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

You can always define and maintain a list variable with the excluded packages.

Then, you may make your task look like this:

- name: yum install OS updates
  shell: yum -x {{ excluded_packages|join('-x ') }} -y update

Or create /etc/yum.conf from a template with an equivalent 'exclude={{ excluded_packages|join(' ') }}' line in its [main] section.

[Johan Wärlander]

I'd normally have the RPM do the work of restarting after installation (upgrade), at least if it's always to be done, and is a safe thing. Given your role above, that seems to be true.. If so, you would only need the "common" role.

Now, if you need to reconfigure stuff after installing the application, then you would of course put that in a separate role, and notify after changing the config so the app will get restarted.

[Azul Inho]

yes, that's what I am looking into now.

I deploy the configuration for the app through a different task, which doesn't change very often.
caking the RPM-initscripts to restart the app looks like the cleanest way forward.

[James Cammarata]

Are your in-house app RPMs in a custom yum repo? Because you could very easily exclude that and do your system upgrade by using the yum module rather than shell:

yum: state=latest name=* disablerepo=custom_repo_here

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/06cdad28-2a24-485f-9799-4d1cad032af2%40googlegroups.com.

[Azul]

ooooooOOOOOOooooo that's quite handy

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/sY63qib6f9c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAFg%2Bn8RMFQicrU-%3D5Occ%2BewzFjCyGxXDTHDWGWMp3t8Md0Fk_Q%40mail.gmail.com.