There is an "ansible" package which is up to version 7.0.0, and which almost no
one has any reason to use. It is a bundle of more than 100 distinct ansible
collection modules, more safely and consistently handled with the "ansible
collections" command.
There is no "ansible collections" command. Do you mean "ansible-galaxy"?
Let's have a discussion about that. What is the preferred method of doing this?
The "ansible-galaxy collections" command does not offer a way to "update"
installed collections.
% ansible-galaxy collection -h
usage: ansible-galaxy collection [-h] COLLECTION_ACTION ...
positional arguments:
COLLECTION_ACTION
download Download collections and their dependencies as a tarball
for an offline install.
init Initialize new collection with the base structure of a
collection.
build Build an Ansible collection artifact that can be published
to Ansible Galaxy.
publish Publish a collection artifact to Ansible Galaxy.
install Install collection(s) from file(s), URL(s) or Ansible
Galaxy
list Show the name and version of each collection installed in
the collections_path.
verify Compare checksums with the collection(s) found on the
server and the installed copy. This does
not verify dependencies.
options:
-h, --help show this help message and exit
For this reason I find using the 'ansible 7.0.0' with included community
collections easier to maintain.
Walter
--
Walter Rowe, Division Chief
Infrastructure Services, OISM
Mobile: 202.355.4123
On Jan 9, 2023, at 8:30 AM, Nico Kadel-Garcia <[email protected]> wrote:
On Sat, Jan 7, 2023 at 10:00 AM Zied Kharrat <[email protected]> wrote:
Hi everyone,
I used to run for my playbooks ansible v2.9 and now I'm testing ansible 2.13.
Playbooks are the same but when executing using 2.13, it tooks randomly for
some tasks long time (like freeze status for a long time).
No issue related to performance (cpu, ram, network).
Could you give me some advice?
Thanks
Note that because of the very confusing split and renumbering, you are
not testing "ansible 2.13". You're testing what is now called
"ansible-core 2.13". There is no "ansible" 2.13. There is an "ansible"
package which is up to version 7.0.0, and which almost no one has any
reason to use. It is a bundle of more than 100 distinct ansible
collection odules, more safely and consistently handled with the
"ansible collections" command. Avoid confusing the two, that way lies
madness.
It's tough to guess why ansible-core might be running slowly for you.
What operating system are you on? What version of python? Does this
happen with very simple tasks like auditing a list of hosts? Have you
turned off SSH hostkey logging, one of the most burdensome parts of
reaching out to hundreds and thousands of hosts at a time? Are you
running these both on the same operating system with the same
resources? It's very difficult to make a good guess without a lot more
hints.
--
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 view this discussion on the web visit
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fansible-project%2FCAOCN9rziorEGfLpKjsDOsYoDp6ex%252BBgF1VEVn37kOFmnhmYcQA%2540mail.gmail.com&data=05%7C01%7Cwalter.rowe%40nist.gov%7Cd76be0dbdc3d44494a6d08daf245b57c%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638088678452097967%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Z4whA8ldkDfYHv5pye3la6Au6ecaIoydWY5HGsfDm%2BI%3D&reserved=0.
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/1CBAB161-216F-4A5D-B68E-1805B47399CE%40nist.gov.
