have any ideas on how to further debug this?
Kind regards,
Sven
Dick Visser schrieb am Donnerstag, 25. April 2024 um 13:36:06 UTC+2:
> I would terminate the host and spin up a fresh one.
> This means your host will be in a known clean state again.
>
> On Thu, 25 Apr 2024 at 12:45
but the problem
persists.
Is there a way to debug this further?
Simply turning the gathering of facts off is not an option, as we rely
heavily on host dependent facts in some of our roles.
Thanks in advance!
Regards,
Sven
--
You received this message because you are subscribed to the Google G
try something like this before adding your package
- name: Import key for mysql-repo
rpm_key:
state: present
key: http://repo.mysql.com/RPM-GPG-KEY-mysql
Best regards
Sven Probst
arrow.pr...@gmail.com schrieb am Samstag, 24. Oktober 2020 um 12:53:56
UTC+2:
> Hope someone w
witch.org/support/dist-docs/ovs-vsctl.8.txt mentions
> the option of generating output as JSON for that command.
> This will probably simplify your problem.
> Can you show some output with that option enabled?
>
> On Mon, 28 Sep 2020 at 19:45, Sven wrote:
> >
> > Hello guys,
Hello guys,
I am not quite sure how to describe this.
I have a simple task, which executes a shell command and register a
variable.
*- name: execute ovs-vsctl show command*
* shell: ovs-vsctl show*
* register: output*
This will give me stdout with different ports like this:
Port "7da0c92dc [.
Well I actually found the problem.
I had to set run_once:yes in the following part:
- name: set fact random2
set_fact:
randomserver: "{{ newlist | random}}"
run_once: yes
Now I get the correct Servers
Anyway, Thank you for your help Mr. Botka.
--
You received this mess
ervers, 3 servers, 2
servers, 1 server. The only Server that is consistent is server1var (whhich
is "server1")###
Maybe you have an idea what might cause that problem?
I saw in your github examples, that you already used random filter.
vbo...@gmail.com schrieb am Mittwoch, 9. Sept
Hello Everyone,
i have a role "x" that uses two default vars:
(roles/x/defaults/main.yml)
server1var: server1
server2var: server2
based on these vars, tasks are executed on server1 or server2
now I have a playbook that executes some tasks and then includes role "x":
tasks:
- name: fetch
way is to use template-module
with external template-file.)
Best regards,
Sven
--
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-projec
_ip'
Am Donnerstag, 15. Februar 2018 18:58:15 UTC+1 schrieb Sven Leupold:
>
> Hi
>
> I wonder if you experience the same problem with os_server if you run an
> openstack playbook twice or more.
>
> If I run os_server after the initial vm setup was successful, it alway
l,
"cloud": null,
"detailed": null,
"endpoint_type": "public",
"key": null,
"region_name": null,
"server": "test*",
"timeout&q
t; behaviour in os_server?
Thanks in advance
Sven
--
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-project+unsubscr...@googlegroups.com.
To post
Awesome, thanks! that explained a lot. Appreciate the help.
On Friday, September 15, 2017 at 10:39:19 AM UTC-4, Brian Coca wrote:
>
> yep
>
> or ":%s,"
>
>
> --
> --
> Brian Coca
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" g
And if I want a comma in between each one, it would look like this?
{{(":%s" % es_port + ",").join(groups['elasticsearch_servers']) + ":" +
es_port}}
right?
On Friday, September 15, 2017 at 10:29:11 AM UTC-4, Brian Coca wrote:
>
> dont stack moustaches:
>
> {{(":%s" % es_port).join(groups['el
So I'd like a variable port, not just a static one, so I'm using:
{{":{{ es_port }}, ".join(groups['elasticsearch_servers']) + ":{{ es_port
}}"}}
I realize I probably have a quote or something wrong, but can you show me
where?
Because I also tried:
{{":" + {{ es_port }}+ ", ".join(groups['e
Awesome! Thanks. I'll start looking into the templates and use those.
On Thu, Sep 14, 2017 at 1:47 PM Kai Stian Olstad <
ansible-project+l...@olstad.com> wrote:
> On 14. sep. 2017 19:19, Sven Hans Knecht wrote:
> > Kai,
> >
> > Is there a way to append
Scenario:
Trying to execute a yum command on a server.
Yum command looks like:
---
- name: upgrade all packages
yum:
name: '*'
state: latest
become: true
This task fails with the return code: you must be root to perform this
action.
This error code is generally associated wi
Kai,
Is there a way to append information to each one as well?
say I want a variable to append a port to each host
Hans
On Thursday, September 14, 2017 at 1:17:46 PM UTC-4, Sven Hans Knecht wrote:
>
> Oh, that's super handy. Because then it would expand dynamically.
>
> T
Oh, that's super handy. Because then it would expand dynamically.
Thanks!
On Thu, Sep 14, 2017 at 12:43 PM Kai Stian Olstad <
ansible-project+l...@olstad.com> wrote:
> On 14. sep. 2017 18:00, Sven Hans Knecht wrote:
> > I'm trying to install a cluster of Elasticsear
I found that I needed to be using:
[groups['groupname'][0]
Thanks!
On Thursday, September 14, 2017 at 12:00:12 PM UTC-4, Sven Hans Knecht
wrote:
> I'm trying to install a cluster of Elasticsearch servers and writing an
> ansible script to manage that.
>
> In my
I'm trying to install a cluster of Elasticsearch servers and writing an
ansible script to manage that.
In my hosts file I have something like:
[elasticsearch-servers]
elk-host-01
elk-host-02
elk-host-03
in side of my config file, I'd like it to do something like:
discovery.zen.ping.unicast.host
Is it possible to pull hosts from an inventory file as a variable to be
used?
Example:
Inventory File ###
[group_1]
host1
### Variable File ##
hostname: {{ host1 }}
I want to reduce the number of places that hosts need to be listed and use
the inventory file
I found a solution myself. The following playbook works as expected. This
should be added to the ec2 tutorial.
- name: pinging myself
hosts: tag_Name_Source
tasks:
- shell: ping {{ groups['tag_Name_Source'][0] }}
--
You received this message because you are subscribed to the Google G
"shell:" section.
Do I need to use a special syntax when using variables with {{ }}?
Am Donnerstag, 11. Dezember 2014 16:32:15 UTC+1 schrieb James Cammarata:
>
> Hi Sven, this is most likely due to the caching of data by the inventory
> script. You can set "cache_max_ag
is
undefined"
What is the right way to get the IP of the target machine?
I'm running Ansible 1.8.2 on Ubuntu.
Thanks for any hints.
/Sven
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from t
25 matches
Mail list logo