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

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

06 Aug '19

Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-AUG-06 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190805T23…>) 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 ] 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.

1 0

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

06 Aug '19

Project: STX_BUILD_2.0 Build #: 8 Status: Still Failing Timestamp: 20190806T190628Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190806T19… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true

1 0

[Starlingx-discuss] [ Regression testing - stx2.0 ] Report for 8/06/19
by Perez Ibarra, Maria G 06 Aug '19

06 Aug '19

StarlingX 2.0 Release Status: ISO: BUILD_ID="20190802T013000Z" from (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190802T01…>) ---------------------------------------------------------------------- MANUAL EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 493 Pass = 404 Fail = 23 Blocked = 15 Not Run = 10 Obsolete = 23 Deferred = 18 Total executed = 442 Pass Rate = 94.61% Formula used : Pass Rate = pass * 100 / (pass + fail) Results per Domain: Regression - AIO-SX 25 PASS | 1 Obsolete Regression - Backup & Restore 6 Deferrer Regression - Distributed Cloud Regression - Gnoochi 15 PASS Regression - FM 3 PASS Regression - HA 11 PASS | 1 FAIL Regression - Heat 12 PASS | 1 OBSOLETE Regression - Horizon 4 PASS Regression - Install and Config 6 PASS | 1 Fail Regression - Maintenance 8 PASS | 1 FAIL Regression - Networking 118 PASS | 2 FAIL | 5 BLOCKED | 19 OBSOLETE Regression - Nova 23 PASS | 10 FAIL Regression - Security 34 PASS | 1 FAIL | 2 BLOCKED | 1 OBSOLETE | 4 Deferrer Regression - Storage 23 PASS |2 BLOCKED| 2 Deferrer Regression - Inventory 30 PASS System Test 21 PASS | 2 FAIL | 6 BLOCKED | 1 OBSOLETE | 6 Deferrer Regression - new features 71 PASS | 5 FAIL --------------------------------------------------------------------------- AUTOMATED EXECUTION - INTEL --------------------------------------------------------------------------- Overall Results: Pass = 197 Fail = 38 Total executed = 235 Pass Rate = 83.82% Formula used : Pass Rate = pass * 100 / (pass + fail) Results per Domain: Fault-Management 15 PASS Gnocchi 12 PASS HEAT 6 PASS High-Availability 9 PASS | 2 FAIL Horizon 2 PASS Insallation-And-Config 8 PASS Maintenance 26 PASS | 3 FAIL Networking 45 PASS | 7 FAIL Nova 17 PASS | 2 FAIL Security 18 PASS | 5 FAIL Storage 5 PASS | 11 FAIL SYSINVENTORY 26 PASS | 5 FAIL System 8 PASS |3 FAIL ---------------------------------------------------------------------- AUTOMATED EXECUTION - Wind River ---------------------------------------------------------------------- "Pending results" ---------------------------------------------------------------------- user does not login within configured time(60s) login is aborted https://bugs.launchpad.net/starlingx/+bug/1833469 After pull data cable on the compute, no alarm has triggered https://bugs.launchpad.net/starlingx/+bug/1834512 Containers: lock_host failed on a host with config_drive VM https://bugs.launchpad.net/starlingx/+bug/1821026 200.006 alarm "controller-0 is degraded due to the failure of its 'pci-irq-affinity-agent' process" after reboot https://bugs.launchpad.net/starlingx/+bug/1832047 stx-openstack apply takes longer time when lock and unlock on standby controller https://bugs.launchpad.net/starlingx/+bug/1834083 Port list was not showing for some computes during install https://bugs.launchpad.net/starlingx/+bug/1834245 neutron-l3-agent and neutron-dhcp-agent never recovered after force reboot on compute https://bugs.launchpad.net/starlingx/+bug/1835807 When creating instance with pci-passthrough port getting error https://bugs.launchpad.net/starlingx/+bug/1836682 unexpected output when wipe unassigned disk https://bugs.launchpad.net/starlingx/+bug/1836633 application apply fails after compute lock and unlock https://bugs.launchpad.net/starlingx/+bug/1836609 CirrOS VM login takes too much time, and throw different log errors https://bugs.launchpad.net/starlingx/+bug/1835575 Live Migration Error: Failed to live migrate instance to host "AUTO_SCHEDULE". https://bugs.launchpad.net/starlingx/+bug/1837256 403 error in horizon log when try to update the flavor metadata (and admin user is logged out) https://bugs.launchpad.net/starlingx/+bug/1821213 Create Volume dialog opens (from image panel in Horizon) but getting error default volume type cannot be found https://bugs.launchpad.net/starlingx/+bug/1826259 instance creating via horizon failed https://bugs.launchpad.net/starlingx/+bug/1829925 Containers: openstack pods failed after force rebooting active controller https://bugs.launchpad.net/starlingx/+bug/1816842 After active controller reboot, VM boot up failed with error "Failed to allocate the network(s), not rescheduling" https://bugs.launchpad.net/starlingx/+bug/1836928 nova instance remnant left behind after cold migration completes https://bugs.launchpad.net/starlingx/+bug/1824858 disk_available_least value updates when instance moved but not to the value expected https://bugs.launchpad.net/nova/+bug/1834527 Containers: vm unreachable for minutes after live migration or vm reboot https://bugs.launchpad.net/starlingx/+bug/1818118 100.114 NTP alarm not cleared after swact https://bugs.launchpad.net/starlingx/+bug/1834071 unexpected output when wipe unassigned disk https://bugs.launchpad.net/starlingx/+bug/1836633 AIO-DX Application apply aborted Unexpected process termination while application-apply was in progress https://bugs.launchpad.net/starlingx/+bug/1838101 Uncontrolled swact on standard system is slow https://bugs.launchpad.net/starlingx/+bug/1838411 tenant-mgmt-net not reachable from external network https://bugs.launchpad.net/starlingx/+bug/1836252 VM filesystem is not RW when attached the 2nd volume https://bugs.launchpad.net/starlingx/+bug/1838546 dedicated instance on low latency worker node not appearing in C1 state https://bugs.launchpad.net/starlingx/+bug/1838524 Intermittently the openstack server show indicates that the server does not exist (in live migration tests) https://bugs.launchpad.net/starlingx/+bug/1838676 Resize to swapless flavor still looking for swap https://bugs.launchpad.net/nova/+bug/1762423 SSH to VM failed by Permission denied (publickey) https://bugs.launchpad.net/starlingx/+bug/1824174 vSwitch 1G Hugepage available size cannot be changed https://bugs.launchpad.net/starlingx/+bug/1834530 Unable to start PTP4L services https://bugs.launchpad.net/starlingx/+bug/1839001 Validate re-purposing worker is getting degraded state https://bugs.launchpad.net/starlingx/+bug/1839018 hypervisor stays down after force lock and unlock due to pci-irq-affinity-agent process failure https://bugs.launchpad.net/starlingx/+bug/1839160 ----------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1MoBroFimeQjsJvCC_N_DSLYMQsNZVMzTwAV… Regards! Maria G

1 0

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

06 Aug '19

Project: STX_BUILD_2.0 Build #: 7 Status: Still Failing Timestamp: 20190806T184524Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190806T18… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true

2 1

[Starlingx-discuss] Edge Hacking Days - August 9, 16
by Ildiko Vancsa 06 Aug '19

06 Aug '19

Hi, Based on the Doodle[1] poll results __August 9 and August 16__ got the most votes. You can find the dial in details on this etherpad: https://etherpad.openstack.org/p/osf-edge-hacking-days If you’re interested in joining please __add your name and the time period (with time zone) when you will be available__ on these dates. You can also add topics that you would be interested in working on. Potential topics to work on: * Building and testing edge reference architectures * Keystone testing and bug fixing Please let me know if you have any questions. See you on Friday! :) Thanks and Best Regards, Ildikó [1] August: https://doodle.com/poll/ucfc9w7iewe6gdp4 September: https://doodle.com/poll/3cyqxzr9vd82pwtr October: https://doodle.com/poll/6nzziuihs65hwt7b

1 0

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

06 Aug '19

Project: STX_BUILD_container_setup Build #: 367 Status: Still Failing Timestamp: 20190806T185246Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190806T18… -------------------------------------------------------------------------------- Parameters PROJECT: rc-2.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-2.0/20190806T184524Z DOCKER_BUILD_ID: jenkins-rc-2.0-20190806T184524Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190806T18… DOCKER_BUILD_TAG: rc-2.0-20190806T184524Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/2.0/centos/20190806T184524Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/rc-2.0

1 0

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

06 Aug '19

Project: STX_BUILD_2.0 Build #: 6 Status: Still Failing Timestamp: 20190806T183504Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190806T18… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true

1 0

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

06 Aug '19

Project: STX_BUILD_container_setup Build #: 366 Status: Failure Timestamp: 20190806T183610Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190806T18… -------------------------------------------------------------------------------- Parameters PROJECT: rc-2.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-2.0/20190806T183504Z DOCKER_BUILD_ID: jenkins-rc-2.0-20190806T183504Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190806T18… DOCKER_BUILD_TAG: rc-2.0-20190806T183504Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/2.0/centos/20190806T183504Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/rc-2.0

1 0

[Starlingx-discuss] [Release] [Build] Preparation and discussion about StarlingX release 2.0
by Scott Little 06 Aug '19

06 Aug '19

StarlingX is preparing for its 2.0 release. Expected next week. Below is a discussion of how this is to be done, and a few the the decisions that need to be taken. The release team has taken a first pass at answering the outstanding questions. Our preferred options are indicated. General Requirements - Create a release candidate branch from master, preferably originating from the context of a green sanity. - Branch creation might require a brief halt of commit activity on the master branch. Stay tuned. - more on branching below - RC branch recieves cherry-picked patches from master until a final compile is declared. - Set SW_VERSION, aka PLATFORM_RELEASE, for RC branch to 19.08 (Format YY.MM) - Retain same SW_VERSION for dot releases - Set SW_VERSION, aka PLATFORM_RELEASE, for master branch to 19.09 - Any helm chart changes to pick up release images, not the master images? - answer appears to be no. Helm charts will list the images we build - Create a CENGN job to build the RC branch. Daily builds until final compile is declared. - scripts are fairly generic. In theory it's just need for a new master job to set customize parameters. - A little bit of work to set docker images tags correctly vs branching startagy... more below - Current default format would default to "r-${BRANCH}-centos-stable-${PUBLISH_TIMESTAMP}", but this can be changed. See below - A release branch will test some new code paths in cengn scripts. Will have to monitor closely. - Make sure the build/image retirement scripts are doing the right thing. - Already coded to support branching opt 2 (below) - Support for opt 1 will require some new scripting in CENGN Branching startagy and content lock down - Desired properties of the branch strategy. - We can re-build the ISO release at a later date. - The exact context of StarlingX git trees is captured in some form. - Context of third party git repos is captured on a best effort basis. e.g. capture tag or sha (an assume they are stable), but not cloning gits. - Leverage the 'revision' field for all repos in the manifest. - We can rebuild our docker images at a later date... I don't think we fully know how to do this yet. - lock down the base centos image, and yum, if possible - Need tooling changes for this - Need to reference centos docker image by sha, not tag. - Probably need to hack the yum configuration as well, point it to cengn. - The build of stx-centos points to cengn repo for yum update. The loci build of images, however, also uses upstream sources. Otherwise, we would need to include all RPMs used for those images in the LST files - lock down our inputs from PYPI as best we can - Find all files named *stable_docker_image, field 'PIP_PACKAGES=' needs to use syntax like ... e.g. panko==5.0.0 - inputs can be found in piplst files e.g. $MY_WORKSPACE/std/build-images/tis-networking-avs-heat-centos-stable.piplst - All python modules (non-starlingx) installed would need to be in the base wheels.cfg, which also updates the upper-constraints.txt in the tarball to restrict the installed version. - Lock down rpms feeding into docker images if possible. - Find all files named *stable_docker_image, field 'DIST_PACKAGES=' needs to use syntax like ... e.g. bash-4.2.46-31.el7.tis.4.x86_64 - inputs can be found in rpmlis files e.g. $MY_WORKSPACE/std/build-images/tis-networking-avs-heat-centos-stable.rpmlst - ALL 'tis' packages found in rpmlst must be listed in DIST_PACKAGES - We don't have the power to branch and tag all repos. - Some of the work needs to be done by further locking down the manifest on specific tags/shas - Do we store the locked down manifest as tagged copy of default.xml, or use versioned file names xml? - What is the basic format of our branchs and tags - YYYY.MM i.e. date like as use by to 2018.10 release - 2.0 i.e. a release version - Current CENGN scripting uses the date format, release format requires scripting changes, but nothing major. - I'm always eager that a release branch be clearly distinguished from a dev/feature branch. Currently CENGN looks for YYYY.MM. Is it safe enough to look for anything starting with a number? - Release Team recommends the release version format be as follows - branch: r/stx.2.0 - tag: v2.0.0 - Opt 1 - Single RC branch. Tags mark dot releases -- preferred by Release Team - A single branch is used to stage commits for both initial release and all subsequent dot releases - Branch name is r/stx.2.0 ... applies to starlingx repos. - Tags for each dot release. - v2.0.## ... for starlingx repos - v.stx.2.0.## ... for starlingx-staging repos. Note: starlingx-staging may have inherited version tags from an upstream project that we must not collide with - Git lock down via creation of a uniquely named manifest (v2.0.##.xml) rather than default.xml. In this manifest we specify tags or shas for each git. - We may need to halt commits to the staging branch, or at least the manifest git, when a dot release is imminent and we are waiting on test results. - New scripting required on CENGN for load and docker image retirement - Opt 2 - Single RC branch. Fork a branch to lock down a dot releases - A single branch is used to stage commits for both initial release and all subsequent dot releases - Branch name of staging branch is rc/stx.2.0 ... applies to starlingx repos. - When a dot release is declared, fork a release branch from the staging branch (r/stx.2.0.##). Only commits permitted are to lock down the manifest. - Can still tag as in opt 1, but not required. - Opt 3 - new RC branch for each dot release (waterfall) - Branch name is r/stx.2.0.0 ... applies to starlingx - Final commit is to lock down the git manifest (default.xml) - Next dot release forks from the prior dot release, using the commit prior to manifest lock down. - Can still tag as in opt 1, but not required. Docker image labeling: - A new set of docker images for each dot release - Probably don't need to distinguish release from release candidate as this is hidden within the helm charts. - Probably don't need to distinguish dot releases. Again it is hidden by the helm charts. - Docker image tagging options ... r-2.0-centos-stable.0 2.0-centos-stable.0 r-2.0-centos-stable-${PUBLISH_TIMESTAMP}.0 2.0-centos-stable-${PUBLISH_TIMESTAMP}.0 <--- preferred by Release Team ? r-2.0.##-centos-stable.0 2.0.##-centos-stable.0 r-2.0.##-centos-stable-${PUBLISH_TIMESTAMP}.0 2.0.##-centos-stable-${PUBLISH_TIMESTAMP}.0 Cengn publication path: - Release path .../starlingx/release/2.0.## .../starlingx/release/2.0/2.0.## <-- Preferred by Scott - RC path .../starlingx/rc/2.0/timestamp <-- Preferred by Scott for opt 1 .../starlingx/rc/2.0.##/timestamp .../starlingx/rc/2.0/2.0.##/timestamp

6 19

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

06 Aug '19

Project: STX_BUILD_2.0 Build #: 5 Status: Still Failing Timestamp: 20190806T161539Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20190806T16… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true

1 0