From alexandru.dimofte at intel.com Wed Dec 1 09:19:23 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 1 Dec 2021 09:19:23 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211130T011303Z Message-ID: Sanity Test from 2021-November-30 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211130T011303Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211130T011303Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz The build is affected by: https://bugs.launchpad.net/starlingx/+bug/1942480 - Alarm 800.010 Potential data loss. No available OSDs in storage replication group group-0 https://bugs.launchpad.net/starlingx/+bug/1952400 - Alarm 750.002 Application Apply Failure for cert-manager Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Wed Dec 1 09:21:09 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 1 Dec 2021 09:21:09 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211201T041648Z Message-ID: Sanity Test from 2021-December-01 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211201T041648Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211201T041648Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz The build is affected by: https://bugs.launchpad.net/starlingx/+bug/1942480 - Alarm 800.010 Potential data loss. No available OSDs in storage replication group group-0 https://bugs.launchpad.net/starlingx/+bug/1952400 - Alarm 750.002 Application Apply Failure for cert-manager Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From Bill.Zvonar at windriver.com Wed Dec 1 12:33:52 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 1 Dec 2021 12:33:52 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 1, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up later today. Please feel free to add other 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=20211201T1500? [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From Thiago.Brito at windriver.com Wed Dec 1 15:13:03 2021 From: Thiago.Brito at windriver.com (Brito, Thiago) Date: Wed, 1 Dec 2021 15:13:03 +0000 Subject: [Starlingx-discuss] Fw: installed .. but docs not working.. In-Reply-To: References: Message-ID: Just fwd to the list since the first time I replied just to Sashi. ________________________________ From: Brito, Thiago Sent: Monday, November 29, 2021 5:42 PM To: Shashi Dahal Subject: Re: [Starlingx-discuss] installed .. but docs not working.. Hi Sashi, stx-openstack is distributed as an application for StarlingX. You will find the instructions on how to download and install the app on your StarlingX here: https://docs.starlingx.io/deploy_install_guides/r5_release/openstack/install.html Btw, plain StarlingX has an instance of Horizon on it as well to manage the cluster, patch upgrades, fault management, and some other stuff. The dashboard has a very different content from the Openstack one. Install StarlingX OpenStack ? StarlingX documentation Install StarlingX OpenStack?. These instructions assume that you have completed the following OpenStack-specific configuration tasks that are required by the underlying StarlingX Kubernetes platform: docs.starlingx.io Best regards, ________________________________ From: Shashi Dahal Sent: Monday, November 29, 2021 5:08 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] installed .. but docs not working.. [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, So finally I have managed to install starlingX. Followed all the docs and now i can login to horizon. But under project .. there is only API access .. there are no services .... like zero .. and I was not able to find anywhere in the documentation how to add/enable/config openstack services. this page: https://docs.starlingx.io/system_configuration/openstack/system-configuration-overview.html points me to system helm-override-list stx-openstack [sysadmin at controller-0 ~(keystone_admin)]$ system helm-override-list stx-openstack Application not found: stx-openstack Can someone point me to the correct steps/documentation after install to get openstack services and kubernetes running ? -- Cheers, Shashi -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Dec 1 15:14:25 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 1 Dec 2021 15:14:25 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 1, 2021) In-Reply-To: References: Message-ID: >From today's call... * Standing Topics * Build/Sanity * sanity still red * details on https://etherpad.opendev.org/p/stx-releases from today's release team meeting * https://bugs.launchpad.net/starlingx/+bug/1942480 seems to be an automation/sequencing thing * https://bugs.launchpad.net/starlingx/+bug/1952400 is under investigation (Sabeel, Bob) * builds are good * Gerrit Reviews in Need of Attention * nothing new this week * Topics for this Week * stx.6.0 release status (https://etherpad.opendev.org/p/stx-releases) * milestone 3 not quite there sanity needs to get out of red, per above * release notes - we'll ask Mary for an update on this offline * the release branch won't be cut until we get 2 green or yellow sanities * see the release team etherpad for more details from today's meeting * ARs from Previous Meetings * nothing new this week * Open Requests for Help * installed .. but docs not working.. * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-November/012465.html * Thiago responded directly, will re-send to include the mailing list as well on the response -----Original Message----- From: Zvonar, Bill Sent: Wednesday, December 1, 2021 7:34 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Dec 1, 2021) Hi all, reminder of the weekly TSC/Community calls coming up later today. Please feel free to add other 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=20211201T1500? [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From fungi at yuggoth.org Wed Dec 1 19:53:40 2021 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 1 Dec 2021 19:53:40 +0000 Subject: [Starlingx-discuss] IMA signatures (was: how to deal with loop dependent in building stage) In-Reply-To: <20210923161125.xhe2hrxhyhuxdorn@yuggoth.org> References: <9b09592c-05d4-05c2-e799-36084e2cde7e@windriver.com> <0da9d1bb-2a90-f1a2-91aa-23055b8bb83a@windriver.com> <91aa695a-9ef2-3945-7a73-542cd3838db8@windriver.com> <0310a376-1e04-5e53-73f2-a95cd774eace@windriver.com> <9a772329-a7e7-5d02-be1a-d1812c5362e4@windriver.com> <31b5e238-f4d2-d53f-2aab-9d75a3cf3f2e@windriver.com> <20210923144339.gnaeh3punbsvyylq@yuggoth.org> <65d56234-c3fa-4f0b-1f5a-c58baa8c2398@windriver.com> <20210923161125.xhe2hrxhyhuxdorn@yuggoth.org> Message-ID: <20211201195340.36zpqt2u5evtw6jg@yuggoth.org> On 2021-09-23 16:11:25 +0000 (+0000), Jeremy Stanley wrote: [...] > Anyway, this looks like a relevant feature request for it along with > a proof of concept implementation (albeit with 7 years of cobwebs): > > https://bugs.debian.org/766267 > https://lists.debian.org/debian-dpkg/2014/08/threads.html#00006 > > The implementation looks fairly straightforward, the file signatures > would be generated when the packages are assembled and stored with > the file checksums normally tracked, then at installation those > signatures would be copied into extended filesystem attributes for > the relevant files, to be consumed by the kernel. > > If this is of interest to the StarlingX community, it might be an > activity worth reigniting in Debian. It looks like the developers at > IBM who originally proposed support for it did not pursue it > further, at least that I can find any record of. A thread on the oss-security mailing list this week reminded me of the earlier discussion here. Interestingly, it's a developer at Red Hat questioning the (f)utility of IMA signatures on files: https://www.openwall.com/lists/oss-security/2021/11/30/1 -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From scott.little at windriver.com Wed Dec 1 20:37:40 2021 From: scott.little at windriver.com (Scott Little) Date: Wed, 1 Dec 2021 15:37:40 -0500 Subject: [Starlingx-discuss] IMA signatures (was: how to deal with loop dependent in building stage) In-Reply-To: <20211201195340.36zpqt2u5evtw6jg@yuggoth.org> References: <9b09592c-05d4-05c2-e799-36084e2cde7e@windriver.com> <0da9d1bb-2a90-f1a2-91aa-23055b8bb83a@windriver.com> <91aa695a-9ef2-3945-7a73-542cd3838db8@windriver.com> <0310a376-1e04-5e53-73f2-a95cd774eace@windriver.com> <9a772329-a7e7-5d02-be1a-d1812c5362e4@windriver.com> <31b5e238-f4d2-d53f-2aab-9d75a3cf3f2e@windriver.com> <20210923144339.gnaeh3punbsvyylq@yuggoth.org> <65d56234-c3fa-4f0b-1f5a-c58baa8c2398@windriver.com> <20210923161125.xhe2hrxhyhuxdorn@yuggoth.org> <20211201195340.36zpqt2u5evtw6jg@yuggoth.org> Message-ID: Thanks for the link.?? Good read. Scott On 2021-12-01 2:53 p.m., Jeremy Stanley wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > On 2021-09-23 16:11:25 +0000 (+0000), Jeremy Stanley wrote: > [...] >> Anyway, this looks like a relevant feature request for it along with >> a proof of concept implementation (albeit with 7 years of cobwebs): >> >> https://bugs.debian.org/766267 >> https://lists.debian.org/debian-dpkg/2014/08/threads.html#00006 >> >> The implementation looks fairly straightforward, the file signatures >> would be generated when the packages are assembled and stored with >> the file checksums normally tracked, then at installation those >> signatures would be copied into extended filesystem attributes for >> the relevant files, to be consumed by the kernel. >> >> If this is of interest to the StarlingX community, it might be an >> activity worth reigniting in Debian. It looks like the developers at >> IBM who originally proposed support for it did not pursue it >> further, at least that I can find any record of. > A thread on the oss-security mailing list this week reminded me of > the earlier discussion here. Interestingly, it's a developer at Red > Hat questioning the (f)utility of IMA signatures on files: > > https://www.openwall.com/lists/oss-security/2021/11/30/1 > > -- > Jeremy Stanley > > _______________________________________________ > 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 maryx.camp at intel.com Thu Dec 2 00:14:41 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 2 Dec 2021 00:14:41 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 01-Dec-21 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 ========== 01-Dec-21?? . All -- reviews merged since last meeting:? 18?????https://review.opendev.org/q/project:starlingx/docs+status:merged ???????????????? . All -- bug status -- 9?total - team agrees to defer all low priority LP until the upstreaming effort is completed.? Status/questions/opens Release Notes for R6.0 ?? Mary will start a review with a WIP draft. ?? Add bullet saying CPU Manager for Kubernetes is no longer supported (deprecated). ?? New limitation coming from Chris Friesen (may be differences between upstream & downstream RN and how to handle).? ???Juanita will confirm with him and keep me posted. (Docker registry for GHCR.io)?? How to handle Install Guides for R6.0? ? Current plan is to defer branching the docs repo until the actual release (instead of 2-3 weeks early like the software does). ? This idea came from Scott,?Greg and the docs team.? ? We will continue as we have now (latest/7 and supported/6 on main branch, all others on R6 branch). ? Mary find notes about updating version dropdown in the theme.? ?? Mary has ARs to remove the old guides into archive/deprecated folder and do reviews.? WR team did a training for gerrit reviews - approx 55 people attended! They will likely do some follow-up?sessions also.? Notification of changes (Ron) ? Recently?there was a change to the constraints file that impacted us. How could we find out about these in advance?? ? Find out if the infra/oslo?team has meeting minutes that we could monitor?? ? What are the issues we are concerned about:? version of sphinx, theme changes.?Ask if they can provide some guidance for what to watch for.? ? Is it oslo team only or is there another team that covers theme?? ? During the meeting, we looked at: ??????http://lists.openstack.org/pipermail/openstack-discuss/? ??????https://meetings.opendev.org/meetings/oslo/2021/??? ? After the meeting, I found this in the OpenStack Projects list:?https://governance.openstack.org/tc/reference/projects/oslo.html ? The Oslo team does support theme.? From fungi at yuggoth.org Thu Dec 2 00:26:18 2021 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 2 Dec 2021 00:26:18 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 01-Dec-21 In-Reply-To: References: Message-ID: <20211202002618.gu6zxbkzuzksignt@yuggoth.org> On 2021-12-02 00:14:41 +0000 (+0000), Camp, MaryX wrote: [...] > Notification of changes (Ron) > ? Recently?there was a change to the constraints file that > impacted us. How could we find out about these in advance?? > ? Find out if the infra/oslo?team has meeting minutes that we > could monitor?? > ? What are the issues we are concerned about:? version of sphinx, > theme changes.?Ask if they can provide some guidance for what > to watch for.? > ? Is it oslo team only or is there another team that covers > theme?? > ? During the meeting, we looked at: > ????http://lists.openstack.org/pipermail/openstack-discuss/? > ????https://meetings.opendev.org/meetings/oslo/2021/??? > ? After the meeting, I found this in the OpenStack Projects > list: > https://governance.openstack.org/tc/reference/projects/oslo.html > ? The Oslo team does support theme.? Those are some of the reasons I suggested StarlingX may want to consider forking that theme, stripping out the OpenStack-only bits, and moving it into the docs repo. I started a PoC of that with https://review.opendev.org/750005 and https://review.opendev.org/750006 but did not find time to finish it. The original has almost certainly diverged enough since that time that the changes would need to be recreated from scratch anyway at this point. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From alexandru.dimofte at intel.com Thu Dec 2 10:14:40 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 2 Dec 2021 10:14:40 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211202T023751Z Message-ID: Sanity Test from 2021-December-02 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211202T023751Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211202T023751Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz The build is affected by: https://bugs.launchpad.net/starlingx/+bug/1942480 - Alarm 800.010 Potential data loss. No available OSDs in storage replication group group-0 https://bugs.launchpad.net/starlingx/+bug/1952400 - Alarm 750.002 Application Apply Failure for cert-manager Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From Frank.Miller at windriver.com Thu Dec 2 14:52:18 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 2 Dec 2021 14:52:18 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211202T023751Z In-Reply-To: References: Message-ID: Alex: I cannot tell from your sanity emails which config was used for each sanity. An initial look at LP 1952400 is leading to a theory that this is only an issue for virtual labs and not bare metal servers. Please include which configuration is having which of the LPs. In particular are you seeing cert-manager apply failures happening when running on a bare metal server? If yes then please also attach the logs for that sanity run to the LP. Frank From: Dimofte, Alexandru Sent: Thursday, December 2, 2021 5:15 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211202T023751Z [Please note: This e-mail is from an EXTERNAL e-mail address] Sanity Test from 2021-December-02 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211202T023751Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211202T023751Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz The build is affected by: https://bugs.launchpad.net/starlingx/+bug/1942480 - Alarm 800.010 Potential data loss. No available OSDs in storage replication group group-0 https://bugs.launchpad.net/starlingx/+bug/1952400 - Alarm 750.002 Application Apply Failure for cert-manager Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Thu Dec 2 15:24:22 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 2 Dec 2021 15:24:22 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211202T023751Z In-Reply-To: References: Message-ID: Hi, Yes, you're right Frank. I executed the sanity on Virtual Simplex, Duplex, Standard and Standard Ext. Currently our baremetal servers from Karlsruhe, Germany are not yet ready. There was a downtime and our baremetal servers were affected and for the moment I can run the sanity only on virtual servers till the connection will be restored. My colleagues are working on this issue and we hope to fix this soon. Kind regards, Alex From: Miller, Frank Sent: Thursday, December 2, 2021 4:52 PM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211202T023751Z Alex: I cannot tell from your sanity emails which config was used for each sanity. An initial look at LP 1952400 is leading to a theory that this is only an issue for virtual labs and not bare metal servers. Please include which configuration is having which of the LPs. In particular are you seeing cert-manager apply failures happening when running on a bare metal server? If yes then please also attach the logs for that sanity run to the LP. Frank From: Dimofte, Alexandru > Sent: Thursday, December 2, 2021 5:15 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211202T023751Z [Please note: This e-mail is from an EXTERNAL e-mail address] Sanity Test from 2021-December-02 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211202T023751Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211202T023751Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz The build is affected by: https://bugs.launchpad.net/starlingx/+bug/1942480 - Alarm 800.010 Potential data loss. No available OSDs in storage replication group group-0 https://bugs.launchpad.net/starlingx/+bug/1952400 - Alarm 750.002 Application Apply Failure for cert-manager Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From Frank.Miller at windriver.com Thu Dec 2 18:17:26 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 2 Dec 2021 18:17:26 +0000 Subject: [Starlingx-discuss] Request adding Bob Church as Core for starlingx/tools repo Message-ID: Starlingx Tools Cores: I propose that Bob Church be added as a Core to the tools repo in particular for commits related to the Debian OS migration. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Dec 3 03:06:17 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 3 Dec 2021 03:06:17 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Dec 1/2021 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Dec 1 2021 stx.6.0 - Release/Feature Planning Spreadsheet: https://docs.google.com/spreadsheets/d/13p0BMlBgJXUVForOFsblAJq9jA1-FMBlmhV5TIc70IE/edit#gid=1107209846 - Test Tracking Spreadsheets: https://drive.google.com/drive/folders/1lfm073XaFGxHZSAf0RPS1DGK6QCReO9u - Re-assess Milesone-3 Criteria - Feature Freeze Status - All features are now merged - No blocking issues from Automated Sanity and Regression - Sanity Status - Sanity is still reported as Red - Sanity Issues: - https://bugs.launchpad.net/starlingx/+bug/1942480 - Alarm 800.010 Potential data loss. No available OSDs in storage replication group group-0 - Logs shows that the OSDs are not configured. Suspect the issue is a procedural issue; likely with the sanity automation sequence. - Flavio is following up with Alex - https://bugs.launchpad.net/starlingx/+bug/1952400 - Alarm 750.002 Application Apply Failure for cert-manager - Still needs investigation - Milestone-3 Decision - Criteria still not met due to inconsistent sanity results - Agreed to wait for two green/yellow sanities in a row before declaring MS-3 - No explicit re-forecast; will monitor sanity progress on a daily basis - stx.6.0 Bugs - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.6.0 - In good shape. Total: 10. Critical: 2 (sanity issues). High: 2 - Release Testing - Feature Testing - Testing is wrapping up. Expect to be complete by Dec 7. - Regression Testing - Completed one automated run. - Planning another automated regression run this week; setup in progress. analysis to be done next week. - Overall Release - Likely will not make the current forecast of Dec 13; possible to make the wk of Dec 20 - Agreed that release announcements will be done in Jan. - 2 Blog posts identified / in progress. Target: End-Year - Documentation Status (including Release Notes) - Will cover in the Dec 8 community call w/ Mary and team stx.7.0 - Will start to focus on the next release in the new year - Review posted to setup spec structure for stx.7.0 - https://review.opendev.org/c/starlingx/specs/+/819360 From Greg.Waines at windriver.com Fri Dec 3 11:20:14 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Fri, 3 Dec 2021 11:20:14 +0000 Subject: [Starlingx-discuss] Request adding Bob Church as Core for starlingx/tools repo In-Reply-To: References: Message-ID: +1 From: Miller, Frank Sent: Thursday, December 2, 2021 1:17 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Request adding Bob Church as Core for starlingx/tools repo Starlingx Tools Cores: I propose that Bob Church be added as a Core to the tools repo in particular for commits related to the Debian OS migration. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Fri Dec 3 17:44:47 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Fri, 3 Dec 2021 17:44:47 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 01-Dec-21 In-Reply-To: <20211202002618.gu6zxbkzuzksignt@yuggoth.org> References: <20211202002618.gu6zxbkzuzksignt@yuggoth.org> Message-ID: Thanks Jeremy for the advice -- something for us to consider for 2022! -Mary C. -----Original Message----- From: Jeremy Stanley Sent: Wednesday, December 1, 2021 7:26 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [docs] [meeting] Docs team notes 01-Dec-21 On 2021-12-02 00:14:41 +0000 (+0000), Camp, MaryX wrote: [...] > Notification of changes (Ron) > ? Recently?there was a change to the constraints file that > impacted us. How could we find out about these in advance? > ? Find out if the infra/oslo?team has meeting minutes that we > could monitor? > ? What are the issues we are concerned about:? version of sphinx, > theme changes.?Ask if they can provide some guidance for what > to watch for. > ? Is it oslo team only or is there another team that covers > theme? > ? During the meeting, we looked at: > ????http://lists.openstack.org/pipermail/openstack-discuss/ > ????https://meetings.opendev.org/meetings/oslo/2021/ > ? After the meeting, I found this in the OpenStack Projects > list: > https://governance.openstack.org/tc/reference/projects/oslo.html > ? The Oslo team does support theme. Those are some of the reasons I suggested StarlingX may want to consider forking that theme, stripping out the OpenStack-only bits, and moving it into the docs repo. I started a PoC of that with https://review.opendev.org/750005 and https://review.opendev.org/750006 but did not find time to finish it. The original has almost certainly diverged enough since that time that the changes would need to be recreated from scratch anyway at this point. -- Jeremy Stanley From alexandru.dimofte at intel.com Fri Dec 3 18:59:07 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 3 Dec 2021 18:59:07 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211203T042048Z Message-ID: Sanity Test from 2021-December-03 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211203T042048Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211203T042048Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz 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 ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Sat Dec 4 15:57:07 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 4 Dec 2021 15:57:07 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211204T031450Z Message-ID: Sanity Test from 2021-December-04 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211204T031450Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211204T031450Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Executed on Baremetal environment: Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 90 TCs ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From lists at optimcloud.com Sun Dec 5 03:41:16 2021 From: lists at optimcloud.com (Embedded Devel) Date: Sun, 05 Dec 2021 03:41:16 +0000 Subject: [Starlingx-discuss] STX tools - still broken, or Im the idiot! Message-ID: <1638675160587.1940131833.1397867783@optimcloud.com> Here we go again...! I dont see how anyone is generating and iso right now, because the document is surely incorrect ... So please enlighten me as to how to accomplish this! I follow this guide.... everything works fine up until generate centos-repos repo sync has finished successfully. [dingo at 1e7c00175f3d master]$ generate-centos-repo.sh /import/mirrors/CentOS mirror_dir=/import/mirrors/CentOS config_dir=/localdisk/designer/dingo/master/cgcs-root/../stx-tools/centos-mirror-tools/config distro=centos layer=all layer_pkg_urls= layer_image_inc_urls= layer_wheels_inc_urls= The mirror /import/mirrors/CentOS doesn't has the Binary and Source folders. Please provide a valid mirror So how goes one create this "mirror" ? So this all works. And yes, Im sorry but I do have a bit of an attitude, Ive been trying to accomplish this for "months" and getting nowhere! Its very frustrating when your trying to understand something and the documentation isnt quite clear. Initialize the source tree. cd $MY_REPO_ROOT_DIR repo init -u https://opendev.org/starlingx/manifest.git -m default.xml repo sync To generate centos-repo The centos-repo is a set of symbolic links to the packages in the mirror and the mock configuration file. It is needed to create these links if this is the first build or the mirror has been updated. generate-centos-repo.sh /import/mirrors/CentOS Where the argument to the script is the path of the mirror. To build all packages: $ cd $MY_REPO $ build-pkgs or build-pkgs --clean ; build-pkgs To generate local-repo: The local-repo has the dependency information that sequences the build order; To generate or update the information the following command needs to be executed after building modified or new packages. $ generate-local-repo.sh -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Sun Dec 5 19:43:53 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 5 Dec 2021 19:43:53 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211205T023500Z Message-ID: Sanity Test from 2021-December-05 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211205T023500Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211205T023500Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz 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 ] Sanity Test executed on Bare Metal environment: Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 90 TCs ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From build.starlingx at gmail.com Mon Dec 6 01:21:20 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 5 Dec 2021 20:21:20 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2298 - Failure! Message-ID: <1910164580.2.1638753684396.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2298 Status: Failure Timestamp: 20211206T010750Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211206T004910Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20211206T004910Z DOCKER_BUILD_ID: jenkins-master-flock-20211206T004910Z-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/20211206T004910Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20211206T004910Z/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 Mon Dec 6 01:21:25 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 5 Dec 2021 20:21:25 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 695 - Failure! Message-ID: <504466461.5.1638753686581.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 695 Status: Failure Timestamp: 20211206T004910Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211206T004910Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From openinfradn at gmail.com Mon Dec 6 18:15:50 2021 From: openinfradn at gmail.com (open infra) Date: Mon, 6 Dec 2021 23:45:50 +0530 Subject: [Starlingx-discuss] How to enable cpu_dedicated_set Message-ID: Hi, Is the cpu_dedicated_set is already enabled in stx based openstack? How to verify and enable it? Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thiago.Brito at windriver.com Mon Dec 6 19:48:13 2021 From: Thiago.Brito at windriver.com (Brito, Thiago) Date: Mon, 6 Dec 2021 19:48:13 +0000 Subject: [Starlingx-discuss] How to enable cpu_dedicated_set In-Reply-To: References: Message-ID: Hi Danishka, Whatever you configure on the platform as Application-isolated core for a node will get to cpu_dedicated_set on stx-openstack. Please check this doc: https://docs.starlingx.io/r/stx.5.0/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html Thiago ________________________________ From: open infra Sent: Monday, December 6, 2021 3:15 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to enable cpu_dedicated_set [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, Is the cpu_dedicated_set is already enabled in stx based openstack? How to verify and enable it? Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Dec 7 02:55:17 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 6 Dec 2021 18:55:17 -0800 Subject: [Starlingx-discuss] StarlingX segment for the 2021 OpenInfra Foundation Annual report Message-ID: Hi StarlingX Community, I?m reaching out to you about the OpenInfra Foundation Annual Report for 2021. As every year the Foundation is putting out a report to summarize the activities and achievements for a calendar year. Since the project?s launch there is a segment that covers these topics for StarlingX as well. While 2021 is still rolling, I know that the community is busy with STX 6.0 and other items so I put together a starting point to cover StarlingX in the report next January: https://etherpad.opendev.org/p/2021_StarlingX_Annual_Update Please review the text and either add questions or comments to the etherpad or reply to this thread if you have any comments or concerns. Thanks, Ildik? From openinfradn at gmail.com Tue Dec 7 08:16:08 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 7 Dec 2021 13:46:08 +0530 Subject: [Starlingx-discuss] How to enable cpu_dedicated_set In-Reply-To: References: Message-ID: Hi Thiago, I have configured the worker as mentioned in the given link and dedicated cpu_policy set in the flavor. Instance creation failed with the following error. No valid host was found. There are not enough hosts available. controller-0:~$ openstack flavor show dn.large -c properties +------------+--------------------------------------------------------------------------------------------------------+ | Field | Value | +------------+--------------------------------------------------------------------------------------------------------+ | properties | hw:cpu_cores='2', hw:cpu_policy='dedicated', hw:cpu_sockets='1', hw:cpu_threads='2', hw:numa_nodes='1' | +------------+--------------------------------------------------------------------------------------------------------+ Regards, Danishka On Tue, Dec 7, 2021 at 1:18 AM Brito, Thiago wrote: > Hi Danishka, > > Whatever you configure on the platform as Application-isolated core for a > node will get to cpu_dedicated_set on stx-openstack. Please check this doc: > https://docs.starlingx.io/r/stx.5.0/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html > > Thiago > ------------------------------ > *From:* open infra > *Sent:* Monday, December 6, 2021 3:15 PM > *To:* starlingx-discuss at lists.starlingx.io < > starlingx-discuss at lists.starlingx.io> > *Subject:* [Starlingx-discuss] How to enable cpu_dedicated_set > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > Hi, > > Is the cpu_dedicated_set is already enabled in stx based openstack? > How to verify and enable it? > > Regards, > Danishka > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Tue Dec 7 08:45:26 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 7 Dec 2021 14:15:26 +0530 Subject: [Starlingx-discuss] How to enable cpu_dedicated_set In-Reply-To: References: Message-ID: Here is the info from STX side Processors 2Physical Cores Per Processor 32Hyper-Threading Yes CPU Assignments Create Cpu Profile Function Processor Logical Cores Platform *Processor 0 : *0,64 vSwitch Shared Application *Processor 0 : *17-31,81-95 *Processor 1 : *56-63,120-127 Application-isolated *Processor 0 : *1-16,65-80 *Processor 1 : *32-55,96-119 On Tue, Dec 7, 2021 at 1:46 PM open infra wrote: > Hi Thiago, > > I have configured the worker as mentioned in the given link and dedicated > cpu_policy set in the flavor. > Instance creation failed with the following error. > > No valid host was found. There are not enough hosts available. > > > controller-0:~$ openstack flavor show dn.large -c properties > > > +------------+--------------------------------------------------------------------------------------------------------+ > > | Field | Value > | > > > +------------+--------------------------------------------------------------------------------------------------------+ > > | properties | hw:cpu_cores='2', hw:cpu_policy='dedicated', > hw:cpu_sockets='1', hw:cpu_threads='2', hw:numa_nodes='1' | > > > +------------+--------------------------------------------------------------------------------------------------------+ > > > Regards, > > Danishka > > On Tue, Dec 7, 2021 at 1:18 AM Brito, Thiago > wrote: > >> Hi Danishka, >> >> Whatever you configure on the platform as Application-isolated core for a >> node will get to cpu_dedicated_set on stx-openstack. Please check this doc: >> https://docs.starlingx.io/r/stx.5.0/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html >> >> Thiago >> ------------------------------ >> *From:* open infra >> *Sent:* Monday, December 6, 2021 3:15 PM >> *To:* starlingx-discuss at lists.starlingx.io < >> starlingx-discuss at lists.starlingx.io> >> *Subject:* [Starlingx-discuss] How to enable cpu_dedicated_set >> >> >> [Please note: This e-mail is from an EXTERNAL e-mail address] >> Hi, >> >> Is the cpu_dedicated_set is already enabled in stx based openstack? >> How to verify and enable it? >> >> Regards, >> Danishka >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue Dec 7 13:35:10 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 7 Dec 2021 13:35:10 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211206T201202Z Message-ID: Sanity Test from 2021-December-06 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211206T201202Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211206T201202Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz 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 ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Sanity Test executed on Bare Metal Environment: Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 90 TCs ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image003.png URL: From Linda.Wang at windriver.com Tue Dec 7 16:39:47 2021 From: Linda.Wang at windriver.com (Wang, Linda) Date: Tue, 7 Dec 2021 16:39:47 +0000 Subject: [Starlingx-discuss] Bi-Weekly StarlingX OS Distro & Multi-OS meeting In-Reply-To: References: Message-ID: Hi, Due to a schedule conflict, I will have to either move this week's StarlingX OS Distro.& Multi-OS meeting to another timeslot or cancel it. Therefore, please let me know if folks have any urgent agenda item that they like to discuss this week, and I will try to find another time slot for us to meet; otherwise, I will cancel the meeting. Many Thanks, Linda ________________________________ From: Wang, Linda Sent: Tuesday, October 26, 2021 6:09 PM To: starlingx-discuss at lists.starlingx.io ; Asselstine, Mark ; Wensley, Barton ; Jones, Bruce E Cc: Xie, Cindy ; Wold, Saul ; Kopec, Gerald (Gerry) ; Subramanian, Ramaswamy ; Eslimi, Dariush ; Waines, Greg ; Hellmann, Gil ; Ansari, Sabeel ; Dunlap, David ; Zvonar, Bill ; CH.Huang789 ; Smith, Kevin; Church, Robert; Little, Scott; Panech, Davlet ; Selvaraj, Susendra ; Bhat, Gopalkrishna ; Nowell, Anthony ; Short, Charles ; Soubihe, Joao Paulo ; Brito, Thiago ; Morgan, Jack; Torres Cardenas, Daniel Stevens ; Hu, Jia Subject: Bi-Weekly StarlingX OS Distro & Multi-OS meeting When: Wednesday, December 8, 2021 6:30 AM-7:00 AM. Where: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * Cadence and time slot: * Bi-Weekly Wednesday 0930 EDT (1430 UTC, 2230 China time, 0630 PT time) * 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue Dec 7 19:00:33 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 7 Dec 2021 19:00:33 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211207T021809Z Message-ID: Sanity Test from 2021-December-07 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211207T021809Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211207T021809Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz 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 ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Sanity Test executed on Bare Metal Environment: AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 88 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From ildiko.vancsa at gmail.com Tue Dec 7 21:32:18 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 7 Dec 2021 13:32:18 -0800 Subject: [Starlingx-discuss] KubeCon EU CFP is now open In-Reply-To: References: Message-ID: Hi, It is a friendly reminder that if you are interested in submitting a talk for KubeCon EU, the CFP is still open and will close shortly. You have until __December 17__ to submit your proposal for this conference. If you need help with your abstract please let me know. I?m happy to help you putting it together or review it if you already put something together and you need someone to read through it. Thanks, Ildik? > On Oct 26, 2021, at 11:10, Ildiko Vancsa wrote: > > Hi, > > Just a quick heads up that the KubeCon EU CFP opened yesterday and will be open till December 17, 2021. > > You can find details here: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/program/cfp/ > > Since the community has been working with Kubernetes and containers a lot, I think it would be great to have presence at the conference and representation from the community to talk about all the great work you all are doing! > > Please let me know if you need any help with putting together a proposal. > > Thanks and Best Regards, > Ildik? > > From Thiago.Brito at windriver.com Tue Dec 7 21:46:00 2021 From: Thiago.Brito at windriver.com (Brito, Thiago) Date: Tue, 7 Dec 2021 21:46:00 +0000 Subject: [Starlingx-discuss] How to enable cpu_dedicated_set In-Reply-To: References: Message-ID: Did you do an application-apply after you changed the processors to application-isolated? Can you send the output of the command below for you compute pods: kubectl exec -n openstack nova-compute-[woker|controller]-X-XXXXX-xxxx -- cat /etc/nova/nova.conf|grep dedicated_set Don't forget to change the id of the pod for your compute pods. Thiago ________________________________ From: open infra Sent: Tuesday, December 7, 2021 5:45 AM To: Brito, Thiago Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] How to enable cpu_dedicated_set [Please note: This e-mail is from an EXTERNAL e-mail address] Here is the info from STX side Processors 2 Physical Cores Per Processor 32 Hyper-Threading Yes CPU Assignments Create Cpu Profile Function Processor Logical Cores Platform Processor 0 : 0,64 vSwitch Shared Application Processor 0 : 17-31,81-95 Processor 1 : 56-63,120-127 Application-isolated Processor 0 : 1-16,65-80 Processor 1 : 32-55,96-119 On Tue, Dec 7, 2021 at 1:46 PM open infra > wrote: Hi Thiago, I have configured the worker as mentioned in the given link and dedicated cpu_policy set in the flavor. Instance creation failed with the following error. No valid host was found. There are not enough hosts available. controller-0:~$ openstack flavor show dn.large -c properties +------------+--------------------------------------------------------------------------------------------------------+ | Field | Value | +------------+--------------------------------------------------------------------------------------------------------+ | properties | hw:cpu_cores='2', hw:cpu_policy='dedicated', hw:cpu_sockets='1', hw:cpu_threads='2', hw:numa_nodes='1' | +------------+--------------------------------------------------------------------------------------------------------+ Regards, Danishka On Tue, Dec 7, 2021 at 1:18 AM Brito, Thiago > wrote: Hi Danishka, Whatever you configure on the platform as Application-isolated core for a node will get to cpu_dedicated_set on stx-openstack. Please check this doc: https://docs.starlingx.io/r/stx.5.0/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html Thiago ________________________________ From: open infra > Sent: Monday, December 6, 2021 3:15 PM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] How to enable cpu_dedicated_set [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, Is the cpu_dedicated_set is already enabled in stx based openstack? How to verify and enable it? Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Dec 7 21:51:53 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 7 Dec 2021 13:51:53 -0800 Subject: [Starlingx-discuss] Community Marketing meeting minutes Message-ID: <66B5FAC9-25A6-4381-97CB-3B8ED5BE2E77@gmail.com> Hi, We?ve just had the last Community Marketing meeting for 2021. We discussed the following topics on today?s call: * Demo videos * A few short videos are being made by the community to help showcasing StarlingX features * 'Patching at Scale' video is now close to completion * We reviewed the video during the call * Attendees gave some feedback for the final touches on the video, before it gets placed on the starlingx.io website * StarlingX 6.0 Release communications * As agreed on the Release Team meeting last week, release announcements will happen in January, 2022 * There are 2 feature-specific blog posts in flight * Steve and Ildiko will work on a release overview blog post as well * OpenInfra Foundation Annual report * There is a segment reserved in the 2021 OIF Annual Report for StarlingX * A draft is already available for the community to review and edit: https://etherpad.opendev.org/p/2021_StarlingX_Annual_Update * Twitter * We have a new form to submit ideas and topics to use for social media promotion * Please help us share the form and also submit your ideas here: https://www.surveymonkey.com/r/GB9HXV3 * Events * Upcoming CFP deadline: KubeCon EU deadline is December 17th Our next call is scheduled for __January 4, 2022 at 12pm Pacific Time__. If you are interested in joining the call, you can find the meeting details here: https://wiki.openstack.org/wiki/Starlingx/Meetings#12:00pm_Pacific_-_Community_Marketing_Planning_Call Please let me know if you have any questions. Thanks, Ildik? From Linda.Wang at windriver.com Tue Dec 7 23:14:54 2021 From: Linda.Wang at windriver.com (Wang, Linda) Date: Tue, 7 Dec 2021 23:14:54 +0000 Subject: [Starlingx-discuss] Canceled: Bi-Weekly StarlingX OS Distro & Multi-OS meeting Message-ID: A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4852 bytes Desc: not available URL: From openinfradn at gmail.com Wed Dec 8 08:41:51 2021 From: openinfradn at gmail.com (open infra) Date: Wed, 8 Dec 2021 14:11:51 +0530 Subject: [Starlingx-discuss] How to enable cpu_dedicated_set In-Reply-To: References: Message-ID: Thank you, Thiago! I managed to create an instance with dedicated cores, after application-apply. Btw, do we need to recreate all instances or is there a solution for existing instances which were created without dedicated cores? On Wed, Dec 8, 2021 at 3:16 AM Brito, Thiago wrote: > Did you do an application-apply after you changed the processors to > application-isolated? Can you send the output of the command below for you > compute pods: > > kubectl exec -n openstack nova-compute-[woker|controller]-X-XXXXX-xxxx -- > cat /etc/nova/nova.conf|grep dedicated_set > > Don't forget to change the id of the pod for your compute pods. > > Thiago > ------------------------------ > *From:* open infra > *Sent:* Tuesday, December 7, 2021 5:45 AM > *To:* Brito, Thiago > *Cc:* starlingx-discuss at lists.starlingx.io < > starlingx-discuss at lists.starlingx.io> > *Subject:* Re: [Starlingx-discuss] How to enable cpu_dedicated_set > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > Here is the info from STX side > > > Processors 2 Physical Cores Per Processor 32 Hyper-Threading Yes > CPU Assignments > Create Cpu Profile > > Function > Processor Logical Cores > Platform *Processor 0 : *0,64 > vSwitch > Shared > Application *Processor 0 : *17-31,81-95 > *Processor 1 : *56-63,120-127 > Application-isolated *Processor 0 : *1-16,65-80 > *Processor 1 : *32-55,96-119 > > On Tue, Dec 7, 2021 at 1:46 PM open infra wrote: > > Hi Thiago, > > I have configured the worker as mentioned in the given link and dedicated > cpu_policy set in the flavor. > Instance creation failed with the following error. > > No valid host was found. There are not enough hosts available. > > > controller-0:~$ openstack flavor show dn.large -c properties > > > +------------+--------------------------------------------------------------------------------------------------------+ > > | Field | Value > | > > > +------------+--------------------------------------------------------------------------------------------------------+ > > | properties | hw:cpu_cores='2', hw:cpu_policy='dedicated', > hw:cpu_sockets='1', hw:cpu_threads='2', hw:numa_nodes='1' | > > > +------------+--------------------------------------------------------------------------------------------------------+ > > > Regards, > > Danishka > > On Tue, Dec 7, 2021 at 1:18 AM Brito, Thiago > wrote: > > Hi Danishka, > > Whatever you configure on the platform as Application-isolated core for a > node will get to cpu_dedicated_set on stx-openstack. Please check this doc: > https://docs.starlingx.io/r/stx.5.0/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html > > > Thiago > ------------------------------ > *From:* open infra > *Sent:* Monday, December 6, 2021 3:15 PM > *To:* starlingx-discuss at lists.starlingx.io < > starlingx-discuss at lists.starlingx.io> > *Subject:* [Starlingx-discuss] How to enable cpu_dedicated_set > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > Hi, > > Is the cpu_dedicated_set is already enabled in stx based openstack? > How to verify and enable it? > > Regards, > Danishka > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thiago.Brito at windriver.com Wed Dec 8 12:40:04 2021 From: Thiago.Brito at windriver.com (Brito, Thiago) Date: Wed, 8 Dec 2021 12:40:04 +0000 Subject: [Starlingx-discuss] How to enable cpu_dedicated_set In-Reply-To: References: Message-ID: I believe if you rezise the instance to a flavor that has hw:cpu_policy=dedicated on it, you should be good. Thiago ________________________________ From: open infra Sent: Wednesday, December 8, 2021 5:41 AM To: Brito, Thiago Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] How to enable cpu_dedicated_set [Please note: This e-mail is from an EXTERNAL e-mail address] Thank you, Thiago! I managed to create an instance with dedicated cores, after application-apply. Btw, do we need to recreate all instances or is there a solution for existing instances which were created without dedicated cores? On Wed, Dec 8, 2021 at 3:16 AM Brito, Thiago > wrote: Did you do an application-apply after you changed the processors to application-isolated? Can you send the output of the command below for you compute pods: kubectl exec -n openstack nova-compute-[woker|controller]-X-XXXXX-xxxx -- cat /etc/nova/nova.conf|grep dedicated_set Don't forget to change the id of the pod for your compute pods. Thiago ________________________________ From: open infra > Sent: Tuesday, December 7, 2021 5:45 AM To: Brito, Thiago > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] How to enable cpu_dedicated_set [Please note: This e-mail is from an EXTERNAL e-mail address] Here is the info from STX side Processors 2 Physical Cores Per Processor 32 Hyper-Threading Yes CPU Assignments Create Cpu Profile Function Processor Logical Cores Platform Processor 0 : 0,64 vSwitch Shared Application Processor 0 : 17-31,81-95 Processor 1 : 56-63,120-127 Application-isolated Processor 0 : 1-16,65-80 Processor 1 : 32-55,96-119 On Tue, Dec 7, 2021 at 1:46 PM open infra > wrote: Hi Thiago, I have configured the worker as mentioned in the given link and dedicated cpu_policy set in the flavor. Instance creation failed with the following error. No valid host was found. There are not enough hosts available. controller-0:~$ openstack flavor show dn.large -c properties +------------+--------------------------------------------------------------------------------------------------------+ | Field | Value | +------------+--------------------------------------------------------------------------------------------------------+ | properties | hw:cpu_cores='2', hw:cpu_policy='dedicated', hw:cpu_sockets='1', hw:cpu_threads='2', hw:numa_nodes='1' | +------------+--------------------------------------------------------------------------------------------------------+ Regards, Danishka On Tue, Dec 7, 2021 at 1:18 AM Brito, Thiago > wrote: Hi Danishka, Whatever you configure on the platform as Application-isolated core for a node will get to cpu_dedicated_set on stx-openstack. Please check this doc: https://docs.starlingx.io/r/stx.5.0/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html Thiago ________________________________ From: open infra > Sent: Monday, December 6, 2021 3:15 PM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] How to enable cpu_dedicated_set [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, Is the cpu_dedicated_set is already enabled in stx based openstack? How to verify and enable it? Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Dec 8 13:36:45 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 8 Dec 2021 13:36:45 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 8, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up shortly. Please feel free to add other 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=20211208T1500? [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From alexandru.dimofte at intel.com Wed Dec 8 14:47:22 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 8 Dec 2021 14:47:22 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211208T032736Z Message-ID: Sanity Test from 2021-December-08 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211208T032736Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211208T032736Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz 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 ] Sanity Test executed on Bare Metal Environment: AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 88 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 90 TCs ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From Bill.Zvonar at windriver.com Wed Dec 8 15:36:27 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 8 Dec 2021 15:36:27 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 8, 2021) In-Reply-To: References: Message-ID: >From today's meeting... * Standing Topics * Build/Sanity * sanity seems to be quite green now * there was a build issue on the weekend due to a power outage at CENGN, but things are fine now * Gerrit Reviews in Need of Attention * https://review.opendev.org/c/starlingx/ansible-playbooks/+/815008 * reviewers please revisit this (but no so soon that it gets into stx.6.0 - Thiago will put a WF-1 so it doesn't inadvertently get in) * Topics for this Week * Open requests for core promotion (Douglas Pereira): * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-November/012458.html * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-November/012459.html * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-November/012456.html * Douglas to reach out to the cores to close on the approvals * stx.6.0 MS-3 status (Ghada) * https://etherpad.opendev.org/p/stx-releases * agreed to declare MS-3, see release team etherpad for details * ARs from Previous Meetings * stx.6.0 release notes (Mary Camp) Gerrit review here: https://review.opendev.org/c/starlingx/docs/+/820946 * Open Requests for Help * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Wednesday, December 8, 2021 8:37 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Dec 8, 2021) Hi all, reminder of the weekly TSC/Community calls coming up shortly. Please feel free to add other 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=20211208T1500? [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From openinfradn at gmail.com Wed Dec 8 15:43:53 2021 From: openinfradn at gmail.com (open infra) Date: Wed, 8 Dec 2021 21:13:53 +0530 Subject: [Starlingx-discuss] How to enable cpu_dedicated_set In-Reply-To: References: Message-ID: On Wed, Dec 8, 2021 at 6:10 PM Brito, Thiago wrote: > I believe if you rezise the instance to a flavor that has > hw:cpu_policy=dedicated on it, you should be good. > It worked! Thanks again :) > > Thiago > ------------------------------ > *From:* open infra > *Sent:* Wednesday, December 8, 2021 5:41 AM > *To:* Brito, Thiago > *Cc:* starlingx-discuss at lists.starlingx.io < > starlingx-discuss at lists.starlingx.io> > *Subject:* Re: [Starlingx-discuss] How to enable cpu_dedicated_set > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > Thank you, Thiago! > I managed to create an instance with dedicated cores, after > application-apply. > Btw, do we need to recreate all instances or is there a solution for > existing instances which were created without dedicated cores? > > > On Wed, Dec 8, 2021 at 3:16 AM Brito, Thiago > wrote: > > Did you do an application-apply after you changed the processors to > application-isolated? Can you send the output of the command below for you > compute pods: > > kubectl exec -n openstack nova-compute-[woker|controller]-X-XXXXX-xxxx -- > cat /etc/nova/nova.conf|grep dedicated_set > > Don't forget to change the id of the pod for your compute pods. > > Thiago > ------------------------------ > *From:* open infra > *Sent:* Tuesday, December 7, 2021 5:45 AM > *To:* Brito, Thiago > *Cc:* starlingx-discuss at lists.starlingx.io < > starlingx-discuss at lists.starlingx.io> > *Subject:* Re: [Starlingx-discuss] How to enable cpu_dedicated_set > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > Here is the info from STX side > > > Processors 2 Physical Cores Per Processor 32 Hyper-Threading Yes > CPU Assignments > Create Cpu Profile > > Function > Processor Logical Cores > Platform *Processor 0 : *0,64 > vSwitch > Shared > Application *Processor 0 : *17-31,81-95 > *Processor 1 : *56-63,120-127 > Application-isolated *Processor 0 : *1-16,65-80 > *Processor 1 : *32-55,96-119 > > On Tue, Dec 7, 2021 at 1:46 PM open infra wrote: > > Hi Thiago, > > I have configured the worker as mentioned in the given link and dedicated > cpu_policy set in the flavor. > Instance creation failed with the following error. > > No valid host was found. There are not enough hosts available. > > > controller-0:~$ openstack flavor show dn.large -c properties > > > +------------+--------------------------------------------------------------------------------------------------------+ > > | Field | Value > | > > > +------------+--------------------------------------------------------------------------------------------------------+ > > | properties | hw:cpu_cores='2', hw:cpu_policy='dedicated', > hw:cpu_sockets='1', hw:cpu_threads='2', hw:numa_nodes='1' | > > > +------------+--------------------------------------------------------------------------------------------------------+ > > > Regards, > > Danishka > > On Tue, Dec 7, 2021 at 1:18 AM Brito, Thiago > wrote: > > Hi Danishka, > > Whatever you configure on the platform as Application-isolated core for a > node will get to cpu_dedicated_set on stx-openstack. Please check this doc: > https://docs.starlingx.io/r/stx.5.0/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html > > > Thiago > ------------------------------ > *From:* open infra > *Sent:* Monday, December 6, 2021 3:15 PM > *To:* starlingx-discuss at lists.starlingx.io < > starlingx-discuss at lists.starlingx.io> > *Subject:* [Starlingx-discuss] How to enable cpu_dedicated_set > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > Hi, > > Is the cpu_dedicated_set is already enabled in stx based openstack? > How to verify and enable it? > > Regards, > Danishka > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Dec 8 17:15:13 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 8 Dec 2021 17:15:13 +0000 Subject: [Starlingx-discuss] stx.6.0 Milestone-3 Declared Message-ID: Hello all, Based on the stx.6.0 release review in the community meeting today, the release team is declaring Milestone-3 with a date of Dec 8/2021. Feature Status: https://docs.google.com/spreadsheets/d/13p0BMlBgJXUVForOFsblAJq9jA1-FMBlmhV5TIc70IE/edit#gid=1107209846 Feature Testing Status: https://docs.google.com/spreadsheets/d/1WG6HDjQz4n4RVZ1asw-bQRJQlk4OXWxnBgg54SxRxx8/edit Details are in the stx-releases etherpad: https://etherpad.opendev.org/p/stx-releases Thank you to all community members who helped achieve this milestone. Regards, Ghada & the stx release team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Dec 8 17:22:38 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 8 Dec 2021 17:22:38 +0000 Subject: [Starlingx-discuss] Branch r/stx.6.0 Message-ID: Hello all, With the declaration of the stx.6.0 Milestone-3 earlier today, Scott will be proceeding with the creation of the r/stx.6.0 release branch tomorrow - Dec 9. Once the branch is created and RC builds are generating, sanity will be executed for those builds. Note: Only stx.6.0 gating LPs and stx.6.0 doc updates should be merged in this branch. For reference, here's the query for open stx.6.0 gating LPs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.6.0 Regards, Ghada & the stx release team From maryx.camp at intel.com Wed Dec 8 21:56:26 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 8 Dec 2021 21:56:26 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 08-Dec-21 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 ========== 08-Dec-21 All -- reviews merged since last meeting: 7 https://review.opendev.org/q/project:starlingx/docs+status:merged Reviews in progress: https://review.opendev.org/c/starlingx/docs/+/820949 (Elisa) Wait till Gustavo replies https://review.opendev.org/c/starlingx/docs/+/820946 (STX 6.0 Release Notes, Mary) AR Mary redo the table to fix permanently. https://review.opendev.org/c/starlingx/docs/+/821118 (Archive old config guides, Mary) All -- bug status -- 9 total - team agrees to defer all low priority LP until the upstreaming effort is completed. Status/questions/opens Scott is going to cut the R6 branch soon, he will not include the docs repo in that task, as discussed. Our plan is to do minimal release docs for the STX Release next week: landing page update + Release notes HOLD on Install guide folder changes/updates - wait till after holiday break, Scott will cut the branch From alexandru.dimofte at intel.com Thu Dec 9 14:53:07 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 9 Dec 2021 14:53:07 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211209T032015Z Message-ID: Sanity Test from 2021-December-09 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211209T032015Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211209T032015Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz 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 ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Sanity Test executed on Bare Metal Environment: Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 90 TCs ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From scott.little at windriver.com Fri Dec 10 06:05:16 2021 From: scott.little at windriver.com (Scott Little) Date: Fri, 10 Dec 2021 01:05:16 -0500 Subject: [Starlingx-discuss] [Important] Creation of branch r/stx.6.0 Message-ID: Code reviews for the creation of r/stx.6.0 branch please https://review.opendev.org/q/topic:%2522r.stx.6.0%2522+(status:open+OR+status:merged) From alexandru.dimofte at intel.com Fri Dec 10 15:15:52 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 10 Dec 2021 15:15:52 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211210T044913Z Message-ID: Sanity Test from 2021-December-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211210T044913Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211210T044913Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz 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 ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Sanity Test executed on Bare Metal Environment: AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 71 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 83 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 88 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 90 TCs ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From build.starlingx at gmail.com Fri Dec 10 20:11:27 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 10 Dec 2021 15:11:27 -0500 (EST) Subject: [Starlingx-discuss] [build-report] r/stx.6.0 STX_repo_sync_layered - Build # 2709 - Failure! Message-ID: <562640181.10.1639167088947.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 2709 Status: Failure Timestamp: 20211210T201119Z Branch: r/stx.6.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20211210T200835Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.6.0 MANIFEST: compiler.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20211210T200835Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/6.0/centos/compiler/20211210T200835Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/rc-6.0-compiler From build.starlingx at gmail.com Fri Dec 10 20:11:30 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 10 Dec 2021 15:11:30 -0500 (EST) Subject: [Starlingx-discuss] [build-report] r/stx.6.0 STX_6.0_build_layer_compiler - Build # 1 - Failure! Message-ID: <1235155349.13.1639167090968.JavaMail.javamailuser@localhost> Project: STX_6.0_build_layer_compiler Build #: 1 Status: Failure Timestamp: 20211210T200835Z Branch: r/stx.6.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20211210T200835Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Fri Dec 10 20:51:09 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 10 Dec 2021 15:51:09 -0500 (EST) Subject: [Starlingx-discuss] [build-report] r/stx.6.0 STX_6.0_build_layer_compiler - Build # 2 - Still Failing! In-Reply-To: <913636839.11.1639167089462.JavaMail.javamailuser@localhost> References: <913636839.11.1639167089462.JavaMail.javamailuser@localhost> Message-ID: <458124676.18.1639169470398.JavaMail.javamailuser@localhost> Project: STX_6.0_build_layer_compiler Build #: 2 Status: Still Failing Timestamp: 20211210T203518Z Branch: r/stx.6.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20211210T203518Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From build.starlingx at gmail.com Fri Dec 10 23:11:51 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 10 Dec 2021 18:11:51 -0500 (EST) Subject: [Starlingx-discuss] [build-report] r/stx.6.0 STX_6.0_build_layer_distro - Build # 1 - Failure! Message-ID: <58479583.24.1639177912184.JavaMail.javamailuser@localhost> Project: STX_6.0_build_layer_distro Build #: 1 Status: Failure Timestamp: 20211210T214409Z Branch: r/stx.6.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/distro/20211210T214409Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From build.starlingx at gmail.com Sat Dec 11 00:36:33 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 10 Dec 2021 19:36:33 -0500 (EST) Subject: [Starlingx-discuss] [build-report] r/stx.6.0 STX_6.0_build_layer_distro - Build # 2 - Still Failing! In-Reply-To: <1638879564.22.1639177910566.JavaMail.javamailuser@localhost> References: <1638879564.22.1639177910566.JavaMail.javamailuser@localhost> Message-ID: <202363928.28.1639182994640.JavaMail.javamailuser@localhost> Project: STX_6.0_build_layer_distro Build #: 2 Status: Still Failing Timestamp: 20211211T002553Z Branch: r/stx.6.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/distro/20211211T002553Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From build.starlingx at gmail.com Sat Dec 11 01:59:55 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 10 Dec 2021 20:59:55 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_deb_build_containers - Build # 77 - Failure! Message-ID: <1927287914.31.1639187995859.JavaMail.javamailuser@localhost> Project: STX_build_deb_build_containers Build #: 77 Status: Failure Timestamp: 20211211T015623Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20211211T015600Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/debian-master-build-containers/20211211T015600Z OS: debian MY_REPO: /localdisk/designer/jenkins/debian-master-build-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20211211T015600Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/debian/build-containers/20211211T015600Z/logs MASTER_JOB_NAME: STX_build_debian_build_containers_master MY_REPO_ROOT: /localdisk/designer/jenkins/debian-master-build-containers FULL_BUILD: false REGISTRY_ORG: starlingx DOCKER_BUILD_TAG: master-debian-20211211T015600Z LAYER: build-containers REGISTRY: docker.io From build.starlingx at gmail.com Sat Dec 11 14:00:30 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 11 Dec 2021 09:00:30 -0500 (EST) Subject: [Starlingx-discuss] [build-report] r/stx.6.0 STX_6.0_build_layer_containers - Build # 1 - Failure! Message-ID: <137611623.38.1639231231584.JavaMail.javamailuser@localhost> Project: STX_6.0_build_layer_containers Build #: 1 Status: Failure Timestamp: 20211211T124057Z Branch: r/stx.6.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/containers/20211211T124057Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From alexandru.dimofte at intel.com Sat Dec 11 14:56:24 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 11 Dec 2021 14:56:24 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211211T032927Z Message-ID: Sanity Test from 2021-December-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211211T032927Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211211T032927Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Virtual Environment: 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 ] Sanity Test executed on Bare Metal Environment: AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 71 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 83 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Sat Dec 11 15:16:00 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 11 Dec 2021 15:16:00 +0000 Subject: [Starlingx-discuss] Regarding first rc of StarlingX 6.0 Message-ID: Hello, I observed that the first image of STX RC6.0 is ready on http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211211T105745Z/ The issue is that we don't have the helm-charts available for this image. In order to run sanity tests I need the helm-charts (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211211T105745Z/outputs/helm-charts/). So, I guess I need to wait for the next RC6.0 image... Kind regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image003.png URL: From build.starlingx at gmail.com Sun Dec 12 04:00:52 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 11 Dec 2021 23:00:52 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2326 - Failure! Message-ID: <163257859.44.1639281653906.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2326 Status: Failure Timestamp: 20211212T034316Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211212T032137Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20211212T032137Z DOCKER_BUILD_ID: jenkins-master-flock-20211212T032137Z-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/20211212T032137Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20211212T032137Z/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 Sun Dec 12 04:00:55 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 11 Dec 2021 23:00:55 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 702 - Failure! Message-ID: <1433709332.47.1639281657229.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 702 Status: Failure Timestamp: 20211212T032137Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211212T032137Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sun Dec 12 09:09:31 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 12 Dec 2021 04:09:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1294 - Failure! Message-ID: <888619933.50.1639300172614.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1294 Status: Failure Timestamp: 20211212T054107Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211212T053000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20211212T053000Z DOCKER_BUILD_ID: jenkins-master-20211212T053000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211212T053000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20211212T053000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sun Dec 12 09:09:34 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 12 Dec 2021 04:09:34 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1139 - Failure! Message-ID: <259062696.53.1639300174862.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1139 Status: Failure Timestamp: 20211212T053000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211212T053000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From amy at demarco.com Sun Dec 12 23:53:47 2021 From: amy at demarco.com (Amy Marrich) Date: Sun, 12 Dec 2021 17:53:47 -0600 Subject: [Starlingx-discuss] [Diversity] D&I WG Meeting Time and IRC vs Video Poll Message-ID: Hi everyone, The Diversity and Inclusion WG is holding a poll to see if there would be interest in attending if it were on another day and time as well as if IRC vs Video would be preferred. We currently meet the first Monday of the month at 17:00 UTC. And hope to have a planning meeting as our first meeting of the year. Our first meeting of the new year is slated for January 3rd at 17:00 UTC and for IRC. We will take the poll results into consideration and may cancel the January meeting to allow folks to plan on attending in which case February's meeting would be the first of the year. Please vote for your preferred days and times AND also for IRC and/or Video. https://doodle.com/poll/mnzxkauzwf2isssm?utm_source=poll&utm_medium=link We are keeping to morning hours to encourage participation from EMEA but not overly early for PST folks to attend. We will keep the poll up through the end of the year. Please feel free to reach out with any questions or concerns and remember the Diversity and Inclusion WG is for ALL projects under the Open Infra Foundation! Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Dec 13 00:40:07 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 12 Dec 2021 19:40:07 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2329 - Failure! Message-ID: <1797257075.57.1639356008636.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2329 Status: Failure Timestamp: 20211213T002235Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211213T000514Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20211213T000514Z DOCKER_BUILD_ID: jenkins-master-flock-20211213T000514Z-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/20211213T000514Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20211213T000514Z/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 Mon Dec 13 00:40:10 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 12 Dec 2021 19:40:10 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 703 - Still Failing! In-Reply-To: <1381775846.45.1639281654418.JavaMail.javamailuser@localhost> References: <1381775846.45.1639281654418.JavaMail.javamailuser@localhost> Message-ID: <804188512.60.1639356011387.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 703 Status: Still Failing Timestamp: 20211213T000514Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211213T000514Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Mon Dec 13 09:12:36 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 13 Dec 2021 04:12:36 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1295 - Still Failing! In-Reply-To: <2085680766.48.1639300166610.JavaMail.javamailuser@localhost> References: <2085680766.48.1639300166610.JavaMail.javamailuser@localhost> Message-ID: <1434011461.63.1639386759345.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1295 Status: Still Failing Timestamp: 20211213T054218Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211213T053000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20211213T053000Z DOCKER_BUILD_ID: jenkins-master-20211213T053000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211213T053000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20211213T053000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Mon Dec 13 09:12:40 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 13 Dec 2021 04:12:40 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1140 - Still Failing! In-Reply-To: <765655689.51.1639300173256.JavaMail.javamailuser@localhost> References: <765655689.51.1639300173256.JavaMail.javamailuser@localhost> Message-ID: <1381900345.66.1639386761565.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1140 Status: Still Failing Timestamp: 20211213T053000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211213T053000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Mon Dec 13 13:51:29 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 13 Dec 2021 08:51:29 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_deb_build_containers - Build # 80 - Failure! Message-ID: <58677174.69.1639403490177.JavaMail.javamailuser@localhost> Project: STX_build_deb_build_containers Build #: 80 Status: Failure Timestamp: 20211213T135001Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20211213T134941Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/debian-master-build-containers/20211213T134941Z OS: debian MY_REPO: /localdisk/designer/jenkins/debian-master-build-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/build-containers/20211213T134941Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/debian/build-containers/20211213T134941Z/logs MASTER_JOB_NAME: STX_build_debian_build_containers_master MY_REPO_ROOT: /localdisk/designer/jenkins/debian-master-build-containers FULL_BUILD: false REGISTRY_ORG: starlingx DOCKER_BUILD_TAG: master-debian-20211213T134941Z LAYER: build-containers REGISTRY: docker.io From scott.little at windriver.com Mon Dec 13 14:28:09 2021 From: scott.little at windriver.com (Scott Little) Date: Mon, 13 Dec 2021 09:28:09 -0500 Subject: [Starlingx-discuss] [build-report] r/stx.6.0 STX_6.0_build_layer_distro - Build # 1 - Failure! In-Reply-To: <58479583.24.1639177912184.JavaMail.javamailuser@localhost> References: <58479583.24.1639177912184.JavaMail.javamailuser@localhost> Message-ID: <368e1d4b-fc6c-2884-74dc-383fd99dfc07@windriver.com> This was the first build attempt for r/stx.6.0 distro lager. There was a glitch in download_mirrors.sh that prevented the initial build attempt from procceeding. The subsequent build passed, and ir ready for testing. I've created a launchpad to track the issue. https://bugs.launchpad.net/starlingx/+bug/1954667 On 2021-12-10 6:11 p.m., build.starlingx at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_6.0_build_layer_distro > Build #: 1 > Status: Failure > Timestamp: 20211210T214409Z > Branch: r/stx.6.0 > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/distro/20211210T214409Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: 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 scott.little at windriver.com Mon Dec 13 14:29:10 2021 From: scott.little at windriver.com (Scott Little) Date: Mon, 13 Dec 2021 09:29:10 -0500 Subject: [Starlingx-discuss] [build-report] r/stx.6.0 STX_6.0_build_layer_compiler - Build # 1 - Failure! In-Reply-To: <1235155349.13.1639167090968.JavaMail.javamailuser@localhost> References: <1235155349.13.1639167090968.JavaMail.javamailuser@localhost> Message-ID: <2a78bb96-19b9-5e3b-c235-5a8691f1c4d3@windriver.com> This was the first build attempt for r/stx.6.0 compiler layer. There was a glitch in download_mirrors.sh that prevented the initial build attempt from proceeding. The subsequent build passed, and is ready for testing. I've created a launchpad to track the issue. https://bugs.launchpad.net/starlingx/+bug/1954667 On 2021-12-10 3:11 p.m., build.starlingx at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_6.0_build_layer_compiler > Build #: 1 > Status: Failure > Timestamp: 20211210T200835Z > Branch: r/stx.6.0 > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/compiler/20211210T200835Z/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 scott.little at windriver.com Mon Dec 13 14:45:07 2021 From: scott.little at windriver.com (Scott Little) Date: Mon, 13 Dec 2021 09:45:07 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1139 - Failure! In-Reply-To: <259062696.53.1639300174862.JavaMail.javamailuser@localhost> References: <259062696.53.1639300174862.JavaMail.javamailuser@localhost> Message-ID: <36ebaee6-b826-6f09-b6d4-a75cd24e29c4@windriver.com> A build-iso failure affecting both 'flocl layer and monolithic builds of the master branch. *23:00:49* 04:00:49 cp: cannot stat ?var/www/pages/feed/rel-*/*.cfg?: No such file or directory *23:00:49* 04:00:49 Failed to copy extracted kickstarts Looks like placing the 'var' prefix on the feed path broke something. I believe the bad commit was ... https://review.opendev.org/c/starlingx/root/+/819008 I suggest we revert it unless a quick fix can be found. Scott On 2021-12-12 4:09 a.m., build.starlingx at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_master_master > Build #: 1139 > Status: Failure > Timestamp: 20211212T053000Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211212T053000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: false > FORCE_BUILD: 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 scott.little at windriver.com Mon Dec 13 14:50:28 2021 From: scott.little at windriver.com (Scott Little) Date: Mon, 13 Dec 2021 09:50:28 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1139 - Failure! In-Reply-To: <36ebaee6-b826-6f09-b6d4-a75cd24e29c4@windriver.com> References: <259062696.53.1639300174862.JavaMail.javamailuser@localhost> <36ebaee6-b826-6f09-b6d4-a75cd24e29c4@windriver.com> Message-ID: <7d1492be-c9a3-3f1c-033a-ff00855c68e9@windriver.com> I have create https://bugs.launchpad.net/starlingx/+bug/1954669 to track this issue. Scott On 2021-12-13 9:45 a.m., Scott Little wrote: > A build-iso failure affecting both 'flocl layer and monolithic builds > of the master branch. > > *23:00:49* 04:00:49 cp: cannot stat ?var/www/pages/feed/rel-*/*.cfg?: No such file or directory > *23:00:49* 04:00:49 Failed to copy extracted kickstarts > > Looks like placing the 'var' prefix on the feed path broke something. > > I believe the bad commit was ... > > https://review.opendev.org/c/starlingx/root/+/819008 > > > I suggest we revert it unless a quick fix can be found. > > Scott > > > On 2021-12-12 4:09 a.m., build.starlingx at gmail.com wrote: >> [Please note: This e-mail is from an EXTERNAL e-mail address] >> >> Project: STX_build_master_master >> Build #: 1139 >> Status: Failure >> Timestamp: 20211212T053000Z >> Branch: master >> >> Check logs at: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211212T053000Z/logs >> -------------------------------------------------------------------------------- >> Parameters >> >> BUILD_CONTAINERS_DEV: false >> BUILD_CONTAINERS_STABLE: false >> FORCE_BUILD: 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 scott.little at windriver.com Mon Dec 13 14:59:40 2021 From: scott.little at windriver.com (Scott Little) Date: Mon, 13 Dec 2021 09:59:40 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1139 - Failure! In-Reply-To: <7d1492be-c9a3-3f1c-033a-ff00855c68e9@windriver.com> References: <259062696.53.1639300174862.JavaMail.javamailuser@localhost> <36ebaee6-b826-6f09-b6d4-a75cd24e29c4@windriver.com> <7d1492be-c9a3-3f1c-033a-ff00855c68e9@windriver.com> Message-ID: <7b6a5d09-0f55-6ce0-44c9-c30dedd3b6a1@windriver.com> A revert has been posted https://review.opendev.org/c/starlingx/root/+/821515 and will soon merge. Scott On 2021-12-13 9:50 a.m., Scott Little wrote: > I have create https://bugs.launchpad.net/starlingx/+bug/1954669 > to track this issue. > > Scott > > > On 2021-12-13 9:45 a.m., Scott Little wrote: >> A build-iso failure affecting both 'flocl layer and monolithic builds >> of the master branch. >> >> *23:00:49* 04:00:49 cp: cannot stat ?var/www/pages/feed/rel-*/*.cfg?: No such file or directory >> *23:00:49* 04:00:49 Failed to copy extracted kickstarts >> >> Looks like placing the 'var' prefix on the feed path broke something. >> >> I believe the bad commit was ... >> >> https://review.opendev.org/c/starlingx/root/+/819008 >> >> >> I suggest we revert it unless a quick fix can be found. >> >> Scott >> >> >> On 2021-12-12 4:09 a.m., build.starlingx at gmail.com wrote: >>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>> >>> Project: STX_build_master_master >>> Build #: 1139 >>> Status: Failure >>> Timestamp: 20211212T053000Z >>> Branch: master >>> >>> Check logs at: >>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211212T053000Z/logs >>> -------------------------------------------------------------------------------- >>> Parameters >>> >>> BUILD_CONTAINERS_DEV: false >>> BUILD_CONTAINERS_STABLE: false >>> FORCE_BUILD: 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 scott.little at windriver.com Mon Dec 13 18:02:04 2021 From: scott.little at windriver.com (Scott Little) Date: Mon, 13 Dec 2021 13:02:04 -0500 Subject: [Starlingx-discuss] Regarding first rc of StarlingX 6.0 In-Reply-To: References: Message-ID: <3fb8047a-85a5-7173-1ec9-9f6a21bc5cef@windriver.com> I have forced a container build.? It should complete 11:00 UTC Scott On 2021-12-11 10:16 a.m., Dimofte, Alexandru wrote: > > **[Please note: This e-mail is from an EXTERNAL e-mail address] > > Hello, > > I observed that the first image of STX RC6.0 is ready on > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211211T105745Z/ > > > The issue is that we don?t have the helm-charts available for this > image. In order to run sanity tests I need the helm-charts > (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211211T105745Z/outputs/helm-charts/ > ). > > > So, I guess I need to wait for the next RC6.0 image... > > Kind regards, > > Alex > > Logo Description automatically generated > > > > Dimofte Alexandru > > Software Engineer > > PMCE TEAM > > Personal Mobile: +40 743167456 > > alexandru.dimofte at intel.com > > Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA > > Intel Romania > > > > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 5155 bytes Desc: not available URL: From scott.little at windriver.com Mon Dec 13 18:43:09 2021 From: scott.little at windriver.com (Scott Little) Date: Mon, 13 Dec 2021 13:43:09 -0500 Subject: [Starlingx-discuss] stx.6.0 Milestone-3 Declared In-Reply-To: References: Message-ID: <40f86718-e3f0-2447-0770-665a7d595446@windriver.com> The r/stx.6.0 branch has been created. The CENGN builds of the release candidate had some early teething pains with the pre-build download of the required rpms.? These have been resolved, and re-builds have completed, except the container build which should complete shortly. ETA ~23:00 UTC. http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/ Scott On 2021-12-08 12:15 p.m., Khalil, Ghada wrote: > > Hello all, > > Based on the stx.6.0 release review in the community meeting today, > the release team is declaring Milestone-3 with a date of Dec 8/2021. > > Feature Status: > > https://docs.google.com/spreadsheets/d/13p0BMlBgJXUVForOFsblAJq9jA1-FMBlmhV5TIc70IE/edit#gid=1107209846 > > > Feature Testing Status: > > https://docs.google.com/spreadsheets/d/1WG6HDjQz4n4RVZ1asw-bQRJQlk4OXWxnBgg54SxRxx8/edit > > > Details are in the stx-releases etherpad: > https://etherpad.opendev.org/p/stx-releases > > > Thank you to all community members who helped achieve this milestone. > > Regards, > > Ghada & the stx release team > > > _______________________________________________ > 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 Greg.Waines at windriver.com Mon Dec 13 19:52:01 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 13 Dec 2021 19:52:01 +0000 Subject: [Starlingx-discuss] StarlingX TSC & Community Call Message-ID: This week's TSC meeting (Dec 15/2021) is cancelled. Greg is out-of-office. We'll go straight to the Community portion of the meeting with Bill. Greg. -----Original Appointment----- From: Zvonar, Bill Sent: Wednesday, October 7, 2020 10:57 AM To: Zvonar, Bill; starlingx-discuss at lists.starlingx.io Cc: Wensley, Barton; Jones, Bruce E Subject: [Starlingx-discuss] [Starlingx-discuss] StarlingX TSC & Community Call When: Wednesday, December 15, 2021 10:00 AM-11:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Dec 13 22:35:05 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 13 Dec 2021 22:35:05 +0000 Subject: [Starlingx-discuss] Bi-weekly build meeting canceled for Dec 14 Message-ID: Next meeting will be in January. -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Tue Dec 14 16:39:34 2021 From: amy at demarco.com (Amy Marrich) Date: Tue, 14 Dec 2021 10:39:34 -0600 Subject: [Starlingx-discuss] [Diversity] D&I WG Meeting Time and IRC vs Video Poll In-Reply-To: References: Message-ID: It seems January 3rd(first Monday in January) is a holiday for most people so we will skip the January meeting. We will also extend the Doodle poll to January 19th to give folks time to participate. I will also send a reminder out in the new year. Please vote for your preferred days and times AND also for IRC and/or Video. https://doodle.com/poll/mnzxkauzwf2isssm?utm_source=poll&utm_medium=link Thanks, Amy (spotz) [Diversity] D&I WG Meeting Time and IRC vs Video Poll Amy Marrich Dec 12, 2021, 5:53 PM (2 days ago) to foundation, openstack-discuss, starlingx-discuss, kata-dev, airship-discuss, zuul-discuss, openinfralabs Hi everyone, The Diversity and Inclusion WG is holding a poll to see if there would be interest in attending if it were on another day and time as well as if IRC vs Video would be preferred. We currently meet the first Monday of the month at 17:00 UTC. And hope to have a planning meeting as our first meeting of the year. Our first meeting of the new year is slated for January 3rd at 17:00 UTC and for IRC. We will take the poll results into consideration and may cancel the January meeting to allow folks to plan on attending in which case February's meeting would be the first of the year. We are keeping to morning hours to encourage participation from EMEA but not overly early for PST folks to attend. We will keep the poll up through the end of the year. Please feel free to reach out with any questions or concerns and remember the Diversity and Inclusion WG is for ALL projects under the Open Infra Foundation! Thanks, Amy (spotz) foundation at lists.openstack.org, openstack-discuss ( openstack-discuss at lists.openstack.org), starlingx-discuss at lists.starlingx.io4 more It seems January 3rd(first Monday in January) is a holiday for most people so we will skip the January meeting. We will also extend the Doodle poll to January 19th to give folks time to participate. I will also send a reminder out in the new year. On Sun, Dec 12, 2021 at 5:53 PM Amy Marrich wrote: > Hi everyone, > > The Diversity and Inclusion WG is holding a poll to see if there would be > interest in attending if it were on another day and time as well as if IRC > vs Video would be preferred. We currently meet the first Monday of the > month at 17:00 UTC. And hope to have a planning meeting as our first > meeting of the year. > > Our first meeting of the new year is slated for January 3rd at 17:00 UTC > and for IRC. We will take the poll results into consideration and may > cancel the January meeting to allow folks to plan on attending in which > case February's meeting would be the first of the year. > > Please vote for your preferred days and times AND also for IRC and/or > Video. > https://doodle.com/poll/mnzxkauzwf2isssm?utm_source=poll&utm_medium=link > > We are keeping to morning hours to encourage participation from EMEA but > not overly early for PST folks to attend. We will keep the poll up through > the end of the year. > > Please feel free to reach out with any questions or concerns and remember > the Diversity and Inclusion WG is for ALL projects under the Open Infra > Foundation! > > Thanks, > > Amy (spotz) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Dec 14 22:43:08 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 14 Dec 2021 14:43:08 -0800 Subject: [Starlingx-discuss] StarlingX segment for the 2021 OpenInfra Foundation Annual report In-Reply-To: References: Message-ID: Hi StarlingX Community, A quick update about the OpenInfra Foundation Annual report for 2021. We are planning to release the report mid-January and therefore set the __deadline for the content to be ready by January 7, 2022__. I already typed up a skeleton for the StarlingX segment to go into the report: https://etherpad.opendev.org/p/2021_StarlingX_Annual_Update Please provide any feedback or edits that you might have before the deadline, either in the etherpad or on this mail thread. Please let me know if you have any questions. Thanks and Best Regards, Ildik? > On Dec 6, 2021, at 18:55, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > I?m reaching out to you about the OpenInfra Foundation Annual Report for 2021. > > As every year the Foundation is putting out a report to summarize the activities and achievements for a calendar year. Since the project?s launch there is a segment that covers these topics for StarlingX as well. > > While 2021 is still rolling, I know that the community is busy with STX 6.0 and other items so I put together a starting point to cover StarlingX in the report next January: https://etherpad.opendev.org/p/2021_StarlingX_Annual_Update > > > Please review the text and either add questions or comments to the etherpad or reply to this thread if you have any comments or concerns. > > Thanks, > Ildik? > > From build.starlingx at gmail.com Wed Dec 15 03:48:35 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 14 Dec 2021 22:48:35 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2336 - Failure! Message-ID: <814621931.77.1639540117864.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2336 Status: Failure Timestamp: 20211215T033838Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211215T032047Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20211215T032047Z DOCKER_BUILD_ID: jenkins-master-flock-20211215T032047Z-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/20211215T032047Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20211215T032047Z/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 15 03:48:39 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 14 Dec 2021 22:48:39 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 706 - Failure! Message-ID: <219227577.80.1639540120480.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 706 Status: Failure Timestamp: 20211215T032047Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211215T032047Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Wed Dec 15 08:34:12 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 15 Dec 2021 03:34:12 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1297 - Failure! Message-ID: <1226196858.83.1639557253589.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1297 Status: Failure Timestamp: 20211215T054144Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211215T053000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20211215T053000Z DOCKER_BUILD_ID: jenkins-master-20211215T053000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211215T053000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20211215T053000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Wed Dec 15 08:34:15 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 15 Dec 2021 03:34:15 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1142 - Failure! Message-ID: <1697874570.86.1639557256374.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1142 Status: Failure Timestamp: 20211215T053000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211215T053000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Bill.Zvonar at windriver.com Wed Dec 15 12:44:59 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 15 Dec 2021 12:44:59 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 15, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up later today. Please feel free to add other 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=20211215T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Dec 15 14:25:27 2021 From: scott.little at windriver.com (Scott Little) Date: Wed, 15 Dec 2021 09:25:27 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 706 - Failure! In-Reply-To: <219227577.80.1639540120480.JavaMail.javamailuser@localhost> References: <219227577.80.1639540120480.JavaMail.javamailuser@localhost> Message-ID: CENGN's flock layer build, master branch, failed last night on stx-openstack-helm. The same issue struck the monolithic build. I've opened a launchpad... ?https://bugs.launchpad.net/starlingx/+bug/1954927 On 2021-12-14 10:48 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 #: 706 > Status: Failure > Timestamp: 20211215T032047Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211215T032047Z/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 priyanka.k at ridenext.in Wed Dec 15 09:50:06 2021 From: priyanka.k at ridenext.in (Priyanka K) Date: Wed, 15 Dec 2021 15:20:06 +0530 Subject: [Starlingx-discuss] ansible-playbook admin password error Message-ID: Hi all, I am trying to install StarlingX R5.0 virtual All-in-one Simplex in Vmware. When I run the ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml command I am getting error as Fail if provided admin password does not meet required complexity] *** fatal: [localhost]: FAILED! => {"changed": false, "msg": "ADMIN_PASSWORD:? Password must have a minimum length of 7 characters, and must contain at least 1 upper case, 1 lower case, 1 digit, and 1 special character"} ? PLAY RECAP ********************************************************************* localhost????????????????? : ok=99?? changed=19?? unreachable=0??? failed=1 Guide us to slove this error, Thanks in advance. Regards, Priyanka.K -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Dec 15 15:18:54 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 15 Dec 2021 15:18:54 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Dec 15, 2021) In-Reply-To: References: Message-ID: >From today's meeting, below. We agreed to cancel the next two meetings & reconvene on Jan 5 next year. Bill... * Standing Topics * Build/Sanity * stx master build broke last night (stx.6.0 is fine) * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-December/012547.html * OpenStack team to investigate (Hugo/Douglas/Thiago) - possibly they've already fixed it * Scott to kick a new build to see if that's the case * stx.6.0 sanity * Alex will send the latest sanity results by tomorrow * per Ghada, we will move to builds on demand now for stx.6.0, there will be at least two more after this one * Alex confirmed that sanity will be kicked automatically whenever a new stx.6.0 build is available * Gerrit Reviews in Need of Attention * nothing this week * Topics for this Week * stx.6.0 status * branch was created & build happened ok, waiting for sanity results & additional cherry-picks (per above) & then doc branching * see https://etherpad.opendev.org/p/stx-releases * given how late in the year we are, we will likely do the formal completion in early January * meetings for the next 2 weeks * proposing to cancel both (Dec 22 & Dec 29) * agreed to cancel both * OpenInfra Report * see http://lists.starlingx.io/pipermail/starlingx-discuss/2021-December/012541.html * deadline for comments is Jan 7 * ARs from Previous Meetings * nothing this week * Open Requests for Help * nothing this week From: Zvonar, Bill Sent: Wednesday, December 15, 2021 7:45 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Dec 15, 2021) Hi all, reminder of the weekly TSC/Community calls coming up later today. Please feel free to add other 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=20211215T1500? [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From Tee.Ngo at windriver.com Wed Dec 15 15:41:07 2021 From: Tee.Ngo at windriver.com (Ngo, Tee) Date: Wed, 15 Dec 2021 15:41:07 +0000 Subject: [Starlingx-discuss] ansible-playbook admin password error In-Reply-To: References: Message-ID: Hi, Please check if you have admin_password parameter specified in the host overrides file (e.g. localhost.yml). It appears that the provided value does not meet the required complexity as stated in the error msg. Tee From: Priyanka K Sent: Wednesday, December 15, 2021 4:50 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] ansible-playbook admin password error [Please note: This e-mail is from an EXTERNAL e-mail address] Hi all, I am trying to install StarlingX R5.0 virtual All-in-one Simplex in Vmware. When I run the ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml command I am getting error as Fail if provided admin password does not meet required complexity] *** fatal: [localhost]: FAILED! => {"changed": false, "msg": "ADMIN_PASSWORD: Password must have a minimum length of 7 characters, and must contain at least 1 upper case, 1 lower case, 1 digit, and 1 special character"} PLAY RECAP ********************************************************************* localhost : ok=99 changed=19 unreachable=0 failed=1 Guide us to slove this error, Thanks in advance. Regards, Priyanka.K -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Wed Dec 15 22:01:18 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 15 Dec 2021 22:01:18 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 15-Dec-21 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 ========== 15-Dec-21?? . All -- reviews merged since last meeting:? 23?? ??? ?? Reviews in progress: ???????https://review.opendev.org/c/starlingx/docs/+/820946? (STX 6.0 Release Notes, Mary)? ???????https://review.opendev.org/c/starlingx/docs/+/821118? (Archive old config guides, Mary)?? ???????https://review.opendev.org/c/starlingx/docs/+/821751? (Ron and Juanita looking into this one) ???????https://review.opendev.org/c/starlingx/docs/+/819621? (Litao Gao new sample application - to be reviewed when there's time) ???????????????? . All -- bug status -- 9 total - team agrees to defer all low priority LP until the upstreaming effort is completed.? Status/questions/opens Cancel meetings next 2 weeks? Yes. Officially we?will cancel the sessions, but we can use this time slot if we need it for discussion.? Mary is working Mon-Wed next 2 weeks.? RN review now includes changes to main index/landing page. We can publish/merge the RN review and hold off cutting the branch until after new year. Need to wait and see how things play out next week. From maryx.camp at intel.com Wed Dec 15 22:02:02 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 15 Dec 2021 22:02:02 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Docs Team Call Message-ID: Meeting cancelled 22-Dec-21 Extending the meeting series through 30-Mar-22 - 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2238 bytes Desc: not available URL: From maryx.camp at intel.com Wed Dec 15 22:02:27 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 15 Dec 2021 22:02:27 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Docs Team Call Message-ID: Meeting cancelled 29-Dec-21 Extending the meeting series through 30-Mar-22 - 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2238 bytes Desc: not available URL: From alexandru.dimofte at intel.com Thu Dec 16 09:37:40 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 16 Dec 2021 09:37:40 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211215T150340Z Message-ID: Sanity Test from 2021-December-12 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211215T150340Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211215T150340Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Virtual Environment: 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 ] Sanity Test executed on Bare Metal Environment: AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 88 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Thu Dec 16 13:16:10 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 16 Dec 2021 13:16:10 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211216T032351Z Message-ID: Sanity Test from 2021-December-16 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211216T032351Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211216T032351Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Virtual Environment: Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Sanity Test executed on Bare Metal Environment: AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 71 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 83 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 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 ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From Ghada.Khalil at windriver.com Thu Dec 16 19:54:54 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 16 Dec 2021 19:54:54 +0000 Subject: [Starlingx-discuss] Regarding first rc of StarlingX 6.0 In-Reply-To: References: Message-ID: Hi Alex, Any news on sanity with the stx.6.0 rc builds? I saw a sanity from the main branch today, but not from the stx.6.0 branch yet. Thanks, Ghada From: Dimofte, Alexandru Sent: Saturday, December 11, 2021 10:16 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Regarding first rc of StarlingX 6.0 [Please note: This e-mail is from an EXTERNAL e-mail address] Hello, I observed that the first image of STX RC6.0 is ready on http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211211T105745Z/ The issue is that we don't have the helm-charts available for this image. In order to run sanity tests I need the helm-charts (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211211T105745Z/outputs/helm-charts/). So, I guess I need to wait for the next RC6.0 image... Kind regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 4767 bytes Desc: image003.png URL: From alexandru.dimofte at intel.com Thu Dec 16 20:47:08 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 16 Dec 2021 20:47:08 +0000 Subject: [Starlingx-discuss] Sanity RC6.0 Test LAYERED build ISO 20211215T131045Z Message-ID: Sanity Test from 2021-December-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211215T131045Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211215T131045Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz We executed the Sanity for RC6.0 first image but all bare-metal configurations are affected by : https://bugs.launchpad.net/starlingx/+bug/1955076 - 200.006 controller-0 is degraded due to the failure of its 'sw-patch-agent' process. Auto recovery of this major process is in progress. Obs: All virtual configurations are GREEN. Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Thu Dec 16 20:51:16 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 16 Dec 2021 20:51:16 +0000 Subject: [Starlingx-discuss] Regarding first rc of StarlingX 6.0 In-Reply-To: References: Message-ID: Hi Ghada, Yes, I sent this report a bit late because I triggered the sanity twice on the bare-metal configurations. All virtual configurations are green but in the same time, all bare-metal configurations are failing at the provisioning step because the controller-0 availability is "degraded". I also observed this alarm: "200.006 controller-0 is degraded due to the failure of its 'sw-patch-agent' process. Auto recovery of this major process is in progress.", so I opened the LP: https://bugs.launchpad.net/starlingx/+bug/1955076 Best regards, Alex From: Khalil, Ghada Sent: Thursday, December 16, 2021 9:55 PM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Regarding first rc of StarlingX 6.0 Hi Alex, Any news on sanity with the stx.6.0 rc builds? I saw a sanity from the main branch today, but not from the stx.6.0 branch yet. Thanks, Ghada From: Dimofte, Alexandru > Sent: Saturday, December 11, 2021 10:16 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Regarding first rc of StarlingX 6.0 [Please note: This e-mail is from an EXTERNAL e-mail address] Hello, I observed that the first image of STX RC6.0 is ready on http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211211T105745Z/ The issue is that we don't have the helm-charts available for this image. In order to run sanity tests I need the helm-charts (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211211T105745Z/outputs/helm-charts/). So, I guess I need to wait for the next RC6.0 image... Kind regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 4767 bytes Desc: image001.png URL: From Ghada.Khalil at windriver.com Thu Dec 16 22:33:06 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 16 Dec 2021 22:33:06 +0000 Subject: [Starlingx-discuss] Regarding first rc of StarlingX 6.0 In-Reply-To: References: Message-ID: Thanks for the update Alex. Al Bailey is looking into the LP. From: Dimofte, Alexandru Sent: Thursday, December 16, 2021 3:51 PM To: Khalil, Ghada ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Regarding first rc of StarlingX 6.0 [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Ghada, Yes, I sent this report a bit late because I triggered the sanity twice on the bare-metal configurations. All virtual configurations are green but in the same time, all bare-metal configurations are failing at the provisioning step because the controller-0 availability is "degraded". I also observed this alarm: "200.006 controller-0 is degraded due to the failure of its 'sw-patch-agent' process. Auto recovery of this major process is in progress.", so I opened the LP: https://bugs.launchpad.net/starlingx/+bug/1955076 Best regards, Alex From: Khalil, Ghada > Sent: Thursday, December 16, 2021 9:55 PM To: Dimofte, Alexandru >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Regarding first rc of StarlingX 6.0 Hi Alex, Any news on sanity with the stx.6.0 rc builds? I saw a sanity from the main branch today, but not from the stx.6.0 branch yet. Thanks, Ghada From: Dimofte, Alexandru > Sent: Saturday, December 11, 2021 10:16 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Regarding first rc of StarlingX 6.0 [Please note: This e-mail is from an EXTERNAL e-mail address] Hello, I observed that the first image of STX RC6.0 is ready on http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211211T105745Z/ The issue is that we don't have the helm-charts available for this image. In order to run sanity tests I need the helm-charts (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211211T105745Z/outputs/helm-charts/). So, I guess I need to wait for the next RC6.0 image... Kind regards, Alex [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 4767 bytes Desc: image001.png URL: From Ghada.Khalil at windriver.com Thu Dec 16 22:44:25 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 16 Dec 2021 22:44:25 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Dec 15/202 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Dec 15 2021 stx.6.0 - Release/Feature Planning Spreadsheet: https://docs.google.com/spreadsheets/d/13p0BMlBgJXUVForOFsblAJq9jA1-FMBlmhV5TIc70IE/edit#gid=1107209846 - Test Tracking Spreadsheets: https://drive.google.com/drive/folders/1lfm073XaFGxHZSAf0RPS1DGK6QCReO9u - r/stx.6.0 Status - Branch: https://review.opendev.org/q/projects:starlingx+branch:r/stx.6.0 - Builds: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/ - Build schedule will be on demand - Cherry-picks: All were posted. Two left to merge - Sanity: Starting within the next day as per Alex - stx.6.0 Bugs - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.6.0 - As of Dec 15, 3 bugs are currently open. - 2 CVEs; will not hold up the release as they can be cherrypicked later - 1 recently tagged for openstack by a community user: https://bugs.launchpad.net/starlingx/+bug/1950406 - Test Update - All feature testing is complete - Ran automation regression last week. Analyzing results now. - Pass Rate: 86.5%. Will re-run the failed TCs to rule out env issues. - Doc Update - Doc branch was not created as per plan - Draft of release notes is available for review: https://review.opendev.org/c/starlingx/docs/+/820946 - Making good progress on finishing up the required reviews: https://review.opendev.org/q/project:starlingx%252Fdocs+status:open - Target doc branch: Dec 20; otherwise will wait for early Jan. will discuss w/ doc team by email - Blog Post Update / Release Announcement - Release Announcement - Prime: Ildiko - Planned for early Jan - Certificate Management Improvement Blog - Prime: Ghada / Sabeel - Info sent to Ildiko. - Ildiko is converting it to markdown. Will create tentative pull request, but will only merge after the release announcement. - Distributed Cloud Scalability Blog - Prime: Ram S - Started. Target is to provide to Ildiko by Jan 15. From mamatha.m at ridenext.in Thu Dec 16 10:59:04 2021 From: mamatha.m at ridenext.in (Mamatha M) Date: Thu, 16 Dec 2021 16:29:04 +0530 Subject: [Starlingx-discuss] push-docker-images : Download images and push to local registry Message-ID: Hi everyone, I am trying to install StarlingX R5.0 virtual All-in-one Simplex in VMware , I am stuck while running ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml command. I have attached the log below. After getting into to the controller-0 console it is not getting connected to the internet. Please anyone suggest some solutions to this issues. I am trying to slove this from past 2 weeks. Thanks in advance. Regards, Mamatha. M PLAY [all] ********************************************************************* TASK [common/prepare-env : stat] *********************************************** ok: [localhost -> localhost] => (item=/root/secrets.yml) ok: [localhost -> localhost] => (item=/root/localhost_secrets.yml) ok: [localhost -> localhost] => (item=/root/site.yml) ok: [localhost -> localhost] => (item=/root/localhost.yml) TASK [common/prepare-env : include_vars] *************************************** TASK [common/prepare-env : Set SSH port] *************************************** TASK [common/prepare-env : Update SSH known hosts] ***************************** TASK [common/prepare-env : Check connectivity] ********************************* TASK [common/prepare-env : Fail if host is unreachable] ************************ TASK [common/prepare-env : Fail if password change response sequence is not defined] *** TASK [common/prepare-env : debug] ********************************************** TASK [common/prepare-env : Change initial password] **************************** TASK [common/validate-target : set_fact] *************************************** ok: [localhost] TASK [common/validate-target : Gather facts if check_bootstrap_address is turned on] *** TASK [common/validate-target : Retrieve software version number] *************** changed: [localhost] TASK [common/validate-target : Fail if software version is not defined] ******** TASK [common/validate-target : Retrieve system type] *************************** changed: [localhost] TASK [common/validate-target : Fail if system type is not defined] ************* TASK [common/validate-target : Set host software version, system type] ********* ok: [localhost] TASK [common/validate-target : Fail if host software version is not supported by this playbook] *** TASK [common/validate-target : Check if the system is ready] ******************* TASK [common/validate-target : Fail if the host was not installed with the right software version] *** TASK [common/validate-target : set_fact] *************************************** TASK [common/validate-target : Fail if the boot address does not exist in this host (IPv4)] *** TASK [common/validate-target : Fail if the boot address does not exist in this host (IPv6)] *** TASK [common/validate-target : Query list of applied patches on master] ******** TASK [common/validate-target : Query list of applied patches on the target] **** TASK [common/validate-target : Fail if the applied patch list on target differs from that on the master] *** TASK [common/validate-target : Set software version, system type config path facts] *** ok: [localhost] TASK [bootstrap/prepare-env : Look for unmistakenly StarlingX packages] ******** changed: [localhost] TASK [bootstrap/prepare-env : Fail if host is not running the right image] ***** TASK [bootstrap/prepare-env : Fail if any of the mandatory configurations are not defined] *** TASK [bootstrap/prepare-env : Set config path facts] *************************** ok: [localhost] TASK [bootstrap/prepare-env : Check initial config flag] *********************** ok: [localhost] TASK [bootstrap/prepare-env : Check if bootstrap_finalized flag exists on host] *** ok: [localhost] TASK [bootstrap/prepare-env : Fail if host is unlocked or host configurations have already started] *** TASK [bootstrap/prepare-env : Set initial address facts if not defined. They will be updated later] *** ok: [localhost] TASK [bootstrap/prepare-env : set_fact] **************************************** TASK [bootstrap/prepare-env : Set default registries dictionary] *************** ok: [localhost] TASK [bootstrap/prepare-env : Save the list of user defined registry keys] ***** ok: [localhost] TASK [bootstrap/prepare-env : Merge user and default registries dictionaries] *** ok: [localhost] TASK [bootstrap/prepare-env : Initialize some flags to be used in subsequent roles/tasks] *** ok: [localhost] TASK [bootstrap/prepare-env : Set initial facts] ******************************* ok: [localhost] TASK [bootstrap/prepare-env : Turn on use_docker_proxy flag] ******************* TASK [bootstrap/prepare-env : Set default values for individual platform registries and registry secrets] *** ok: [localhost] TASK [bootstrap/prepare-env : Set default values for additional images list] *** ok: [localhost] TASK [bootstrap/prepare-env : Set default values for OpenID connect] *********** ok: [localhost] TASK [bootstrap/prepare-env : Set default values for docker proxies if not defined] *** ok: [localhost] TASK [bootstrap/prepare-env : Set default values for kubernetes certificate parameters if not defined] *** ok: [localhost] TASK [bootstrap/prepare-env : Set bootstrap output file] *********************** ok: [localhost] TASK [bootstrap/prepare-env : Check Docker status] ***************************** changed: [localhost] TASK [bootstrap/prepare-env : Look for openrc file] **************************** ok: [localhost] TASK [bootstrap/prepare-env : Turn on replayed flag] *************************** ok: [localhost] TASK [bootstrap/prepare-env : Turn off save_password flag] ********************* ok: [localhost] TASK [bootstrap/prepare-env : Check the overall status of the previous play] *** ok: [localhost] TASK [bootstrap/prepare-env : Turn on incomplete_bootstrap flag if the previous play did not complete] *** ok: [localhost] TASK [bootstrap/prepare-env : Check the initial database population status] **** ok: [localhost] TASK [bootstrap/prepare-env : Turn on initial_db_populated and restart_services flags if initial db population did complete] *** ok: [localhost] TASK [bootstrap/prepare-env : Remove bootstrap_completed flag for the current play if the previous play succeeded] *** TASK [bootstrap/prepare-env : Turn on initial_db_populated flag] *************** TASK [bootstrap/prepare-env : Find previous config file for this host] ********* ok: [localhost] TASK [bootstrap/prepare-env : Turn on last_config_file_exists flag] ************ TASK [bootstrap/prepare-env : Set last config file to import (local)] ********** TASK [bootstrap/prepare-env : Set last config file to import (remote)] ********* TASK [bootstrap/prepare-env : Fetch previous config file from this host] ******* TASK [bootstrap/prepare-env : Read in last config values] ********************** TASK [bootstrap/prepare-env : Turn on system attributes reconfiguration flag] *** TASK [bootstrap/prepare-env : Convert previous docker no proxy config value for comparison] *** TASK [bootstrap/prepare-env : Turn on docker reconfiguration flag if docker config is changed] *** TASK [bootstrap/prepare-env : Turn on service endpoints reconfiguration flag if management and/or oam network config is changed] *** TASK [bootstrap/prepare-env : Turn on service endpoints reconfiguration flag if distributed_cloud_role is changed] *** TASK [bootstrap/prepare-env : Turn on network reconfiguration flag if any of the network related config is changed] *** TASK [bootstrap/prepare-env : Turn on restart services flag if management/oam/cluster network or docker config is changed] *** TASK [bootstrap/prepare-env : Turn on restart services flag if Kubernetes OpenID config is changed] *** TASK [bootstrap/prepare-env : Turn off save_config_to_db flag] ***************** TASK [bootstrap/prepare-env : Check volume groups] ***************************** changed: [localhost] TASK [bootstrap/prepare-env : Check size of root disk] ************************* changed: [localhost] TASK [bootstrap/prepare-env : Check for valid Platform Backup partition] ******* TASK [bootstrap/prepare-env : Fail if Platform Backup partition is not valid] *** TASK [bootstrap/prepare-env : Update root disk index for remote play] ********** TASK [bootstrap/prepare-env : Set root disk and root disk size facts] ********** ok: [localhost] TASK [bootstrap/prepare-env : debug] ******************************************* TASK [bootstrap/prepare-env : include_tasks] *********************************** TASK [bootstrap/prepare-env : Look for branding tar file] ********************** ok: [localhost] TASK [bootstrap/prepare-env : Fail if there are more than one branding tar files] *** TASK [bootstrap/prepare-env : Look for other branding files] ******************* ok: [localhost] TASK [bootstrap/prepare-env : Fail if the branding filename is not valid] ****** TASK [bootstrap/prepare-env : Mark environment as Ansible bootstrap] *********** changed: [localhost] TASK [bootstrap/prepare-env : Set up Ansible remote tmp dir] ******************* ok: [localhost] TASK [bootstrap/prepare-env : debug] ******************************************* ok: [localhost] => { "msg": "system_config_update flag: False, network_config_update flag: False, docker_config_update flag: False, restart_services flag: True, endpoints_reconfiguration_flag: False, save_password flag: False, save_config_to_db flag: True, incomplete_bootstrap flag: True, initial_db_populated_flag: True, dc_role_changed_flag: False" } TASK [bootstrap/validate-config : Fail if any of the configured registry keys is unknown] *** TASK [bootstrap/validate-config : Check k8s_registry credentials] ************** TASK [bootstrap/validate-config : Check gcr_registry credentials] ************** TASK [bootstrap/validate-config : Check quay_registry credentials] ************* TASK [bootstrap/validate-config : Check docker_registry credentials] *********** TASK [bootstrap/validate-config : Check elastic_registry credentials] ********** TASK [bootstrap/validate-config : Check ghcr_registry credentials] ************* TASK [bootstrap/validate-config : Check defaults registry credentials] ********* TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] => (item=None) ok: [localhost] => (item=None) ok: [localhost] => (item=None) ok: [localhost] => (item=None) ok: [localhost] => (item=None) ok: [localhost] => (item=None) ok: [localhost] TASK [bootstrap/validate-config : debug] *************************************** ok: [localhost] => { "msg": [ "System mode is simplex", "Timezone is UTC", "Distributed Cloud Role is none", "Region name is RegionOne", "DNS servers is [u'8.8.8.8', u'8.8.4.4']", "PXE boot subnet is 169.254.202.0/24", "Management subnet is 192.168.204.0/24", "Cluster host subnet is 192.168.206.0/24", "Cluster pod subnet is 172.16.0.0/16", "Cluster service subnet is 10.96.0.0/12", "OAM subnet is 10.10.10.0/24", "OAM gateway is 10.10.10.1", "OAM floating ip is 10.10.10.2", "Management dynamic address allocation is True", "Cluster host dynamic address allocation is True", "Docker registries is {u'quay.io': {u'url': None, 'password': u'secret'}, u'ghcr.io': {u'url': None, 'password': u'secret'}, u'docker.elastic.co': {u'url': None, 'password': u'secret'}, u'gcr.io': {u'url': None, 'password': u'secret'}, u'k8s.gcr.io': {u'url': None, 'password': u'secret'}, u'docker.io': {u'url': None, 'password': u'secret'}}", "Docker HTTP proxy is undef", "Docker HTTPS proxy is undef", "Docker no proxy list is []", "Applications are []" ] } TASK [bootstrap/validate-config : Set system mode fact] ************************ ok: [localhost] TASK [bootstrap/validate-config : debug] *************************************** TASK [bootstrap/validate-config : Set system mode to duplex for Standard system] *** TASK [bootstrap/validate-config : Validate system mode if system type is All-in-one] *** TASK [bootstrap/validate-config : Validate virtual system setting] ************* TASK [bootstrap/validate-config : Fail if virtual system type is not All-in-one] *** TASK [bootstrap/validate-config : Validate distributed cloud role] ************* TASK [bootstrap/validate-config : Validate system type and system mode if distributed cloud role is system controller] *** TASK [bootstrap/validate-config : Validate virtual system setting if distributed cloud role is system controller] *** TASK [bootstrap/validate-config : Checking registered timezones] *************** ok: [localhost] TASK [bootstrap/validate-config : Fail if provided timezone is unknown] ******** TASK [bootstrap/validate-config : Fail if the number of dns servers provided is not at least 1 and no more than 3] *** TASK [bootstrap/validate-config : Check format of DNS server IP(s)] ************ ok: [localhost] => (item=8.8.8.8) => { "msg": "DNS Server: 8.8.8.8" } ok: [localhost] => (item=8.8.4.4) => { "msg": "DNS Server: 8.8.4.4" } TASK [bootstrap/validate-config : Validate provided subnets (both IPv4 & IPv6 notations)] *** ok: [localhost] => (item={'value': u'10.10.10.0/24', 'key': u'external_oam_subnet'}) => { "msg": "external_oam_subnet: 10.10.10.0/24" } ok: [localhost] => (item={'value': u'192.168.206.0/24', 'key': u'cluster_host_subnet'}) => { "msg": "cluster_host_subnet: 192.168.206.0/24" } ok: [localhost] => (item={'value': u'10.10.10.1', 'key': u'external_oam_gateway_address'}) => { "msg": "external_oam_gateway_address: 10.10.10.1" } ok: [localhost] => (item={'value': u'10.96.0.0/12', 'key': u'cluster_service_subnet'}) => { "msg": "cluster_service_subnet: 10.96.0.0/12" } ok: [localhost] => (item={'value': u'169.254.202.0/24', 'key': u'pxeboot_subnet'}) => { "msg": "pxeboot_subnet: 169.254.202.0/24" } ok: [localhost] => (item={'value': u'239.1.1.0/28', 'key': u'management_multicast_subnet'}) => { "msg": "management_multicast_subnet: 239.1.1.0/28" } ok: [localhost] => (item={'value': u'192.168.204.0/24', 'key': u'management_subnet'}) => { "msg": "management_subnet: 192.168.204.0/24" } ok: [localhost] => (item={'value': u'172.16.0.0/16', 'key': u'cluster_pod_subnet'}) => { "msg": "cluster_pod_subnet: 172.16.0.0/16" } ok: [localhost] => (item={'value': u'10.10.10.2', 'key': u'external_oam_floating_address'}) => { "msg": "external_oam_floating_address: 10.10.10.2" } TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : Validate all network subnets are IPv4] ******* ok: [localhost] => (item=192.168.204.0/24) => { "msg": "All infrastructure and cluster subnets must be the same IP version" } ok: [localhost] => (item=192.168.206.0/24) => { "msg": "All infrastructure and cluster subnets must be the same IP version" } ok: [localhost] => (item=172.16.0.0/16) => { "msg": "All infrastructure and cluster subnets must be the same IP version" } ok: [localhost] => (item=10.96.0.0/12) => { "msg": "All infrastructure and cluster subnets must be the same IP version" } ok: [localhost] => (item=10.10.10.0/24) => { "msg": "All infrastructure and cluster subnets must be the same IP version" } ok: [localhost] => (item=239.1.1.0/28) => { "msg": "All infrastructure and cluster subnets must be the same IP version" } TASK [bootstrap/validate-config : Validate all network subnets are IPv6] ******* TASK [bootstrap/validate-config : Validate pxeboot subnet is IPv4] ************* ok: [localhost] => { "msg": "pxeboot_subnet subnet must always be IPv4" } TASK [bootstrap/validate-config : Generate warning if subnet prefix is not typical for Standard systems] *** TASK [bootstrap/validate-config : Fail if IPv6 prefix length is too short] ***** TASK [bootstrap/validate-config : Fail if management address allocation is misconfigured] *** TASK [bootstrap/validate-config : Fail if cluster-host address allocation is misconfigured] *** TASK [bootstrap/validate-config : Fail if management start or end address is not configured for System Controller] *** TASK [bootstrap/validate-config : Set default start and end addresses based on provided subnets] *** ok: [localhost] TASK [bootstrap/validate-config : Build address pairs for validation, merging default and user provided values] *** ok: [localhost] TASK [bootstrap/validate-config : include] ************************************* included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address_range.yml for localhost => (item={'key': u'oam_node', 'value': {u'start': u'10.10.10.3', u'end': u'10.10.10.4', u'subnet': u'10.10.10.0/24'}}) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address_range.yml for localhost => (item={'key': u'cluster_pod', 'value': {u'start': u'172.16.0.1', u'end': u'172.16.255.254', u'subnet': u'172.16.0.0/16'}}) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address_range.yml for localhost => (item={'key': u'management', 'value': {u'start': u'192.168.204.1', u'end': u'192.168.204.254', u'subnet': u'192.168.204.0/24'}}) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address_range.yml for localhost => (item={'key': u'multicast', 'value': {u'start': u'239.1.1.1', u'end': u'239.1.1.14', u'subnet': u'239.1.1.0/28'}}) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address_range.yml for localhost => (item={'key': u'cluster_service', 'value': {u'start': u'10.96.0.1', u'end': u'10.111.255.254', u'subnet': u'10.96.0.0/12'}}) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address_range.yml for localhost => (item={'key': u'oam', 'value': {u'start': u'10.10.10.1', u'end': u'10.10.10.254', u'subnet': u'10.10.10.0/24'}}) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address_range.yml for localhost => (item={'key': u'cluster_host', 'value': {u'start': u'192.168.206.1', u'end': u'192.168.206.254', u'subnet': u'192.168.206.0/24'}}) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address_range.yml for localhost => (item={'key': u'pxeboot', 'value': {u'start': u'169.254.202.1', u'end': u'169.254.202.254', u'subnet': u'169.254.202.0/24'}}) TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : Validate oam_node start and end address format] *** ok: [localhost] => { "msg": "oam_node: 10.10.10.3 10.10.10.4" } TASK [bootstrap/validate-config : Validate oam_node start and end range] ******* TASK [bootstrap/validate-config : Fail if address range did not meet required criteria] *** TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : Validate cluster_pod start and end address format] *** ok: [localhost] => { "msg": "cluster_pod: 172.16.0.1 172.16.255.254" } TASK [bootstrap/validate-config : Validate cluster_pod start and end range] **** changed: [localhost] TASK [bootstrap/validate-config : Fail if address range did not meet required criteria] *** TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : Validate management start and end address format] *** ok: [localhost] => { "msg": "management: 192.168.204.1 192.168.204.254" } TASK [bootstrap/validate-config : Validate management start and end range] ***** changed: [localhost] TASK [bootstrap/validate-config : Fail if address range did not meet required criteria] *** TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : Validate multicast start and end address format] *** ok: [localhost] => { "msg": "multicast: 239.1.1.1 239.1.1.14" } TASK [bootstrap/validate-config : Validate multicast start and end range] ****** changed: [localhost] TASK [bootstrap/validate-config : Fail if address range did not meet required criteria] *** TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : Validate cluster_service start and end address format] *** ok: [localhost] => { "msg": "cluster_service: 10.96.0.1 10.111.255.254" } TASK [bootstrap/validate-config : Validate cluster_service start and end range] *** changed: [localhost] TASK [bootstrap/validate-config : Fail if address range did not meet required criteria] *** TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : Validate oam start and end address format] *** ok: [localhost] => { "msg": "oam: 10.10.10.1 10.10.10.254" } TASK [bootstrap/validate-config : Validate oam start and end range] ************ changed: [localhost] TASK [bootstrap/validate-config : Fail if address range did not meet required criteria] *** TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : Validate cluster_host start and end address format] *** ok: [localhost] => { "msg": "cluster_host: 192.168.206.1 192.168.206.254" } TASK [bootstrap/validate-config : Validate cluster_host start and end range] *** changed: [localhost] TASK [bootstrap/validate-config : Fail if address range did not meet required criteria] *** TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : Validate pxeboot start and end address format] *** ok: [localhost] => { "msg": "pxeboot: 169.254.202.1 169.254.202.254" } TASK [bootstrap/validate-config : Validate pxeboot start and end range] ******** changed: [localhost] TASK [bootstrap/validate-config : Fail if address range did not meet required criteria] *** TASK [bootstrap/validate-config : Set OAM address list] ************************ ok: [localhost] TASK [bootstrap/validate-config : Update OAM address list for duplex] ********** TASK [bootstrap/validate-config : Set floating addresses based on subnets or start addresses] *** ok: [localhost] TASK [bootstrap/validate-config : Set derived facts for subsequent tasks/roles] *** ok: [localhost] TASK [bootstrap/validate-config : Set facts for IP address provisioning against loopback interface] *** ok: [localhost] TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : Set subcloud no proxy list] ****************** TASK [bootstrap/validate-config : Update default no proxy list for subcloud] *** TASK [bootstrap/validate-config : Set default no-proxy address list (non simplex)] *** TASK [bootstrap/validate-config : Validate http proxy urls] ******************** TASK [bootstrap/validate-config : Validate no proxy addresses] ***************** TASK [bootstrap/validate-config : Add user defined no-proxy address list to default] *** TASK [bootstrap/validate-config : Turn on use_defaults_registry flag] ********** TASK [bootstrap/validate-config : set_fact] ************************************ TASK [bootstrap/validate-config : set_fact] ************************************ TASK [bootstrap/validate-config : set_fact] ************************************ TASK [bootstrap/validate-config : set_fact] ************************************ TASK [bootstrap/validate-config : set_fact] ************************************ TASK [bootstrap/validate-config : set_fact] ************************************ TASK [bootstrap/validate-config : Update use_default_registries flag] ********** ok: [localhost] TASK [bootstrap/validate-config : Validate registry type if specified] ********* TASK [bootstrap/validate-config : Fail if secure registry flag is misconfigured] *** TASK [bootstrap/validate-config : include] ************************************* included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address.yml for localhost => (item=k8s.gcr.io) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address.yml for localhost => (item=gcr.io) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address.yml for localhost => (item=quay.io) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address.yml for localhost => (item=docker.io) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address.yml for localhost => (item=docker.elastic.co) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/validate-config/tasks/validate_address.yml for localhost => (item=ghcr.io) TASK [bootstrap/validate-config : Check if the supplied address is a valid domain name or ip address] *** changed: [localhost] TASK [bootstrap/validate-config : Fail if the supplied address is not a valid domain name or ip address] *** TASK [bootstrap/validate-config : Check if the supplied address is a valid domain name or ip address] *** changed: [localhost] TASK [bootstrap/validate-config : Fail if the supplied address is not a valid domain name or ip address] *** TASK [bootstrap/validate-config : Check if the supplied address is a valid domain name or ip address] *** changed: [localhost] TASK [bootstrap/validate-config : Fail if the supplied address is not a valid domain name or ip address] *** TASK [bootstrap/validate-config : Check if the supplied address is a valid domain name or ip address] *** changed: [localhost] TASK [bootstrap/validate-config : Fail if the supplied address is not a valid domain name or ip address] *** TASK [bootstrap/validate-config : Check if the supplied address is a valid domain name or ip address] *** changed: [localhost] TASK [bootstrap/validate-config : Fail if the supplied address is not a valid domain name or ip address] *** TASK [bootstrap/validate-config : Check if the supplied address is a valid domain name or ip address] *** changed: [localhost] TASK [bootstrap/validate-config : Fail if the supplied address is not a valid domain name or ip address] *** TASK [bootstrap/validate-config : Validate additional_local_registry_images list] *** TASK [bootstrap/validate-config : set_fact] ************************************ ok: [localhost] TASK [bootstrap/validate-config : Check if images archive location exists] ***** TASK [bootstrap/validate-config : Get list of archived files] ****************** TASK [bootstrap/validate-config : Turn on images archive flag] ***************** TASK [bootstrap/validate-config : Validate applications] *********************** TASK [bootstrap/validate-config : Build application list] ********************** ok: [localhost] TASK [bootstrap/validate-config : Append applications to application list] ***** TASK [bootstrap/validate-config : Get the name of the nginx tarball] *********** ok: [localhost] TASK [bootstrap/validate-config : Get the name of the cert manager tarball] **** ok: [localhost] TASK [bootstrap/validate-config : Append default nginx entry if not present] *** ok: [localhost] => (item={u'rusr': True, u'uid': 0, u'rgrp': True, u'xoth': True, u'islnk': False, u'woth': False, u'nlink': 1, u'issock': False, u'mtime': 1630695322.0, u'gr_name': u'root', u'path': u'/usr/local/share/applications/helm/nginx-ingress-controller-1.1-15.tgz', u'xusr': True, u'atime': 1630695322.0, u'inode': 1186195, u'isgid': False, u'size': 26982, u'isdir': False, u'ctime': 1639571608.434, u'roth': True, u'isblk': False, u'xgrp': True, u'isuid': False, u'dev': 2052, u'wgrp': False, u'isreg': True, u'isfifo': False, u'mode': u'0755', u'pw_name': u'root', u'gid': 0, u'ischr': False, u'wusr': True}) TASK [bootstrap/validate-config : Append default cert manager entry if not present] *** ok: [localhost] => (item={u'rusr': True, u'uid': 0, u'rgrp': True, u'xoth': True, u'islnk': False, u'woth': False, u'nlink': 1, u'issock': False, u'mtime': 1630695317.0, u'gr_name': u'root', u'path': u'/usr/local/share/applications/helm/cert-manager-1.0-15.tgz', u'xusr': True, u'atime': 1630695317.0, u'inode': 1186462, u'isgid': False, u'size': 60211, u'isdir': False, u'ctime': 1639571610.612, u'roth': True, u'isblk': False, u'xgrp': True, u'isuid': False, u'dev': 2052, u'wgrp': False, u'isreg': True, u'isfifo': False, u'mode': u'0755', u'pw_name': u'root', u'gid': 0, u'ischr': False, u'wusr': True}) TASK [bootstrap/validate-config : Retrieve list of applications from sysinv] *** changed: [localhost] TASK [bootstrap/validate-config : Build list of existing applications] ********* ok: [localhost] TASK [bootstrap/validate-config : Remove header from application list output] *** ok: [localhost] TASK [bootstrap/validate-config : Find armada container] *********************** TASK [bootstrap/validate-config : Update /etc/resolv.conf with coredns] ******** TASK [bootstrap/validate-config : Restart armada container to pick up resolv.conf changes] *** TASK [bootstrap/validate-config : Purge old applications] ********************** TASK [bootstrap/validate-config : Revert /etc/resolv.conf from coredns] ******** TASK [bootstrap/validate-config : Validate apiserver_cert_sans list] *********** TASK [bootstrap/validate-config : Validate apiserver_cert_sans entries] ******** TASK [bootstrap/validate-config : Verify that either both Kubernetes root ca cert and key are defined or not at all] *** TASK [bootstrap/validate-config : Check for k8s_root_ca_cert file] ************* TASK [bootstrap/validate-config : Check for k8s_root_ca_key file] ************** TASK [bootstrap/validate-config : Check for ssl_ca_cert file] ****************** TASK [bootstrap/validate-config : Check OpenID Connect parameters] ************* TASK [bootstrap/validate-config : Check for Ceph data wipe flag] *************** TASK [bootstrap/validate-config : Wipe ceph osds] ****************************** changed: [localhost] TASK [bootstrap/validate-config : Result of wiping ceph osds] ****************** ok: [localhost] => { "results.stdout_lines": [] } TASK [bootstrap/validate-config : Create config workdir] *********************** changed: [localhost] TASK [bootstrap/validate-config : Generate config ini file for python sysinv db population script] *** changed: [localhost] => (item=[BOOTSTRAP_CONFIG]) changed: [localhost] => (item=CONTROLLER_HOSTNAME=controller-0) changed: [localhost] => (item=SYSTEM_TYPE=All-in-one) changed: [localhost] => (item=SYSTEM_MODE=simplex) changed: [localhost] => (item=VIRTUAL_SYSTEM=False) changed: [localhost] => (item=TIMEZONE=UTC) changed: [localhost] => (item=DISTRIBUTED_CLOUD_ROLE=none) changed: [localhost] => (item=REGION_NAME=RegionOne) changed: [localhost] => (item=SW_VERSION=21.05) changed: [localhost] => (item=NAMESERVERS=8.8.8.8,8.8.4.4) changed: [localhost] => (item=PXEBOOT_SUBNET=169.254.202.0/24) changed: [localhost] => (item=PXEBOOT_START_ADDRESS=169.254.202.1) changed: [localhost] => (item=PXEBOOT_END_ADDRESS=169.254.202.254) changed: [localhost] => (item=MANAGEMENT_SUBNET=192.168.204.0/24) changed: [localhost] => (item=MANAGEMENT_START_ADDRESS=192.168.204.1) changed: [localhost] => (item=MANAGEMENT_END_ADDRESS=192.168.204.254) changed: [localhost] => (item=MANAGEMENT_DYNAMIC_ADDRESS_ALLOCATION=True) changed: [localhost] => (item=MANAGEMENT_INTERFACE=lo) changed: [localhost] => (item=CONTROLLER_0_ADDRESS=192.168.204.2) changed: [localhost] => (item=CLUSTER_HOST_SUBNET=192.168.206.0/24) changed: [localhost] => (item=CLUSTER_HOST_START_ADDRESS=192.168.206.1) changed: [localhost] => (item=CLUSTER_HOST_END_ADDRESS=192.168.206.254) changed: [localhost] => (item=CLUSTER_HOST_DYNAMIC_ADDRESS_ALLOCATION=True) changed: [localhost] => (item=CLUSTER_POD_SUBNET=172.16.0.0/16) changed: [localhost] => (item=CLUSTER_POD_START_ADDRESS=172.16.0.1) changed: [localhost] => (item=CLUSTER_POD_END_ADDRESS=172.16.255.254) changed: [localhost] => (item=CLUSTER_SERVICE_SUBNET=10.96.0.0/12) changed: [localhost] => (item=CLUSTER_SERVICE_START_ADDRESS=10.96.0.1) changed: [localhost] => (item=CLUSTER_SERVICE_END_ADDRESS=10.111.255.254) changed: [localhost] => (item=EXTERNAL_OAM_SUBNET=10.10.10.0/24) changed: [localhost] => (item=EXTERNAL_OAM_START_ADDRESS=10.10.10.1) changed: [localhost] => (item=EXTERNAL_OAM_END_ADDRESS=10.10.10.254) changed: [localhost] => (item=EXTERNAL_OAM_GATEWAY_ADDRESS=10.10.10.1) changed: [localhost] => (item=EXTERNAL_OAM_FLOATING_ADDRESS=10.10.10.2) changed: [localhost] => (item=EXTERNAL_OAM_0_ADDRESS=10.10.10.3) changed: [localhost] => (item=EXTERNAL_OAM_1_ADDRESS=10.10.10.4) changed: [localhost] => (item=MANAGEMENT_MULTICAST_SUBNET=239.1.1.0/28) changed: [localhost] => (item=MANAGEMENT_MULTICAST_START_ADDRESS=239.1.1.1) changed: [localhost] => (item=MANAGEMENT_MULTICAST_END_ADDRESS=239.1.1.14) changed: [localhost] => (item=SYSTEM_CONTROLLER_SUBNET=none) changed: [localhost] => (item=SYSTEM_CONTROLLER_FLOATING_ADDRESS=none) changed: [localhost] => (item=SYSTEM_CONTROLLER_OAM_SUBNET=none) changed: [localhost] => (item=SYSTEM_CONTROLLER_OAM_FLOATING_ADDRESS=none) changed: [localhost] => (item=DOCKER_HTTP_PROXY=undef) changed: [localhost] => (item=DOCKER_HTTPS_PROXY=undef) changed: [localhost] => (item=DOCKER_NO_PROXY=) changed: [localhost] => (item=K8S_REGISTRY=k8s.gcr.io) changed: [localhost] => (item=GCR_REGISTRY=gcr.io) changed: [localhost] => (item=QUAY_REGISTRY=quay.io) changed: [localhost] => (item=DOCKER_REGISTRY=docker.io) changed: [localhost] => (item=ELASTIC_REGISTRY=docker.elastic.co) changed: [localhost] => (item=GHCR_REGISTRY=ghcr.io) changed: [localhost] => (item=K8S_REGISTRY_TYPE=docker) changed: [localhost] => (item=GCR_REGISTRY_TYPE=docker) changed: [localhost] => (item=QUAY_REGISTRY_TYPE=docker) changed: [localhost] => (item=DOCKER_REGISTRY_TYPE=docker) changed: [localhost] => (item=ELASTIC_REGISTRY_TYPE=docker) changed: [localhost] => (item=GHCR_REGISTRY_TYPE=docker) changed: [localhost] => (item=K8S_REGISTRY_SECURE=True) changed: [localhost] => (item=GCR_REGISTRY_SECURE=True) changed: [localhost] => (item=QUAY_REGISTRY_SECURE=True) changed: [localhost] => (item=DOCKER_REGISTRY_SECURE=True) changed: [localhost] => (item=ELASTIC_REGISTRY_SECURE=True) changed: [localhost] => (item=GHCR_REGISTRY_SECURE=True) changed: [localhost] => (item=K8S_REGISTRY_ADDITIONAL_OVERRIDES=undef) changed: [localhost] => (item=GCR_REGISTRY_ADDITIONAL_OVERRIDES=undef) changed: [localhost] => (item=QUAY_REGISTRY_ADDITIONAL_OVERRIDES=undef) changed: [localhost] => (item=DOCKER_REGISTRY_ADDITIONAL_OVERRIDES=undef) changed: [localhost] => (item=ELASTIC_REGISTRY_ADDITIONAL_OVERRIDES=undef) changed: [localhost] => (item=GHCR_REGISTRY_ADDITIONAL_OVERRIDES=undef) changed: [localhost] => (item=USE_DEFAULT_REGISTRIES=False) changed: [localhost] => (item=RECONFIGURE_ENDPOINTS=False) changed: [localhost] => (item=INITIAL_DB_POPULATED=True) changed: [localhost] => (item=INCOMPLETE_BOOTSTRAP=True) changed: [localhost] => (item=APISERVER_SANS=) changed: [localhost] => (item=OIDC_ISSUER_URL=undef) changed: [localhost] => (item=OIDC_CLIENT_ID=undef) changed: [localhost] => (item=OIDC_USERNAME_CLAIM=undef) changed: [localhost] => (item=OIDC_GROUPS_CLAIM=undef) TASK [bootstrap/validate-config : Write simplex flag] ************************** changed: [localhost] TASK [bootstrap/store-passwd : debug] ****************************************** TASK [bootstrap/store-passwd : set_fact] *************************************** TASK [bootstrap/store-passwd : Print warning if admin credentials are not stored in vault] *** TASK [bootstrap/store-passwd : Set admin username and password facts] ********** TASK [bootstrap/store-passwd : Look for password rules file] ******************* TASK [bootstrap/store-passwd : Fail if password rules file is missing] ********* TASK [bootstrap/store-passwd : Get password rules] ***************************** TASK [bootstrap/store-passwd : Get password rules description] ***************** TASK [bootstrap/store-passwd : Set password regex facts] *********************** TASK [bootstrap/store-passwd : Fail if password regex cannot be found] ********* TASK [bootstrap/store-passwd : Set password regex description fact] ************ TASK [bootstrap/store-passwd : Validate admin password] ************************ TASK [bootstrap/store-passwd : Fail if provided admin password does not meet required complexity] *** TASK [bootstrap/store-passwd : Store admin password] *************************** TASK [bootstrap/store-passwd : Set temp keyring directory fact] **************** TASK [bootstrap/store-passwd : Create temp keyring directory] ****************** TASK [bootstrap/store-passwd : Prefetch the keyring from the tarball] ********** TASK [bootstrap/store-passwd : Remove the unwanted directory] ****************** TASK [bootstrap/store-passwd : Store service passwords] ************************ TASK [bootstrap/apply-manifest : Apply bootstrap manifest (only in the initial play)] *** TASK [bootstrap/apply-manifest : Apply manifest to reconfigure etcd] *********** TASK [bootstrap/persist-config : Check if keyring data has been persisted] ***** TASK [bootstrap/persist-config : Delete the previous python_keyring directory if exists] *** TASK [bootstrap/persist-config : Persist keyring data] ************************* TASK [bootstrap/persist-config : Ensure replicated config parent directories exist] *** changed: [localhost] => (item={u'owner': u'root', u'path': u'/opt/platform/config/21.05', u'group': u'root'}) ok: [localhost] => (item={u'owner': u'sysinv', u'path': u'/opt/platform/sysinv/21.05', u'group': u'sysinv'}) TASK [bootstrap/persist-config : Get list of new config files] ***************** ok: [localhost] TASK [bootstrap/persist-config : Remove existing config files from permanent location] *** ok: [localhost] => (item={u'rusr': True, u'uid': 0, u'rgrp': True, u'xoth': False, u'islnk': False, u'woth': False, u'nlink': 1, u'issock': False, u'mtime': 1639649402.934, u'gr_name': u'root', u'path': u'/tmp/config/bootstrap_config', u'xusr': False, u'atime': 1639649402.934, u'inode': 1826407, u'isgid': False, u'size': 2472, u'isdir': False, u'ctime': 1639649402.935, u'roth': True, u'isblk': False, u'xgrp': False, u'isuid': False, u'dev': 38, u'wgrp': False, u'isreg': True, u'isfifo': False, u'mode': u'0644', u'pw_name': u'root', u'gid': 0, u'ischr': False, u'wusr': True}) TASK [bootstrap/persist-config : Move new config files to permanent location] *** changed: [localhost] TASK [bootstrap/persist-config : Delete working config directory] ************** changed: [localhost] TASK [bootstrap/persist-config : Set Postgres, PXE, branding config directory fact] *** TASK [bootstrap/persist-config : debug] **************************************** TASK [bootstrap/persist-config : Ensure Postres, PXE config directories exist] *** TASK [bootstrap/persist-config : Ensure SSL CA and etcd certs directories exist] *** TASK [bootstrap/persist-config : Get list of Postgres conf files] ************** TASK [bootstrap/persist-config : Copy postgres conf files for mate] ************ TASK [bootstrap/persist-config : Find etcd certs files] ************************ TASK [bootstrap/persist-config : Copy etcd certificates to etcd certs directory] *** TASK [bootstrap/persist-config : Create a symlink to PXE config files] ********* TASK [bootstrap/persist-config : Check if copying of branding files for mate is required] *** TASK [bootstrap/persist-config : Ensure branding config directory exists] ****** TASK [bootstrap/persist-config : Check if branding tar files exist (there should be only one)] *** TASK [bootstrap/persist-config : Copy branding tar files] ********************** TASK [bootstrap/persist-config : Get grub default kernel] ********************** TASK [bootstrap/persist-config : Add default security feature to kernel parameters] *** TASK [bootstrap/persist-config : Gather drbd status] *************************** TASK [bootstrap/persist-config : Record drbd status] *************************** TASK [bootstrap/persist-config : Check if custom banner exists] **************** ok: [localhost] TASK [bootstrap/persist-config : Apply custom banner] ************************** TASK [bootstrap/persist-config : Fail if banner customization failed] ********** TASK [bootstrap/persist-config : Shutdown Maintenance services] **************** changed: [localhost] TASK [bootstrap/persist-config : Shutdown FM services] ************************* changed: [localhost] => (item=/etc/init.d/fminit stop) changed: [localhost] => (item=/etc/init.d/fm-api stop) TASK [bootstrap/persist-config : Shut down and remove Kubernetes components] *** changed: [localhost] TASK [bootstrap/persist-config : debug] **************************************** ok: [localhost] => { "reset_info.stdout_lines": [ "[preflight] Running pre-flight checks", "[reset] No etcd config found. Assuming external etcd", "[reset] Please, manually reset etcd to prevent further issues", "[reset] Stopping the kubelet service", "[reset] Unmounting mounted directories in \"/var/lib/kubelet\"", "[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]", "[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]", "[reset] Deleting contents of stateful directories: [/var/lib/kubelet /var/lib/dockershim /var/run/kubernetes /var/lib/cni]", "", "The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d", "", "The reset process does not reset or clean up iptables rules or IPVS tables.", "If you wish to reset iptables, you must do so manually by using the \"iptables\" command.", "", "If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)", "to reset your system's IPVS tables.", "", "The reset process does not clean your kubeconfig files and you must remove them manually.", "Please, check the contents of the $HOME/.kube/config file." ] } TASK [bootstrap/persist-config : Mount kubelet-lv] ***************************** changed: [localhost] TASK [bootstrap/persist-config : Clear kubelet data] *************************** changed: [localhost] TASK [bootstrap/persist-config : Clear etcd data cache] ************************ changed: [localhost] TASK [bootstrap/persist-config : Restart etcd] ********************************* changed: [localhost] TASK [bootstrap/persist-config : Set facts derived from previous network configurations] *** TASK [bootstrap/persist-config : Set facts derived from previous floating addresses] *** TASK [bootstrap/persist-config : Set facts for the removal of addresses assigned to loopback interface] *** TASK [bootstrap/persist-config : Remove loopback interface in sysinv db and associated addresses] *** TASK [bootstrap/persist-config : Fail if removing interface addresses failed for reason other than it has been done already] *** TASK [bootstrap/persist-config : Find old registry secrets in Barbican] ******** changed: [localhost] => (item=source /etc/platform/openrc; openstack secret list -c 'Secret href' -n k8s-registry-secret -f value) changed: [localhost] => (item=source /etc/platform/openrc; openstack secret list -c 'Secret href' -n gcr-registry-secret -f value) changed: [localhost] => (item=source /etc/platform/openrc; openstack secret list -c 'Secret href' -n quay-registry-secret -f value) changed: [localhost] => (item=source /etc/platform/openrc; openstack secret list -c 'Secret href' -n docker-registry-secret -f value) changed: [localhost] => (item=source /etc/platform/openrc; openstack secret list -c 'Secret href' -n elastic-registry-secret -f value) changed: [localhost] => (item=source /etc/platform/openrc; openstack secret list -c 'Secret href' -n ghcr-registry-secret -f value) TASK [bootstrap/persist-config : Delete old registry secrets in Barbican] ****** TASK [bootstrap/persist-config : Create Barbican secret for k8s registry if credentials exist] *** TASK [bootstrap/persist-config : set_fact] ************************************* TASK [bootstrap/persist-config : Create Barbican secret for gcr registry if credentials exist] *** TASK [bootstrap/persist-config : set_fact] ************************************* TASK [bootstrap/persist-config : Create Barbican secret for quay registry if credentials exist] *** TASK [bootstrap/persist-config : set_fact] ************************************* TASK [bootstrap/persist-config : Create Barbican secret for docker registry if credentials exist] *** TASK [bootstrap/persist-config : set_fact] ************************************* TASK [bootstrap/persist-config : Create Barbican secret for elastic registry if credentials exist] *** TASK [bootstrap/persist-config : set_fact] ************************************* TASK [bootstrap/persist-config : Create Barbican secret for ghcr registry if credentials exist] *** TASK [bootstrap/persist-config : set_fact] ************************************* TASK [bootstrap/persist-config : Append config ini file with Barbican secret uuid] *** changed: [localhost] => (item=K8S_REGISTRY_SECRET=none) changed: [localhost] => (item=GCR_REGISTRY_SECRET=none) changed: [localhost] => (item=QUAY_REGISTRY_SECRET=none) changed: [localhost] => (item=DOCKER_REGISTRY_SECRET=none) changed: [localhost] => (item=ELASTIC_REGISTRY_SECRET=none) changed: [localhost] => (item=GHCR_REGISTRY_SECRET=none) TASK [bootstrap/persist-config : Set input parameters to populate config script] *** ok: [localhost] TASK [bootstrap/persist-config : Update input parameters with reconfigure system flag] *** TASK [bootstrap/persist-config : Update input parameters with reconfigure network flag] *** TASK [bootstrap/persist-config : Update input parameters with reconfigure service flag] *** TASK [bootstrap/persist-config : Update input parameters if config from previous play has not been generated or is missing] *** ok: [localhost] TASK [bootstrap/persist-config : debug] **************************************** ok: [localhost] => { "script_input": "/opt/platform/config/21.05/bootstrap_config --system --network --service" } TASK [bootstrap/persist-config : Remove the endpoint reconfig flag before reconfiguring the service endpoints] *** changed: [localhost] TASK [bootstrap/persist-config : Remove the system controller database config flag before reconfigure role] *** TASK [bootstrap/persist-config : Add the management floating address] ********** changed: [localhost] TASK [bootstrap/persist-config : Saving config in sysinv database] ************* changed: [localhost] TASK [bootstrap/persist-config : debug] **************************************** ok: [localhost] => { "populate_result": { "changed": true, "failed": false, "failed_when_result": false, "rc": 0, "stderr": "", "stderr_lines": [], "stdout": "Updating system config...\nSystem config completed.\nDeleting network and address pool for network mgmt...\nUpdating management network...\nDeleting network and address pool for network pxeboot...\nUpdating pxeboot network...\nDeleting network and address pool for network oam...\nUpdating oam network...\nDeleting network and address pool for network multicast...\nUpdating multicast network...\nDeleting network and address pool for network cluster-host...\nUpdating cluster host network...\nDeleting network and address pool for network cluster-pod...\nUpdating cluster pod network...\nDeleting network and address pool for network cluster-service...\nUpdating cluster service network...\nNetwork config completed.\nPopulating/Updating DNS config...\nDNS config completed.\nPopulating/Updating docker registry config...\nDocker registry config completed.\nSuccessfully provisioned the initial system config.\n", "stdout_lines": [ "Updating system config...", "System config completed.", "Deleting network and address pool for network mgmt...", "Updating management network...", "Deleting network and address pool for network pxeboot...", "Updating pxeboot network...", "Deleting network and address pool for network oam...", "Updating oam network...", "Deleting network and address pool for network multicast...", "Updating multicast network...", "Deleting network and address pool for network cluster-host...", "Updating cluster host network...", "Deleting network and address pool for network cluster-pod...", "Updating cluster pod network...", "Deleting network and address pool for network cluster-service...", "Updating cluster service network...", "Network config completed.", "Populating/Updating DNS config...", "DNS config completed.", "Populating/Updating docker registry config...", "Docker registry config completed.", "Successfully provisioned the initial system config." ] } } TASK [bootstrap/persist-config : Fail if populate config script throws an exception] *** TASK [bootstrap/persist-config : Wait for service endpoints reconfiguration to complete] *** ok: [localhost] TASK [bootstrap/persist-config : Restart barbican] ***************************** changed: [localhost] TASK [bootstrap/persist-config : Wait for system controller database configuration to complete] *** TASK [bootstrap/persist-config : Update sysinv with new region name] *********** TASK [bootstrap/persist-config : Restart sysinv-agent and sysinv-api to pick up sysinv.conf update] *** TASK [bootstrap/persist-config : Set flag to mark the initial db population completed milestone] *** TASK [bootstrap/persist-config : Ensure docker and containerd config directory exist] *** TASK [bootstrap/persist-config : Ensure docker and containerd proxy config exist] *** TASK [bootstrap/persist-config : Write header to docker and containerd proxy conf files] *** TASK [bootstrap/persist-config : Add http proxy URL to docker and containerd proxy conf files] *** TASK [bootstrap/persist-config : Add https proxy URL to docker and containerd proxy conf files] *** TASK [bootstrap/persist-config : Add no proxy address list to docker proxy config file] *** TASK [bootstrap/persist-config : Add no proxy address list to containerd proxy config file] *** TASK [bootstrap/persist-config : Restart Docker and containerd] **************** TASK [bootstrap/persist-config : Set source for copying certificate] *********** TASK [bootstrap/persist-config : Copy ssl_ca certificate] ********************** TASK [bootstrap/persist-config : Remove ssl_ca complete flag] ****************** TASK [bootstrap/persist-config : Add ssl_ca certificate] *********************** TASK [bootstrap/persist-config : Wait for certificate install] ***************** TASK [bootstrap/persist-config : Cleanup temporary certificate] **************** TASK [bootstrap/persist-config : Set pxeboot files source if address allocation is dynamic] *** ok: [localhost] TASK [bootstrap/persist-config : Set pxeboot files source if address allocation is static] *** TASK [bootstrap/persist-config : Set pxeboot files symlinks] ******************* ok: [localhost] => (item={u'dest': u'pxelinux.cfg/default', u'src': u'pxelinux.cfg.files/default'}) ok: [localhost] => (item={u'dest': u'pxelinux.cfg/grub.cfg', u'src': u'pxelinux.cfg.files/grub.cfg'}) TASK [bootstrap/persist-config : Update the management_interface in platform.conf] *** ok: [localhost] TASK [bootstrap/persist-config : Add new entries to platform.conf] ************* ok: [localhost] => (item=region_config=False) ok: [localhost] => (item=sw_version=21.05) ok: [localhost] => (item=vswitch_type=none) TASK [bootstrap/persist-config : Ensure distributed cloud role is removed from platform.conf] *** ok: [localhost] TASK [bootstrap/persist-config : Add distributed cloud role to platform.conf] *** TASK [bootstrap/persist-config : Update resolv.conf with list of dns servers] *** ok: [localhost] => (item=8.8.8.8) ok: [localhost] => (item=8.8.4.4) TASK [bootstrap/persist-config : Remove localhost address from resolv.conf] **** ok: [localhost] TASK [bootstrap/persist-config : Invalidate name service caching server] ******* changed: [localhost] TASK [bootstrap/persist-config : Set config path facts] ************************ ok: [localhost] TASK [bootstrap/persist-config : Ensure extra dir exist] *********************** ok: [localhost] TASK [bootstrap/persist-config : Strip the leading '/' from directories and assign them to new variables] *** TASK [bootstrap/persist-config : Look for extra dir in backup archive] ********* TASK [bootstrap/persist-config : Restore extra dir] **************************** TASK [bootstrap/persist-config : Create source and target device_images bind directories] *** ok: [localhost] => (item=/opt/platform/device_images) ok: [localhost] => (item=/www/pages/device_images) TASK [bootstrap/persist-config : Bind mount on /www/pages/device_images] ******* changed: [localhost] TASK [bootstrap/bringup-essential-services : Add loopback interface] *********** changed: [localhost] => (item=source /etc/platform/openrc; system host-if-add controller-0 lo virtual none lo -c platform -m 1500) changed: [localhost] => (item=source /etc/platform/openrc; system interface-network-assign controller-0 lo mgmt) changed: [localhost] => (item=source /etc/platform/openrc; system interface-network-assign controller-0 lo cluster-host) changed: [localhost] => (item=ip addr add 192.168.206.2/24 brd 192.168.206.255 dev lo scope host label lo:5) changed: [localhost] => (item=ip addr add 192.168.204.2/24 brd 192.168.204.255 dev lo scope host label lo:1) changed: [localhost] => (item=ip addr add 169.254.202.1/24 dev lo scope host) changed: [localhost] => (item=ip addr add 192.168.206.1/24 dev lo scope host) changed: [localhost] => (item=ip addr add 192.168.204.4/24 dev lo scope host) changed: [localhost] => (item=ip addr add 192.168.204.5/24 dev lo scope host) TASK [bootstrap/bringup-essential-services : Fail if adding interface addresses failed for reason other than it has been done before] *** TASK [bootstrap/bringup-essential-services : Remove previous management floating address if management network config has changed] *** TASK [bootstrap/bringup-essential-services : Remove existing /etc/hosts] ******* changed: [localhost] TASK [bootstrap/bringup-essential-services : Populate /etc/hosts] ************** changed: [localhost] => (item=127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4) changed: [localhost] => (item=192.168.204.1 controller) changed: [localhost] => (item=192.168.206.2 controller-0-infra) changed: [localhost] => (item=169.254.202.1 pxecontroller) changed: [localhost] => (item=10.10.10.2 oamcontroller) changed: [localhost] => (item=192.168.204.4 controller-platform-nfs) changed: [localhost] => (item=192.168.204.3 controller-1) changed: [localhost] => (item=192.168.204.2 controller-0) changed: [localhost] => (item=192.168.206.3 controller-1-infra) changed: [localhost] => (item=192.168.204.5 controller-nfs) TASK [bootstrap/bringup-essential-services : Set central registry for subcloud] *** TASK [bootstrap/bringup-essential-services : Update /etc/hosts for subcloud] *** TASK [bootstrap/bringup-essential-services : Save hosts file to permanent location] *** ok: [localhost] TASK [bootstrap/bringup-essential-services : restore /etc/hosts file] ********** TASK [bootstrap/bringup-essential-services : restore hosts in config permdir] *** TASK [bootstrap/bringup-essential-services : Temporary add central OAM as registry.central in /etc/hosts for subcloud restore] *** TASK [bootstrap/bringup-essential-services : Update name service caching server] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Set up default route to the oam gateway] *** included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/bringup-essential-services/tasks/setup_default_route.yml for localhost TASK [bootstrap/bringup-essential-services : Set the ip command based on IP address version] *** ok: [localhost] TASK [bootstrap/bringup-essential-services : Check if the default route exists] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Configure the default route] ****** TASK [bootstrap/bringup-essential-services : Fail if configuring the default route returns an error] *** TASK [bootstrap/bringup-essential-services : Copy the central registry certificate] *** TASK [bootstrap/bringup-essential-services : Load images from archives if configured] *** TASK [bootstrap/bringup-essential-services : Set insecure registries] ********** TASK [bootstrap/bringup-essential-services : Create daemon.json file for insecure registry] *** TASK [bootstrap/bringup-essential-services : Update daemon.json with registry IP] *** TASK [bootstrap/bringup-essential-services : Restart docker] ******************* TASK [bootstrap/bringup-essential-services : Create containerd config file directory] *** ok: [localhost] TASK [bootstrap/bringup-essential-services : Determine the stream_server_address for containerd] *** ok: [localhost] TASK [bootstrap/bringup-essential-services : Get guest local registry credentials] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : set_fact] ************************* ok: [localhost] TASK [bootstrap/bringup-essential-services : Determine the registry_auth for containerd] *** ok: [localhost] TASK [bootstrap/bringup-essential-services : Create config.toml file for containerd configuration] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Remove puppet template for insecure registries] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Update config.toml with insecure registries] *** TASK [bootstrap/bringup-essential-services : Get local registry credentials] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : set_fact] ************************* ok: [localhost] TASK [bootstrap/bringup-essential-services : Restart containerd] *************** changed: [localhost] TASK [bootstrap/bringup-essential-services : Generate local registry runtime config file from template] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Generate local registry readonly config file from template] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Update local registry config files] *** changed: [localhost] => (item=sed -i -e 's|<%= @registry_readonly %>|'false'|g' /etc/docker-distribution/registry/runtime_config.yml) changed: [localhost] => (item=sed -i -e 's|<%= @registry_readonly %>|'true'|g' /etc/docker-distribution/registry/readonly_config.yml) changed: [localhost] => (item=sed -i -e 's|<%= @docker_registry_host %>|'$DOCKER_REGISTRY_HOST'|g' /etc/docker-distribution/registry/runtime_config.yml) changed: [localhost] => (item=sed -i -e 's|<%= @docker_registry_host %>|'$DOCKER_REGISTRY_HOST'|g' /etc/docker-distribution/registry/readonly_config.yml) changed: [localhost] => (item=sed -i -e 's|<%= @docker_realm_host %>|'$DOCKER_REGISTRY_HOST'|g' /etc/docker-distribution/registry/runtime_config.yml) changed: [localhost] => (item=sed -i -e 's|<%= @docker_realm_host %>|'$DOCKER_REGISTRY_HOST'|g' /etc/docker-distribution/registry/readonly_config.yml) TASK [bootstrap/bringup-essential-services : Create symlink from local registry runtime config file] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Generate local registry token server config file from template] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Update local registry token server file] *** changed: [localhost] => (item=sed -i -e 's|<%= @docker_registry_host %>|'$DOCKER_REGISTRY_HOST'|g' /etc/docker-distribution/registry/token_server.conf) changed: [localhost] => (item=sed -i -e 's|<%= @registry_ks_endpoint %>|'$REGISTRY_KS_ENDPOINT'|g' /etc/docker-distribution/registry/token_server.conf) TASK [bootstrap/bringup-essential-services : Set network info for docker registry] *** ok: [localhost] TASK [bootstrap/bringup-essential-services : Generate cnf file from template] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Generate certificate and key files] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Generate pkcs1 key file] ********** changed: [localhost] TASK [bootstrap/bringup-essential-services : Remove extfile used in certificate generation] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Set certificate file and key permissions to root read-only] *** ok: [localhost] => (item=/etc/ssl/private/registry-cert.key) ok: [localhost] => (item=/etc/ssl/private/registry-cert.crt) ok: [localhost] => (item=/etc/ssl/private/registry-cert-pkcs1.key) TASK [bootstrap/bringup-essential-services : Restore certificate and key files] *** TASK [bootstrap/bringup-essential-services : Check if /etc/ssl/private/server-cert.pem exists] *** TASK [bootstrap/bringup-essential-services : Copy /etc/ssl/private/server-cert.pem to shared filesystem for mate] *** TASK [bootstrap/bringup-essential-services : Copy certificate and keys to shared filesystem for mate] *** changed: [localhost] => (item=/etc/ssl/private/registry-cert.key) changed: [localhost] => (item=/etc/ssl/private/registry-cert.crt) changed: [localhost] => (item=/etc/ssl/private/registry-cert-pkcs1.key) TASK [bootstrap/bringup-essential-services : Create docker certificate directory] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Copy certificate file to docker certificate directory] *** changed: [localhost] TASK [bootstrap/bringup-essential-services : Start registry token server] ****** changed: [localhost] TASK [bootstrap/bringup-essential-services : Start docker registry] ************ changed: [localhost] TASK [bootstrap/bringup-essential-services : Update /etc/hosts with local registry host] *** changed: [localhost] TASK [common/push-docker-images : Set default values for docker_http_proxy and docker_https_proxy if they are undefined] *** ok: [localhost] TASK [common/push-docker-images : Get docker registries if not in bootstap or restore mode] *** TASK [common/push-docker-images : Get registry credentials if registry type is AWS ECR] *** TASK [common/load-images-information : set_fact] ******************************* ok: [localhost] TASK [common/load-images-information : Get the list of kubernetes images] ****** changed: [localhost] TASK [common/load-images-information : set_fact] ******************************* ok: [localhost] TASK [common/load-images-information : Read in system images list] ************* ok: [localhost] TASK [common/load-images-information : Check if additional image config file exists] *** ok: [localhost] TASK [common/load-images-information : Read in additional system images list(s) in localhost] *** TASK [common/load-images-information : Create a temporary file on remote] ****** TASK [common/load-images-information : Fetch the additional images config in case the playbook is executed remotely] *** TASK [common/load-images-information : Read in additional system images list(s) fetched from remote] *** TASK [common/load-images-information : Remove the temporary file on remote] **** TASK [common/load-images-information : Remove override temp file on Ansible control host] *** TASK [common/load-images-information : Categorize system images] *************** ok: [localhost] TASK [common/load-images-information : Append additional static images if provisioned] *** TASK [common/load-images-information : Append RVMC image for a DC system controller] *** TASK [common/load-images-information : Append additional static images for a DC system controller if provisioned] *** TASK [common/push-docker-images : Set download images list] ******************** ok: [localhost] TASK [common/push-docker-images : Set download images list to static images if upgrading static images] *** TASK [common/push-docker-images : Set download images list to k8s network images if upgrading k8s networking] *** TASK [common/push-docker-images : Set download images list to kubernetes images if upgrading kubernetes] *** TASK [common/push-docker-images : Set download images list to netapp images if installing trident] *** TASK [common/push-docker-images : set_fact] ************************************ ok: [localhost] TASK [common/push-docker-images : debug] *************************************** ok: [localhost] => { "download_images_list": [ "k8s.gcr.io/kube-apiserver:v1.18.1", "k8s.gcr.io/kube-controller-manager:v1.18.1", "k8s.gcr.io/kube-scheduler:v1.18.1", "k8s.gcr.io/kube-proxy:v1.18.1", "k8s.gcr.io/pause:3.2", "k8s.gcr.io/etcd:3.4.3-0", "k8s.gcr.io/coredns:1.6.7", "quay.io/calico/cni:v3.12.0", "quay.io/calico/node:v3.12.0", "quay.io/calico/kube-controllers:v3.12.0", "quay.io/calico/pod2daemon-flexvol:v3.12.0", "docker.io/nfvpe/multus:v3.4", "docker.io/starlingx/k8s-cni-sriov:stx.5.0-v2.6-7-gb18123d8", "docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae", "ghcr.io/helm/tiller:v2.16.9", "quay.io/airshipit/armada:7ef4b8643b5ec5216a8f6726841e156c0aa54a1a-ubuntu_bionic", "docker.io/starlingx/n3000-opae:stx.4.0-v1.0.0", "quay.io/stackanetes/kubernetes-entrypoint:v0.3.1", "quay.io/k8scsi/snapshot-controller:v2.0.0-rc2" ] } TASK [common/push-docker-images : Set registries information] ****************** ok: [localhost] => (item={u'replaced_url': u'k8s.gcr.io', u'default_url': u'k8s.gcr.io'}) ok: [localhost] => (item={u'replaced_url': u'gcr.io', u'default_url': u'gcr.io'}) ok: [localhost] => (item={u'replaced_url': u'quay.io', u'default_url': u'quay.io'}) ok: [localhost] => (item={u'replaced_url': u'docker.io', u'default_url': u'docker.io'}) ok: [localhost] => (item={u'replaced_url': u'docker.elastic.co', u'default_url': u'docker.elastic.co'}) ok: [localhost] => (item={u'replaced_url': u'ghcr.io', u'default_url': u'ghcr.io'}) TASK [common/push-docker-images : Log in k8s, gcr, quay, ghcr, docker registries if credentials exist] *** TASK [common/push-docker-images : Get local registry credentials] ************** TASK [common/push-docker-images : set_fact] ************************************ TASK [common/push-docker-images : Download images and push to local registry] *** Sent from Mail for Windows -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Dec 16 23:22:25 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 16 Dec 2021 23:22:25 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Networking Sub-Project Meeting (bi-weekly) Message-ID: Canceling on Dec 23 due to the Christmas / Year-End holidays. We will resume our meeting in early Jan. Happy 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: 3144 bytes Desc: not available URL: From alexandru.dimofte at intel.com Fri Dec 17 13:21:10 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 17 Dec 2021 13:21:10 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211217T023654Z Message-ID: Sanity Test from 2021-December-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211217T023654Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211217T023654Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Virtual Environment: 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 ] Sanity Test executed on Bare Metal Environment: AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 71 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 83 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 88 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 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 ] Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image003.png URL: From Bill.Zvonar at windriver.com Fri Dec 17 13:22:19 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Fri, 17 Dec 2021 13:22:19 +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: 2501 bytes Desc: not available URL: From Bill.Zvonar at windriver.com Fri Dec 17 13:33:38 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Fri, 17 Dec 2021 13:33: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: 2501 bytes Desc: not available URL: From Frank.Miller at windriver.com Fri Dec 17 16:13:02 2021 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 17 Dec 2021 16:13:02 +0000 Subject: [Starlingx-discuss] Test Plan required in commit messages (was RE: Introducing Test Plan Section in Commit Message) Message-ID: StarlingX Community: Please remember to include a test section in your commit messages as per the guidelines and Ram's email from October. Thanks. Frank From: Subramanian, Ramaswamy Sent: Wednesday, October 6, 2021 8:53 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Introducing Test Plan Section in Commit Message Hello, We have received numerous feedback from various team members to improve the following items. 1. Core reviewer(s) of various repositories have very limited visibility on the tests (scenarios, count, etc) executed on the code posted for review. There is additional communication between core reviewer(s) and author to understand tests executed. In some cases, core reviewer(s) request additional test coverage. 2. Share the developer test details between development and test teams in a consistent way. In order to address the above items, we are introducing a test plan section in the commit message. This section should specify tests executed on the changed code. Please refer to the updated code submission guide for additional details. An example commit message is added to the wiki. We encourage everyone to adopt the updated commit message template effective immediately. Should you have any suggestions/feedback to improve this further, please do not hesitate to reach out. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Dec 17 20:53:55 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 17 Dec 2021 20:53:55 +0000 Subject: [Starlingx-discuss] On-demand request for r/stx.6.0 RC build Message-ID: Hi, There have been 2 merges in the r/stx.6.0 build since the last build early on 2021-12-15. Can you please trigger another build? An ISO build is sufficient; we don't need new images or helm charts as the merges are unrelated. https://review.opendev.org/q/projects:starlingx+branch:r/stx.6.0+status:merged Thanks, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Sat Dec 18 20:48:28 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 18 Dec 2021 20:48:28 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211218T023712Z Message-ID: Sanity Test from 2021-December-18 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211218T023712Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211218T023712Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Bare Metal Environment: AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 71 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 83 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 88 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 90 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 ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Sun Dec 19 10:58:32 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 19 Dec 2021 10:58:32 +0000 Subject: [Starlingx-discuss] Sanity RC6.0 Test LAYERED build ISO 20211217T221324Z Message-ID: Sanity Test from 2021-December-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211217T221324Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211217T221324Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz All configurations are affected by: https://bugs.launchpad.net/starlingx/+bug/1955329 - Ansible Bootstrap Configuration failed using stx6.0 image. /var/www/pages/helm_charts/stx-platform doesn't exist Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From Ghada.Khalil at windriver.com Mon Dec 20 15:05:40 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 20 Dec 2021 15:05:40 +0000 Subject: [Starlingx-discuss] Sanity RC6.0 Test LAYERED build ISO 20211217T221324Z In-Reply-To: References: Message-ID: Hi Alex, I've asked Scott to look into this issue. Perhaps it's an issue with the build itself as I can't see this failure related to the additional commits which recently merged in the branch. Thanks, Ghada From: Dimofte, Alexandru Sent: Sunday, December 19, 2021 5:59 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC6.0 Test LAYERED build ISO 20211217T221324Z [Please note: This e-mail is from an EXTERNAL e-mail address] Sanity Test from 2021-December-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211217T221324Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211217T221324Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz All configurations are affected by: https://bugs.launchpad.net/starlingx/+bug/1955329 - Ansible Bootstrap Configuration failed using stx6.0 image. /var/www/pages/helm_charts/stx-platform doesn't exist Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 4767 bytes Desc: image003.png URL: From nicolae.jascanu at intel.com Tue Dec 21 10:47:00 2021 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Tue, 21 Dec 2021 10:47:00 +0000 Subject: [Starlingx-discuss] Intel Validation vacation days Message-ID: <8342466f05334d8a9a4bd308bc1857d9@intel.com> Hi All, Starting with Thursday, December 23rd, Alex is on vacation till January, 3rd. We will not be able to run any daily sanity during this period. Thank you for your understanding. Regards, Nicolae Jascanu, Ph.D. Software Engineer INTEL IOTG Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue Dec 21 13:49:20 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 21 Dec 2021 13:49:20 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211221T014938Z Message-ID: Sanity Test from 2021-December-21 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211221T014938Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211221T014938Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Bare Metal Environment: AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 71 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 83 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 88 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 90 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 ] 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 ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From erin at openstack.org Tue Dec 21 17:04:04 2021 From: erin at openstack.org (Erin Disney) Date: Tue, 21 Dec 2021 11:04:04 -0600 Subject: [Starlingx-discuss] OpenInfra Summit Berlin 2022 Programming Committee Nominations Now Open Message-ID: <6C1174EE-2B8E-42C7-8354-30930F76D061@openstack.org> Hey everyone- Programming Committee nominations for the 2022 OpenInfra Summit in Berlin (June 7-9th) are now open! Programming Committees for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: Help the Summit team put together the best possible content based on your subject matter expertise Promote the individual Tracks within your networks Review the submissions and Community voting results in your particular Track Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit Ensure diversity of speakers and companies represented in your Track Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences Identify which submissions would make good content for OpenInfra Live, the virtual show hosted by the OpenInfra Foundation that encourages live questions from a global audience 2022 Summit Tracks: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops NEW: Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security Full track descriptions are available here . If you?re interested in nominating yourself or someone else to be a member of the Summit Programming Committee for a specific Track, please fill out the nomination form . Nominations will close on January 19, 2022. Programming Committee selections will occur before we close the Call for Presentations (CFP) so that the Committees can host office hours to consult on submissions, and help promote the event. CFP will be opening in January, registration and sponsorship information are already available. Please email speakersupport at openinfra.dev with any questions or feedback. Cheers, Erin Disney Event Marketing Open Infrastructure Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Dec 22 01:13:16 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 22 Dec 2021 01:13:16 +0000 Subject: [Starlingx-discuss] Sanity RC6.0 Test LAYERED build ISO 20211217T221324Z In-Reply-To: References: Message-ID: Hi Alex, https://bugs.launchpad.net/starlingx/+bug/1955329 has now been addressed. The fix is available in this build: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211221T231755Z/ It would be great if we can get a sanity attempt before the holidays. Thanks, Ghada From: Khalil, Ghada Sent: Monday, December 20, 2021 10:06 AM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io; Little, Scott Subject: Re: [Starlingx-discuss] Sanity RC6.0 Test LAYERED build ISO 20211217T221324Z Hi Alex, I've asked Scott to look into this issue. Perhaps it's an issue with the build itself as I can't see this failure related to the additional commits which recently merged in the branch. Thanks, Ghada From: Dimofte, Alexandru > Sent: Sunday, December 19, 2021 5:59 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC6.0 Test LAYERED build ISO 20211217T221324Z [Please note: This e-mail is from an EXTERNAL e-mail address] Sanity Test from 2021-December-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211217T221324Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211217T221324Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz All configurations are affected by: https://bugs.launchpad.net/starlingx/+bug/1955329 - Ansible Bootstrap Configuration failed using stx6.0 image. /var/www/pages/helm_charts/stx-platform doesn't exist Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 4767 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Wed Dec 22 12:54:36 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 22 Dec 2021 12:54:36 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211222T032116Z Message-ID: Sanity Test from 2021-December-22 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211222T032116Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211222T032116Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Bare Metal Environment: AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 71 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 83 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 88 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 90 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 ] 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 ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image003.png URL: From alexandru.dimofte at intel.com Wed Dec 22 15:06:43 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 22 Dec 2021 15:06:43 +0000 Subject: [Starlingx-discuss] Sanity RC6.0 Test LAYERED build ISO 20211221T231755Z Message-ID: Sanity Test from 2021-December-21 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211221T231755Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211221T231755Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz All configurations are affected by: https://bugs.launchpad.net/starlingx/+bug/1955329 - Ansible Bootstrap Configuration failed using stx6.0 image. /var/www/pages/helm_charts/stx-platform doesn't exist Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From Ghada.Khalil at windriver.com Wed Dec 22 16:26:50 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 22 Dec 2021 16:26:50 +0000 Subject: [Starlingx-discuss] Sanity RC6.0 Test LAYERED build ISO 20211221T231755Z In-Reply-To: References: Message-ID: Thanks Alex for trying. Scott is already away for the holidays. So we will resume the investigation early in Jan. I re-opened the LP. From: Dimofte, Alexandru Sent: Wednesday, December 22, 2021 10:07 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity RC6.0 Test LAYERED build ISO 20211221T231755Z [Please note: This e-mail is from an EXTERNAL e-mail address] Sanity Test from 2021-December-21 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211221T231755Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/centos/flock/20211221T231755Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz All configurations are affected by: https://bugs.launchpad.net/starlingx/+bug/1955329 - Ansible Bootstrap Configuration failed using stx6.0 image. /var/www/pages/helm_charts/stx-platform doesn't exist Kind regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 4767 bytes Desc: image001.png URL: From build.starlingx at gmail.com Thu Dec 23 03:16:19 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 22 Dec 2021 22:16:19 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2370 - Failure! Message-ID: <592790953.93.1640229383966.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2370 Status: Failure Timestamp: 20211223T025449Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211223T023650Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20211223T023650Z DOCKER_BUILD_ID: jenkins-master-flock-20211223T023650Z-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/20211223T023650Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20211223T023650Z/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 Thu Dec 23 03:16:25 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 22 Dec 2021 22:16:25 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 715 - Failure! Message-ID: <1262114693.96.1640229386564.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 715 Status: Failure Timestamp: 20211223T023650Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211223T023650Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Thu Dec 23 09:12:44 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 23 Dec 2021 04:12:44 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1305 - Failure! Message-ID: <1961925329.99.1640250765643.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1305 Status: Failure Timestamp: 20211223T054112Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211223T053000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20211223T053000Z DOCKER_BUILD_ID: jenkins-master-20211223T053000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211223T053000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20211223T053000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Thu Dec 23 09:12:47 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 23 Dec 2021 04:12:47 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1150 - Failure! Message-ID: <2016981761.102.1640250767935.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1150 Status: Failure Timestamp: 20211223T053000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211223T053000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Bin.Qian at windriver.com Thu Dec 23 20:43:39 2021 From: Bin.Qian at windriver.com (Qian, Bin) Date: Thu, 23 Dec 2021 20:43:39 +0000 Subject: [Starlingx-discuss] build-iso issue Message-ID: Hello, A list of code changes were merged yesterday (Dec 22nd) that relocate /pxeboot to /var/pxeboot. Unfortunately one of the changes (in the integ repo) was missing in the batch. This caused build-iso failure if you synced after that. The failure message reads like: 13:09:49 cp: cannot stat 'var/pxeboot/EFI/grubx64.efi': No such file or directory 13:09:49 Error: Could not copy all files from installer The missing change (https://review.opendev.org/c/starlingx/integ/+/822854) has been merged. If you encountered above mentioned failure, please sync integ repo. Thanks, Bin -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Dec 23 21:09:57 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 23 Dec 2021 21:09:57 +0000 Subject: [Starlingx-discuss] Canceled: Bi-weekly StarlingX Release Meeting (new time) Message-ID: Cancelling due to the Year End 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: 3111 bytes Desc: not available URL: From Venkata.Veldanda at radisys.com Fri Dec 24 08:28:19 2021 From: Venkata.Veldanda at radisys.com (Venkata Ramana Veldanda) Date: Fri, 24 Dec 2021 08:28:19 +0000 Subject: [Starlingx-discuss] StarlingX with Ubuntu/Debian Message-ID: Hi STX-Team In one of the forums, we came across StarlingX will have the host OS as Ubuntu/Debian. Could you let us know from which specific release is that ? Regards, Venkata Veldanda -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Sun Dec 26 15:51:23 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 26 Dec 2021 15:51:23 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211224T032455Z Message-ID: <647347f7272247c8b6fa70b05fd73c8d@intel.com> Sanity Test from 2021-December-24 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211224T032455Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211224T032455Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Bare Metal Environment: Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Sun Dec 26 15:53:14 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 26 Dec 2021 15:53:14 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20211225T023632Z Message-ID: <30e96de434eb49699d2f91efe85113cb@intel.com> Sanity Test from 2021-December-25 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211225T023632Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211225T023632Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Bare Metal Environment: AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 88 TCs ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer PMCE TEAM Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Str. Iancu Fotea nr. 38, mun. Galati, jud. Galati, 800017, ROMANIA 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: 5155 bytes Desc: image001.png URL: From mamatha.m at ridenext.in Tue Dec 28 06:08:12 2021 From: mamatha.m at ridenext.in (Mamatha M) Date: Tue, 28 Dec 2021 11:38:12 +0530 Subject: [Starlingx-discuss] controller-0 network unreachable Message-ID: Hi all, I am trying to install starlingX r5. All in simplex mode, in console controller-0 its not connecting to external network. Anyone know how to resolve it. Regards, Mamatha. M Sent from Mail for Windows -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Dec 30 14:45:47 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 30 Dec 2021 09:45:47 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1154 - Failure! Message-ID: <1010108172.109.1640875552489.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1154 Status: Failure Timestamp: 20211227T053000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211227T053000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Thu Dec 30 15:44:57 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 30 Dec 2021 10:44:57 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup_layered - Build # 2718 - Failure! Message-ID: <716614865.112.1640879098318.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup_layered Build #: 2718 Status: Failure Timestamp: 20211230T151408Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211230T151249Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master-flock MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20211230T151249Z DOCKER_BUILD_ID: jenkins-master-flock-20211230T151249Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211230T151249Z/logs DOCKER_BUILD_TAG: master-flock-20211230T151249Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20211230T151249Z/logs LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock From build.starlingx at gmail.com Thu Dec 30 15:44:59 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 30 Dec 2021 10:44:59 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 724 - Failure! Message-ID: <388635056.115.1640879100568.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 724 Status: Failure Timestamp: 20211230T151249Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211230T151249Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From build.starlingx at gmail.com Thu Dec 30 20:32:34 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 30 Dec 2021 15:32:34 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup_layered - Build # 2719 - Still Failing! In-Reply-To: <787213487.110.1640879094923.JavaMail.javamailuser@localhost> References: <787213487.110.1640879094923.JavaMail.javamailuser@localhost> Message-ID: <1638129880.118.1640896355992.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup_layered Build #: 2719 Status: Still Failing Timestamp: 20211230T203128Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211230T202946Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master-flock MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20211230T202946Z DOCKER_BUILD_ID: jenkins-master-flock-20211230T202946Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211230T202946Z/logs DOCKER_BUILD_TAG: master-flock-20211230T202946Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20211230T202946Z/logs LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock From build.starlingx at gmail.com Thu Dec 30 20:32:37 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 30 Dec 2021 15:32:37 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 725 - Still Failing! In-Reply-To: <634642854.113.1640879098759.JavaMail.javamailuser@localhost> References: <634642854.113.1640879098759.JavaMail.javamailuser@localhost> Message-ID: <2020938288.121.1640896358525.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 725 Status: Still Failing Timestamp: 20211230T202946Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211230T202946Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From build.starlingx at gmail.com Fri Dec 31 02:41:40 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 30 Dec 2021 21:41:40 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup_layered - Build # 2723 - Failure! Message-ID: <1877226257.126.1640918501525.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup_layered Build #: 2723 Status: Failure Timestamp: 20211231T024030Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20211231T023810Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master-containers MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20211231T023810Z DOCKER_BUILD_ID: jenkins-master-containers-20211231T023810Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20211231T023810Z/logs DOCKER_BUILD_TAG: master-containers-20211231T023810Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20211231T023810Z/logs LAYER: containers MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers From build.starlingx at gmail.com Fri Dec 31 02:41:42 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 30 Dec 2021 21:41:42 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 233 - Failure! Message-ID: <1480893503.129.1640918503572.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 233 Status: Failure Timestamp: 20211231T023810Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20211231T023810Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From build.starlingx at gmail.com Fri Dec 31 05:35:28 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 31 Dec 2021 00:35:28 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 1519 - Failure! Message-ID: <27393535.132.1640928929718.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup Build #: 1519 Status: Failure Timestamp: 20211231T053425Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211231T053000Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20211231T053000Z DOCKER_BUILD_ID: jenkins-master-20211231T053000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211231T053000Z/logs DOCKER_BUILD_TAG: master-20211231T053000Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20211231T053000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Fri Dec 31 05:35:30 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 31 Dec 2021 00:35:30 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1156 - Failure! Message-ID: <424313145.135.1640928931594.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1156 Status: Failure Timestamp: 20211231T053000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20211231T053000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From scott.little at windriver.com Fri Dec 31 15:01:36 2021 From: scott.little at windriver.com (Scott Little) Date: Fri, 31 Dec 2021 10:01:36 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 724 - Failure! In-Reply-To: <388635056.115.1640879100568.JavaMail.javamailuser@localhost> References: <388635056.115.1640879100568.JavaMail.javamailuser@localhost> Message-ID: filelock was upgraded over the holidays, breaking python 2.7 support. I'll open a launchpad to track the issue Scott On 2021-12-30 10:44 a.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 #: 724 > Status: Failure > Timestamp: 20211230T151249Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20211230T151249Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: 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: