September 2019 - Starlingx-discuss

[Starlingx-discuss] Sanity Test - ISO 20190911
by Perez Ibarra, Maria G 11 Sep '19

11 Sep '19

Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-September-11 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190911T01…>) 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 - 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 ] Regards Maria G.

1 0

[Starlingx-discuss] repo tool and starlingX: where is the meta file?
by Dominig ar Foll (Intel Open Source) 11 Sep '19

11 Sep '19

Hello, I wanted to ease my tracking of StarlingX code and I notice that in the deprecated wiki and in some message on this mailing list, the use of the repo tool for syncing source was name. Unfortunately, I could not find anywhere, the location of the repo meta file that I need as input to achieve my easy/lazy tracking of all the project code. Would someone be able to point me to the adequate documentation ? Thanks. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre

4 4

[Starlingx-discuss] [build-report] STX_build_helm_charts - Build # 410 - Still Failing!
by build.starlingx＠gmail.com 11 Sep '19

11 Sep '19

Project: STX_build_helm_charts Build #: 410 Status: Still Failing Timestamp: 20190911T180210Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190909T23… -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190909T230000Z OS: centos DOCKER_BUILD_ID: jenkins-master-20190909T230000Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190909T23… PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190909T230000Z/logs PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos

2 1

[Starlingx-discuss] [build-report] STX_build_helm_charts - Build # 409 - Still Failing!
by build.starlingx＠gmail.com 11 Sep '19

11 Sep '19

Project: STX_build_helm_charts Build #: 409 Status: Still Failing Timestamp: 20190911T180013Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190909T23… -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190909T230000Z OS: centos DOCKER_BUILD_ID: jenkins-master-20190909T230000Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190909T23… PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190909T230000Z/logs PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos

1 0

[Starlingx-discuss] [build-report] STX_build_helm_charts - Build # 408 - Failure!
by build.starlingx＠gmail.com 11 Sep '19

11 Sep '19

Project: STX_build_helm_charts Build #: 408 Status: Failure Timestamp: 20190911T174940Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190909T23… -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190909T230000Z OS: centos DOCKER_BUILD_ID: jenkins-master-20190909T230000Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190909T23… PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190909T230000Z/logs PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos

1 0

[Starlingx-discuss] MultiOS: call of python via #!/usr/bin/env
by Dominig ar Foll (Intel Open Source) 11 Sep '19

11 Sep '19

Hello, We have a error raised by the Open Build System from OpenSUSE (OBS) due to the use of "#!/usr/bin/env" as interpreter. This stops the OBS to correctly detect dependencies. The use of /usr/bin/env is tricky as it creates an undefined build/run dependency on the target. Could someone explains why such trick is used ? I would need to get rid of it. Just want to find what will be required to be changed. If this is just to call python2 then #!/usr/bin/python2 would do. Thanks. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre [ 10s] worker-utils.noarch: E: env-script-interpreter (Badness: 9) /usr/bin/topology.py /usr/bin/env python [ 10s] This script uses 'env' as an interpreter. For the rpm runtime dependency [ 10s] detection to work, the shebang #!/usr/bin/env python needs to be patched into [ 10s] #!/usr/bin/python otherwise the package dependency generator merely adds a [ 10s] dependency on /usr/bin/env rather than the actual interpreter /usr/bin/python. [ 10s] Alternatively, if the file should not be executed, then ensure that it is not [ 10s] marked as executable or don't install it in a path that is reserved for [ 10s] executables.

3 6

[Starlingx-discuss] Notes: Agenda: Weekly StarlingX non-OpenStack distro meeting, 9/11
by Xie, Cindy 11 Sep '19

11 Sep '19

Agenda & Notes for 9/11 meeting: 1. Ceph containerization status update (Tingjie) update the storyboard and now working on helm-chart of rook. patch uploaded: https://review.opendev.org/#/c/681457/. verified in local environment (raw helm-chart, not starlingX), integration to StarlingX is WIP. sub-task w/ Martin - investigation for Ceph configuration. 36576. how many Ceph monitors we have for AIO-SX? Brent: right now we have 1 only (not 3). in legacy config, it's one for both SX and DX. AR: Martin to confirm the # of monitors for Ceph in stx.2.0. if we go to 3 monitors, it consumes 3GB memory and this is HW resource concerns of go w/ 3 monitors. Fermando from Ada's team got assigned to feature testing of Ceph containerization. Tingjie to review the test plan w/ Fermando, and can kick off the testing starting from next. ETA: Patch ready for reivew/feature testing/merge. AR: Cindy to check w/ Martin to get his estimation of the task 36576. 2. stx.3.0 bug review (Cindy) stx.distro.others: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.other+stx.3… 1841478: timer waiting for RPC, bug reproduced by Yan. 1827080: https://review.opendev.org/#/c/678203/ need rework w/ Ovidiu's comments. AR: Tingjie to update the patch to check the reserved space. Need to reserve space for ceph-mon on all worker-nodes. 1827119: https://review.opendev.org/#/c/677424/, patch updated to address Daniel's. 1840267: Peng Peng to check if the behavior is expected. stx.storage: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.storage+stx.3.0&fi… 1827063 , 1831635 and 1826886 , Tingjie to assign the bugs to other team members. 1842945: newly assigned. 3. Opens: None -----Original Message----- From: Xie, Cindy <cindy.xie(a)intel.com> Sent: Tuesday, September 10, 2019 11:14 PM To: Wold, Saul <saul.wold(a)intel.com>; 'starlingx-discuss(a)lists.starlingx.io' <starlingx-discuss(a)lists.starlingx.io>; 'Rowsell, Brent' <Brent.Rowsell(a)windriver.com> Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 9/11 All, This week I have very light agenda as below, please put what you want to discuss into etherpad or just reply this email: Agenda for 9/11 meeting: 1. Ceph containerization status update (Tingjie) 2. stx.3.0 bug review (Cindy) 3. Opens Thx. - cindy -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss(a)lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, September 11, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss(a)lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

1 0

[Starlingx-discuss] [STX R2.0] Access to VM console not working as Horizon redirects to novncproxy.openstack.svc.cluster.local
by Ezpeer Chen 11 Sep '19

11 Sep '19

Dear all, This issus seems not fixed on STX R2.0. https://bugs.launchpad.net/starlingx/+bug/1827246 Is there any SOP about how to patch on STX R2.0? Thanks.

3 2

[Starlingx-discuss] pmond and systemd handling for fm-rest-api
by Cordoba Malibran, Erich 11 Sep '19

11 Sep '19

Hi, I'm converting the fm-api init script to be handled completely by systemd, however I'm seeing that, once I created the unit file, pmod is constantly launching fm-api (which causes a failure in fm-api is there is a conflict in the network address usage). So, this is my unit file for fm-api. [Unit] Description=Fault Management REST API Service After=nfscommon.service sw-patch.service After=network-online.target systemd-udev-settle.service [Service] Type=simple RemainAfterExit=yes User=root ExecStart=/usr/bin/fm-api --config-file=/etc/fm/fm.conf PIDFile=/var/run/fm-api.pid [Install] WantedBy=multi-user.target Then I edit the /etc/pmon.d/fm-api.conf file to this: [process] process = fm-api pidfile = /var/run/fm-api.pid service = fm-api.service style = systemd ; ocf or lsb severity = major ; minor, major, critical restarts = 3 ; restarts before error assertion interval = 5 ; number of seconds to wait between restarts debounce = 20 ; number of seconds to wait before degrade clear What I've seen is that pmond is looking for the pidfile, but this is not created as this was done by the deleted init script[0]. Also, according to this comment[1], looking for the pidfile is the last resource but I can see frequent attempts to find this file, see below: $ sudo strace -e trace=file -p 86386 --- SIGRT_2 {si_signo=SIGRT_2, si_code=SI_TIMER, si_timerid=0x20, si_overrun=0, si_value={int=6882944, ptr=0x690680}} --- open("/var/run/fm-api.pid", O_RDONLY) = -1 ENOENT (No such file or directory) --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3222970, si_uid=0, si_status=0, si_utime=0, si_stime=0} --- --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3222617, si_uid=0, si_status=0, si_utime=0, si_stime=0} --- --- SIGRT_2 {si_signo=SIGRT_2, si_code=SI_TIMER, si_timerid=0x20, si_overrun=0, si_value={int=6882944, ptr=0x690680}} --- --- SIGRT_2 {si_signo=SIGRT_2, si_code=SI_TIMER, si_timerid=0x20, si_overrun=0, si_value={int=6882944, ptr=0x690680}} --- --- SIGRT_2 {si_signo=SIGRT_2, si_code=SI_TIMER, si_timerid=0x7efa, si_overrun=0, si_value={int=6853136, ptr=0x689210}} --- --- SIGRT_2 {si_signo=SIGRT_2, si_code=SI_TIMER, si_timerid=0x20, si_overrun=0, si_value={int=6882944, ptr=0x690680}} --- open("/var/run/fm-api.pid", O_RDONLY) = -1 ENOENT (No such file or directory) --- SIGRT_2 {si_signo=SIGRT_2, si_code=SI_TIMER, si_timerid=0x7ed1, si_overrun=0, si_value={int=6883584, ptr=0x690900}} --- Does anybody know what can be causing this behavior ? Thanks -Erich - [0] https://opendev.org/starlingx/fault/src/branch/master/fm-rest-api/fm/script… - [1] https://opendev.org/starlingx/metal/src/branch/master/mtce/src/pmon/pmonHdl…

3 3

[Starlingx-discuss] Community Call (Sep 11, 2019)
by Zvonar, Bill 11 Sep '19

11 Sep '19

Hi folks, reminder of the Community call coming up later today. Topics on the agenda include these - feel free to add more at [0]. - 3.0 milestone-2 - repo restructuring - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005938… - release notes - don't close a feature w/out doing release notes! (per release team meeting last week) - when code is changed that impacts our Documentation, should the person making the change also change the documents? - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005925… - Root Ara report removed from Zuul Jobs - Clark Boylan email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005931… - server usage audit log API in Nova - Dean's email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005951… - StarlingX Beijing meetup - Sep 20th - Cindy's email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/005956… Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_C… [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190911T1400

1 0