The bug report should go here: https://bugs.launchpad.net/tripleo/+filebug

* Fill in the summary, click next, and then provide everything you can within the body. Once the bug is created, you can upload files (like the mentioned diff) to the bug report. Any and all information you can share is helpful in tracking down what is going on; please also include repos enabled so we can try and recreate the issue locally.

Sorry for the issues you've run into, but thanks again for reporting them. If you have any questions let us know.

--

Kevin Carter
IRC: Cloudnull

On Tue, May 5, 2020 at 3:40 PM Ruslanas Gžibovskis <ruslanas@lpic.lt> wrote:

I will file a launchpad bug, Tomorrow, today almost sleeping ;)

nope, only tripleo-ansible, I have 3 versions available, 0.4.0 0.4.1 and 0.5.0. 

0.4.1 - works, 0.5.0 do not.

[stack@remote-u ~]$ paunch --version
paunch 5.3.1
[stack@remote-u ~]$ rpm -qa | grep -i paunch
python2-paunch-5.3.1-1.el7.noarch
paunch-services-5.3.1-1.el7.noarch
[stack@remote-u ~]$ uname -a
Linux remote-u.tecloud.sample.xxx 3.10.0-1127.el7.x86_64 #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
[stack@remote-u ~]$

Would be very helpful if you could share or howto, or steps to place that bug report :)

https://bugs.launchpad.net/openstack/+filebug ? This one? Which project? tripleo?

How to name it, so it would be understandable? 

Which logs would you need? would be suficient with ansible.log and ansible-playbook-2 -vvvv .... last output, with error message?

I also can provide a diff for what is changed in that exact file. And package contents from 0.4.1 and 0.5.0 

if you need more or less, just mention here, or after I launch a bug report, I can recreate VM and try setting it up.