On Tue, May 26, 2020 at 11:02 PM Ruslanas Gžibovskis <ruslanas@lpic.lt> wrote:
hi all again.

I still and still and again fail on similar steps.
Using CentOS7 and eth# as net device names.
still running on tripleo-ansible version number 4.1.0 (instead of 5.0.0) which should be fixed [0].

You mentioned tripleo-ansible but the link is for a new release of paunch. I understand you need a build for paunch-5.3.2. We are in the process and building it and pushing to train repos in centos mirrors. In the meanwhile you can get the python2-paunch package from https://trunk.rdoproject.org/centos7-train/consistent/
 

1) failing on OVN config, should I try not using OVN? just OVS?

2) first most annoying problem is that on a first deployment it cannot connect to the controller/compute, but I can ssh using ssh -l heat-admin IP
BUT, on the second launch it is always able to connect from first attempt.

3) When using undercloud as repo for container images, it fails, as undercloud ins not added to insecure registries, how should I add it? should it be specified in undercloud.conf as insecure registry?

could you please give me some hints, please?


external links:


On Wed, 13 May 2020 at 20:14, Ruslanas Gžibovskis <ruslanas@lpic.lt> wrote:
Hi all,

I am running this deployment described here [1].
I am getting error on: Start containers for step 4 using paunch
Error in link bellow [2]
Running podman containers [3]


links:
--
Ruslanas Gžibovskis
+370 6030 7030


--
Ruslanas Gžibovskis
+370 6030 7030
_______________________________________________
users mailing list
users@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: users-unsubscribe@lists.rdoproject.org