<div dir="ltr"><div>Greetings,</div><div><br></div><div>I hope you all are well.  I have two virtualized Starling-X distributed cloud deployments (both which consist of 2 VMs for AIO HA central cloud and 2 VMs for AIO HA subcloud).  One is version 3.0 and the other is 4.0.  Both were created/installed following the official documentation:</div><div><br></div><div>- <a href="https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html">https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html</a></div><div>- <a href="https://docs.starlingx.io/deploy_install_guides/r3_release/openstack/install.html">https://docs.starlingx.io/deploy_install_guides/r3_release/openstack/install.html</a></div><div>- <a href="https://docs.starlingx.io/deploy_install_guides/r4_release/distributed_cloud/index.html">https://docs.starlingx.io/deploy_install_guides/r4_release/distributed_cloud/index.html</a></div><div>- <a href="https://docs.starlingx.io/deploy_install_guides/r4_release/openstack/install.html">https://docs.starlingx.io/deploy_install_guides/r4_release/openstack/install.html</a></div><div><br></div><div>My 3.0 deployment has both k8s and Openstack running on the central and subcloud clouds.  I didn't have any luck with stx-openstack version 1.0-9 "latest" stable at first, so I tried <a href="http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/helm-charts/stx-openstack-1.0-19-centos-stable-versioned.tgz">"versioned"</a>, which ended up working for me.  However, once I set my subcloud to "managed" in the central cloud with dcmanager, I never saw the Openstack identity sync status reach "in-sync", even after waiting a long time:</div><div><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><span style="font-family:monospace">[sysadmin@controller-0 ~(keystone_admin)]$ dcmanager subcloud show subcloud2<br>+--------------------------------+----------------------------+<br>| Field                          | Value                      |<br>+--------------------------------+----------------------------+<br>| id                             | 8                          |<br>| name                           | subcloud2                  |<br>...<br>| software_version               | 19.12                      |<br>| management                     | managed                    |<br>| availability                   | online                     |<br>| deploy_status                  | complete                   | <br></span></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><span style="font-family:monospace">...<br>| identity_sync_status           | in-sync                    |<br>| identity_openstack_sync_status | unknown                    |<br>| patching_sync_status           | in-sync                    |<br>| platform_sync_status           | in-sync                    |<br>+--------------------------------+----------------------------+</span><br></div></blockquote><div><br></div><div>Could anyone provide guidance on where to look in terms of pods, services, logs, etc, such that I might find a clue as to what the problem might be?  Am I possibly missing configuration or some other required step to enable the sync (beyond just setting the subcloud to "managed")?<br></div><div><br></div><div>For my 4.0 distributed cloud, I can't even get stx-openstack 1-0.49 (<a href="http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/helm-charts/stx-openstack-1.0-49-centos-stable-latest.tgz">"latest"</a> or <a href="http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz">"versioned"</a>) to install.  The keystone-api-proxy pod fails with the following error in its logs:</div><div><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><span style="font-family:monospace">$ kubectl logs pods/keystone-api-proxy-f<br>+ dcorch-api-proxy --config-file=/etc/dcorch/dcorch.conf --type identity<br>Traceback (most recent call last):<br>  File "/var/lib/openstack/bin/dcorch-api-proxy", line 5, in <module><br>    from dcorch.cmd.api_proxy import main<br>  File "/var/lib/openstack/lib/python2.7/site-packages/dcorch/cmd/api_proxy.py", line 42, in <module><br>    from dcorch.api.proxy.common import utils<br>  File "/var/lib/openstack/lib/python2.7/site-packages/dcorch/api/proxy/common/utils.py", line 26, in <module><br>    from dccommon.drivers.openstack import sdk_platform as sdk<br>  File "/var/lib/openstack/lib/python2.7/site-packages/dccommon/drivers/openstack/sdk_platform.py", line 26, in <module><br>    from dccommon.drivers.openstack.barbican import BarbicanClient<br>  File "/var/lib/openstack/lib/python2.7/site-packages/dccommon/drivers/openstack/barbican.py", line 23, in <module><br>    from barbicanclient import client<br><b>ImportError: No module named barbicanclient</b></span></div></blockquote><div><br></div><div>Has anyone else encountered this issue or know how to fix/work-around it?  It seems like some dependency is missing from the container image, but I'm not sure.</div><div><br></div><div>Any insights/feedback on these two issues would be greatly appreciated.  Thank you!</div><div><br></div><div>Regards,</div><div>Andrew<br></div></div>