<div dir="ltr"><div>Any ideas?</div><div><br></div><div>No matter what I tried to do with ansible.conf, the same problem :</div><div>- using one -v the deployment goes till the end</div><div>- using more -v the deployment gets stuck somewhere.</div><div><br></div><div>Here is my ansible.conf</div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">[defaults]
</span><br>host_key_checking=False
<br>pipelining=True
<br>forks=100
<br>log_path=/home/deployer/myansiblelogs/log.txt
<br>display_args_to_stdout = True<br></span></div><div><br></div><div>I commented on all of them without success. I get the same behavior.<br></div><div><br></div><div>Regards<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mar. 25 oct. 2022 à 16:06, wodel youchi <<a href="mailto:wodel.youchi@gmail.com">wodel.youchi@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>I think I found what causes the problem, but I don't understand why.</div><div><br></div><div>I removed the verbosity, i.e I removed -vvv I only kept just one and I disabled ANSIBLE_DEBUG variable, and voila the deployment went till the end.</div><div>First I suspected the tmux process, some kind of buffer overflow because of the quantity of the logs, but then I connected to the VM's console and it is the behavior.</div><div><br></div><div>With one -v the process goes without problem, but if I put more -vvv it gets stuck somewhere.</div><div>If someone can explain this to me!!!!???<br></div><div> <br></div><div><br></div><div><br></div><div>Regards.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le lun. 24 oct. 2022 à 14:00, wodel youchi <<a href="mailto:wodel.youchi@gmail.com" target="_blank">wodel.youchi@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Anyone????<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le lun. 24 oct. 2022 à 07:53, wodel youchi <<a href="mailto:wodel.youchi@gmail.com" target="_blank">wodel.youchi@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Hi,<div dir="auto"><br></div><div dir="auto">My setup is simple, it's an hci deployment composed of 3 controllers nodes and 6 compute and storage nodes.</div><div dir="auto">I am using ceph-ansible for deploying the storage part and the deployment goes well.</div><div dir="auto"><br></div><div dir="auto">My base OS is Rocky Linux 8 fully updated.</div><div dir="auto"><br></div><div dir="auto">My network is composed of a 1Gb management network for OS, application deployment and server management. And a 40Gb with LACP (80Gb) data network. I am using vlans to segregate openstack networks.</div><div dir="auto"><br></div><div dir="auto">I updated both Xena and Yoga kolla-ansible package I updated several times the container images (I am using a local registry).</div><div dir="auto"><br></div><div dir="auto">No matter how many times I tried to deploy it's the same behavior. The setup gets stuck somewhere.</div><div dir="auto"><br></div><div dir="auto">I tried to deploy the core modules without SSL, I tried to use an older kernel, I tried to use the 40Gb network to deploy, nothing works. The problem is the lack of error if there was one it would have been a starting point but I have nothing.</div><div dir="auto"><div dir="auto"><br></div><div dir="auto">Regards.</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Oct 23, 2022, 00:42 wodel youchi <<a href="mailto:wodel.youchi@gmail.com" target="_blank">wodel.youchi@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>Here you can find the kolla-ansible <b>deploy </b>log with ANSIBLE_DEBUG=1<br></div><div><br></div><div>Regards.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le sam. 22 oct. 2022 à 23:55, wodel youchi <<a href="mailto:wodel.youchi@gmail.com" rel="noreferrer" target="_blank">wodel.youchi@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>I am trying to deploy a new platform using kolla-ansible Yoga and I am trying to upgrade another platform from Xena to yoga.</div><div><br></div><div>On both platforms the prechecks went well, but when I start the process of deployment for the first and upgrade for the second, the process gets stuck.<br></div><div><br></div><div>I tried to tail -f /var/log/kolla/*/*.log but I can't get hold of the cause.</div><div><br></div><div>In the first platform, some services get deployed, and at some point the script gets stuck, several times in the modprobe phase.</div><div><br></div><div>In the second platform, the upgrade gets stuck on :</div><div><br></div><div>Escalation succeeded [204/1859]<br><20.3.0.28> (0, b'\n{"path": "/etc/kolla/cron", "changed": false, "diff": {"before": {"path": "/etc/kolla/cro<br>n"}, "after": {"path": "/etc/kolla/cron"}}, "uid": 0, "gid": 0, "owner": "root", "group": "root", "mode": "07<br>70", "state": "directory", "secontext": "unconfined_u:object_r:etc_t:s0", "size": 70, "invocation": {"module_<br>args": {"path": "/etc/kolla/cron", "owner": "root", "group": "root", "mode": "0770", "recurse": false, "force<br>": false, "follow": true, "modification_time_format": "%Y%m%d%H%M.%S", "access_time_format": "%Y%m%d%H%M.%S",<br> "unsafe_writes": false, "state": "directory", "_original_basename": null, "_diff_peek": null, "src": null, "<br>modification_time": null, "access_time": null, "seuser": null, "serole": null, "selevel": null, "setype": nul<br>l, "attributes": null}}}\n', b'')<br>ok: [20.3.0.28] => (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True<br>, 'image': '<a href="http://20.3.0.34:4000/openstack.kolla/centos-source-cron:yoga" rel="noreferrer" target="_blank">20.3.0.34:4000/openstack.kolla/centos-source-cron:yoga</a>', 'environment': {'DUMMY_ENVIRONMENT': 'ko<br>lla_useless_env', 'KOLLA_LOGROTATE_SCHEDULE': 'daily'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_f<br>iles/:ro', '/etc/localtime:/etc/localtime:ro', '', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) => {<br> "ansible_loop_var": "item",<br> "changed": false,<br> "diff": {<br> "after": {<br> "path": "/etc/kolla/cron"<br> },<br> "before": {<br> "path": "/etc/kolla/cron"<br> }<br> },<br> "gid": 0,<br> "group": "root",<br></div><div><br></div><div>How to start debugging the situation.<br></div><div><br></div><div>Regards.<br></div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>