Marc Patermann schrieb (16.02.2015 14:22 Uhr):
Marc Patermann schrieb (16.02.2015 14:07 Uhr):
I ran the playbook again and it tells the openldap2-client rpm
"changed", so it does update:
TASK: [install LDAP RPMs]
*****************************************************
ok: [server] => (item=libdb-4_8)
changed: [server] => (item=openldap2-client)
ok: [server] => (item=libldap-2_4-2)
ok: [server] => (item=libldap-2_4-2-32bit)
ok: [server] => (item=openldap2)
When I checked, this is not the whole truth:
openldap2-client-2.4.40-0 Mon 16 Feb 2015 02:08:35 PM CET
openldap2-2.4.40-0 Mon 16 Feb 2015 02:08:30 PM CET
libldap-2_4-2-2.4.40-0 Mon 16 Feb 2015 02:08:29 PM CET
Not only the client rpm did update, two other did too, but ansible did
not tell!
well, openldap2-client depends on libldap-2_4-2 and on this depends
openldap2. So all three package update together.
But ansible does not tell.
I suspect, that when ansible comes to the next item - libldap-2_4-2 -
this is already updated from the previous item, so it is "OK".
Is this the way it is intended to be?
Marc
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/54E33DA2.1060406%40ofd-z.niedersachsen.de.
For more options, visit https://groups.google.com/d/optout.
