August 2019 - Starlingx-discuss - lists.starlingx.io

[Starlingx-discuss] [Release] [Build] StarlingX release 2.0: We have a load!
by Scott Little 07 Aug '19

07 Aug '19

Yahoo! The first successful build of STX 2.0 RC1 is available. http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190807T13… Scott

5 4

[Starlingx-discuss] [Containers] Sanity Test - ISO 20190807
by Perez Ibarra, Maria G 07 Aug '19

07 Aug '19

Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-AUG-07 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190807T05…>) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs PASS ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs PASS ] Standard - External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs PASS ] =========================================== Regards Maria G.

3 2

[Starlingx-discuss] Help understanding an application-appy failure
by Saul Wold 07 Aug '19

07 Aug '19

Folks, I am getting a failure during application-apply on a new Baremetal install. I installed based on the image built over the weekend. It appears to be a timeout (see the attached log). Thoughts, suggestions to debug this further and if a bug is needed Thanks Sau! > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller [-] [chart=openstack-libvirt]: Error while installing release osh-openstack-libvirt: grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with: > status = StatusCode.UNKNOWN > details = "release osh-openstack-libvirt failed: timed out waiting for the condition" > debug_error_string = "{"created":"@1565150558.052442767","description":"Error received from peer","file":"src/core/lib/surface/call.cc","file_line":1017,"grpc_message":"release osh-openstack-libvirt failed: timed out waiting for the condition","grpc_status":2}" >> > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller Traceback (most recent call last): > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller File "/usr/local/lib/python3.6/dist-packages/armada/handlers/tiller.py", line 465, in install_release > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller metadata=self.metadata) > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller File "/usr/local/lib/python3.6/dist-packages/grpc/_channel.py", line 533, in __call__ > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller return _end_unary_response_blocking(state, call, False, None) > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller File "/usr/local/lib/python3.6/dist-packages/grpc/_channel.py", line 467, in _end_unary_response_blocking > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller raise _Rendezvous(state, None, None, deadline) > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with: > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller status = StatusCode.UNKNOWN > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller details = "release osh-openstack-libvirt failed: timed out waiting for the condition" > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller debug_error_string = "{"created":"@1565150558.052442767","description":"Error received from peer","file":"src/core/lib/surface/call.cc","file_line":1017,"grpc_message":"release osh-openstack-libvirt failed: timed out waiting for the condition","grpc_status":2}" > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller > > 2019-08-07 04:02:38.052 85578 ERROR armada.handlers.tiller ^[[00m > 2019-08-07 04:02:38.053 85578 DEBUG armada.handlers.tiller [-] [chart=openstack-libvirt]: Helm getting release status for release=osh-openstack-libvirt, version=0 get_release_status /usr/local/lib/python3.6/dist-packages/armada/handlers/tiller.py:531^[[00m > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.wait [-] [chart=openstack-openvswitch]: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-openvswitch)). None found! Are `wait.labels` correct? Does `wait.resources` need to exclude `type: pod`?^[[00m > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada [-] Chart deploy [openstack-openvswitch] failed: armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-openvswitch)). None found! Are `wait.labels` correct? Does `wait.resources` need to exclude `type: pod`? > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada Traceback (most recent call last): > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 223, in handle_result > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada result = get_result() > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 425, in result > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada return self.__get_result() > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada raise self._exception > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada result = self.fn(*self.args, **self.kwargs) > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/armada.py", line 212, in deploy_chart > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada prefix, known_releases) > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/chart_deploy.py", line 242, in execute > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada chart_wait.wait(timer) > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 130, in wait > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada wait.wait(timeout=timeout) > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 292, in wait > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada modified = self._wait(deadline) > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada File "/usr/local/lib/python3.6/dist-packages/armada/handlers/wait.py", line 349, in _wait > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada raise k8s_exceptions.KubernetesWatchTimeoutException(error) > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada armada.exceptions.k8s_exceptions.KubernetesWatchTimeoutException: Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-openvswitch)). None found! Are `wait.labels` correct? Does `wait.resources` need to exclude `type: pod`? > 2019-08-07 04:02:38.129 85578 ERROR armada.handlers.armada ^[[00m > 2019-08-07 04:02:38.162 85578 DEBUG armada.handlers.tiller [-] [chart=openstack-libvirt]: GetReleaseStatus= name: "osh-openstack-libvirt" > info { > status { > code: FAILED > } > first_deployed { > seconds: 1565148757 > nanos: 968267140 > } > last_deployed { > seconds: 1565148757 > nanos: 968267140 > } > Description: "Release \"osh-openstack-libvirt\" failed: timed out waiting for the condition" > } > namespace: "openstack" > get_release_status /usr/local/lib/python3.6/dist-packages/armada/handlers/tiller.py:539^[[00m

3 5

[Starlingx-discuss] [docs][meetings] docs team meeting minutes 8/7/2019
by Tullis, Michael L 07 Aug '19

07 Aug '19

For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike

1 0

[Starlingx-discuss] [build][multi-os]Proposal for new starlingx repo - stx-zuul-jobs
by Saul Wold 07 Aug '19

07 Aug '19

Folks, As I am doing the work for multi-os, I have created some Zuul ansible playbooks and some new roles to go along with that. We have also enabled (or will enable) some additional zuul jobs that use various scripts. These are currently being tested in the starlingx/fault repo, but need to be in a more generic location. In the past we have been putting scripts into stx-integ, which is not the most ideal location. I see that the "openstack" repo name space has an openstack-zuul-jobs, I think this is because zuul itself has a zuul-jobs which might conflict in the zuul namespace (this is just a guess). StarlingX would need a stx-zuul-jobs and it would contain new StarlingX specific Zuul playbooks and associated roles, along with other tools/scripts to support these playbooks and other StarlingX Zuul jobs. For example the recently added spec-tools to stx-integ could be moved this new repo. I have heard that the Infra team might be looking at some restructuring so that might play a role in the direction or creation of the repo. Maybe somebody from infra will pipe in here, or I will ping later. Thoughts? Thanks Sau!

2 4

[Starlingx-discuss] [build-report] STX_build_helm_charts - Build # 329 - Failure!
by build.starlingx＠gmail.com 07 Aug '19

07 Aug '19

Project: STX_build_helm_charts Build #: 329 Status: Failure Timestamp: 20190807T135448Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190807T03… -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-2.0/20190807T032530Z OS: centos DOCKER_BUILD_ID: jenkins-rc-2.0-20190807T032530Z-builder MY_REPO: /localdisk/designer/jenkins/rc-2.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190807T03… PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/2.0/centos/20190807T032530Z/logs PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/2.0/centos

1 0

[Starlingx-discuss] [build-report] STX_BUILD_2.0 - Build # 12 - Still Failing!
by build.starlingx＠gmail.com 06 Aug '19

06 Aug '19

Project: STX_BUILD_2.0 Build #: 12 Status: Still Failing Timestamp: 20190807T032530Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190807T03… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true

1 0

[Starlingx-discuss] [build-report] STX_build_helm_charts - Build # 327 - Failure!
by build.starlingx＠gmail.com 06 Aug '19

06 Aug '19

Project: STX_build_helm_charts Build #: 327 Status: Failure Timestamp: 20190807T055801Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190807T03… -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-2.0/20190807T032530Z OS: centos DOCKER_BUILD_ID: jenkins-rc-2.0-20190807T032530Z-builder MY_REPO: /localdisk/designer/jenkins/rc-2.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190807T03… PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/2.0/centos/20190807T032530Z/logs PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/2.0/centos

1 0

[Starlingx-discuss] Query about adding a new OpenStack service to StarlingX
by Akshay 346 06 Aug '19

06 Aug '19

Hello Team, I hope you all are doing good. I need to ask that can I install any other OpenStack service ( like zun or any other which is not installed ) on StarlingX 18.10 ? Please guide me if there is a way to add any additional OpenStack service to StarlingX 18.10 release. Best Regards, [cid:image001.jpg@01D46BAD.8F199640] DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

1 0

[Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 48 - Still Failing!
by build.starlingx＠gmail.com 06 Aug '19

06 Aug '19

Project: STX_build_lst_audit Build #: 48 Status: Still Failing Timestamp: 20190807T015352Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190807T01… -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-2.0/20190807T013000Z DOCKER_BUILD_ID: jenkins-rc-2.0-20190807T013000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/rc-2.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190807T01… PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/2.0/centos/20190807T013000Z/logs MASTER_JOB_NAME: STX_BUILD_2.0 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-2.0 PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/2.0/centos

1 0