From fuyong at neusoft.com Tue Dec 1 01:12:08 2020 From: fuyong at neusoft.com (fuyong) Date: Tue, 1 Dec 2020 09:12:08 +0800 Subject: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue In-Reply-To: References: Message-ID: <6362974c-12d4-1be3-b7d2-c9d4a081b765@neusoft.com> Hi Haiqing Bai Has libvirt compiled successfully in your integ directory? python3-ipaddr has no el8 version. At present, you need to comment out the place where python3-ipaddr is dependent B,R Yong On 2020/11/30 上午10:26, Bai, Haiqing wrote: Build-iso on f/centos8 branch has below runtime dependency list: ============================================================== Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/hbai/c81nststx/export/deps.txt for details -- exiting These RPMS had problems (likely version conflicts) libvirt-daemon libvirt-daemon-driver-network libvirt.so.0()(64bit) libvirt.so.0(LIBVIRT_0.0.3)(64bit) libvirt.so.0(LIBVIRT_0.1.0)(64bit) libvirt.so.0(LIBVIRT_0.6.1)(64bit) libvirt.so.0(LIBVIRT_0.9.0)(64bit) libvirt.so.0(LIBVIRT_0.9.3)(64bit) libvirt.so.0(LIBVIRT_1.0.2)(64bit) libvirt.so.0(LIBVIRT_1.0.6)(64bit) libvirt.so.0(LIBVIRT_4.5.0)(64bit) libvirt.so.0(LIBVIRT_PRIVATE_4.7.0)(64bit) python3-ipaddr python3-ipaddress python-kubernetes python-pint PyYAML qemu-kvm-ev I remembered the python3-ipaddr issue had been mentioned before by some guys, anyone knows the latest status of that issue? thanks B,R Haiqing Bai _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From Haiqing.Bai at windriver.com Tue Dec 1 03:58:32 2020 From: Haiqing.Bai at windriver.com (Bai, Haiqing) Date: Tue, 1 Dec 2020 03:58:32 +0000 Subject: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue In-Reply-To: <6362974c-12d4-1be3-b7d2-c9d4a081b765@neusoft.com> References: <6362974c-12d4-1be3-b7d2-c9d4a081b765@neusoft.com> Message-ID: Yes, libvirt can be compiled ok and each sub packages are created, for example: -rw-r--r-- 1 hbai 751 7784 11月 30 22:41 libvirt-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 1921432 11月 30 22:41 libvirt-docs-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 8740 11月 30 22:41 libvirt-daemon-config-network-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 700736 11月 30 22:41 libvirt-daemon-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 12728 11月 30 22:41 libvirt-daemon-config-nwfilter-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 243360 11月 30 22:41 libvirt-daemon-driver-network-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 74268 11月 30 22:41 libvirt-daemon-driver-nwfilter-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 48976 11月 30 22:41 libvirt-daemon-driver-nodedev-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 49204 11月 30 22:41 libvirt-daemon-driver-interface-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 37812 11月 30 22:41 libvirt-daemon-driver-secret-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 269600 11月 30 22:41 libvirt-daemon-driver-storage-core-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 40708 11月 30 22:41 libvirt-daemon-driver-storage-logical-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 39512 11月 30 22:41 libvirt-daemon-driver-storage-disk-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 36836 11月 30 22:41 libvirt-daemon-driver-storage-scsi-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 36780 11月 30 22:41 libvirt-daemon-driver-storage-iscsi-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 38952 11月 30 22:41 libvirt-daemon-driver-storage-iscsi-direct-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 35020 11月 30 22:41 libvirt-daemon-driver-storage-mpath-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 48772 11月 30 22:41 libvirt-daemon-driver-storage-gluster-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 43076 11月 30 22:41 libvirt-daemon-driver-storage-rbd-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 6756 11月 30 22:41 libvirt-daemon-driver-storage-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 612932 11月 30 22:41 libvirt-daemon-driver-qemu-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 6540 11月 30 22:41 libvirt-daemon-lxc-4.7.0-1.tis.101.x86_64.rpm …… But “build-iso” complains: 10:19:34 Could not resolve packages: libvirt libvirt-client libvirt-daemon libvirt-daemon-config-network It seems version conflicts with “libvirt.so” and some “python2” upgrading to “python3” runtime dependency issues have not been resolved yet. From: fuyong Sent: Tuesday, December 1, 2020 9:12 AM To: Bai, Haiqing ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue [Please note this e-mail is from an EXTERNAL e-mail address] Hi Haiqing Bai Has libvirt compiled successfully in your integ directory? python3-ipaddr has no el8 version. At present, you need to comment out the place where python3-ipaddr is dependent B,R Yong On 2020/11/30 上午10:26, Bai, Haiqing wrote: Build-iso on f/centos8 branch has below runtime dependency list: ============================================================== Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/hbai/c81nststx/export/deps.txt for details -- exiting These RPMS had problems (likely version conflicts) libvirt-daemon libvirt-daemon-driver-network libvirt.so.0()(64bit) libvirt.so.0(LIBVIRT_0.0.3)(64bit) libvirt.so.0(LIBVIRT_0.1.0)(64bit) libvirt.so.0(LIBVIRT_0.6.1)(64bit) libvirt.so.0(LIBVIRT_0.9.0)(64bit) libvirt.so.0(LIBVIRT_0.9.3)(64bit) libvirt.so.0(LIBVIRT_1.0.2)(64bit) libvirt.so.0(LIBVIRT_1.0.6)(64bit) libvirt.so.0(LIBVIRT_4.5.0)(64bit) libvirt.so.0(LIBVIRT_PRIVATE_4.7.0)(64bit) python3-ipaddr python3-ipaddress python-kubernetes python-pint PyYAML qemu-kvm-ev I remembered the python3-ipaddr issue had been mentioned before by some guys, anyone knows the latest status of that issue? thanks B,R Haiqing Bai _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From fuyong at neusoft.com Tue Dec 1 06:53:51 2020 From: fuyong at neusoft.com (fuyong) Date: Tue, 1 Dec 2020 14:53:51 +0800 Subject: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue In-Reply-To: References: <6362974c-12d4-1be3-b7d2-c9d4a081b765@neusoft.com> Message-ID: <9b658d67-fffe-68a6-e87f-505811fb21cd@neusoft.com> Hi Haiqing Bai Maybe you can run the following command "dnf repo-pkgs -c $MY_WORKSPACE/std/yum.conf local-std list" Make sure the rpm you listed is included in the local-std repo config/sysinv Requires: python3-ipaddr. But python3-ipaddr package does not exist in centos8 utilites/python-cephclient Requires: python3-ipaddress. But python3-ipaddress package does not exist in centos8 Please confirm in sysinv and python-cephclient, and compile after commenting. B,R Yong Fu On 2020/12/1 上午11:58, Bai, Haiqing wrote: Yes, libvirt can be compiled ok and each sub packages are created, for example: -rw-r--r-- 1 hbai 751 7784 11月 30 22:41 libvirt-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 1921432 11月 30 22:41 libvirt-docs-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 8740 11月 30 22:41 libvirt-daemon-config-network-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 700736 11月 30 22:41 libvirt-daemon-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 12728 11月 30 22:41 libvirt-daemon-config-nwfilter-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 243360 11月 30 22:41 libvirt-daemon-driver-network-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 74268 11月 30 22:41 libvirt-daemon-driver-nwfilter-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 48976 11月 30 22:41 libvirt-daemon-driver-nodedev-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 49204 11月 30 22:41 libvirt-daemon-driver-interface-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 37812 11月 30 22:41 libvirt-daemon-driver-secret-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 269600 11月 30 22:41 libvirt-daemon-driver-storage-core-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 40708 11月 30 22:41 libvirt-daemon-driver-storage-logical-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 39512 11月 30 22:41 libvirt-daemon-driver-storage-disk-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 36836 11月 30 22:41 libvirt-daemon-driver-storage-scsi-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 36780 11月 30 22:41 libvirt-daemon-driver-storage-iscsi-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 38952 11月 30 22:41 libvirt-daemon-driver-storage-iscsi-direct-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 35020 11月 30 22:41 libvirt-daemon-driver-storage-mpath-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 48772 11月 30 22:41 libvirt-daemon-driver-storage-gluster-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 43076 11月 30 22:41 libvirt-daemon-driver-storage-rbd-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 6756 11月 30 22:41 libvirt-daemon-driver-storage-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 612932 11月 30 22:41 libvirt-daemon-driver-qemu-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 6540 11月 30 22:41 libvirt-daemon-lxc-4.7.0-1.tis.101.x86_64.rpm …… But “build-iso” complains: 10:19:34 Could not resolve packages: libvirt libvirt-client libvirt-daemon libvirt-daemon-config-network It seems version conflicts with “libvirt.so” and some “python2” upgrading to “python3” runtime dependency issues have not been resolved yet. From: fuyong Sent: Tuesday, December 1, 2020 9:12 AM To: Bai, Haiqing ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue [Please note this e-mail is from an EXTERNAL e-mail address] Hi Haiqing Bai Has libvirt compiled successfully in your integ directory? python3-ipaddr has no el8 version. At present, you need to comment out the place where python3-ipaddr is dependent B,R Yong On 2020/11/30 上午10:26, Bai, Haiqing wrote: Build-iso on f/centos8 branch has below runtime dependency list: ============================================================== Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/hbai/c81nststx/export/deps.txt for details -- exiting These RPMS had problems (likely version conflicts) libvirt-daemon libvirt-daemon-driver-network libvirt.so.0()(64bit) libvirt.so.0(LIBVIRT_0.0.3)(64bit) libvirt.so.0(LIBVIRT_0.1.0)(64bit) libvirt.so.0(LIBVIRT_0.6.1)(64bit) libvirt.so.0(LIBVIRT_0.9.0)(64bit) libvirt.so.0(LIBVIRT_0.9.3)(64bit) libvirt.so.0(LIBVIRT_1.0.2)(64bit) libvirt.so.0(LIBVIRT_1.0.6)(64bit) libvirt.so.0(LIBVIRT_4.5.0)(64bit) libvirt.so.0(LIBVIRT_PRIVATE_4.7.0)(64bit) python3-ipaddr python3-ipaddress python-kubernetes python-pint PyYAML qemu-kvm-ev I remembered the python3-ipaddr issue had been mentioned before by some guys, anyone knows the latest status of that issue? thanks B,R Haiqing Bai _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From haridhar.kalvala at intel.com Tue Dec 1 05:02:59 2020 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Tue, 1 Dec 2020 05:02:59 +0000 Subject: [Starlingx-discuss] Openstack dashboard login issue with changes. Message-ID: Hi Scott & All, Query : 1 I am facing issue with openstack dashboard login as admin when I am trying to build stx-horizon locally (without any changes). Raised launchpad for same : https://bugs.launchpad.net/starlingx/+bug/1905517 . (A) Working case: 1. I have build latest master code (Following internal wiki ) ISO and deployed on machine. 2. Pulled openstack application from location here. 3. I am able to login into the openstack dashboard and starlingX dashboard. (B) Non-Working case(Containerize horizon build): 1. Used same environment as above (ISO, deployed machine and stx-openstack application) 2. Build “stx-horizon locally”. Pushed it on to github, updated openstack-application (on top of working case tgz file) files “stx-openstack.yaml”, “checksum.md5” accordingly with location and md5 number. 3. Applied openstack application. 4. But not able to login into openstack-dashboard as admin. Whereas able to login into starlingX dashboard. 5. Error message invalid credentials. 6. Logs are attached in launchpad. (C) Working Case: Used same environment as above Non-Working case (ISO, deployed machine and stx-openstack application), Except Instead of taking stx-openstack from flock ‘s output folder. I took from container’s output folder. With this I am able to apply and able to login into openstack dashboard. But whatever changes I am doing (mario patch in horizon), and build successfully, those changes are not getting reflected in the dashboard (FM panel in openstack dashboard), the same works in 3.0 release. So I have following queries and request your support in resolving it. Please let me know if we can have 30 minutes discussion today ? 1. What is the difference in flock’s and containers’s stx-openstack application ? You can further check with Scott. 1. Which one to use ? We usually use flock one. 1. Why changes are not reflecting neither in the filesystem of horizon nor on the dashboard, whereas same steps works on the 3.0 release. Stx-horizon build file (latest of master. Have attached too) : ./starlingx/workspace/localdisk/designer/intel/distro/cgcs-root/stx/upstream/openstack/python-horizon/centos/stx-horizon.stable_docker_image Query : 2 I am trying to build RMPS and local wheels, so that during stx-horizon build it can refer latest wheels. But this is not happening and I get same error as package/wheel not found. Followed below steps suggested by Austin; “ I think it is from the wheel is generated by this script https://opendev.org/starlingx/root/src/branch/master/build-tools/build-wheels/get-stx-wheels.sh Those wheel should be extracted from local build rpms. So from my understanding , here should be steps: 1) change spec files for stx gui, to support python3 2) build gui rpms in local w/ python3 3) build wheels for gui python3 4) build docker images. ” In docker build; we export wheels to be picked from here. So is this is the reason why it is not picking local build wheels ? How to club both ? Request support in building local wheel and stx-horizon docker with below pipi packages mentioned in https://review.opendev.org/c/starlingx/upstream/+/661423/4/openstack/python-horizon/centos/stx-horizon.stable_docker_image Thanks, Haridhar Kalvala From: Hu, Yong Sent: Friday, November 27, 2020 2:40 PM To: Kalvala, Haridhar Cc: Sun, Austin ; Liu, ZhipengS ; Liu, Zhipeng ; Chen, Yan ; Mukherjee, Sanjay K ; Bhat, Gopalkrishna ; Kumar, Sharath Subject: Re: Openstack dashboard login. Again, pls DO have the discussions in the mailing list. 发自我的iPhone 在 2020年11月27日,下午5:00,Kalvala, Haridhar > 写道:  Hi Austin, I did step 1 and 2. Step 3 throwing error for to get wheels. I will debug further and update here. Thanks, Haridhar Kalvala From: Sun, Austin > Sent: Friday, November 27, 2020 12:26 PM To: Liu, ZhipengS >; Kalvala, Haridhar >; Hu, Yong >; Liu, Zhipeng > Cc: Mukherjee, Sanjay K >; Bhat, Gopalkrishna >; Kumar, Sharath > Subject: RE: Openstack dashboard login. Hi Haridhar: I think it is from the wheel is generated by this script https://opendev.org/starlingx/root/src/branch/master/build-tools/build-wheels/get-stx-wheels.sh Those wheel should be extracted from local build rpms. So from my understanding , here should be steps: 1) change spec files for stx gui, to support python3 2) build gui rpms in local w/ python3 3) build wheels for gui python3 4) build docker images. Thanks. BR Austin Sun. From: Liu, ZhipengS > Sent: Thursday, November 26, 2020 1:22 PM To: Kalvala, Haridhar >; Sun, Austin >; Hu, Yong >; Liu, Zhipeng > Cc: Mukherjee, Sanjay K >; Bhat, Gopalkrishna >; Kumar, Sharath > Subject: RE: Openstack dashboard login. Hi Haridhar, Please see my inline comment below. You’d better send it to starlingx mail list as well. Thanks! Zhipeng From: Kalvala, Haridhar > Sent: 2020年11月26日 12:26 To: Liu, ZhipengS >; Sun, Austin >; Hu, Yong >; Liu, Zhipeng > Cc: Mukherjee, Sanjay K >; Bhat, Gopalkrishna >; Kumar, Sharath > Subject: RE: Openstack dashboard login. Hi Yong & Team, Instead of taking stx-openstack from flock ‘s output folder. I took from container’s output folder. With this I am able to apply and able to login into openstack dashboard. But whatever changes I am doing (mario patch in horizon), and build successfully, those changes are not getting reflected in the dashboard (FM panel in openstack dashboard), the same works in 3.0 release. So I have following queries and request your support in resolving it. Please let me know if we can have 30 minutes discussion today ? 1. What is the difference in flock’s and containers’s stx-openstack application ? You can further check with Scott. 1. Which one to use ? We usually use flock one. 1. Why changes are not reflecting neither in the filesystem of horizon nor on the dashboard, whereas same steps works on the 3.0 release. Thanks, Haridhar Kalvala From: Liu, ZhipengS > Sent: Wednesday, November 25, 2020 11:09 AM To: Kalvala, Haridhar >; Sun, Austin >; Hu, Yong >; Liu, Zhipeng > Cc: Mukherjee, Sanjay K >; Bhat, Gopalkrishna >; Kumar, Sharath > Subject: RE: Openstack dashboard login. Horizon code should be OK since we build it on cengn with latest code every week. You can also compare the build log for the pass one and failure one, to see if any difference for the dependent package version used for building image. Below one is from cengn. http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/logs/docker-images/docker-stx-horizon-centos-stable.log compare with your failure log you built locally. Especially for RBAC, neutron related packages. Zhipeng From: Kalvala, Haridhar > Sent: 2020年11月25日 12:14 To: Liu, ZhipengS >; Sun, Austin >; Hu, Yong >; Liu, Zhipeng > Cc: Mukherjee, Sanjay K >; Bhat, Gopalkrishna >; Kumar, Sharath > Subject: RE: Openstack dashboard login. Hi Zhipeng, Thank you. Yes nothing changed in horizon and is just build and included in openstack-application. W.r.t point -1 already retried On few times on different machine. I will check point-2. But is their anything that cause communication with neutron endpoint failure ? Thank you, Haridhar Kalvala From: Liu, ZhipengS > Sent: Wednesday, November 25, 2020 8:42 AM To: Kalvala, Haridhar >; Sun, Austin >; Hu, Yong >; Liu, Zhipeng > Cc: Mukherjee, Sanjay K >; Bhat, Gopalkrishna >; Kumar, Sharath > Subject: RE: Openstack dashboard login. Hi Haridhar, It seems you did not change any code, also not related to your build script, no issue found. You just rebuild it locally, right? Error code from log is below. [ERROR] openstack_dashboard.dashboards.admin.rbac_policies.panel: Call to list enabled services failed. This is likely due to a problem communicating with the Neutron endpoint. RBAC Policies panel will not be displayed. I can give you 2 ideas that you can further check. 1. Remove openstack application, upload and apply again. 2. Compare the horizon code you build with the code without issue. Thanks! Zhipeng From: Kalvala, Haridhar > Sent: 2020年11月24日 22:58 To: Sun, Austin >; Hu, Yong >; Liu, Zhipeng >; Liu, ZhipengS > Cc: Mukherjee, Sanjay K >; Bhat, Gopalkrishna >; Kumar, Sharath > Subject: Openstack dashboard login. Hi Austin & Yong, As discussed in distro meeting today, please find the details below and request for support. Working case: 1. I have build latest master code (Following internal wiki ) ISO and deployed on machine. 2. Pulled openstack application from location here. 3. I am able to login into the openstack dashboard and starlingX dashboard. Non-Working case(Containerize horizon build): 1. Used same environment as above (ISO, deployed machine and stx-openstack application) 2. Build “stx-horizon locally”. Pushed it on to github, updated openstack-application (on top of working case tgz file) files “stx-openstack.yaml”, “checksum.md5” accordingly with location and md5 number. 3. Applied openstack application. 4. But not able to login into openstack-dashboard as admin. Whereas able to login into starlingX dashboard. 5. Error message invalid credentials. 6. Attached docker build file,stx-horizon build file, keystone logs and horizon logs. Stx-horizon build file (latest of master. Have attached too) : ./starlingx/workspace/localdisk/designer/intel/distro/cgcs-root/stx/upstream/openstack/python-horizon/centos/stx-horizon.stable_docker_image Note: I need to rename file_extension to txt because of outlook policy. I will raise launchpad issue and keep you updated with ID. Please let me know if any more information needed. Horizon log: [cid:image002.jpg at 01D6C7CB.031E8A70] Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 137743 bytes Desc: image002.jpg URL: From yadav.akshay58 at gmail.com Tue Dec 1 12:21:26 2020 From: yadav.akshay58 at gmail.com (Akki yadav) Date: Tue, 1 Dec 2020 17:51:26 +0530 Subject: [Starlingx-discuss] IRONIC STARLINGX unable to launch baremetal with partitioned image Message-ID: Hello Team, I hope you all are keeping safe and doing good. I have a StarlingX IRONIC setup up and running with 2 controllers, 1 worker node and one baremetal node. I am able to spawn a bare metal node with centos8.2 whole-disk image but when I spawn bare metal with partitioned image, it fails to spawn it stating the following trace ( Full trace back attached in the email): *“2020-12-01 12:35:34.603 1 ERROR ironic.conductor.utils [req-0d3a375e-90a3-485d-a7c3-895c97c88006 - - - - -] Deploy failed for instance 463bd844-7f80-4c57-98dd-6ca8cfdb6121. Error: [Errno 2] No such file or directory: 'sgdisk': 'sgdisk': FileNotFoundError: [Errno 2] No such file or directory: 'sgdisk': 'sgdisk'”.* I have also installed sgdisk (yum install gdisk) on the qcow2 from which I build the partitioned image. Can anyone please guide how to debug it? Regards Akshay -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ironic_openstack_partitioned_image_error Type: application/octet-stream Size: 7400 bytes Desc: not available URL: From haochuan.z.chen at intel.com Tue Dec 1 12:40:27 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 1 Dec 2020 12:40:27 +0000 Subject: [Starlingx-discuss] patch review for rook, project starling/utilities Message-ID: Hi For ceph containerization, I should build a docker image, this is patch. https://review.opendev.org/c/starlingx/utilities/+/760503 For host-based ceph cluster, service manager launch a service ceph-manager which read ceph cluster by ceph-mgr's restful module and raise or clear alarm to fault. For containerized ceph, I build a stx-ceph-manager image and plan to launch a deployment after containerized ceph cluster launched, which will also raise or clean alarm to fault. Please review my patch. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Dec 1 12:42:34 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 1 Dec 2020 12:42:34 +0000 Subject: [Starlingx-discuss] patch review for rook, project starling/utilities In-Reply-To: References: Message-ID: Add Ovidiu. Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, December 1, 2020 8:40 PM To: Scott Little ; Qian, Bin ; MacDonald, Eric ; Bart Wensley ; Kung, John ; Waines, Greg Cc: starlingx-discuss at lists.starlingx.io Subject: patch review for rook, project starling/utilities Hi For ceph containerization, I should build a docker image, this is patch. https://review.opendev.org/c/starlingx/utilities/+/760503 For host-based ceph cluster, service manager launch a service ceph-manager which read ceph cluster by ceph-mgr's restful module and raise or clear alarm to fault. For containerized ceph, I build a stx-ceph-manager image and plan to launch a deployment after containerized ceph cluster launched, which will also raise or clean alarm to fault. Please review my patch. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Tue Dec 1 12:45:01 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 1 Dec 2020 12:45:01 +0000 Subject: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue In-Reply-To: <9b658d67-fffe-68a6-e87f-505811fb21cd@neusoft.com> References: <6362974c-12d4-1be3-b7d2-c9d4a081b765@neusoft.com> <9b658d67-fffe-68a6-e87f-505811fb21cd@neusoft.com> Message-ID: Just a note that the python2-ipaddr module has been superseded by the python3 ipaddress module that is now part of the standard library (see https://docs.python.org/3.6/howto/ipaddress.html). In the case of sysinv, although the spec file says it Requires python2-ipaddr, I don’t see any code actually using this module (it is using the netaddr module which has a python3 version). So I think it is safe to just delete the python2-ipaddr Requires from the sysinv spec file. Bart From: fuyong Sent: Tuesday, December 1, 2020 1:54 AM To: Bai, Haiqing ; starlingx-discuss at lists.starlingx.io Cc: Wold, Saul Subject: Re: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue [Please note this e-mail is from an EXTERNAL e-mail address] Hi Haiqing Bai Maybe you can run the following command "dnf repo-pkgs -c $MY_WORKSPACE/std/yum.conf local-std list" Make sure the rpm you listed is included in the local-std repo config/sysinv Requires: python3-ipaddr. But python3-ipaddr package does not exist in centos8 utilites/python-cephclient Requires: python3-ipaddress. But python3-ipaddress package does not exist in centos8 Please confirm in sysinv and python-cephclient, and compile after commenting. B,R Yong Fu On 2020/12/1 上午11:58, Bai, Haiqing wrote: Yes, libvirt can be compiled ok and each sub packages are created, for example: -rw-r--r-- 1 hbai 751 7784 11月 30 22:41 libvirt-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 1921432 11月 30 22:41 libvirt-docs-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 8740 11月 30 22:41 libvirt-daemon-config-network-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 700736 11月 30 22:41 libvirt-daemon-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 12728 11月 30 22:41 libvirt-daemon-config-nwfilter-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 243360 11月 30 22:41 libvirt-daemon-driver-network-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 74268 11月 30 22:41 libvirt-daemon-driver-nwfilter-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 48976 11月 30 22:41 libvirt-daemon-driver-nodedev-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 49204 11月 30 22:41 libvirt-daemon-driver-interface-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 37812 11月 30 22:41 libvirt-daemon-driver-secret-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 269600 11月 30 22:41 libvirt-daemon-driver-storage-core-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 40708 11月 30 22:41 libvirt-daemon-driver-storage-logical-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 39512 11月 30 22:41 libvirt-daemon-driver-storage-disk-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 36836 11月 30 22:41 libvirt-daemon-driver-storage-scsi-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 36780 11月 30 22:41 libvirt-daemon-driver-storage-iscsi-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 38952 11月 30 22:41 libvirt-daemon-driver-storage-iscsi-direct-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 35020 11月 30 22:41 libvirt-daemon-driver-storage-mpath-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 48772 11月 30 22:41 libvirt-daemon-driver-storage-gluster-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 43076 11月 30 22:41 libvirt-daemon-driver-storage-rbd-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 6756 11月 30 22:41 libvirt-daemon-driver-storage-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 612932 11月 30 22:41 libvirt-daemon-driver-qemu-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 6540 11月 30 22:41 libvirt-daemon-lxc-4.7.0-1.tis.101.x86_64.rpm …… But “build-iso” complains: 10:19:34 Could not resolve packages: libvirt libvirt-client libvirt-daemon libvirt-daemon-config-network It seems version conflicts with “libvirt.so” and some “python2” upgrading to “python3” runtime dependency issues have not been resolved yet. From: fuyong Sent: Tuesday, December 1, 2020 9:12 AM To: Bai, Haiqing ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue [Please note this e-mail is from an EXTERNAL e-mail address] Hi Haiqing Bai Has libvirt compiled successfully in your integ directory? python3-ipaddr has no el8 version. At present, you need to comment out the place where python3-ipaddr is dependent B,R Yong On 2020/11/30 上午10:26, Bai, Haiqing wrote: Build-iso on f/centos8 branch has below runtime dependency list: ============================================================== Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/hbai/c81nststx/export/deps.txt for details -- exiting These RPMS had problems (likely version conflicts) libvirt-daemon libvirt-daemon-driver-network libvirt.so.0()(64bit) libvirt.so.0(LIBVIRT_0.0.3)(64bit) libvirt.so.0(LIBVIRT_0.1.0)(64bit) libvirt.so.0(LIBVIRT_0.6.1)(64bit) libvirt.so.0(LIBVIRT_0.9.0)(64bit) libvirt.so.0(LIBVIRT_0.9.3)(64bit) libvirt.so.0(LIBVIRT_1.0.2)(64bit) libvirt.so.0(LIBVIRT_1.0.6)(64bit) libvirt.so.0(LIBVIRT_4.5.0)(64bit) libvirt.so.0(LIBVIRT_PRIVATE_4.7.0)(64bit) python3-ipaddr python3-ipaddress python-kubernetes python-pint PyYAML qemu-kvm-ev I remembered the python3-ipaddr issue had been mentioned before by some guys, anyone knows the latest status of that issue? thanks B,R Haiqing Bai _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Dec 1 13:38:42 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 1 Dec 2020 13:38:42 +0000 Subject: [Starlingx-discuss] patch review for ceph containerization Message-ID: Hi Please review patch for ceph containerization. I already fix bug for duplex case. https://review.opendev.org/c/starlingx/ha/+/764588 https://review.opendev.org/c/starlingx/rook-ceph/+/716792 https://review.opendev.org/c/starlingx/stx-puppet/+/739363 https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/config/+/758935 https://review.opendev.org/c/starlingx/metal/+/737228 Deploy guide https://review.opendev.org/c/starlingx/docs/+/751158 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Tue Dec 1 13:50:49 2020 From: Saul.Wold at windriver.com (Saul Wold) Date: Tue, 1 Dec 2020 05:50:49 -0800 Subject: [Starlingx-discuss] Adding a centos8 team members to release group Message-ID: Hi Folks, particularly Al, Austin, Scott Shicheng: As you know we are starting up the CentOS8 merging, we need to add a couple of people to the "starling-release" group [0]. This group of people are allowed to merges commits. I would like to add Haiqing Bai and Xia Zhang from windriver. I will also remove Dean from that group as he has moved on. Please respond with yeah or nay. Thanks Sau! [0] https://review.opendev.org/admin/groups/9dacf3ca73d038f36b82262356ff812c416f114c From Al.Bailey at windriver.com Tue Dec 1 14:12:29 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 1 Dec 2020 14:12:29 +0000 Subject: [Starlingx-discuss] Adding a centos8 team members to release group In-Reply-To: References: Message-ID: This sounds fine to me. Al ________________________________ From: Wold, Saul Sent: Tuesday, December 1, 2020 8:50 AM To: Little, Scott ; Bailey, Henry Albert (Al) ; Sun, Austin ; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io ; Bai, Haiqing ; Zhang, Xiao Subject: Adding a centos8 team members to release group Hi Folks, particularly Al, Austin, Scott Shicheng: As you know we are starting up the CentOS8 merging, we need to add a couple of people to the "starling-release" group [0]. This group of people are allowed to merges commits. I would like to add Haiqing Bai and Xia Zhang from windriver. I will also remove Dean from that group as he has moved on. Please respond with yeah or nay. Thanks Sau! [0] https://review.opendev.org/admin/groups/9dacf3ca73d038f36b82262356ff812c416f114c -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Tue Dec 1 14:29:55 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 1 Dec 2020 14:29:55 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Test meeting Message-ID: A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 6028 bytes Desc: not available URL: From scott.little at windriver.com Tue Dec 1 15:50:39 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 1 Dec 2020 10:50:39 -0500 Subject: [Starlingx-discuss] Adding a centos8 team members to release group In-Reply-To: References: Message-ID: <2414e93b-4ed6-65c6-e924-dbc08cabfdd3@windriver.com> Done On 2020-12-01 8:50 a.m., Saul Wold wrote: > > Hi Folks, particularly Al, Austin, Scott Shicheng: > > As you know we are starting up the CentOS8 merging, we need to add a > couple of people to the "starling-release" group [0].  This group of > people are allowed to merges commits. > > I would like to add Haiqing Bai and Xia Zhang from windriver. > > I will also remove Dean from that group as he has moved on. > > Please respond with yeah or nay. > > Thanks >   Sau! > > [0] > https://review.opendev.org/admin/groups/9dacf3ca73d038f36b82262356ff812c416f114c From build.starlingx at gmail.com Tue Dec 1 16:20:24 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 1 Dec 2020 11:20:24 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_base_image - Build # 353 - Still Failing! In-Reply-To: null References: null Message-ID: <1592217173.414.1606839625375.JavaMail.javamailuser@localhost> Project: STX_build_docker_base_image Build #: 353 Status: Still Failing Timestamp: 20201201T161929Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201201T151602Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201201T151602Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20201201T151602Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201201T151602Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201201T151602Z/logs WEB_HOST_PORT: 80 OS_VERSION: 7.5.1804 BUILD_STREAM: stable REGISTRY_ORG: starlingx BASE_LATEST_TAG: master-stable-latest PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201201T151602Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201201T151602Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Tue Dec 1 16:20:27 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 1 Dec 2020 11:20:27 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 63 - Still Failing! In-Reply-To: null References: null Message-ID: <47363471.417.1606839628380.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 63 Status: Still Failing Timestamp: 20201201T161929Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201201T151602Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201201T151602Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201201T151602Z/logs MASTER_BUILD_NUMBER: 86 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201201T151602Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20201201T151602Z DOCKER_BUILD_ID: jenkins-master-containers-20201201T151602Z-builder TIMESTAMP: 20201201T151602Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201201T151602Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201201T151602Z/outputs From build.starlingx at gmail.com Tue Dec 1 16:20:30 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 1 Dec 2020 11:20:30 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 86 - Still Failing! In-Reply-To: null References: null Message-ID: <1159594695.420.1606839631331.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 86 Status: Still Failing Timestamp: 20201201T151602Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201201T151602Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Bill.Zvonar at windriver.com Tue Dec 1 16:33:40 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 1 Dec 2020 16:33:40 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 2, 2020) Message-ID: Hi all, reminder that we're back on tomorrow for the TSC/Community call. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201202T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From Saul.Wold at windriver.com Tue Dec 1 16:34:03 2020 From: Saul.Wold at windriver.com (Saul Wold) Date: Tue, 1 Dec 2020 08:34:03 -0800 Subject: [Starlingx-discuss] Adding a centos8 team members to release group In-Reply-To: <2414e93b-4ed6-65c6-e924-dbc08cabfdd3@windriver.com> References: <2414e93b-4ed6-65c6-e924-dbc08cabfdd3@windriver.com> Message-ID: <596dcb7f-dc3b-c6c6-a9d4-7d9e01604bad@windriver.com> On 12/1/20 7:50 AM, Scott Little wrote: > Done > Thank you Scott, I also removed Dean from the group. Sau! > On 2020-12-01 8:50 a.m., Saul Wold wrote: >> >> Hi Folks, particularly Al, Austin, Scott Shicheng: >> >> As you know we are starting up the CentOS8 merging, we need to add a >> couple of people to the "starling-release" group [0].  This group of >> people are allowed to merges commits. >> >> I would like to add Haiqing Bai and Xia Zhang from windriver. >> >> I will also remove Dean from that group as he has moved on. >> >> Please respond with yeah or nay. >> >> Thanks >>   Sau! >> >> [0] >> https://review.opendev.org/admin/groups/9dacf3ca73d038f36b82262356ff812c416f114c >> > > -- Sau! From build.starlingx at gmail.com Tue Dec 1 18:32:53 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 1 Dec 2020 13:32:53 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_download_mirror - Build # 1074 - Failure! Message-ID: <1142474092.423.1606847574630.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1074 Status: Failure Timestamp: 20201201T100322Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201201T100001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/centos8 DOCKER_BUILD_ID: jenkins-f-centos8-20201201T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201201T100001Z/logs MY_REPO: /localdisk/designer/jenkins/f-centos8/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201201T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Tue Dec 1 18:32:56 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 1 Dec 2020 13:32:56 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 44 - Still Failing! In-Reply-To: <1990484568.402.1606760667991.JavaMail.javamailuser@localhost> References: <1990484568.402.1606760667991.JavaMail.javamailuser@localhost> Message-ID: <1290013776.426.1606847577381.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 44 Status: Still Failing Timestamp: 20201201T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201201T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From zhaos at neusoft.com Wed Dec 2 01:34:52 2020 From: zhaos at neusoft.com (zhaos at neusoft.com) Date: Wed, 2 Dec 2020 09:34:52 +0800 Subject: [Starlingx-discuss] Adding a centos8 team members to release group In-Reply-To: References: Message-ID: <004f01d6c84b$59e46110$0dad2330$@neusoft.com> Hi Saul, Austin, Scott, Shuicheng: For the kernel and integ repo of the CentOS8 branch, Fu Yong tried to merge operations from the Master to the CentOS8 branch many times, but was also told that there was no permission, we think FuYong also does not have CentOS8 merging permission, Do you think we need to add FuYong to the "starling-release" group? Best Regards --------------------- Shuai -----Original Message----- From: Saul Wold Sent: 2020年12月1日 21:51 To: Little, Scott ; Bailey, Henry Albert (Al) ; Sun, Austin ; Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io; Bai, Haiqing ; zhangxiao Subject: [Starlingx-discuss] Adding a centos8 team members to release group Hi Folks, particularly Al, Austin, Scott Shicheng: As you know we are starting up the CentOS8 merging, we need to add a couple of people to the "starling-release" group [0]. This group of people are allowed to merges commits. I would like to add Haiqing Bai and Xia Zhang from windriver. I will also remove Dean from that group as he has moved on. Please respond with yeah or nay. Thanks Sau! [0] https://review.opendev.org/admin/groups/9dacf3ca73d038f36b82262356ff812c416f114c _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- From build.starlingx at gmail.com Wed Dec 2 03:43:04 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 1 Dec 2020 22:43:04 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1051 - Failure! Message-ID: <1589999502.429.1606880585647.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1051 Status: Failure Timestamp: 20201202T033810Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T023718Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20201202T023718Z DOCKER_BUILD_ID: jenkins-master-flock-20201202T023718Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T023718Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20201202T023718Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From build.starlingx at gmail.com Wed Dec 2 03:43:07 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 1 Dec 2020 22:43:07 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 333 - Failure! Message-ID: <1864792267.432.1606880588117.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 333 Status: Failure Timestamp: 20201202T023718Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T023718Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From Saul.Wold at windriver.com Wed Dec 2 03:43:27 2020 From: Saul.Wold at windriver.com (Saul Wold) Date: Tue, 1 Dec 2020 19:43:27 -0800 Subject: [Starlingx-discuss] Adding a centos8 team members to release group In-Reply-To: <004f01d6c84b$59e46110$0dad2330$@neusoft.com> References: <004f01d6c84b$59e46110$0dad2330$@neusoft.com> Message-ID: <89a6c9bd-3fa0-b3ff-b5e6-71bcd05f76e6@windriver.com> I did a quick addition of Fu Yong for now, so that we can move forward with the CentOS-8 work. Please let me know if you additional issues. Sau! On 12/1/20 5:34 PM, zhaos at neusoft.com wrote: > Hi Saul, Austin, Scott, Shuicheng: > > For the kernel and integ repo of the CentOS8 branch, > Fu Yong tried to merge operations from the Master to the CentOS8 branch many times, > but was also told that there was no permission, we think FuYong also does not have CentOS8 merging permission, > Do you think we need to add FuYong to the "starling-release" group? > > Best Regards > --------------------- > Shuai > > -----Original Message----- > From: Saul Wold > Sent: 2020年12月1日 21:51 > To: Little, Scott ; Bailey, Henry Albert (Al) ; Sun, Austin ; Lin, Shuicheng > Cc: starlingx-discuss at lists.starlingx.io; Bai, Haiqing ; zhangxiao > Subject: [Starlingx-discuss] Adding a centos8 team members to release group > > > Hi Folks, particularly Al, Austin, Scott Shicheng: > > As you know we are starting up the CentOS8 merging, we need to add a couple of people to the "starling-release" group [0]. This group of people are allowed to merges commits. > > I would like to add Haiqing Bai and Xia Zhang from windriver. > > I will also remove Dean from that group as he has moved on. > > Please respond with yeah or nay. > > Thanks > Sau! > > [0] > https://review.opendev.org/admin/groups/9dacf3ca73d038f36b82262356ff812c416f114c > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > --------------------------------------------------------------------------------------------------- > Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) > is intended only for the use of the intended recipient and may be confidential and/or privileged of > Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication > is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying > is strictly prohibited, and may be unlawful.If you have received this communication in error,please > immediately notify the sender by return e-mail, and delete the original message and all copies from > your system. Thank you. > --------------------------------------------------------------------------------------------------- > -- Sau! From build.starlingx at gmail.com Wed Dec 2 06:47:27 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 2 Dec 2020 01:47:27 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 952 - Failure! Message-ID: <692729143.437.1606891647956.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 952 Status: Failure Timestamp: 20201202T063328Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201202T053001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20201202T053001Z DOCKER_BUILD_ID: jenkins-master-20201202T053001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201202T053001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20201202T053001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Wed Dec 2 06:47:29 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 2 Dec 2020 01:47:29 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 755 - Failure! Message-ID: <598049207.440.1606891650187.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 755 Status: Failure Timestamp: 20201202T053001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201202T053001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From fuyong at neusoft.com Wed Dec 2 07:18:46 2020 From: fuyong at neusoft.com (fuyong) Date: Wed, 2 Dec 2020 15:18:46 +0800 Subject: [Starlingx-discuss] Adding a centos8 team members to release group In-Reply-To: <89a6c9bd-3fa0-b3ff-b5e6-71bcd05f76e6@windriver.com> References: <004f01d6c84b$59e46110$0dad2330$@neusoft.com> <89a6c9bd-3fa0-b3ff-b5e6-71bcd05f76e6@windriver.com> Message-ID: <490c1c86-3dd9-35fa-b4df-6842f542496b@neusoft.com> Hi Sau: Thank you so much. Best Regards --------------------- Yong Fu On 2020/12/2 上午11:43, Saul Wold wrote: > > I did a quick addition of Fu Yong for now, so that we can move forward > with the CentOS-8 work. > > Please let me know if you additional issues. > > Sau! > > On 12/1/20 5:34 PM, zhaos at neusoft.com wrote: >> Hi Saul, Austin, Scott, Shuicheng: >> >> For the kernel and integ repo of the CentOS8 branch, >> Fu Yong tried to merge operations from the Master to the CentOS8 >> branch many times, >> but was also told that there was no permission, we think FuYong also >> does not have CentOS8 merging permission, >> Do you think we need to add FuYong to the "starling-release" group? >> >> Best Regards >> --------------------- >> Shuai >> >> -----Original Message----- >> From: Saul Wold >> Sent: 2020年12月1日 21:51 >> To: Little, Scott ; Bailey, Henry Albert >> (Al) ; Sun, Austin ; >> Lin, Shuicheng >> Cc: starlingx-discuss at lists.starlingx.io; Bai, Haiqing >> ; zhangxiao >> Subject: [Starlingx-discuss] Adding a centos8 team members to release >> group >> >> >> Hi Folks, particularly Al, Austin, Scott Shicheng: >> >> As you know we are starting up the CentOS8 merging, we need to add a >> couple of people to the "starling-release" group [0]. This group of >> people are allowed to merges commits. >> >> I would like to add Haiqing Bai and Xia Zhang from windriver. >> >> I will also remove Dean from that group as he has moved on. >> >> Please respond with yeah or nay. >> >> Thanks >> Sau! >> >> [0] >> https://review.opendev.org/admin/groups/9dacf3ca73d038f36b82262356ff812c416f114c >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> --------------------------------------------------------------------------------------------------- >> >> Confidentiality Notice: The information contained in this e-mail and >> any accompanying attachment(s) >> is intended only for the use of the intended recipient and may be >> confidential and/or privileged of >> Neusoft Corporation, its subsidiaries and/or its affiliates. If any >> reader of this communication >> is not the intended recipient,unauthorized use,forwarding, printing, >> storing, disclosure or copying >> is strictly prohibited, and may be unlawful.If you have received this >> communication in error,please >> immediately notify the sender by return e-mail, and delete the >> original message and all copies from >> your system. Thank you. >> --------------------------------------------------------------------------------------------------- >> >> > --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- From murthyp at gmail.com Wed Dec 2 10:27:15 2020 From: murthyp at gmail.com (Prashant Murthy) Date: Wed, 2 Dec 2020 15:57:15 +0530 Subject: [Starlingx-discuss] DC for 2 AIO-SX - in VMs Message-ID: Hi, I could successfully install two AIO-SX in two VMs. But I also wanted to try the Distributed Cloud management in a 3rd VM - which can manage these two clusters. But the installation of Distributed cloud is provided only on Bare Metal. Can that be installed and tried on a VM? https://docs.starlingx.io/deploy_install_guides/r4_release/distributed_cloud/index.html Thanks, Prashant -------------- next part -------------- An HTML attachment was scrubbed... URL: From sanathukumar14 at gmail.com Wed Dec 2 15:00:09 2020 From: sanathukumar14 at gmail.com (sanath kumar) Date: Wed, 2 Dec 2020 20:30:09 +0530 Subject: [Starlingx-discuss] Fwd: Error while using StarlingX In-Reply-To: References: Message-ID: ---------- Forwarded message --------- From: sanath kumar Date: Wed, 2 Dec 2020 at 12:19 Subject: Re: [Starlingx-discuss] Error while using StarlingX To: Jascanu, Nicolae Hello Sir, When I do *ls -al* in * test/automated-robot-suite* folder, I got this (my-venv) general at gs-lab-51:~/test/automated-robot-suite$ ls -al total 1520 drwxrwxr-x 14 general general 4096 Dec 2 11:51 . drwxrwxr-x 7 general general 4096 Dec 1 22:40 .. drwxrwxr-x 3 general general 4096 Dec 1 22:40 baremetal lrwxrwxrwx 1 general general 31 Dec 2 11:51 bootimage.iso -> stx-2018-10-19-29-r-2018.10.iso drwxrwxr-x 3 general general 4096 Dec 2 11:51 Config drwxrwxr-x 2 general general 4096 Dec 1 22:40 docs lrwxrwxrwx 1 general general 69 Dec 2 11:51 latest-results -> /home/general/test/automated-robot-suite/Results/20201202115139_Setup drwxrwxr-x 3 general general 4096 Dec 2 11:51 Libraries -rw-rw-r-- 1 general general 137 Dec 1 22:40 LICENSE -rw-rw-r-- 1 general general 11358 Dec 1 22:40 LICENSE.apache drwxrwxr-x 5 general general 4096 Dec 2 11:51 Qemu -rw-rw-r-- 1 general general 21506 Dec 1 22:40 README.rst -rw-rw-r-- 1 general general 209 Dec 1 22:40 requirements.txt drwxrwxr-x 2 general general 4096 Dec 1 22:40 Resources drwxrwxr-x 3 general general 4096 Dec 2 11:51 Results -rwxrwxr-x 1 general general 13672 Dec 1 22:40 runner.py drwxrwxr-x 2 general general 4096 Dec 2 11:51 %s -rw-rw-r-- 1 general general 159 Dec 1 22:40 setup.cfg -rw-rw-r-- 1 general general 1419574 Dec 2 11:41 stx-openstack.tgz drwxrwxr-x 2 general general 4096 Dec 1 22:40 testcases -rw-rw-r-- 1 general general 109 Dec 1 22:40 test-requirements.txt drwxrwxr-x 4 general general 4096 Dec 1 22:40 Tests -rw-rw-r-- 1 general general 1318 Dec 1 22:40 tox.ini drwxrwxr-x 3 general general 4096 Dec 2 11:51 Utils drwxrwxr-x 3 general general 4096 Dec 2 11:51 Variables I have also attached all the log files from *test/automated-robot-suite/latest-results* Regards, Sanath Kumar +91 8971546076 On Thu, 26 Nov 2020 at 20:37, Jascanu, Nicolae wrote: > Hi Kumar, > > Could you please send the output of command *ls -al* in > *test/automated-robot-suite* folder? > > Also, please send all the log files from > *test/automated-robot-suite/latest-results* > > We will try to figure out what is missing. > > > > Regards, > > Nicolae Jascanu, Ph.D. > > Software Engineer > > IOTG > > Galati, Romania > > > > > > *From:* sanath kumar > *Sent:* Wednesday, November 25, 2020 20:47 > *To:* Jascanu, Nicolae > *Subject:* Re: [Starlingx-discuss] Error while using StarlingX > > > > Hello Sir, > > I have done all the above steps. And below is the error message I > was getting, Please help me out. > > > > (my-venv) iot at gss-lab-51:~/test/automated-robot-suite$ python runner.py > --run-suite Setup --configuration 1 --environment virtual > /home/iot/my-venv/lib/python3.5/site-packages/paramiko/transport.py:33: > CryptographyDeprecationWarning: Python 3.5 support will be dropped in the > next release of cryptography. Please upgrade your Python. > from cryptography.hazmat.backends import default_backend > /home/iot/my-venv/lib/python3.5/site-packages/robot/variables/filesetter.py:77: > YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as > the default Loader is unsafe. Please read https://msg.pyyaml.org/load for > full details. > variables = yaml.load(stream) > > ============================================================================== > Setup :: Install and configure StarlingX ISO. > > ============================================================================== > Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... ... > Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... | > FAIL | > 1 != 0 > > ------------------------------------------------------------------------------ > GRUB Checker For BIOS Virtual :: Check grub cmd boot line against ... | > FAIL | > sudo mount -o loop /home/iot/test/automated-robot-suite/bootimage.iso > /tmp/cdrom: b'mount: /home/iot/test/automated-robot-suite/bootimage.iso: > failed to setup loop device: No such file or directory' > > ------------------------------------------------------------------------------ > Install ISO Virtual :: Installation of controller node and define the | > FAIL | > EOF: End Of File (EOF). Exception style platform. > > command: /usr/bin/virsh > args: ['/usr/bin/virsh', '-c', 'qemu:///system', 'console', 'controller-0'] > buffer (last 100 chars): b'' > before (last 100 chars): b" get domain 'controller-0'\r\nerror: Domain not > found: no domain with matching name 'controller-0'\r\n\r\n" > after: > match: None > match_index: None > exitstatus: 1 > flag_eof: True > pid: 3589 > child_fd: 15 > closed: False > timeout: 30 > delimiter: > logfile: <_io.BufferedWriter > name='/home/iot/test/automated-robot-suite/Results/20201126001352_Setup/iso_setup_console.txt'> > logfile_read: None > logfile_send: None > maxread: 2000 > ignorecase: False > searchwindowsize: None > delaybeforesend: 0.05 > delayafterclose: 0.1 > delayafterterminate: 0.1 > searcher: searcher_re: > 0: re.compile(b'Escape character') > > ------------------------------------------------------------------------------ > Ansible Bootstrap Configuration :: Configure controller with local... > > Regards, > > Sanath Kumar > > +91 8971546076 > > > > > > On Wed, 25 Nov 2020 at 11:12, sanath kumar > wrote: > > Thank you, I will check. > > Regards, > > Sanath Kumar > > +91 8971546076 > > > > > > On Tue, 24 Nov 2020 at 14:35, Jascanu, Nicolae > wrote: > > Hi Kumar, > > We discussed the feedback you provided. Please check the following > potential issues: > > 1. please check if *bootimage.iso* and *stx-openstack.tgz* (rename the > versioned helmchart ) are present in the *test/automated-robot-suite* > folder > 2. add in /etc/sudoers the following: username ALL=(ALL) NOPASSWD: ALL > 3. provide the proper rights to libvirt-sock: sudo chmod 666 > /var/run/libvirt/libvirt-sock > 4. uncomment *StrictHostKeyChecking no* in /etc/ssh/ssh_config > > > > Please let us know if you encounter other errors > > > > > > Regards, > > Nicolae Jascanu, Ph.D. > > Software Engineer > > IOTG > > Galati, Romania > > > > > > *From:* sanath kumar > *Sent:* Monday, November 23, 2020 14:25 > *To:* Jascanu, Nicolae > *Subject:* Re: [Starlingx-discuss] Error while using StarlingX > > > > Hello StarlingX Team, > > I am getting Below Error. > > > > (my-venv) starlingx at gss-lab-51:~/test/automated-robot-suite$ python3 > runner.py --run-suite Setup --configuration 1 --environment virtual > /home/starlingx/my-venv/lib/python3.5/site-packages/paramiko/transport.py:33: > CryptographyDeprecationWarning: Python 3.5 support will be dropped in the > next release of cryptography. Please upgrade your Python. > from cryptography.hazmat.backends import default_backend > /home/starlingx/my-venv/lib/python3.5/site-packages/robot/variables/filesetter.py:77: > YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as > the default Loader is unsafe. Please read https://msg.pyyaml.org/load for > full details. > variables = yaml.load(stream) > > ============================================================================== > Setup :: Install and configure StarlingX ISO. > > ============================================================================== > Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... ... > Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... | > FAIL | > 1 != 0 > > ------------------------------------------------------------------------------ > GRUB Checker For BIOS Virtual :: Check grub cmd boot line against ... | > FAIL | > sudo mount -o loop > /home/starlingx/test/automated-robot-suite/bootimage.iso /tmp/cdrom: > b'mount: /home/starlingx/test/automated-robot-suite/bootimage.iso: failed > to setup loop device: No such file or directory' > > ------------------------------------------------------------------------------ > Install ISO Virtual :: Installation of controller node and define the | > FAIL | > EOF: End Of File (EOF). Exception style platform. > > command: /usr/bin/virsh > args: ['/usr/bin/virsh', '-c', 'qemu:///system', 'console', 'controller-0'] > buffer (last 100 chars): b'' > before (last 100 chars): b" hypervisor\r\nerror: Failed to connect socket > to '/var/run/libvirt/libvirt-sock': Permission denied\r\n" > after: > match: None > match_index: None > exitstatus: 1 > flag_eof: True > pid: 2884 > child_fd: 15 > closed: False > timeout: 30 > delimiter: > logfile: <_io.BufferedWriter > name='/home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/iso_setup_console.txt'> > logfile_read: None > logfile_send: None > maxread: 2000 > ignorecase: False > searchwindowsize: None > delaybeforesend: 0.05 > delayafterclose: 0.1 > delayafterterminate: 0.1 > searcher: searcher_re: > 0: re.compile(b'Escape character') > > ------------------------------------------------------------------------------ > Ansible Bootstrap Configuration :: Configure controller with local... | > FAIL | > Keyword 'Connect to Controller Node' failed after retrying for 5 minutes. > The last error was: timeout: timed out > > ------------------------------------------------------------------------------ > Setup :: Install and configure StarlingX ISO. | > FAIL | > 4 critical tests, 0 passed, 4 failed > 4 tests total, 0 passed, 4 failed > > ============================================================================== > Debug: > /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/debug.log > Output: > /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/output.xml > Log: > /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/log.html > Report: > /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/report.html > > > > Regards, > > Sanath Kumar > > +91 8971546076 > > > > > > On Wed, 18 Nov 2020 at 20:57, Jascanu, Nicolae > wrote: > > Hi Kumar, > > You can try to install StarlingX virtual or baremetal using the scripts > that we are using for daily sanity validation. Please follow the > configuration steps at: > https://opendev.org/starlingx/test/src/branch/master/automated-robot-suite > . > > > > Let us know if you have issues. > > > > Regards, > > Nicolae Jascanu, Ph.D. > > Software Engineer > > IOTG > > Galati, Romania > > > > > > *From:* sanath kumar > *Sent:* Thursday, November 12, 2020 08:52 > *To:* Starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Error while using StarlingX > > > > Hello StarlingX Team, > > While I execute below Commands I am getting some error. > > These are the Errors I am getting. > > > > > Regards, > > Sanath Kumar > > +91 8971546076 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: log_files.zip Type: application/zip Size: 158165 bytes Desc: not available URL: From bruce.e.jones at intel.com Wed Dec 2 15:12:34 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 2 Dec 2020 15:12:34 +0000 Subject: [Starlingx-discuss] TSC meeting notes Dec 2 2020 Message-ID: 12/02/2020 Missing PL/TL updates - ildikov Test PL: Yang Liu volunteered: https://review.opendev.org/c/starlingx/governance/+/764984 TSC Members - please review and approve Distro PL: Saul may take on the role Please review and approve the SDO spec. https://review.opendev.org/c/starlingx/specs/+/750636 Ghada - there may be additional specs for 5.0 not yet posted. The deadline for new spec Submissions and approval for the 5.0 release (MS-3) is December 18th (EOY). brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From sanathukumar14 at gmail.com Wed Dec 2 15:14:22 2020 From: sanathukumar14 at gmail.com (sanath kumar) Date: Wed, 2 Dec 2020 20:44:22 +0530 Subject: [Starlingx-discuss] Error while using StarlingX In-Reply-To: References: Message-ID: Hello Sir, When I do *ls -al* in * test/automated-robot-suite* folder, I got this (my-venv) general at gs-lab-51:~/test/automated-robot-suite$ ls -al total 1520 drwxrwxr-x 14 general general 4096 Dec 2 11:51 . drwxrwxr-x 7 general general 4096 Dec 1 22:40 .. drwxrwxr-x 3 general general 4096 Dec 1 22:40 baremetal lrwxrwxrwx 1 general general 31 Dec 2 11:51 bootimage.iso -> stx-2018-10-19-29-r-2018.10.iso drwxrwxr-x 3 general general 4096 Dec 2 11:51 Config drwxrwxr-x 2 general general 4096 Dec 1 22:40 docs lrwxrwxrwx 1 general general 69 Dec 2 11:51 latest-results -> /home/general/test/automated-robot-suite/Results/20201202115139_Setup drwxrwxr-x 3 general general 4096 Dec 2 11:51 Libraries -rw-rw-r-- 1 general general 137 Dec 1 22:40 LICENSE -rw-rw-r-- 1 general general 11358 Dec 1 22:40 LICENSE.apache drwxrwxr-x 5 general general 4096 Dec 2 11:51 Qemu -rw-rw-r-- 1 general general 21506 Dec 1 22:40 README.rst -rw-rw-r-- 1 general general 209 Dec 1 22:40 requirements.txt drwxrwxr-x 2 general general 4096 Dec 1 22:40 Resources drwxrwxr-x 3 general general 4096 Dec 2 11:51 Results -rwxrwxr-x 1 general general 13672 Dec 1 22:40 runner.py drwxrwxr-x 2 general general 4096 Dec 2 11:51 %s -rw-rw-r-- 1 general general 159 Dec 1 22:40 setup.cfg -rw-rw-r-- 1 general general 1419574 Dec 2 11:41 stx-openstack.tgz drwxrwxr-x 2 general general 4096 Dec 1 22:40 testcases -rw-rw-r-- 1 general general 109 Dec 1 22:40 test-requirements.txt drwxrwxr-x 4 general general 4096 Dec 1 22:40 Tests -rw-rw-r-- 1 general general 1318 Dec 1 22:40 tox.ini drwxrwxr-x 3 general general 4096 Dec 2 11:51 Utils drwxrwxr-x 3 general general 4096 Dec 2 11:51 Variables I have also attached all the log files from *test/automated-robot-suite/latest-results* Regards, Sanath Kumar +91 8971546076 On Wed, 2 Dec 2020 at 20:30, sanath kumar wrote: > > ---------- Forwarded message --------- > From: sanath kumar > Date: Wed, 2 Dec 2020 at 12:19 > Subject: Re: [Starlingx-discuss] Error while using StarlingX > To: Jascanu, Nicolae > > > Hello Sir, > When I do *ls -al* in * test/automated-robot-suite* folder, I got this > > (my-venv) general at gs-lab-51:~/test/automated-robot-suite$ ls -al > total 1520 > drwxrwxr-x 14 general general 4096 Dec 2 11:51 . > drwxrwxr-x 7 general general 4096 Dec 1 22:40 .. > drwxrwxr-x 3 general general 4096 Dec 1 22:40 baremetal > lrwxrwxrwx 1 general general 31 Dec 2 11:51 bootimage.iso -> > stx-2018-10-19-29-r-2018.10.iso > drwxrwxr-x 3 general general 4096 Dec 2 11:51 Config > drwxrwxr-x 2 general general 4096 Dec 1 22:40 docs > lrwxrwxrwx 1 general general 69 Dec 2 11:51 latest-results -> > /home/general/test/automated-robot-suite/Results/20201202115139_Setup > drwxrwxr-x 3 general general 4096 Dec 2 11:51 Libraries > -rw-rw-r-- 1 general general 137 Dec 1 22:40 LICENSE > -rw-rw-r-- 1 general general 11358 Dec 1 22:40 LICENSE.apache > drwxrwxr-x 5 general general 4096 Dec 2 11:51 Qemu > -rw-rw-r-- 1 general general 21506 Dec 1 22:40 README.rst > -rw-rw-r-- 1 general general 209 Dec 1 22:40 requirements.txt > drwxrwxr-x 2 general general 4096 Dec 1 22:40 Resources > drwxrwxr-x 3 general general 4096 Dec 2 11:51 Results > -rwxrwxr-x 1 general general 13672 Dec 1 22:40 runner.py > drwxrwxr-x 2 general general 4096 Dec 2 11:51 %s > -rw-rw-r-- 1 general general 159 Dec 1 22:40 setup.cfg > -rw-rw-r-- 1 general general 1419574 Dec 2 11:41 stx-openstack.tgz > drwxrwxr-x 2 general general 4096 Dec 1 22:40 testcases > -rw-rw-r-- 1 general general 109 Dec 1 22:40 test-requirements.txt > drwxrwxr-x 4 general general 4096 Dec 1 22:40 Tests > -rw-rw-r-- 1 general general 1318 Dec 1 22:40 tox.ini > drwxrwxr-x 3 general general 4096 Dec 2 11:51 Utils > drwxrwxr-x 3 general general 4096 Dec 2 11:51 Variables > > > I have also attached all the log files from > *test/automated-robot-suite/latest-results* > > > Regards, > Sanath Kumar > +91 8971546076 > > > On Thu, 26 Nov 2020 at 20:37, Jascanu, Nicolae > wrote: > >> Hi Kumar, >> >> Could you please send the output of command *ls -al* in >> *test/automated-robot-suite* folder? >> >> Also, please send all the log files from >> *test/automated-robot-suite/latest-results* >> >> We will try to figure out what is missing. >> >> >> >> Regards, >> >> Nicolae Jascanu, Ph.D. >> >> Software Engineer >> >> IOTG >> >> Galati, Romania >> >> >> >> >> >> *From:* sanath kumar >> *Sent:* Wednesday, November 25, 2020 20:47 >> *To:* Jascanu, Nicolae >> *Subject:* Re: [Starlingx-discuss] Error while using StarlingX >> >> >> >> Hello Sir, >> >> I have done all the above steps. And below is the error message I >> was getting, Please help me out. >> >> >> >> (my-venv) iot at gss-lab-51:~/test/automated-robot-suite$ python runner.py >> --run-suite Setup --configuration 1 --environment virtual >> /home/iot/my-venv/lib/python3.5/site-packages/paramiko/transport.py:33: >> CryptographyDeprecationWarning: Python 3.5 support will be dropped in the >> next release of cryptography. Please upgrade your Python. >> from cryptography.hazmat.backends import default_backend >> /home/iot/my-venv/lib/python3.5/site-packages/robot/variables/filesetter.py:77: >> YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as >> the default Loader is unsafe. Please read https://msg.pyyaml.org/load >> for full details. >> variables = yaml.load(stream) >> >> ============================================================================== >> Setup :: Install and configure StarlingX ISO. >> >> ============================================================================== >> Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... ... >> Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... | >> FAIL | >> 1 != 0 >> >> ------------------------------------------------------------------------------ >> GRUB Checker For BIOS Virtual :: Check grub cmd boot line against ... | >> FAIL | >> sudo mount -o loop /home/iot/test/automated-robot-suite/bootimage.iso >> /tmp/cdrom: b'mount: /home/iot/test/automated-robot-suite/bootimage.iso: >> failed to setup loop device: No such file or directory' >> >> ------------------------------------------------------------------------------ >> Install ISO Virtual :: Installation of controller node and define the | >> FAIL | >> EOF: End Of File (EOF). Exception style platform. >> >> command: /usr/bin/virsh >> args: ['/usr/bin/virsh', '-c', 'qemu:///system', 'console', >> 'controller-0'] >> buffer (last 100 chars): b'' >> before (last 100 chars): b" get domain 'controller-0'\r\nerror: Domain >> not found: no domain with matching name 'controller-0'\r\n\r\n" >> after: >> match: None >> match_index: None >> exitstatus: 1 >> flag_eof: True >> pid: 3589 >> child_fd: 15 >> closed: False >> timeout: 30 >> delimiter: >> logfile: <_io.BufferedWriter >> name='/home/iot/test/automated-robot-suite/Results/20201126001352_Setup/iso_setup_console.txt'> >> logfile_read: None >> logfile_send: None >> maxread: 2000 >> ignorecase: False >> searchwindowsize: None >> delaybeforesend: 0.05 >> delayafterclose: 0.1 >> delayafterterminate: 0.1 >> searcher: searcher_re: >> 0: re.compile(b'Escape character') >> >> ------------------------------------------------------------------------------ >> Ansible Bootstrap Configuration :: Configure controller with local... >> >> Regards, >> >> Sanath Kumar >> >> +91 8971546076 >> >> >> >> >> >> On Wed, 25 Nov 2020 at 11:12, sanath kumar >> wrote: >> >> Thank you, I will check. >> >> Regards, >> >> Sanath Kumar >> >> +91 8971546076 >> >> >> >> >> >> On Tue, 24 Nov 2020 at 14:35, Jascanu, Nicolae >> wrote: >> >> Hi Kumar, >> >> We discussed the feedback you provided. Please check the following >> potential issues: >> >> 1. please check if *bootimage.iso* and *stx-openstack.tgz* (rename >> the versioned helmchart ) are present in the >> *test/automated-robot-suite* folder >> 2. add in /etc/sudoers the following: username ALL=(ALL) NOPASSWD: ALL >> 3. provide the proper rights to libvirt-sock: sudo chmod 666 >> /var/run/libvirt/libvirt-sock >> 4. uncomment *StrictHostKeyChecking no* in /etc/ssh/ssh_config >> >> >> >> Please let us know if you encounter other errors >> >> >> >> >> >> Regards, >> >> Nicolae Jascanu, Ph.D. >> >> Software Engineer >> >> IOTG >> >> Galati, Romania >> >> >> >> >> >> *From:* sanath kumar >> *Sent:* Monday, November 23, 2020 14:25 >> *To:* Jascanu, Nicolae >> *Subject:* Re: [Starlingx-discuss] Error while using StarlingX >> >> >> >> Hello StarlingX Team, >> >> I am getting Below Error. >> >> >> >> (my-venv) starlingx at gss-lab-51:~/test/automated-robot-suite$ python3 >> runner.py --run-suite Setup --configuration 1 --environment virtual >> /home/starlingx/my-venv/lib/python3.5/site-packages/paramiko/transport.py:33: >> CryptographyDeprecationWarning: Python 3.5 support will be dropped in the >> next release of cryptography. Please upgrade your Python. >> from cryptography.hazmat.backends import default_backend >> /home/starlingx/my-venv/lib/python3.5/site-packages/robot/variables/filesetter.py:77: >> YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as >> the default Loader is unsafe. Please read https://msg.pyyaml.org/load >> for full details. >> variables = yaml.load(stream) >> >> ============================================================================== >> Setup :: Install and configure StarlingX ISO. >> >> ============================================================================== >> Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... ... >> Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... | >> FAIL | >> 1 != 0 >> >> ------------------------------------------------------------------------------ >> GRUB Checker For BIOS Virtual :: Check grub cmd boot line against ... | >> FAIL | >> sudo mount -o loop >> /home/starlingx/test/automated-robot-suite/bootimage.iso /tmp/cdrom: >> b'mount: /home/starlingx/test/automated-robot-suite/bootimage.iso: failed >> to setup loop device: No such file or directory' >> >> ------------------------------------------------------------------------------ >> Install ISO Virtual :: Installation of controller node and define the | >> FAIL | >> EOF: End Of File (EOF). Exception style platform. >> >> command: /usr/bin/virsh >> args: ['/usr/bin/virsh', '-c', 'qemu:///system', 'console', >> 'controller-0'] >> buffer (last 100 chars): b'' >> before (last 100 chars): b" hypervisor\r\nerror: Failed to connect socket >> to '/var/run/libvirt/libvirt-sock': Permission denied\r\n" >> after: >> match: None >> match_index: None >> exitstatus: 1 >> flag_eof: True >> pid: 2884 >> child_fd: 15 >> closed: False >> timeout: 30 >> delimiter: >> logfile: <_io.BufferedWriter >> name='/home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/iso_setup_console.txt'> >> logfile_read: None >> logfile_send: None >> maxread: 2000 >> ignorecase: False >> searchwindowsize: None >> delaybeforesend: 0.05 >> delayafterclose: 0.1 >> delayafterterminate: 0.1 >> searcher: searcher_re: >> 0: re.compile(b'Escape character') >> >> ------------------------------------------------------------------------------ >> Ansible Bootstrap Configuration :: Configure controller with local... | >> FAIL | >> Keyword 'Connect to Controller Node' failed after retrying for 5 minutes. >> The last error was: timeout: timed out >> >> ------------------------------------------------------------------------------ >> Setup :: Install and configure StarlingX ISO. | >> FAIL | >> 4 critical tests, 0 passed, 4 failed >> 4 tests total, 0 passed, 4 failed >> >> ============================================================================== >> Debug: >> /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/debug.log >> Output: >> /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/output.xml >> Log: >> /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/log.html >> Report: >> /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/report.html >> >> >> >> Regards, >> >> Sanath Kumar >> >> +91 8971546076 >> >> >> >> >> >> On Wed, 18 Nov 2020 at 20:57, Jascanu, Nicolae >> wrote: >> >> Hi Kumar, >> >> You can try to install StarlingX virtual or baremetal using the scripts >> that we are using for daily sanity validation. Please follow the >> configuration steps at: >> https://opendev.org/starlingx/test/src/branch/master/automated-robot-suite >> . >> >> >> >> Let us know if you have issues. >> >> >> >> Regards, >> >> Nicolae Jascanu, Ph.D. >> >> Software Engineer >> >> IOTG >> >> Galati, Romania >> >> >> >> >> >> *From:* sanath kumar >> *Sent:* Thursday, November 12, 2020 08:52 >> *To:* Starlingx-discuss at lists.starlingx.io >> *Subject:* [Starlingx-discuss] Error while using StarlingX >> >> >> >> Hello StarlingX Team, >> >> While I execute below Commands I am getting some error. >> >> These are the Errors I am getting. >> >> >> >> >> Regards, >> >> Sanath Kumar >> >> +91 8971546076 >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: log_files.zip Type: application/x-zip-compressed Size: 158165 bytes Desc: not available URL: From Barton.Wensley at windriver.com Wed Dec 2 15:32:02 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Wed, 2 Dec 2020 15:32:02 +0000 Subject: [Starlingx-discuss] DC for 2 AIO-SX - in VMs In-Reply-To: References: Message-ID: Prashant, It is possible to set up a Distributed Cloud system in VMs, but we do not have instructions for that. The System Controller needs to be connected to the Subclouds over an L3 network, so you need to create another VM to act as the router between the System Controller and the subclouds. Bart From: Prashant Murthy Sent: Wednesday, December 2, 2020 5:27 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] DC for 2 AIO-SX - in VMs [Please note this e-mail is from an EXTERNAL e-mail address] Hi, I could successfully install two AIO-SX in two VMs. But I also wanted to try the Distributed Cloud management in a 3rd VM - which can manage these two clusters. But the installation of Distributed cloud is provided only on Bare Metal. Can that be installed and tried on a VM? https://docs.starlingx.io/deploy_install_guides/r4_release/distributed_cloud/index.html Thanks, Prashant -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Dec 2 15:32:44 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 2 Dec 2020 15:32:44 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 2, 2020) In-Reply-To: References: Message-ID: >From today's meeting... * Standing Topics * Sanity * green until some recent build failures * Gerrit Reviews in Need of Attention * Rook Ceph Patch - latest updates https://review.opendev.org/c/starlingx/ha/+/764588 https://review.opendev.org/c/starlingx/rook-ceph/+/716792 https://review.opendev.org/c/starlingx/stx-puppet/+/739363 https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/config/+/758935 https://review.opendev.org/c/starlingx/metal/+/737228 Deploy guide https://review.opendev.org/c/starlingx/docs/+/751158 * CentOS 8 updates coming, per Saul * Topics for this Week * Pulling for the public starlingx registries is resulting in failures as docker hub rate limiting took effect on Nov20, 2020. * For details, https://www.docker.com/increase-rate-limits?utm_source=docker&utm_medium=web%20referral&utm_campaign=increase%20rate%20limit&utm_budget= * Failure signature on StarlingX looks as follows: * Image download failed: docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2500 Server Error: Internal Server Error (\"toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit\")\nSleep 20s before retry downloading image docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2 ...\n * sysinv 2020-11-26 09:38:51.632 100687 ERROR sysinv.conductor.kube_app [-] Image docker.io/starlingx/ceph-config-helper:v1.15.0 download failed from public/privateregistry: 500 Server Error: Internal Server Error ("toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit"): APIError: 500 Server Error: Internal Server Error ("toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading:https://www.docker.com/increase-rate-limit") * sysinv 2020-11-26 09:38:51.632 100687 INFO sysinv.conductor.kube_app [-] Failed to download image: registry.local:9001/docker.io/starlingx/ceph-config-helper:v1.15.0 * sysinv 2020-11-26 09:38:51.633 100687 ERROR sysinv.conductor.kube_app [-] Deployment of application platform-integ-apps (1.0-9) failed: failed to download one or more image(s).: KubeAppApplyFailure: Deployment of application platform-integ-apps (1.0-9) failed: failed to download one or more image(s). * Tracked by stx LP: https://bugs.launchpad.net/starlingx/+bug/1906298 * AR: Bill to look into getting a pro account funded so we don't have to work around this too much * Open Infrastructure Foundation Annual Report - ildikov * Need a section to summarize news and activities for the project * Deadline: January 13, 2021 * Previous reports: * https://www.openstack.org/annual-reports/2018-openstack-foundation-annual-report * https://www.openstack.org/annual-reports/2019-openstack-foundation-annual-report * Volunteer(s): * AR: Bruce & Bill will start something * ARs from Previous Meetings * nothing this week - the one about the Helm chart repo deprecation is still pending though * Open Requests for Help * Openstack dashboard login issue with changes * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010190.html * new, pending with Scott for now * IRONIC STARLINGX unable to launch baremetal with partitioned image * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010191.html * Austin will check with Mingyuan * DC for 2 AIO-SX - in VMs * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010214.html * Bart will respond * Build Matters (if required) * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Tuesday, December 1, 2020 11:34 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Dec 2, 2020) Hi all, reminder that we're back on tomorrow for the TSC/Community call. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201202T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From scott.little at windriver.com Wed Dec 2 17:05:28 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 2 Dec 2020 12:05:28 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 333 - Failure! In-Reply-To: <1864792267.432.1606880588117.JavaMail.javamailuser@localhost> References: <1864792267.432.1606880588117.JavaMail.javamailuser@localhost> Message-ID: <49e530d5-c550-45ed-0ced-7de11358d207@windriver.com> The build failure was cause by the merge of code intended to add support for building in a centos 8 environment.  The update was intended to retain support for centos 7. The build failed because it tried to use a centos 8 mock configuration within a centos 7 build container. Two bugs have been identified that when combined produced the failure. Commits that introduced the error: https://review.opendev.org/c/starlingx/tools/+/762700 https://review.opendev.org/c/starlingx/root/+/762701 I'll be posting a fix shortly Scott Little On 2020-12-01 10:43 p.m., build.starlingx at gmail.com wrote: > [Please note this e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_flock_master_master > Build #: 333 > Status: Failure > Timestamp: 20201202T023718Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T023718Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Wed Dec 2 17:15:47 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 2 Dec 2020 17:15:47 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO20201201T000520Z Message-ID: Sanity Test from 2020-December-1 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201201T000520Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201201T000520Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From sanathukumar14 at gmail.com Wed Dec 2 18:10:35 2020 From: sanathukumar14 at gmail.com (sanath kumar) Date: Wed, 2 Dec 2020 23:40:35 +0530 Subject: [Starlingx-discuss] Error while using StarlingX In-Reply-To: References: Message-ID: Hello StarlingX team, I am getting Below Error, It would be great if somebody can help me out, I am running out of option. I will also attach the Log-files for the reference. (my-venv) general at gs-lab-51:~/test/automated-robot-suite$ python runner.py --run-suite Setup --configuration 1 --environment virtual /home/general/my-venv/lib/python3.6/site-packages/robot/variables/filesetter.py:77: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details. variables = yaml.load(stream) ============================================================================== Setup :: Install and configure StarlingX ISO. ============================================================================== Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... ... Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... | FAIL | 1 != 0 ------------------------------------------------------------------------------ GRUB Checker For BIOS Virtual :: Check grub cmd boot line against ... | FAIL | sudo mount -o loop /home/general/test/automated-robot-suite/bootimage.iso /tmp/cdrom: b'mount: /tmp/cdrom: failed to setup loop device for /home/general/test/automated-robot-suite/bootimage.iso.' ------------------------------------------------------------------------------ Install ISO Virtual :: Installation of controller node and define the | FAIL | EOF: End Of File (EOF). Exception style platform. command: /usr/bin/virsh args: ['/usr/bin/virsh', '-c', 'qemu:///system', 'console', 'controller-0'] buffer (last 100 chars): b'' before (last 100 chars): b" get domain 'controller-0'\r\nerror: Domain not found: no domain with matching name 'controller-0'\r\n\r\n" after: match: None match_index: None exitstatus: 1 flag_eof: True pid: 4154 child_fd: 15 closed: False timeout: 30 delimiter: logfile: <_io.BufferedWriter name='/home/general/test/automated-robot-suite/Results/20201202231938_Setup/iso_setup_console.txt'> logfile_read: None logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1 searcher: searcher_re: 0: re.compile(b'Escape character') ------------------------------------------------------------------------------ Ansible Bootstrap Configuration :: Configure controller with local... | FAIL | Keyword 'Connect to Controller Node' failed after retrying for 5 minutes. The last error was: timeout: timed out ------------------------------------------------------------------------------ Setup :: Install and configure StarlingX ISO. | FAIL | 4 critical tests, 0 passed, 4 failed 4 tests total, 0 passed, 4 failed ============================================================================== Debug: /home/general/test/automated-robot-suite/Results/20201202231938_Setup/debug.log Output: /home/general/test/automated-robot-suite/Results/20201202231938_Setup/output.xml Log: /home/general/test/automated-robot-suite/Results/20201202231938_Setup/log.html Report: /home/general/test/automated-robot-suite/Results/20201202231938_Setup/report.html (my-venv) general at gs-lab-51:~/test/automated-robot-suite$ Regards, Sanath Kumar +91 8971546076 On Wed, 2 Dec 2020 at 20:44, sanath kumar wrote: > Hello Sir, > When I do *ls -al* in * test/automated-robot-suite* folder, I got this > > (my-venv) general at gs-lab-51:~/test/automated-robot-suite$ ls -al > total 1520 > drwxrwxr-x 14 general general 4096 Dec 2 11:51 . > drwxrwxr-x 7 general general 4096 Dec 1 22:40 .. > drwxrwxr-x 3 general general 4096 Dec 1 22:40 baremetal > lrwxrwxrwx 1 general general 31 Dec 2 11:51 bootimage.iso -> > stx-2018-10-19-29-r-2018.10.iso > drwxrwxr-x 3 general general 4096 Dec 2 11:51 Config > drwxrwxr-x 2 general general 4096 Dec 1 22:40 docs > lrwxrwxrwx 1 general general 69 Dec 2 11:51 latest-results -> > /home/general/test/automated-robot-suite/Results/20201202115139_Setup > drwxrwxr-x 3 general general 4096 Dec 2 11:51 Libraries > -rw-rw-r-- 1 general general 137 Dec 1 22:40 LICENSE > -rw-rw-r-- 1 general general 11358 Dec 1 22:40 LICENSE.apache > drwxrwxr-x 5 general general 4096 Dec 2 11:51 Qemu > -rw-rw-r-- 1 general general 21506 Dec 1 22:40 README.rst > -rw-rw-r-- 1 general general 209 Dec 1 22:40 requirements.txt > drwxrwxr-x 2 general general 4096 Dec 1 22:40 Resources > drwxrwxr-x 3 general general 4096 Dec 2 11:51 Results > -rwxrwxr-x 1 general general 13672 Dec 1 22:40 runner.py > drwxrwxr-x 2 general general 4096 Dec 2 11:51 %s > -rw-rw-r-- 1 general general 159 Dec 1 22:40 setup.cfg > -rw-rw-r-- 1 general general 1419574 Dec 2 11:41 stx-openstack.tgz > drwxrwxr-x 2 general general 4096 Dec 1 22:40 testcases > -rw-rw-r-- 1 general general 109 Dec 1 22:40 test-requirements.txt > drwxrwxr-x 4 general general 4096 Dec 1 22:40 Tests > -rw-rw-r-- 1 general general 1318 Dec 1 22:40 tox.ini > drwxrwxr-x 3 general general 4096 Dec 2 11:51 Utils > drwxrwxr-x 3 general general 4096 Dec 2 11:51 Variables > > > I have also attached all the log files from > *test/automated-robot-suite/latest-results* > > Regards, > Sanath Kumar > +91 8971546076 > > > On Wed, 2 Dec 2020 at 20:30, sanath kumar > wrote: > >> >> ---------- Forwarded message --------- >> From: sanath kumar >> Date: Wed, 2 Dec 2020 at 12:19 >> Subject: Re: [Starlingx-discuss] Error while using StarlingX >> To: Jascanu, Nicolae >> >> >> Hello Sir, >> When I do *ls -al* in * test/automated-robot-suite* folder, I got this >> >> (my-venv) general at gs-lab-51:~/test/automated-robot-suite$ ls -al >> total 1520 >> drwxrwxr-x 14 general general 4096 Dec 2 11:51 . >> drwxrwxr-x 7 general general 4096 Dec 1 22:40 .. >> drwxrwxr-x 3 general general 4096 Dec 1 22:40 baremetal >> lrwxrwxrwx 1 general general 31 Dec 2 11:51 bootimage.iso -> >> stx-2018-10-19-29-r-2018.10.iso >> drwxrwxr-x 3 general general 4096 Dec 2 11:51 Config >> drwxrwxr-x 2 general general 4096 Dec 1 22:40 docs >> lrwxrwxrwx 1 general general 69 Dec 2 11:51 latest-results -> >> /home/general/test/automated-robot-suite/Results/20201202115139_Setup >> drwxrwxr-x 3 general general 4096 Dec 2 11:51 Libraries >> -rw-rw-r-- 1 general general 137 Dec 1 22:40 LICENSE >> -rw-rw-r-- 1 general general 11358 Dec 1 22:40 LICENSE.apache >> drwxrwxr-x 5 general general 4096 Dec 2 11:51 Qemu >> -rw-rw-r-- 1 general general 21506 Dec 1 22:40 README.rst >> -rw-rw-r-- 1 general general 209 Dec 1 22:40 requirements.txt >> drwxrwxr-x 2 general general 4096 Dec 1 22:40 Resources >> drwxrwxr-x 3 general general 4096 Dec 2 11:51 Results >> -rwxrwxr-x 1 general general 13672 Dec 1 22:40 runner.py >> drwxrwxr-x 2 general general 4096 Dec 2 11:51 %s >> -rw-rw-r-- 1 general general 159 Dec 1 22:40 setup.cfg >> -rw-rw-r-- 1 general general 1419574 Dec 2 11:41 stx-openstack.tgz >> drwxrwxr-x 2 general general 4096 Dec 1 22:40 testcases >> -rw-rw-r-- 1 general general 109 Dec 1 22:40 test-requirements.txt >> drwxrwxr-x 4 general general 4096 Dec 1 22:40 Tests >> -rw-rw-r-- 1 general general 1318 Dec 1 22:40 tox.ini >> drwxrwxr-x 3 general general 4096 Dec 2 11:51 Utils >> drwxrwxr-x 3 general general 4096 Dec 2 11:51 Variables >> >> >> I have also attached all the log files from >> *test/automated-robot-suite/latest-results* >> >> >> Regards, >> Sanath Kumar >> +91 8971546076 >> >> >> On Thu, 26 Nov 2020 at 20:37, Jascanu, Nicolae >> wrote: >> >>> Hi Kumar, >>> >>> Could you please send the output of command *ls -al* in >>> *test/automated-robot-suite* folder? >>> >>> Also, please send all the log files from >>> *test/automated-robot-suite/latest-results* >>> >>> We will try to figure out what is missing. >>> >>> >>> >>> Regards, >>> >>> Nicolae Jascanu, Ph.D. >>> >>> Software Engineer >>> >>> IOTG >>> >>> Galati, Romania >>> >>> >>> >>> >>> >>> *From:* sanath kumar >>> *Sent:* Wednesday, November 25, 2020 20:47 >>> *To:* Jascanu, Nicolae >>> *Subject:* Re: [Starlingx-discuss] Error while using StarlingX >>> >>> >>> >>> Hello Sir, >>> >>> I have done all the above steps. And below is the error message I >>> was getting, Please help me out. >>> >>> >>> >>> (my-venv) iot at gss-lab-51:~/test/automated-robot-suite$ python >>> runner.py --run-suite Setup --configuration 1 --environment virtual >>> /home/iot/my-venv/lib/python3.5/site-packages/paramiko/transport.py:33: >>> CryptographyDeprecationWarning: Python 3.5 support will be dropped in the >>> next release of cryptography. Please upgrade your Python. >>> from cryptography.hazmat.backends import default_backend >>> /home/iot/my-venv/lib/python3.5/site-packages/robot/variables/filesetter.py:77: >>> YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as >>> the default Loader is unsafe. Please read https://msg.pyyaml.org/load >>> for full details. >>> variables = yaml.load(stream) >>> >>> ============================================================================== >>> Setup :: Install and configure StarlingX ISO. >>> >>> ============================================================================== >>> Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... ... >>> Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... | >>> FAIL | >>> 1 != 0 >>> >>> ------------------------------------------------------------------------------ >>> GRUB Checker For BIOS Virtual :: Check grub cmd boot line against ... | >>> FAIL | >>> sudo mount -o loop /home/iot/test/automated-robot-suite/bootimage.iso >>> /tmp/cdrom: b'mount: /home/iot/test/automated-robot-suite/bootimage.iso: >>> failed to setup loop device: No such file or directory' >>> >>> ------------------------------------------------------------------------------ >>> Install ISO Virtual :: Installation of controller node and define the | >>> FAIL | >>> EOF: End Of File (EOF). Exception style platform. >>> >>> command: /usr/bin/virsh >>> args: ['/usr/bin/virsh', '-c', 'qemu:///system', 'console', >>> 'controller-0'] >>> buffer (last 100 chars): b'' >>> before (last 100 chars): b" get domain 'controller-0'\r\nerror: Domain >>> not found: no domain with matching name 'controller-0'\r\n\r\n" >>> after: >>> match: None >>> match_index: None >>> exitstatus: 1 >>> flag_eof: True >>> pid: 3589 >>> child_fd: 15 >>> closed: False >>> timeout: 30 >>> delimiter: >>> logfile: <_io.BufferedWriter >>> name='/home/iot/test/automated-robot-suite/Results/20201126001352_Setup/iso_setup_console.txt'> >>> logfile_read: None >>> logfile_send: None >>> maxread: 2000 >>> ignorecase: False >>> searchwindowsize: None >>> delaybeforesend: 0.05 >>> delayafterclose: 0.1 >>> delayafterterminate: 0.1 >>> searcher: searcher_re: >>> 0: re.compile(b'Escape character') >>> >>> ------------------------------------------------------------------------------ >>> Ansible Bootstrap Configuration :: Configure controller with local... >>> >>> Regards, >>> >>> Sanath Kumar >>> >>> +91 8971546076 >>> >>> >>> >>> >>> >>> On Wed, 25 Nov 2020 at 11:12, sanath kumar >>> wrote: >>> >>> Thank you, I will check. >>> >>> Regards, >>> >>> Sanath Kumar >>> >>> +91 8971546076 >>> >>> >>> >>> >>> >>> On Tue, 24 Nov 2020 at 14:35, Jascanu, Nicolae < >>> nicolae.jascanu at intel.com> wrote: >>> >>> Hi Kumar, >>> >>> We discussed the feedback you provided. Please check the following >>> potential issues: >>> >>> 1. please check if *bootimage.iso* and *stx-openstack.tgz* (rename >>> the versioned helmchart ) are present in the >>> *test/automated-robot-suite* folder >>> 2. add in /etc/sudoers the following: username ALL=(ALL) NOPASSWD: >>> ALL >>> 3. provide the proper rights to libvirt-sock: sudo chmod 666 >>> /var/run/libvirt/libvirt-sock >>> 4. uncomment *StrictHostKeyChecking no* in /etc/ssh/ssh_config >>> >>> >>> >>> Please let us know if you encounter other errors >>> >>> >>> >>> >>> >>> Regards, >>> >>> Nicolae Jascanu, Ph.D. >>> >>> Software Engineer >>> >>> IOTG >>> >>> Galati, Romania >>> >>> >>> >>> >>> >>> *From:* sanath kumar >>> *Sent:* Monday, November 23, 2020 14:25 >>> *To:* Jascanu, Nicolae >>> *Subject:* Re: [Starlingx-discuss] Error while using StarlingX >>> >>> >>> >>> Hello StarlingX Team, >>> >>> I am getting Below Error. >>> >>> >>> >>> (my-venv) starlingx at gss-lab-51:~/test/automated-robot-suite$ python3 >>> runner.py --run-suite Setup --configuration 1 --environment virtual >>> /home/starlingx/my-venv/lib/python3.5/site-packages/paramiko/transport.py:33: >>> CryptographyDeprecationWarning: Python 3.5 support will be dropped in the >>> next release of cryptography. Please upgrade your Python. >>> from cryptography.hazmat.backends import default_backend >>> /home/starlingx/my-venv/lib/python3.5/site-packages/robot/variables/filesetter.py:77: >>> YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as >>> the default Loader is unsafe. Please read https://msg.pyyaml.org/load >>> for full details. >>> variables = yaml.load(stream) >>> >>> ============================================================================== >>> Setup :: Install and configure StarlingX ISO. >>> >>> ============================================================================== >>> Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... ... >>> Qemu Libvirt VMs Setup Virtual :: Qemu-Libvirt VMs setup and confi... | >>> FAIL | >>> 1 != 0 >>> >>> ------------------------------------------------------------------------------ >>> GRUB Checker For BIOS Virtual :: Check grub cmd boot line against ... | >>> FAIL | >>> sudo mount -o loop >>> /home/starlingx/test/automated-robot-suite/bootimage.iso /tmp/cdrom: >>> b'mount: /home/starlingx/test/automated-robot-suite/bootimage.iso: failed >>> to setup loop device: No such file or directory' >>> >>> ------------------------------------------------------------------------------ >>> Install ISO Virtual :: Installation of controller node and define the | >>> FAIL | >>> EOF: End Of File (EOF). Exception style platform. >>> >>> command: /usr/bin/virsh >>> args: ['/usr/bin/virsh', '-c', 'qemu:///system', 'console', >>> 'controller-0'] >>> buffer (last 100 chars): b'' >>> before (last 100 chars): b" hypervisor\r\nerror: Failed to connect >>> socket to '/var/run/libvirt/libvirt-sock': Permission denied\r\n" >>> after: >>> match: None >>> match_index: None >>> exitstatus: 1 >>> flag_eof: True >>> pid: 2884 >>> child_fd: 15 >>> closed: False >>> timeout: 30 >>> delimiter: >>> logfile: <_io.BufferedWriter >>> name='/home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/iso_setup_console.txt'> >>> logfile_read: None >>> logfile_send: None >>> maxread: 2000 >>> ignorecase: False >>> searchwindowsize: None >>> delaybeforesend: 0.05 >>> delayafterclose: 0.1 >>> delayafterterminate: 0.1 >>> searcher: searcher_re: >>> 0: re.compile(b'Escape character') >>> >>> ------------------------------------------------------------------------------ >>> Ansible Bootstrap Configuration :: Configure controller with local... | >>> FAIL | >>> Keyword 'Connect to Controller Node' failed after retrying for 5 >>> minutes. The last error was: timeout: timed out >>> >>> ------------------------------------------------------------------------------ >>> Setup :: Install and configure StarlingX ISO. | >>> FAIL | >>> 4 critical tests, 0 passed, 4 failed >>> 4 tests total, 0 passed, 4 failed >>> >>> ============================================================================== >>> Debug: >>> /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/debug.log >>> Output: >>> /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/output.xml >>> Log: >>> /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/log.html >>> Report: >>> /home/starlingx/test/automated-robot-suite/Results/20201123174658_Setup/report.html >>> >>> >>> >>> Regards, >>> >>> Sanath Kumar >>> >>> +91 8971546076 >>> >>> >>> >>> >>> >>> On Wed, 18 Nov 2020 at 20:57, Jascanu, Nicolae < >>> nicolae.jascanu at intel.com> wrote: >>> >>> Hi Kumar, >>> >>> You can try to install StarlingX virtual or baremetal using the scripts >>> that we are using for daily sanity validation. Please follow the >>> configuration steps at: >>> https://opendev.org/starlingx/test/src/branch/master/automated-robot-suite >>> . >>> >>> >>> >>> Let us know if you have issues. >>> >>> >>> >>> Regards, >>> >>> Nicolae Jascanu, Ph.D. >>> >>> Software Engineer >>> >>> IOTG >>> >>> Galati, Romania >>> >>> >>> >>> >>> >>> *From:* sanath kumar >>> *Sent:* Thursday, November 12, 2020 08:52 >>> *To:* Starlingx-discuss at lists.starlingx.io >>> *Subject:* [Starlingx-discuss] Error while using StarlingX >>> >>> >>> >>> Hello StarlingX Team, >>> >>> While I execute below Commands I am getting some error. >>> >>> These are the Errors I am getting. >>> >>> >>> >>> >>> Regards, >>> >>> Sanath Kumar >>> >>> +91 8971546076 >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: log_file.zip Type: application/x-zip-compressed Size: 158293 bytes Desc: not available URL: From build.starlingx at gmail.com Wed Dec 2 18:18:37 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 2 Dec 2020 13:18:37 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1052 - Still Failing! In-Reply-To: <2055330056.427.1606880583226.JavaMail.javamailuser@localhost> References: <2055330056.427.1606880583226.JavaMail.javamailuser@localhost> Message-ID: <2101163622.444.1606933118067.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1052 Status: Still Failing Timestamp: 20201202T180754Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T023718Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20201202T023718Z DOCKER_BUILD_ID: jenkins-master-flock-20201202T023718Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T023718Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20201202T023718Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From scott.little at windriver.com Wed Dec 2 18:45:08 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 2 Dec 2020 13:45:08 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 333 - Failure! In-Reply-To: <49e530d5-c550-45ed-0ced-7de11358d207@windriver.com> References: <1864792267.432.1606880588117.JavaMail.javamailuser@localhost> <49e530d5-c550-45ed-0ced-7de11358d207@windriver.com> Message-ID: Fixes posted for review. # Fix for 762700 https://review.opendev.org/c/starlingx/tools/+/765179 # Reversion of 762701 https://review.opendev.org/c/starlingx/root/+/765191 Scott On 2020-12-02 12:05 p.m., Scott Little wrote: > The build failure was cause by the merge of code intended to add > support for building in a centos 8 environment.  The update was > intended to retain support for centos 7. > > The build failed because it tried to use a centos 8 mock configuration > within a centos 7 build container. > > Two bugs have been identified that when combined produced the failure. > > Commits that introduced the error: > https://review.opendev.org/c/starlingx/tools/+/762700 > https://review.opendev.org/c/starlingx/root/+/762701 > > I'll be posting a fix shortly > > Scott Little > > > On 2020-12-01 10:43 p.m., build.starlingx at gmail.com wrote: >> [Please note this e-mail is from an EXTERNAL e-mail address] >> >> Project: STX_build_layer_flock_master_master >> Build #: 333 >> Status: Failure >> Timestamp: 20201202T023718Z >> Branch: master >> >> Check logs at: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T023718Z/logs >> -------------------------------------------------------------------------------- >> Parameters >> >> FULL_BUILD: false >> FORCE_BUILD: false >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Dec 2 19:16:30 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 2 Dec 2020 14:16:30 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_download_mirror - Build # 1076 - Failure! Message-ID: <1294318100.449.1606936590687.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1076 Status: Failure Timestamp: 20201202T100414Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201202T100001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/centos8 DOCKER_BUILD_ID: jenkins-f-centos8-20201202T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201202T100001Z/logs MY_REPO: /localdisk/designer/jenkins/f-centos8/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201202T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Wed Dec 2 19:16:32 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 2 Dec 2020 14:16:32 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 45 - Still Failing! In-Reply-To: <52145094.424.1606847575234.JavaMail.javamailuser@localhost> References: <52145094.424.1606847575234.JavaMail.javamailuser@localhost> Message-ID: <788024880.452.1606936593073.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 45 Status: Still Failing Timestamp: 20201202T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201202T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From scott.little at windriver.com Wed Dec 2 19:46:42 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 2 Dec 2020 14:46:42 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 333 - Failure! In-Reply-To: References: <1864792267.432.1606880588117.JavaMail.javamailuser@localhost> <49e530d5-c550-45ed-0ced-7de11358d207@windriver.com> Message-ID: <80e07848-490c-2d38-2def-dbb3b3d3e4f1@windriver.com> Fixes have merged. A fresh CENGN build is underfway. Scott On 2020-12-02 1:45 p.m., Scott Little wrote: > Fixes posted for review. > > # Fix for 762700 > https://review.opendev.org/c/starlingx/tools/+/765179 > > # Reversion of 762701 > https://review.opendev.org/c/starlingx/root/+/765191 > > > Scott > > > On 2020-12-02 12:05 p.m., Scott Little wrote: >> The build failure was cause by the merge of code intended to add >> support for building in a centos 8 environment.  The update was >> intended to retain support for centos 7. >> >> The build failed because it tried to use a centos 8 mock >> configuration within a centos 7 build container. >> >> Two bugs have been identified that when combined produced the failure. >> >> Commits that introduced the error: >> https://review.opendev.org/c/starlingx/tools/+/762700 >> https://review.opendev.org/c/starlingx/root/+/762701 >> >> I'll be posting a fix shortly >> >> Scott Little >> >> >> On 2020-12-01 10:43 p.m., build.starlingx at gmail.com wrote: >>> [Please note this e-mail is from an EXTERNAL e-mail address] >>> >>> Project: STX_build_layer_flock_master_master >>> Build #: 333 >>> Status: Failure >>> Timestamp: 20201202T023718Z >>> Branch: master >>> >>> Check logs at: >>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T023718Z/logs >>> -------------------------------------------------------------------------------- >>> Parameters >>> >>> FULL_BUILD: false >>> FORCE_BUILD: false >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Dec 2 20:23:46 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 2 Dec 2020 15:23:46 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 333 - Failure! In-Reply-To: <80e07848-490c-2d38-2def-dbb3b3d3e4f1@windriver.com> References: <1864792267.432.1606880588117.JavaMail.javamailuser@localhost> <49e530d5-c550-45ed-0ced-7de11358d207@windriver.com> <80e07848-490c-2d38-2def-dbb3b3d3e4f1@windriver.com> Message-ID: <0f4ce118-ed84-d928-e5e0-f46d1441c3d5@windriver.com> Add https://review.opendev.org/c/starlingx/tools/+/765091 (merged) to revert 765179 which breaks in the absence to 762701 Starting the build again... Sorry for the mess folks. Scott On 2020-12-02 2:46 p.m., Scott Little wrote: > Fixes have merged. > > A fresh CENGN build is underfway. > > Scott > > > On 2020-12-02 1:45 p.m., Scott Little wrote: >> Fixes posted for review. >> >> # Fix for 762700 >> https://review.opendev.org/c/starlingx/tools/+/765179 >> >> # Reversion of 762701 >> https://review.opendev.org/c/starlingx/root/+/765191 >> >> >> Scott >> >> >> On 2020-12-02 12:05 p.m., Scott Little wrote: >>> The build failure was cause by the merge of code intended to add >>> support for building in a centos 8 environment.  The update was >>> intended to retain support for centos 7. >>> >>> The build failed because it tried to use a centos 8 mock >>> configuration within a centos 7 build container. >>> >>> Two bugs have been identified that when combined produced the failure. >>> >>> Commits that introduced the error: >>> https://review.opendev.org/c/starlingx/tools/+/762700 >>> https://review.opendev.org/c/starlingx/root/+/762701 >>> >>> I'll be posting a fix shortly >>> >>> Scott Little >>> >>> >>> On 2020-12-01 10:43 p.m., build.starlingx at gmail.com wrote: >>>> [Please note this e-mail is from an EXTERNAL e-mail address] >>>> >>>> Project: STX_build_layer_flock_master_master >>>> Build #: 333 >>>> Status: Failure >>>> Timestamp: 20201202T023718Z >>>> Branch: master >>>> >>>> Check logs at: >>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T023718Z/logs >>>> -------------------------------------------------------------------------------- >>>> Parameters >>>> >>>> FULL_BUILD: false >>>> FORCE_BUILD: false >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Dec 2 21:16:43 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 2 Dec 2020 16:16:43 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1351 - Failure! Message-ID: <1360036603.458.1606943803836.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1351 Status: Failure Timestamp: 20201202T204330Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20201202T202347Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20201202T202347Z DOCKER_BUILD_ID: jenkins-master-distro-20201202T202347Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20201202T202347Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20201202T202347Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From maryx.camp at intel.com Wed Dec 2 22:30:13 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 2 Dec 2020 22:30:13 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-12-02 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-12-02  All -- reviews merged since last meeting:  5  All -- bug status -- 21 total - team agrees to defer all low priority LP until the upstreaming effort is completed.  13 LP submitted by https://launchpad.net/~leiyuehui against API documentation, which is generated from source code (low priority). Reviews here: https://review.opendev.org/#/q/project:starlingx/config Reviews in progress:   upstream docs, rook reviews Upstreaming Status: 3 major guides are now merged: Fault Management, Data Networks, and User Tasks. Congrats to the team!  5 guides are WIP: Deployment Configuration, System Config, Storage Config, Node Management, Security Approx 7 guides remaining - some will be divided into other guides (Distributed Cloud is one example of this). Need to compare to Greg's original TOC and see if any updates to the plan.  STX backup and restore:  https://docs.starlingx.io/developer_resources/backup_restore.html Release request submitted to Openstack Tools team by Jeremy Stanley. When merged, this will activate the rubric styling for Prerequisites.  https://review.opendev.org/765192       Deployment Configuration guide - https://review.opendev.org/c/starlingx/docs/+/764491  Mary had a review comment about installation diagrams in upstream vs STX docs - Ron is using the STX diagrams, no issues. Abbreviations for acronyms   Ron asked: is there a list or guidelines on what is expected? Ignore common terms like CPU? When to do it - first instance only or every time?   He proposes using substitutions/strings file to define them all instead of cluttering up the rst file with :abbr:`blah blah blah`   Team agrees this is a good idea. In practice, it will look like this:  |AIO|  instead of :abbr:`AIO (All-In-One)`   Note that the string doesn't work for a plural term. |PVC|s will not work. For some common terms we will need 2 forms like this |PVC| and |PVCs|   Ron will start creating the strings file and team can review it. We can use it to create a Glossary later. From build.starlingx at gmail.com Wed Dec 2 23:51:30 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 2 Dec 2020 18:51:30 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_base_image - Build # 354 - Still Failing! In-Reply-To: <409054802.412.1606839622793.JavaMail.javamailuser@localhost> References: <409054802.412.1606839622793.JavaMail.javamailuser@localhost> Message-ID: <477165254.462.1606953090946.JavaMail.javamailuser@localhost> Project: STX_build_docker_base_image Build #: 354 Status: Still Failing Timestamp: 20201202T235036Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201202T232432Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201202T232432Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20201202T232432Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201202T232432Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201202T232432Z/logs WEB_HOST_PORT: 80 OS_VERSION: 7.5.1804 BUILD_STREAM: stable REGISTRY_ORG: starlingx BASE_LATEST_TAG: master-stable-latest PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201202T232432Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201202T232432Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Wed Dec 2 23:51:32 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 2 Dec 2020 18:51:32 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 64 - Still Failing! In-Reply-To: <1414870630.415.1606839626055.JavaMail.javamailuser@localhost> References: <1414870630.415.1606839626055.JavaMail.javamailuser@localhost> Message-ID: <696037133.465.1606953093408.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 64 Status: Still Failing Timestamp: 20201202T235036Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201202T232432Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201202T232432Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201202T232432Z/logs MASTER_BUILD_NUMBER: 87 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201202T232432Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20201202T232432Z DOCKER_BUILD_ID: jenkins-master-containers-20201202T232432Z-builder TIMESTAMP: 20201202T232432Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201202T232432Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201202T232432Z/outputs From build.starlingx at gmail.com Wed Dec 2 23:51:35 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 2 Dec 2020 18:51:35 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 87 - Still Failing! In-Reply-To: <789498562.418.1606839629024.JavaMail.javamailuser@localhost> References: <789498562.418.1606839629024.JavaMail.javamailuser@localhost> Message-ID: <1022405759.468.1606953095625.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 87 Status: Still Failing Timestamp: 20201202T232432Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201202T232432Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From murthyp at gmail.com Thu Dec 3 03:35:28 2020 From: murthyp at gmail.com (Prashant Murthy) Date: Thu, 3 Dec 2020 09:05:28 +0530 Subject: [Starlingx-discuss] DC for 2 AIO-SX - in VMs In-Reply-To: References: Message-ID: Thanks Bart. I would have the 4th VM as well in the same setup, but then exactly setting it up as a router - which connects the subclouds to the DCM - those instructions or network diagram if present it will become easier. Thanks, Prashant On Wed, Dec 2, 2020 at 9:02 PM Wensley, Barton wrote: > Prashant, > > > > It is possible to set up a Distributed Cloud system in VMs, but we do not > have instructions for that. The System Controller needs to be connected to > the Subclouds over an L3 network, so you need to create another VM to act > as the router between the System Controller and the subclouds. > > > > Bart > > > > *From:* Prashant Murthy > *Sent:* Wednesday, December 2, 2020 5:27 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] DC for 2 AIO-SX - in VMs > > > > [Please note this e-mail is from an EXTERNAL e-mail address] > > Hi, > > > > I could successfully install two AIO-SX in two VMs. But I also wanted to > try the Distributed Cloud management in a 3rd VM - which can manage these > two clusters. But the installation of Distributed cloud is provided only on > Bare Metal. Can that be installed and tried on a VM? > > > > > https://docs.starlingx.io/deploy_install_guides/r4_release/distributed_cloud/index.html > > > > Thanks, > > Prashant > -- "The big challenge is to become all that you have the potential of becoming" -------------- next part -------------- An HTML attachment was scrubbed... URL: From haridhar.kalvala at intel.com Thu Dec 3 08:08:35 2020 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Thu, 3 Dec 2020 08:08:35 +0000 Subject: [Starlingx-discuss] Distro (Non-OpenStack) Meeting Minutes - 11/25 In-Reply-To: References: Message-ID: Hi Saul, As discussed in last meeting regarding remaining complete list of centos migration, just want to check is the list available to share. Thank you, Haridhar Kalvala > -----Original Message----- > From: Saul Wold > Sent: Wednesday, November 25, 2020 11:16 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Distro (Non-OpenStack) Meeting Minutes - 11/25 > > > > Agenda 11/25 meeting: > 1) Rook Ceph Status > - Duplex solution needs to be re-worked exisit, Martin is working this > - By end of 11/27 should have an update. > 2) CentOS-8 Update > - Working on remaining StarlingX packages build with about 10 packages > remaining. > - Vanilla ISO is buildable, installable, and boots with login. > - 3 issues sent to discuss list regarding chart museum rebase > - Currently maintaining some local patches which need to get pushed to > gerrit > f/centos-8 merge status > - Need to provide specific repos to Neusoft that have conflicts > - Davlet/Scott will look root and tools repos > Please use centos8 as topic for centos8 related work > Discussion of dnf modular filtering - move to email to get clarification. > 3) Python3 Status > - Would like to talk about where this work left off. > - Is https://wiki.openstack.org/wiki/StarlingX/Python2 up to date? > - The wiki needs to be updated based on story status > - Some specfiles updated for new python3 requires > - was all flock services addressed? > - Check status email for failing builds > - No actual functional testing done since no actual provisioning was done > > Next meeting: 12/9 > > > -- > Sau! > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Haiqing.Bai at windriver.com Thu Dec 3 09:14:18 2020 From: Haiqing.Bai at windriver.com (Bai, Haiqing) Date: Thu, 3 Dec 2020 09:14:18 +0000 Subject: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue In-Reply-To: <9b658d67-fffe-68a6-e87f-505811fb21cd@neusoft.com> References: <6362974c-12d4-1be3-b7d2-c9d4a081b765@neusoft.com> <9b658d67-fffe-68a6-e87f-505811fb21cd@neusoft.com> Message-ID: Yes, both “python3-ipaddr” and “python3-ipaddr” do not exist and removed. Now I think we have to face the issue caused by “python2” to “python3”: 07:48:56 TMPDIR=/localdisk/loadbuild/hbai/c81nststx/tmp dnf repoquery -c /localdisk/loadbuild/hbai/c81nststx/export/yum.conf --repoid=local-rt --arch=x86_64,noarch platform-python --qf='%{name} %{name}-%{version}-%{release}.%{arch}.rpm %{relativepath}' 07:48:56 local-rt 3.0 MB/s | 3.0 kB 00:00 07:48:56 TMPDIR=/localdisk/loadbuild/hbai/c81nststx/tmp dnf repoquery -c /localdisk/loadbuild/hbai/c81nststx/export/yum.conf --repoid=local-installer --arch=x86_64,noarch platform-python --qf='%{name} %{name}-%{version}-%{release}.%{arch}.rpm %{relativepath}' 07:48:57 local-installer 2.9 MB/s | 3.0 kB 00:00 07:48:57 TMPDIR=/localdisk/loadbuild/hbai/c81nststx/tmp dnf repoquery -c /localdisk/loadbuild/hbai/c81nststx/export/yum.conf --repoid=StxCentos8Distro --arch=x86_64,noarch platform-python --qf='%{name} %{name}-%{version}-%{release}.%{arch}.rpm %{relativepath}' 07:48:57 Last metadata expiration check: 0:01:43 ago on Thu 03 Dec 2020 07:47:14 AM UTC. 07:48:57 STR=platform-python platform-python-3.6.8-15.1.el8.x86_64.rpm x86_64/platform-python-3.6.8-15.1.el8.x86_64.rpm 07:48:57 Installing PKG=platform-python PKG_FILE=platform-python-3.6.8-15.1.el8.x86_64.rpm PKG_REL_PATH=x86_64/platform-python-3.6.8-15.1.el8.x86_64.rpm PKG_PATH=/localdisk/designer/hbai/c81nststx/cgcs-root/cgcs-centos-repo/Binary/x86_64/platform-python-3.6.8-15.1.el8.x86_64.rpm from repo StxCentos8Distro 07:48:57 Debug: Packages still unresolved: 07:48:57 07:48:59 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/hbai/c81nststx/export/deps.txt for details -- exiting 07:48:59 These RPMS had problems (likely version conflicts) 07:48:59 python(abi) 07:48:59 PyYAML 07:48:59 Could not install dependencies It seems this means that at least not all “python2 runtime dependency” have been addressed on current stx. From: fuyong Sent: Tuesday, December 1, 2020 2:54 PM To: Bai, Haiqing ; starlingx-discuss at lists.starlingx.io Cc: Wold, Saul Subject: Re: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue [Please note this e-mail is from an EXTERNAL e-mail address] Hi Haiqing Bai Maybe you can run the following command "dnf repo-pkgs -c $MY_WORKSPACE/std/yum.conf local-std list" Make sure the rpm you listed is included in the local-std repo config/sysinv Requires: python3-ipaddr. But python3-ipaddr package does not exist in centos8 utilites/python-cephclient Requires: python3-ipaddress. But python3-ipaddress package does not exist in centos8 Please confirm in sysinv and python-cephclient, and compile after commenting. B,R Yong Fu On 2020/12/1 上午11:58, Bai, Haiqing wrote: Yes, libvirt can be compiled ok and each sub packages are created, for example: -rw-r--r-- 1 hbai 751 7784 11月 30 22:41 libvirt-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 1921432 11月 30 22:41 libvirt-docs-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 8740 11月 30 22:41 libvirt-daemon-config-network-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 700736 11月 30 22:41 libvirt-daemon-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 12728 11月 30 22:41 libvirt-daemon-config-nwfilter-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 243360 11月 30 22:41 libvirt-daemon-driver-network-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 74268 11月 30 22:41 libvirt-daemon-driver-nwfilter-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 48976 11月 30 22:41 libvirt-daemon-driver-nodedev-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 49204 11月 30 22:41 libvirt-daemon-driver-interface-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 37812 11月 30 22:41 libvirt-daemon-driver-secret-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 269600 11月 30 22:41 libvirt-daemon-driver-storage-core-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 40708 11月 30 22:41 libvirt-daemon-driver-storage-logical-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 39512 11月 30 22:41 libvirt-daemon-driver-storage-disk-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 36836 11月 30 22:41 libvirt-daemon-driver-storage-scsi-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 36780 11月 30 22:41 libvirt-daemon-driver-storage-iscsi-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 38952 11月 30 22:41 libvirt-daemon-driver-storage-iscsi-direct-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 35020 11月 30 22:41 libvirt-daemon-driver-storage-mpath-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 48772 11月 30 22:41 libvirt-daemon-driver-storage-gluster-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 43076 11月 30 22:41 libvirt-daemon-driver-storage-rbd-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 6756 11月 30 22:41 libvirt-daemon-driver-storage-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 612932 11月 30 22:41 libvirt-daemon-driver-qemu-4.7.0-1.tis.101.x86_64.rpm -rw-r--r-- 1 hbai 751 6540 11月 30 22:41 libvirt-daemon-lxc-4.7.0-1.tis.101.x86_64.rpm …… But “build-iso” complains: 10:19:34 Could not resolve packages: libvirt libvirt-client libvirt-daemon libvirt-daemon-config-network It seems version conflicts with “libvirt.so” and some “python2” upgrading to “python3” runtime dependency issues have not been resolved yet. From: fuyong Sent: Tuesday, December 1, 2020 9:12 AM To: Bai, Haiqing ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue [Please note this e-mail is from an EXTERNAL e-mail address] Hi Haiqing Bai Has libvirt compiled successfully in your integ directory? python3-ipaddr has no el8 version. At present, you need to comment out the place where python3-ipaddr is dependent B,R Yong On 2020/11/30 上午10:26, Bai, Haiqing wrote: Build-iso on f/centos8 branch has below runtime dependency list: ============================================================== Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/hbai/c81nststx/export/deps.txt for details -- exiting These RPMS had problems (likely version conflicts) libvirt-daemon libvirt-daemon-driver-network libvirt.so.0()(64bit) libvirt.so.0(LIBVIRT_0.0.3)(64bit) libvirt.so.0(LIBVIRT_0.1.0)(64bit) libvirt.so.0(LIBVIRT_0.6.1)(64bit) libvirt.so.0(LIBVIRT_0.9.0)(64bit) libvirt.so.0(LIBVIRT_0.9.3)(64bit) libvirt.so.0(LIBVIRT_1.0.2)(64bit) libvirt.so.0(LIBVIRT_1.0.6)(64bit) libvirt.so.0(LIBVIRT_4.5.0)(64bit) libvirt.so.0(LIBVIRT_PRIVATE_4.7.0)(64bit) python3-ipaddr python3-ipaddress python-kubernetes python-pint PyYAML qemu-kvm-ev I remembered the python3-ipaddr issue had been mentioned before by some guys, anyone knows the latest status of that issue? thanks B,R Haiqing Bai _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Dec 3 10:04:03 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Dec 2020 05:04:03 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 1117 - Failure! Message-ID: <177809657.475.1606989844008.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup Build #: 1117 Status: Failure Timestamp: 20201203T100401Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201203T100001Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: f-centos8 MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-centos8/20201203T100001Z DOCKER_BUILD_ID: jenkins-f-centos8-20201203T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201203T100001Z/logs DOCKER_BUILD_TAG: f-centos8-20201203T100001Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201203T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Thu Dec 3 10:04:06 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Dec 2020 05:04:06 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 46 - Still Failing! In-Reply-To: <1593789553.450.1606936591396.JavaMail.javamailuser@localhost> References: <1593789553.450.1606936591396.JavaMail.javamailuser@localhost> Message-ID: <1611744543.478.1606989846748.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 46 Status: Still Failing Timestamp: 20201203T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201203T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From murthyp at gmail.com Thu Dec 3 10:35:19 2020 From: murthyp at gmail.com (Prashant Murthy) Date: Thu, 3 Dec 2020 16:05:19 +0530 Subject: [Starlingx-discuss] =?utf-8?q?=28no_subject=29?= Message-ID: Hi, I had installed AIO-SX on one VM and things were fine - k8s came up. But after reboot of the VM, I was not able to access it. So I again followed the steps in to re-install. https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_install_kubernetes.html I did only step 1 and 4 here: 'Bootstrap system on controller-0' - also ansible install failed. failed: [localhost] (item=Openstack Admin credentials can only be loaded from the active controller.) => {"changed": true, "cmd": "source /etc/platform/openrc; openstack secret delete Openstack Admin credentials can only be loaded from the active controller.", "delta": "0:00:03.579807", "end": "2020-12-03 10:29:15.269034", "item": "Openstack Admin credentials can only be loaded from the active controller.", "msg": "non-zero return code", "rc": 1, "start": "2020-12-03 10:29:11.689227", "stderr": "No password entered, or found via --os-password or OS_PASSWORD", "stderr_lines": ["No password entered, or found via --os-password or OS_PASSWORD"], "stdout": "Openstack Admin credentials can only be loaded from the active controller.", "stdout_lines": ["Openstack Admin credentials can only be loaded from the active controller."]} But on "source /etc/platform/openrc" - I get this error: Openstack Admin credentials can only be loaded from the active controller. I need only k8s - not the openstack. Can someone please provide additional info? Thanks, Prashant -------------- next part -------------- An HTML attachment was scrubbed... URL: From murthyp at gmail.com Thu Dec 3 13:13:00 2020 From: murthyp at gmail.com (Prashant Murthy) Date: Thu, 3 Dec 2020 18:43:00 +0530 Subject: [Starlingx-discuss] AIO-SX install In-Reply-To: References: Message-ID: On Thu, Dec 3, 2020 at 4:07 PM Prashant Murthy wrote: > Hi, > > I had installed AIO-SX on one VM and things were fine - k8s came up. But > after reboot of the VM, I was not able to access it. So I again followed > the steps in to re-install. > > https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_install_kubernetes.html > > I did only step 1 and 4 here: 'Bootstrap system on controller-0' - also > ansible install failed. > > failed: [localhost] (item=Openstack Admin credentials can only be loaded > from the active controller.) => {"changed": true, "cmd": "source > /etc/platform/openrc; openstack secret delete Openstack Admin credentials > can only be loaded from the active controller.", "delta": "0:00:03.579807", > "end": "2020-12-03 10:29:15.269034", "item": "Openstack Admin credentials > can only be loaded from the active controller.", "msg": "non-zero return > code", "rc": 1, "start": "2020-12-03 10:29:11.689227", "stderr": "No > password entered, or found via --os-password or OS_PASSWORD", > "stderr_lines": ["No password entered, or found via --os-password or > OS_PASSWORD"], "stdout": "Openstack Admin credentials can only be loaded > from the active controller.", "stdout_lines": ["Openstack Admin credentials > can only be loaded from the active controller."]} > > But on "source /etc/platform/openrc" - I get this error: > Openstack Admin credentials can only be loaded from the active controller. > > I need only k8s - not the openstack. Can someone please provide additional > info? > > Thanks, > Prashant > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- "The big challenge is to become all that you have the potential of becoming" -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Dec 3 14:38:33 2020 From: scott.little at windriver.com (Scott Little) Date: Thu, 3 Dec 2020 09:38:33 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 333 - Failure! In-Reply-To: <0f4ce118-ed84-d928-e5e0-f46d1441c3d5@windriver.com> References: <1864792267.432.1606880588117.JavaMail.javamailuser@localhost> <49e530d5-c550-45ed-0ced-7de11358d207@windriver.com> <80e07848-490c-2d38-2def-dbb3b3d3e4f1@windriver.com> <0f4ce118-ed84-d928-e5e0-f46d1441c3d5@windriver.com> Message-ID: <5a1d0b77-fad5-4067-bcf4-3b4541a01b5c@windriver.com> We are now able to build packages and iso's again. Docker image builds are still having issues.  I continue to investigate ... Scott On 2020-12-02 3:23 p.m., Scott Little wrote: > Add https://review.opendev.org/c/starlingx/tools/+/765091 (merged) to > revert 765179 which breaks in the absence to 762701 > > Starting the build again... > > Sorry for the mess folks. > > Scott > > > On 2020-12-02 2:46 p.m., Scott Little wrote: >> Fixes have merged. >> >> A fresh CENGN build is underfway. >> >> Scott >> >> >> On 2020-12-02 1:45 p.m., Scott Little wrote: >>> Fixes posted for review. >>> >>> # Fix for 762700 >>> https://review.opendev.org/c/starlingx/tools/+/765179 >>> >>> # Reversion of 762701 >>> https://review.opendev.org/c/starlingx/root/+/765191 >>> >>> >>> Scott >>> >>> >>> On 2020-12-02 12:05 p.m., Scott Little wrote: >>>> The build failure was cause by the merge of code intended to add >>>> support for building in a centos 8 environment.  The update was >>>> intended to retain support for centos 7. >>>> >>>> The build failed because it tried to use a centos 8 mock >>>> configuration within a centos 7 build container. >>>> >>>> Two bugs have been identified that when combined produced the failure. >>>> >>>> Commits that introduced the error: >>>> https://review.opendev.org/c/starlingx/tools/+/762700 >>>> https://review.opendev.org/c/starlingx/root/+/762701 >>>> >>>> I'll be posting a fix shortly >>>> >>>> Scott Little >>>> >>>> >>>> On 2020-12-01 10:43 p.m., build.starlingx at gmail.com wrote: >>>>> [Please note this e-mail is from an EXTERNAL e-mail address] >>>>> >>>>> Project: STX_build_layer_flock_master_master >>>>> Build #: 333 >>>>> Status: Failure >>>>> Timestamp: 20201202T023718Z >>>>> Branch: master >>>>> >>>>> Check logs at: >>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T023718Z/logs >>>>> -------------------------------------------------------------------------------- >>>>> Parameters >>>>> >>>>> FULL_BUILD: false >>>>> FORCE_BUILD: false >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Thu Dec 3 14:48:19 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 3 Dec 2020 14:48:19 +0000 Subject: [Starlingx-discuss] (no subject) In-Reply-To: References: Message-ID: When you say you “did only step 1 and 4”, do you mean that you skipped steps 2 and 3 of the bootstrap instructions? From: Prashant Murthy Sent: Thursday, December 3, 2020 5:35 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] (no subject) [Please note this e-mail is from an EXTERNAL e-mail address] Hi, I had installed AIO-SX on one VM and things were fine - k8s came up. But after reboot of the VM, I was not able to access it. So I again followed the steps in to re-install. https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_install_kubernetes.html I did only step 1 and 4 here: 'Bootstrap system on controller-0' - also ansible install failed. failed: [localhost] (item=Openstack Admin credentials can only be loaded from the active controller.) => {"changed": true, "cmd": "source /etc/platform/openrc; openstack secret delete Openstack Admin credentials can only be loaded from the active controller.", "delta": "0:00:03.579807", "end": "2020-12-03 10:29:15.269034", "item": "Openstack Admin credentials can only be loaded from the active controller.", "msg": "non-zero return code", "rc": 1, "start": "2020-12-03 10:29:11.689227", "stderr": "No password entered, or found via --os-password or OS_PASSWORD", "stderr_lines": ["No password entered, or found via --os-password or OS_PASSWORD"], "stdout": "Openstack Admin credentials can only be loaded from the active controller.", "stdout_lines": ["Openstack Admin credentials can only be loaded from the active controller."]} But on "source /etc/platform/openrc" - I get this error: Openstack Admin credentials can only be loaded from the active controller. I need only k8s - not the openstack. Can someone please provide additional info? Thanks, Prashant -------------- next part -------------- An HTML attachment was scrubbed... URL: From ch.huang789 at advantech.com.tw Thu Dec 3 15:58:54 2020 From: ch.huang789 at advantech.com.tw (CH.Huang789) Date: Thu, 3 Dec 2020 15:58:54 +0000 Subject: [Starlingx-discuss] Missing host-port in controller-1 Message-ID: <3018be5330cc48bd8095fc1606f26597@taipei09.ADVANTECH.CORP> Dear Sir: I have 2 exact the same bare metal machines. The controller-1 lost eno2 – eno4 in the “system host-port-list”. Can someone help me how to solve it? [sysadmin at controller-0 ~(keystone_admin)]$ system host-port-list 1 +--------------------------------------+------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | 2c52c301-9398-4017-bb57-16c265e8b4db | eno1 | ethernet | 0000:1c:00.0 | 0 | 0 | True | Ethernet Connection X722 for 10GbE SFP+ [37d3] | | 3c92fb60-6a59-41f9-835f-cf96d5a08686 | eno2 | ethernet | 0000:1c:00.1 | 0 | 0 | True | Ethernet Connection X722 for 10GbE SFP+ [37d3] | | 4b90b755-5fba-4b55-91e9-d28fc9603620 | eno3 | ethernet | 0000:1c:00.2 | 0 | 0 | True | Ethernet Connection X722 for 10GbE SFP+ [37d3] | | dbf486ce-f71c-40ad-adbd-bd7bb6d446c4 | eno4 | ethernet | 0000:1c:00.3 | 0 | 0 | True | Ethernet Connection X722 for 10GbE SFP+ [37d3] | | 0d52f733-6f94-4321-a21c-0e655ccee987 | eno5 | ethernet | 0000:01:00.0 | 0 | 0 | True | I210 Gigabit Network Connection [1533] | | f15b90ef-b16d-4abe-bd00-a415233971c9 | eno6 | ethernet | 0000:02:00.0 | 0 | 0 | True | I210 Gigabit Network Connection [1533] | | 6dec8bee-d11b-4808-ac49-b943087f7ffa | eno7 | ethernet | 0000:05:00.0 | 0 | 0 | True | I210 Gigabit Network Connection [1533] | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system host-port-list 2 +--------------------------------------+------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ | b4be29b2-eb7f-40ce-9f6e-a429bfe42d8d | eno1 | ethernet | 0000:1c:00.0 | 0 | 0 | True | Ethernet Connection X722 for 10GbE SFP+ [37d3] | | c646820c-4bca-4abe-ad89-a310c49395a6 | eno5 | ethernet | 0000:01:00.0 | 0 | 0 | True | I210 Gigabit Network Connection [1533] | | b072e986-5904-4868-a027-64bc5f1cea23 | eno6 | ethernet | 0000:02:00.0 | 0 | 0 | True | I210 Gigabit Network Connection [1533] | | a9b6bfcd-4372-438b-b2c6-ed09dd67e98f | eno7 | ethernet | 0000:05:00.0 | 0 | 0 | True | I210 Gigabit Network Connection [1533] | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+------------------------------------------------+ Regards, C.H. Huang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Thu Dec 3 16:16:29 2020 From: Saul.Wold at windriver.com (Saul Wold) Date: Thu, 3 Dec 2020 08:16:29 -0800 Subject: [Starlingx-discuss] Distro (Non-OpenStack) Meeting Minutes - 11/25 In-Reply-To: References: Message-ID: Haridhar: Here is the high level list of activities, some of this can be done in parallel and some of it has to wait for other tasks to complete. Let me know if you have any questions about this. Sau! Get existing CentOS-8.0 branch built and brought-up - Build of Packages - ISO Built - Test bringup from ISO and install - Provisioning (will fail) Update CentOS8 branch to master (could be in parallel with 1 above) - Initial update of all repos - Update Tools and Root Repos - Update of other repos with conflicts - Continued Update (every other sprint) Upgrade CentOS 8.0 to 8.2 in Starling X - Binary Package update / Mirror - Source sprm/tarball update and patch cleanup - ISO build / boot / install Kernel Performance Testing and Addressing Issues Update Flock both for CentOS8 and Python3, include functional testing - stx-upstream - stx-update - stx-fault - stx-metal - stx-ha - stx-config - stx-nfv - stx-distcloud - stx-distcloud-client - stx-gui Bring up and validate simplex / duplex / standard environments Update Non-CentOS middleware components (Ceph/k8s/drdb/puppet) - Ceph - Mimic -> Nautilus (Stable / LTS Release) - K8S - Stay with current version of K8S - rebuild for CentOS-8.2 - Upversion DRBD RPMs to 9.13 (from 8.4) - drop or port patched as necessary (10 patches). - Regression test DRBD functionality - fix any issues that interacts DRBD (ansible, sysinv, puppet, OCF script, etc…). - Puppet - Upversion puppet RPM to 6.19.0 (from 4.8.2) - drop or port patches as necessary (5 patches). - Upversion any puppet dependencies as necessary (e.g. ruby, hiera). - Upversion the 3rd party puppet modules (~20) - port patches. - Update platform puppet modules (~10) to work with new version. - Testing to verify that all the above holds together. Testing & Cut Over - Gradual System Testing (would be same as release system testing) - Community Cut Over Period - Sanity Testing - Bug fixing - Regression Testing Release Process On 12/3/20 12:08 AM, Kalvala, Haridhar wrote: > Hi Saul, > > As discussed in last meeting regarding remaining complete list of centos migration, just want to check is the list available to share. > > Thank you, > Haridhar Kalvala > >> -----Original Message----- >> From: Saul Wold >> Sent: Wednesday, November 25, 2020 11:16 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] Distro (Non-OpenStack) Meeting Minutes - 11/25 >> >> >> >> Agenda 11/25 meeting: >> 1) Rook Ceph Status >> - Duplex solution needs to be re-worked exisit, Martin is working this >> - By end of 11/27 should have an update. >> 2) CentOS-8 Update >> - Working on remaining StarlingX packages build with about 10 packages >> remaining. >> - Vanilla ISO is buildable, installable, and boots with login. >> - 3 issues sent to discuss list regarding chart museum rebase >> - Currently maintaining some local patches which need to get pushed to >> gerrit >> f/centos-8 merge status >> - Need to provide specific repos to Neusoft that have conflicts >> - Davlet/Scott will look root and tools repos >> Please use centos8 as topic for centos8 related work >> Discussion of dnf modular filtering - move to email to get clarification. >> 3) Python3 Status >> - Would like to talk about where this work left off. >> - Is https://wiki.openstack.org/wiki/StarlingX/Python2 up to date? >> - The wiki needs to be updated based on story status >> - Some specfiles updated for new python3 requires >> - was all flock services addressed? >> - Check status email for failing builds >> - No actual functional testing done since no actual provisioning was done >> >> Next meeting: 12/9 >> >> >> -- >> Sau! >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Sau! From alexandru.dimofte at intel.com Thu Dec 3 21:04:14 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 3 Dec 2020 21:04:14 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201202T221143Z Message-ID: Sanity Test from 2020-December-2 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T221143Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T221143Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From build.starlingx at gmail.com Thu Dec 3 21:19:24 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Dec 2020 16:19:24 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 300 - Failure! Message-ID: <513091928.482.1607030365462.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 300 Status: Failure Timestamp: 20201203T155259Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201203T150133Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201203T150133Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20201203T150133Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201203T150133Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201203T150133Z/logs PUBLISH_TIMESTAMP: 20201203T150133Z FLOCK_VERSION: master-centos-stable-20201203T150133Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20201203T150133Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201203T150133Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Thu Dec 3 21:19:27 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Dec 2020 16:19:27 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 65 - Still Failing! In-Reply-To: <650309278.463.1606953091517.JavaMail.javamailuser@localhost> References: <650309278.463.1606953091517.JavaMail.javamailuser@localhost> Message-ID: <105222228.485.1607030367946.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 65 Status: Still Failing Timestamp: 20201203T153212Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201203T150133Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201203T150133Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201203T150133Z/logs MASTER_BUILD_NUMBER: 88 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201203T150133Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20201203T150133Z DOCKER_BUILD_ID: jenkins-master-containers-20201203T150133Z-builder TIMESTAMP: 20201203T150133Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201203T150133Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201203T150133Z/outputs From build.starlingx at gmail.com Thu Dec 3 21:19:29 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Dec 2020 16:19:29 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 88 - Still Failing! In-Reply-To: <387263711.466.1606953093977.JavaMail.javamailuser@localhost> References: <387263711.466.1606953093977.JavaMail.javamailuser@localhost> Message-ID: <95798756.488.1607030370466.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 88 Status: Still Failing Timestamp: 20201203T150133Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201203T150133Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From murthyp at gmail.com Fri Dec 4 04:50:41 2020 From: murthyp at gmail.com (Prashant Murthy) Date: Fri, 4 Dec 2020 10:20:41 +0530 Subject: [Starlingx-discuss] (no subject) In-Reply-To: References: Message-ID: Yes.. again did all steps and things were fine. On Thu, Dec 3, 2020 at 8:18 PM Penney, Don wrote: > When you say you “did only step 1 and 4”, do you mean that you skipped > steps 2 and 3 of the bootstrap instructions? > > > > > > *From:* Prashant Murthy > *Sent:* Thursday, December 3, 2020 5:35 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] (no subject) > > > > [Please note this e-mail is from an EXTERNAL e-mail address] > > Hi, > > > > I had installed AIO-SX on one VM and things were fine - k8s came up. But > after reboot of the VM, I was not able to access it. So I again followed > the steps in to re-install. > > > https://docs.starlingx.io/deploy_install_guides/r4_release/virtual/aio_simplex_install_kubernetes.html > > > > I did only step 1 and 4 here: 'Bootstrap system on controller-0' - also > ansible install failed. > > > > failed: [localhost] (item=Openstack Admin credentials can only be loaded > from the active controller.) => {"changed": true, "cmd": "source > /etc/platform/openrc; openstack secret delete Openstack Admin credentials > can only be loaded from the active controller.", "delta": "0:00:03.579807", > "end": "2020-12-03 10:29:15.269034", "item": "Openstack Admin credentials > can only be loaded from the active controller.", "msg": "non-zero return > code", "rc": 1, "start": "2020-12-03 10:29:11.689227", "stderr": "No > password entered, or found via --os-password or OS_PASSWORD", > "stderr_lines": ["No password entered, or found via --os-password or > OS_PASSWORD"], "stdout": "Openstack Admin credentials can only be loaded > from the active controller.", "stdout_lines": ["Openstack Admin credentials > can only be loaded from the active controller."]} > > > > But on "source /etc/platform/openrc" - I get this error: > > Openstack Admin credentials can only be loaded from the active controller. > > > > I need only k8s - not the openstack. Can someone please provide additional > info? > > > > Thanks, > > Prashant > -- "The big challenge is to become all that you have the potential of becoming" -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Fri Dec 4 07:47:54 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 4 Dec 2020 07:47:54 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201203T023600Z Message-ID: Sanity Test from 2020-December-3 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201203T023600Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201203T023600Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From build.starlingx at gmail.com Fri Dec 4 10:06:02 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 4 Dec 2020 05:06:02 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 47 - Still Failing! In-Reply-To: <1774337873.476.1606989844626.JavaMail.javamailuser@localhost> References: <1774337873.476.1606989844626.JavaMail.javamailuser@localhost> Message-ID: <2129291525.494.1607076363468.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 47 Status: Still Failing Timestamp: 20201204T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201204T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From amy at demarco.com Fri Dec 4 18:17:22 2020 From: amy at demarco.com (Amy Marrich) Date: Fri, 4 Dec 2020 12:17:22 -0600 Subject: [Starlingx-discuss] [Diversity] Diversity & Inclusion Meeting 12/7 Message-ID: The Diversity & Inclusion WG invites members of all OSF projects to our next meeting Monday, December 7th, at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity -wg-agenda. Please feel free to add any other topics you wish to discuss at the meeting. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Fri Dec 4 19:44:09 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 4 Dec 2020 19:44:09 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201204T023729Z Message-ID: Sanity Test from 2020-December-4 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201204T023729Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201204T023729Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From build.starlingx at gmail.com Sat Dec 5 19:06:40 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 5 Dec 2020 14:06:40 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_download_mirror - Build # 1080 - Failure! Message-ID: <1380936842.500.1607195201657.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1080 Status: Failure Timestamp: 20201205T100225Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201205T100001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/centos8 DOCKER_BUILD_ID: jenkins-f-centos8-20201205T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201205T100001Z/logs MY_REPO: /localdisk/designer/jenkins/f-centos8/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201205T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Sat Dec 5 19:06:43 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 5 Dec 2020 14:06:43 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 48 - Still Failing! In-Reply-To: <1367380190.492.1607076361693.JavaMail.javamailuser@localhost> References: <1367380190.492.1607076361693.JavaMail.javamailuser@localhost> Message-ID: <357893445.503.1607195204242.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 48 Status: Still Failing Timestamp: 20201205T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201205T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From alexandru.dimofte at intel.com Sat Dec 5 20:18:48 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 5 Dec 2020 20:18:48 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201205T023257Z Message-ID: Sanity Test from 2020-December-5 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201205T023257Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201204T023729Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Obs: We used the helm-charts from previous build because the helm-charts from current build were not generated. =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 8408 bytes Desc: image002.png URL: From haochuan.z.chen at intel.com Mon Dec 7 01:14:36 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 7 Dec 2020 01:14:36 +0000 Subject: [Starlingx-discuss] ceph containerization status update Message-ID: Rook status sync meeting link https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2252 bytes Desc: not available URL: From haochuan.z.chen at intel.com Mon Dec 7 05:59:10 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 7 Dec 2020 05:59:10 +0000 Subject: [Starlingx-discuss] review patch for enable rook-ceph in openstack-armada-app project Message-ID: Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Dec 7 06:05:33 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 7 Dec 2020 06:05:33 +0000 Subject: [Starlingx-discuss] patch review for rook, project starling/utilities In-Reply-To: References: Message-ID: Thanks Don Penney and Scott review for my patch. Welcome more review and wish W+1 Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, December 1, 2020 8:43 PM To: 'Scott Little' ; 'Qian, Bin' ; 'MacDonald, Eric' ; 'Bart Wensley' ; 'Kung, John' ; 'Waines, Greg' ; 'Poncea, Ovidiu' Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: patch review for rook, project starling/utilities Add Ovidiu. Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, December 1, 2020 8:40 PM To: Scott Little >; Qian, Bin >; MacDonald, Eric >; Bart Wensley >; Kung, John >; Waines, Greg > Cc: starlingx-discuss at lists.starlingx.io Subject: patch review for rook, project starling/utilities Hi For ceph containerization, I should build a docker image, this is patch. https://review.opendev.org/c/starlingx/utilities/+/760503 For host-based ceph cluster, service manager launch a service ceph-manager which read ceph cluster by ceph-mgr's restful module and raise or clear alarm to fault. For containerized ceph, I build a stx-ceph-manager image and plan to launch a deployment after containerized ceph cluster launched, which will also raise or clean alarm to fault. Please review my patch. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Dec 7 06:07:50 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 7 Dec 2020 06:07:50 +0000 Subject: [Starlingx-discuss] rook ceph patch review for starlingx/ha project Message-ID: Hi Please review my patch for starlingx/ha project to enable rook-ceph https://review.opendev.org/c/starlingx/ha/+/764588 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Dec 7 06:10:08 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 7 Dec 2020 06:10:08 +0000 Subject: [Starlingx-discuss] rook patch review for project rook-ceph Message-ID: Hi Please review my patch for rook-ceph project https://review.opendev.org/c/starlingx/rook-ceph/+/716792 https://review.opendev.org/c/starlingx/rook-ceph/+/765693 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Dec 7 05:59:49 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 7 Dec 2020 05:59:49 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in stx-puppet project In-Reply-To: References: Message-ID: Hi folks Please review my patch to enable rook-ceph in stx-puppet project. https://review.opendev.org/c/starlingx/stx-puppet/+/739363 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Dec 7 06:01:35 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 7 Dec 2020 06:01:35 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in config project. In-Reply-To: References: Message-ID: Hi folks Please review my patch and bob patch to enable rook-ceph in config project. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/config/+/758935 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Dec 7 06:02:29 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 7 Dec 2020 06:02:29 +0000 Subject: [Starlingx-discuss] review patch for enable rook-ceph in openstack-armada-app project In-Reply-To: References: Message-ID: + Greg Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 1:59 PM To: Angie Wang ; Church, Robert ; Chris Friesen ; Penney, Don ; Liu, ZhipengS Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: review patch for enable rook-ceph in openstack-armada-app project Hi folks Please review my patch to enable rook-ceph in openstack-armada-app project. https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Dec 7 06:02:45 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 7 Dec 2020 06:02:45 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in stx-puppet project In-Reply-To: References: Message-ID: + Greg Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 7, 2020 2:00 PM To: Bailey, Henry Albert (Al) ; Bart Wensley ; Church, Robert ; Chris Friesen ; Penney, Don ; Kung, John Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: review patch to enable rook-ceph in stx-puppet project Hi folks Please review my patch to enable rook-ceph in stx-puppet project. https://review.opendev.org/c/starlingx/stx-puppet/+/739363 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Dec 7 06:13:57 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 7 Dec 2020 06:13:57 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in metal project Message-ID: Hi folks Please review my patch to enable rook-ceph in metal project. https://review.opendev.org/c/starlingx/metal/+/737228 Ovidiu already agree fix in this patch. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Haiqing.Bai at windriver.com Mon Dec 7 08:44:36 2020 From: Haiqing.Bai at windriver.com (Bai, Haiqing) Date: Mon, 7 Dec 2020 08:44:36 +0000 Subject: [Starlingx-discuss] [CentOS8] build-pkgs/build-iso completed successfully, but installer reports dependency issues Message-ID: Hi, all: Is there anyone knows why "build-pkgs" and "build-iso" completed successfully and bootimage.iso created, but the target installer has below errors: (I have checked that "python36" and "python36-devel" are in dist/comps.xml and the type is "mandatory" of group ID "platform-controller", "platform-controller-worker", "platform-controller-worker-lowlatency", and the kickstarts cfg files include the related group in "%packages" ). Thanks. ======================================== Error The following software marked for installation has errors. This is likely caused by an error with your installation source. Problem 1: package patch-alarm-1.0-2.tis.x86_64 requires python3-devel, but none of the providers can be installed - conflicting requests - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Problem 2: package grubby-8.40-34.el8.tis.1.x86_64 requires python3-devel, but none of the providers can be installed - conflicting requests - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Problem 3: package cgcs-patch-1.0-28.tis.x86_64 requires python3-devel, but none of the providers can be installed - conflicting requests - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Problem 4: package worker-utils-1.0-5.tis.x86_64 requires /usr/bin/python3, but none of the providers can be installed - package worker-utils-1.0-5.tis.x86_64 requires python3, but none of the providers can be installed - conflicting requests - package python36-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Press ENTER to continue: -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Mon Dec 7 09:27:12 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 7 Dec 2020 09:27:12 +0000 Subject: [Starlingx-discuss] [CentOS8] build-pkgs/build-iso completed successfully, but installer reports dependency issues In-Reply-To: References: Message-ID: It sounds like this new RHEL8 feature, modularity: https://dnf.readthedocs.io/en/latest/modularity.html#hotfix-repositories It looks like it could be disabled with module_hotfixes=true in the repo config file, but I don't see any way of passing this to the kickstart repo command. I expect there will need to be some investigation of the differences in the installation of centos8 vs centos7, maybe look at the stock installation media to look at how the software repositories are setup. The introduction of modularity and "AppStream" could necessitate some changes in how we setup our ISO and software repositories. From: Bai, Haiqing Sent: Monday, December 7, 2020 3:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [CentOS8] build-pkgs/build-iso completed successfully, but installer reports dependency issues Hi, all: Is there anyone knows why "build-pkgs" and "build-iso" completed successfully and bootimage.iso created, but the target installer has below errors: (I have checked that "python36" and "python36-devel" are in dist/comps.xml and the type is "mandatory" of group ID "platform-controller", "platform-controller-worker", "platform-controller-worker-lowlatency", and the kickstarts cfg files include the related group in "%packages" ). Thanks. ======================================== Error The following software marked for installation has errors. This is likely caused by an error with your installation source. Problem 1: package patch-alarm-1.0-2.tis.x86_64 requires python3-devel, but none of the providers can be installed - conflicting requests - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Problem 2: package grubby-8.40-34.el8.tis.1.x86_64 requires python3-devel, but none of the providers can be installed - conflicting requests - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Problem 3: package cgcs-patch-1.0-28.tis.x86_64 requires python3-devel, but none of the providers can be installed - conflicting requests - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Problem 4: package worker-utils-1.0-5.tis.x86_64 requires /usr/bin/python3, but none of the providers can be installed - package worker-utils-1.0-5.tis.x86_64 requires python3, but none of the providers can be installed - conflicting requests - package python36-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Press ENTER to continue: -------------- next part -------------- An HTML attachment was scrubbed... URL: From lilong-neu at neusoft.com Mon Dec 7 10:34:17 2020 From: lilong-neu at neusoft.com (lilong-neu) Date: Mon, 7 Dec 2020 18:34:17 +0800 Subject: [Starlingx-discuss] latest image for rook deployment and test Message-ID: <0f322692-4e07-f1fa-4c9f-a3710d3b1952@neusoft.com> Hi all: Regarding Rook&Ceph deployment and test with latest image : ★Test Results: (1) Rook&Ceph deployment: Simplex: Basic environment deployment: Pass Cirros virtual machine creation: Pass Duplex (VM): Basic environment deployment: Pass Cirros virtual machine creation: Pass Host controller swact: Pass Multi 2+2 (VM): Basic environment deployment: Pass Cirros virtual machine creation: Pass Host controller swact: Pass (Refer to the rook deployment document: https://review.opendev.org/c/starlingx/docs/+/751158 ) (2) Original environment deployment (Ceph): Simplex (VM): Basic environment deployment: Pass Cirros virtual machine creation: Pass Duplex (VM): Basic environment deployment: Pass Cirros virtual machine creation: Pass Host controller swact: Pass Multi 2+2 (VM): Basic environment deployment: Pass Cirros virtual machine creation: Pass Host controller swact: Pass (Refer to the official basic deployment document: https://docs.starlingx.io/deploy_install_guides/r4_release/index.html ) ★Remarks: STX ISO Version & Path: (Build locally with the latest Rook&ceph code) https://pan.baidu.com/s/10wCGn1i3tKMVuA-HvKzWKg Password: y3zd Best Regards --------------------- Long --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From yadav.akshay58 at gmail.com Mon Dec 7 13:30:50 2020 From: yadav.akshay58 at gmail.com (Akki yadav) Date: Mon, 7 Dec 2020 19:00:50 +0530 Subject: [Starlingx-discuss] Starlingx Ironic Bare metal partitioned-disk image issue Message-ID: Hi Team, Hope you all are doing good. I have a Standard Starlingx R4.0 with ironic setup up and running. I have launched a Bare metal with whole-disk image and it came up flawlessly. But when I was trying to launch a bare metal node with partitioned-disk image, It gave me an error in the ironic-conductor stating that "sgdisk: not found". Then steps I did to resolve it are: 1. Then I installed "gdisk" on both containers of ironic-conductor . (i.e. ironic-conductor-0 and ironic-conductor-1). 2. Now, I tried agin to launch a bare metal node, this time it failed stating "parted : not found". 3. Then I installed "parted" on both containers of ironic-conductor . (i.e. ironic-conductor-0 and ironic-conductor-1). 4. Now I can flawlessly launch bare metal node with partitioned-disk image. Now, I wanted to know how may I get these packages (gdisk and parted) already installed in ironic-conductor containers when the stx-openstack application gets applied ? Regards Akshay -------------- next part -------------- An HTML attachment was scrubbed... URL: From yadav.akshay58 at gmail.com Mon Dec 7 13:41:15 2020 From: yadav.akshay58 at gmail.com (Akki yadav) Date: Mon, 7 Dec 2020 19:11:15 +0530 Subject: [Starlingx-discuss] docker-lv extension issue with RAID-5 Message-ID: Hi Team, I am trying to install Bare metal StarlingX AIO duplex setup with RAID-5 configured on my physical servers. While applying stx-openstack application, it always fails at 21% stating a timeout. In sysinv logs, I have seen some XFS currupt errors and some other errors which could be because of the extension of docker-lv from 30 GB to 60 GB. I was trying to install the setup from scratch again so that I could deploy the setup with docker-lv set to 60 GB only so that I need not to extend the LV. Can anyone please tell me how may set it to 60 so no need to extend it? Regards Akshay -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Dec 7 15:16:30 2020 From: scott.little at windriver.com (Scott Little) Date: Mon, 7 Dec 2020 10:16:30 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 333 - Failure! In-Reply-To: <5a1d0b77-fad5-4067-bcf4-3b4541a01b5c@windriver.com> References: <1864792267.432.1606880588117.JavaMail.javamailuser@localhost> <49e530d5-c550-45ed-0ced-7de11358d207@windriver.com> <80e07848-490c-2d38-2def-dbb3b3d3e4f1@windriver.com> <0f4ce118-ed84-d928-e5e0-f46d1441c3d5@windriver.com> <5a1d0b77-fad5-4067-bcf4-3b4541a01b5c@windriver.com> Message-ID: <1c4d02fc-f1ae-7049-947d-98c642f3110f@windriver.com> mirrorlist.centos.org was down.  I'll restart the build Time to start looking into a caching web proxy. Scott On 2020-12-03 9:38 a.m., Scott Little wrote: > We are now able to build packages and iso's again. > > Docker image builds are still having issues.  I continue to > investigate ... > > Scott > > On 2020-12-02 3:23 p.m., Scott Little wrote: >> Add https://review.opendev.org/c/starlingx/tools/+/765091 (merged) to >> revert 765179 which breaks in the absence to 762701 >> >> Starting the build again... >> >> Sorry for the mess folks. >> >> Scott >> >> >> On 2020-12-02 2:46 p.m., Scott Little wrote: >>> Fixes have merged. >>> >>> A fresh CENGN build is underfway. >>> >>> Scott >>> >>> >>> On 2020-12-02 1:45 p.m., Scott Little wrote: >>>> Fixes posted for review. >>>> >>>> # Fix for 762700 >>>> https://review.opendev.org/c/starlingx/tools/+/765179 >>>> >>>> # Reversion of 762701 >>>> https://review.opendev.org/c/starlingx/root/+/765191 >>>> >>>> >>>> Scott >>>> >>>> >>>> On 2020-12-02 12:05 p.m., Scott Little wrote: >>>>> The build failure was cause by the merge of code intended to add >>>>> support for building in a centos 8 environment.  The update was >>>>> intended to retain support for centos 7. >>>>> >>>>> The build failed because it tried to use a centos 8 mock >>>>> configuration within a centos 7 build container. >>>>> >>>>> Two bugs have been identified that when combined produced the failure. >>>>> >>>>> Commits that introduced the error: >>>>> https://review.opendev.org/c/starlingx/tools/+/762700 >>>>> https://review.opendev.org/c/starlingx/root/+/762701 >>>>> >>>>> I'll be posting a fix shortly >>>>> >>>>> Scott Little >>>>> >>>>> >>>>> On 2020-12-01 10:43 p.m., build.starlingx at gmail.com wrote: >>>>>> [Please note this e-mail is from an EXTERNAL e-mail address] >>>>>> >>>>>> Project: STX_build_layer_flock_master_master >>>>>> Build #: 333 >>>>>> Status: Failure >>>>>> Timestamp: 20201202T023718Z >>>>>> Branch: master >>>>>> >>>>>> Check logs at: >>>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201202T023718Z/logs >>>>>> -------------------------------------------------------------------------------- >>>>>> Parameters >>>>>> >>>>>> FULL_BUILD: false >>>>>> FORCE_BUILD: false >>>>>> >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Dec 7 16:05:12 2020 From: scott.little at windriver.com (Scott Little) Date: Mon, 7 Dec 2020 11:05:12 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 86 - Still Failing! In-Reply-To: <1159594695.420.1606839631331.JavaMail.javamailuser@localhost> References: <1159594695.420.1606839631331.JavaMail.javamailuser@localhost> Message-ID: <68acf7a4-e4d8-f3e1-ae75-b75d471b6cab@windriver.com> mirrorlist.centos.org was down.  I'll restart the build Time to start looking into a caching web proxy. Scott On 2020-12-01 11:20 a.m., build.starlingx at gmail.com wrote: > [Please note this e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_containers_master_master > Build #: 86 > Status: Still Failing > Timestamp: 20201201T151602Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201201T151602Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Mon Dec 7 18:04:53 2020 From: amy at demarco.com (Amy Marrich) Date: Mon, 7 Dec 2020 12:04:53 -0600 Subject: [Starlingx-discuss] [Diversity] Diversity and Inclusion WG Meeting Change for January Message-ID: Due to the end of year holidays and the fact some people may still be out we will be moving our January meeting. As our backup meeting date is on Martin Luther King Day, the WG has selected January 11 to meet in IRC. As always I'll send out a reminder in the days leading up to the meeting. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Dec 7 18:34:26 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 7 Dec 2020 13:34:26 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_download_mirror - Build # 1084 - Failure! Message-ID: <1707749142.519.1607366067416.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1084 Status: Failure Timestamp: 20201207T100158Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201207T100001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/centos8 DOCKER_BUILD_ID: jenkins-f-centos8-20201207T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201207T100001Z/logs MY_REPO: /localdisk/designer/jenkins/f-centos8/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201207T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Mon Dec 7 18:34:29 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 7 Dec 2020 13:34:29 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 50 - Still Failing! In-Reply-To: null References: null Message-ID: <1660593208.522.1607366069955.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 50 Status: Still Failing Timestamp: 20201207T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201207T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Mon Dec 7 19:30:56 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 7 Dec 2020 14:30:56 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 302 - Failure! Message-ID: <826728470.525.1607369457283.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 302 Status: Failure Timestamp: 20201207T155153Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201207T151349Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201207T151349Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20201207T151349Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201207T151349Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201207T151349Z/logs PUBLISH_TIMESTAMP: 20201207T151349Z FLOCK_VERSION: master-centos-stable-20201207T151349Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20201207T151349Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201207T151349Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Mon Dec 7 19:30:59 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 7 Dec 2020 14:30:59 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 66 - Still Failing! In-Reply-To: <478698257.483.1607030366127.JavaMail.javamailuser@localhost> References: <478698257.483.1607030366127.JavaMail.javamailuser@localhost> Message-ID: <1176167117.528.1607369459742.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 66 Status: Still Failing Timestamp: 20201207T153332Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201207T151349Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201207T151349Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201207T151349Z/logs MASTER_BUILD_NUMBER: 89 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201207T151349Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20201207T151349Z DOCKER_BUILD_ID: jenkins-master-containers-20201207T151349Z-builder TIMESTAMP: 20201207T151349Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201207T151349Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201207T151349Z/outputs From build.starlingx at gmail.com Mon Dec 7 19:31:01 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 7 Dec 2020 14:31:01 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 89 - Still Failing! In-Reply-To: <1346792315.486.1607030368613.JavaMail.javamailuser@localhost> References: <1346792315.486.1607030368613.JavaMail.javamailuser@localhost> Message-ID: <1680525543.531.1607369462170.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 89 Status: Still Failing Timestamp: 20201207T151349Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201207T151349Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From austin.sun at intel.com Tue Dec 8 00:47:15 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 8 Dec 2020 00:47:15 +0000 Subject: [Starlingx-discuss] docker-lv extension issue with RAID-5 In-Reply-To: References: Message-ID: Hi Akshay: I think you want to extend the docker-lv w/o reinstall and provision . In you setup , you can run command like ‘system host-fs-modify controller-0 docker=60” to enlarge docker lv. system host-fs-modify controller-1 docker=60 Thanks. BR Austin Sun. From: Akki yadav Sent: Monday, December 7, 2020 9:41 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] docker-lv extension issue with RAID-5 Hi Team, I am trying to install Bare metal StarlingX AIO duplex setup with RAID-5 configured on my physical servers. While applying stx-openstack application, it always fails at 21% stating a timeout. In sysinv logs, I have seen some XFS currupt errors and some other errors which could be because of the extension of docker-lv from 30 GB to 60 GB. I was trying to install the setup from scratch again so that I could deploy the setup with docker-lv set to 60 GB only so that I need not to extend the LV. Can anyone please tell me how may set it to 60 so no need to extend it? Regards Akshay -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Tue Dec 8 01:36:50 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 8 Dec 2020 01:36:50 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Dec 2/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Dec 2 2020 stx.5.0 - Status for Milestone-2 - Dec 18 - Specs - One spec pending approval: https://review.opendev.org/c/starlingx/specs/+/750636 - Action: Greg to review - Bill pointed out that there are some new specs expected shortly. He'll provide info shortly. - Feature Content - Feature List: https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=1107209846 - Need follow-up on CentOS8 status if there is a change in the plan for inclusion in stx.5.0 - Other features have code merge dates and appear to fit within the release with some minor exceptions - Feature Testing: https://docs.google.com/spreadsheets/d/1jro4ItdSobB0-fseK_4cOZJHhUyuh_eCBBsDOp_A5Pc/edit#gid=968103774 - Action: Nick/Yang to update the Feature Test End Dates. Target by the next meeting stx.3.0.1 - Regarding https://bugs.launchpad.net/starlingx/+bug/1897896 , nothing new. No further responses from Ovidiu. Still unclear why the standard config provisioning fails - Agreed to abandon this stx.3.0.1 maintenance release given stx.3.0 is end of life by year-end - Action: Mary to update the release notes and mark stx.2.0.1 & stx.3.0 as EOL From yadav.akshay58 at gmail.com Tue Dec 8 04:41:56 2020 From: yadav.akshay58 at gmail.com (Akki yadav) Date: Tue, 8 Dec 2020 10:11:56 +0530 Subject: [Starlingx-discuss] docker-lv extension issue with RAID-5 In-Reply-To: References: Message-ID: Hi Austin, Thanks for the reply. We don't want to extend XFS, we want to reserve 60 GB for the docker filesystem from the beginning. We want that the setup should come up with docker-lv size of 60 GB by default. Can you please suggest the way? Regards Akshay On Tue, Dec 8, 2020 at 6:17 AM Sun, Austin wrote: > Hi Akshay: > > I think you want to extend the docker-lv w/o reinstall and provision . > > > > In you setup , you can run command like > > > > ‘system host-fs-modify controller-0 docker=60” to enlarge docker lv. > > system host-fs-modify controller-1 docker=60 > > Thanks. > > BR > Austin Sun. > > *From:* Akki yadav > *Sent:* Monday, December 7, 2020 9:41 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] docker-lv extension issue with RAID-5 > > > > Hi Team, > > I am trying to install Bare metal StarlingX AIO duplex setup with RAID-5 > configured on my physical servers. > While applying stx-openstack application, it always fails at 21% stating a > timeout. > In sysinv logs, I have seen some XFS currupt errors and some other errors > which could be because of the extension of docker-lv from 30 GB to 60 GB. > I was trying to install the setup from scratch again so that I could > deploy the setup with docker-lv set to 60 GB only so that I need not to > extend the LV. > > Can anyone please tell me how may set it to 60 so no need to extend it? > > Regards > Akshay > -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Dec 8 06:08:49 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 8 Dec 2020 01:08:49 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 303 - Still Failing! In-Reply-To: <1682628245.523.1607369454600.JavaMail.javamailuser@localhost> References: <1682628245.523.1607369454600.JavaMail.javamailuser@localhost> Message-ID: <1112093441.536.1607407730312.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 303 Status: Still Failing Timestamp: 20201208T022320Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201208T014249Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20201208T014249Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201208T014249Z/logs PUBLISH_TIMESTAMP: 20201208T014249Z FLOCK_VERSION: master-centos-stable-20201208T014249Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20201208T014249Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201208T014249Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Tue Dec 8 06:08:52 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 8 Dec 2020 01:08:52 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 67 - Still Failing! In-Reply-To: <1721323425.526.1607369457950.JavaMail.javamailuser@localhost> References: <1721323425.526.1607369457950.JavaMail.javamailuser@localhost> Message-ID: <55528054.539.1607407732786.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 67 Status: Still Failing Timestamp: 20201208T020352Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201208T014249Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs MASTER_BUILD_NUMBER: 90 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201208T014249Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20201208T014249Z DOCKER_BUILD_ID: jenkins-master-containers-20201208T014249Z-builder TIMESTAMP: 20201208T014249Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201208T014249Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201208T014249Z/outputs From build.starlingx at gmail.com Tue Dec 8 06:08:54 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 8 Dec 2020 01:08:54 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! In-Reply-To: <1766225256.529.1607369460415.JavaMail.javamailuser@localhost> References: <1766225256.529.1607369460415.JavaMail.javamailuser@localhost> Message-ID: <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 90 Status: Still Failing Timestamp: 20201208T014249Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From build.starlingx at gmail.com Tue Dec 8 10:01:16 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 8 Dec 2020 05:01:16 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 51 - Still Failing! In-Reply-To: <1915857984.520.1607366068110.JavaMail.javamailuser@localhost> References: <1915857984.520.1607366068110.JavaMail.javamailuser@localhost> Message-ID: <1822589676.547.1607421677139.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 51 Status: Still Failing Timestamp: 20201208T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201208T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From austin.sun at intel.com Tue Dec 8 12:25:04 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 8 Dec 2020 12:25:04 +0000 Subject: [Starlingx-discuss] Agenda StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 12/08 Message-ID: Hi All: 12/08/2020 Meeting: - Bugs review https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack https://bugs.launchpad.net/starlingx/+bug/1879018 https://bugs.launchpad.net/starlingx/+bug/1887677 https://bugs.launchpad.net/starlingx/+bug/1887755 Fix released https://bugs.launchpad.net/starlingx/+bug/1904635 https://bugs.launchpad.net/starlingx/+bug/1904729 - Open Topic If any more topic : Adding to https://etherpad.opendev.org/p/stx-distro-openstack-meetings Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Dec 8 13:26:47 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 8 Dec 2020 13:26:47 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph Message-ID: Hi Please review patch for rook-ceph. We already confirm it is function ready and pass function test. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/716792 https://review.opendev.org/c/starlingx/rook-ceph/+/765693 https://review.opendev.org/c/starlingx/utilities/+/760503 https://review.opendev.org/c/starlingx/ha/+/764588 https://review.opendev.org/c/starlingx/stx-puppet/+/739363 https://review.opendev.org/c/starlingx/config/+/758935 https://review.opendev.org/c/starlingx/metal/+/737228 https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Dec 8 13:32:19 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 8 Dec 2020 13:32:19 +0000 Subject: [Starlingx-discuss] proposal for lifecycle operator Message-ID: Hi Bob I study patch for lifecycle operator. Something to check with you https://review.opendev.org/q/topic:%22story_2007960%22+(status:open%20OR%20status:merged) 1, lifecycle operator will merge in r5 release or not? 2, propose to add a hook for APP_LIFECYCLE_TIMMING_POST. Now there is only hook for constants.APP_LIFECYCLE_TIMING_PRE, which is called before application apply. Propose to add a hook to be called, after application apply, APP_LIFECYCLE_TIMMING_POST. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Dec 8 13:52:12 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 8 Dec 2020 13:52:12 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Today is the scheduled day for the biweekly containerization meeting. We'll meet today as per schedule. The agenda is open so if anyone has a topic please add to the etherpad agenda. Etherpad: https://etherpad.openstack.org/p/stx-containerization Zoom: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 ------ Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2180 bytes Desc: not available URL: From sharath.kumar at intel.com Tue Dec 8 14:46:14 2020 From: sharath.kumar at intel.com (Kumar, Sharath) Date: Tue, 8 Dec 2020 14:46:14 +0000 Subject: [Starlingx-discuss] Help required on the code commit for the horizon repo In-Reply-To: References: Message-ID: Adding starlingx-discussion. From: Kumar, Sharath Sent: Tuesday, December 8, 2020 7:54 PM To: 'angie.wang at windriver.com' ; Wensley, Barton ; 'Kristine.Bujold at windriver.com' ; Smith, Tyler Subject: Help required on the code commit for the horizon repo Hi All, I am working on Fault management front end coding for openstack dashboard, and to push my changes for the review, I have some questions on branch and commits. My code is currently part of horizon repo which comes under distro layer. In the build layer, code will be present under below path: /stx/distro/cgcs-root/stx/git/horizon/openstack_dashboard/dashboards. Under horizon repo, only openstack community branches are present : remotes/m/master -> openstack/stable/train remotes/openstack/master remotes/openstack/stable/ocata remotes/openstack/stable/pike remotes/openstack/stable/queens remotes/openstack/stable/rocky remotes/openstack/stable/stein remotes/openstack/stable/train remotes/openstack/stable/ussuri remotes/openstack/stable/Victoria I can see starlingx branches under below path in distro layer: /stx/distro/cgcs-root/stx/git Branches: remotes/m/master -> starlingx/master remotes/starlingx/centos75 remotes/starlingx/f/centos75 remotes/starlingx/f/centos76 remotes/starlingx/f/centos8 remotes/starlingx/f/keystone-db remotes/starlingx/m/2018.07 remotes/starlingx/m/2018.08 remotes/starlingx/master remotes/starlingx/r/2018.10 remotes/starlingx/r/stx.2.0 remotes/starlingx/r/stx.3.0 remotes/starlingx/r/stx.4.0 Now challenge is, to push my code under horizon repo only openstack branches are listing , not starlingx. My questions: 1. With the present repo path and branches, I cannot push code because it will go to the openstack community. Could you please suggest how can I push my changes to the starlingx community for review? 2. Whom should I add from WindRiver team to review my code which are part of horizon repo? Thank you for helping me here. Regards, Sharath -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Dec 8 14:53:01 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 8 Dec 2020 14:53:01 +0000 Subject: [Starlingx-discuss] MoM StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 12/08 Message-ID: Hi All: Please check MoM: 12/08/2020 Meeting: - Bugs review https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack https://bugs.launchpad.net/starlingx/+bug/1879018 https://review.opendev.org/c/starlingx/openstack-armada-app/+/751358/, no update for 2 weeks , and feedback for review comments. https://bugs.launchpad.net/starlingx/+bug/1888178 still not find solution yet. https://bugs.launchpad.net/starlingx/+bug/1887677 https://bugs.launchpad.net/starlingx/+bug/1887755 Fix released https://bugs.launchpad.net/starlingx/+bug/1904635 https://bugs.launchpad.net/starlingx/+bug/1904729 Zhipeng will take these two bugs. - Open Topic --- measure performance , check the offset between controller and compute (> 60 secs) NTP. Nic will raise bug first. and then we will find developer for this . --- Cancel next meeting ( 12/22th) , Next meeting will be on Jan 5th 2021 Thanks. BR Austin Sun. From: Sun, Austin Sent: Tuesday, December 8, 2020 8:25 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Agenda StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 12/08 Hi All: 12/08/2020 Meeting: - Bugs review https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack https://bugs.launchpad.net/starlingx/+bug/1879018 https://bugs.launchpad.net/starlingx/+bug/1887677 https://bugs.launchpad.net/starlingx/+bug/1887755 Fix released https://bugs.launchpad.net/starlingx/+bug/1904635 https://bugs.launchpad.net/starlingx/+bug/1904729 - Open Topic If any more topic : Adding to https://etherpad.opendev.org/p/stx-distro-openstack-meetings Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Dec 8 14:53:50 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 8 Dec 2020 14:53:50 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Distro-OpenStack: Bi-weekly Project Meeting Message-ID: Hi folks, This is a new series of bi-weekly project meeting on StarlingX Distro-OpenStack. Your participation to this meeting and/or other offline contribution by all means are highly appreciated! Project Team Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings The Winter Time Slot for this meeting : CST: 10:00 PM(China, Shanghai ) PST: 7:00 AM (US West , US, Oregon) EST: 9:00 AM (East Canada , Canada Ottawa) Thanks BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3067 bytes Desc: not available URL: From tyler.smith at windriver.com Tue Dec 8 15:39:02 2020 From: tyler.smith at windriver.com (Smith, Tyler) Date: Tue, 8 Dec 2020 15:39:02 +0000 Subject: [Starlingx-discuss] Help required on the code commit for the horizon repo In-Reply-To: References: Message-ID: Hi Sharath, The code will have to live in the stx-gui repo at /stx/gui/ as this isn't a change we would want to push to upstream horizon. Bart, Kristine, Angie, and myself will be able to review your code. Thanks, Tyler From: Kumar, Sharath Sent: December 8, 2020 9:46 AM To: Wang, Jing (Angie) ; Wensley, Barton ; Bujold, Kristine ; Smith, Tyler ; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K ; Kalvala, Haridhar ; Bhat, Gopalkrishna Subject: RE: Help required on the code commit for the horizon repo [Please note this e-mail is from an EXTERNAL e-mail address] Adding starlingx-discussion. From: Kumar, Sharath Sent: Tuesday, December 8, 2020 7:54 PM To: 'angie.wang at windriver.com' >; Wensley, Barton >; 'Kristine.Bujold at windriver.com' >; Smith, Tyler > Subject: Help required on the code commit for the horizon repo Hi All, I am working on Fault management front end coding for openstack dashboard, and to push my changes for the review, I have some questions on branch and commits. My code is currently part of horizon repo which comes under distro layer. In the build layer, code will be present under below path: /stx/distro/cgcs-root/stx/git/horizon/openstack_dashboard/dashboards. Under horizon repo, only openstack community branches are present : remotes/m/master -> openstack/stable/train remotes/openstack/master remotes/openstack/stable/ocata remotes/openstack/stable/pike remotes/openstack/stable/queens remotes/openstack/stable/rocky remotes/openstack/stable/stein remotes/openstack/stable/train remotes/openstack/stable/ussuri remotes/openstack/stable/Victoria I can see starlingx branches under below path in distro layer: /stx/distro/cgcs-root/stx/git Branches: remotes/m/master -> starlingx/master remotes/starlingx/centos75 remotes/starlingx/f/centos75 remotes/starlingx/f/centos76 remotes/starlingx/f/centos8 remotes/starlingx/f/keystone-db remotes/starlingx/m/2018.07 remotes/starlingx/m/2018.08 remotes/starlingx/master remotes/starlingx/r/2018.10 remotes/starlingx/r/stx.2.0 remotes/starlingx/r/stx.3.0 remotes/starlingx/r/stx.4.0 Now challenge is, to push my code under horizon repo only openstack branches are listing , not starlingx. My questions: 1. With the present repo path and branches, I cannot push code because it will go to the openstack community. Could you please suggest how can I push my changes to the starlingx community for review? 2. Whom should I add from WindRiver team to review my code which are part of horizon repo? Thank you for helping me here. Regards, Sharath -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Dec 8 16:23:12 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 8 Dec 2020 11:23:12 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! In-Reply-To: <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> References: <1766225256.529.1607369460415.JavaMail.javamailuser@localhost> <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> Message-ID: <214690a5-aaaa-3e47-a5b9-00adb77cac09@windriver.com> Centos 8.3 was released yesterday. One of the changes is to repo names, and that broke at least one container build. e.g. stx-fm-trap-subagent's Dockerfile was referencing 'PowerTools' which is now 'powertools' I've posted a fix for this one: https://review.opendev.org/c/starlingx/snmp-armada-app/+/766035 To all container owners:  Please verify your containers still build! Scott On 2020-12-08 1:08 a.m., build.starlingx at gmail.com wrote: > [Please note this e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_containers_master_master > Build #: 90 > Status: Still Failing > Timestamp: 20201208T014249Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Dec 8 17:45:36 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 8 Dec 2020 12:45:36 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! In-Reply-To: <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> References: <1766225256.529.1607369460415.JavaMail.javamailuser@localhost> <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> Message-ID: <07701fc7-b77f-be54-4796-3165a8764a7d@windriver.com> There is second container build failure in the logs. The stx-horizon docker image can't find a version of Django that it can use. https://bugs.launchpad.net/starlingx/+bug/1907290 Can someone volunteer to investigate this one? Scott On 2020-12-08 1:08 a.m., build.starlingx at gmail.com wrote: > [Please note this e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_containers_master_master > Build #: 90 > Status: Still Failing > Timestamp: 20201208T014249Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From sharath.kumar at intel.com Tue Dec 8 17:46:20 2020 From: sharath.kumar at intel.com (Kumar, Sharath) Date: Tue, 8 Dec 2020 17:46:20 +0000 Subject: [Starlingx-discuss] Help required on the code commit for the horizon repo In-Reply-To: References: Message-ID: Hi Tyler, Thank you for the response. I believe, once code is push to stx/gui repo it will be part of starlingx dashboard, then how openstack horizon docker image(stx-horizon) will be built using custom code which will be present in stx/gui instead of upstream horizon repo? As per my understanding, drawing below diagram of horizon docker image build process. Please let me know your views. [cid:image002.png at 01D6CDB8.216D8330] Regards, Sharath From: Smith, Tyler Sent: Tuesday, December 8, 2020 9:09 PM To: Kumar, Sharath ; Wang, Jing (Angie) ; Wensley, Barton ; Bujold, Kristine ; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K ; Kalvala, Haridhar ; Bhat, Gopalkrishna Subject: RE: Help required on the code commit for the horizon repo Hi Sharath, The code will have to live in the stx-gui repo at /stx/gui/ as this isn't a change we would want to push to upstream horizon. Bart, Kristine, Angie, and myself will be able to review your code. Thanks, Tyler From: Kumar, Sharath > Sent: December 8, 2020 9:46 AM To: Wang, Jing (Angie) >; Wensley, Barton >; Bujold, Kristine >; Smith, Tyler >; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K >; Kalvala, Haridhar >; Bhat, Gopalkrishna > Subject: RE: Help required on the code commit for the horizon repo [Please note this e-mail is from an EXTERNAL e-mail address] Adding starlingx-discussion. From: Kumar, Sharath Sent: Tuesday, December 8, 2020 7:54 PM To: 'angie.wang at windriver.com' >; Wensley, Barton >; 'Kristine.Bujold at windriver.com' >; Smith, Tyler > Subject: Help required on the code commit for the horizon repo Hi All, I am working on Fault management front end coding for openstack dashboard, and to push my changes for the review, I have some questions on branch and commits. My code is currently part of horizon repo which comes under distro layer. In the build layer, code will be present under below path: /stx/distro/cgcs-root/stx/git/horizon/openstack_dashboard/dashboards. Under horizon repo, only openstack community branches are present : remotes/m/master -> openstack/stable/train remotes/openstack/master remotes/openstack/stable/ocata remotes/openstack/stable/pike remotes/openstack/stable/queens remotes/openstack/stable/rocky remotes/openstack/stable/stein remotes/openstack/stable/train remotes/openstack/stable/ussuri remotes/openstack/stable/Victoria I can see starlingx branches under below path in distro layer: /stx/distro/cgcs-root/stx/git Branches: remotes/m/master -> starlingx/master remotes/starlingx/centos75 remotes/starlingx/f/centos75 remotes/starlingx/f/centos76 remotes/starlingx/f/centos8 remotes/starlingx/f/keystone-db remotes/starlingx/m/2018.07 remotes/starlingx/m/2018.08 remotes/starlingx/master remotes/starlingx/r/2018.10 remotes/starlingx/r/stx.2.0 remotes/starlingx/r/stx.3.0 remotes/starlingx/r/stx.4.0 Now challenge is, to push my code under horizon repo only openstack branches are listing , not starlingx. My questions: 1. With the present repo path and branches, I cannot push code because it will go to the openstack community. Could you please suggest how can I push my changes to the starlingx community for review? 2. Whom should I add from WindRiver team to review my code which are part of horizon repo? Thank you for helping me here. Regards, Sharath -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 22306 bytes Desc: image002.png URL: From Don.Penney at windriver.com Tue Dec 8 17:54:44 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 8 Dec 2020 17:54:44 +0000 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! In-Reply-To: <07701fc7-b77f-be54-4796-3165a8764a7d@windriver.com> References: <1766225256.529.1607369460415.JavaMail.javamailuser@localhost> <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> <07701fc7-b77f-be54-4796-3165a8764a7d@windriver.com> Message-ID: That seems odd. It certainly looks like pypi.org has a wheel that should satisfy the requirement Django<3.0,>=2.2: https://pypi.org/project/Django/2.2.17/#files Django-2.2.17-py3-none-any.whl This is a py3 wheel, and stx-horizon has been updated to python3: https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-horizon/centos/stx-horizon.stable_docker_image#L16 From: Scott Little Sent: Tuesday, December 8, 2020 12:46 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! There is second container build failure in the logs. The stx-horizon docker image can't find a version of Django that it can use. https://bugs.launchpad.net/starlingx/+bug/1907290 Can someone volunteer to investigate this one? Scott On 2020-12-08 1:08 a.m., build.starlingx at gmail.com wrote: [Please note this e-mail is from an EXTERNAL e-mail address] Project: STX_build_layer_containers_master_master Build #: 90 Status: Still Failing Timestamp: 20201208T014249Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Tue Dec 8 18:46:22 2020 From: Saul.Wold at windriver.com (Saul Wold) Date: Tue, 8 Dec 2020 10:46:22 -0800 Subject: [Starlingx-discuss] Distro (non-openstack) Meeting Reminder - Wednesday Message-ID: <57ba188f-308c-8abe-165d-ed8d8192f870@windriver.com> Zoom Link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 EtherPad: https://etherpad.opendev.org/p/stx-distro-other Ceph/Rook Status CentOS-8 - Current status - f/centos8 repo updates - CentOS-8.2 package update Python3 -- Sau! From tyler.smith at windriver.com Tue Dec 8 18:55:57 2020 From: tyler.smith at windriver.com (Smith, Tyler) Date: Tue, 8 Dec 2020 18:55:57 +0000 Subject: [Starlingx-discuss] Help required on the code commit for the horizon repo In-Reply-To: References: Message-ID: I think the best way to go about it would be to leave horizon/openstack_dashboard packages untouched, but as part of the image build bring in the fault_management plugin as its own package and copy the enabled files from it into the openstack_dashboard enabled directory inside of the image. The discussion from a while ago was whether starlingx_dashboard plugin could contain everything and have only the relevant dashboards enabled where needed in containerized and platform horizon. It looks like that ran into some issues, so the other approach would be to separate the fault_management components into its own plugin/package, which is what would be imported into the docker image. Tyler From: Kumar, Sharath Sent: December 8, 2020 12:46 PM To: Smith, Tyler ; Wang, Jing (Angie) ; Wensley, Barton ; Bujold, Kristine ; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K ; Kalvala, Haridhar ; Bhat, Gopalkrishna Subject: RE: Help required on the code commit for the horizon repo [Please note this e-mail is from an EXTERNAL e-mail address] Hi Tyler, Thank you for the response. I believe, once code is push to stx/gui repo it will be part of starlingx dashboard, then how openstack horizon docker image(stx-horizon) will be built using custom code which will be present in stx/gui instead of upstream horizon repo? As per my understanding, drawing below diagram of horizon docker image build process. Please let me know your views. [cid:image001.png at 01D6CD65.C3084B60] Regards, Sharath From: Smith, Tyler > Sent: Tuesday, December 8, 2020 9:09 PM To: Kumar, Sharath >; Wang, Jing (Angie) >; Wensley, Barton >; Bujold, Kristine >; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K >; Kalvala, Haridhar >; Bhat, Gopalkrishna > Subject: RE: Help required on the code commit for the horizon repo Hi Sharath, The code will have to live in the stx-gui repo at /stx/gui/ as this isn't a change we would want to push to upstream horizon. Bart, Kristine, Angie, and myself will be able to review your code. Thanks, Tyler From: Kumar, Sharath > Sent: December 8, 2020 9:46 AM To: Wang, Jing (Angie) >; Wensley, Barton >; Bujold, Kristine >; Smith, Tyler >; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K >; Kalvala, Haridhar >; Bhat, Gopalkrishna > Subject: RE: Help required on the code commit for the horizon repo [Please note this e-mail is from an EXTERNAL e-mail address] Adding starlingx-discussion. From: Kumar, Sharath Sent: Tuesday, December 8, 2020 7:54 PM To: 'angie.wang at windriver.com' >; Wensley, Barton >; 'Kristine.Bujold at windriver.com' >; Smith, Tyler > Subject: Help required on the code commit for the horizon repo Hi All, I am working on Fault management front end coding for openstack dashboard, and to push my changes for the review, I have some questions on branch and commits. My code is currently part of horizon repo which comes under distro layer. In the build layer, code will be present under below path: /stx/distro/cgcs-root/stx/git/horizon/openstack_dashboard/dashboards. Under horizon repo, only openstack community branches are present : remotes/m/master -> openstack/stable/train remotes/openstack/master remotes/openstack/stable/ocata remotes/openstack/stable/pike remotes/openstack/stable/queens remotes/openstack/stable/rocky remotes/openstack/stable/stein remotes/openstack/stable/train remotes/openstack/stable/ussuri remotes/openstack/stable/Victoria I can see starlingx branches under below path in distro layer: /stx/distro/cgcs-root/stx/git Branches: remotes/m/master -> starlingx/master remotes/starlingx/centos75 remotes/starlingx/f/centos75 remotes/starlingx/f/centos76 remotes/starlingx/f/centos8 remotes/starlingx/f/keystone-db remotes/starlingx/m/2018.07 remotes/starlingx/m/2018.08 remotes/starlingx/master remotes/starlingx/r/2018.10 remotes/starlingx/r/stx.2.0 remotes/starlingx/r/stx.3.0 remotes/starlingx/r/stx.4.0 Now challenge is, to push my code under horizon repo only openstack branches are listing , not starlingx. My questions: 1. With the present repo path and branches, I cannot push code because it will go to the openstack community. Could you please suggest how can I push my changes to the starlingx community for review? 2. Whom should I add from WindRiver team to review my code which are part of horizon repo? Thank you for helping me here. Regards, Sharath -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 22306 bytes Desc: image001.png URL: From Al.Bailey at windriver.com Tue Dec 8 20:32:23 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 8 Dec 2020 20:32:23 +0000 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! In-Reply-To: References: <1766225256.529.1607369460415.JavaMail.javamailuser@localhost> <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> <07701fc7-b77f-be54-4796-3165a8764a7d@windriver.com>, Message-ID: This is because of the new pip https://discuss.python.org/t/announcement-pip-20-3-release/5948 In python3 it uses a diff resolver. Which seems to fail for any component ending in a number (Django2, iso8601, etc..) virtualenv on Dec7 was also updated to use that version of pip by default, which is what is affecting some tox jobs. there is supposed to be a way to add --use-deprecated=legacy-resolver to the pip command, which is what I am trying to do to get sysinv zuul to pass, I havent had much luck yet. Al ________________________________ From: Penney, Don Sent: Tuesday, December 8, 2020 12:54 PM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! That seems odd. It certainly looks like pypi.org has a wheel that should satisfy the requirement Django<3.0,>=2.2: https://pypi.org/project/Django/2.2.17/#files Django-2.2.17-py3-none-any.whl This is a py3 wheel, and stx-horizon has been updated to python3: https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-horizon/centos/stx-horizon.stable_docker_image#L16 From: Scott Little Sent: Tuesday, December 8, 2020 12:46 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! There is second container build failure in the logs. The stx-horizon docker image can't find a version of Django that it can use. https://bugs.launchpad.net/starlingx/+bug/1907290 Can someone volunteer to investigate this one? Scott On 2020-12-08 1:08 a.m., build.starlingx at gmail.com wrote: [Please note this e-mail is from an EXTERNAL e-mail address] Project: STX_build_layer_containers_master_master Build #: 90 Status: Still Failing Timestamp: 20201208T014249Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Tue Dec 8 21:12:34 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 8 Dec 2020 21:12:34 +0000 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! In-Reply-To: References: <1766225256.529.1607369460415.JavaMail.javamailuser@localhost> <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> <07701fc7-b77f-be54-4796-3165a8764a7d@windriver.com> Message-ID: <20201208211234.chw5p5heqsmcznsc@yuggoth.org> On 2020-12-08 20:32:23 +0000 (+0000), Bailey, Henry Albert (Al) wrote: [...] > In python3 it uses a diff resolver. Which seems to fail for any > component ending in a number (Django2, iso8601, etc..) [...] Interesting. I've helped a lot of folks fix latent dependency version conflicts exposed by the new solver, but this is the first I've heard that it cares whether package names end in digits. Can you point to where you saw that asserted? -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From alexandru.dimofte at intel.com Tue Dec 8 21:13:38 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 8 Dec 2020 21:13:38 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201208T003512Z Message-ID: Sanity Test from 2020-December-8 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201208T003512Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201208T003512Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From Bill.Zvonar at windriver.com Tue Dec 8 22:08:53 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 8 Dec 2020 22:08:53 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 9, 2020) Message-ID: Hi all, reminder of tomorrow's TSC/Community call. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201209T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From Al.Bailey at windriver.com Tue Dec 8 23:16:20 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 8 Dec 2020 23:16:20 +0000 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! In-Reply-To: <20201208211234.chw5p5heqsmcznsc@yuggoth.org> References: <1766225256.529.1607369460415.JavaMail.javamailuser@localhost> <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> <07701fc7-b77f-be54-4796-3165a8764a7d@windriver.com> , <20201208211234.chw5p5heqsmcznsc@yuggoth.org> Message-ID: I think the trailing number was just a wild goose chase. The resolver will complain if a min version and a max version don't line up. I was able to successfully use some of the entities in a minimal setup (boto3, iso8601) that had been failing when hitting conflicts in the larger env. Al ________________________________ From: Jeremy Stanley Sent: Tuesday, December 8, 2020 4:12 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! [Please note this e-mail is from an EXTERNAL e-mail address] On 2020-12-08 20:32:23 +0000 (+0000), Bailey, Henry Albert (Al) wrote: [...] > In python3 it uses a diff resolver. Which seems to fail for any > component ending in a number (Django2, iso8601, etc..) [...] Interesting. I've helped a lot of folks fix latent dependency version conflicts exposed by the new solver, but this is the first I've heard that it cares whether package names end in digits. Can you point to where you saw that asserted? -- Jeremy Stanley -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Dec 9 02:30:06 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 8 Dec 2020 21:30:06 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 380 - Failure! Message-ID: <1700757258.560.1607481007059.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 380 Status: Failure Timestamp: 20201209T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201209T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From Haiqing.Bai at windriver.com Wed Dec 9 02:32:54 2020 From: Haiqing.Bai at windriver.com (Bai, Haiqing) Date: Wed, 9 Dec 2020 02:32:54 +0000 Subject: [Starlingx-discuss] [CentOS8] build-pkgs/build-iso completed successfully, but installer reports dependency issues In-Reply-To: References: Message-ID: You are right, this is caused by the dnf modularity. For just test purpose, do you know whether can adding "#!/bin/sh echo module_hotfixes=true >> '/etc/dnf/dnf.conf'" in the "%pre" section of kickstart cfg, I tried but failed to update "/etc/dnf/dnf.conf" on target. Actually the below commit[0] making the normal repodata to module repo with the upstream "modules.yaml": http://mirror.centos.org/centos/8.1.1911/AppStream/x86_64/os/repodata/1feb2b0b68761a17ebdf1084518e3f53cec4ec5f317dc1dc7c780a2b041ec3b6-modules.yaml.gz this gz file has been deprecated , after updated the above one with the modules.yaml in https://vault.centos.org/8.1.1911/AppStream/x86_64/os/repodata/, the pyton36/python36-devel excluding issue gone, but the same issues for qemu-kvm-ev. I think this can be explained for that "qemu-kvm-ev" is not from vault AppStream, but built locally. This means we have to create module repo for these packages built locally. I found below tools set that can do this: https://github.com/rpm-software-management/modulemd-tools These tools requires that the "libmodulemd" must be upgraded to 2.0 which will cause python "__common_types" issue. I am still working on this. [0] =================================================== commit 3139368079e66aba19dab4e4ed58665df5f55ca1 (HEAD) Author: Yong Fu Date: Wed Jul 8 11:29:04 2020 +0800 CentOS 8: Add modular repository to fix ISO installation problems. In the centos8.1 environment, "dnf: No available modular metadata for modular package" error occurs in ISO installation. Modular repository must contain the modular metadata (modulemd) in the repodata. Excluding the metadata will cause all the modular packages to become standalone packages which could have negative consequences. 'modules.yaml' get from http://mirror.centos.org/centos/8.1.1911/AppStream/x86_64/os/repodata/1feb2b0b68761a17ebdf1084518e3f53cec4ec5f317dc1dc7c780a2b041ec3b6-modules.yaml.gz Change-Id: I92a7f1a3c74197d7a9cec1fb5f0cc5fa5e961900 Story: 2006729 Task: 40294 Signed-off-by: Yong Fu diff --git a/build-tools/build-iso b/build-tools/build-iso index b9ad63d..4e8d962 100755 --- a/build-tools/build-iso +++ b/build-tools/build-iso @@ -458,7 +458,8 @@ function final_touches { # create the repo \cd $OUTPUT_DIST_DIR/isolinux $CREATEREPO -q -g ../comps.xml . - + # add modulemd + modifyrepo_c --mdtype=modules $MY_REPO/build-tools/modularity/modules.yaml ./repodata # build the ISO printf "Building image $OUTPUT_FILE\n" \cd $OUTPUT_DIST_DIR diff --git a/build-tools/modularity/modules.yaml b/build-tools/modularity/modules.yaml ============================================= From: Penney, Don Sent: Monday, December 7, 2020 5:27 PM To: Bai, Haiqing ; starlingx-discuss at lists.starlingx.io Subject: RE: [CentOS8] build-pkgs/build-iso completed successfully, but installer reports dependency issues It sounds like this new RHEL8 feature, modularity: https://dnf.readthedocs.io/en/latest/modularity.html#hotfix-repositories It looks like it could be disabled with module_hotfixes=true in the repo config file, but I don't see any way of passing this to the kickstart repo command. I expect there will need to be some investigation of the differences in the installation of centos8 vs centos7, maybe look at the stock installation media to look at how the software repositories are setup. The introduction of modularity and "AppStream" could necessitate some changes in how we setup our ISO and software repositories. From: Bai, Haiqing > Sent: Monday, December 7, 2020 3:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [CentOS8] build-pkgs/build-iso completed successfully, but installer reports dependency issues Hi, all: Is there anyone knows why "build-pkgs" and "build-iso" completed successfully and bootimage.iso created, but the target installer has below errors: (I have checked that "python36" and "python36-devel" are in dist/comps.xml and the type is "mandatory" of group ID "platform-controller", "platform-controller-worker", "platform-controller-worker-lowlatency", and the kickstarts cfg files include the related group in "%packages" ). Thanks. ======================================== Error The following software marked for installation has errors. This is likely caused by an error with your installation source. Problem 1: package patch-alarm-1.0-2.tis.x86_64 requires python3-devel, but none of the providers can be installed - conflicting requests - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Problem 2: package grubby-8.40-34.el8.tis.1.x86_64 requires python3-devel, but none of the providers can be installed - conflicting requests - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Problem 3: package cgcs-patch-1.0-28.tis.x86_64 requires python3-devel, but none of the providers can be installed - conflicting requests - package python36-devel-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Problem 4: package worker-utils-1.0-5.tis.x86_64 requires /usr/bin/python3, but none of the providers can be installed - package worker-utils-1.0-5.tis.x86_64 requires python3, but none of the providers can be installed - conflicting requests - package python36-3.6.8-2.module_el8.1.0+245+c39af44f.x86_64 is excluded Press ENTER to continue: -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Wed Dec 9 03:26:02 2020 From: Robert.Church at windriver.com (Church, Robert) Date: Wed, 9 Dec 2020 03:26:02 +0000 Subject: [Starlingx-discuss] proposal for lifecycle operator In-Reply-To: References: Message-ID: Hi Martin, See inline.. Thanks, Bob From: "Chen, Haochuan Z" Date: Tuesday, December 8, 2020 at 7:32 AM To: "'starlingx-discuss at lists.starlingx.io'" , Robert Church , "Voiculeasa, Dan" Subject: proposal for lifecycle operator [Please note this e-mail is from an EXTERNAL e-mail address] Hi Bob I study patch for lifecycle operator. Something to check with you https://review.opendev.org/q/topic:%22story_2007960%22+(status:open%20OR%20status:merged) 1, lifecycle operator will merge in r5 release or not? [RTC] Yes. We’ll land this prior to MS3 (1/29/21). Based on the year-end holidays, I’d like to get this merged in the 1st or 2nd week in January 2, propose to add a hook for APP_LIFECYCLE_TIMMING_POST. Now there is only hook for constants.APP_LIFECYCLE_TIMING_PRE, which is called before application apply. Propose to add a hook to be called, after application apply, APP_LIFECYCLE_TIMMING_POST. [RTC] Seems reasonable. We’ll add this as well. Let me know if you have any other suggestions. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haridhar.kalvala at intel.com Wed Dec 9 04:07:21 2020 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Wed, 9 Dec 2020 04:07:21 +0000 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! In-Reply-To: <07701fc7-b77f-be54-4796-3165a8764a7d@windriver.com> References: <1766225256.529.1607369460415.JavaMail.javamailuser@localhost> <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> <07701fc7-b77f-be54-4796-3165a8764a7d@windriver.com> Message-ID: Hi Scott, Even I am seeing this error since last two days. It was building fine(same code/repo) prior to 7th Dec. Anything changed in upstream open stack reference ? Thank you, Haridhar Kalvala From: Scott Little Sent: Tuesday, December 8, 2020 11:16 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! There is second container build failure in the logs. The stx-horizon docker image can't find a version of Django that it can use. https://bugs.launchpad.net/starlingx/+bug/1907290 Can someone volunteer to investigate this one? Scott On 2020-12-08 1:08 a.m., build.starlingx at gmail.com wrote: [Please note this e-mail is from an EXTERNAL e-mail address] Project: STX_build_layer_containers_master_master Build #: 90 Status: Still Failing Timestamp: 20201208T014249Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Shubham.Gaur at commscope.com Wed Dec 9 05:56:09 2020 From: Shubham.Gaur at commscope.com (Gaur, Shubham) Date: Wed, 9 Dec 2020 05:56:09 +0000 Subject: [Starlingx-discuss] [Query]: Keystone-API-Proxy pod not able to initialize as part of stx-openstack application-apply Message-ID: Hi All, Stx-openstack manifest apply is failing due to continuous CrashLoopBackOff of keystone API proxy pod. I have attached the starlingx build info and the logs of keystone API proxy pod. Log info highlights the barbicanclient python module missing (ImportError: No module named barbicanclient). StarlingX Info [sysadmin at controller-0 ~(keystone_admin)]$ cat /etc/build.info ### ### StarlingX ### Built from master ### OS="centos" SW_VERSION="20.06" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="20200812T013433Z" JOB="STX_build_layer_flock_master_master" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="210" BUILD_HOST="starlingx_mirror" BUILD_DATE="2020-08-12 01:34:33 +0000" FLOCK_OS="centos" FLOCK_JOB="STX_build_layer_flock_master_master" FLOCK_BUILD_BY="starlingx.build at cengn.ca" FLOCK_BUILD_NUMBER="210" FLOCK_BUILD_HOST="starlingx_mirror" FLOCK_BUILD_DATE="2020-08-12 01:34:33 +0000" Keystone API Proxy Pod [sysadmin at controller-0 ~(keystone_admin)]$ kubectl logs keystone-api-proxy-d78757c74-l2xb5 -n openstack + dcorch-api-proxy --config-file=/etc/dcorch/dcorch.conf --type identity Traceback (most recent call last): File "/var/lib/openstack/bin/dcorch-api-proxy", line 5, in from dcorch.cmd.api_proxy import main File "/var/lib/openstack/lib/python2.7/site-packages/dcorch/cmd/api_proxy.py", line 42, in from dcorch.api.proxy.common import utils File "/var/lib/openstack/lib/python2.7/site-packages/dcorch/api/proxy/common/utils.py", line 26, in from dccommon.drivers.openstack import sdk_platform as sdk File "/var/lib/openstack/lib/python2.7/site-packages/dccommon/drivers/openstack/sdk_platform.py", line 26, in from dccommon.drivers.openstack.barbican import BarbicanClient File "/var/lib/openstack/lib/python2.7/site-packages/dccommon/drivers/openstack/barbican.py", line 23, in from barbicanclient import client ImportError: No module named barbicanclient -------------- next part -------------- An HTML attachment was scrubbed... URL: From sharath.kumar at intel.com Wed Dec 9 07:15:02 2020 From: sharath.kumar at intel.com (Kumar, Sharath) Date: Wed, 9 Dec 2020 07:15:02 +0000 Subject: [Starlingx-discuss] Help required on the code commit for the horizon repo In-Reply-To: References: Message-ID: Hi Tyler, I think the best way to go about it would be to leave horizon/openstack_dashboard packages untouched, but as part of the image build bring in the fault management plugin as its own package We also considered above method, but we are stuck on the point that goes back to mario's patch (https://review.opendev.org/c/starlingx/upstream/+/661423/4/openstack/python-horizon/centos/stx-horizon.stable_docker_image#6) of customization which was considered as hack and abandoned. copy the enabled files from it into the openstack_dashboard enabled directory inside of the image. Considering we make FM plugin and include the changes as pip packages, please let us know how to enable this ? Please provide your input at the earliest, let me know if you can have separate discussion. Regards, Sharath From: Smith, Tyler Sent: Wednesday, December 9, 2020 12:26 AM To: Kumar, Sharath ; Wang, Jing (Angie) ; Wensley, Barton ; Bujold, Kristine ; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K ; Kalvala, Haridhar ; Bhat, Gopalkrishna Subject: RE: Help required on the code commit for the horizon repo I think the best way to go about it would be to leave horizon/openstack_dashboard packages untouched, but as part of the image build bring in the fault_management plugin as its own package and copy the enabled files from it into the openstack_dashboard enabled directory inside of the image. The discussion from a while ago was whether starlingx_dashboard plugin could contain everything and have only the relevant dashboards enabled where needed in containerized and platform horizon. It looks like that ran into some issues, so the other approach would be to separate the fault_management components into its own plugin/package, which is what would be imported into the docker image. Tyler From: Kumar, Sharath > Sent: December 8, 2020 12:46 PM To: Smith, Tyler >; Wang, Jing (Angie) >; Wensley, Barton >; Bujold, Kristine >; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K >; Kalvala, Haridhar >; Bhat, Gopalkrishna > Subject: RE: Help required on the code commit for the horizon repo [Please note this e-mail is from an EXTERNAL e-mail address] Hi Tyler, Thank you for the response. I believe, once code is push to stx/gui repo it will be part of starlingx dashboard, then how openstack horizon docker image(stx-horizon) will be built using custom code which will be present in stx/gui instead of upstream horizon repo? As per my understanding, drawing below diagram of horizon docker image build process. Please let me know your views. [cid:image001.png at 01D6CE28.84D566C0] Regards, Sharath From: Smith, Tyler > Sent: Tuesday, December 8, 2020 9:09 PM To: Kumar, Sharath >; Wang, Jing (Angie) >; Wensley, Barton >; Bujold, Kristine >; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K >; Kalvala, Haridhar >; Bhat, Gopalkrishna > Subject: RE: Help required on the code commit for the horizon repo Hi Sharath, The code will have to live in the stx-gui repo at /stx/gui/ as this isn't a change we would want to push to upstream horizon. Bart, Kristine, Angie, and myself will be able to review your code. Thanks, Tyler From: Kumar, Sharath > Sent: December 8, 2020 9:46 AM To: Wang, Jing (Angie) >; Wensley, Barton >; Bujold, Kristine >; Smith, Tyler >; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K >; Kalvala, Haridhar >; Bhat, Gopalkrishna > Subject: RE: Help required on the code commit for the horizon repo [Please note this e-mail is from an EXTERNAL e-mail address] Adding starlingx-discussion. From: Kumar, Sharath Sent: Tuesday, December 8, 2020 7:54 PM To: 'angie.wang at windriver.com' >; Wensley, Barton >; 'Kristine.Bujold at windriver.com' >; Smith, Tyler > Subject: Help required on the code commit for the horizon repo Hi All, I am working on Fault management front end coding for openstack dashboard, and to push my changes for the review, I have some questions on branch and commits. My code is currently part of horizon repo which comes under distro layer. In the build layer, code will be present under below path: /stx/distro/cgcs-root/stx/git/horizon/openstack_dashboard/dashboards. Under horizon repo, only openstack community branches are present : remotes/m/master -> openstack/stable/train remotes/openstack/master remotes/openstack/stable/ocata remotes/openstack/stable/pike remotes/openstack/stable/queens remotes/openstack/stable/rocky remotes/openstack/stable/stein remotes/openstack/stable/train remotes/openstack/stable/ussuri remotes/openstack/stable/Victoria I can see starlingx branches under below path in distro layer: /stx/distro/cgcs-root/stx/git Branches: remotes/m/master -> starlingx/master remotes/starlingx/centos75 remotes/starlingx/f/centos75 remotes/starlingx/f/centos76 remotes/starlingx/f/centos8 remotes/starlingx/f/keystone-db remotes/starlingx/m/2018.07 remotes/starlingx/m/2018.08 remotes/starlingx/master remotes/starlingx/r/2018.10 remotes/starlingx/r/stx.2.0 remotes/starlingx/r/stx.3.0 remotes/starlingx/r/stx.4.0 Now challenge is, to push my code under horizon repo only openstack branches are listing , not starlingx. My questions: 1. With the present repo path and branches, I cannot push code because it will go to the openstack community. Could you please suggest how can I push my changes to the starlingx community for review? 2. Whom should I add from WindRiver team to review my code which are part of horizon repo? Thank you for helping me here. Regards, Sharath -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 22306 bytes Desc: image001.png URL: From build.starlingx at gmail.com Wed Dec 9 10:00:04 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 9 Dec 2020 05:00:04 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 52 - Still Failing! In-Reply-To: <2042280336.545.1607421675330.JavaMail.javamailuser@localhost> References: <2042280336.545.1607421675330.JavaMail.javamailuser@localhost> Message-ID: <1841522201.573.1607508004909.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 52 Status: Still Failing Timestamp: 20201209T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201209T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From ebiibe82 at gmail.com Wed Dec 9 11:30:17 2020 From: ebiibe82 at gmail.com (Amit Mahajan) Date: Wed, 9 Dec 2020 17:00:17 +0530 Subject: [Starlingx-discuss] Regarding Ironic integration with networking service Message-ID: Hi All, As per OpenStack Ironic documentation, it is recommended to install bare-metal ML2 mechanism driver and L2 agent (ironic-neutron-agent) for proper integration with the Networking service, but on the StarlingX setup that we have deployed with Ironic, we do not see "baremetal" set in mechanism_drivers in ml2_conf.ini. Also, there is no kubernetes pod in openstack namespace running ironic-neutron-agent. Is there any specific reason that integration of Ironic with networking service for routed networks is not supported in StarlingX Ironic deployment? Regards, Amit -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ronald.Stone at windriver.com Wed Dec 9 13:11:06 2020 From: Ronald.Stone at windriver.com (Stone, Ronald) Date: Wed, 9 Dec 2020 13:11:06 +0000 Subject: [Starlingx-discuss] doc-build-failures Message-ID: Hi, Starting yesterday several contributors to StarlingX docs can no longer successfully perform local doc builds: $ tox -e docs docs installed: alabaster==0.7.12,Babel==2.9.0,certifi==2020.11.8,chardet==3.0.4,colorama==0.4.4,docutils==0.15.2,dulwich==0.20.14,idna==2.10,imagesize==1.2.0,Jinja2==2.11.2,MarkupSafe==1.1.1,openstackdocstheme==2.2.7,os-api-ref==2.1.0,packaging==20.4,pbr==5.5.1,Pygments==2.7.2,pyparsing==2.4.7,pytz==2020.4,PyYAML==5.3.1,requests==2.25.0,six==1.15.0,snowballstemmer==2.0.0,Sphinx==3.3.1,sphinxcontrib-applehelp==1.0.2,sphinxcontrib-devhelp==1.0.2,sphinxcontrib-htmlhelp==1.0.3,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.3,sphinxcontrib-serializinghtml==1.1.4,urllib3==1.26.2 docs run-test-pre: PYTHONHASHSEED='925' docs run-test: commands[0] | sphinx-build -a -E -W -d doc/build/doctrees -b html doc/source doc/build/html ERROR: InvocationError for command could not find executable sphinx-build ___________________________________ summary ___________________________________ ERROR: docs: commands failed The executable sphinx-build.exe is missing from docs/.tox/docs/Scripts/ If manually restored, it is deleted the next time tox -e docs is run. docs/.tox/log is empty. Has there been a tox requirements change that would cause builds to start failing for multiple users simultaneously? Any insights/suggestions appreciated. Ron -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tao.Liu at windriver.com Wed Dec 9 14:01:47 2020 From: Tao.Liu at windriver.com (Liu, Tao) Date: Wed, 9 Dec 2020 14:01:47 +0000 Subject: [Starlingx-discuss] [Query]: Keystone-API-Proxy pod not able to initialize as part of stx-openstack application-apply In-Reply-To: References: Message-ID: Hi Shubham, The stx-openstack app is not officially supported on System Controller (in a distributed cloud environment). The error below is due to the new dependency 'barbicanclient' is not included in the docker image. Regards, Tao From: Gaur, Shubham Sent: Wednesday, December 9, 2020 12:56 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [Query]: Keystone-API-Proxy pod not able to initialize as part of stx-openstack application-apply [Please note this e-mail is from an EXTERNAL e-mail address] Hi All, Stx-openstack manifest apply is failing due to continuous CrashLoopBackOff of keystone API proxy pod. I have attached the starlingx build info and the logs of keystone API proxy pod. Log info highlights the barbicanclient python module missing (ImportError: No module named barbicanclient). StarlingX Info [sysadmin at controller-0 ~(keystone_admin)]$ cat /etc/build.info ### ### StarlingX ### Built from master ### OS="centos" SW_VERSION="20.06" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="20200812T013433Z" JOB="STX_build_layer_flock_master_master" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="210" BUILD_HOST="starlingx_mirror" BUILD_DATE="2020-08-12 01:34:33 +0000" FLOCK_OS="centos" FLOCK_JOB="STX_build_layer_flock_master_master" FLOCK_BUILD_BY="starlingx.build at cengn.ca" FLOCK_BUILD_NUMBER="210" FLOCK_BUILD_HOST="starlingx_mirror" FLOCK_BUILD_DATE="2020-08-12 01:34:33 +0000" Keystone API Proxy Pod [sysadmin at controller-0 ~(keystone_admin)]$ kubectl logs keystone-api-proxy-d78757c74-l2xb5 -n openstack + dcorch-api-proxy --config-file=/etc/dcorch/dcorch.conf --type identity Traceback (most recent call last): File "/var/lib/openstack/bin/dcorch-api-proxy", line 5, in from dcorch.cmd.api_proxy import main File "/var/lib/openstack/lib/python2.7/site-packages/dcorch/cmd/api_proxy.py", line 42, in from dcorch.api.proxy.common import utils File "/var/lib/openstack/lib/python2.7/site-packages/dcorch/api/proxy/common/utils.py", line 26, in from dccommon.drivers.openstack import sdk_platform as sdk File "/var/lib/openstack/lib/python2.7/site-packages/dccommon/drivers/openstack/sdk_platform.py", line 26, in from dccommon.drivers.openstack.barbican import BarbicanClient File "/var/lib/openstack/lib/python2.7/site-packages/dccommon/drivers/openstack/barbican.py", line 23, in from barbicanclient import client ImportError: No module named barbicanclient -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Wed Dec 9 14:27:35 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 9 Dec 2020 14:27:35 +0000 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! In-Reply-To: References: <1766225256.529.1607369460415.JavaMail.javamailuser@localhost> <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> <07701fc7-b77f-be54-4796-3165a8764a7d@windriver.com> Message-ID: <20201209142735.2w2bnfnciq63vk4o@yuggoth.org> On 2020-12-09 04:07:21 +0000 (+0000), Kalvala, Haridhar wrote: > Even I am seeing this error since last two days. It was building > fine(same code/repo) prior to 7th Dec. Anything changed in > upstream open stack reference ? [...] Not in upstream OpenStack specifically, but across the Python packaging ecosystem as a whole. Pip 20.3.0, released on November 30, turned on a new and much more thorough dependency resolver. Earlier versions of pip did not try particularly hard to make sure the dependencies claimed by packages were all satisfied. Virtualenv 20.2.2, released December 7, increased the version of pip it's vendoring to a version which uses the new solver as well. These changes mean that latent version conflicts are now being correctly identified as bugs, and so your builds will do a far better job of confirming the declared versions of dependencies are actually used if possible (and generate an error if not). The error in the bug you linked looks like it's probably a version conflict between what's in the constraints file you're applying and what horizon says it wants to satisfy its django requirement. Earlier releases of pip included in earlier releases of virtualenv may have not been capable of noticing this latent conflict, so if loci relies on virtualenv (I don't know much about it to be honest), then starting to see this bug exposed coincident with the release of virtualenv 20.2.2 would make sense. Projects in OpenStack are currently working to solve these sorts of emergent problems in their own builds as well, though for the most part keeping the global upper constraints list in sync with the corresponding project branches has shielded them from major issues and this is mainly cropping up in places where projects are supplying their own bespoke constraints lists which aren't built from a guaranteed consistent set. I don't know what the state of the source code and constraints lists being used in your builds is, so it's hard for me to speculate. If it's just asking loci to generate images from upstream stable/ussuri branches in combination with the upstream stable/ussuri upper-constraints.txt file, then perhaps this is a stable branch bug which needs to get solved in loci or even deeper in the stack. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From Don.Penney at windriver.com Wed Dec 9 14:47:40 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 9 Dec 2020 14:47:40 +0000 Subject: [Starlingx-discuss] doc-build-failures In-Reply-To: References: Message-ID: I just rebased and tried tox in docs, and it worked for me. The install list was almost identical: docs installed: alabaster==0.7.12,Babel==2.9.0,certifi==2020.11.8,chardet==3.0.4,docutils==0.15.2,dulwich==0.20.14,idna==2.10,imagesize==1.2.0,Jinja2==2.11.2,MarkupSafe==1.1.1,openstackdocstheme==2.2.7,os-api-ref==2.1.0,packaging==20.7,pbr==5.5.1,Pygments==2.7.2,pyparsing==2.4.7,pytz==2020.4,PyYAML==5.3.1,requests==2.25.0,six==1.15.0,snowballstemmer==2.0.0,Sphinx==3.3.1,sphinxcontrib-applehelp==1.0.2,sphinxcontrib-devhelp==1.0.2,sphinxcontrib-htmlhelp==1.0.3,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.3,sphinxcontrib-serializinghtml==1.1.4,urllib3==1.26.2 Have you tried wiping your .tox to start fresh, or do "tox -r" to reinstall? From: Stone, Ronald Sent: Wednesday, December 9, 2020 8:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] doc-build-failures Hi, Starting yesterday several contributors to StarlingX docs can no longer successfully perform local doc builds: $ tox -e docs docs installed: alabaster==0.7.12,Babel==2.9.0,certifi==2020.11.8,chardet==3.0.4,colorama==0.4.4,docutils==0.15.2,dulwich==0.20.14,idna==2.10,imagesize==1.2.0,Jinja2==2.11.2,MarkupSafe==1.1.1,openstackdocstheme==2.2.7,os-api-ref==2.1.0,packaging==20.4,pbr==5.5.1,Pygments==2.7.2,pyparsing==2.4.7,pytz==2020.4,PyYAML==5.3.1,requests==2.25.0,six==1.15.0,snowballstemmer==2.0.0,Sphinx==3.3.1,sphinxcontrib-applehelp==1.0.2,sphinxcontrib-devhelp==1.0.2,sphinxcontrib-htmlhelp==1.0.3,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.3,sphinxcontrib-serializinghtml==1.1.4,urllib3==1.26.2 docs run-test-pre: PYTHONHASHSEED='925' docs run-test: commands[0] | sphinx-build -a -E -W -d doc/build/doctrees -b html doc/source doc/build/html ERROR: InvocationError for command could not find executable sphinx-build ___________________________________ summary ___________________________________ ERROR: docs: commands failed The executable sphinx-build.exe is missing from docs/.tox/docs/Scripts/ If manually restored, it is deleted the next time tox -e docs is run. docs/.tox/log is empty. Has there been a tox requirements change that would cause builds to start failing for multiple users simultaneously? Any insights/suggestions appreciated. Ron -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Wed Dec 9 14:58:35 2020 From: Saul.Wold at windriver.com (Saul Wold) Date: Wed, 9 Dec 2020 06:58:35 -0800 Subject: [Starlingx-discuss] Distro Team Meeting Minutes 12/9 Message-ID: <506dc0be-811e-d275-33fe-c8c31175c74e@windriver.com> 12/09 Meeting: Ceph/Rook Status - Martin is hosting a zoom meeting - Tests are passing for Rook and Native Ceph - Waiting for core reviews from that team. CentOS-8 - Current status - Build the ISO - Anaconda install issue with modularity repos - Need to investigate creating modular repos - f/centos8 repo updates - Issue with gui and tox hacking test-requirements - HA is coming - kernel repo review is available - Integ rebase work from Neusoft - Build issue with certain packages - Couple more days to fix this issues, review should be posted by end of week - Root and Tools - Pending work from Scott - Utilities - Davlet will work on - Update - TBD - CentOS-8.2 package update - Not Started until rebase is stabiliaized - Redhat announces CentOS-8 will be EOL'ed and CentOS-Stream - Python3 - Waiting for CentOS 8 ISO to stabilize - fault containerization issues with Python2/3 - Calling between flock and openstack containers seems to have python2/3 issues - dependencies with fm-containerization, stx-horizon and cephclient - email to come from Haridar -- Sau! From bruce.e.jones at intel.com Wed Dec 9 15:07:23 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 9 Dec 2020 15:07:23 +0000 Subject: [Starlingx-discuss] TSC call minutes Dec 9 2020 Message-ID: 12/9/2020 * TSC members - please review https://review.opendev.org/c/starlingx/governance/+/765371 and https://review.opendev.org/c/starlingx/specs/+/750636 * No other topics for today... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Wed Dec 9 15:09:06 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Wed, 9 Dec 2020 15:09:06 +0000 Subject: [Starlingx-discuss] doc-build-failures In-Reply-To: References: Message-ID: Ron pip and virtualenv changed recently (within the last week) so it has wide reaching impact. In my ubuntu container which pulls in the new virtualenv and pip, it appears to be working. That env has python3.6 The only difference I see is that mine pulls in packaging==20.7 whereas yours is using 20.4 docs installed: alabaster==0.7.12,Babel==2.9.0,certifi==2020.11.8,chardet==3.0.4,docutils==0.15.2,dulwich==0.20.14,idna==2.10,imagesize==1.2.0,Jinja2==2.11.2,MarkupSafe==1.1.1,openstackdocstheme==2.2.7,os-api-ref==2.1.0,packaging==20.7,pbr==5.5.1,Pygments==2.7.2,pyparsing==2.4.7,pytz==2020.4,PyYAML==5.3.1,requests==2.25.0,six==1.15.0,snowballstemmer==2.0.0,Sphinx==3.3.1,sphinxcontrib-applehelp==1.0.2,sphinxcontrib-devhelp==1.0.2,sphinxcontrib-htmlhelp==1.0.3,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.3,sphinxcontrib-serializinghtml==1.1.4,urllib3==1.26.2 docs run-test-pre: PYTHONHASHSEED='3039678748' docs run-test: commands[0] | sphinx-build -a -E -W -d doc/build/doctrees -b html doc/source doc/build/html Running Sphinx v3.3.1 [openstackdocstheme] version: 2.2.7 [openstackdocstheme] connecting html-page-context event handler Al ________________________________ From: Stone, Ronald Sent: Wednesday, December 9, 2020 8:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] doc-build-failures Hi, Starting yesterday several contributors to StarlingX docs can no longer successfully perform local doc builds: $ tox -e docs docs installed: alabaster==0.7.12,Babel==2.9.0,certifi==2020.11.8,chardet==3.0.4,colorama==0.4.4,docutils==0.15.2,dulwich==0.20.14,idna==2.10,imagesize==1.2.0,Jinja2==2.11.2,MarkupSafe==1.1.1,openstackdocstheme==2.2.7,os-api-ref==2.1.0,packaging==20.4,pbr==5.5.1,Pygments==2.7.2,pyparsing==2.4.7,pytz==2020.4,PyYAML==5.3.1,requests==2.25.0,six==1.15.0,snowballstemmer==2.0.0,Sphinx==3.3.1,sphinxcontrib-applehelp==1.0.2,sphinxcontrib-devhelp==1.0.2,sphinxcontrib-htmlhelp==1.0.3,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.3,sphinxcontrib-serializinghtml==1.1.4,urllib3==1.26.2 docs run-test-pre: PYTHONHASHSEED='925' docs run-test: commands[0] | sphinx-build -a -E -W -d doc/build/doctrees -b html doc/source doc/build/html ERROR: InvocationError for command could not find executable sphinx-build ___________________________________ summary ___________________________________ ERROR: docs: commands failed The executable sphinx-build.exe is missing from docs/.tox/docs/Scripts/ If manually restored, it is deleted the next time tox -e docs is run. docs/.tox/log is empty. Has there been a tox requirements change that would cause builds to start failing for multiple users simultaneously? Any insights/suggestions appreciated. Ron -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Wed Dec 9 15:45:58 2020 From: Saul.Wold at windriver.com (Wold, Saul) Date: Wed, 9 Dec 2020 15:45:58 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Message-ID: Hi All: Update new series Next Meeting will be planned on Dec 23 (last of the year). * Cadence and time slot: * Bi-Weekly Wednesday 9AM EDT (2200 China time, US PDT time 6AM) * Call Details: * Zoom link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * Dialing in from phone: * Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 * Meeting ID: 342 730 236 * Passcode: 419405 * International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: * https://etherpad.openstack.org/p/stx-distro-other Sau! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 6841 bytes Desc: not available URL: From tyler.smith at windriver.com Wed Dec 9 15:51:42 2020 From: tyler.smith at windriver.com (Smith, Tyler) Date: Wed, 9 Dec 2020 15:51:42 +0000 Subject: [Starlingx-discuss] Help required on the code commit for the horizon repo In-Reply-To: References: Message-ID: The iffy part of that approach was modifying code directly using sed commands during image build. From my comment here https://review.opendev.org/c/starlingx/upstream/+/661423/3/openstack/python-horizon/centos/stx-horizon.stable_docker_image#36 some of these changes are expected. The way plugins are registered with horizon some file copying commands are necessary. I'm not all that familiar with pip packaging, but after being installed in the image, the plugin code along with the enabled files in it should be available to copy the enabled files over to the openstack_dashboard enabled folder Thanks, Tyler From: Kumar, Sharath Sent: December 9, 2020 2:15 AM To: Smith, Tyler ; Wang, Jing (Angie) ; Wensley, Barton ; Bujold, Kristine ; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K ; Kalvala, Haridhar ; Bhat, Gopalkrishna Subject: RE: Help required on the code commit for the horizon repo Importance: High [Please note this e-mail is from an EXTERNAL e-mail address] Hi Tyler, I think the best way to go about it would be to leave horizon/openstack_dashboard packages untouched, but as part of the image build bring in the fault management plugin as its own package We also considered above method, but we are stuck on the point that goes back to mario's patch (https://review.opendev.org/c/starlingx/upstream/+/661423/4/openstack/python-horizon/centos/stx-horizon.stable_docker_image#6) of customization which was considered as hack and abandoned. copy the enabled files from it into the openstack_dashboard enabled directory inside of the image. Considering we make FM plugin and include the changes as pip packages, please let us know how to enable this ? Please provide your input at the earliest, let me know if you can have separate discussion. Regards, Sharath From: Smith, Tyler > Sent: Wednesday, December 9, 2020 12:26 AM To: Kumar, Sharath >; Wang, Jing (Angie) >; Wensley, Barton >; Bujold, Kristine >; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K >; Kalvala, Haridhar >; Bhat, Gopalkrishna > Subject: RE: Help required on the code commit for the horizon repo I think the best way to go about it would be to leave horizon/openstack_dashboard packages untouched, but as part of the image build bring in the fault_management plugin as its own package and copy the enabled files from it into the openstack_dashboard enabled directory inside of the image. The discussion from a while ago was whether starlingx_dashboard plugin could contain everything and have only the relevant dashboards enabled where needed in containerized and platform horizon. It looks like that ran into some issues, so the other approach would be to separate the fault_management components into its own plugin/package, which is what would be imported into the docker image. Tyler From: Kumar, Sharath > Sent: December 8, 2020 12:46 PM To: Smith, Tyler >; Wang, Jing (Angie) >; Wensley, Barton >; Bujold, Kristine >; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K >; Kalvala, Haridhar >; Bhat, Gopalkrishna > Subject: RE: Help required on the code commit for the horizon repo [Please note this e-mail is from an EXTERNAL e-mail address] Hi Tyler, Thank you for the response. I believe, once code is push to stx/gui repo it will be part of starlingx dashboard, then how openstack horizon docker image(stx-horizon) will be built using custom code which will be present in stx/gui instead of upstream horizon repo? As per my understanding, drawing below diagram of horizon docker image build process. Please let me know your views. [cid:image001.png at 01D6CE14.8F9B5D80] Regards, Sharath From: Smith, Tyler > Sent: Tuesday, December 8, 2020 9:09 PM To: Kumar, Sharath >; Wang, Jing (Angie) >; Wensley, Barton >; Bujold, Kristine >; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K >; Kalvala, Haridhar >; Bhat, Gopalkrishna > Subject: RE: Help required on the code commit for the horizon repo Hi Sharath, The code will have to live in the stx-gui repo at /stx/gui/ as this isn't a change we would want to push to upstream horizon. Bart, Kristine, Angie, and myself will be able to review your code. Thanks, Tyler From: Kumar, Sharath > Sent: December 8, 2020 9:46 AM To: Wang, Jing (Angie) >; Wensley, Barton >; Bujold, Kristine >; Smith, Tyler >; starlingx-discuss at lists.starlingx.io Cc: Mukherjee, Sanjay K >; Kalvala, Haridhar >; Bhat, Gopalkrishna > Subject: RE: Help required on the code commit for the horizon repo [Please note this e-mail is from an EXTERNAL e-mail address] Adding starlingx-discussion. From: Kumar, Sharath Sent: Tuesday, December 8, 2020 7:54 PM To: 'angie.wang at windriver.com' >; Wensley, Barton >; 'Kristine.Bujold at windriver.com' >; Smith, Tyler > Subject: Help required on the code commit for the horizon repo Hi All, I am working on Fault management front end coding for openstack dashboard, and to push my changes for the review, I have some questions on branch and commits. My code is currently part of horizon repo which comes under distro layer. In the build layer, code will be present under below path: /stx/distro/cgcs-root/stx/git/horizon/openstack_dashboard/dashboards. Under horizon repo, only openstack community branches are present : remotes/m/master -> openstack/stable/train remotes/openstack/master remotes/openstack/stable/ocata remotes/openstack/stable/pike remotes/openstack/stable/queens remotes/openstack/stable/rocky remotes/openstack/stable/stein remotes/openstack/stable/train remotes/openstack/stable/ussuri remotes/openstack/stable/Victoria I can see starlingx branches under below path in distro layer: /stx/distro/cgcs-root/stx/git Branches: remotes/m/master -> starlingx/master remotes/starlingx/centos75 remotes/starlingx/f/centos75 remotes/starlingx/f/centos76 remotes/starlingx/f/centos8 remotes/starlingx/f/keystone-db remotes/starlingx/m/2018.07 remotes/starlingx/m/2018.08 remotes/starlingx/master remotes/starlingx/r/2018.10 remotes/starlingx/r/stx.2.0 remotes/starlingx/r/stx.3.0 remotes/starlingx/r/stx.4.0 Now challenge is, to push my code under horizon repo only openstack branches are listing , not starlingx. My questions: 1. With the present repo path and branches, I cannot push code because it will go to the openstack community. Could you please suggest how can I push my changes to the starlingx community for review? 2. Whom should I add from WindRiver team to review my code which are part of horizon repo? Thank you for helping me here. Regards, Sharath -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 22306 bytes Desc: image001.png URL: From Bill.Zvonar at windriver.com Wed Dec 9 15:54:17 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 9 Dec 2020 15:54:17 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 9, 2020) In-Reply-To: References: Message-ID: Notes from today's meeting... * Standing Topics * Sanity * some build issues early this week, but otherwise Sanity all green * per Scott, he's working on several issues now - is asking for some help from Container SMEs - we'll revisit later in the call * Gerrit Reviews in Need of Attention * Rook changes. * latest eng build test result * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010269.html * https://review.opendev.org/c/starlingx/config/+/720637 * https://review.opendev.org/c/starlingx/rook-ceph/+/716792 * https://review.opendev.org/c/starlingx/rook-ceph/+/765693 * https://review.opendev.org/c/starlingx/utilities/+/760503 * https://review.opendev.org/c/starlingx/ha/+/764588 * https://review.opendev.org/c/starlingx/stx-puppet/+/739363 * https://review.opendev.org/c/starlingx/config/+/758935 * https://review.opendev.org/c/starlingx/metal/+/737228 * https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 * CentOS 8 updates coming, per Saul * https://review.opendev.org/q/projects:starlingx/+AND+intopic:%255Ecentos8.*+AND+status:open * Topics for this Week * Doc Build Failures * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010314.html * Outreachy internship program - ildikov * https://www.outreachy.org/ * Ildilko will send more information * Redhat announcement regarding CentOS 8 -> CentOS Stream and EOL dates * https://www.redhat.com/en/blog/centos-stream-building-innovative-future-enterprise-linux * https://www.cyberciti.biz/linux-news/centos-linux-8-will-end-in-2021-and-shifts-focus-to-centos-stream/ * https://wiki.centos.org/About/Product * CentOS 8 will be EOL Dec 2021 - among other things, this means no CVE fixes as of then * CentOS Stream will get CVE fixes, but later than other things * what about Python 3? CentOS 7 supports Python 2 & 3, so conceivably we could do a slower migration there, but would have to ultimately get everything on Python 3 eventually (say on a separate branch) * Saul will run point on fleshing this out some more * regarding planning implications, we'll plan to discuss during the next Release Team meeting (next Wednesday), though CentOS 8 is not formally in stx.5.0 release yet at this point * ARs from Previous Meetings * Bill still has the one from last week re: getting a Docker Hub pro account * Open Requests for Help * Missing host-port in controller-1 * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010243.html * Austin already talked to the guy * Starlingx Ironic Bare metal partitioned-disk image issue * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010270.html * Austin will look into this * Keystone-API-Proxy pod not able to initialize as part of stx-openstack application-apply * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010310.html * no takers on this one * Regarding Ironic integration with networking service * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010313.html * Austin will look into this * Build Matters (if required) * regarding the stx-horizon container build issue * https://bugs.launchpad.net/starlingx/+bug/1907290 * per Austin, could be related to upper-constraints.txt * Hari is looking into this as well, since it's blocking him http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010309.html * there's a repo issue related to Python 2 / 3 * Scott looking into fixing this up - may be changes in a couple of places and/or some new recommendations -----Original Message----- From: Zvonar, Bill Sent: Tuesday, December 8, 2020 5:09 PM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Dec 9, 2020) Hi all, reminder of tomorrow's TSC/Community call. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201209T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From scott.little at windriver.com Wed Dec 9 16:24:09 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 9 Dec 2020 11:24:09 -0500 Subject: [Starlingx-discuss] repo error Message-ID: <02b800c8-7b48-dec9-03b7-b42d288b7d95@windriver.com> Some of you may be seeing error from the 'repo' tool ... *e.g.* **00:30:01* repo init -u 'https://opendev.org/starlingx/manifest' -b 'master' 00:30:01* Traceback (most recent call last): *00:30:01* File "/var/lib/jenkins/stx-repo/master/.repo/repo/main.py", line 56, in *00:30:01* from subcmds.version import Version *00:30:01* File "/var/lib/jenkins/stx-repo/master/.repo/repo/subcmds/__init__.py", line 38, in *00:30:01* ['%s' % name]) *00:30:01* File "/var/lib/jenkins/stx-repo/master/.repo/repo/subcmds/upload.py", line 27, in *00:30:01* from hooks import RepoHook *00:30:01* File "/var/lib/jenkins/stx-repo/master/.repo/repo/hooks.py", line 472 *00:30:01* file=sys.stderr) *00:30:01* ^ *00:30:01* SyntaxError: invalid syntax repo put out an update that has broken python 2 compatibility. To get it working again, you may need to install python3 on your system. If you still encounter errors, It may be because repo uses ... #!/usr/bin/env python Which means that it will use the first 'python' it finds in your PATH, and there are various ways that 'python' might map to python2 or python3 depending on your system. If your system is defaulting to python2 and it otherwise is working for you, I'm reluctant to recommend making python3 the default. It might be safer to edit 'repo' and force it to use python3. REPO=$(which repo) PY3=$(which python3) echo " $REPO $PY3" /usr/local/bin/repo /usr/bin/python3 # If everything looks sane ... sudo cp ${REPO} ${REPO}.original sudo sed "s%#\!/usr/bin/env python%#\!${PY3}%" -i ${REPO} # Did it work ? head -n1 $REPO     #!/usr/bin/python3 I'll be testing our build container, and if required posting an update to our Dockerfile. Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Wed Dec 9 22:25:09 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 9 Dec 2020 22:25:09 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-12-08 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-12-09 All -- reviews merged since last meeting: 3 All -- bug status -- 22 total - team agrees to defer all low priority LP until the upstreaming effort is completed. 13 LP are WIP against API documentation, which is generated from source code (low priority). Those reviews are here: https://review.opendev.org/#/q/project:starlingx/config Reviews in progress: upstream docs, rook reviews Opens: Gerrit issues ongoing today - status link to bookmark: https://wiki.openstack.org/wiki/Infrastructure_Status WindRiver docs team is blocked from building docs locally. Could be caused by the recent PIP update? They are on Windows machines. Several messages about this on stx-discuss and openstack-discuss, including: http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019285.html Ron posted message on STX discuss - other WR folks have suggested possible fixes. Ron will uninstall/reinstall tox as recommended and see what happens. AR Mary send Ron and Juanita my cheatsheet for setup. (Mary sets up Ubuntu within Windows and works behind a proxy, so it's not an exact comparison.) Upstreaming status: Security guide updates coming end of week, also System Admin. Node management doc was delayed but should be coming soon. Ron is working on the deeply nested index files and how to make it flatter. User Tasks guide may be a good example to follow: https://docs.starlingx.io/usertasks/index.html STX 5.0 Release team Etherpad: https://etherpad.opendev.org/p/stx-releases R5.0 Feature List: https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=1107209846 Row 15 is SNMPv3. Spec is complete. Code merge target = 15Jan21 Doc Process discussion - How to coordinate changes to docs that have been upstreamed (part of StarlingX docs) SNMPv3 is planned for the STX R5 release (April 2020 target). The tasks are captured in this story: https://storyboard.openstack.org/#!/story/2008132 Changes will affect the Fault Management Guide, which is already upstreamed. This is the first time we're running into this, so we want to be clear about the process. On STX, we update the docs on an ongoing basis in the master branch. Then at release time, they are branched and tagged. This means the SNMPv3 changes will be publicly available before R5 release. The team agreed that Mary will add starlingx/docs tasks to the story, email Les with heads-up / how can I help? Code review: remove the config/CLI commands from software: https://review.opendev.org/c/starlingx/config/+/765813 Requires doc change in starlingx/config repo: /api-ref/source/api-ref-sysinv-v1-config.rst ~line 4800 AR Mary reply to review. Remove REST API from software: https://review.opendev.org/c/starlingx/config/+/766094 Requires doc change in starlingx/docs repo: doc/source/cli_ref/system.rst ~line 315 AR Mary reply to review. Doc reviews should be set to "depends on" the code change reviews. Open: How to document SNMPv2 and V3 in the same docs? Identify SNMP v2 as "planned for deprecation"? From Don.Penney at windriver.com Wed Dec 9 22:56:28 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 9 Dec 2020 22:56:28 +0000 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! In-Reply-To: References: <1766225256.529.1607369460415.JavaMail.javamailuser@localhost> <1236726844.542.1607407735425.JavaMail.javamailuser@localhost> <07701fc7-b77f-be54-4796-3165a8764a7d@windriver.com> Message-ID: I've posted a fix for the stx-horizon build issue: https://review.opendev.org/c/starlingx/root/+/766357 Inclusion of a specific version of Django in our wheels tarball for the loci build resulted in a conflict between the upper-constraints.txt in the tarball and the requirements.txt from openstack/horizon. The new pip resolver exposed this conflict and causes the stx-horizon image build to fail. Removing the entry from our stable-wheels.cfg avoids the conflict, and I'm able to successfully build the image. Once the review is approved and merged, we can kick a new image build from cengn. Cheers, Don. From: Penney, Don Sent: Tuesday, December 8, 2020 12:55 PM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! That seems odd. It certainly looks like pypi.org has a wheel that should satisfy the requirement Django<3.0,>=2.2: https://pypi.org/project/Django/2.2.17/#files Django-2.2.17-py3-none-any.whl This is a py3 wheel, and stx-horizon has been updated to python3: https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-horizon/centos/stx-horizon.stable_docker_image#L16 From: Scott Little > Sent: Tuesday, December 8, 2020 12:46 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 90 - Still Failing! There is second container build failure in the logs. The stx-horizon docker image can't find a version of Django that it can use. https://bugs.launchpad.net/starlingx/+bug/1907290 Can someone volunteer to investigate this one? Scott On 2020-12-08 1:08 a.m., build.starlingx at gmail.com wrote: [Please note this e-mail is from an EXTERNAL e-mail address] Project: STX_build_layer_containers_master_master Build #: 90 Status: Still Failing Timestamp: 20201208T014249Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201208T014249Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Dec 10 02:22:44 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 10 Dec 2020 02:22:44 +0000 Subject: [Starlingx-discuss] proposal for lifecycle operator In-Reply-To: References: Message-ID: Hi Bob For lifecycle operator, after it merge, I should update two of my patch for rook. If your patch merge in 1st and 2nd week of Jan, it only left 1 or two week for me, with basic function validation. It is very time limited for me. So I wish to merge my patch firstly and I could work together with Dan for lifecycle operator. https://review.opendev.org/c/starlingx/config/+/720637 https://review.opendev.org/c/starlingx/rook-ceph/+/716792 https://review.opendev.org/c/starlingx/rook-ceph/+/765693 https://review.opendev.org/c/starlingx/utilities/+/760503 https://review.opendev.org/c/starlingx/ha/+/764588 https://review.opendev.org/c/starlingx/stx-puppet/+/739363 https://review.opendev.org/c/starlingx/config/+/758935 https://review.opendev.org/c/starlingx/metal/+/737228 https://review.opendev.org/c/starlingx/openstack-armada-app/+/731872 Please review my patch. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Church, Robert Sent: Wednesday, December 9, 2020 11:26 AM To: Chen, Haochuan Z ; starlingx-discuss at lists.starlingx.io; Voiculeasa, Dan Subject: Re: proposal for lifecycle operator Hi Martin, See inline.. Thanks, Bob From: "Chen, Haochuan Z" > Date: Tuesday, December 8, 2020 at 7:32 AM To: "'starlingx-discuss at lists.starlingx.io'" >, Robert Church >, "Voiculeasa, Dan" > Subject: proposal for lifecycle operator [Please note this e-mail is from an EXTERNAL e-mail address] Hi Bob I study patch for lifecycle operator. Something to check with you https://review.opendev.org/q/topic:%22story_2007960%22+(status:open%20OR%20status:merged) 1, lifecycle operator will merge in r5 release or not? [RTC] Yes. We’ll land this prior to MS3 (1/29/21). Based on the year-end holidays, I’d like to get this merged in the 1st or 2nd week in January 2, propose to add a hook for APP_LIFECYCLE_TIMMING_POST. Now there is only hook for constants.APP_LIFECYCLE_TIMING_PRE, which is called before application apply. Propose to add a hook to be called, after application apply, APP_LIFECYCLE_TIMMING_POST. [RTC] Seems reasonable. We’ll add this as well. Let me know if you have any other suggestions. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fuyong at neusoft.com Thu Dec 10 02:25:51 2020 From: fuyong at neusoft.com (fuyong) Date: Thu, 10 Dec 2020 10:25:51 +0800 Subject: [Starlingx-discuss] [CentOS8] build-pkgs/build-iso completed successfully, but installer reports dependency issues In-Reply-To: References: Message-ID: Hi Haiqing Thanks for your investigation. >>“#!/bin/sh echo module_hotfixes=true >> ‘/etc/dnf/dnf.conf’” in the “%pre” section of kickstart cfg" yes, i tried, it invalid. In the end, I had to use "modules.yaml". On 2020/12/9 上午10:32, Bai, Haiqing wrote: You are right, this is caused by the dnf modularity. For just test purpose, do you know whether can adding “#!/bin/sh echo module_hotfixes=true >> ‘/etc/dnf/dnf.conf’” in the “%pre” section of kickstart cfg, I tried but failed to update “/etc/dnf/dnf.conf” on target. Actually the below commit[0] making the normal repodata to module repo with the upstream “modules.yaml”: http://mirror.centos.org/centos/8.1.1911/AppStream/x86_64/os/repodata/1feb2b0b68761a17ebdf1084518e3f53cec4ec5f317dc1dc7c780a2b041ec3b6-modules.yaml.gz this gz file has been deprecated , after updated the above one with the modules.yaml in https://vault.centos.org/8.1.1911/AppStream/x86_64/os/repodata/, the pyton36/python36-devel excluding issue gone, but the same issues for qemu-kvm-ev. I think this can be explained for that “qemu-kvm-ev” is not from vault AppStream, but built locally. This means we have to create module repo for these packages built locally. I found below tools set that can do this: https://github.com/rpm-software-management/modulemd-tools These tools requires that the “libmodulemd” must be upgraded to 2.0 which will cause python “__common_types” issue. I am still working on this. --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Dec 10 02:43:50 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 9 Dec 2020 21:43:50 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 383 - Failure! Message-ID: <1037023089.586.1607568231388.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 383 Status: Failure Timestamp: 20201210T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201210T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From zhipengs.liu at intel.com Thu Dec 10 02:54:41 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 10 Dec 2020 02:54:41 +0000 Subject: [Starlingx-discuss] Regarding Ironic integration with networking service In-Reply-To: References: Message-ID: Hi Amit, From openstack-helm, I see deployment_ironic_agent was disabled by default. You can enable it through user override.( system helm-override-update command) https://opendev.org/openstack/openstack-helm/src/branch/master/neutron/values.yaml#L2510 Thanks! Zhipeng From: Amit Mahajan Sent: 2020年12月9日 19:30 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Regarding Ironic integration with networking service Hi All, As per OpenStack Ironic documentation, it is recommended to install bare-metal ML2 mechanism driver and L2 agent (ironic-neutron-agent) for proper integration with the Networking service, but on the StarlingX setup that we have deployed with Ironic, we do not see "baremetal" set in mechanism_drivers in ml2_conf.ini. Also, there is no kubernetes pod in openstack namespace running ironic-neutron-agent. Is there any specific reason that integration of Ironic with networking service for routed networks is not supported in StarlingX Ironic deployment? Regards, Amit -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Dec 10 03:06:17 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 10 Dec 2020 03:06:17 +0000 Subject: [Starlingx-discuss] Starlingx Ironic Bare metal partitioned-disk image issue In-Reply-To: References: Message-ID: Hi Akshay, You can build your customized ironic image if you want to add you required packages. https://docs.starlingx.io/developer_resources/build_docker_image.html Or you can submit a LP and raise your patch to change below line and get it reviewed in our community. https://review.opendev.org/c/starlingx/upstream/+/712862/20/openstack/openstack-ironic/centos/stx-ironic.stable_docker_image#7 Thanks! Zhipeng From: Akki yadav Sent: 2020年12月7日 21:31 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Starlingx Ironic Bare metal partitioned-disk image issue Hi Team, Hope you all are doing good. I have a Standard Starlingx R4.0 with ironic setup up and running. I have launched a Bare metal with whole-disk image and it came up flawlessly. But when I was trying to launch a bare metal node with partitioned-disk image, It gave me an error in the ironic-conductor stating that "sgdisk: not found". Then steps I did to resolve it are: 1. Then I installed "gdisk" on both containers of ironic-conductor . (i.e. ironic-conductor-0 and ironic-conductor-1). 2. Now, I tried agin to launch a bare metal node, this time it failed stating "parted : not found". 3. Then I installed "parted" on both containers of ironic-conductor . (i.e. ironic-conductor-0 and ironic-conductor-1). 4. Now I can flawlessly launch bare metal node with partitioned-disk image. Now, I wanted to know how may I get these packages (gdisk and parted) already installed in ironic-conductor containers when the stx-openstack application gets applied ? Regards Akshay -------------- next part -------------- An HTML attachment was scrubbed... URL: From haridhar.kalvala at intel.com Thu Dec 10 04:48:09 2020 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Thu, 10 Dec 2020 04:48:09 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. Message-ID: Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein's openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: Saul Wold Subject: [Starlingx-discuss] Distro Team Meeting Minutes 12/9 Date: Wed, 9 Dec 2020 14:58:35 +0000 Size: 18406 URL: From build.starlingx at gmail.com Thu Dec 10 05:43:06 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 10 Dec 2020 00:43:06 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 763 - Still Failing! In-Reply-To: null References: null Message-ID: <1019038166.595.1607578987050.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 763 Status: Still Failing Timestamp: 20201210T053001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201210T053001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Thu Dec 10 10:10:50 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 10 Dec 2020 05:10:50 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 53 - Still Failing! In-Reply-To: <1804394430.571.1607508003135.JavaMail.javamailuser@localhost> References: <1804394430.571.1607508003135.JavaMail.javamailuser@localhost> Message-ID: <1271147039.600.1607595051161.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 53 Status: Still Failing Timestamp: 20201210T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201210T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From alexandru.dimofte at intel.com Thu Dec 10 14:55:17 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 10 Dec 2020 14:55:17 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201209T154905Z Message-ID: Sanity Test from 2020-December-9 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201209T154905Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201209T154905Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 8408 bytes Desc: image003.png URL: From poornima.y.n at intel.com Thu Dec 10 16:22:24 2020 From: poornima.y.n at intel.com (N, Poornima Y) Date: Thu, 10 Dec 2020 16:22:24 +0000 Subject: [Starlingx-discuss] Query on Patch merge Message-ID: Hi all, I have uploaded following patches on the opendev gerrit server. Even though I have got +2 I see that the patch status is still "Merge If Necessary". Can anyone help what needs to be done here to get these patches merged? 1. https://review.opendev.org/c/starlingx/specs/+/750636 2. https://review.opendev.org/c/openstack/project-config/+/765494 Thanks and Regards, Poornima -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Thu Dec 10 23:19:18 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Thu, 10 Dec 2020 23:19:18 +0000 Subject: [Starlingx-discuss] Query on Patch merge In-Reply-To: References: Message-ID: I think you have followed the proper procedure https://wiki.openstack.org/wiki/StarlingX/Feature_Development_Process#Specification_Process Once enough TSC have approved, one of them will give W+1, usually after a TSC meeting I think. Al ________________________________ From: N, Poornima Y Sent: Thursday, December 10, 2020 11:22 AM To: starlingx-discuss at lists.starlingx.io Cc: N, Poornima Y Subject: [Starlingx-discuss] Query on Patch merge [Please note this e-mail is from an EXTERNAL e-mail address] Hi all, I have uploaded following patches on the opendev gerrit server. Even though I have got +2 I see that the patch status is still “Merge If Necessary”. Can anyone help what needs to be done here to get these patches merged? 1. https://review.opendev.org/c/starlingx/specs/+/750636 2. https://review.opendev.org/c/openstack/project-config/+/765494 Thanks and Regards, Poornima -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Dec 11 16:50:40 2020 From: scott.little at windriver.com (Scott Little) Date: Fri, 11 Dec 2020 11:50:40 -0500 Subject: [Starlingx-discuss] [Build] All master branch builds passed last might In-Reply-To: <1112093441.536.1607407730312.JavaMail.javamailuser@localhost> References: <1682628245.523.1607369454600.JavaMail.javamailuser@localhost> <1112093441.536.1607407730312.JavaMail.javamailuser@localhost> Message-ID: <4edf4cb7-9ace-b439-fe05-4b0f7c509726@windriver.com> All master branch layers build successfully last night. Scott From build.starlingx at gmail.com Fri Dec 11 19:04:13 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 11 Dec 2020 14:04:13 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_download_mirror - Build # 1087 - Failure! Message-ID: <1552926935.616.1607713454700.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1087 Status: Failure Timestamp: 20201211T100221Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201211T100001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/centos8 DOCKER_BUILD_ID: jenkins-f-centos8-20201211T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201211T100001Z/logs MY_REPO: /localdisk/designer/jenkins/f-centos8/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201211T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Fri Dec 11 19:04:17 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 11 Dec 2020 14:04:17 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 54 - Still Failing! In-Reply-To: <662618221.598.1607595049387.JavaMail.javamailuser@localhost> References: <662618221.598.1607595049387.JavaMail.javamailuser@localhost> Message-ID: <1784588590.619.1607713458013.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 54 Status: Still Failing Timestamp: 20201211T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201211T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From alexandru.dimofte at intel.com Fri Dec 11 20:40:54 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 11 Dec 2020 20:40:54 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201211T023154Z Message-ID: Sanity Test from 2020-December-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201211T023154Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201211T023154Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] 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 ] Standard External - 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 ] =========================================== Sanity Test executed on 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External 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 ] Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8408 bytes Desc: image001.png URL: From build.starlingx at gmail.com Sat Dec 12 10:55:29 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 12 Dec 2020 05:55:29 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_download_mirror - Build # 1089 - Failure! Message-ID: <1550593096.623.1607770530178.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1089 Status: Failure Timestamp: 20201212T102316Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201212T100001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/centos8 DOCKER_BUILD_ID: jenkins-f-centos8-20201212T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201212T100001Z/logs MY_REPO: /localdisk/designer/jenkins/f-centos8/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201212T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Sat Dec 12 10:55:31 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 12 Dec 2020 05:55:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 55 - Still Failing! In-Reply-To: <765166350.617.1607713455776.JavaMail.javamailuser@localhost> References: <765166350.617.1607713455776.JavaMail.javamailuser@localhost> Message-ID: <1332438493.626.1607770532553.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 55 Status: Still Failing Timestamp: 20201212T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201212T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From ildiko.vancsa at gmail.com Sat Dec 12 11:27:15 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Sat, 12 Dec 2020 12:27:15 +0100 Subject: [Starlingx-discuss] Outreachy internship program Message-ID: <49E8B0CE-98E0-4AF8-977C-BDE48EEB8819@gmail.com> Hi StarlingX Community, I’m reaching out to you about the Outreachy internship program. The OpenStack community has been mentoring Outreachy interns for a while and it’s been a great experience for both mentors and interns. As StarlingX is a confirmed top-level project it came up if the community might interested in participating in this program as well? The goal of the program is to support people from groups underrepresented in tech. The internship period is 3-months where the interns are working on pre-defined tasks. You can find more information about the program and timeline here: https://www.outreachy.org/mentor/ Please let me know if you have any questions. My question to you is would that StarlingX community be interested in participating? Are there volunteers to become mentors? Thanks, Ildikó From build.starlingx at gmail.com Sun Dec 13 10:50:18 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 13 Dec 2020 05:50:18 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_download_mirror - Build # 1091 - Failure! Message-ID: <1495282264.630.1607856618936.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1091 Status: Failure Timestamp: 20201213T102244Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201213T100001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/centos8 DOCKER_BUILD_ID: jenkins-f-centos8-20201213T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201213T100001Z/logs MY_REPO: /localdisk/designer/jenkins/f-centos8/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201213T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Sun Dec 13 10:50:20 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 13 Dec 2020 05:50:20 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 56 - Still Failing! In-Reply-To: <1386215861.624.1607770530817.JavaMail.javamailuser@localhost> References: <1386215861.624.1607770530817.JavaMail.javamailuser@localhost> Message-ID: <500848848.633.1607856621563.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 56 Status: Still Failing Timestamp: 20201213T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201213T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Shubham.Gaur at commscope.com Mon Dec 14 08:41:35 2020 From: Shubham.Gaur at commscope.com (Gaur, Shubham) Date: Mon, 14 Dec 2020 08:41:35 +0000 Subject: [Starlingx-discuss] [Info Required] Deploy custom armada/ helm application using StrarlingX Rest API Endpoint Message-ID: Hi All, Has there any Rest API/ Application Endpoint been provided to deploy armada application post-installation? Use Case: Need to deploy applications using armada manifest or helm package from outside the StarlingX Network. Thanks and regards, Shubham -------------- next part -------------- An HTML attachment was scrubbed... URL: From haridhar.kalvala at intel.com Mon Dec 14 11:12:55 2020 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Mon, 14 Dec 2020 11:12:55 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. In-Reply-To: References: Message-ID: Reminder for below request. Thank You, Haridhar Kalvala From: Kalvala, Haridhar Sent: Thursday, December 10, 2020 10:18 AM To: starlingx-discuss at lists.starlingx.io; Wensley, Barton ; Saul Wold ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada Subject: Flock components python3 migration query on master. Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein's openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde > Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Dec 14 12:55:08 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 14 Dec 2020 07:55:08 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 305 - Failure! Message-ID: <2078774240.641.1607950509279.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 305 Status: Failure Timestamp: 20201214T092521Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201214T053001Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20201214T053001Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20201214T053001Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201214T053001Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20201214T053001Z/logs PUBLISH_TIMESTAMP: 20201214T053001Z FLOCK_VERSION: master-centos-stable-20201214T053001Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20201214T053001Z BUILD_STREAM: stable REGISTRY_ORG: slittlewrs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20201214T053001Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Mon Dec 14 12:55:11 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 14 Dec 2020 07:55:11 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images - Build # 282 - Failure! Message-ID: <680544472.644.1607950511736.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 282 Status: Failure Timestamp: 20201214T090527Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201214T053001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20201214T053001Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201214T053001Z/logs MASTER_BUILD_NUMBER: 767 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20201214T053001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic PUBLISH_TIMESTAMP: 20201214T053001Z DOCKER_BUILD_ID: jenkins-master-20201214T053001Z-builder TIMESTAMP: 20201214T053001Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20201214T053001Z/inputs LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20201214T053001Z/outputs From build.starlingx at gmail.com Mon Dec 14 12:55:24 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 14 Dec 2020 07:55:24 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 767 - Failure! Message-ID: <1113425668.647.1607950525434.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 767 Status: Failure Timestamp: 20201214T053001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201214T053001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From scott.little at windriver.com Mon Dec 14 14:34:46 2020 From: scott.little at windriver.com (Scott Little) Date: Mon, 14 Dec 2020 09:34:46 -0500 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 305 - Failure! In-Reply-To: <2078774240.641.1607950509279.JavaMail.javamailuser@localhost> References: <2078774240.641.1607950509279.JavaMail.javamailuser@localhost> Message-ID: <3e2af376-39b0-7b61-48d9-c355797ce845@windriver.com> This was the monolithic build, not the layered build.  The layered build completed this step successfully. We were unable to access mirrorlist.centos.org for an extended period of time. Eventually we hit max retries and gave up. Scott On 2020-12-14 7:55 a.m., build.starlingx at gmail.com wrote: > [Please note this e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_docker_flock_images > Build #: 305 > Status: Failure > Timestamp: 20201214T092521Z > Branch: > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201214T053001Z/logs > -------------------------------------------------------------------------------- > Parameters > > WEB_HOST: mirror.starlingx.cengn.ca > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20201214T053001Z > OS: centos > MY_REPO: /localdisk/designer/jenkins/master/cgcs-root > BASE_VERSION: master-stable-20201214T053001Z > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201214T053001Z/logs > REGISTRY_USERID: slittlewrs > LATEST_PREFIX: master > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20201214T053001Z/logs > PUBLISH_TIMESTAMP: 20201214T053001Z > FLOCK_VERSION: master-centos-stable-20201214T053001Z > WEB_HOST_PORT: 80 > PREFIX: master > TIMESTAMP: 20201214T053001Z > BUILD_STREAM: stable > REGISTRY_ORG: slittlewrs > PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20201214T053001Z/outputs > REGISTRY: docker.io > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Mon Dec 14 18:57:35 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 14 Dec 2020 18:57:35 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201212T040027Z Message-ID: Sanity Test from 2020-December-12 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201212T040027Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201212T040027Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz This image is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From build.starlingx at gmail.com Mon Dec 14 19:14:52 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 14 Dec 2020 14:14:52 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1385 - Failure! Message-ID: <576903942.650.1607973293841.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1385 Status: Failure Timestamp: 20201214T191225Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201214T182618Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201214T182618Z DOCKER_BUILD_ID: jenkins-master-compiler-20201214T182618Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201214T182618Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201214T182618Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From alexandru.dimofte at intel.com Mon Dec 14 22:10:08 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 14 Dec 2020 22:10:08 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201213T023251Z Message-ID: Sanity Test from 2020-December-13 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201213T023251Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201213T023251Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz This image is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From ch.huang789 at advantech.com.tw Tue Dec 15 02:48:52 2020 From: ch.huang789 at advantech.com.tw (CH.Huang789) Date: Tue, 15 Dec 2020 02:48:52 +0000 Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Message-ID: Dear Sir: I follow the instruction to setup the StarlingX 4.0 on 2 bare metal machine with Simple AIO DX. I create one network and two cirros VM. One VM (vm0) host in controller-0, the other VM (vm1) host in controller-1. Everything looks fine on OpenStack Web UI. Each VM assigned a IP address. But only vm0 get the IP address. The vm1 do not have a IP address. Can someone help me on it? vm0: (controller-0): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:e5:76:e3 brd ff:ff:ff:ff:ff:ff inet 192.168.0.28/24 brd 192.168.0.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fee5:76e3/64 scope link valid_lft forever preferred_lft forever vm1: (controller-1): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:15:55:de brd ff:ff:ff:ff:ff:ff inet6 fe80::f816:3eff:fe15:55de/64 scope link valid_lft forever preferred_lft forever [sysadmin at controller-0 ~(keystone_admin)]$ openstack network show public-net01 +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | admin_state_up | UP | | availability_zone_hints | nova | | availability_zones | nova | | created_at | 2020-12-14T15:42:18Z | | description | | | dns_domain | None | | id | 81decfb7-ee67-466d-b644-e71d5a2b04db | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | False | | location | cloud='', project.domain_id=, project.domain_name='Default', project.id='6a2e43c744e24df89214ae72577d3ca6', project.name='admin', region_name='RegionOne', zone= | | mtu | 1500 | | name | public-net01 | | port_security_enabled | True | | project_id | 6a2e43c744e24df89214ae72577d3ca6 | | provider:network_type | vlan | | provider:physical_network | physnet0 | | provider:segmentation_id | 1000 | | qos_policy_id | None | | revision_number | 4 | | router:external | External | | segments | None | | shared | True | | status | ACTIVE | | subnets | d724cdfb-11c2-4509-805a-cf45a62fe569 | | tags | | | updated_at | 2020-12-14T15:57:26Z | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ Regards, C.H. Huang Technical Service for Advantech Cloud-IoT [advantech-logo-retina-email] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8891 bytes Desc: image001.png URL: From haochuan.z.chen at intel.com Tue Dec 15 03:07:18 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 15 Dec 2020 03:07:18 +0000 Subject: [Starlingx-discuss] check mirror status on cenga Message-ID: Hi Scott 1, why on cenga, download folder for all layer is blank now. http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/inputs/downloads/ http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/latest_build/inputs/downloads/ http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/latest_build/inputs/downloads/ http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/latest_build/inputs/downloads/ 2, the latest_build saved binary, is now target for monolithic build. Correct? http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_build/inputs/ Or now should only use mirror for layer builder http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos// Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Dec 15 05:59:36 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 15 Dec 2020 00:59:36 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1389 - Failure! Message-ID: <840461345.656.1608011977230.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1389 Status: Failure Timestamp: 20201215T055438Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201215T053001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20201215T053001Z DOCKER_BUILD_ID: jenkins-master-20201215T053001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201215T053001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20201215T053001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From Al.Bailey at windriver.com Mon Dec 14 22:55:20 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Mon, 14 Dec 2020 22:55:20 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. In-Reply-To: References: , Message-ID: The containers typically install the python components they need using wheels If the flock components are updated in their setup.cfg to be built universal wheels (which are py2 and py3 compatible) then the wheels being generated from the spec should be able to be included. That can be done in master, assuming the code runs in both py2 and py3 without needing major changes. Al ________________________________ From: Kalvala, Haridhar Sent: Monday, December 14, 2020 6:12 AM To: starlingx-discuss at lists.starlingx.io ; Wensley, Barton ; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Reminder for below request. Thank You, Haridhar Kalvala From: Kalvala, Haridhar Sent: Thursday, December 10, 2020 10:18 AM To: starlingx-discuss at lists.starlingx.io; Wensley, Barton ; Saul Wold ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada Subject: Flock components python3 migration query on master. Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein’s openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde > Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From haridhar.kalvala at intel.com Tue Dec 15 05:57:48 2020 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Tue, 15 Dec 2020 05:57:48 +0000 Subject: [Starlingx-discuss] Flock components python3 migration query on master. In-Reply-To: References: , Message-ID: Hi Henry, Thank you for response. I tried the same approach(spec and setup configuration file changes) on master branch for few flock components related with fault containerization. After changing few requires to python3, I observe below issues. Which I am not clear how to solve. Below are the few more blocker we are facing: * Starlingx-dashboard : * can't migrate python-pbr to python3-pbr. * Cephclient is throwing errors on trying to migrate to py3. * Fmclient : * Nfv components migration is a issue. So I am looking for some inputs here who have done it earlier. Sample error log: INFO: pip is looking at multiple versions of horizon to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of distributedcloud-client to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of coverage to determine which version is compatible with other requirements. This could take a while. INFO: pip is looking at multiple versions of cgtsclient to determine which version is compatible with other requirements. This could take a while. ^[[91mERROR: Cannot install pylint==1.4.0, pylint==1.4.1, pylint==1.4.2, pylint==1.4.3, pylint==1.4.4 and pylint==1.4.5 because these package versions have conflicting dependencies. ^[[0m The conflict is caused by: pylint 1.4.5 depends on logilab-common>=0.53.0 pylint 1.4.4 depends on logilab-common>=0.53.0 pylint 1.4.3 depends on logilab-common>=0.53.0 pylint 1.4.2 depends on logilab-common>=0.53.0 pylint 1.4.1 depends on logilab-common>=0.53.0 pylint 1.4.0 depends on logilab-common>=0.53.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip attempt to solve the dependency conflict ^[[91mERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies ^[[0m^[[91mWARNING: You are using pip version 20.3.1; however, version 20.3.2 is available. You should consider upgrading via the '/var/lib/openstack/bin/python -m pip install --upgrade pip' command. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. Max command attempts reached. Aborting... Thank you, Haridhar Kalvala From: Bailey, Henry Albert (Al) Sent: Tuesday, December 15, 2020 4:25 AM To: Kalvala, Haridhar ; starlingx-discuss at lists.starlingx.io; Wensley, Barton ; Wold, Saul ; Jones, Bruce E ; Sun, Austin Cc: Mukherjee, Sanjay K ; Kumar, Sharath ; Bhat, Gopalkrishna ; Khalil, Ghada Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. The containers typically install the python components they need using wheels If the flock components are updated in their setup.cfg to be built universal wheels (which are py2 and py3 compatible) then the wheels being generated from the spec should be able to be included. That can be done in master, assuming the code runs in both py2 and py3 without needing major changes. Al ________________________________ From: Kalvala, Haridhar > Sent: Monday, December 14, 2020 6:12 AM To: starlingx-discuss at lists.starlingx.io >; Wensley, Barton >; Wold, Saul >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Re: [Starlingx-discuss] Flock components python3 migration query on master. [Please note this e-mail is from an EXTERNAL e-mail address] Reminder for below request. Thank You, Haridhar Kalvala From: Kalvala, Haridhar Sent: Thursday, December 10, 2020 10:18 AM To: starlingx-discuss at lists.starlingx.io; Wensley, Barton >; Saul Wold >; Jones, Bruce E >; Sun, Austin > Cc: Mukherjee, Sanjay K >; Kumar, Sharath >; Bhat, Gopalkrishna >; Khalil, Ghada > Subject: Flock components python3 migration query on master. Hello All, We are working on FM containerization (FM panel in open stack dashboard and backend pod service(fault)). As part of this activity, we are doing stx-horizon docker build. Which will include components from flock (for fm calls). As a reference example, please refer to this patch. The front panel would be calling flock components fmclient, cgtsclient, distributedcloud etc. These components are python2 build. For FM panel to work we need migration of these components (seeing lot of dependency issues) from python2 to python3 on master branch. Yesterday(9-Dec-2020) in non-openstack distro meeting, the discussion was flock python2 dependent components cannot be migrated in master branch and will done in centos8 migration branch/stream. So, I request for clarity/decision from community on this blocker for FM containerization. Earlier in stx-3.0(stein's openstack) as in above link, these component were part of stx-horizon docker build. But these were removed(as per patch below) as part of stx-4.0 migration (stein -->train --> Ussuri), as latest openstack only supports python3. Patch details: commit b8b897a028cda3936f17c5ac6b73af146c5de96b (tag: v4.0.0.rc0) Author: yuchengde > Depends-on: https://review.opendev.org/#/c/731461/ Change-Id: I415ea75eb24d8b1c3151b63efd2e82075e68f26e Signed-off-by: Yu Chengde yu.chengde at 99cloud.com Thank you, Haridhar Kalvala -------------- next part -------------- An HTML attachment was scrubbed... URL: From Sriram.Dharwadkar at commscope.com Tue Dec 15 07:49:47 2020 From: Sriram.Dharwadkar at commscope.com (Dharwadkar, Sriram) Date: Tue, 15 Dec 2020 07:49:47 +0000 Subject: [Starlingx-discuss] [Distributed StarlingX 4.0] Running testpmd application in StarlingX Message-ID: Hi, I have installed starlingX in All in One Duplex Low latency configuration in edge cloud. Below is the build detail. controller-0:~$ cat /etc/build.info ### ### StarlingX ### Release 20.06 ### OS="centos" SW_VERSION="20.06" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="r/stx.4.0" JOB="STX_4.0_build_layer_flock" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="22" BUILD_HOST="starlingx_mirror" BUILD_DATE="2020-08-05 12:25:52 +0000" FLOCK_OS="centos" FLOCK_JOB="STX_4.0_build_layer_flock" FLOCK_BUILD_BY="starlingx.build at cengn.ca" FLOCK_BUILD_NUMBER="22" FLOCK_BUILD_HOST="starlingx_mirror" FLOCK_BUILD_DATE="2020-08-05 12:25:52 +0000" Servers on which starlingx is installed have Mellanox ConnectX-4 NIC. We plan to run dpdk applications making use of vf's created out of this NIC. For this purpose I ran test pmd application, but got the below error. controller-1:~$ sudo ./testpmd -l 0-3 -n 4 -- -i --portmask=0x1 --nb-cores=2 Password: ./testpmd: /lib64/libmlx5.so.1: version `MLX5_OFED' not found (required by ./testpmd) I have compiled testpmd application using OFED 5.1 version. Please let me know how to get testpmd working in StarlingX setup. Regards, Sriram -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Dec 15 07:58:49 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 15 Dec 2020 07:58:49 +0000 Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 In-Reply-To: References: Message-ID: Hi Huang: Would you check ? system host-if-list controller-1 ? and the NIC assigned as data network in controller-1 is up ? Thanks. BR Austin Sun. From: CH.Huang789 Sent: Tuesday, December 15, 2020 10:49 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Dear Sir: I follow the instruction to setup the StarlingX 4.0 on 2 bare metal machine with Simple AIO DX. I create one network and two cirros VM. One VM (vm0) host in controller-0, the other VM (vm1) host in controller-1. Everything looks fine on OpenStack Web UI. Each VM assigned a IP address. But only vm0 get the IP address. The vm1 do not have a IP address. Can someone help me on it? vm0: (controller-0): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:e5:76:e3 brd ff:ff:ff:ff:ff:ff inet 192.168.0.28/24 brd 192.168.0.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fee5:76e3/64 scope link valid_lft forever preferred_lft forever vm1: (controller-1): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:15:55:de brd ff:ff:ff:ff:ff:ff inet6 fe80::f816:3eff:fe15:55de/64 scope link valid_lft forever preferred_lft forever [sysadmin at controller-0 ~(keystone_admin)]$ openstack network show public-net01 +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | admin_state_up | UP | | availability_zone_hints | nova | | availability_zones | nova | | created_at | 2020-12-14T15:42:18Z | | description | | | dns_domain | None | | id | 81decfb7-ee67-466d-b644-e71d5a2b04db | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | False | | location | cloud='', project.domain_id=, project.domain_name='Default', project.id='6a2e43c744e24df89214ae72577d3ca6', project.name='admin', region_name='RegionOne', zone= | | mtu | 1500 | | name | public-net01 | | port_security_enabled | True | | project_id | 6a2e43c744e24df89214ae72577d3ca6 | | provider:network_type | vlan | | provider:physical_network | physnet0 | | provider:segmentation_id | 1000 | | qos_policy_id | None | | revision_number | 4 | | router:external | External | | segments | None | | shared | True | | status | ACTIVE | | subnets | d724cdfb-11c2-4509-805a-cf45a62fe569 | | tags | | | updated_at | 2020-12-14T15:57:26Z | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ Regards, C.H. Huang Technical Service for Advantech Cloud-IoT [advantech-logo-retina-email] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8891 bytes Desc: image001.png URL: From ch.huang789 at advantech.com.tw Tue Dec 15 08:08:54 2020 From: ch.huang789 at advantech.com.tw (CH.Huang789) Date: Tue, 15 Dec 2020 08:08:54 +0000 Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 In-Reply-To: References: Message-ID: Hi Austin: I loop back eno2 for these 2 servers. Yes, it link up on controller-1. [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-1 +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ | 5cda648c-1c8e-4acc-8661-d8cc10b6f790 | eno7 | platform | ethernet | None | [u'eno7'] | [] | [] | MTU=1500 | | 811ec9ed-cbdc-40ec-b18d-82dd54ad40c5 | data0 | data | ethernet | None | [u'eno2'] | [] | [] | MTU=1500,accelerated=True | | b421709e-3048-44e7-b91f-aeb7de3dac0f | eno5 | platform | ethernet | None | [u'eno5'] | [] | [] | MTU=1500 | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ ssh controller-1 controller-1:~$ ip link show eno2 3: eno2: mtu 1500 qdisc mq master ovs-system state UP mode DEFAULT group default qlen 1000 link/ether 00:d0:c9:cc:33:1d brd ff:ff:ff:ff:ff:ff Regards, C.H. Huang Technical Service for Advantech Cloud-IoT From: Sun, Austin Sent: Tuesday, December 15, 2020 3:59 PM To: CH.Huang789 ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Huang: Would you check ? system host-if-list controller-1 ? and the NIC assigned as data network in controller-1 is up ? Thanks. BR Austin Sun. From: CH.Huang789 > Sent: Tuesday, December 15, 2020 10:49 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Dear Sir: I follow the instruction to setup the StarlingX 4.0 on 2 bare metal machine with Simple AIO DX. I create one network and two cirros VM. One VM (vm0) host in controller-0, the other VM (vm1) host in controller-1. Everything looks fine on OpenStack Web UI. Each VM assigned a IP address. But only vm0 get the IP address. The vm1 do not have a IP address. Can someone help me on it? vm0: (controller-0): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:e5:76:e3 brd ff:ff:ff:ff:ff:ff inet 192.168.0.28/24 brd 192.168.0.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fee5:76e3/64 scope link valid_lft forever preferred_lft forever vm1: (controller-1): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:15:55:de brd ff:ff:ff:ff:ff:ff inet6 fe80::f816:3eff:fe15:55de/64 scope link valid_lft forever preferred_lft forever [sysadmin at controller-0 ~(keystone_admin)]$ openstack network show public-net01 +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | admin_state_up | UP | | availability_zone_hints | nova | | availability_zones | nova | | created_at | 2020-12-14T15:42:18Z | | description | | | dns_domain | None | | id | 81decfb7-ee67-466d-b644-e71d5a2b04db | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | False | | location | cloud='', project.domain_id=, project.domain_name='Default', project.id='6a2e43c744e24df89214ae72577d3ca6', project.name='admin', region_name='RegionOne', zone= | | mtu | 1500 | | name | public-net01 | | port_security_enabled | True | | project_id | 6a2e43c744e24df89214ae72577d3ca6 | | provider:network_type | vlan | | provider:physical_network | physnet0 | | provider:segmentation_id | 1000 | | qos_policy_id | None | | revision_number | 4 | | router:external | External | | segments | None | | shared | True | | status | ACTIVE | | subnets | d724cdfb-11c2-4509-805a-cf45a62fe569 | | tags | | | updated_at | 2020-12-14T15:57:26Z | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ Regards, C.H. Huang Technical Service for Advantech Cloud-IoT [advantech-logo-retina-email] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8891 bytes Desc: image001.png URL: From build.starlingx at gmail.com Tue Dec 15 10:48:24 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 15 Dec 2020 05:48:24 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_download_mirror - Build # 1094 - Failure! Message-ID: <317155369.660.1608029304947.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1094 Status: Failure Timestamp: 20201215T102213Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201215T100001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/centos8 DOCKER_BUILD_ID: jenkins-f-centos8-20201215T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201215T100001Z/logs MY_REPO: /localdisk/designer/jenkins/f-centos8/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201215T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Tue Dec 15 10:48:26 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 15 Dec 2020 05:48:26 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 58 - Still Failing! In-Reply-To: null References: null Message-ID: <2074715397.663.1608029307434.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 58 Status: Still Failing Timestamp: 20201215T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201215T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From alexandru.dimofte at intel.com Tue Dec 15 16:22:02 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 15 Dec 2020 16:22:02 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201214T201638Z Message-ID: Sanity Test from 2020-December-14 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201214T201638Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201214T201638Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz This image is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Tue Dec 15 16:24:16 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 15 Dec 2020 16:24:16 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201215T033558Z Message-ID: Sanity Test from 2020-December-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201215T033558Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201214T201638Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Obs: We used the helm-charts from previous build because the helm-charts from current build were not generated. This image is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From bruce.e.jones at intel.com Tue Dec 15 17:11:20 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 15 Dec 2020 17:11:20 +0000 Subject: [Starlingx-discuss] Lenix - new version of CentOS.... Message-ID: FYI - CloudLinux has announced a new open source project that looks a lot like CentOS. https://www.zdnet.com/article/cloudlinux-to-invest-more-than-a-million-dollar-a-year-into-centos-clone/ brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Tue Dec 15 18:15:38 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 15 Dec 2020 18:15:38 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 16, 2020) Message-ID: Hi all, reminder of tomorrow's TSC/Community call. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201216T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From build.starlingx at gmail.com Tue Dec 15 20:36:22 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 15 Dec 2020 15:36:22 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_publish_success - Build # 1 - Failure! Message-ID: <909989013.666.1608064582795.JavaMail.javamailuser@localhost> Project: STX_publish_success Build #: 1 Status: Failure Timestamp: 20201215T203620Z Branch: Check logs at: https://127.0.0.1/ -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: OS: centos PUBLISH_LOGS_URL: https://127.0.0.1/ RETRIES: 13 PUBLISH_LOGS_BASE: /tmp/logs MASTER_JOB_NAME: RETRY_INTERVAL_SEC: 300 MY_REPO_ROOT: PUBLISH_DISTRO_BASE: TIMESTAMP: PUBLISH_INPUTS_BASE: LAYER: PUBLISH_OUTPUTS_BASE: From build.starlingx at gmail.com Tue Dec 15 20:36:24 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 15 Dec 2020 15:36:24 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 390 - Failure! Message-ID: <1831980080.669.1608064585279.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 390 Status: Failure Timestamp: 20201215T203513Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201215T203513Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Tue Dec 15 20:59:55 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 15 Dec 2020 15:59:55 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_publish_success - Build # 2 - Still Failing! In-Reply-To: <1085824900.664.1608064580570.JavaMail.javamailuser@localhost> References: <1085824900.664.1608064580570.JavaMail.javamailuser@localhost> Message-ID: <2067205951.673.1608065996505.JavaMail.javamailuser@localhost> Project: STX_publish_success Build #: 2 Status: Still Failing Timestamp: 20201215T205954Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201215T205902Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201215T205902Z OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201215T205902Z/logs RETRIES: 13 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201215T205902Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master RETRY_INTERVAL_SEC: 300 MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler TIMESTAMP: 20201215T205902Z PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/compiler/20201215T205902Z/inputs LAYER: compiler PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/compiler/20201215T205902Z/outputs From build.starlingx at gmail.com Tue Dec 15 20:59:58 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 15 Dec 2020 15:59:58 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 391 - Still Failing! In-Reply-To: <1089597033.667.1608064583412.JavaMail.javamailuser@localhost> References: <1089597033.667.1608064583412.JavaMail.javamailuser@localhost> Message-ID: <895458237.676.1608065998746.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 391 Status: Still Failing Timestamp: 20201215T205902Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201215T205902Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Wed Dec 16 03:58:12 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 15 Dec 2020 22:58:12 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 307 - Failure! Message-ID: <1342021047.681.1608091094158.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 307 Status: Failure Timestamp: 20201215T234738Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201215T223645Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201215T223645Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20201215T223645Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201215T223645Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201215T223645Z/logs PUBLISH_TIMESTAMP: 20201215T223645Z FLOCK_VERSION: master-centos-stable-20201215T223645Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20201215T223645Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201215T223645Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Wed Dec 16 03:58:16 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 15 Dec 2020 22:58:16 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 70 - Failure! Message-ID: <157114055.684.1608091096662.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 70 Status: Failure Timestamp: 20201215T232849Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201215T223645Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20201215T223645Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201215T223645Z/logs MASTER_BUILD_NUMBER: 93 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20201215T223645Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20201215T223645Z DOCKER_BUILD_ID: jenkins-master-containers-20201215T223645Z-builder TIMESTAMP: 20201215T223645Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201215T223645Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20201215T223645Z/outputs From build.starlingx at gmail.com Wed Dec 16 03:58:18 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 15 Dec 2020 22:58:18 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 93 - Failure! Message-ID: <1765683755.687.1608091098948.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 93 Status: Failure Timestamp: 20201215T223645Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201215T223645Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From bnovickovs at weecodelab.com Wed Dec 16 04:18:06 2020 From: bnovickovs at weecodelab.com (bnovickovs at weecodelab.com) Date: Wed, 16 Dec 2020 04:18:06 +0000 Subject: [Starlingx-discuss] CNI Chaining Message-ID: <888375fab02908481d172e435e44ab45@weecodelab.com> Hi STX community, I ve been aware that Calico shall be used as the main CNI in Stx deployments. However, I am wondering what would be your opinion of using Cilium CNI chaining in conjunction with Calico - https://docs.cilium.io/en/v1.9/gettingstarted/cni-chaining-calico/ which would give “ With Cilium CNI chaining, the base network connectivity and IP address management is managed by the non-Cilium CNI plugin, but Cilium attaches eBPF programs to the network devices created by the non-Cilium plugin to provide L3/L4/L7 network visibility & policy enforcement and other advanced features like transparent encryption.” Do you think it’s safe enough and good practice overall to mix it up this way or it’s better to avoid doing it? Thank you Regards From parkeryan at tencent.com Wed Dec 16 07:53:14 2020 From: parkeryan at tencent.com (=?gb2312?B?cGFya2VyeWFuKOPG1r693Ck=?=) Date: Wed, 16 Dec 2020 07:53:14 +0000 Subject: [Starlingx-discuss] Openstack application can not be deployed on some compute nodes. Message-ID: <952cb11639c64d758807f7fb2504de52@tencent.com> Hello, all. I deployed StarlingX 2.0 on bare metal standard with controller storage, and got some problems while applying stx-openstack application. Here is the details. [sysadmin at controller-0 log(keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 18 | controller-1 | controller | unlocked | enabled | available | | 19 | compute-0 | worker | unlocked | enabled | available | | 20 | compute-1 | worker | unlocked | enabled | available | | 21 | compute-2 | worker | unlocked | enabled | available | | 22 | compute-3 | worker | unlocked | enabled | available | | 23 | compute-4 | worker | unlocked | enabled | available | | 24 | compute-5 | worker | unlocked | enabled | available | | 25 | compute-6 | worker | unlocked | enabled | available | | 26 | compute-7 | worker | unlocked | enabled | available | | 27 | compute-8 | worker | unlocked | enabled | available | | 29 | compute-10 | worker | unlocked | enabled | available | | 30 | compute-11 | worker | unlocked | enabled | available | | 32 | compute-12 | worker | unlocked | enabled | available | | 33 | compute-13 | worker | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ And I labed all compute nodes to support openstack application. [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-0 +-----------+------------------------+-------------+ | hostname | label key | label value | +-----------+------------------------+-------------+ | compute-0 | openstack-compute-node | enabled | | compute-0 | openvswitch | enabled | | compute-0 | sriov | enabled | | compute-0 | sriovdp | enabled | +-----------+------------------------+-------------+ [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-1 +-----------+------------------------+-------------+ | hostname | label key | label value | +-----------+------------------------+-------------+ | compute-1 | openstack-compute-node | enabled | | compute-1 | openvswitch | enabled | | compute-1 | sriov | enabled | | compute-1 | sriovdp | enabled | +-----------+------------------------+-------------+ [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-2 +-----------+------------------------+-------------+ | hostname | label key | label value | +-----------+------------------------+-------------+ | compute-2 | openstack-compute-node | enabled | | compute-2 | openvswitch | enabled | | compute-2 | sriov | enabled | | compute-2 | sriovdp | enabled | +-----------+------------------------+-------------+ [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-3 +-----------+------------------------+-------------+ | hostname | label key | label value | +-----------+------------------------+-------------+ | compute-3 | openstack-compute-node | enabled | | compute-3 | openvswitch | enabled | | compute-3 | sriov | enabled | | compute-3 | sriovdp | enabled | +-----------+------------------------+-------------+ [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-12 +------------+------------------------+-------------+ | hostname | label key | label value | +------------+------------------------+-------------+ | compute-12 | openstack-compute-node | enabled | | compute-12 | openvswitch | enabled | | compute-12 | sriov | enabled | | compute-12 | sriovdp | enabled | +------------+------------------------+-------------+ [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-13 +------------+------------------------+-------------+ | hostname | label key | label value | +------------+------------------------+-------------+ | compute-13 | openstack-compute-node | enabled | | compute-13 | openvswitch | enabled | | compute-13 | sriov | enabled | | compute-13 | sriovdp | enabled | +------------+------------------------+-------------+ However, I found some of them didn’t take effect by openstack host list command. controller-0:~$ openstack host list +----------------------------------+-------------+----------+ | Host Name | Service | Zone | +----------------------------------+-------------+----------+ | nova-consoleauth-d54b6864c-r78q8 | consoleauth | internal | | nova-conductor-855dff79f-rltf4 | conductor | internal | | nova-consoleauth-d54b6864c-78nkh | consoleauth | internal | | nova-conductor-855dff79f-9kn2j | conductor | internal | | nova-scheduler-6554b9c6bb-hqmw2 | scheduler | internal | | nova-scheduler-6554b9c6bb-nzjfl | scheduler | internal | | compute-5 | compute | nova | | compute-8 | compute | nova | | compute-4 | compute | nova | | compute-11 | compute | nova | | compute-7 | compute | nova | | compute-1 | compute | nova | | compute-6 | compute | nova | | compute-0 | compute | nova | | compute-10 | compute | nova | +----------------------------------+-------------+----------+ From which I found compute-2, compute-3, compute-12 and compute-13 is nod displayed in openstack host. I wonder how to solve the problem, and is there some logs can help to determine what happedn to these compute nodes. Thanks in advance. Best regards parkeryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Dec 16 09:57:47 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 16 Dec 2020 09:57:47 +0000 Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 In-Reply-To: References: Message-ID: Hi Huang: are datanetwork NIC on controller-0 and controller-1 connected to each other or in same switch/network ? Thanks. BR Austin Sun. From: CH.Huang789 Sent: Tuesday, December 15, 2020 4:09 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Austin: I loop back eno2 for these 2 servers. Yes, it link up on controller-1. [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-1 +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ | 5cda648c-1c8e-4acc-8661-d8cc10b6f790 | eno7 | platform | ethernet | None | [u'eno7'] | [] | [] | MTU=1500 | | 811ec9ed-cbdc-40ec-b18d-82dd54ad40c5 | data0 | data | ethernet | None | [u'eno2'] | [] | [] | MTU=1500,accelerated=True | | b421709e-3048-44e7-b91f-aeb7de3dac0f | eno5 | platform | ethernet | None | [u'eno5'] | [] | [] | MTU=1500 | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ ssh controller-1 controller-1:~$ ip link show eno2 3: eno2: mtu 1500 qdisc mq master ovs-system state UP mode DEFAULT group default qlen 1000 link/ether 00:d0:c9:cc:33:1d brd ff:ff:ff:ff:ff:ff Regards, C.H. Huang Technical Service for Advantech Cloud-IoT From: Sun, Austin > Sent: Tuesday, December 15, 2020 3:59 PM To: CH.Huang789 >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Huang: Would you check ? system host-if-list controller-1 ? and the NIC assigned as data network in controller-1 is up ? Thanks. BR Austin Sun. From: CH.Huang789 > Sent: Tuesday, December 15, 2020 10:49 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Dear Sir: I follow the instruction to setup the StarlingX 4.0 on 2 bare metal machine with Simple AIO DX. I create one network and two cirros VM. One VM (vm0) host in controller-0, the other VM (vm1) host in controller-1. Everything looks fine on OpenStack Web UI. Each VM assigned a IP address. But only vm0 get the IP address. The vm1 do not have a IP address. Can someone help me on it? vm0: (controller-0): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:e5:76:e3 brd ff:ff:ff:ff:ff:ff inet 192.168.0.28/24 brd 192.168.0.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fee5:76e3/64 scope link valid_lft forever preferred_lft forever vm1: (controller-1): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:15:55:de brd ff:ff:ff:ff:ff:ff inet6 fe80::f816:3eff:fe15:55de/64 scope link valid_lft forever preferred_lft forever [sysadmin at controller-0 ~(keystone_admin)]$ openstack network show public-net01 +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | admin_state_up | UP | | availability_zone_hints | nova | | availability_zones | nova | | created_at | 2020-12-14T15:42:18Z | | description | | | dns_domain | None | | id | 81decfb7-ee67-466d-b644-e71d5a2b04db | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | False | | location | cloud='', project.domain_id=, project.domain_name='Default', project.id='6a2e43c744e24df89214ae72577d3ca6', project.name='admin', region_name='RegionOne', zone= | | mtu | 1500 | | name | public-net01 | | port_security_enabled | True | | project_id | 6a2e43c744e24df89214ae72577d3ca6 | | provider:network_type | vlan | | provider:physical_network | physnet0 | | provider:segmentation_id | 1000 | | qos_policy_id | None | | revision_number | 4 | | router:external | External | | segments | None | | shared | True | | status | ACTIVE | | subnets | d724cdfb-11c2-4509-805a-cf45a62fe569 | | tags | | | updated_at | 2020-12-14T15:57:26Z | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ Regards, C.H. Huang Technical Service for Advantech Cloud-IoT [advantech-logo-retina-email] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8891 bytes Desc: image001.png URL: From ch.huang789 at advantech.com.tw Wed Dec 16 10:00:34 2020 From: ch.huang789 at advantech.com.tw (CH.Huang789) Date: Wed, 16 Dec 2020 10:00:34 +0000 Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 In-Reply-To: References: Message-ID: <562227acd98e423e822317ec250e7ddf@taipei09.ADVANTECH.CORP> Dear Austin: Datanetwork NIC on controller-0 and controller-1 connected to each other. Regards, C.H. Huang Technical Service for Advantech Cloud-IoT From: Sun, Austin Sent: Wednesday, December 16, 2020 5:58 PM To: CH.Huang789 ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Huang: are datanetwork NIC on controller-0 and controller-1 connected to each other or in same switch/network ? Thanks. BR Austin Sun. From: CH.Huang789 > Sent: Tuesday, December 15, 2020 4:09 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Austin: I loop back eno2 for these 2 servers. Yes, it link up on controller-1. [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-1 +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ | 5cda648c-1c8e-4acc-8661-d8cc10b6f790 | eno7 | platform | ethernet | None | [u'eno7'] | [] | [] | MTU=1500 | | 811ec9ed-cbdc-40ec-b18d-82dd54ad40c5 | data0 | data | ethernet | None | [u'eno2'] | [] | [] | MTU=1500,accelerated=True | | b421709e-3048-44e7-b91f-aeb7de3dac0f | eno5 | platform | ethernet | None | [u'eno5'] | [] | [] | MTU=1500 | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ ssh controller-1 controller-1:~$ ip link show eno2 3: eno2: mtu 1500 qdisc mq master ovs-system state UP mode DEFAULT group default qlen 1000 link/ether 00:d0:c9:cc:33:1d brd ff:ff:ff:ff:ff:ff Regards, C.H. Huang Technical Service for Advantech Cloud-IoT From: Sun, Austin > Sent: Tuesday, December 15, 2020 3:59 PM To: CH.Huang789 >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Huang: Would you check ? system host-if-list controller-1 ? and the NIC assigned as data network in controller-1 is up ? Thanks. BR Austin Sun. From: CH.Huang789 > Sent: Tuesday, December 15, 2020 10:49 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Dear Sir: I follow the instruction to setup the StarlingX 4.0 on 2 bare metal machine with Simple AIO DX. I create one network and two cirros VM. One VM (vm0) host in controller-0, the other VM (vm1) host in controller-1. Everything looks fine on OpenStack Web UI. Each VM assigned a IP address. But only vm0 get the IP address. The vm1 do not have a IP address. Can someone help me on it? vm0: (controller-0): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:e5:76:e3 brd ff:ff:ff:ff:ff:ff inet 192.168.0.28/24 brd 192.168.0.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fee5:76e3/64 scope link valid_lft forever preferred_lft forever vm1: (controller-1): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:15:55:de brd ff:ff:ff:ff:ff:ff inet6 fe80::f816:3eff:fe15:55de/64 scope link valid_lft forever preferred_lft forever [sysadmin at controller-0 ~(keystone_admin)]$ openstack network show public-net01 +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | admin_state_up | UP | | availability_zone_hints | nova | | availability_zones | nova | | created_at | 2020-12-14T15:42:18Z | | description | | | dns_domain | None | | id | 81decfb7-ee67-466d-b644-e71d5a2b04db | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | False | | location | cloud='', project.domain_id=, project.domain_name='Default', project.id='6a2e43c744e24df89214ae72577d3ca6', project.name='admin', region_name='RegionOne', zone= | | mtu | 1500 | | name | public-net01 | | port_security_enabled | True | | project_id | 6a2e43c744e24df89214ae72577d3ca6 | | provider:network_type | vlan | | provider:physical_network | physnet0 | | provider:segmentation_id | 1000 | | qos_policy_id | None | | revision_number | 4 | | router:external | External | | segments | None | | shared | True | | status | ACTIVE | | subnets | d724cdfb-11c2-4509-805a-cf45a62fe569 | | tags | | | updated_at | 2020-12-14T15:57:26Z | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ Regards, C.H. Huang Technical Service for Advantech Cloud-IoT [advantech-logo-retina-email] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8891 bytes Desc: image001.png URL: From build.starlingx at gmail.com Wed Dec 16 10:49:00 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 16 Dec 2020 05:49:00 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_download_mirror - Build # 1096 - Failure! Message-ID: <1369311438.691.1608115740992.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1096 Status: Failure Timestamp: 20201216T102419Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201216T100001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/centos8 DOCKER_BUILD_ID: jenkins-f-centos8-20201216T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201216T100001Z/logs MY_REPO: /localdisk/designer/jenkins/f-centos8/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201216T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Wed Dec 16 10:49:02 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 16 Dec 2020 05:49:02 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 59 - Still Failing! In-Reply-To: <194870042.661.1608029305542.JavaMail.javamailuser@localhost> References: <194870042.661.1608029305542.JavaMail.javamailuser@localhost> Message-ID: <99488961.694.1608115743232.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 59 Status: Still Failing Timestamp: 20201216T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201216T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From scott.little at windriver.com Wed Dec 16 14:42:08 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 16 Dec 2020 09:42:08 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 93 - Failure! In-Reply-To: <1765683755.687.1608091098948.JavaMail.javamailuser@localhost> References: <1765683755.687.1608091098948.JavaMail.javamailuser@localhost> Message-ID: <3e08ba6a-70a6-3f94-0846-328a446a09aa@windriver.com> Failed to build containers ... rvmc stx-fm-subagent stx-libvirt stx-nova-api-proxy stx-oidc-client ... because rpms are missing from the published artifacts of a lower layer build. I am investigating. Scott On 2020-12-15 10:58 p.m., build.starlingx at gmail.com wrote: > [Please note this e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_containers_master_master > Build #: 93 > Status: Failure > Timestamp: 20201215T223645Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201215T223645Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Dec 16 14:47:32 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 16 Dec 2020 09:47:32 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 93 - Failure! In-Reply-To: <3e08ba6a-70a6-3f94-0846-328a446a09aa@windriver.com> References: <1765683755.687.1608091098948.JavaMail.javamailuser@localhost> <3e08ba6a-70a6-3f94-0846-328a446a09aa@windriver.com> Message-ID: <5e74b5a3-e133-ea46-f4a0-845670d10d7e@windriver.com> Actually that repo really is empty the fatal error was actually ... Could not resolve host: mirrorlist.centos.org; Unknown error" On 2020-12-16 9:42 a.m., Scott Little wrote: > Failed to build containers ... > > rvmc > > stx-fm-subagent > > stx-libvirt > > stx-nova-api-proxy > > stx-oidc-client > > ... because rpms are missing from the published artifacts of a lower > layer build. > > I am investigating. > > Scott > > On 2020-12-15 10:58 p.m., build.starlingx at gmail.com wrote: >> [Please note this e-mail is from an EXTERNAL e-mail address] >> >> Project: STX_build_layer_containers_master_master >> Build #: 93 >> Status: Failure >> Timestamp: 20201215T223645Z >> Branch: master >> >> Check logs at: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20201215T223645Z/logs >> -------------------------------------------------------------------------------- >> Parameters >> >> BUILD_CONTAINERS_DEV: false >> BUILD_CONTAINERS_STABLE: true >> FORCE_BUILD: false >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From anyrude10 at gmail.com Wed Dec 16 14:54:00 2020 From: anyrude10 at gmail.com (Anirudh Gupta) Date: Wed, 16 Dec 2020 20:24:00 +0530 Subject: [Starlingx-discuss] StarlingX 4.0 Issue in Extending XFS Filesystem Message-ID: Hi Team, We are Installing StarlingX 4.0 and facing an issue which is related to the below bug: https://bugs.launchpad.net/starlingx/+bug/1904973 We have Raid 5 configuration at our setup on which STX 4.0 is installed. While extending the XFS filesystem for docker-lv before uploading stx-openstack application https://docs.starlingx.io/deploy_install_guides/r4_release/openstack/install.html Command: *system host-fs-modify controller-0 docker=60* As we run this command, we get kernel alert logs in */var/log/kern.log/* 2020-12-16T13:23:40.467 controller-0 kernel: alert [ 921.174512] XFS (dm-5): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x77fc002 len 1 error 74 2020-12-16T13:23:41.715 controller-0 kernel: alert [ 922.488879] XFS (dm-5): Metadata CRC error detected at xfs_agi_read_verify+0xd0/0xf0 [xfs], xfs_agi block 0x77fc002 2020-12-16T13:23:41.715 controller-0 kernel: alert [ 922.498188] XFS (dm-5): Unmount and run xfs_repair 2020-12-16T13:23:41.715 controller-0 kernel: alert [ 922.507214] XFS (dm-5): First 128 bytes of corrupted metadata buffer: 2020-12-16T13:23:41.809 controller-0 kernel: alert [ 922.516545] 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2020-12-16T13:23:41.809 controller-0 kernel: alert [ 922.516547] 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2020-12-16T13:23:41.809 controller-0 kernel: alert [ 922.516548] 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2020-12-16T13:23:41.809 controller-0 kernel: alert [ 922.516549] 00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2020-12-16T13:23:41.809 controller-0 kernel: alert [ 922.516551] 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2020-12-16T13:23:41.809 controller-0 kernel: alert [ 922.516552] 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2020-12-16T13:23:41.809 controller-0 kernel: alert [ 922.516553] 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2020-12-16T13:23:41.809 controller-0 kernel: alert [ 922.516555] 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ In order to avoid this, we thought to initially set the size of docker-lv filesystem to 60 instead of increasing it from 30 to 60 For this, before bootstrap C0, we changed the following: 1. lv_size changed from 30 to 60 in file */usr/share/puppet/modules/platform/manifests/filesystem.pp* class platform::filesystem::docker::params::bootstrap ( $lv_size = '*60*', $lv_name = 'docker-lv', $mountpoint = '/var/lib/docker', $devmapper = '/dev/mapper/cgts--vg-docker--lv', $fs_type = 'xfs', $fs_options = '-n ftype=1', $fs_use_all = false ) { } 2. Value of KUBERNETES_DOCKER_STOR_SIZE at line 39 changed to 60 from 30 in file */usr/lib64/python2.7/site-packages/sysinv/common/constants.py* KUBERNETES_DOCKER_STOR_SIZE = *60* With these changes, after bootstrap of Controller-0, the size of docker-lv changes to 60 successfully. The same is verified running the command "system host-fs-list controller-0" But once Controller-1 bootstraps and comes up, we still get the size of docker-lv as 30. Since Controller-0 PXE boots Controller-1, there must be a file at C0 which we could change so that Controller-1's docker-lv gets a size of 60G. We are unable to find such a file and would require help in order to resolve this. Regards Anirudh Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Dec 16 15:07:34 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 16 Dec 2020 15:07:34 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Networking Sub-Project Meeting (bi-weekly) Message-ID: Cancelling for the Christmas/New Year holidays. Re-sending with new zoom link Bi-weekly on Thursday 0615 PT / 0915 ET Zoom Link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-networking Networking team wiki: https://wiki.openstack.org/wiki/StarlingX/Networking -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2526 bytes Desc: not available URL: From Ghada.Khalil at windriver.com Wed Dec 16 15:11:50 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 16 Dec 2020 15:11:50 +0000 Subject: [Starlingx-discuss] Canceled: Bi-weekly StarlingX Release Meeting (new time) Message-ID: Cancelling for the Christmas/New Year holidays. New meeting series for the StarlingX Release Meeting Bi-weekly meeting on Wednesday 06:30AM PT / 09:30AM ET / 02:30PM UTC Zoom Link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2109 bytes Desc: not available URL: From bruce.e.jones at intel.com Wed Dec 16 15:15:51 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 16 Dec 2020 15:15:51 +0000 Subject: [Starlingx-discuss] TSC call Dec 16 2020 Message-ID: 12/16/2020 * Last TSC meeting of the year. Resuming them January 6th. * Some meetings may continue, up to each team (e.g. Multi-OS call will happen next week) * No specs outstanding * No open governance reviews * How do we want to figure out our CentOS strategy? * Distro team TL (Saul) to lead option gathering and analysis. * Need help from the community e.g. install/updates, ceph, etc... * Consider both short term (2021) and long term solutions * Will use the Multi-OS meeting to gather data * Report back to TSC Jan 6th -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Dec 16 15:39:16 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 16 Dec 2020 15:39:16 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 16, 2020) In-Reply-To: References: Message-ID: >From today's meeting, below. We'll have our next meeting on Jan 6, 2021 - see you next year! Bill... * Standing Topics * Sanity * per Scott, there was one issue w/ build tools, fixed now, and also some intermittent issues w/ the DNS resolver (Google's) - Scott will try to provide some DNS redundancy to address the 2nd issue * Gerrit Reviews in Need of Attention * rook features https://review.opendev.org/q/topic:%22ceph+containerization%22+(status:open%20OR%20status:merged) config/ha/puppet/ansible-playbook/metal/openstack-armada-application * Topics for this Week * Outreachy internship program: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010344.html * find more information about the program and timeline here: https://www.outreachy.org/mentor/ * questions can be posted to the mailing list, and both Ildiko & Saul have some knowledge of the program * Next meeting: Jan 6? * agreed that we'll cancel the next 2 meetings and reconvene on Jan 6, 2021 * ARs from Previous Meetings * Bill re: getting a Docker Hub pro account - will follow up with Scott on details * Open Requests for Help * CNI Chaining * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010377.html * Bill will talk to Matt & respond * Openstack application can not be deployed on some compute nodes. * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-December/010378.html * Bill will respond that stx.2.0 is EOL * https://docs.starlingx.io/releasenotes/index.html#release-notes * Build Matters (if required) * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Tuesday, December 15, 2020 1:16 PM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Dec 16, 2020) Hi all, reminder of tomorrow's TSC/Community call. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201216T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From Bill.Zvonar at windriver.com Wed Dec 16 15:40:38 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 16 Dec 2020 15:40:38 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX TSC & Community Call Message-ID: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1879 bytes Desc: not available URL: From Bill.Zvonar at windriver.com Wed Dec 16 15:40:49 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 16 Dec 2020 15:40:49 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX TSC & Community Call Message-ID: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1879 bytes Desc: not available URL: From Bill.Zvonar at windriver.com Wed Dec 16 15:43:11 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 16 Dec 2020 15:43:11 +0000 Subject: [Starlingx-discuss] CNI Chaining In-Reply-To: <888375fab02908481d172e435e44ab45@weecodelab.com> References: <888375fab02908481d172e435e44ab45@weecodelab.com> Message-ID: Hi there - we discussed this on the community call today. While Cilium isn't officially supported in StarlingX, we encourage you to share your results if you want to do some testing/experimentation. Bill... -----Original Message----- From: bnovickovs at weecodelab.com Sent: Tuesday, December 15, 2020 11:18 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CNI Chaining [Please note this e-mail is from an EXTERNAL e-mail address] Hi STX community, I ve been aware that Calico shall be used as the main CNI in Stx deployments. However, I am wondering what would be your opinion of using Cilium CNI chaining in conjunction with Calico - https://docs.cilium.io/en/v1.9/gettingstarted/cni-chaining-calico/ which would give “ With Cilium CNI chaining, the base network connectivity and IP address management is managed by the non-Cilium CNI plugin, but Cilium attaches eBPF programs to the network devices created by the non-Cilium plugin to provide L3/L4/L7 network visibility & policy enforcement and other advanced features like transparent encryption.” Do you think it’s safe enough and good practice overall to mix it up this way or it’s better to avoid doing it? Thank you Regards _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Bill.Zvonar at windriver.com Wed Dec 16 15:46:34 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 16 Dec 2020 15:46:34 +0000 Subject: [Starlingx-discuss] Openstack application can not be deployed on some compute nodes. In-Reply-To: <952cb11639c64d758807f7fb2504de52@tencent.com> References: <952cb11639c64d758807f7fb2504de52@tencent.com> Message-ID: Hi there – please note that StarlingX 2.0 is End of Life, and no longer supported. Please try with the latest released version, StarlingX 4.0. Bill… From: parkeryan(闫志杰) Sent: Wednesday, December 16, 2020 2:53 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Openstack application can not be deployed on some compute nodes. [Please note this e-mail is from an EXTERNAL e-mail address] Hello, all. I deployed StarlingX 2.0 on bare metal standard with controller storage, and got some problems while applying stx-openstack application. Here is the details. [sysadmin at controller-0 log(keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 18 | controller-1 | controller | unlocked | enabled | available | | 19 | compute-0 | worker | unlocked | enabled | available | | 20 | compute-1 | worker | unlocked | enabled | available | | 21 | compute-2 | worker | unlocked | enabled | available | | 22 | compute-3 | worker | unlocked | enabled | available | | 23 | compute-4 | worker | unlocked | enabled | available | | 24 | compute-5 | worker | unlocked | enabled | available | | 25 | compute-6 | worker | unlocked | enabled | available | | 26 | compute-7 | worker | unlocked | enabled | available | | 27 | compute-8 | worker | unlocked | enabled | available | | 29 | compute-10 | worker | unlocked | enabled | available | | 30 | compute-11 | worker | unlocked | enabled | available | | 32 | compute-12 | worker | unlocked | enabled | available | | 33 | compute-13 | worker | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ And I labed all compute nodes to support openstack application. [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-0 +-----------+------------------------+-------------+ | hostname | label key | label value | +-----------+------------------------+-------------+ | compute-0 | openstack-compute-node | enabled | | compute-0 | openvswitch | enabled | | compute-0 | sriov | enabled | | compute-0 | sriovdp | enabled | +-----------+------------------------+-------------+ [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-1 +-----------+------------------------+-------------+ | hostname | label key | label value | +-----------+------------------------+-------------+ | compute-1 | openstack-compute-node | enabled | | compute-1 | openvswitch | enabled | | compute-1 | sriov | enabled | | compute-1 | sriovdp | enabled | +-----------+------------------------+-------------+ [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-2 +-----------+------------------------+-------------+ | hostname | label key | label value | +-----------+------------------------+-------------+ | compute-2 | openstack-compute-node | enabled | | compute-2 | openvswitch | enabled | | compute-2 | sriov | enabled | | compute-2 | sriovdp | enabled | +-----------+------------------------+-------------+ [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-3 +-----------+------------------------+-------------+ | hostname | label key | label value | +-----------+------------------------+-------------+ | compute-3 | openstack-compute-node | enabled | | compute-3 | openvswitch | enabled | | compute-3 | sriov | enabled | | compute-3 | sriovdp | enabled | +-----------+------------------------+-------------+ [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-12 +------------+------------------------+-------------+ | hostname | label key | label value | +------------+------------------------+-------------+ | compute-12 | openstack-compute-node | enabled | | compute-12 | openvswitch | enabled | | compute-12 | sriov | enabled | | compute-12 | sriovdp | enabled | +------------+------------------------+-------------+ [sysadmin at controller-0 log(keystone_admin)]$ system host-label-list compute-13 +------------+------------------------+-------------+ | hostname | label key | label value | +------------+------------------------+-------------+ | compute-13 | openstack-compute-node | enabled | | compute-13 | openvswitch | enabled | | compute-13 | sriov | enabled | | compute-13 | sriovdp | enabled | +------------+------------------------+-------------+ However, I found some of them didn’t take effect by openstack host list command. controller-0:~$ openstack host list +----------------------------------+-------------+----------+ | Host Name | Service | Zone | +----------------------------------+-------------+----------+ | nova-consoleauth-d54b6864c-r78q8 | consoleauth | internal | | nova-conductor-855dff79f-rltf4 | conductor | internal | | nova-consoleauth-d54b6864c-78nkh | consoleauth | internal | | nova-conductor-855dff79f-9kn2j | conductor | internal | | nova-scheduler-6554b9c6bb-hqmw2 | scheduler | internal | | nova-scheduler-6554b9c6bb-nzjfl | scheduler | internal | | compute-5 | compute | nova | | compute-8 | compute | nova | | compute-4 | compute | nova | | compute-11 | compute | nova | | compute-7 | compute | nova | | compute-1 | compute | nova | | compute-6 | compute | nova | | compute-0 | compute | nova | | compute-10 | compute | nova | +----------------------------------+-------------+----------+ From which I found compute-2, compute-3, compute-12 and compute-13 is nod displayed in openstack host. I wonder how to solve the problem, and is there some logs can help to determine what happedn to these compute nodes. Thanks in advance. Best regards parkeryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Wed Dec 16 22:31:34 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 16 Dec 2020 22:31:34 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-12-16 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-12-16 All -- reviews merged since last meeting: 0 All -- bug status -- 22 total - team agrees to defer all low priority LP until the upstreaming effort is completed. 13 LP are WIP against API documentation, which is generated from source code (low priority). Those reviews are here: https://review.opendev.org/#/q/project:starlingx/config Reviews in progress: upstream docs, rook reviews The next 2 meetings are cancelled (23 Dec, 30 Dec). We will meet again 06Jan. Happy Holidays to all and thanks for all your hard work this year - eggnog for everyone! Brandy or Wild Turkey are optional :) Status Node Management has a new patch set, submitted before this meeting. Doc has been restructured quite a bit to align with the comments. The WindRiver team are using the Windows subsystem for Linux and now they are back up and able to run local builds again. Drake plans to submit a new patch set on the System Config review before he leaves at end of week. SNMPv3 updates will be January work. We can revisit the doc process then, if any remaining questions. Bruce gave +2/+1 to Juanita's bug fix. From ch.huang789 at advantech.com.tw Thu Dec 17 01:19:28 2020 From: ch.huang789 at advantech.com.tw (CH.Huang789) Date: Thu, 17 Dec 2020 01:19:28 +0000 Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 In-Reply-To: <562227acd98e423e822317ec250e7ddf@taipei09.ADVANTECH.CORP> References: <562227acd98e423e822317ec250e7ddf@taipei09.ADVANTECH.CORP> Message-ID: <4186663939c84725be741dac320c8d47@taipei09.ADVANTECH.CORP> Hi Austin: I think I found the cause is that I should set both controllers's eno1/eno2 as the same datanetwork type, class and vlan. Please correct me if I am wrong. Regards, C.H. Huang Technical Service for Advantech Cloud-IoT From: CH.Huang789 Sent: Wednesday, December 16, 2020 6:01 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Dear Austin: Datanetwork NIC on controller-0 and controller-1 connected to each other. Regards, C.H. Huang Technical Service for Advantech Cloud-IoT From: Sun, Austin > Sent: Wednesday, December 16, 2020 5:58 PM To: CH.Huang789 >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Huang: are datanetwork NIC on controller-0 and controller-1 connected to each other or in same switch/network ? Thanks. BR Austin Sun. From: CH.Huang789 > Sent: Tuesday, December 15, 2020 4:09 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Austin: I loop back eno2 for these 2 servers. Yes, it link up on controller-1. [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-1 +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ | 5cda648c-1c8e-4acc-8661-d8cc10b6f790 | eno7 | platform | ethernet | None | [u'eno7'] | [] | [] | MTU=1500 | | 811ec9ed-cbdc-40ec-b18d-82dd54ad40c5 | data0 | data | ethernet | None | [u'eno2'] | [] | [] | MTU=1500,accelerated=True | | b421709e-3048-44e7-b91f-aeb7de3dac0f | eno5 | platform | ethernet | None | [u'eno5'] | [] | [] | MTU=1500 | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ ssh controller-1 controller-1:~$ ip link show eno2 3: eno2: mtu 1500 qdisc mq master ovs-system state UP mode DEFAULT group default qlen 1000 link/ether 00:d0:c9:cc:33:1d brd ff:ff:ff:ff:ff:ff Regards, C.H. Huang Technical Service for Advantech Cloud-IoT From: Sun, Austin > Sent: Tuesday, December 15, 2020 3:59 PM To: CH.Huang789 >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Huang: Would you check ? system host-if-list controller-1 ? and the NIC assigned as data network in controller-1 is up ? Thanks. BR Austin Sun. From: CH.Huang789 > Sent: Tuesday, December 15, 2020 10:49 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Dear Sir: I follow the instruction to setup the StarlingX 4.0 on 2 bare metal machine with Simple AIO DX. I create one network and two cirros VM. One VM (vm0) host in controller-0, the other VM (vm1) host in controller-1. Everything looks fine on OpenStack Web UI. Each VM assigned a IP address. But only vm0 get the IP address. The vm1 do not have a IP address. Can someone help me on it? vm0: (controller-0): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:e5:76:e3 brd ff:ff:ff:ff:ff:ff inet 192.168.0.28/24 brd 192.168.0.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fee5:76e3/64 scope link valid_lft forever preferred_lft forever vm1: (controller-1): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:15:55:de brd ff:ff:ff:ff:ff:ff inet6 fe80::f816:3eff:fe15:55de/64 scope link valid_lft forever preferred_lft forever [sysadmin at controller-0 ~(keystone_admin)]$ openstack network show public-net01 +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | admin_state_up | UP | | availability_zone_hints | nova | | availability_zones | nova | | created_at | 2020-12-14T15:42:18Z | | description | | | dns_domain | None | | id | 81decfb7-ee67-466d-b644-e71d5a2b04db | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | False | | location | cloud='', project.domain_id=, project.domain_name='Default', project.id='6a2e43c744e24df89214ae72577d3ca6', project.name='admin', region_name='RegionOne', zone= | | mtu | 1500 | | name | public-net01 | | port_security_enabled | True | | project_id | 6a2e43c744e24df89214ae72577d3ca6 | | provider:network_type | vlan | | provider:physical_network | physnet0 | | provider:segmentation_id | 1000 | | qos_policy_id | None | | revision_number | 4 | | router:external | External | | segments | None | | shared | True | | status | ACTIVE | | subnets | d724cdfb-11c2-4509-805a-cf45a62fe569 | | tags | | | updated_at | 2020-12-14T15:57:26Z | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ Regards, C.H. Huang Technical Service for Advantech Cloud-IoT [advantech-logo-retina-email] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8891 bytes Desc: image001.png URL: From austin.sun at intel.com Thu Dec 17 01:41:14 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 17 Dec 2020 01:41:14 +0000 Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 In-Reply-To: <4186663939c84725be741dac320c8d47@taipei09.ADVANTECH.CORP> References: <562227acd98e423e822317ec250e7ddf@taipei09.ADVANTECH.CORP> <4186663939c84725be741dac320c8d47@taipei09.ADVANTECH.CORP> Message-ID: Hi Huang: Yes. you are right . Thanks. BR Austin Sun. From: CH.Huang789 Sent: Thursday, December 17, 2020 9:19 AM To: CH.Huang789 ; Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Austin: I think I found the cause is that I should set both controllers's eno1/eno2 as the same datanetwork type, class and vlan. Please correct me if I am wrong. Regards, C.H. Huang Technical Service for Advantech Cloud-IoT From: CH.Huang789 > Sent: Wednesday, December 16, 2020 6:01 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Dear Austin: Datanetwork NIC on controller-0 and controller-1 connected to each other. Regards, C.H. Huang Technical Service for Advantech Cloud-IoT From: Sun, Austin > Sent: Wednesday, December 16, 2020 5:58 PM To: CH.Huang789 >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Huang: are datanetwork NIC on controller-0 and controller-1 connected to each other or in same switch/network ? Thanks. BR Austin Sun. From: CH.Huang789 > Sent: Tuesday, December 15, 2020 4:09 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Austin: I loop back eno2 for these 2 servers. Yes, it link up on controller-1. [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-1 +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ | 5cda648c-1c8e-4acc-8661-d8cc10b6f790 | eno7 | platform | ethernet | None | [u'eno7'] | [] | [] | MTU=1500 | | 811ec9ed-cbdc-40ec-b18d-82dd54ad40c5 | data0 | data | ethernet | None | [u'eno2'] | [] | [] | MTU=1500,accelerated=True | | b421709e-3048-44e7-b91f-aeb7de3dac0f | eno5 | platform | ethernet | None | [u'eno5'] | [] | [] | MTU=1500 | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+---------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ ssh controller-1 controller-1:~$ ip link show eno2 3: eno2: mtu 1500 qdisc mq master ovs-system state UP mode DEFAULT group default qlen 1000 link/ether 00:d0:c9:cc:33:1d brd ff:ff:ff:ff:ff:ff Regards, C.H. Huang Technical Service for Advantech Cloud-IoT From: Sun, Austin > Sent: Tuesday, December 15, 2020 3:59 PM To: CH.Huang789 >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Hi Huang: Would you check ? system host-if-list controller-1 ? and the NIC assigned as data network in controller-1 is up ? Thanks. BR Austin Sun. From: CH.Huang789 > Sent: Tuesday, December 15, 2020 10:49 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx 4.0 Simple-AIO-DX can not get the IP host on controller-1 Dear Sir: I follow the instruction to setup the StarlingX 4.0 on 2 bare metal machine with Simple AIO DX. I create one network and two cirros VM. One VM (vm0) host in controller-0, the other VM (vm1) host in controller-1. Everything looks fine on OpenStack Web UI. Each VM assigned a IP address. But only vm0 get the IP address. The vm1 do not have a IP address. Can someone help me on it? vm0: (controller-0): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:e5:76:e3 brd ff:ff:ff:ff:ff:ff inet 192.168.0.28/24 brd 192.168.0.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fee5:76e3/64 scope link valid_lft forever preferred_lft forever vm1: (controller-1): 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:15:55:de brd ff:ff:ff:ff:ff:ff inet6 fe80::f816:3eff:fe15:55de/64 scope link valid_lft forever preferred_lft forever [sysadmin at controller-0 ~(keystone_admin)]$ openstack network show public-net01 +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | admin_state_up | UP | | availability_zone_hints | nova | | availability_zones | nova | | created_at | 2020-12-14T15:42:18Z | | description | | | dns_domain | None | | id | 81decfb7-ee67-466d-b644-e71d5a2b04db | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | False | | location | cloud='', project.domain_id=, project.domain_name='Default', project.id='6a2e43c744e24df89214ae72577d3ca6', project.name='admin', region_name='RegionOne', zone= | | mtu | 1500 | | name | public-net01 | | port_security_enabled | True | | project_id | 6a2e43c744e24df89214ae72577d3ca6 | | provider:network_type | vlan | | provider:physical_network | physnet0 | | provider:segmentation_id | 1000 | | qos_policy_id | None | | revision_number | 4 | | router:external | External | | segments | None | | shared | True | | status | ACTIVE | | subnets | d724cdfb-11c2-4509-805a-cf45a62fe569 | | tags | | | updated_at | 2020-12-14T15:57:26Z | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ Regards, C.H. Huang Technical Service for Advantech Cloud-IoT [advantech-logo-retina-email] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8891 bytes Desc: image001.png URL: From build.starlingx at gmail.com Thu Dec 17 10:47:44 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 17 Dec 2020 05:47:44 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_download_mirror - Build # 1098 - Failure! Message-ID: <427602388.701.1608202065977.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1098 Status: Failure Timestamp: 20201217T102255Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201217T100001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/centos8 DOCKER_BUILD_ID: jenkins-f-centos8-20201217T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201217T100001Z/logs MY_REPO: /localdisk/designer/jenkins/f-centos8/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201217T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Thu Dec 17 10:47:47 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 17 Dec 2020 05:47:47 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 60 - Still Failing! In-Reply-To: <506482102.692.1608115741616.JavaMail.javamailuser@localhost> References: <506482102.692.1608115741616.JavaMail.javamailuser@localhost> Message-ID: <325686499.704.1608202068420.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 60 Status: Still Failing Timestamp: 20201217T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201217T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From maryx.camp at intel.com Thu Dec 17 20:05:43 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 17 Dec 2020 20:05:43 +0000 Subject: [Starlingx-discuss] StarlingX Docs Team Call In-Reply-To: References: Message-ID: 3:30 pm Eastern - 12:30 pm Pacific - Docs Team Call Call details * https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * 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 Passcode: 419405 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes * The agenda and notes for each call are kept here: https://etherpad.openstack.org/p/stx-documentation * Call recordings: https://wiki.openstack.org/wiki/Starlingx/Meeting_Logs#Docs_Team_Call -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2305 bytes Desc: not available URL: From maryx.camp at intel.com Thu Dec 17 20:12:56 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 17 Dec 2020 20:12:56 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Docs Team Call Message-ID: 30Dec20: meeting canceled. 3:30 pm Eastern - 12:30 pm Pacific - Docs Team Call Call details * https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * 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 Passcode: 419405 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes * The agenda and notes for each call are kept here: https://etherpad.openstack.org/p/stx-documentation * Call recordings: https://wiki.openstack.org/wiki/Starlingx/Meeting_Logs#Docs_Team_Call -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2345 bytes Desc: not available URL: From maryx.camp at intel.com Thu Dec 17 20:15:30 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 17 Dec 2020 20:15:30 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Docs Team Call Message-ID: 23Dec20: meeting canceled. Sorry for the extra messages. 3:30 pm Eastern - 12:30 pm Pacific - Docs Team Call Call details * https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * 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 Passcode: 419405 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes * The agenda and notes for each call are kept here: https://etherpad.openstack.org/p/stx-documentation * Call recordings: https://wiki.openstack.org/wiki/Starlingx/Meeting_Logs#Docs_Team_Call -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2376 bytes Desc: not available URL: From Don.Penney at windriver.com Thu Dec 17 21:21:59 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 17 Dec 2020 21:21:59 +0000 Subject: [Starlingx-discuss] Updating remaining packages to use PKG_GITREVCOUNT Message-ID: Hi all, I've gone through the starlingx repos to look for remaining packages that are using hardcoded TIS_PATCH_VER values in their build_srpm.data files, replacing them with PKG_GITREVCOUNT. I compared a build with the updated versioning against the hardcoded versions, adding offsets to the PKG_GITREVCOUNT where necessary, to ensure that all updated packages have an incremented version. There are updates in most of our repos, so I'd appreciate it if cores have a few minutes for reviews in their areas: https://review.opendev.org/q/topic:%22auto-versioning%22+(status:open%20OR%20status:merged) Going forward, we should try to ensure new packages use one of the auto-versioning mechanisms. Descriptions of the options (PKG_GITREVCOUNT, SRC_GITREVCOUNT, OTHER_GITREVCOUNT, GITREVCOUNT) can be found in the StarlingX docs here: https://docs.starlingx.io/developer_resources/packaging_ref.html#details-for-build-srpm-data Thanks, Don. -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Dec 18 03:34:58 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 17 Dec 2020 22:34:58 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1401 - Failure! Message-ID: <835517915.707.1608262499329.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1401 Status: Failure Timestamp: 20201218T031513Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20201218T023120Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20201218T023120Z DOCKER_BUILD_ID: jenkins-master-distro-20201218T023120Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20201218T023120Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20201218T023120Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From build.starlingx at gmail.com Fri Dec 18 05:27:41 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Dec 2020 00:27:41 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1110 - Failure! Message-ID: <1685467419.710.1608269262625.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1110 Status: Failure Timestamp: 20201218T051611Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T043029Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20201218T043029Z DOCKER_BUILD_ID: jenkins-master-flock-20201218T043029Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T043029Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20201218T043029Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From build.starlingx at gmail.com Fri Dec 18 05:27:45 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Dec 2020 00:27:45 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 351 - Failure! Message-ID: <657313771.713.1608269265925.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 351 Status: Failure Timestamp: 20201218T043029Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T043029Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Fri Dec 18 08:09:12 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Dec 2020 03:09:12 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 966 - Failure! Message-ID: <1158550991.718.1608278952869.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 966 Status: Failure Timestamp: 20201218T061551Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201218T053001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20201218T053001Z DOCKER_BUILD_ID: jenkins-master-20201218T053001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201218T053001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20201218T053001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Fri Dec 18 08:09:14 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Dec 2020 03:09:14 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 771 - Failure! Message-ID: <191347326.721.1608278955361.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 771 Status: Failure Timestamp: 20201218T053001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201218T053001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From alexandru.dimofte at intel.com Fri Dec 18 09:53:30 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 18 Dec 2020 09:53:30 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201217T035751Z Message-ID: Sanity Test from 2020-December-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201217T035751Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201217T035751Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz This image is affected by: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8413 bytes Desc: image001.png URL: From build.starlingx at gmail.com Fri Dec 18 10:49:46 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Dec 2020 05:49:46 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_download_mirror - Build # 1100 - Failure! Message-ID: <2054452049.724.1608288587476.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1100 Status: Failure Timestamp: 20201218T102349Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201218T100001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/centos8 DOCKER_BUILD_ID: jenkins-f-centos8-20201218T100001Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201218T100001Z/logs MY_REPO: /localdisk/designer/jenkins/f-centos8/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos8/centos/monolithic/20201218T100001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos8 From build.starlingx at gmail.com Fri Dec 18 10:49:49 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Dec 2020 05:49:49 -0500 (EST) Subject: [Starlingx-discuss] [build-report] f/centos8 STX_build_centos8_master - Build # 61 - Still Failing! In-Reply-To: <323735950.702.1608202066579.JavaMail.javamailuser@localhost> References: <323735950.702.1608202066579.JavaMail.javamailuser@localhost> Message-ID: <106776195.727.1608288589703.JavaMail.javamailuser@localhost> Project: STX_build_centos8_master Build #: 61 Status: Still Failing Timestamp: 20201218T100001Z Branch: f/centos8 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos8/centos/monolithic/20201218T100001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From scott.little at windriver.com Fri Dec 18 14:54:46 2020 From: scott.little at windriver.com (Scott Little) Date: Fri, 18 Dec 2020 09:54:46 -0500 Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1110 - Failure! In-Reply-To: <1685467419.710.1608269262625.JavaMail.javamailuser@localhost> References: <1685467419.710.1608269262625.JavaMail.javamailuser@localhost> Message-ID: The following commit appears to have broken the build last night. https://review.opendev.org/c/starlingx/platform-armada-app/+/758786 Change-Id: Ic4270e401b2c3e51c3aecfab23af1e874e733831 Git sha: 3466dd67da245ebc678aa75c3c95c6c90257326e Error logs ... http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T043029Z/logs/jenkins-STX_build_pre_installer_layered-1110.log.html http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T043029Z/logs/std/failed-packages/stx-platform-helm-1.0-12.tis/build.log ==> Linting cephfs-provisioner [INFO] Chart.yaml: icon is recommended [ERROR] templates/: template: cephfs-provisioner/templates/storageclass.yaml:17:9: executing "cephfs-provisioner/templates/storageclass.yaml" at : error calling eq: invalid type for comparison BUILDSTDERR: Error: 1 chart(s) linted, 1 chart(s) failed BUILDSTDERR: make[1]: *** [lint-cephfs-provisioner] Error 1 make[1]: Leaving directory `/builddir/build/BUILD/stx-platform-helm-1.0/helm-charts' BUILDSTDERR: make: *** [cephfs-provisioner] Error 2 On 2020-12-18 12:27 a.m., build.starlingx at gmail.com wrote: > [Please note this e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_pre_installer_layered > Build #: 1110 > Status: Failure > Timestamp: 20201218T051611Z > Branch: > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T043029Z/logs > -------------------------------------------------------------------------------- > Parameters > > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20201218T043029Z > DOCKER_BUILD_ID: jenkins-master-flock-20201218T043029Z-builder > OS: centos > MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T043029Z/logs > BUILD_IMG: true > FULL_BUILD: false > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20201218T043029Z/logs > MASTER_JOB_NAME: STX_build_layer_flock_master_master > LAYER: flock > MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock > BUILD_ISO: true > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Fri Dec 18 17:11:40 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 18 Dec 2020 17:11:40 +0000 Subject: [Starlingx-discuss] FW: [build-report] STX_build_pre_installer_layered - Build # 1110 - Failure! In-Reply-To: References: <1685467419.710.1608269262625.JavaMail.javamailuser@localhost>, , Message-ID: For some reason Daniel Safta's email is not getting through. I'm forwarding his email that provides a fix for the build failure. Frank From: Safta, Daniel Sent: Friday, December 18, 2020 11:01 AM To: Miller, Frank Subject: Fw: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1110 - Failure! ________________________________ De la: Safta, Daniel > Trimis: vineri, 18 decembrie 2020 17:13 Către: Little, Scott > Subiect: Re: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1110 - Failure! Regarding the build error: A key has been deleted from values.yaml. I have a fix for that at https://review.opendev.org/c/starlingx/platform-armada-app/+/767755 Thanks, Daniel ________________________________ De la: Little, Scott > Trimis: vineri, 18 decembrie 2020 16:54 Către: starlingx-discuss at lists.starlingx.io >; Safta, Daniel > Cc: Wang, Jing (Angie) >; Church, Robert > Subiect: Re: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1110 - Failure! The following commit appears to have broken the build last night. https://review.opendev.org/c/starlingx/platform-armada-app/+/758786 Change-Id: Ic4270e401b2c3e51c3aecfab23af1e874e733831 Git sha: 3466dd67da245ebc678aa75c3c95c6c90257326e Error logs ... http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T043029Z/logs/jenkins-STX_build_pre_installer_layered-1110.log.html http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T043029Z/logs/std/failed-packages/stx-platform-helm-1.0-12.tis/build.log ==> Linting cephfs-provisioner [INFO] Chart.yaml: icon is recommended [ERROR] templates/: template: cephfs-provisioner/templates/storageclass.yaml:17:9: executing "cephfs-provisioner/templates/storageclass.yaml" at : error calling eq: invalid type for comparison BUILDSTDERR: Error: 1 chart(s) linted, 1 chart(s) failed BUILDSTDERR: make[1]: *** [lint-cephfs-provisioner] Error 1 make[1]: Leaving directory `/builddir/build/BUILD/stx-platform-helm-1.0/helm-charts' BUILDSTDERR: make: *** [cephfs-provisioner] Error 2 On 2020-12-18 12:27 a.m., build.starlingx at gmail.com wrote: [Please note this e-mail is from an EXTERNAL e-mail address] Project: STX_build_pre_installer_layered Build #: 1110 Status: Failure Timestamp: 20201218T051611Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T043029Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20201218T043029Z DOCKER_BUILD_ID: jenkins-master-flock-20201218T043029Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T043029Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20201218T043029Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sat Dec 19 03:13:06 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Dec 2020 22:13:06 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1112 - Failure! Message-ID: <1599651262.735.1608347587367.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1112 Status: Failure Timestamp: 20201219T031218Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201219T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201219T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201219T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201219T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201219T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Sat Dec 19 03:13:09 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Dec 2020 22:13:09 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 396 - Failure! Message-ID: <477013930.738.1608347589803.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 396 Status: Failure Timestamp: 20201219T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201219T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sat Dec 19 03:13:28 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Dec 2020 22:13:28 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1403 - Failure! Message-ID: <1879776065.741.1608347608662.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1403 Status: Failure Timestamp: 20201219T031226Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201219T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201219T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201219T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201219T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201219T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Sun Dec 20 03:12:23 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 19 Dec 2020 22:12:23 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1113 - Still Failing! In-Reply-To: <1203587002.733.1608347584894.JavaMail.javamailuser@localhost> References: <1203587002.733.1608347584894.JavaMail.javamailuser@localhost> Message-ID: <1673726780.748.1608433943971.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1113 Status: Still Failing Timestamp: 20201220T031134Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201220T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201220T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201220T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201220T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201220T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Sun Dec 20 03:12:25 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 19 Dec 2020 22:12:25 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 397 - Still Failing! In-Reply-To: <1006118412.736.1608347588139.JavaMail.javamailuser@localhost> References: <1006118412.736.1608347588139.JavaMail.javamailuser@localhost> Message-ID: <421692690.751.1608433946230.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 397 Status: Still Failing Timestamp: 20201220T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201220T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sun Dec 20 03:12:45 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 19 Dec 2020 22:12:45 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1405 - Failure! Message-ID: <1549535333.754.1608433966467.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1405 Status: Failure Timestamp: 20201220T031144Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201220T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201220T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201220T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201220T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201220T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From murthyp at gmail.com Sun Dec 20 06:14:52 2020 From: murthyp at gmail.com (Prashant Murthy) Date: Sun, 20 Dec 2020 11:44:52 +0530 Subject: [Starlingx-discuss] KickStart Application Message-ID: Hi, I have one basic question. Once StarlingX is installed - is there a way to kick-start some pod/application - which can autofetch information for next set of operations? How does StaringX provide ZTP for applications? Thanks Prashant -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Dec 21 00:42:59 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 20 Dec 2020 19:42:59 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1114 - Still Failing! In-Reply-To: <601177233.746.1608433941568.JavaMail.javamailuser@localhost> References: <601177233.746.1608433941568.JavaMail.javamailuser@localhost> Message-ID: <733738441.760.1608511380536.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1114 Status: Still Failing Timestamp: 20201221T004212Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201221T000001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201221T000001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201221T000001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201221T000001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201221T000001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Mon Dec 21 00:43:03 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 20 Dec 2020 19:43:03 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 398 - Still Failing! In-Reply-To: <369212205.749.1608433944537.JavaMail.javamailuser@localhost> References: <369212205.749.1608433944537.JavaMail.javamailuser@localhost> Message-ID: <637759847.763.1608511384103.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 398 Status: Still Failing Timestamp: 20201221T000001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201221T000001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Mon Dec 21 00:43:23 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 20 Dec 2020 19:43:23 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1407 - Failure! Message-ID: <1609927469.766.1608511404431.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1407 Status: Failure Timestamp: 20201221T004221Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201221T000001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201221T000001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201221T000001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201221T000001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201221T000001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From Frank.Miller at windriver.com Mon Dec 21 14:58:12 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 21 Dec 2020 14:58:12 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX build meting Dec 29 Message-ID: FYI - there will not be a meeting on Dec 29 and the next build meeting is planned for Tuesday January 12th. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Dec 21 14:58:10 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 21 Dec 2020 14:58:10 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX containerization meting Dec 22 Message-ID: FYI - there will not be a meeting on Dec 22 and the next containerization meeting is planned for Tuesday January 5th. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Mon Dec 21 15:10:43 2020 From: Saul.Wold at windriver.com (Saul Wold) Date: Mon, 21 Dec 2020 07:10:43 -0800 Subject: [Starlingx-discuss] StarlingX Multi-OS Meeting Message-ID: <4f8decb1-f19c-2131-49c2-e24b99e46fa1@windriver.com> Agenda: - meta-starlingx Status - Alternate OS discussion 7:30am Pacific - Multi-OS Team Call - bi-weekly Call details Meetpad link: https://meet.jit.si/starlingx-multios Dialing in from phone: Dial(for higher quality, dial a number based on your current location): To join by phone instead, tap this: +1.512.647.1431,,2792742287# PIN: 2792 7422 87 Looking for a different dial-in number? See meeting dial-in numbers: https://meet.jit.si/static/dialInInfo.html?room=starlingx-multios Agenda and meeting minutes The agenda and notes for each call are kept in Etherpads: Multi-OS team Agenda and Notes https://wiki.openstack.org/wiki/Starlingx/Meetings#7:30am_Pacific_-_Multi-OS_Team_Call_-_bi-weekly -- Sau! From build.starlingx at gmail.com Tue Dec 22 00:42:31 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 21 Dec 2020 19:42:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1115 - Still Failing! In-Reply-To: <707672666.758.1608511378054.JavaMail.javamailuser@localhost> References: <707672666.758.1608511378054.JavaMail.javamailuser@localhost> Message-ID: <1215174109.774.1608597752406.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1115 Status: Still Failing Timestamp: 20201222T004148Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201222T000001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201222T000001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201222T000001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201222T000001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201222T000001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Tue Dec 22 00:42:34 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 21 Dec 2020 19:42:34 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 399 - Still Failing! In-Reply-To: <809748165.761.1608511381209.JavaMail.javamailuser@localhost> References: <809748165.761.1608511381209.JavaMail.javamailuser@localhost> Message-ID: <704272182.777.1608597754767.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 399 Status: Still Failing Timestamp: 20201222T000001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201222T000001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Tue Dec 22 00:42:53 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 21 Dec 2020 19:42:53 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1409 - Failure! Message-ID: <1741864640.780.1608597774465.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1409 Status: Failure Timestamp: 20201222T004157Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201222T000001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201222T000001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201222T000001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201222T000001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201222T000001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Tue Dec 22 08:22:31 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 22 Dec 2020 03:22:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1410 - Still Failing! In-Reply-To: <1790954621.778.1608597772679.JavaMail.javamailuser@localhost> References: <1790954621.778.1608597772679.JavaMail.javamailuser@localhost> Message-ID: <1077352273.783.1608625352127.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1410 Status: Still Failing Timestamp: 20201222T061547Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201222T053001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20201222T053001Z DOCKER_BUILD_ID: jenkins-master-20201222T053001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20201222T053001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20201222T053001Z/logs MASTER_JOB_NAME: STX_build_master_master LAYER: MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From nicolae.jascanu at intel.com Tue Dec 22 10:39:58 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Tue, 22 Dec 2020 10:39:58 +0000 Subject: [Starlingx-discuss] Intel validation team - vacation days Message-ID: Hi All, These two weeks, Intel validation team is on vacation so there will be no Sanity report for this period. We will resume executing sanity on January 4th. Regards, Nicolae Jascanu, Ph.D. Software Engineer IOTG Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Tue Dec 22 17:05:31 2020 From: Saul.Wold at windriver.com (Saul Wold) Date: Tue, 22 Dec 2020 09:05:31 -0800 Subject: [Starlingx-discuss] Multi OS Meeting Notes & Initial Centos-8 Alternatives Message-ID: <2925f882-9092-9949-e6ff-3ce23675774c@windriver.com> StarlingX Community: As has been announced Long Term Support for CentOS-8 will be going away in December of 2021 (1 year away). CentOS-Stream will be the "replacement", but has some challenges due to the update policy and possible patching of CVEs in packages. Listed below are additional options, please provide feedback so we can start discussing options here and during the next set of calls. I would like to hear if there are ideas I am missing or other proposals. Thanks Sau! MultiOS Team Meeting - 12/22/2020 - meta-starlingx - No update at this point. - Starting the CentOS-8 Alternatives discussion - CentOS-8 is not getting long term support (stops in Dec 2021) - CentOS-7 Short - medium term (CVEs 2024) - Question about support for new hardware? - RHEL Alternatives - Cloudlinux / RockyLinux - CentOS-Stream may not be stable enought - What's the CVE support commitment for older packages - Debian / Ubuntu - Technical challenges with rpm->deb packaging - Ubuntu has known branding / licenses issues - OpenEmbedded / Yocto Project meta-startlingx - Work in progress already using StarlingX-3.0 - SuSE / OpenSuse - RPM based - Make StarlingX platform agnostic - Currently there is a custom kernel and userspace - Need to get rid of custom userspace. - Oracle Linux -- Sau! From Daniel.Safta at windriver.com Tue Dec 22 19:56:39 2020 From: Daniel.Safta at windriver.com (Safta, Daniel) Date: Tue, 22 Dec 2020 19:56:39 +0000 Subject: [Starlingx-discuss] New docker image needed in StarlingX Message-ID: Hi all, Just a heads-up that with https://review.opendev.org/c/starlingx/platform-armada-app/+/758786 a new docker image is required to enable cephfs-provisioner: cephfs-provisioner:v2.1.0-k8s1.11. Thanks, Daniel Safta -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Tue Dec 22 21:57:39 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Tue, 22 Dec 2020 21:57:39 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20201218T192132Z Message-ID: Sanity Test from 2020-December-18 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T192132Z/outputs/iso/ ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20201218T192132Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Please see the openstack-horizon error log from the comments at: https://bugs.launchpad.net/starlingx/+bug/1908117 Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Tue Dec 22 21:58:36 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Tue, 22 Dec 2020 21:58:36 +0000 Subject: [Starlingx-discuss] Validation team - vacation days Message-ID: Hi All, These two weeks, Intel validation team is on vacation so there will be no Sanity report for this period. We will resume executing sanity on January 4th. Regards, Nicolae Jascanu, Ph.D. Software Engineer IOTG Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Dec 23 02:53:15 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 22 Dec 2020 21:53:15 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1116 - Still Failing! In-Reply-To: <192207093.772.1608597749098.JavaMail.javamailuser@localhost> References: <192207093.772.1608597749098.JavaMail.javamailuser@localhost> Message-ID: <572324361.786.1608691995700.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1116 Status: Still Failing Timestamp: 20201223T025237Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201223T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201223T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201223T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201223T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201223T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Wed Dec 23 02:53:17 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 22 Dec 2020 21:53:17 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 400 - Still Failing! In-Reply-To: <497781797.775.1608597753001.JavaMail.javamailuser@localhost> References: <497781797.775.1608597753001.JavaMail.javamailuser@localhost> Message-ID: <232557525.789.1608691998087.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 400 Status: Still Failing Timestamp: 20201223T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201223T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Wed Dec 23 02:53:36 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 22 Dec 2020 21:53:36 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1411 - Still Failing! In-Reply-To: <217956302.781.1608625349028.JavaMail.javamailuser@localhost> References: <217956302.781.1608625349028.JavaMail.javamailuser@localhost> Message-ID: <140991114.792.1608692016877.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1411 Status: Still Failing Timestamp: 20201223T025244Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201223T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201223T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201223T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201223T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201223T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From Frank.Miller at windriver.com Wed Dec 23 18:32:53 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Wed, 23 Dec 2020 18:32:53 +0000 Subject: [Starlingx-discuss] FW: New docker image needed in StarlingX In-Reply-To: References: Message-ID: I’m not seeing emails on the mailing list so forwarding this email just in case it is not getting through. Frank ________________________________ De la: Safta, Daniel Trimis: marți, 22 decembrie 2020 21:56 Către: starlingx-discuss at lists.starlingx.io > Subiect: New docker image needed in StarlingX Hi all, Just a heads-up that with https://review.opendev.org/c/starlingx/platform-armada-app/+/758786 a new docker image is required to enable cephfs-provisioner: cephfs-provisioner:v2.1.0-k8s1.11. Thanks, Daniel Safta -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Dec 23 22:29:10 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 23 Dec 2020 22:29:10 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Dec 16/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Dec 16 2020 stx.5.0 - Status for Milestone-2 - Dec 18 - All current proposed specs are merged. - Current Feature Status - Feature List: https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=1107209846 - Overall the status is acceptable with some highlighted risks: - Ceph Rook - risk due to slow review cycle - Fault Containerization - risk due to needing support for ceph-client and nfv - Release Test Status - No concerns raised from the test team regarding the release test plans - Currently working on feature test plans - Feature Testing: https://docs.google.com/spreadsheets/d/1jro4ItdSobB0-fseK_4cOZJHhUyuh_eCBBsDOp_A5Pc/edit#gid=968103774 - Test Automation Deliverables: focusing on test automation in January before regression starts - Regression to start in early Feb - From Bill: New features/specs potentially being proposed for this release - working to assign primes so we can start working on the specs - Intel Ice-Lake CPU Support - Intel Mt. Bryce eASIC / Pomona Lake Support - Intel Columbiaville NIC Support - Shared Single NIC Support - PTP Notification Enhancements - Nvidia T4 GPU Support - Note: Specs (if required) will be targeted for mid-Jan; don't expect all to require specs as some are mostly test activities. Code merge target close to the current MS-3 date w/ minor exceptions. - Reviewed with release team - no current concerns; features can proceed; release team will monitor status over the next few weeks to determine any potential risk to the overall stx.5.0 release - OS Direction given CentOS8 announcement - StarlingX has about a year to implement an alternative as CentOS8 will be EOL on Dec 31/2021. CentOS7 will be EOL on Dec 31/2024. - Next step is to focus on discussing/evaluating the technical options - Note: Multi-OS work to date has shown that swapping out the OS is a challenging task From build.starlingx at gmail.com Thu Dec 24 02:52:39 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 23 Dec 2020 21:52:39 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1117 - Still Failing! In-Reply-To: <393087805.784.1608691993321.JavaMail.javamailuser@localhost> References: <393087805.784.1608691993321.JavaMail.javamailuser@localhost> Message-ID: <1712985330.796.1608778360307.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1117 Status: Still Failing Timestamp: 20201224T025150Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201224T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201224T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201224T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201224T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201224T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Thu Dec 24 02:52:42 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 23 Dec 2020 21:52:42 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 401 - Still Failing! In-Reply-To: <1585739877.787.1608691996331.JavaMail.javamailuser@localhost> References: <1585739877.787.1608691996331.JavaMail.javamailuser@localhost> Message-ID: <1043452250.799.1608778362819.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 401 Status: Still Failing Timestamp: 20201224T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201224T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Thu Dec 24 02:53:03 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 23 Dec 2020 21:53:03 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1413 - Failure! Message-ID: <1619079010.802.1608778384374.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1413 Status: Failure Timestamp: 20201224T025200Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201224T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201224T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201224T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201224T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201224T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Fri Dec 25 02:43:59 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 24 Dec 2020 21:43:59 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1118 - Still Failing! In-Reply-To: <2047493400.794.1608778356490.JavaMail.javamailuser@localhost> References: <2047493400.794.1608778356490.JavaMail.javamailuser@localhost> Message-ID: <182217191.806.1608864239936.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1118 Status: Still Failing Timestamp: 20201225T024310Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201225T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201225T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201225T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201225T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201225T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Fri Dec 25 02:44:01 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 24 Dec 2020 21:44:01 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 402 - Still Failing! In-Reply-To: <528401151.797.1608778361105.JavaMail.javamailuser@localhost> References: <528401151.797.1608778361105.JavaMail.javamailuser@localhost> Message-ID: <1044569249.809.1608864242466.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 402 Status: Still Failing Timestamp: 20201225T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201225T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Fri Dec 25 02:44:21 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 24 Dec 2020 21:44:21 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1415 - Failure! Message-ID: <1680416199.812.1608864262511.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1415 Status: Failure Timestamp: 20201225T024315Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201225T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201225T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201225T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201225T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201225T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Sat Dec 26 02:44:06 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 25 Dec 2020 21:44:06 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1119 - Still Failing! In-Reply-To: <214314152.804.1608864237330.JavaMail.javamailuser@localhost> References: <214314152.804.1608864237330.JavaMail.javamailuser@localhost> Message-ID: <1987719569.816.1608950647652.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1119 Status: Still Failing Timestamp: 20201226T024312Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201226T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201226T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201226T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201226T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201226T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Sat Dec 26 02:44:09 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 25 Dec 2020 21:44:09 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 403 - Still Failing! In-Reply-To: <2067229576.807.1608864240577.JavaMail.javamailuser@localhost> References: <2067229576.807.1608864240577.JavaMail.javamailuser@localhost> Message-ID: <811129075.819.1608950650178.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 403 Status: Still Failing Timestamp: 20201226T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201226T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sat Dec 26 02:44:29 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 25 Dec 2020 21:44:29 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1417 - Failure! Message-ID: <1484698355.822.1608950670558.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1417 Status: Failure Timestamp: 20201226T024317Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201226T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201226T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201226T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201226T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201226T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Sun Dec 27 02:44:31 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 26 Dec 2020 21:44:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1120 - Still Failing! In-Reply-To: <1801851660.814.1608950645167.JavaMail.javamailuser@localhost> References: <1801851660.814.1608950645167.JavaMail.javamailuser@localhost> Message-ID: <333846688.826.1609037072149.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1120 Status: Still Failing Timestamp: 20201227T024338Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201227T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201227T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201227T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201227T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201227T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Sun Dec 27 02:44:33 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 26 Dec 2020 21:44:33 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 404 - Still Failing! In-Reply-To: <1509117228.817.1608950648418.JavaMail.javamailuser@localhost> References: <1509117228.817.1608950648418.JavaMail.javamailuser@localhost> Message-ID: <1718342957.829.1609037074431.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 404 Status: Still Failing Timestamp: 20201227T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201227T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sun Dec 27 02:44:52 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 26 Dec 2020 21:44:52 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1419 - Failure! Message-ID: <144886340.832.1609037093412.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1419 Status: Failure Timestamp: 20201227T024346Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201227T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201227T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201227T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201227T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201227T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Mon Dec 28 00:13:35 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 27 Dec 2020 19:13:35 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1121 - Still Failing! In-Reply-To: <79904140.824.1609037069397.JavaMail.javamailuser@localhost> References: <79904140.824.1609037069397.JavaMail.javamailuser@localhost> Message-ID: <2041112722.836.1609114416388.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1121 Status: Still Failing Timestamp: 20201228T001244Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201228T000001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201228T000001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201228T000001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201228T000001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201228T000001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Mon Dec 28 00:13:38 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 27 Dec 2020 19:13:38 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 405 - Still Failing! In-Reply-To: <1699379231.827.1609037072784.JavaMail.javamailuser@localhost> References: <1699379231.827.1609037072784.JavaMail.javamailuser@localhost> Message-ID: <1695397961.839.1609114419489.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 405 Status: Still Failing Timestamp: 20201228T000001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201228T000001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Mon Dec 28 00:14:00 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 27 Dec 2020 19:14:00 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1421 - Failure! Message-ID: <1052478573.842.1609114440845.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1421 Status: Failure Timestamp: 20201228T001253Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201228T000001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201228T000001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201228T000001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201228T000001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201228T000001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Tue Dec 29 00:13:54 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 28 Dec 2020 19:13:54 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1122 - Still Failing! In-Reply-To: <1043828182.834.1609114414204.JavaMail.javamailuser@localhost> References: <1043828182.834.1609114414204.JavaMail.javamailuser@localhost> Message-ID: <1818178714.846.1609200834809.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1122 Status: Still Failing Timestamp: 20201229T001301Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201229T000001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201229T000001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201229T000001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201229T000001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201229T000001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Tue Dec 29 00:13:56 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 28 Dec 2020 19:13:56 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 406 - Still Failing! In-Reply-To: <1237657778.837.1609114417075.JavaMail.javamailuser@localhost> References: <1237657778.837.1609114417075.JavaMail.javamailuser@localhost> Message-ID: <1940737998.849.1609200837059.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 406 Status: Still Failing Timestamp: 20201229T000001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201229T000001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Tue Dec 29 00:14:19 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 28 Dec 2020 19:14:19 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1423 - Failure! Message-ID: <1805302600.852.1609200859622.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1423 Status: Failure Timestamp: 20201229T001307Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201229T000001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201229T000001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201229T000001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201229T000001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201229T000001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Wed Dec 30 02:43:58 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 29 Dec 2020 21:43:58 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1123 - Still Failing! In-Reply-To: <2072210877.844.1609200832222.JavaMail.javamailuser@localhost> References: <2072210877.844.1609200832222.JavaMail.javamailuser@localhost> Message-ID: <373864226.856.1609296239165.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1123 Status: Still Failing Timestamp: 20201230T024307Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201230T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201230T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201230T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201230T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201230T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Wed Dec 30 02:44:00 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 29 Dec 2020 21:44:00 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 407 - Still Failing! In-Reply-To: <808247252.847.1609200835402.JavaMail.javamailuser@localhost> References: <808247252.847.1609200835402.JavaMail.javamailuser@localhost> Message-ID: <866382009.859.1609296241230.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 407 Status: Still Failing Timestamp: 20201230T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201230T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Wed Dec 30 02:44:22 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 29 Dec 2020 21:44:22 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1425 - Failure! Message-ID: <1160217938.862.1609296262616.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1425 Status: Failure Timestamp: 20201230T024315Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201230T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201230T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201230T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201230T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201230T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From Haiqing.Bai at windriver.com Wed Dec 30 10:46:11 2020 From: Haiqing.Bai at windriver.com (Bai, Haiqing) Date: Wed, 30 Dec 2020 10:46:11 +0000 Subject: [Starlingx-discuss] Issue when resize2fs on /dev/drbd[x] Message-ID: Any idea about the below issue during running playbook, or how to make the lv disk "/dev/drbd[x]" not "read-only" files system? Thanks. controller-0:~$ ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml TASK [bootstrap/persist-config : Fail if file system resizing failed for a reason other than it has been done already] *** failed: [localhost] (item={'msg': 'non-zero return code', 'cmd': ['resize2fs', '/dev/drbd0'], 'stdout': '', 'stderr': 'resize2fs 1.44.6 (5-Mar-2019)\nopen: Read-only file system while opening /dev/drbd0', 'rc': 1, 'start': '2020-12-30 09:26:23.094706', 'end': '2020-12-30 09:26:23.096630', 'delta': '0:00:00.001924', 'changed': True, 'failed': False, 'invocation': {'module_args': {'_raw_params': 'resize2fs /dev/drbd0', 'warn': True, '_uses_shell': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': [], 'stderr_lines': ['resize2fs 1.44.6 (5-Mar-2019)', 'open: Read-only file system while opening /dev/drbd0'], 'failed_when_result': False, 'item': 'resize2fs /dev/drbd0', 'ansible_loop_var': 'item'}) => {"ansible_loop_var": "item", "changed": false, "item": {"ansible_loop_var": "item", "changed": true, "cmd": ["resize2fs", "/dev/drbd0"], "delta": "0:00:00.001924", "end": "2020-12-30 09:26:23.096630", "failed": false, "failed_when_result": false, "invocation": {"module_args": {"_raw_params": "resize2fs /dev/drbd0", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true, "warn": true}}, "item": "resize2fs /dev/drbd0", "msg": "non-zero return code", "rc": 1, "start": "2020-12-30 09:26:23.094706", "stderr": "resize2fs 1.44.6 (5-Mar-2019)\nopen: Read-only file system while opening /dev/drbd0", "stderr_lines": ["resize2fs 1.44.6 (5-Mar-2019)", "open: Read-only file system while opening /dev/drbd0"], "stdout": "", "stdout_lines": []}, "msg": "resize2fs /dev/drbd0 failed for the following reason: resize2fs 1.44.6 (5-Mar-2019)\nopen: Read-only file system while opening /dev/drbd0."} B,R Haiqing Bai -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Dec 31 02:40:36 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 31 Dec 2020 02:40:36 +0000 Subject: [Starlingx-discuss] config project zuul check fail again Message-ID: Hi AL This patch is failed to merge, blocked for zuul check. https://review.opendev.org/c/starlingx/config/+/761711 This should be config project base code, zuul check fail again. 2020-12-30 17:53:17.385590 | ubuntu-xenial | tests.api.test_certificate.ApiCertificatePostTestSuite.test_install_2xcert_1xkey_ssl_certificate 2020-12-30 17:53:17.385618 | ubuntu-xenial | ------------------------------------------------------------------------------------------------ 2020-12-30 17:53:17.385644 | ubuntu-xenial | 2020-12-30 17:53:17.385670 | ubuntu-xenial | Captured traceback: 2020-12-30 17:53:17.385696 | ubuntu-xenial | ~~~~~~~~~~~~~~~~~~~ 2020-12-30 17:53:17.385722 | ubuntu-xenial | Traceback (most recent call last): 2020-12-30 17:53:17.385757 | ubuntu-xenial | File "/home/zuul/src/opendev.org/starlingx/config/sysinv/sysinv/sysinv/sysinv/tests/api/test_certificate.py", line 395, in test_install_2xcert_1xkey_ssl_certificate 2020-12-30 17:53:17.385787 | ubuntu-xenial | self.assertIn('certificates', resp) 2020-12-30 17:53:17.385813 | ubuntu-xenial | File "/tmp/zuul_sysinvtox/py27/lib/python2.7/site-packages/testtools/testcase.py", line 417, in assertIn 2020-12-30 17:53:17.385841 | ubuntu-xenial | self.assertThat(haystack, Contains(needle), message) 2020-12-30 17:53:17.385867 | ubuntu-xenial | File "/tmp/zuul_sysinvtox/py27/lib/python2.7/site-packages/testtools/testcase.py", line 498, in assertThat 2020-12-30 17:53:17.385893 | ubuntu-xenial | raise mismatch_error 2020-12-30 17:53:17.385918 | ubuntu-xenial | testtools.matchers._impl.MismatchError: 'certificates' not in {u'success': u'', u'error': u'certificate is not valid before 2020-06-25 15:10:01 nor after 2020-12-22 15:10:01'} Could you help to check. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Dec 31 02:43:56 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 30 Dec 2020 21:43:56 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1124 - Still Failing! In-Reply-To: <137563249.854.1609296236432.JavaMail.javamailuser@localhost> References: <137563249.854.1609296236432.JavaMail.javamailuser@localhost> Message-ID: <1281157520.866.1609382637380.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1124 Status: Still Failing Timestamp: 20201231T024300Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201231T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201231T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201231T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201231T023001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201231T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Thu Dec 31 02:43:59 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 30 Dec 2020 21:43:59 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 408 - Still Failing! In-Reply-To: <199159959.857.1609296239881.JavaMail.javamailuser@localhost> References: <199159959.857.1609296239881.JavaMail.javamailuser@localhost> Message-ID: <757775078.869.1609382639510.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 408 Status: Still Failing Timestamp: 20201231T023001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201231T023001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Thu Dec 31 02:44:17 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 30 Dec 2020 21:44:17 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1427 - Failure! Message-ID: <1625578995.872.1609382658241.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1427 Status: Failure Timestamp: 20201231T024311Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201231T023001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20201231T023001Z DOCKER_BUILD_ID: jenkins-master-compiler-20201231T023001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20201231T023001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20201231T023001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From Ankush.Rai at commscope.com Mon Dec 21 15:34:57 2020 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Mon, 21 Dec 2020 15:34:57 +0000 Subject: [Starlingx-discuss] How to enable CPU-manager? Message-ID: Hi, Is this possible to enable Kubernetes labels on a host during installation itself via localhost.yaml ? I know this can be done via a system command like below, but is there any way to automatically assign this ? system host-label-assign controller-0 kube-cpu-mgr-policy=static Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ankush.Rai at commscope.com Mon Dec 21 09:34:20 2020 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Mon, 21 Dec 2020 09:34:20 +0000 Subject: [Starlingx-discuss] How to provision the DOCKER REGISTRIES to edge cloud Message-ID: Hi, In a distributed cloud environment, how to provision the DOCKER REGISTRIES from central cloud ? Is there any support to provide the required docker registry details in the bootstrap-values.yml like docker_registries: defaults: url: type: docker username: password: ssl_ca_cert: /etc/docker/certs.d//ca.crt Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Thu Dec 24 19:28:11 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Thu, 24 Dec 2020 19:28:11 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Test meeting Message-ID: A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 6028 bytes Desc: not available URL: