lists.starlingx.io
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

Starlingx-discuss

Thread Start a new thread
Download
Threads by month
  • ----- 2025 -----
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2021 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2020 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2019 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2018 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
starlingx-discuss@lists.starlingx.io

  • 7 participants
  • 8223 discussions
[Starlingx-discuss] StarlingX Survey discussion follow up
by Ildiko Vancsa 23 Jul '22

23 Jul '22
Hi StarlingX Community, I’m reaching out to provide some information as a follow up to the StarlingX survey discussion on the TSC & Community call this week. The open question during the call was: Where can the community see the info that’s been collected? A few people from the OpenInfra Foundation staff have access to the raw data. We cannot share that publicly due to confidentiality reasons. We aggregate and anonymize responses to these surveys before sharing, to ensure that our communities can still receive information that is important for them. You can find statistics extracted from the survey under the StarlingX section here: https://openinfra.dev/user-survey/ When the responders provide contact information I always reach out to them to find out more and encourage them to get in touch with the community. I usually share data and some specifics from the feedback section on the starlingx-discuss mailing list, where we get new results that contain responses to those questions. The responses from the past one year were partial and din't include feedback about the platform. Call to Action: If you know anyone who’s using or evaluating StarlingX but is not in touch with the community yet, please encourage them to fill out the survey to still help the contributors’ work. As a reminder, you can find the survey here: https://www.surveymonkey.com/r/StarlingX We can also update some of the questions or the structure of the survey, if the community has a preference on any of that. Please let me know if you have any questions or comments on any of the above. Thanks and Best Regards, Ildikó ——— Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation
1 0
0 0
[Starlingx-discuss] Minutes: Community Call (July 20 2022)
by Khalil, Ghada 20 Jul '22

20 Jul '22
Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call July 20 2022 Standing Topics - Build - CentOS builds - Builds are green this week. No failures. - Debian builds - Mostly green. One failure reported. - Sanity - Sanity w/o stx-openstack - Sanity is now running on AIO-DX and is green - Latest Report is Green: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-July/013165.html - Next step is to add AIO-SX to the sanity suite - Sanity w/ stx-openstack - Blocked on https://bugs.launchpad.net/starlingx/+bug/1980397 - Should be unblocked next week based on plan below - Gerrit Reviews in Need of Attention - stx.7.0 Release Notes: - https://review.opendev.org/c/starlingx/docs/+/850424 - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for This Week - stx-openstack Support on stx.7.0 - LP: https://bugs.launchpad.net/starlingx/+bug/1980397 - Progress since last week: - The stx-openstack application is now applied w/ k8s 1.23 - Now facing issues w/ application removal, but it doesn't seem related to the recent changes - New LP opened: https://bugs.launchpad.net/starlingx/+bug/1982220 - This looks an existing issue. TBC - Agreed to proceed with the code review and merge. Then continue to investigate the removal issue. - Forecast: July 22 - stx.7.0 Release Branch Creation - As per community agreement, proceeding with branch creation given we have sanity reports - Request sent on July 17: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-July/013164.html - Both Scott & Davlet are out this week. Jason Norton will start the branch creation today: July 20 - High Level Steps: - Create branch and tag/build the first RC build - Start sanity on the RC builds - Cherry-pick required fixes - Once all fixes are in, build and run final sanity - Tag final build and update CENGN to move the build under the release directory ARs from Previous Meetings - None Open Requests for Help - Build Issues: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-July/013157.html - Discussion ongoing. But not making progress this week since Scott & Davlet are both out
1 0
0 0
[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220715T013854Z
by Peng, Peng 19 Jul '22

19 Jul '22
Sanity Test from 2022-July-18 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220…) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220… Sanity Test executed on Bare Metal Environment AIO - Duplex Setup 1 TCs [PASS] Sanity Platform 09 TCs [PASS] Daily Regression Platform 10 TCs [PASS] TOTAL: [ 20 TCs ] Test case detail: PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host[controller] PASS test_swact_controller_platform PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] PASS test_push_docker_image_to_local_registry[active] PASS test_push_docker_image_to_local_registry[standby] PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_1p_1pod[2-fill-static-best-effort-None-AIO] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] Kind regards, PV Team
1 0
0 0
[Starlingx-discuss] Request to create the r/stx.7.0 release branch
by Khalil, Ghada 17 Jul '22

17 Jul '22
Hello StarlingX Build team, Given we have a successful sanity on the stx main branch, please proceed with creating the r/stx.7.0 release branch. This is in agreement with discussions in the release planning as well as the community meeting last week. Sanity Email: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-July/013161.html Thanks, Ghada
1 0
0 0
[Starlingx-discuss] Minutes: Community Call (July 13 2022)
by Khalil, Ghada 17 Jul '22

17 Jul '22
Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call July 13 2022 Standing Topics - Build - CentOS builds - Installer monolithic build issue (due to expat CVE fix) is addressed as of July 12 - LP: https://bugs.launchpad.net/starlingx/+bug/1980838 - Today's builds are passing now - Debian builds - Lock down of Debian release in stx Complete - Reviews merged - https://review.opendev.org/c/starlingx/tools/+/839126 - https://review.opendev.org/c/starlingx/root/+/844816 - Some Debian build failures were seen; likely due to the Debian upstream upgrade - Latest Debian build is still in progress. Build team will investigate if that failed. - Sanity - Sanity w/o stx-openstack - WR team was able to run an AIO-SX sanity. - Hit some issues w/ AIO-DX that are under investigation; TBD whether it's a procedural or software issue - Action: Rob to ensure sanity reports start getting sent to stx-discuss this week. - Sanity w/ stx-openstack - Blocked on https://bugs.launchpad.net/starlingx/+bug/1980397 - Gerrit Reviews in Need of Attention - Nothing brought up in the meeting today - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for This Week - stx-openstack Support on stx.7.0 - LP: https://bugs.launchpad.net/starlingx/+bug/1980397 - Actively being worked. - Made some progress: - 60% of stx-openstack pods are applying properly - Currently investigating issues w/ neutron & nova pods getting stuck; looks to be related to volume attachment - Forecast: hard to predict at this time ARs from Previous Meetings - Edge infrastructure orchestration discussion with the edge WG - Meeting on July 18 - Closed. Greg will be attending. Open Requests for Help - Nothing new on the mailing list - Incorrect public key for signed starlingX 5.0 iso: http://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013072.html - Scott prepared a high level explanation last week which will be sent to the mailing list - Topic was also generally covered in TSC. Current proposal is to add some clarification on usage to the StarlingX docs. - Greg took the action to create a Doc story board to track the suggested updates. - Consider Closed
1 0
0 0
[Starlingx-discuss] Minutes: StarlingX Release Meeting - Jul 13/2022
by Khalil, Ghada 17 Jul '22

17 Jul '22
Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Sanity - Last Update - Community Call on July 6 - Expect to have a sanity report (w/o stx-openstack) - by July 8 - Plan is to work on sanity w/ stx-openstack once fixes are available for: - https://bugs.launchpad.net/starlingx/+bug/1978409 - merged July 12 - https://bugs.launchpad.net/starlingx/+bug/1980397 - still open - Sanity w/o stx-openstack - WR team was able to run an AIO-SX sanity. - Hit some issues w/ AIO-DX that are under investigation; TBD whether it's a procedural or software issue - Action: Rob to ensure sanity reports start getting sent this week. - Sanity w/ stx-openstack - Blocked on https://bugs.launchpad.net/starlingx/+bug/1980397 stx.7.0 - Reference Links: - Release/Feature Planning: https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbI… - Release Verification: - Folder: https://drive.google.com/drive/folders/1szAP-xVZq7ebSyGJ-EHTVebMmsupSY7w - Feature Testing: https://docs.google.com/spreadsheets/d/1hXJJ4LvxhWwLIF_PHpCyxlGpfKdXtcPjlyc… - Regression Testing: https://docs.google.com/spreadsheets/d/19OQmmo5OfD1eHS8rp5uBgnVaS7i8J-NhQui… - From TSC / Community Call on July 6 - Agreed that getting stx-openstack running on stx.7.0 is a release blocker - Plans in place to address the identified issues and re-enable stx-openstack - Two key fixes required which are forecast for ~July 12 - https://bugs.launchpad.net/starlingx/+bug/1978409 - merged July 12 - https://bugs.launchpad.net/starlingx/+bug/1980397 - still open - Some WIP reviews posted. Need an update from the openstack team; expected in the community call - Upcoming Milestones - Revised - Based on discussion in Community Call on July 13 - RC1 (Branch Creation): week of July 4 >> week of July 18 (based on above sanity plans) - Final Regression: week of July 18 >> week of July 25 - Release: week of July 25 >> week of Aug 1 - Branch Creation - Option 1: Go ahead and branch the r/stx.7.0 branch - suggested by Frank - PRO: Avoid pollution from content unrelated to stx.7.0 (ex: prep for stx.8.0 features / Debian / etc) - CON: If we branch w/o a sanity, we don't have a known state of the load - Option 2: Institute a freeze on the stx main branch - suggested by Ildiko - PRO: Nothing goes in, so no pollution from unrelated content - CON: Impact to more community members who are already looking at stx.8.0 or bugs - Decision - Agreed a sanity w/o stx-openstack is sufficient for branch creation as the required stx-openstack changes are understood and in progress. - If it's not red, we can proceed with branch creation next week as per the plan discussed last week. - Bug status - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.7.0 - In good shape. Only 3 LPs open. 2 are actively being worked and 1 is pending a sanity re-reun. - Docs - Majority of doc updates have merged. - Release notes in progress. Juanita expects to send draft this week. - Blogs - Release Announcement - Prime: Ildiko - In progress - Debian OS Migration - Prime: Frank Miller - PTP Enhancements - Dual NIC Support / SyncE / Various NIC Support - Prime: Ghada Khalil - Subcloud Local Install - Prime: RamS - Action: Each prime to provide forecast for draft info for the next planning meeting: July 27 stx.8.0 - Release folder and planning spreadsheet created: - Release Folder: https://drive.google.com/drive/folders/1qbnm3Zz5JzM16Drhw4locVQhn4uk7HI1?us… - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-r… - Milestones (based on typical durations) are proposed - Milestone-1 8/29/2022 - Milestone-2 - 4wks after MS-1 9/26/2022 - Milestone-3 - 10wks after MS-2 12/5/2022 - Feature Test Complete - 4wks after MS-3 1/2/2023 - Regression Test Start - 1wk after MS-3 (in parallel w/ feature test) 12/12/2022 - Regression Test Complete - 3wks after Regression Start 1/2/2023 - RC1 - 1wk after Regression Test Complete 1/9/2023 - Final Regression Complete - 2wks after RC1 1/23/2023 - Release - 1wk after Final Regression 1/30/2023 - Dates are currently aligned with the typical release cadence - one release in Jan and one in July. - Action: Release team to review; we'll discuss again in the next - Next steps: Populate with candidate features - Action: Community / PLs to update the planning spreadsheet
1 0
0 0
[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220714T014026Z
by Peng, Peng 15 Jul '22

15 Jul '22
Sanity Test from 2022-July-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220…) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220… Sanity Test executed on Bare Metal Environment AIO - Duplex Setup 1 TCs [PASS] Sanity Platform 09 TCs [PASS] Daily Regression Platform 10 TCs [PASS] TOTAL: [ 20 TCs ] Test case detail: PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host[controller] PASS test_swact_controller_platform PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] PASS test_push_docker_image_to_local_registry[active] PASS test_push_docker_image_to_local_registry[standby] PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_1p_1pod[2-fill-static-best-effort-None-AIO] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] Kind regards, PV Team
1 0
0 0
[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220709T013733Z
by Peng, Peng 14 Jul '22

14 Jul '22
Sanity Test from 2022-July-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220…) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220… =========================================== Sanity Test executed on Bare Metal Environment AIO - Duplex Setup 1 TCs [PASS] Sanity Platform 09 TCs [PASS] Daily Regression Platform 10 TCs [PASS] TOTAL: [ 20 TCs ] Kind regards, PV Team
1 0
0 0
Re: [Starlingx-discuss] Looking for StarlingX Build Environment help for INTEL Team
by Waines, Greg 14 Jul '22

14 Jul '22
+ starlingx-discuss(a)lists.starlingx.io From: Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com> Sent: Wednesday, July 13, 2022 4:06 PM To: Little, Scott <Scott.Little(a)windriver.com>; Khalil, Ghada <Ghada.Khalil(a)windriver.com>; Sun, Austin <austin.sun(a)intel.com>; Waines, Greg <Greg.Waines(a)windriver.com>; Qi, Mingyuan <mingyuan.qi(a)intel.com>; Liu, ZhipengS <zhipengs.liu(a)intel.com>; Burla, Balendu <balendu.burla(a)intel.com>; Yu, Chengde <chengde.yu(a)intel.com>; Panech, Davlet <Davlet.Panech(a)windriver.com> Cc: Webster, Steven <Steven.Webster(a)windriver.com>; Thothadri, Ram <Ram.Thothadri(a)windriver.com>; Melnick, Ruth <Ruth.Melnick(a)windriver.com>; Jones, Bruce E <bruce.e.jones(a)intel.com>; Nowell, Anthony <Anthony.Nowell(a)windriver.com> Subject: RE: Looking for StarlingX Build Environment help for INTEL Team [Please note: This e-mail is from an EXTERNAL e-mail address] Hello Davlet, After yesterday’s call, I tried building the sriov-fec-operator package again, the BuildRequires as in the dependency packages chartmuseum, helm and openstack-helm-infra in the application spec file was commented out, therefore it did not show any errors. I rebuilt the package after adding these deps back and still shows the same error. Please refer to the same build logs that I shared in my previous email. Mouli and I discussed after the call yesterday and decided that we want to try bring up build system with centos as the host OS, then try to build packages to see if that makes any difference. @Panech, Davlet<mailto:Davlet.Panech@windriver.com> Can you please share any instructions on build system bring up steps for CentOS. Currently we are running this on a Ubuntu 16.04 as per the starlingx official build system documentation. We would like to try this in parallel while working on debugging build issues on ubuntu. Thank you, Nidhi From: Shivashankara Belur, Nidhi Sent: Monday, July 11, 2022 1:53 PM To: Scott Little <scott.little(a)windriver.com<mailto:scott.little@windriver.com>>; Khalil, Ghada <ghada.khalil(a)windriver.com<mailto:ghada.khalil@windriver.com>>; Sun, Austin <austin.sun(a)intel.com<mailto:austin.sun@intel.com>>; Waines, Greg <Greg.waines(a)windriver.com<mailto:Greg.waines@windriver.com>>; Qi, Mingyuan <mingyuan.qi(a)intel.com<mailto:mingyuan.qi@intel.com>>; Liu, ZhipengS <zhipengs.liu(a)intel.com<mailto:zhipengs.liu@intel.com>>; Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>>; Yu, Chengde <chengde.yu(a)intel.com<mailto:chengde.yu@intel.com>>; Panech, Davlet <Davlet.Panech(a)windriver.com<mailto:Davlet.Panech@windriver.com>> Cc: Webster, Steven <steven.webster(a)windriver.com<mailto:steven.webster@windriver.com>>; Ram.Thothadri <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; ruth.melnick <ruth.melnick(a)windriver.com<mailto:ruth.melnick@windriver.com>>; Jones, Bruce E <bruce.e.jones(a)intel.com<mailto:bruce.e.jones@intel.com>>; Nowell, Anthony <Anthony.Nowell(a)windriver.com<mailto:Anthony.Nowell@windriver.com>> Subject: RE: Looking for StarlingX Build Environment help for INTEL Team Hi Davlet, I’m sending build logs from last Friday that you requested. After adding the missing packages, there are still some errors and build-pkgs fails. I executed the build-pkgs a few times and collected multiple logs, attached in this email. 1. build-pkgs-serial stx-sriov-fec-operator-helm 2. build-pkgs-serial chartmuseum helm openstack-helm-infra stx-sriov-fec-operator-helm We will definitely need to schedule another debug session for this week, I suggest tomorrow between 9 AM – 11 AM (PST), which is 12 PM – 2 PM (EST). I’ll send a meeting invite, please let me know your availability. Regards, Nidhi From: Shivashankara Belur, Nidhi Sent: Wednesday, July 6, 2022 12:14 PM To: Scott Little <scott.little(a)windriver.com<mailto:scott.little@windriver.com>>; Khalil, Ghada <ghada.khalil(a)windriver.com<mailto:ghada.khalil@windriver.com>>; Sun, Austin <austin.sun(a)intel.com<mailto:austin.sun@intel.com>>; Waines, Greg <Greg.waines(a)windriver.com<mailto:Greg.waines@windriver.com>>; Qi, Mingyuan <mingyuan.qi(a)intel.com<mailto:mingyuan.qi@intel.com>>; Liu, ZhipengS <zhipengs.liu(a)intel.com<mailto:zhipengs.liu@intel.com>>; Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>>; Yu, Chengde <chengde.yu(a)intel.com<mailto:chengde.yu@intel.com>>; Panech, Davlet <Davlet.Panech(a)windriver.com<mailto:Davlet.Panech@windriver.com>> Cc: Webster, Steven <steven.webster(a)windriver.com<mailto:steven.webster@windriver.com>>; Ram.Thothadri <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; ruth.melnick <ruth.melnick(a)windriver.com<mailto:ruth.melnick@windriver.com>>; Jones, Bruce E <bruce.e.jones(a)intel.com<mailto:bruce.e.jones@intel.com>>; Nowell, Anthony <Anthony.Nowell(a)windriver.com<mailto:Anthony.Nowell@windriver.com>> Subject: RE: Looking for StarlingX Build Environment help for INTEL Team I did run just build-pkgs, before attempting with the package name, it also fails building all the pkgs due to same error. I see the following errors in every single package build. 1. ERROR: Command failed: 19:03:30 # mount -n -t tmpfs -o mode=0755 -o nr_inodes=0 -o size=11g mock_chroot_tmpfs /localdisk/loadbuild/stx_builder/fec-operator/std/mock/b3/root 1. ERROR: Command failed: 19:03:29 # /usr/bin/yum --installroot /localdisk/loadbuild/stx_builder/fec-operator/std/mock/b0/root/ --releasever 7 install @buildsys-build pigz lbzip2 bash yum python3 This 2nd error is followed by below messages, which suggests to me that the mirror is not accessible from my lab maybe due to proxy? 19:03:29 Failed to set locale, defaulting to C 19:03:29 http://127.0.0.1:8088/localdisk/loadbuild/stx_builder/fec-operator/std/resu…<https://urldefense.com/v3/__http:/127.0.0.1:8088/localdisk/loadbuild/stx_bu…> epomd.xml: [Errno 14] HTTP Error 403 - Forbidden 19:03:29 Trying other mirror. 19:03:29 To address this issue please refer to the below wiki article 19:03:29 19:03:29 https://wiki.centos.org/yum-errors<https://urldefense.com/v3/__https:/wiki.centos.org/yum-errors__;!!AjveYdw8E…> 19:03:29 19:03:29 If above article doesn't help to resolve this issue please use https://bugs.centos.org/<https://urldefense.com/v3/__https:/bugs.centos.org/__;!!AjveYdw8EvQ!dFWcSv_…>. 19:03:29 19:03:29 http://127.0.0.1:8088/localdisk/loadbuild/stx_builder/fec-operator/std/rpmb…<https://urldefense.com/v3/__http:/127.0.0.1:8088/localdisk/loadbuild/stx_bu…>: [Errno 14] HTT$ Error 403 - Forbidden 19:03:29 Trying other mirror. 19:03:29 http://127.0.0.1:8088/localdisk/designer/stx_builder/fec-operator/cgcs-root…<https://urldefense.com/v3/__http:/127.0.0.1:8088/localdisk/designer/stx_bui…>: [Errno 14] HTTP Error 403 - Forbidden 19:03:29 Trying other mirror. 19:03:29 One of the configured repositories failed (Stx-Centos-7-Distro), 19:03:29 and yum doesn't have enough cached data to continue. At this point the only 19:03:29 safe thing yum can do is fail. There are a few ways to work "fix" this: 19:03:29 19:03:29 1. Contact the upstream for the repository and get them to fix the problem. 19:03:29 19:03:29 2. Reconfigure the baseurl/etc. for the repository, to point to a working 19:03:29 upstream. This is most often useful if you are using a newer 19:03:29 distribution release than is supported by the repository (and the 19:03:29 packages for the previous distribution release still work). 19:03:29 19:03:29 3. Run the command with the repository temporarily disabled 19:03:29 yum --disablerepo=StxCentos7Distro ... 19:03:29 19:03:29 4. Disable the repository permanently, so yum won't use it by default. Yum 19:03:29 will then just ignore the repository until you permanently enable it 19:03:29 again or use --enablerepo for temporary usage: 19:03:29 19:03:29 yum-config-manager --disable StxCentos7Distro 19:03:29 or 19:03:29 subscription-manager repos --disable=StxCentos7Distro 19:03:29 19:03:29 5. Configure the failing repository to be skipped, if it is unavailable. 19:03:29 Note that yum will try to contact the repo. when it runs most commands, 19:03:29 so will have to try and fail each time (and thus. yum will be be much 19:03:29 slower). If it is a very temporary problem though, this is often a nice 19:03:29 compromise: 19:03:29 19:03:29 yum-config-manager --save --setopt=StxCentos7Distro.skip_if_unavailable=true 19:03:29 19:03:29 failure: repodata/repomd.xml from StxCentos7Distro: [Errno 256] No more mirrors to try. 19:03:29 http://127.0.0.1:8088/localdisk/designer/stx_builder/fec-operator/cgcs-root…<https://urldefense.com/v3/__http:/127.0.0.1:8088/localdisk/designer/stx_bui…>: [Errno 14] HTTP Error 403 - Forbidden 19:03:29 Regards, Nidhi From: Scott Little <scott.little(a)windriver.com<mailto:scott.little@windriver.com>> Sent: Wednesday, July 6, 2022 7:09 AM To: Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com<mailto:nidhi.shivashankara.belur@intel.com>>; Khalil, Ghada <ghada.khalil(a)windriver.com<mailto:ghada.khalil@windriver.com>>; Sun, Austin <austin.sun(a)intel.com<mailto:austin.sun@intel.com>>; Waines, Greg <Greg.waines(a)windriver.com<mailto:Greg.waines@windriver.com>>; Qi, Mingyuan <mingyuan.qi(a)intel.com<mailto:mingyuan.qi@intel.com>>; Liu, ZhipengS <zhipengs.liu(a)intel.com<mailto:zhipengs.liu@intel.com>>; Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>>; Yu, Chengde <chengde.yu(a)intel.com<mailto:chengde.yu@intel.com>>; Panech, Davlet <Davlet.Panech(a)windriver.com<mailto:Davlet.Panech@windriver.com>> Cc: Webster, Steven <steven.webster(a)windriver.com<mailto:steven.webster@windriver.com>>; Ram.Thothadri <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; ruth.melnick <ruth.melnick(a)windriver.com<mailto:ruth.melnick@windriver.com>>; Jones, Bruce E <bruce.e.jones(a)intel.com<mailto:bruce.e.jones@intel.com>>; Nowell, Anthony <Anthony.Nowell(a)windriver.com<mailto:Anthony.Nowell@windriver.com>> Subject: Re: Looking for StarlingX Build Environment help for INTEL Team Did you do a full 'build-pkgs' before attempting 'build-pkgs <pkg-name>' ? Your first build should build everything. Scott On 2022-07-05 8:23 p.m., Shivashankara Belur, Nidhi wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Scott, Quick update from today’s build, * Resolved all issues related to “DOS” formatting. * build-pkgs moved forward and able to fix some mistakes in our operator source code .spec file 00:05:56 ==== Update repodata complete ===== 00:05:56 00:05:56 Successfully built 1 packages: 00:05:56 stx-sriov-fec-operator-helm 00:05:56 00:05:56 Compiled src.rpm's can be found here: /localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS ######## Wed Jul 6 00:05:56 UTC 2022: build-srpm-parallel --std was successful * build-pkgs of our fec-operator now fails at the same step as cert-manager. 00:06:16 b0: Mock Version: 1.4.16 00:06:16 b0: INFO: Mock Version: 1.4.16 00:06:16 b0: Start: yum install 00:06:16 b0: ERROR: Command failed: 00:06:16 b0: # /usr/bin/yum --installroot /localdisk/loadbuild/stx_builder/fec-operator/std/mock/b0/root/ --relea sever 7 install @buildsys-build pigz lbzip2 bash yum python3 00:06:16 b0: Failed to set locale, defaulting to C 00:06:16 b0: http://127.0.0.1:8088/localdisk/loadbuild/stx_builder/fec-operator/std/resu…<https://urldefense.com/v3/__http:/127.0.0.1:8088/localdisk/loadbuild/stx_bu…> or-4.0-std/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden 00:06:16 b0: Trying other mirror. 00:06:16 b0: To address this issue please refer to the below wiki article 00:06:16 b0: 00:06:16 b0: https://wiki.centos.org/yum-errors<https://urldefense.com/v3/__https:/wiki.centos.org/yum-errors__;!!AjveYdw8E…> 00:06:16 b0: 00:06:16 b0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/<https://urldefense.com/v3/__https:/bugs.centos.org/__;!!AjveYdw8EvQ!ZePVDJS…>. 00:06:16 b0: 00:06:16 b0: http://127.0.0.1:8088/localdisk/loadbuild/stx_builder/fec-operator/std/rpmb…<https://urldefense.com/v3/__http:/127.0.0.1:8088/localdisk/loadbuild/stx_bu…> .xml: [Errno 14] HTTP Error 403 - Forbidden 00:06:16 b0: Trying other mirror. 00:06:16 b0: http://127.0.0.1:8088/localdisk/designer/stx_builder/fec-operator/cgcs-root…<https://urldefense.com/v3/__http:/127.0.0.1:8088/localdisk/designer/stx_bui…> ta/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden 00:06:16 b0: Trying other mirror. 00:06:16 b0: failure: repodata/repomd.xml from StxCentos7Distro: [Errno 256] No more mirrors to try. 00:06:16 b0: http://127.0.0.1:8088/localdisk/designer/stx_builder/fec-operator/cgcs-root…<https://urldefense.com/v3/__http:/127.0.0.1:8088/localdisk/designer/stx_bui…> ta/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden 00:06:16 b0: 00:06:16 mock_update_or_init: out 00:06:16 00:06:34 ===== wait for last jobs in iteration 1 to complete ===== 00:06:34 End build on 'b0': /localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/stx-sriov-fec-operato r-helm-1.0-2.tis.src.rpm 00:06:34 Error building stx-sriov-fec-operator-helm-1.0-2.tis.src.rpm on 'b0'. 00:06:34 Will try to build again (if some other package will succeed). 00:06:34 ===== iteration 1 complete ===== 00:06:34 failed=['/localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/build-info-1.0-4.tis.src.rpm', '/localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/stx-sriov-fec-operator-helm-1.0-2.tis.src.rpm'] 00:06:34 to_be_built=['/localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/build-info-1.0-4.tis.src.r pm', '/localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/stx-sriov-fec-operator-helm-1.0-2.tis.src.r pm'] 00:06:34 00:06:34 *** Build Failed *** 00:06:34 Tried 1 times - following pkgs could not be successfully built: 00:06:34 *** Build Failed *** 00:06:34 /localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/build-info-1.0-4.tis.src.rpm 00:06:34 /localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/stx-sriov-fec-operator-helm-1.0-2.tis.sr<https://urldefense.com/v3/__http:/stx-sriov-fec-operator-helm-1.0-2.tis.sr_…> c.rpm 00:06:34 00:06:34 00:06:34 Results out to: /localdisk/loadbuild/stx_builder/fec-operator/std/results/stx_builder-fec-operator-4.0-st d 00:06:34 00:06:34 Pkgs built: 0 00:06:34 dirname: missing operand 00:06:34 Try 'dirname --help' for more information. 00:06:34 Recreate repodata 00:06:35 00:06:35 Failed to build packages: stx-sriov-fec-operator-helm-1.0-2.tis.src.rpm build-info-1.0-4.tis.src.rpm ######## Wed Jul 6 00:06:36 UTC 2022: build-rpm-parallel --std failed with rc=1 Wed Jul 6 00:06:36 UTC 2022: build-rpm-parallel --std failed with rc=1 Can we have another live debug session tomorrow to see further into this issue? Thank you, Nidhi From: Scott Little <scott.little(a)windriver.com><mailto:scott.little@windriver.com> Sent: Tuesday, July 5, 2022 12:52 PM To: Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com><mailto:nidhi.shivashankara.belur@intel.com>; Khalil, Ghada <ghada.khalil(a)windriver.com><mailto:ghada.khalil@windriver.com>; Sun, Austin <austin.sun(a)intel.com><mailto:austin.sun@intel.com>; Waines, Greg <Greg.waines(a)windriver.com><mailto:Greg.waines@windriver.com>; Qi, Mingyuan <mingyuan.qi(a)intel.com><mailto:mingyuan.qi@intel.com>; Liu, ZhipengS <zhipengs.liu(a)intel.com><mailto:zhipengs.liu@intel.com>; Burla, Balendu <balendu.burla(a)intel.com><mailto:balendu.burla@intel.com>; Yu, Chengde <chengde.yu(a)intel.com><mailto:chengde.yu@intel.com>; Panech, Davlet <Davlet.Panech(a)windriver.com><mailto:Davlet.Panech@windriver.com> Cc: Webster, Steven <steven.webster(a)windriver.com><mailto:steven.webster@windriver.com>; Ram.Thothadri <Ram.Thothadri(a)windriver.com><mailto:Ram.Thothadri@windriver.com>; ruth.melnick <ruth.melnick(a)windriver.com><mailto:ruth.melnick@windriver.com>; Jones, Bruce E <bruce.e.jones(a)intel.com><mailto:bruce.e.jones@intel.com>; Nowell, Anthony <Anthony.Nowell(a)windriver.com><mailto:Anthony.Nowell@windriver.com> Subject: Re: Looking for StarlingX Build Environment help for INTEL Team Within the build container, the first place it would have been copied is $HOME/buildrc . That file initializes your environment variables within the container. It should remain confined to the environment variables after that as far as I can recall. That file should be reset if you clean and recreate the build container. If that procedure doesn't fix $HOME/buildrc, perhaps deleting and recreating the image from which the container is launched might also be required. Let me know if you find that to be the case. On 2022-07-05 15:05, Shivashankara Belur, Nidhi wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Scott, Thank you for providing the feedback on remaining issues. It was a federal holiday yesterday and I’m trying the fixes you mentioned right now. I’ll send another update once it completes. If any issues still remain, we would need a follow up call tomorrow. However, I still see this error pops up, even after applying the ff as unix on localrc find: ‘/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock \r’: No such file or directory Not quite sure how to find which other file could have been edited on windows. Regards, Nidhi From: Scott Little <scott.little(a)windriver.com><mailto:scott.little@windriver.com> Sent: Tuesday, July 5, 2022 10:20 AM To: Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com><mailto:nidhi.shivashankara.belur@intel.com>; Khalil, Ghada <ghada.khalil(a)windriver.com><mailto:ghada.khalil@windriver.com>; Sun, Austin <austin.sun(a)intel.com><mailto:austin.sun@intel.com>; Waines, Greg <Greg.waines(a)windriver.com><mailto:Greg.waines@windriver.com>; Qi, Mingyuan <mingyuan.qi(a)intel.com><mailto:mingyuan.qi@intel.com>; Liu, ZhipengS <zhipengs.liu(a)intel.com><mailto:zhipengs.liu@intel.com>; Burla, Balendu <balendu.burla(a)intel.com><mailto:balendu.burla@intel.com>; Yu, Chengde <chengde.yu(a)intel.com><mailto:chengde.yu@intel.com>; Panech, Davlet <Davlet.Panech(a)windriver.com><mailto:Davlet.Panech@windriver.com> Cc: Webster, Steven <steven.webster(a)windriver.com><mailto:steven.webster@windriver.com>; Ram.Thothadri <Ram.Thothadri(a)windriver.com><mailto:Ram.Thothadri@windriver.com>; ruth.melnick <ruth.melnick(a)windriver.com><mailto:ruth.melnick@windriver.com>; Jones, Bruce E <bruce.e.jones(a)intel.com><mailto:bruce.e.jones@intel.com>; Nowell, Anthony <Anthony.Nowell(a)windriver.com><mailto:Anthony.Nowell@windriver.com> Subject: Re: Looking for StarlingX Build Environment help for INTEL Team Do you need a follow up call ? Scott On 2022-07-01 17:39, Shivashankara Belur, Nidhi wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Ghada, Please find below detail description with error logs of all issues along with 1 line “current status” for each issue. Build system errors: 1. Download source code repositories, step 3: synchronize the repository (repo sync -j`nproc`). This step fails to download yocto linux repository, therefore fails. Resolved: Replaced “git” with “https” in the manifest default.xml file, another pointer is to run the command “repo sync” without any arguments as “-j” has some known issues. Resolution was given by WR team on 6/29/22 live debug session (attendees: Davelet, Scott, Steven) 2. Download Packages, download_mirror.sh<https://urldefense.com/v3/__http:/download_mirror.sh__;!!AjveYdw8EvQ!fn18tG…> had multiple failures “permission denied” due to a root privilege docker access issue. Resolved: Running the following command, adding env variables for sudo as well as proxies. cd $MY_REPO_ROOT_DIR/stx-tools/centos-mirror-tools && sudo bash -c "source env_sudo.sh<https://urldefense.com/v3/__http:/env_sudo.sh__;!!AjveYdw8EvQ!fn18tGZLvHRAP…> && bash download_mirror.sh" cat env_sudo.sh<https://urldefense.com/v3/__http:/env_sudo.sh__;!!AjveYdw8EvQ!fn18tGZLvHRAP…> export MY_REPO_ROOT_DIR=/localdisk/designer/stx_builder/fec-operator export MY_REPO=/localdisk/designer/stx_builder/fec-operator/cgcs-root export MY_WORKSPACE=/localdisk/loadbuild/stx_builder/fec-operator export http_proxy=http://proxy-chain.intel.com:911<https://urldefense.com/v3/__http:/proxy-chain.intel.com:911__;!!AjveYdw8EvQ…> export https_proxy=http://proxy-chain.intel.com:911<https://urldefense.com/v3/__http:/proxy-chain.intel.com:911__;!!AjveYdw8EvQ…> Resolution was given by WR team on 6/29/22 live debug session (attendees: Davelet, Scott, Steven) 3. Download packages in the above step had some failures, resolved it by manually downloading and moving the following rpms to “downloads” (Not verified by WR) [stx_builder@4df2aa3dafa0 centos-mirror-tools]$ cat logs/*_failmoved_*.log fail_move_srpm:bash-4.2.46-34.el7.x86_64.rpm fail_move_srpm:linuxptp-2.0-2.el7.src.rpm fail_move_srpm:net-tools-2.0-0.24.20131004git.el7.src.rpm fail_move_srpm:openldap-2.4.44-20.el7.tis.9.x86_64.rpm fail_move_srpm:openldap-2.4.44-20.el7.x86_64.rpm fail_move_srpm:openssh-7.4p1-21.el7.src.rpm fail_move_srpm:puppet-firewall-1.8.2-2.2f892e9git.el7.src.rpm fail_move_srpm:python-2.7.5-89.el7.src.rpm fail_move_srpm:rabbitmq-server-3.6.5-1.el7.src.rpm fail_move_srpm:setup-2.8.71-10.el7.src.rpm fail_move_srpm:sudo-1.8.23-10.el7_9.1.x86_64.rpm Status: Need help from WR to verify that this resolution is valid. 4. Populate downloads step shows an error [stx_builder@4df2aa3dafa0 cgcs-root]$ ln -s /import/mirrors/CentOS/stx/CentOS/downloads/ $MY_REPO/stx/ ln: failed to create symbolic link ‘/localdisk/designer/stx_builder/fec-operator/cgcs-root/stx/downloads’: File exists [stx_builder@4df2aa3dafa0 cgcs-root]$ populate_downloads.sh<https://urldefense.com/v3/__http:/populate_downloads.sh__;!!AjveYdw8EvQ!fn1…> /import/mirrors/CentOS/stx/CentOS/ mirror_dir=/import/mirrors/CentOS/stx/CentOS/ config_dir=/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config distro=centos layer=all find: ‘/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock \r’: No such file or directory find: ‘/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock \r’: No such file or directory Status: Need help from WR to resolve this issue. 5. Build packages, updating symbolic links shows similar error: [stx_builder@4df2aa3dafa0 toCOPY]$ bash generate-centos-repo.sh<https://urldefense.com/v3/__http:/generate-centos-repo.sh__;!!AjveYdw8EvQ!f…> /import/mirrors/CentOS/stx/CentOS/ mirror_dir=/import/mirrors/CentOS/stx/CentOS/ config_dir=/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config distro=centos layer=all layer_pkg_urls= layer_image_inc_urls= layer_wheels_inc_urls= find: ‘/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock\r’: No such file or directory find: ‘/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock\r’: No such file or directory find: ‘/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock\r’: No such file or directory find: ‘/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock\r’: No such file or directory rpm_lst_files=rpms_3rdparties.lst rpms_centos3rdparties.lst rpms_centos.lst rpm_lst_files_rt= layer_dirs= Status: Need help from WR to resolve this issue. 6. build-pkgs command fails for all packages, probably due to dependency on previous steps. Error logs: [stx_builder@4df2aa3dafa0 stx]$ build-pkgs stx-sriov-fec-operator-helm No changes for stx projects build-pkgs-parallel stx-sriov-fec-operator-helm Reading: /localdisk/designer/stx_builder/fec-operator/cgcs-root/build-data/build_avoidance_source BUILD_AVOIDANCE_DIR= BUILD_AVOIDANCE_HOST= BUILD_AVOIDANCE_USR= BUILD_AVOIDANCE_FLAG=0 CLEAN_FLAG=0 EDIT_FLAG=0 find: ‘/localdisk/designer/stx_builder/fec-operator/cgcs-root/stx/app-sriov-fec-operator/stx-sriov-fec-operator-helm\r/centos/’: No such file or directory find: ‘/localdisk/designer/stx_builder/fec-operator/cgcs-root/stx/app-sriov-fec-operator/stx-sriov-fec-operator-helm\r/centos/’: No such file or directory TARGETS_STD= TARGETS_RT= TARGETS_INSTALLER= TARGETS_CONTAINERS= EXTRA_ARGS_COMMON='' EXTRA_ARGS_SRPM='' EXTRA_ARGS_RPM='' TARGETS=' stx-sriov-fec-operator-helm ' TARGETS_STD=' ' TARGETS_RT=' ' TARGETS_INSTALLER=' ' TARGETS_CONTAINERS=' ' TARGETS_MISC=' stx-sriov-fec-operator-helm ' Capture build context Launching std build, logging to /localdisk/loadbuild/stx_builder/fec-operator/build-std.log ######## Fri Jul 1 21:10:15 UTC 2022: Launching build-srpms-parallel --std BUILD_AVOIDANCE_URL= /localdisk/designer/stx_builder/fec-operator/cgcs-root/build-tools/build-srpms-parallel --std stx-sriov-fec-operator-helm MAX_WORKERS=8 CLEAN_FLAG=0 21:10:17 build-srpms-parallel --std stx-sriov-fec-operator-helm 21:10:17 make: stx-sriov-fec-operator-helm 21:10:17 removed ‘/localdisk/loadbuild/stx_builder/fec-operator/std/tmp/SRPM_REBUILT_LIST_6’ ' in file '/localdisk/designer/stx_builder/fec-operator/cgcs-root/stx/app-sriov-fec-operator/centos_pkg_dirs' 21:10:29 ==== Update repodata ===== 21:10:33 Directory walk started 21:10:33 Directory walk done - 302 packages 21:10:33 Temporary output repo path: /localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/.repodata/ 21:10:33 Preparing sqlite DBs 21:10:33 Pool started (with 5 workers) 21:10:33 Pool finished 21:10:33 ==== Update repodata complete ===== 21:10:33 21:10:33 No packages required a rebuild 21:10:33 21:10:33 ERROR: (1600): failed to resolve build targets: stx-sriov-fec-operator-helm ######## Fri Jul 1 21:10:33 UTC 2022: build-srpm-parallel --std failed with rc=1 Fri Jul 1 21:10:33 UTC 2022: build-srpm-parallel --std failed with rc=1 Status: Need help from WR to resolve this issue. @Sun, Austin<mailto:austin.sun@intel.com> I got your email on proposed changes for build-system issues. I tried a few of them applicable for us. 1. We have already passed noProxy env variable for docker container 2. Download_mirror.sh<https://urldefense.com/v3/__http:/Download_mirror.sh__;!!AjveYdw8EvQ!fn18tG…> command was executed as “sudo” 3. "get_sources.sh", is not executable. Fixed this locally by changing the file mode. Question: I didn’t quite understand these two changes, feat: Modify layer build process (Ibded97db) · Gerrit Code Review (opendev.org)<https://urldefense.com/v3/__https:/review.opendev.org/c/starlingx/tools/*/8…> ; didn’t think this was applicable to us since we are not doing layer build. Do we need to do layer build ? fix: drop the relative gopath (I950184f0) · Gerrit Code Review (opendev.org)<https://urldefense.com/v3/__https:/review.opendev.org/c/starlingx/container…> ; I applied this fix locally on my system. Is this a mandatory fix ? Regards, Nidhi From: Khalil, Ghada <Ghada.Khalil(a)windriver.com><mailto:Ghada.Khalil@windriver.com> Sent: Wednesday, June 29, 2022 6:32 AM To: Sun, Austin <austin.sun(a)intel.com><mailto:austin.sun@intel.com>; Waines, Greg <Greg.waines(a)windriver.com><mailto:Greg.waines@windriver.com>; Qi, Mingyuan <mingyuan.qi(a)intel.com><mailto:mingyuan.qi@intel.com>; Liu, ZhipengS <zhipengs.liu(a)intel.com><mailto:zhipengs.liu@intel.com>; Burla, Balendu <balendu.burla(a)intel.com><mailto:balendu.burla@intel.com>; Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com><mailto:nidhi.shivashankara.belur@intel.com>; Yu, Chengde <chengde.yu(a)intel.com><mailto:chengde.yu@intel.com>; Little, Scott <Scott.Little(a)windriver.com><mailto:Scott.Little@windriver.com>; Panech, Davlet <Davlet.Panech(a)windriver.com><mailto:Davlet.Panech@windriver.com> Cc: Webster, Steven <steven.webster(a)windriver.com><mailto:steven.webster@windriver.com>; Ram.Thothadri <Ram.Thothadri(a)windriver.com><mailto:Ram.Thothadri@windriver.com>; ruth.melnick <ruth.melnick(a)windriver.com><mailto:ruth.melnick@windriver.com>; Jones, Bruce E <bruce.e.jones(a)intel.com><mailto:bruce.e.jones@intel.com>; Nowell, Anthony <Anthony.Nowell(a)windriver.com><mailto:Anthony.Nowell@windriver.com> Subject: RE: Looking for StarlingX Build Environment help for INTEL Team There was a live zoom session yesterday with @Shivashankara Belur, Nidhi<mailto:nidhi.shivashankara.belur@intel.com> and @Panech, Davlet<mailto:Davlet.Panech@windriver.com> / @Little, Scott<mailto:Scott.Little@windriver.com> to investigate the build failures as well. Can someone provide a readout of the meeting please so that everyone is on the same page? Thanks, Ghada From: Sun, Austin <austin.sun(a)intel.com<mailto:austin.sun@intel.com>> Sent: Wednesday, June 29, 2022 3:41 AM To: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>>; Qi, Mingyuan <mingyuan.qi(a)intel.com<mailto:mingyuan.qi@intel.com>>; Liu, ZhipengS <zhipengs.liu(a)intel.com<mailto:zhipengs.liu@intel.com>>; Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>>; Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com<mailto:nidhi.shivashankara.belur@intel.com>>; Yu, Chengde <chengde.yu(a)intel.com<mailto:chengde.yu@intel.com>> Cc: Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Webster, Steven <Steven.Webster(a)windriver.com<mailto:Steven.Webster@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; Melnick, Ruth <Ruth.Melnick(a)windriver.com<mailto:Ruth.Melnick@windriver.com>>; Jones, Bruce E <bruce.e.jones(a)intel.com<mailto:bruce.e.jones@intel.com>>; Little, Scott <Scott.Little(a)windriver.com<mailto:Scott.Little@windriver.com>>; Panech, Davlet <Davlet.Panech(a)windriver.com<mailto:Davlet.Panech@windriver.com>>; Nowell, Anthony <Anthony.Nowell(a)windriver.com<mailto:Anthony.Nowell@windriver.com>> Subject: RE: Looking for StarlingX Build Environment help for INTEL Team [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg and Scott : Chant has been working on build latest starlingx with layer-build in intel environment and uploaded several patches to address build issues. With these patches, Chant can build iso successfully . would you like review these patches ? https://review.opendev.org/c/starlingx/tools/+/846573<https://urldefense.com/v3/__https:/review.opendev.org/c/starlingx/tools/*/8…> https://review.opendev.org/c/starlingx/tools/+/846846<https://urldefense.com/v3/__https:/review.opendev.org/c/starlingx/tools/*/8…> https://review.opendev.org/c/starlingx/containers/+/847231<https://urldefense.com/v3/__https:/review.opendev.org/c/starlingx/container…> https://review.opendev.org/c/starlingx/tools/+/847066<https://urldefense.com/v3/__https:/review.opendev.org/c/starlingx/tools/*/8…> https://review.opendev.org/c/starlingx/tools/+/847061<https://urldefense.com/v3/__https:/review.opendev.org/c/starlingx/tools/*/8…> @Burla, Balendu<mailto:balendu.burla@intel.com> and @Shivashankara Belur, Nidhi<mailto:nidhi.shivashankara.belur@intel.com>: you can cherry-pick those patches and try build in your environment . Thanks. BR Austin Sun. From: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>> Sent: Friday, June 10, 2022 6:47 PM To: Sun, Austin <austin.sun(a)intel.com<mailto:austin.sun@intel.com>>; Qi, Mingyuan <mingyuan.qi(a)intel.com<mailto:mingyuan.qi@intel.com>>; Liu, ZhipengS <zhipengs.liu(a)intel.com<mailto:zhipengs.liu@intel.com>>; Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>>; Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com<mailto:nidhi.shivashankara.belur@intel.com>> Cc: Khalil, Ghada <ghada.khalil(a)windriver.com<mailto:ghada.khalil@windriver.com>>; Webster, Steven <steven.webster(a)windriver.com<mailto:steven.webster@windriver.com>>; Ram.Thothadri <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; ruth.melnick <ruth.melnick(a)windriver.com<mailto:ruth.melnick@windriver.com>>; Jones, Bruce E <bruce.e.jones(a)intel.com<mailto:bruce.e.jones@intel.com>>; Little, Scott <Scott.Little(a)windriver.com<mailto:Scott.Little@windriver.com>>; Panech, Davlet <Davlet.Panech(a)windriver.com<mailto:Davlet.Panech@windriver.com>>; Nowell, Anthony <Anthony.Nowell(a)windriver.com<mailto:Anthony.Nowell@windriver.com>> Subject: RE: Looking for StarlingX Build Environment help for INTEL Team thanks very much Austin. Greg. From: Sun, Austin <austin.sun(a)intel.com<mailto:austin.sun@intel.com>> Sent: Thursday, June 9, 2022 11:39 PM To: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>>; Qi, Mingyuan <mingyuan.qi(a)intel.com<mailto:mingyuan.qi@intel.com>>; Liu, ZhipengS <zhipengs.liu(a)intel.com<mailto:zhipengs.liu@intel.com>>; Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>>; Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com<mailto:nidhi.shivashankara.belur@intel.com>> Cc: Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Webster, Steven <Steven.Webster(a)windriver.com<mailto:Steven.Webster@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; Melnick, Ruth <Ruth.Melnick(a)windriver.com<mailto:Ruth.Melnick@windriver.com>>; Jones, Bruce E <bruce.e.jones(a)intel.com<mailto:bruce.e.jones@intel.com>>; Little, Scott <Scott.Little(a)windriver.com<mailto:Scott.Little@windriver.com>>; Panech, Davlet <Davlet.Panech(a)windriver.com<mailto:Davlet.Panech@windriver.com>>; Nowell, Anthony <Anthony.Nowell(a)windriver.com<mailto:Anthony.Nowell@windriver.com>> Subject: RE: Looking for StarlingX Build Environment help for INTEL Team [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg: OK. @Burla, Balendu<mailto:balendu.burla@intel.com>, and @Shivashankara Belur, Nidhi<mailto:nidhi.shivashankara.belur@intel.com>, please contact us , we can syn-cup internally . Thanks. BR Austin Sun. From: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>> Sent: Thursday, June 9, 2022 9:41 PM To: Qi, Mingyuan <mingyuan.qi(a)intel.com<mailto:mingyuan.qi@intel.com>>; Sun, Austin <austin.sun(a)intel.com<mailto:austin.sun@intel.com>>; Liu, ZhipengS <zhipengs.liu(a)intel.com<mailto:zhipengs.liu@intel.com>> Cc: Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>>; Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com<mailto:nidhi.shivashankara.belur@intel.com>>; Khalil, Ghada <ghada.khalil(a)windriver.com<mailto:ghada.khalil@windriver.com>>; Webster, Steven <steven.webster(a)windriver.com<mailto:steven.webster@windriver.com>>; Ram.Thothadri <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; ruth.melnick <ruth.melnick(a)windriver.com<mailto:ruth.melnick@windriver.com>>; Jones, Bruce E <bruce.e.jones(a)intel.com<mailto:bruce.e.jones@intel.com>>; Little, Scott <Scott.Little(a)windriver.com<mailto:Scott.Little@windriver.com>>; Panech, Davlet <Davlet.Panech(a)windriver.com<mailto:Davlet.Panech@windriver.com>>; Nowell, Anthony <Anthony.Nowell(a)windriver.com<mailto:Anthony.Nowell@windriver.com>> Subject: Looking for StarlingX Build Environment help for INTEL Team Mingyuan, Austin, Zhipeng, (Intel StarlingX folks) Balendu (Mouli) Burla and Nidhi Shivashankara Belur are new members of StarlingX from the Intel Networking(?) org who are in the process of contributing a kubernetes operator for configuring FEC in a couple of intel hardware devices. They are having difficulty setting up their StarlingX Build Environment and getting it to work. Is there any chance that you guys (who have working StarlingX Build Environments inside Intel) could help Mouli and Nidhi out in setting up their environment ? let me know, thanks a lot, Greg. From: Waines, Greg Sent: Tuesday, June 7, 2022 6:58 AM To: Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>>; Nowell, Anthony <Anthony.Nowell(a)windriver.com<mailto:Anthony.Nowell@windriver.com>> Cc: Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com<mailto:nidhi.shivashankara.belur@intel.com>>; Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Webster, Steven <Steven.Webster(a)windriver.com<mailto:Steven.Webster@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; Melnick, Ruth <Ruth.Melnick(a)windriver.com<mailto:Ruth.Melnick@windriver.com>>; Rasa, Nimalini <Nimalini.Rasa(a)windriver.com<mailto:Nimalini.Rasa@windriver.com>>; Peters, Matt <Matt.Peters(a)windriver.com<mailto:Matt.Peters@windriver.com>> Subject: RE: sriov-fec-operator plan update ? Thanks Mouli. Anthony ? I think scott or davlet have provided a bit of help to Mouli on his build-pkg issues … any chance we can get some more direct help from them in order to get over this build issue ? Greg. From: Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>> Sent: Monday, June 6, 2022 6:14 PM To: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>>; Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com<mailto:nidhi.shivashankara.belur@intel.com>> Cc: Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Webster, Steven <Steven.Webster(a)windriver.com<mailto:Steven.Webster@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; Melnick, Ruth <Ruth.Melnick(a)windriver.com<mailto:Ruth.Melnick@windriver.com>>; Rasa, Nimalini <Nimalini.Rasa(a)windriver.com<mailto:Nimalini.Rasa@windriver.com>>; Peters, Matt <Matt.Peters(a)windriver.com<mailto:Matt.Peters@windriver.com>> Subject: RE: sriov-fec-operator plan update ? [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg, We have tested the fec-operator on StarlingX platform manually using the helm chats. And we have packaged the helm chats as system application with the help of documentation and Teresa for integration. However, To test that, we need a local build environment and we are struck in brining up the local build environment and looking for help from WR/STX to resolve the build-pkg issues since 4 weeks. Without resolving those build issues, we can not submit a working code. Although, Nidhi will submit the code for review in a draft status. Assuming the local build issues are resolved, from there on we can try to submit the working code, review, tested in two weeks. Can someone help in resolving our local build-pkg issues? Nidhi can setup a debug call, if that work for your team members. NOTE: these build-pkg issues are not related to fec-operator, trying to build the default iso image with latest master. Best regards, Mouli. From: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>> Sent: Monday, June 6, 2022 6:12 AM To: Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com<mailto:nidhi.shivashankara.belur@intel.com>>; Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>> Cc: Khalil, Ghada <ghada.khalil(a)windriver.com<mailto:ghada.khalil@windriver.com>>; Webster, Steven <steven.webster(a)windriver.com<mailto:steven.webster@windriver.com>>; Ram.Thothadri <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; ruth.melnick <ruth.melnick(a)windriver.com<mailto:ruth.melnick@windriver.com>>; Rasa, Nimalini <Nimalini.Rasa(a)windriver.com<mailto:Nimalini.Rasa@windriver.com>>; Peters, Matt <matt.peters(a)windriver.com<mailto:matt.peters@windriver.com>> Subject: RE: sriov-fec-operator plan update ? Thanks for the status update. What I’m looking for though is a committed date for - code submitted, merged and tested, and - customer documentation updated. Do you have a forecast for that date ? Greg. From: Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com<mailto:nidhi.shivashankara.belur@intel.com>> Sent: Friday, June 3, 2022 2:18 PM To: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>>; Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>> Cc: Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Webster, Steven <Steven.Webster(a)windriver.com<mailto:Steven.Webster@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; Melnick, Ruth <Ruth.Melnick(a)windriver.com<mailto:Ruth.Melnick@windriver.com>>; Rasa, Nimalini <Nimalini.Rasa(a)windriver.com<mailto:Nimalini.Rasa@windriver.com>>; Peters, Matt <Matt.Peters(a)windriver.com<mailto:Matt.Peters@windriver.com>> Subject: RE: sriov-fec-operator plan update ? [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg, I am currently blocked by 2 issues, 1. Build-pkgs tool is failing 2. System application-apply fails to bring up operator pods. Pending items: 1. Build fec-operator docker images for STX – WIP: * Imported pre-built docker images for the operator and pushed it with tag registry.local. But system application-apply fails here. * Include build images into build iso – Not yet started. I have 2 active email threads for these 2 issues. Contact person for build issues is Scott Little, there isn’t much progress here yet. Can you please include a contact who can help resolve this issue through a live debug call ? Contact person for system application-apply failure is Teresa Ho, we are doing 1:1 debug sessions since yesterday. Some reasons for failure identified, we will meet again on Monday to try some solutions. Regards, Nidhi From: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>> Sent: Monday, May 30, 2022 7:39 AM To: Burla, Balendu <balendu.burla(a)intel.com<mailto:balendu.burla@intel.com>> Cc: Khalil, Ghada <ghada.khalil(a)windriver.com<mailto:ghada.khalil@windriver.com>>; Webster, Steven <steven.webster(a)windriver.com<mailto:steven.webster@windriver.com>>; Ram.Thothadri <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; ruth.melnick <ruth.melnick(a)windriver.com<mailto:ruth.melnick@windriver.com>>; Shivashankara Belur, Nidhi <nidhi.shivashankara.belur(a)intel.com<mailto:nidhi.shivashankara.belur@intel.com>>; Rasa, Nimalini <Nimalini.Rasa(a)windriver.com<mailto:Nimalini.Rasa@windriver.com>>; Peters, Matt <matt.peters(a)windriver.com<mailto:matt.peters@windriver.com>> Subject: sriov-fec-operator plan update ? Hey Mouli, Wrt your ‘FEC Operator Integration to enable FEC Device Configurability’ ( https://storyboard.openstack.org/#!/story/2009749<https://urldefense.com/v3/__https:/storyboard.openstack.org/*!/story/200974…> ), are you still tracking to your ‘Code Merge’ (5/27) and ‘Feature Tested’ (6/6) dates in the StarlingX STX7.0 Feature Planning Spreadsheet ( ROW 36 of https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbI…<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/171PJAu9S…> ) ? Although there is no hard commitment in StarlingX for the delivery of this functionality, there are hard commitments wrt this functionality being available in Wind River’s commercial product based on StarlingX. I’d like to confirm that your feature delivery dates are still accurate and you are getting all the support you need from the StarlingX projects, so I can make sure your dates align with Wind River commercial product dates. let me know, Greg.
1 0
0 0
[Starlingx-discuss] [docs] [meeting] Docs team notes 13-July-22
by Balaraj, Juanita 13 Jul '22

13 Jul '22
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<https://urldefense.com/v3/__https:/wiki.openstack.org/wiki/Starlingx/Meetin…> [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation<https://urldefense.com/v3/__https:/etherpad.openstack.org/p/stx-documentati…> Thanks, Juanita Balaraj ============ 13-July-22 - Stx 7.0 GA date is July 25th - AR Juanita to review Stx 7.0 Release checklist - Need to update the Installation Guide to display Stx 7.0 once docs are merged : https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.… - AR Ron - Version drop-down on https://docs.starlingx.io/ to be updated to display Stx 7.0 - AR Ron - Stx Release Notes - AR Juanita - To automate the updates for the Introduction Guide - AR Ron - Scott to cut the Stx 7.0 docs branch - To confirm the date - No Cherry picks this week. Waiting for reviews to merge. - Team to address LP Bugs - https://bugs.launchpad.net/starlingx/+bug/1932314; https://bugs.launchpad.net/starlingx/+bug/1951165 - AR Elaine to close these bugs - On hold - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs for a list of pending Doc Bugs - https://bugs.launchpad.net/starlingx/+bug/1980666 - AR Elisa - Introduction Guide to be updated with new features for Stx 7.0 - Team and pulled in from STx 7.0 Release Notes - Ron to automate it - TAI clock updates - Juanita to discuss with Ghada regarding https://storyboard.openstack.org/#!/story/2010033 - Operations Guide Archive - On Hold until further clarifications are discussed - https://review.opendev.org/c/starlingx/docs/+/822030 - Ron in the process of updating the Glossary File to keep it current; https://review.opendev.org/c/starlingx/docs/+/848772 - https://review.opendev.org/c/starlingx/docs/+/849003 - AR Juanita to confirm if this needs to be cherrypicked to dsr6 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss(a)lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss<https://urldefense.com/v3/__http:/lists.starlingx.io/cgi-bin/mailman/listin…>
1 0
0 0
  • ← Newer
  • 1
  • ...
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • ...
  • 823
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.