[Starlingx-discuss] Potential failure in stx-openstack application

[Wensley, Barton]

If you issue the commands below when logged in as the root user, the username will default to "admin". You would then use the "admin" password that was configured when you ran config_controller.

Bart

From: Sun, Austin [mailto:austin.sun at intel.com]
Sent: March 12, 2019 11:57 PM
To: Wensley, Barton; starlingx-discuss at lists.starlingx.io
Subject: RE: Potential failure in stx-openstack application

Hi Bart:
Thanks your announcement in advance .

When I run docker login $REGISTRY,  it prompt to input user and password ,  where can get user/password ?

Thanks.
BR
Austin Sun.

From: Wensley, Barton [mailto:Barton.Wensley at windriver.com]
Sent: Wednesday, March 13, 2019 1:35 AM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] Potential failure in stx-openstack application

Public service announcement...

If you are using a load built after Friday, you may see the stx-openstack apply failing - the symptom will be that the ceph-pools-audit pod will be scheduled to run on controller-1 and will be stuck in the ImagePullBackOff state. The following bug is tracking the issue: https://bugs.launchpad.net/starlingx/+bug/1819720

To work around this, you can do the following on controller-1 (as root):
export KUBECONFIG=/etc/kubernetes/admin.conf
export REGISTRY_HOST=192.168.204.2
export REGISTRY_PORT=9001
export REGISTRY=${REGISTRY_HOST}:${REGISTRY_PORT}
docker login $REGISTRY
docker pull $REGISTRY/docker.io/port/ceph-config-helper:v1.10.3

You can then redo your "system application-apply stx-openstack" and all should be good.

Bart

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190313/0256ff17/attachment-0001.html>