From dtroyer at gmail.com Sun Sep 2 21:05:29 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Sun, 2 Sep 2018 16:05:29 -0500 Subject: [Starlingx-discuss] [f/centos75] Feature branch updated cleanly Message-ID: I have updated the f/centos75 feature branches in stx-integ, stx-tools and stx-upstream to merge in current master. This updates the feature branch with the current contents of the master branch. In the git log you will see a merge commit marking where the master branch commits were merged in. There were no merge conflicts, there are three merge reviews that need to be approved to complete the process: * stx-integ: https://review.openstack.org/#/c/599260/ * stx-tools: https://review.openstack.org/#/c/599262/ * stx-upstream: https://review.openstack.org/#/c/599261/ I would like a couple of the engineers working on the feature branch to +1 or +2 those and confirm all is well. The original plan was to do this weekly, getting the correct ACLs set up got in the way of doing it last week, I plan to do it again next weekend. dt -- Dean Troyer dtroyer at gmail.com From cindy.xie at intel.com Mon Sep 3 09:53:27 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 3 Sep 2018 09:53:27 +0000 Subject: [Starlingx-discuss] StarlingX non-OpenStack Distro 9/5 meeting Agenda Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B3337E2@SHSMSX104.ccr.corp.intel.com> Agenda for 9/5 meetings: * CentOS 7.5 upgrade & test status (Shuicheng, Ada), 15min * Ceph package upgrade status (Vivian), 15min * Open topics (Brent, Saul?) We have 30min slot open. Brent, Saul, anything you'd like to add? https://etherpad.openstack.org/p/stx-distro-other And also welcome others to propose topics as well. Thx. - cindy -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Sat Sep 1 01:44:53 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Sat, 1 Sep 2018 01:44:53 +0000 Subject: [Starlingx-discuss] mem run our in StarlingX Simplex bare metal install In-Reply-To: <9A85D2917C58154C960D95352B22818BAB586085@fmsmsx115.amr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F2B33075F@SHSMSX104.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB586085@fmsmsx115.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B33158C@SHSMSX104.ccr.corp.intel.com> We do not have that Simplex/baremetal setup in Shanghai yet. I am getting help from Luis. Ticket has been submitted: https://bugs.launchpad.net/starlingx/+bug/1790252 Thx. - cindy From: Jones, Bruce E Sent: Friday, August 31, 2018 11:14 PM To: Xie, Cindy ; starlingx-discuss at lists.starlingx.io; li, Subject: RE: [Starlingx-discuss] mem run our in StarlingX Simplex bare metal install Does this issue reproduce? Cindy, can you file a bug in Launchpad please? brucej From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Friday, August 31, 2018 2:47 AM To: starlingx-discuss at lists.starlingx.io; li, > Subject: [Starlingx-discuss] mem run our in StarlingX Simplex bare metal install All, 99Cloud reported that they encountered mem run out issue after StarlingX being installed in their Simplex bare metal. Below are some info provided by them: HW config: - CPU: 56c - Memory: 188GB - Hard Disck: 2400G SAS RAID1*1/480G SSD RAID1*1 - OS: bootimage0727.iso - NIC (see below picture) [cid:image001.png at 01D440FF.4AE05140] Issue: once the system being installed on bare metal server (Simplex), check the mem usage, they see the issue below: [cid:image002.png at 01D440FF.4AE05140] They didn't have chance to create any tenant VM yet due to mem is almost fully occupied (170GB). @Li Kai, please add additional info if the above is not complete. Thanks. - cindy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 44411 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 655405 bytes Desc: image002.png URL: From kailun.qin at intel.com Mon Sep 3 07:28:56 2018 From: kailun.qin at intel.com (Qin, Kailun) Date: Mon, 3 Sep 2018 07:28:56 +0000 Subject: [Starlingx-discuss] mem run our in StarlingX Simplex bare metal install In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B33075F@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F2B33075F@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi, >From the bug description and screenshot, the issue happens once after the system was installed on a bare metal server (Simplex). ovs-vswitchd processes that you suspected are running in background when 1st time the system was booting up (so more like a memory used up rather than memory leak). Correct? I'd like to check whether and how OVS supports multiple ovs-vswitchd processes (which seems abnormal to me). Would you please kindly provide the following details which may help with the triage? 1. kernel version and OVS version that you're using; 2. OVS or OVS-DPDK; 3. full screenshot (with full cmds) and additional OVS logs if possible. BTW, 1. can manually killing all OVS processes followed by starting/configuring an OVS instance/daemon work around the issue? 2. does anyone have a remote debug environment so that we could better look into the issue? Thanks! BR, Kailun From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Friday, August 31, 2018 5:47 PM To: starlingx-discuss at lists.starlingx.io; li, Subject: [Starlingx-discuss] mem run our in StarlingX Simplex bare metal install All, 99Cloud reported that they encountered mem run out issue after StarlingX being installed in their Simplex bare metal. Below are some info provided by them: HW config: - CPU: 56c - Memory: 188GB - Hard Disck: 2400G SAS RAID1*1/480G SSD RAID1*1 - OS: bootimage0727.iso - NIC (see below picture) [cid:image001.png at 01D44385.959AD290] Issue: once the system being installed on bare metal server (Simplex), check the mem usage, they see the issue below: [cid:image002.png at 01D44385.959AD290] They didn't have chance to create any tenant VM yet due to mem is almost fully occupied (170GB). @Li Kai, please add additional info if the above is not complete. Thanks. - cindy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 44411 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 655405 bytes Desc: image002.png URL: From cindy.xie at intel.com Mon Sep 3 14:21:53 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 3 Sep 2018 14:21:53 +0000 Subject: [Starlingx-discuss] Daily SW update for StarlingX deployment Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B3339F8@SHSMSX104.ccr.corp.intel.com> Is there a way that we can do SW update based on daily ISO? Say if I have 5 patches today against yesterday's build, can I just update yesterday's deployment with "sw update" feature, instead of installing a fresh ISO every day? Andy do we have such document for our community developers? Thanks. - cindy -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Mon Sep 3 14:43:54 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 3 Sep 2018 14:43:54 +0000 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: Message-ID: > I've started the process of getting the docs.starlingx.io website set up, one of > the things required is defining the Zuul publish jobs as this is how the content > gets from the build job out to the webserver. Thanks Dean > I'd like to confirm some things and ask for a bit of information: > 1. The stx-docs repo will contain most of the docs.starlingx.io site? Also it might include a section to document the existing APIs from OpenStack projects modified by StarlingX. > 3. Release notes also need to be published, should they go in > docs.starlingx.io/releasenotes/? Can we please include API Reference documentation? How about under docs.starlingx.io/api-ref/? > 4. Does anyone feel like there is a need to not use a Sphinx-generated page as > the root page? > > Given this is a Friday afternoon before a holiday weekend (for me > anyway) I am proceeding with default answers of 1=yes and 4=no to get the > process rolling, that can be changed and the rest addressed in follow-ups. Is this related to generating our documentation using tox -e [releasenotes / api-ref / doc] ? From dtroyer at gmail.com Mon Sep 3 15:03:09 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 3 Sep 2018 10:03:09 -0500 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: Message-ID: On Mon, Sep 3, 2018 at 9:43 AM, Arce Moreno, Abraham wrote: >> I'd like to confirm some things and ask for a bit of information: >> 1. The stx-docs repo will contain most of the docs.starlingx.io site? > > Also it might include a section to document the existing APIs from OpenStack projects > modified by StarlingX. api-ref is generally in-repo with its code.... >> 3. Release notes also need to be published, should they go in >> docs.starlingx.io/releasenotes/? > > Can we please include API Reference documentation? How about under > docs.starlingx.io/api-ref/? Sure. > Is this related to generating our documentation using > tox -e [releasenotes / api-ref / doc] ? Yes, those tox jobs are what generates the documents and the publish jobs are what puts it on the web server. The way to think about this is that it is probably best to consider each repo that has something to be published as a separate sub-tree on the site, with one of them (stx-docs) also being the root of the site. We'll put stx-specs at /specs and do similar with the other things to publish here. dt -- Dean Troyer dtroyer at gmail.com From abraham.arce.moreno at intel.com Mon Sep 3 15:55:43 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 3 Sep 2018 15:55:43 +0000 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: Message-ID: > > > I'd like to confirm some things and ask for a bit of information: > > > 1. The stx-docs repo will contain most of the docs.starlingx.io site? > > > > Also it might include a section to document the existing APIs from > > OpenStack projects modified by StarlingX. > > api-ref is generally in-repo with its code.... Some of these API modifications fall into one of the existing OpenStack projects [0] and modifications are done at the starlingx-staging repo level [1], that was the reason we were thinking to host them under stx-docs, based in a previous analysis done [2], the latest list is as follows: Dcmanager API v1 - starlingx-staging/stx-distcloud Extensions to Block Storage REST API - starlingx-staging/stx-python-cinderclient Extensions to Compute REST API - starlingx-staging/stx-nova Extensions to Image REST API - starlingx-staging/stx-glance Extensions to Networking REST API - starlingx-staging/stx-neutron Is stx-upstream repository another option to host these OpenStack modified APIs leaving stx-docs repository for doc type information? > > Is this related to generating our documentation using tox -e > > [releasenotes / api-ref / doc] ? > > Yes, those tox jobs are what generates the documents and the publish jobs > are what puts it on the web server. > > The way to think about this is that it is probably best to consider each repo > that has something to be published as a separate sub-tree on the site, with > one of them (stx-docs) also being the root of the site. stx-docs being the root of the site and every repo having its own doc/ directory so our working teams can take care of the whole documentation process including release notes and api-ref if applies, is this a correct assumption? stx-docs [StarlingX Landing Page] documentation > docs/ api-ref > api-ref releasenotes > releasenotes/ > We'll put stx-specs at /specs and do similar with the other things to publish > here. I will appreciate your help to feedback the patches I need to work on based on this email, the documentation projects [docs / releasenotes / api-ref] and our StarlingX repos [3] Any modification to the existing Yes / No? Once I have approval I will take 1 day to send all the gerrit reviews. [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide/API_Documentation#StarlingX_API_Existing [1] https://github.com/starlingx-staging [2] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide/API_Documentation#Analysis [3] https://ethercalc.openstack.org/sifnpbvze9lb From abraham.arce.moreno at intel.com Mon Sep 3 16:16:23 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 3 Sep 2018 16:16:23 +0000 Subject: [Starlingx-discuss] [Release] October Release Prep Kick-Off Meeting -- Call for participants In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA44CCD4@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA44CCD4@ALA-MBD.corp.ad.wrs.com> Message-ID: > Note: Release content/priorities will not be discussed in this meeting; only > mechanics and delivery mechanism. > * Release Notes > * Standard Documentation - Developer Guide / API / others Can we please include 1 minute to talk about the future involvement from our community on "[Doc] Release Notes Management"? http://lists.starlingx.io/pipermail/starlingx-discuss/2018-August/000690.html Only objective this for quick discussion is to get your feedback to the email above to help us understand if we are in the correct understanding or not to support future releases. From dtroyer at gmail.com Mon Sep 3 16:43:46 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 3 Sep 2018 11:43:46 -0500 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: Message-ID: On Mon, Sep 3, 2018 at 10:55 AM, Arce Moreno, Abraham wrote: > Some of these API modifications fall into one of the existing OpenStack projects [0] > and modifications are done at the starlingx-staging repo level [1], that was the reason > we were thinking to host them under stx-docs, based in a previous analysis done [2], > the latest list is as follows: > > Dcmanager API v1 > - starlingx-staging/stx-distcloud This will be in the DC repo which is going to be imported into Gerrit Real Soon Now. > Extensions to Block Storage REST API > - starlingx-staging/stx-python-cinderclient > Extensions to Compute REST API > - starlingx-staging/stx-nova > Extensions to Image REST API > - starlingx-staging/stx-glance > Extensions to Networking REST API > - starlingx-staging/stx-neutron Yup, I forgot about these. > Is stx-upstream repository another option to host these OpenStack modified APIs > leaving stx-docs repository for doc type information? I like this idea, it keeps -docs clean for only the new code. > stx-docs being the root of the site and every repo having its own doc/ directory > so our working teams can take care of the whole documentation process > including release notes and api-ref if applies, is this a correct assumption? > > stx-docs [StarlingX Landing Page] > > documentation > docs/ > api-ref > api-ref > releasenotes > releasenotes/ That set of references under can all be done as in-document links, the way redirects are handled makes it a bit clumsy to update. It shouldn't change frequently but I imagine we'll tweak a bit until we're happy at the start. > I will appreciate your help to feedback the patches I need to work on > based on this email, the documentation projects [docs / releasenotes / api-ref] and our > StarlingX repos [3] Any modification to the existing Yes / No? I'll come back to this tomorrow, at a glance it looks like it is on-track. > Once I have approval I will take 1 day to send all the gerrit reviews. You might want to get the first couple put together and merged to make sure everything is sorted out before doing a lot of reviews and having to go back and update them all when something is different that we originally thought. dt -- Dean Troyer dtroyer at gmail.com From elio.martinez.monroy at intel.com Mon Sep 3 18:28:27 2018 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Mon, 3 Sep 2018 18:28:27 +0000 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: Message-ID: <1466AF2176E6F040BD63860D0A241BBD1ED52E41@FMSMSX109.amr.corp.intel.com> Sorry for my comment, Are we considering to include some path in the site in order to upload reports?, should we open a thread for this as well? BR Elio -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Monday, September 3, 2018 10:56 AM To: Dean Troyer Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website > > > I'd like to confirm some things and ask for a bit of information: > > > 1. The stx-docs repo will contain most of the docs.starlingx.io site? > > > > Also it might include a section to document the existing APIs from > > OpenStack projects modified by StarlingX. > > api-ref is generally in-repo with its code.... Some of these API modifications fall into one of the existing OpenStack projects [0] and modifications are done at the starlingx-staging repo level [1], that was the reason we were thinking to host them under stx-docs, based in a previous analysis done [2], the latest list is as follows: Dcmanager API v1 - starlingx-staging/stx-distcloud Extensions to Block Storage REST API - starlingx-staging/stx-python-cinderclient Extensions to Compute REST API - starlingx-staging/stx-nova Extensions to Image REST API - starlingx-staging/stx-glance Extensions to Networking REST API - starlingx-staging/stx-neutron Is stx-upstream repository another option to host these OpenStack modified APIs leaving stx-docs repository for doc type information? > > Is this related to generating our documentation using tox -e > > [releasenotes / api-ref / doc] ? > > Yes, those tox jobs are what generates the documents and the publish > jobs are what puts it on the web server. > > The way to think about this is that it is probably best to consider > each repo that has something to be published as a separate sub-tree on > the site, with one of them (stx-docs) also being the root of the site. stx-docs being the root of the site and every repo having its own doc/ directory so our working teams can take care of the whole documentation process including release notes and api-ref if applies, is this a correct assumption? stx-docs [StarlingX Landing Page] documentation > docs/ api-ref > api-ref releasenotes > releasenotes/ > We'll put stx-specs at /specs and do similar with the other things to > publish here. I will appreciate your help to feedback the patches I need to work on based on this email, the documentation projects [docs / releasenotes / api-ref] and our StarlingX repos [3] Any modification to the existing Yes / No? Once I have approval I will take 1 day to send all the gerrit reviews. [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide/API_Documentation#StarlingX_API_Existing [1] https://github.com/starlingx-staging [2] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide/API_Documentation#Analysis [3] https://ethercalc.openstack.org/sifnpbvze9lb _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Mon Sep 3 18:51:07 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 3 Sep 2018 13:51:07 -0500 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD1ED52E41@FMSMSX109.amr.corp.intel.com> References: <1466AF2176E6F040BD63860D0A241BBD1ED52E41@FMSMSX109.amr.corp.intel.com> Message-ID: On Mon, Sep 3, 2018 at 1:28 PM, Martinez Monroy, Elio wrote: > Are we considering to include some path in the site in order to upload reports?, should we open a thread for this as well? This is a static site built from Sphinx docs. What sort of report are you thinking about? dt -- Dean Troyer dtroyer at gmail.com From elio.martinez.monroy at intel.com Mon Sep 3 19:36:50 2018 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Mon, 3 Sep 2018 19:36:50 +0000 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: <1466AF2176E6F040BD63860D0A241BBD1ED52E41@FMSMSX109.amr.corp.intel.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD1ED52E88@FMSMSX109.amr.corp.intel.com> General reporting porpuses, maybe tars, html and xml robot reports -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Monday, September 3, 2018 1:51 PM To: Martinez Monroy, Elio Cc: Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website On Mon, Sep 3, 2018 at 1:28 PM, Martinez Monroy, Elio wrote: > Are we considering to include some path in the site in order to upload reports?, should we open a thread for this as well? This is a static site built from Sphinx docs. What sort of report are you thinking about? dt -- Dean Troyer dtroyer at gmail.com From abraham.arce.moreno at intel.com Mon Sep 3 21:07:41 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 3 Sep 2018 21:07:41 +0000 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD1ED52E88@FMSMSX109.amr.corp.intel.com> References: <1466AF2176E6F040BD63860D0A241BBD1ED52E41@FMSMSX109.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED52E88@FMSMSX109.amr.corp.intel.com> Message-ID: > > Are we considering to include some path in the site in order to upload > reports?, should we open a thread for this as well? > > This is a static site built from Sphinx docs. What sort of report are you > thinking about? Reports containing results coming from our regular functional tests, an example of the output in xml: - - + + + Tests for Install and Configuration of a controller node. Author(s): - Jose Perez... + We were thinking where it could make sense to upload / post those results: - Wiki - Launchpad - Repository We also looked at how OpenStack reports results: - For every repo, under Gerrit giving a Pass / Fail - For RefStack, under their homepage page "community results" [0] - Any other that could fit our needs? Some ideas how to share StarlingX test reports: - Test wiki page to show executive summary results parsed from the given xml: - Today this is how we report under our Test wiki page [1] - Partially automated - stx-docs hosting those results parsed from the given xml to rst format: - Fully automated taking advantage of tox infrastructure, how about using "tox -e results"? - Results uploaded to doc.starlingx.io/results? [0] https://refstack.openstack.org/#/community_results [1] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary From abraham.arce.moreno at intel.com Mon Sep 3 22:58:01 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 3 Sep 2018 22:58:01 +0000 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: Message-ID: > > Once I have approval I will take 1 day to send all the gerrit reviews. > > You might want to get the first couple put together and merged to make sure > everything is sorted out before doing a lot of reviews and having to go back > and update them all when something is different that we originally thought. Sure, here you have: stx-metal [Doc] Building docs following Docs Contrib Guide https://review.openstack.org/#/c/590094/ [Doc] Release Notes Management https://review.openstack.org/#/c/599454/ [Doc] OpenStack API Reference Guide https://review.openstack.org/#/c/590097/ stx-ha [Doc] Building docs following Docs Contrib Guide https://review.openstack.org/#/c/599464/ [Doc] Release Notes Management https://review.openstack.org/#/c/599465/ [Doc] OpenStack API Reference Guide https://review.openstack.org/#/c/599466/ From dtroyer at gmail.com Mon Sep 3 23:46:12 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 3 Sep 2018 18:46:12 -0500 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: <1466AF2176E6F040BD63860D0A241BBD1ED52E41@FMSMSX109.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED52E88@FMSMSX109.amr.corp.intel.com> Message-ID: On Mon, Sep 3, 2018 at 4:07 PM, Arce Moreno, Abraham wrote: > We also looked at how OpenStack reports results: > - For every repo, under Gerrit giving a Pass / Fail This is served from a central log server that Zuul jobs push test logs to. I don't know if infra would let outside systems push here too, I'm leaning toward unlikely. All 3rd party CI systems are required to host their own logs on a public-facing server. I'm not sure why we would be any different here. dt -- Dean Troyer dtroyer at gmail.com From Ghada.Khalil at windriver.com Tue Sep 4 00:36:21 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 4 Sep 2018 00:36:21 +0000 Subject: [Starlingx-discuss] STX October Release Prep Kick-Off Meeting Message-ID: <151EE31B9FCCA54397A757BC674650F0BA44E922@ALA-MBD.corp.ad.wrs.com> This meeting focuses on prep items for the starlingx October release. Representatives from the build, docs, test, releases and technical core teams are strongly encouraged to attend. All are welcome. The agenda items (and responses received by email) are available at: https://etherpad.openstack.org/p/stx-releases If there are other topics, please add them to the above etherpad. Meeting Details: Zoom link: https://zoom.us/j/342730236 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 International numbers available: https://zoom.us/u/ed95sU7aQ Regards, Ghada PS: Moving forward, the STX releases call will be held on Tuesday 9am Eastern, starting on Sept 18 (after the PTG); separate meeting invite to follow. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3437 bytes Desc: not available URL: From Ghada.Khalil at windriver.com Tue Sep 4 01:02:08 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 4 Sep 2018 01:02:08 +0000 Subject: [Starlingx-discuss] Pre-Submission / Pre-Gerrit Testing Message-ID: <151EE31B9FCCA54397A757BC674650F0BA44E998@ALA-MBD.corp.ad.wrs.com> From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, August 15, 2018 10:58 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Meeting notes from today's project call * What level of designer testing is done, before gerrit review is submitted ? (Dariush) o Make sure at a minimum that the code builds and the dev should make sure basic functional testing on an ISO is performed - does the new code at least get executed. o Unit tests should be part of code submissions. As we build out Zuul infra those tests should be run per check in o Core Reviewers can/should ask about test status for code submissions. o Meanwhile our test infrastructure automation build-out is in progress and (long term) will help. [[GK]] I added the above points to this wiki: https://wiki.openstack.org/wiki/StarlingX/CodeSubmissionGuidelines so that it's available to any new team members. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Tue Sep 4 03:11:07 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 4 Sep 2018 03:11:07 +0000 Subject: [Starlingx-discuss] StarlingX October Release Content Message-ID: <151EE31B9FCCA54397A757BC674650F0BA44EB57@ALA-MBD.corp.ad.wrs.com> Hello all, Just an FYI, I have been working with the different sub-project teams to confirm the content for the stx.2018.10 release. The majority of the sub-teams have confirmed their content (features/enhancements) with only a few still under review. Confirmed content has been tagged using the STX tags/conventions documented on the wiki. Regarding bugs, I have been monitoring new bugs in Launchpad and assigning the sub-project tag and sometimes a candidate release. This allows the bugs to appear in the sub-project team queries (linked from the individual wikis). Queries for the release content & status (active vs merged) is available at: https://etherpad.openstack.org/p/stx-releases If there are any questions or suggestions, please let me know. Regards, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Tue Sep 4 03:47:03 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 4 Sep 2018 03:47:03 +0000 Subject: [Starlingx-discuss] Notes: StarlingX Networking meeting - 8/30 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA44EB7D@ALA-MBD.corp.ad.wrs.com> The StarlingX networking team had their first meeting on 8/30. Weekly meetings are scheduled for Thursday at 9am Eastern. Meeting Details are available on the wiki: https://wiki.openstack.org/wiki/StarlingX/Networking Meeting agenda/notes are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Aug 30/2018 * First networking team meeting; team member introductions * Intel: Forrest, Ruijen, Huifeng, Kailun, Chenjie * Wind River: Ghada, Brent, Matt * Agreed to have a team meeting weekly at Thursday 9am Eastern / 6am Pacific / 9pm China. * Action: Forrest to send out the recurring invite * Intel team focus has been on upstreaming STX neutron patches * Neutron Upstreaming Status: * Detailed spreadsheet is on google docs. Bruce can provide access (need gmail account) * Patch analysis complete * 3 features/blueprints proposed ? Plan to review the blueprints with neutron team in the PTG in Denver - Prime: Kailun/Ruijen w/ assistance from Matt ? Matt to forward email with business justification for STX neutron blueprints - Aug 30 (Done) ? Kailun/team to update blueprints and re-send for review - Aug 31 (Done) ? Matt to review first version and provide feedback - Aug 31 (Done) ? Kailun/team to incorporate feedback and re-send second version - Sept 3 (Done) ? Matt/Brent to conduct final review - Sept 4 ? Kailun/team to submit the blueprints to neutron team - Sept 5 * StarlingX ovs-dpdk Enhancements / Support * Initial ovs-dpsk integration was done by Matt Peters, but need more people in the networking team to ramp up by implementing some of the outstanding enhancements and addressing bugs * Action: Ghada to identify members of her team. Done - Steve Webster is ramping up. Already assigned one enhancement and two bugs for stx.2018.10 * Action: Forrest to identify members of his team. There is one enhancement (2002944) to be assigned and some bugs for stx.2018.10 * Networking Long Term Interest * Discussed some long term items related containerization: ? Forrest to add list here for reference * Agreed that these need to be discussed relative to the project technical direction, but are likely beyond the scope of the stx.2019.03 release ? May need to engage with the TSC on those * Networking Medium Term Items * ovs-dpdk running containerized; need to engage with the Containerized openstack team. Regards, Ghada & Forrest -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Tue Sep 4 12:13:19 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 4 Sep 2018 12:13:19 +0000 Subject: [Starlingx-discuss] [f/centos75] Feature branch updated cleanly In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C7655356808@SHSMSX101.ccr.corp.intel.com> Hi Dean, Could you help create branch for stx-root? There is rpm name change after rpm package upgrade. Thanks. Best Regards Shuicheng -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Monday, September 3, 2018 5:05 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [f/centos75] Feature branch updated cleanly I have updated the f/centos75 feature branches in stx-integ, stx-tools and stx-upstream to merge in current master. This updates the feature branch with the current contents of the master branch. In the git log you will see a merge commit marking where the master branch commits were merged in. There were no merge conflicts, there are three merge reviews that need to be approved to complete the process: * stx-integ: https://review.openstack.org/#/c/599260/ * stx-tools: https://review.openstack.org/#/c/599262/ * stx-upstream: https://review.openstack.org/#/c/599261/ I would like a couple of the engineers working on the feature branch to +1 or +2 those and confirm all is well. The original plan was to do this weekly, getting the correct ACLs set up got in the way of doing it last week, I plan to do it again next weekend. dt -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Tue Sep 4 16:11:51 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 4 Sep 2018 10:11:51 -0600 Subject: [Starlingx-discuss] Weekly meetings wiki page Message-ID: <3228201D-057C-4DA0-A86E-E944B8CB0125@gmail.com> Hi, To make it easier to find meeting information such as time slots and dial-in info I created a separate wiki page to store this information: https://wiki.openstack.org/wiki/Starlingx/Meetings I would like to ask every project team who’s already having a weekly call to use this page for sharing meeting information, you can easily use a link to point to your team’s meeting from the team wiki page or any other place you store information about your calls. This way we will have a centralized source of information that will help with keeping the information up to date and also easy to discover. I added some initial information where I had a few details, please feel free to add agenda items and description to your weekly meeting as it fits your needs. If you would like to organize a weekly call or an ad-hoc meeting using the Foundation Zoom account please __reach out to me at ildiko at openstack.org first__ before grabbing any of the links displayed on the wiki page. Please let me know if you have any questions or comments. Thanks and Best Regards, Ildikó From ildiko.vancsa at gmail.com Tue Sep 4 16:25:20 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 4 Sep 2018 10:25:20 -0600 Subject: [Starlingx-discuss] ONS Europe Edge meetup - ACTION NEEDED Message-ID: <4303236D-1E16-472B-AD9C-CB13503F88EA@gmail.com> Hi All, There are a few of us who’s planning to attend ONS Europe at the end of the month: https://events.linuxfoundation.org/events/open-networking-summit-europe-2018/ We were planning to organize an ad-hoc session to talk about edge like how we did at ONS NA in March this year. In order to find the best option as time and place for this meetup I created an etherpad to coordinate: https://etherpad.openstack.org/p/EdgeMeetup-ONS-EU-2018 __If you are attending the event and interested in participating in this gathering please add your name to the etherpad above as soon as possible.__ Please let me know if you have any questions or comments. Thanks and Best Regards, Ildikó From dtroyer at gmail.com Tue Sep 4 19:14:46 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 4 Sep 2018 14:14:46 -0500 Subject: [Starlingx-discuss] [f/centos75] Feature branch updated cleanly In-Reply-To: <9700A18779F35F49AF027300A49E7C7655356808@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356808@SHSMSX101.ccr.corp.intel.com> Message-ID: On Tue, Sep 4, 2018 at 7:13 AM, Lin, Shuicheng wrote: > Could you help create branch for stx-root? There is rpm name change after rpm package upgrade. It is created. When https://review.openstack.org/599611 merges it will be ready it use. dt -- Dean Troyer dtroyer at gmail.com From dtroyer at gmail.com Tue Sep 4 21:46:49 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 4 Sep 2018 16:46:49 -0500 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: Message-ID: On Mon, Sep 3, 2018 at 5:58 PM, Arce Moreno, Abraham wrote: > stx-metal > [Doc] Building docs following Docs Contrib Guide > https://review.openstack.org/#/c/590094/ You can add the docs build job that will actually test the configuration you are setting up. https://review.openstack.org/#/c/599041/3/.zuul.yaml should be all you need, then the results of the job is lined in the Gerrit review so you can see it before it is merged and published. This is really useful since we don't have the publising part set up yet. > [Doc] Release Notes Management > https://review.openstack.org/#/c/599454/ I've pushed up https://review.openstack.org/599831 to run the docs and relnotes build jobs to see what they looks like. > [Doc] OpenStack API Reference Guide > https://review.openstack.org/#/c/590097/ I don't have any first-hand experience with this and will come back to it...I imagine it will be very similar to the above job-wise. dt -- Dean Troyer dtroyer at gmail.com From ada.cabrales at intel.com Tue Sep 4 21:50:59 2018 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 4 Sep 2018 21:50:59 +0000 Subject: [Starlingx-discuss] Bi-Weekly StarlingX Test meeting - 9:00 PDT Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E716DFB7C@fmsmsx104.amr.corp.intel.com> Bi-weekly meetings on Tuesdays at 9am PDT / 1600 UTC * Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes: https://etherpad.openstack.org/p/stx-test -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3133 bytes Desc: not available URL: From cesar.lara at intel.com Tue Sep 4 22:12:31 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Tue, 4 Sep 2018 22:12:31 +0000 Subject: [Starlingx-discuss] Notes: Build team meeting 9/4/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47104FDA83@fmsmsx104.amr.corp.intel.com> Attendees: Hayde, Marce, Erich, Mingyuan, Memo, Mario, Chuy, Scott, Jason, Saul, Cesar Agenda Build tools - Presentation of stx command line Code freeze for October release opens Meeting Minutes Presentation on StarlingX single command - Presentation was about the steps we are taking to remove the complexity of our build scripts and wrap them around single commands as first step on having a repeatable process - We were also discussing as an extra step to use a single Docker file to do all build steps https://ethercalc.openstack.org/prvxrp1bpa - Information for single command - Comments for the presentation - We should still have a way to run each script individually for troubleshooting and debugging or in case we need to validate an specific step of the build. we may also expose a way to run scripts using parameters to the single command. - On the Docker file we should find a way to separate the contents of mirror/ and tools/ directories, due that today there is no distinction in where those live. - We may also want to discuss the boundaries on what do we store/execute on containers and what do we do on bare metal. - Comments in general - The team will review the documentation posted in the developer guide, just to make sure there are not unnecessary steps listed there. - We need to find a way on how to work with releases and manifests. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center From shuicheng.lin at intel.com Wed Sep 5 07:27:40 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 5 Sep 2018 07:27:40 +0000 Subject: [Starlingx-discuss] python-eventlet upgrade issue In-Reply-To: <5B884683.5080402@windriver.com> References: <9700A18779F35F49AF027300A49E7C7655355AEF@SHSMSX101.ccr.corp.intel.com> <5B884683.5080402@windriver.com> Message-ID: <9700A18779F35F49AF027300A49E7C7655356ABD@SHSMSX101.ccr.corp.intel.com> Hi all, The issue is caused by patch method in the new eventlet. It is still open at eventlet issue list as below link. https://github.com/eventlet/eventlet/issues/413 I don't want to change our code to workaround it. So I decide not to upgrade eventlet src rpm. Feel free to notify me if you have concern on it. Hi Chris, Thanks for your help. I will correct the '1' error if it is not done yet. Best Regards Shuicheng -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: Friday, August 31, 2018 3:33 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] python-eventlet upgrade issue On 08/29/2018 08:51 PM, Lin, Shuicheng wrote: > Hi, > > Anyone familiar with python-eventlet? I meet a problem when upgrade > python-eventlet from “0.18.4-2” to “0.20.1-2”, when do CentOS7.5 upgrade. > > Eventlet will hook/patch some basic python function, such as “call”/”check_call” > from subprocess.py > > The issue is that, after upgrade to 0.20.1-2 version, these functions > don’t work as expected. > > For the pass log (with eventlet 0.18.4), below log is as expected: > > 2018-08-28 05:38:33.816 21142 INFO sysinv.agent.pci [-] Could not > determine DPDK support for NIC (vendor 0x8086 device: 0x100e), > defaulting to False > > But for the fail log(with eventlet 0.20.1), it seems the exception is > not handled correctly: > > 2018-08-28 03:48:21.687 21302 ERROR > sysinv.openstack.common.periodic_task [-] Error during > AgentManager._agent_audit: Command '['query_pci_id', '-v 0x8086', '-d > 0x100e']' returned non-zero exit status 1 > > Is there any code style change with new eventlet? There are a couple odd things going on here. First, you found a bug. The check at http://git.openstack.org/cgit/openstack/stx-config/tree/sysinv/sysinv/sysinv/sysinv/agent/pci.py#n477 currently reads if e.returncode == '1' when it should be if e.returncode == 1 This explains why you were getting the "Could not determine DPDK support..." message" before, when really you should have been getting "DPDK does support NIC..." I can't explain why the CalledProcessError was caught by sysinv.openstack.common.periodic_task when it should have been caught (and swallowed) by http://git.openstack.org/cgit/openstack/stx-config/tree/sysinv/sysinv/sysinv/sysinv/agent/pci.py#n475 Chris _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Jason.McKenna at windriver.com Wed Sep 5 13:31:09 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Wed, 5 Sep 2018 13:31:09 +0000 Subject: [Starlingx-discuss] [Build] unified build command suggestions Message-ID: Hi Cesar and build team, I've been thinking about the proposal for the unified build command as discussed in the last build team meeting. "stx --build-iso" or "stx --create-iso" was suggested as command for building all targets - source rpms, binary rpms, and the final ISO. We should probably change that command name to "stx --build-all" or something similar. This would meet the immediate request of providing a single command to wrap around the existing steps, and would allow us to grow the tool's functionality without tying us to the concept of "an ISO == a build". As a bonus, it allows us to improve the granularity the build commands while maintaining a consistent command naming convention. A potential first cut of commands could be: # Download items specified in lst files (replaces download_mirror.sh) stx --mirror-download # Places downloaded items in the specified mirror path stx --mirror-populate # Do all mirror steps stx --mirror-all # sets up a build environment with artifacts from the specified mirror path (replaces generate-cgcs-centos-repo.sh and populate_downloads.sh) stx --build-env # builds specified package or all packages (replaces build-pkgs) stx --build-pkgs [pkg_name] # Produces an ISO from current build (replaces build-iso) stx --build-iso # Runs previous steps (I'm not sure if running --build-env during build-all is a good idea, but perhaps we could skip the --build-env if no mirror_path is specified) stx --build-all [mirror_path] Future commands like --build-patch or --sign-pkgs or --project-integrate or wherever this grows, could be added as more advanced use cases are fleshed out. Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: From vivian.zhu at intel.com Wed Sep 5 13:53:28 2018 From: vivian.zhu at intel.com (Zhu, Vivian) Date: Wed, 5 Sep 2018 13:53:28 +0000 Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Message-ID: <371DF9A763E9F44F924F4A821FC070264C4993FF@SHSMSX104.ccr.corp.intel.com> Hi Anyone who is familiar with stx-tools or build flow, Our storage team (Dehao etc.) have worked on Ceph upgrading on starlingX project and we are still staggering to resolve issues one-by-one, now we fail to build ISO, the log points to “These RPMS had problems (likely version conflicts) “. Here is our build steps and according action we did. We are looking for help to solve it, if anyone who can give some hints to narrow down/address issue or point out the wrong step here. That’s really helpful to unblock Ceph upgrade to catch up Sep.26 code freeze. Build flow step 1: download_mirror ---> container 1 | step 2: manually check *_miss_*.txt and *_fails_*.txt file, then download miss and fails package | step 3: to ensure that all package listed by rpms_from_3rd_parties.list and rpms_from_centos_repo.lst are downloaded | step 4: create work space : mkdir -p $HOME/starlingx/mirror/Centos | step 5: copy mirror to workspace which can be used by container 2 | step 6: edit Dockerfile, create image, then run container, and so on. | step 7 : clone all source using "repo sync" → container 2 | step 8: at git folder, using ceph 13.2.0 to replace ceph 10.2.6 | step 9: using ceph tools "make-srpm.sh" to create 13.2.0 ceph.spec file. | step 10 : modify new ceph.spec file according to stx-ceph's ceph.spec file | step 11: copy stx-ceph's wrs folder to ceph 13.2.0 | step 12: build-pkgs --serial | step 13: build_iso <-----------------------------fails !!! | step 14 : success building What we had done 1:can build starlingx image 2:ceph 13.2.0’s ceph.spec file can works. 3: build-pkgs can build all package What part we are gating when building ISO, deps can’t be resolved. we tried steps but failed. Stalingx log give one error conclusion as following: 22:14:55 Debug: Packages still unresolved: 22:14:55 22:14:56 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 22:14:56 These RPMS had problems (likely version conflicts) 22:14:56 librados.so.2()(64bit) 22:14:56 Could not install dependencies What’s the next step 1: Talked with Qi mingyuan, plan to compare every ceph 13.2.0 depes package with mirror’s package. 2: Deploy one starlingx cluster, check package and env. Help needed If we can get stx-tools design, implement overview or building flow, it can help us speed up the debug/upgrading. Thanks! - Vivian SSG OTC NST Storage Tel: (8621)61167437 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Sep 5 14:02:06 2018 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 5 Sep 2018 14:02:06 +0000 Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status In-Reply-To: <371DF9A763E9F44F924F4A821FC070264C4993FF@SHSMSX104.ccr.corp.intel.com> References: <371DF9A763E9F44F924F4A821FC070264C4993FF@SHSMSX104.ccr.corp.intel.com> Message-ID: Quick question: Before switching to newer version (ceph 13.2.0), have you ever built out the packages and ISO? From: "Zhu, Vivian" Date: Wednesday, 5 September 2018 at 9:54 PM To: "starlingx-discuss at lists.starlingx.io" Cc: "Shang, Dehao" Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Hi Anyone who is familiar with stx-tools or build flow, Our storage team (Dehao etc.) have worked on Ceph upgrading on starlingX project and we are still staggering to resolve issues one-by-one, now we fail to build ISO, the log points to “These RPMS had problems (likely version conflicts) “. Here is our build steps and according action we did. We are looking for help to solve it, if anyone who can give some hints to narrow down/address issue or point out the wrong step here. That’s really helpful to unblock Ceph upgrade to catch up Sep.26 code freeze. Build flow step 1: download_mirror ---> container 1 | step 2: manually check *_miss_*.txt and *_fails_*.txt file, then download miss and fails package | step 3: to ensure that all package listed by rpms_from_3rd_parties.list and rpms_from_centos_repo.lst are downloaded | step 4: create work space : mkdir -p $HOME/starlingx/mirror/Centos | step 5: copy mirror to workspace which can be used by container 2 | step 6: edit Dockerfile, create image, then run container, and so on. | step 7 : clone all source using "repo sync" → container 2 | step 8: at git folder, using ceph 13.2.0 to replace ceph 10.2.6 | step 9: using ceph tools "make-srpm.sh" to create 13.2.0 ceph.spec file. | step 10 : modify new ceph.spec file according to stx-ceph's ceph.spec file | step 11: copy stx-ceph's wrs folder to ceph 13.2.0 | step 12: build-pkgs --serial | step 13: build_iso <-----------------------------fails !!! | step 14 : success building What we had done 1:can build starlingx image 2:ceph 13.2.0’s ceph.spec file can works. 3: build-pkgs can build all package What part we are gating when building ISO, deps can’t be resolved. we tried steps but failed. Stalingx log give one error conclusion as following: 22:14:55 Debug: Packages still unresolved: 22:14:55 22:14:56 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 22:14:56 These RPMS had problems (likely version conflicts) 22:14:56 librados.so.2()(64bit) 22:14:56 Could not install dependencies What’s the next step 1: Talked with Qi mingyuan, plan to compare every ceph 13.2.0 depes package with mirror’s package. 2: Deploy one starlingx cluster, check package and env. Help needed If we can get stx-tools design, implement overview or building flow, it can help us speed up the debug/upgrading. Thanks! - Vivian SSG OTC NST Storage Tel: (8621)61167437 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Sep 5 13:54:51 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 5 Sep 2018 13:54:51 +0000 Subject: [Starlingx-discuss] Notes: StarlingX non-OpenStack Distro meeting, 9/5 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B337039@SHSMSX104.ccr.corp.intel.com> Agenda & notes for 9/5 meetings: * AR reviews (Cindy) * AR: Saul to define a more realistic goal for # of patch reductions (10%, 50% & 90% today) - let's discuss this during patch analysis. * AR:Shuicheng file a story for OS kernel upgrade to 7.5 kernel (DONE) * AR: Shuicheng to scope what is the kernel drivers needs to be upgraded (push it to Mar's release) * AR: Cindy to invite Vivian into this meeting to provide Ceph status (DONE) * non-OpenStack patch analysis sharing (Saul) * analysis results for patch catagories in pivot table: https://drive.google.com/open?id=1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMjB7VIrfc * version patches may double count: * source patches may have a higher number. * CentOS 7.5 upgrade & test status (Shuicheng, Ada) * still have 3 sRPM left (2 under debug, 1 WIP). lighttpd & puppet-haproxy. python-eventlet has upstream bug and decided to stay w/ 7.4 version. * ~260 rpm rebase to be merged. will include into this week's build. * clean build has been done and deployment and sanity tested. * Elio: GDC didn't find obvious bugs in last Friday's test build. One bug filed but this is on both master & f/CentOS7.5. testing is conducted on libvirt/qemu and not bare-metal. * kernel upgrade patch is expected be in next week's build * AR: Elio to take the question (about test on bare-metal) to Ada and Ghada take this into test sub-project meeting for tracking. * AR: Elio to send out the test report to the mailing list for the ISO built last Friday. o Ceph package upgrade status (Vivian) o Story: https://storyboard.openstack.org/#!/story/2003605 * 10.2.0 -minic version to 13.2.0. Built ISO image done; new Ceph version can be built as well. "RPM has problem?" when build the whole StarlingX ISO. * Deployment of StarlingX on storage side. Has question regarding StarlingX tools (stx-tools). * AR: Vivian to send your quesitons and ask help to StarlingX mailing list. * Open topics (Brent, Saul?) * Jim is on vacation but we will still target the libvirt/qemu and python-libvirt lib upgrade to newer version by 2018.10. From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, August 30, 2018 12:08 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Notes: StarlingX non-OpenStack Distro meeting, 8/29 Agenda & notes for 8/29 meetings: * Review Team objectives & prioritize (Cindy) Review team goal. Concern about the % patch reduction by 50% and 90% by mid of 2019 and end of 2019. Saul: define a more realistic # after patch review. * CentOS 7.5 upgrade status (Cindy) most of sRPM upgrade patches has been merged into f/centos 7.5 branch; 5 to be merged: 2 patches is under review, 1 in progress. 2 patches causes basic deployment issues: lighttpd (https://review.openstack.org/#/c/596263/) & python-eventlet-0.20.1-2.el7.src.rpm (patch# TBD); plan is to keep the SRPM in 7.4 w/ other sRPM for a test build to GDC and WR. Trending: end of Friday China time for test build; ISO to GDC, build instructions (including pending patches if needs to be cherry-picked), branch-name. Shuicheng will send this out. * OS kernel version upgrade: can we upgrade to another kernel (to be planned). Code freeze for 2018.10: Sep 26th. AR: Shuicheng file a story for OS kernel upgrade into 7.5 kernel. * Out of tree kernel driver is part of the scope? AR: Shuicheng to scope what is the kernel drivers needs to be upgraded it's OK if we cannot hit Sep 26 code freeze date. * Ceph package upgrade (Vivian Zhu is working) - part of storage team. AR: Cindy to invite Vivian into this meeting to provide the status update. recommendation from Brent: very high risk of upgrading Ceph to hit Sep 26th code freeze date. * libvirt and qemu upgrade status (Ghada) Jim has a basic build for libvirt w/ patch rebase. Finishing Qemu trending end of this week. will be off next week. Patch will not be merged before WR internal testing, will be merged before Sep 20th? * non-OpenStack patches review status (Saul) master xls: https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMjB7VIrfc/edit?usp=sharing Intel or gmail address to Bruce if you'd like to get access. Goal: to get 1st pass of analysis results by PTG (Sep 12th) * 2018.10 release content review (Ghada) * Active all storyboard: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.distro.other&project_group_id=86 * Tag 2018.10: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.distro.other&tags=stx.2018.10&project_group_id=86 * OS independent topics (Saul) - defered EOM -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Wed Sep 5 14:14:08 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 5 Sep 2018 14:14:08 +0000 Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status In-Reply-To: References: <371DF9A763E9F44F924F4A821FC070264C4993FF@SHSMSX104.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C7655356CF0@SHSMSX101.ccr.corp.intel.com> For the build-iso failure, it should be due to dependency check. There should be another file “deps-detail.txt” under the same folder as deps.txt. (/localdisk/loadbuild/dehao/starlingx/export/deps.txt) You could get more info from this file. Best Regards Shuicheng From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Wednesday, September 5, 2018 10:02 PM To: Zhu, Vivian ; starlingx-discuss at lists.starlingx.io Cc: Shang, Dehao Subject: Re: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Quick question: Before switching to newer version (ceph 13.2.0), have you ever built out the packages and ISO? From: "Zhu, Vivian" > Date: Wednesday, 5 September 2018 at 9:54 PM To: "starlingx-discuss at lists.starlingx.io" > Cc: "Shang, Dehao" > Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Hi Anyone who is familiar with stx-tools or build flow, Our storage team (Dehao etc.) have worked on Ceph upgrading on starlingX project and we are still staggering to resolve issues one-by-one, now we fail to build ISO, the log points to “These RPMS had problems (likely version conflicts) “. Here is our build steps and according action we did. We are looking for help to solve it, if anyone who can give some hints to narrow down/address issue or point out the wrong step here. That’s really helpful to unblock Ceph upgrade to catch up Sep.26 code freeze. Build flow step 1: download_mirror ---> container 1 | step 2: manually check *_miss_*.txt and *_fails_*.txt file, then download miss and fails package | step 3: to ensure that all package listed by rpms_from_3rd_parties.list and rpms_from_centos_repo.lst are downloaded | step 4: create work space : mkdir -p $HOME/starlingx/mirror/Centos | step 5: copy mirror to workspace which can be used by container 2 | step 6: edit Dockerfile, create image, then run container, and so on. | step 7 : clone all source using "repo sync" → container 2 | step 8: at git folder, using ceph 13.2.0 to replace ceph 10.2.6 | step 9: using ceph tools "make-srpm.sh" to create 13.2.0 ceph.spec file. | step 10 : modify new ceph.spec file according to stx-ceph's ceph.spec file | step 11: copy stx-ceph's wrs folder to ceph 13.2.0 | step 12: build-pkgs --serial | step 13: build_iso <-----------------------------fails !!! | step 14 : success building What we had done 1:can build starlingx image 2:ceph 13.2.0’s ceph.spec file can works. 3: build-pkgs can build all package What part we are gating when building ISO, deps can’t be resolved. we tried steps but failed. Stalingx log give one error conclusion as following: 22:14:55 Debug: Packages still unresolved: 22:14:55 22:14:56 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 22:14:56 These RPMS had problems (likely version conflicts) 22:14:56 librados.so.2()(64bit) 22:14:56 Could not install dependencies What’s the next step 1: Talked with Qi mingyuan, plan to compare every ceph 13.2.0 depes package with mirror’s package. 2: Deploy one starlingx cluster, check package and env. Help needed If we can get stx-tools design, implement overview or building flow, it can help us speed up the debug/upgrading. Thanks! - Vivian SSG OTC NST Storage Tel: (8621)61167437 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jason.McKenna at windriver.com Wed Sep 5 14:20:15 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Wed, 5 Sep 2018 14:20:15 +0000 Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status In-Reply-To: <371DF9A763E9F44F924F4A821FC070264C4993FF@SHSMSX104.ccr.corp.intel.com> References: <371DF9A763E9F44F924F4A821FC070264C4993FF@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Vivian, librados.so.2()(64bit) should be provided by the librados2 package which is built as part of ceph 10.x.x. I suspect this package did not get built in your environment (which is why build-iso fails to find it) because the updated version of ceph does not build the package. There are a few possibilities here: - Maybe librados2 is an optional output of the ceph package. You’d have to “turn on” this functionality - Maybe librados2 has been renamed or upversioned. You’d have to update the spec file for whatever is requiring librados.so.2()(64bit) to use the new name/version of the library - Maybe librados2 is no longer required. You’d have to update the spec file for whatever is requiring librados.so.2()(64bit) to remove the requirement You can check what package has the “librados.so.2()(64bit)” requirement by looking at the $MY_WORKSPACE/export/deps_detail.txt file Hope this helps! -Jason From: Zhu, Vivian Sent: September 5, 2018 9:53 AM To: starlingx-discuss at lists.starlingx.io Cc: Shang, Dehao Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Hi Anyone who is familiar with stx-tools or build flow, Our storage team (Dehao etc.) have worked on Ceph upgrading on starlingX project and we are still staggering to resolve issues one-by-one, now we fail to build ISO, the log points to “These RPMS had problems (likely version conflicts) “. Here is our build steps and according action we did. We are looking for help to solve it, if anyone who can give some hints to narrow down/address issue or point out the wrong step here. That’s really helpful to unblock Ceph upgrade to catch up Sep.26 code freeze. Build flow step 1: download_mirror ---> container 1 | step 2: manually check *_miss_*.txt and *_fails_*.txt file, then download miss and fails package | step 3: to ensure that all package listed by rpms_from_3rd_parties.list and rpms_from_centos_repo.lst are downloaded | step 4: create work space : mkdir -p $HOME/starlingx/mirror/Centos | step 5: copy mirror to workspace which can be used by container 2 | step 6: edit Dockerfile, create image, then run container, and so on. | step 7 : clone all source using "repo sync" → container 2 | step 8: at git folder, using ceph 13.2.0 to replace ceph 10.2.6 | step 9: using ceph tools "make-srpm.sh" to create 13.2.0 ceph.spec file. | step 10 : modify new ceph.spec file according to stx-ceph's ceph.spec file | step 11: copy stx-ceph's wrs folder to ceph 13.2.0 | step 12: build-pkgs --serial | step 13: build_iso <-----------------------------fails !!! | step 14 : success building What we had done 1:can build starlingx image 2:ceph 13.2.0’s ceph.spec file can works. 3: build-pkgs can build all package What part we are gating when building ISO, deps can’t be resolved. we tried steps but failed. Stalingx log give one error conclusion as following: 22:14:55 Debug: Packages still unresolved: 22:14:55 22:14:56 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 22:14:56 These RPMS had problems (likely version conflicts) 22:14:56 librados.so.2()(64bit) 22:14:56 Could not install dependencies What’s the next step 1: Talked with Qi mingyuan, plan to compare every ceph 13.2.0 depes package with mirror’s package. 2: Deploy one starlingx cluster, check package and env. Help needed If we can get stx-tools design, implement overview or building flow, it can help us speed up the debug/upgrading. Thanks! - Vivian SSG OTC NST Storage Tel: (8621)61167437 -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Wed Sep 5 14:30:07 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 5 Sep 2018 14:30:07 +0000 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: Message-ID: > On Mon, Sep 3, 2018 at 5:58 PM, Arce Moreno, Abraham > wrote: > > stx-metal > > [Doc] Building docs following Docs Contrib Guide > > https://review.openstack.org/#/c/590094/ > > You can add the docs build job that will actually test the configuration you > are setting up. > https://review.openstack.org/#/c/599041/3/.zuul.yaml should be all you > need, then the results of the job is lined in the Gerrit review so you can see it > before it is merged and published. This is really useful since we don't have > the publising part set up yet. What is the difference between .zuul.yaml in each repo and project.yaml from openstack-infra/project-config [0] ? > > [Doc] Release Notes Management > > https://review.openstack.org/#/c/599454/ > > I've pushed up https://review.openstack.org/599831 to run the docs and > relnotes build jobs to see what they looks like. > > [Doc] OpenStack API Reference Guide > > https://review.openstack.org/#/c/590097/ > > I don't have any first-hand experience with this and will come back to it...I > imagine it will be very similar to the above job-wise. Based on OpenStack API documentation [1]: "Add the api-ref-jobs template..." Working now in taking your changes into stx-ha including api-ref-jobs. [0] https://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul.d/projects.yaml [1] https://docs.openstack.org/doc-contrib-guide/api-guides.html From yong.hu at intel.com Wed Sep 5 14:53:16 2018 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 5 Sep 2018 14:53:16 +0000 Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status In-Reply-To: References: <371DF9A763E9F44F924F4A821FC070264C4993FF@SHSMSX104.ccr.corp.intel.com> Message-ID: <611E5212-893A-4654-880F-60BBA69F2888@intel.com> From this file: https://github.com/ceph/ceph/blob/mimic/ceph.spec.in We can see “%package -n librados2” and “%package -n librados-devel” still existing, so technically related RPMs will be built out together with Ceph RPMs. Then next step is to figure out anything, which librados2 depends on, is missing. From: "McKenna, Jason" Date: Wednesday, 5 September 2018 at 10:22 PM To: "Zhu, Vivian" , "starlingx-discuss at lists.starlingx.io" Cc: "Shang, Dehao" Subject: Re: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status , Hi Vivian, librados.so.2()(64bit) should be provided by the librados2 package which is built as part of ceph 10.x.x. I suspect this package did not get built in your environment (which is why build-iso fails to find it) because the updated version of ceph does not build the package. There are a few possibilities here: * Maybe librados2 is an optional output of the ceph package. You’d have to “turn on” this functionality * Maybe librados2 has been renamed or upversioned. You’d have to update the spec file for whatever is requiring librados.so.2()(64bit) to use the new name/version of the library * Maybe librados2 is no longer required. You’d have to update the spec file for whatever is requiring librados.so.2()(64bit) to remove the requirement You can check what package has the “librados.so.2()(64bit)” requirement by looking at the $MY_WORKSPACE/export/deps_detail.txt file Hope this helps! -Jason From: Zhu, Vivian Sent: September 5, 2018 9:53 AM To: starlingx-discuss at lists.starlingx.io Cc: Shang, Dehao Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Hi Anyone who is familiar with stx-tools or build flow, Our storage team (Dehao etc.) have worked on Ceph upgrading on starlingX project and we are still staggering to resolve issues one-by-one, now we fail to build ISO, the log points to “These RPMS had problems (likely version conflicts) “. Here is our build steps and according action we did. We are looking for help to solve it, if anyone who can give some hints to narrow down/address issue or point out the wrong step here. That’s really helpful to unblock Ceph upgrade to catch up Sep.26 code freeze. Build flow step 1: download_mirror ---> container 1 | step 2: manually check *_miss_*.txt and *_fails_*.txt file, then download miss and fails package | step 3: to ensure that all package listed by rpms_from_3rd_parties.list and rpms_from_centos_repo.lst are downloaded | step 4: create work space : mkdir -p $HOME/starlingx/mirror/Centos | step 5: copy mirror to workspace which can be used by container 2 | step 6: edit Dockerfile, create image, then run container, and so on. | step 7 : clone all source using "repo sync" → container 2 | step 8: at git folder, using ceph 13.2.0 to replace ceph 10.2.6 | step 9: using ceph tools "make-srpm.sh" to create 13.2.0 ceph.spec file. | step 10 : modify new ceph.spec file according to stx-ceph's ceph.spec file | step 11: copy stx-ceph's wrs folder to ceph 13.2.0 | step 12: build-pkgs --serial | step 13: build_iso <-----------------------------fails !!! | step 14 : success building What we had done 1:can build starlingx image 2:ceph 13.2.0’s ceph.spec file can works. 3: build-pkgs can build all package What part we are gating when building ISO, deps can’t be resolved. we tried steps but failed. Stalingx log give one error conclusion as following: 22:14:55 Debug: Packages still unresolved: 22:14:55 22:14:56 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 22:14:56 These RPMS had problems (likely version conflicts) 22:14:56 librados.so.2()(64bit) 22:14:56 Could not install dependencies What’s the next step 1: Talked with Qi mingyuan, plan to compare every ceph 13.2.0 depes package with mirror’s package. 2: Deploy one starlingx cluster, check package and env. Help needed If we can get stx-tools design, implement overview or building flow, it can help us speed up the debug/upgrading. Thanks! - Vivian SSG OTC NST Storage Tel: (8621)61167437 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Sep 5 14:59:47 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 5 Sep 2018 14:59:47 +0000 Subject: [Starlingx-discuss] Notes from our weekly call today Message-ID: <9A85D2917C58154C960D95352B22818BAB587CFB@fmsmsx115.amr.corp.intel.com> Agenda and notes for the 9/5 meeting * Release readiness / Bug status * Update from DEV sub-project teams on release deliverables o We have 55 items active in SB for the release and 9 bugs in LP o stx-gui - merge for stx-gui packaging is in progress, one gating bug, fix in progress. Then we can flip the switch and start building the new RPM. On track. o stx-config - No concerns, on track. memcached integration in progress. o disrto-non-openstack - Saul has completed his first pass analysis of patches, categorizing them into buckets (init, config, etc..). See master tracking spreadsheet. CentOS 7.5 update in progress, 2 packages have runtime issues. One package is not going to be updated due to known issues in the upstream package. Will update 255 packages this week and create a new build for Testing. On track. o distro-openstack - changes in flight for keystone and ceilometer. Backup and restore work in progress. Gnocchi work is done but story not closed. o Docs - Work in progress on API document conversion and on release notes infrastructure. Every dev will need to tag their changes for reno. Automated rel notes are per git repo. Docs team to document / publish process to the team. We have deliverables not strictly tied to the code freeze e.g. wiki updates. On track. o Build team - no issues / risk for the release, On track. Cesar to invalidate a few legacy stories. o Security - status of fuzz testing - Ken to remove tag from story. Team to work with Jeremy to build process for how to handle Security issues privately. Security team to review any open CVE issues in SB - already addressed, just need to close the Story. o Networking - One feature - generalize networking config - on track. Two OVS enhancements in flight o Zuul team on track o Python2 team has reduced 4 tickets to 2. o Devstack - nothing planned for October. * Test Team Update ? Current frequency on sanity runs on master - sanity is triggered after each daily build ? infrastructure for October release testing ? baremetal testing update o Thoughts on Bug Triage process o How do we host log files for bug analysis? What is the file size limit for posting files for Launchpad? 593 kbytes. paste.openstack.org can be used to post log snippets. Collect cmd can be used but the files are 10-200MB in size. Need to discuss with OpenStack Infra team... o How to deal with critical/blocking bugs -- email to the mailing list? ...so that someone can jump on it o Current build hasn't worked for 5+ days. Test team to raise red flag and ask for triage help. WR has simplex running and duplex is running, both on bare metal. Devs are using VB and report no problems. Intel is using libvirt/qemu which WR doesn't cover. * PTG agenda - please review https://etherpad.openstack.org/p/stx-PTG-agenda and update if you have topics for the PTG * Team roundtable - issues? blockers? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jason.McKenna at windriver.com Wed Sep 5 15:12:55 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Wed, 5 Sep 2018 15:12:55 +0000 Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status In-Reply-To: <611E5212-893A-4654-880F-60BBA69F2888@intel.com> References: <371DF9A763E9F44F924F4A821FC070264C4993FF@SHSMSX104.ccr.corp.intel.com> <611E5212-893A-4654-880F-60BBA69F2888@intel.com> Message-ID: It may be an updated filename in the librados2 package then. Note that whatever is requiring the package is specifying the shared library file name and architecture, rather than a package name (librados.so.2()(64bit)) Step 1: check that librados2 package actually is being built – you should see it in $MY_WORKSPACE/std/rpmbuild/RPMS/ after the new ceph package is built. Step 2: check what the package provides (rpm -qp [path_to_package].rpm -l) Look for the .so -Jason From: Hu, Yong Sent: September 5, 2018 10:53 AM To: McKenna, Jason ; Zhu, Vivian ; starlingx-discuss at lists.starlingx.io Cc: Shang, Dehao Subject: Re: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status From this file: https://github.com/ceph/ceph/blob/mimic/ceph.spec.in We can see “%package -n librados2” and “%package -n librados-devel” still existing, so technically related RPMs will be built out together with Ceph RPMs. Then next step is to figure out anything, which librados2 depends on, is missing. From: "McKenna, Jason" > Date: Wednesday, 5 September 2018 at 10:22 PM To: "Zhu, Vivian" >, "starlingx-discuss at lists.starlingx.io" > Cc: "Shang, Dehao" > Subject: Re: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status , Hi Vivian, librados.so.2()(64bit) should be provided by the librados2 package which is built as part of ceph 10.x.x. I suspect this package did not get built in your environment (which is why build-iso fails to find it) because the updated version of ceph does not build the package. There are a few possibilities here: - Maybe librados2 is an optional output of the ceph package. You’d have to “turn on” this functionality - Maybe librados2 has been renamed or upversioned. You’d have to update the spec file for whatever is requiring librados.so.2()(64bit) to use the new name/version of the library - Maybe librados2 is no longer required. You’d have to update the spec file for whatever is requiring librados.so.2()(64bit) to remove the requirement You can check what package has the “librados.so.2()(64bit)” requirement by looking at the $MY_WORKSPACE/export/deps_detail.txt file Hope this helps! -Jason From: Zhu, Vivian > Sent: September 5, 2018 9:53 AM To: starlingx-discuss at lists.starlingx.io Cc: Shang, Dehao > Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Hi Anyone who is familiar with stx-tools or build flow, Our storage team (Dehao etc.) have worked on Ceph upgrading on starlingX project and we are still staggering to resolve issues one-by-one, now we fail to build ISO, the log points to “These RPMS had problems (likely version conflicts) “. Here is our build steps and according action we did. We are looking for help to solve it, if anyone who can give some hints to narrow down/address issue or point out the wrong step here. That’s really helpful to unblock Ceph upgrade to catch up Sep.26 code freeze. Build flow step 1: download_mirror ---> container 1 | step 2: manually check *_miss_*.txt and *_fails_*.txt file, then download miss and fails package | step 3: to ensure that all package listed by rpms_from_3rd_parties.list and rpms_from_centos_repo.lst are downloaded | step 4: create work space : mkdir -p $HOME/starlingx/mirror/Centos | step 5: copy mirror to workspace which can be used by container 2 | step 6: edit Dockerfile, create image, then run container, and so on. | step 7 : clone all source using "repo sync" → container 2 | step 8: at git folder, using ceph 13.2.0 to replace ceph 10.2.6 | step 9: using ceph tools "make-srpm.sh" to create 13.2.0 ceph.spec file. | step 10 : modify new ceph.spec file according to stx-ceph's ceph.spec file | step 11: copy stx-ceph's wrs folder to ceph 13.2.0 | step 12: build-pkgs --serial | step 13: build_iso <-----------------------------fails !!! | step 14 : success building What we had done 1:can build starlingx image 2:ceph 13.2.0’s ceph.spec file can works. 3: build-pkgs can build all package What part we are gating when building ISO, deps can’t be resolved. we tried steps but failed. Stalingx log give one error conclusion as following: 22:14:55 Debug: Packages still unresolved: 22:14:55 22:14:56 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 22:14:56 These RPMS had problems (likely version conflicts) 22:14:56 librados.so.2()(64bit) 22:14:56 Could not install dependencies What’s the next step 1: Talked with Qi mingyuan, plan to compare every ceph 13.2.0 depes package with mirror’s package. 2: Deploy one starlingx cluster, check package and env. Help needed If we can get stx-tools design, implement overview or building flow, it can help us speed up the debug/upgrading. Thanks! - Vivian SSG OTC NST Storage Tel: (8621)61167437 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Wed Sep 5 16:32:05 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 5 Sep 2018 11:32:05 -0500 Subject: [Starlingx-discuss] [Build] unified build command suggestions In-Reply-To: References: Message-ID: I've spent a few cycles thinking about CLI construction (syntax-wise) and have come to believe that not all command forms are created equal and that rigorous consistency is a big feature. I think using something that looks like an option as the command can be confusing to users, it is better to use a form of object-action with options or positional arguments (the fewer the better). If you've used OpenStackClient you will know exactly what I am talking about. Also, as an aside, I would really like to suggest not using 'stx' as the command for build-related things and saving that for user/cloud consumer things. On Wed, Sep 5, 2018 at 8:31 AM, McKenna, Jason wrote: > I’ve been thinking about the proposal for the unified build command as > discussed in the last build team meeting. “stx --build-iso” or “stx > --create-iso” was suggested as command for building all targets – source > rpms, binary rpms, and the final ISO. We should probably change that > command name to “stx --build-all” or something similar. This would meet the > immediate request of providing a single command to wrap around the existing > steps, and would allow us to grow the tool’s functionality without tying us > to the concept of “an ISO == a build”. As a bonus, it allows us to improve > the granularity the build commands while maintaining a consistent command > naming convention. A potential first cut of commands could be: In the below examples I am assuming object - action ordering, which turned out to be easier to set up bash completion for than action - object ordering in OSC. (Personally I prefer the latter) > # Download items specified in lst files (replaces download_mirror.sh) > stx --mirror-download stxb mirror download > # Places downloaded items in the specified mirror path > stx --mirror-populate stxb mirror populate [-mirror ] > # Do all mirror steps > stx --mirror-all stxb mirror create [-mirror ] (or init or update or whatever action name) > # sets up a build environment with artifacts from the specified mirror path > (replaces generate-cgcs-centos-repo.sh and populate_downloads.sh) > stx --build-env stxb environment create [-mirror ] > # builds specified package or all packages (replaces build-pkgs) > stx --build-pkgs [pkg_name] stxb package build [ ...] > # Produces an ISO from current build (replaces build-iso) > stx --build-iso stxb iso build > # Runs previous steps (I’m not sure if running --build-env during build-all > is a good idea, but perhaps we could skip the --build-env if no mirror_path > is specified) > stx --build-all [mirror_path] stxb all build [-mirror ] dt -- Dean Troyer dtroyer at gmail.com From dtroyer at gmail.com Wed Sep 5 16:38:38 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 5 Sep 2018 11:38:38 -0500 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: Message-ID: On Wed, Sep 5, 2018 at 9:30 AM, Arce Moreno, Abraham wrote: > What is the difference between .zuul.yaml in each repo and project.yaml from > openstack-infra/project-config [0] ? Primarily that project-config is shared by all of OpenStack Infra and centrally managed, while .zuul.yaml is in the project repo and can be easily maintained within the project team directly. >> > [Doc] Release Notes Management >> > https://review.openstack.org/#/c/599454/ >> >> I've pushed up https://review.openstack.org/599831 to run the docs and >> relnotes build jobs to see what they looks like. >> > [Doc] OpenStack API Reference Guide >> > https://review.openstack.org/#/c/590097/ >> >> I don't have any first-hand experience with this and will come back to it...I >> imagine it will be very similar to the above job-wise. > > Based on OpenStack API documentation [1]: > "Add the api-ref-jobs template..." > > Working now in taking your changes into stx-ha including api-ref-jobs. Like I suggested earlier, let's get one set of these worked out first then fan out to the repos as required. It will kepp all of the discussion in one place and avoid re-working if/when things change before we are happy with the first one. Also, be careful about blindly adopting OpenStack job templates, some of them include the publishing jobs that we are unable to use, we need to define our own, which has started but none are merged yet. This is why I've called build-openstack-releasenotes directly in [0] rather than the upstream template, as I did with build-openstack-sphinx-docs-python3, which does not include any publish jobs. dt [0] https://review.openstack.org/#/c/599831/5/.zuul.yaml -- Dean Troyer dtroyer at gmail.com From dtroyer at gmail.com Wed Sep 5 16:57:50 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 5 Sep 2018 11:57:50 -0500 Subject: [Starlingx-discuss] python-eventlet upgrade issue In-Reply-To: <9700A18779F35F49AF027300A49E7C7655355AEF@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655355AEF@SHSMSX101.ccr.corp.intel.com> Message-ID: On Wed, Aug 29, 2018 at 9:51 PM, Lin, Shuicheng wrote: > Anyone familiar with python-eventlet? I meet a problem when upgrade > python-eventlet from “0.18.4-2” to “0.20.1-2”, when do CentOS7.5 upgrade. [...] > The issue is that, after upgrade to 0.20.1-2 version, these functions don’t > work as expected. Looking at upstream OpenStack requirements for Pike, eventlet is listed in global-requirements (the minimum required version) as eventlet!=0.18.3,>=0.18.2,!=0.20.1,<0.21.0 # MIT and in upper-contraints.txt (what is actually tests in the gate) as eventlet===0.20.0 In order to be co-installable with OpenStack we must maintain similar versions for the STX services. FWIW, rocky's versions of the above are similar: eventlet!=0.18.3,!=0.20.1,!=0.21.0,!=0.23.0 and eventlet===0.20.0 Also note that OpenStack is preparing[0] to raise the u-c version of eventlet to 0.24.1, which I believe is current master. We should be preparing 0.20.0 for packaging. Even though OpenStack master is mostly ready for 0.24.1 I doubt that Pike is nor will it be made so... Background OpenStack maintains both minimum and maximum version requirements for Python dependencies that must be shared by all OpenStack projects. This is to maintain co-installability since Python can not install multiple versions of a package without resorting to techniques such as virtual environments. There are CI jobs for checking these, and projects are free to be stricter in their reqirements.txt files as long as they fit within the globally defined min/max. StarlingX services (flock) need to be compatible with Pike, although it is not currently enforced. dt [0] http://lists.openstack.org/pipermail/openstack-dev/2018-August/133728.html -- Dean Troyer dtroyer at gmail.com From sgw at linux.intel.com Wed Sep 5 17:16:46 2018 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 5 Sep 2018 10:16:46 -0700 Subject: [Starlingx-discuss] [Build] unified build command suggestions In-Reply-To: References: Message-ID: <5e4d9d83-93f8-c04f-47b5-46b795d4287a@linux.intel.com> On 09/05/2018 09:32 AM, Dean Troyer wrote: > I've spent a few cycles thinking about CLI construction (syntax-wise) > and have come to believe that not all command forms are created equal > and that rigorous consistency is a big feature. > > I think using something that looks like an option as the command can > be confusing to users, it is better to use a form of object-action > with options or positional arguments (the fewer the better). If > you've used OpenStackClient you will know exactly what I am talking > about. > I agree with this, similar to what git and some other tools do also, I like the examples you provided below. Sau! > Also, as an aside, I would really like to suggest not using 'stx' as > the command for build-related things and saving that for user/cloud > consumer things. > > On Wed, Sep 5, 2018 at 8:31 AM, McKenna, Jason > wrote: >> I’ve been thinking about the proposal for the unified build command as >> discussed in the last build team meeting. “stx --build-iso” or “stx >> --create-iso” was suggested as command for building all targets – source >> rpms, binary rpms, and the final ISO. We should probably change that >> command name to “stx --build-all” or something similar. This would meet the >> immediate request of providing a single command to wrap around the existing >> steps, and would allow us to grow the tool’s functionality without tying us >> to the concept of “an ISO == a build”. As a bonus, it allows us to improve >> the granularity the build commands while maintaining a consistent command >> naming convention. A potential first cut of commands could be: > > In the below examples I am assuming object - action ordering, which > turned out to be easier to set up bash completion for than action - > object ordering in OSC. (Personally I prefer the latter) > >> # Download items specified in lst files (replaces download_mirror.sh) >> stx --mirror-download > > stxb mirror download > >> # Places downloaded items in the specified mirror path >> stx --mirror-populate > > stxb mirror populate [-mirror ] > >> # Do all mirror steps >> stx --mirror-all > > stxb mirror create [-mirror ] > (or init or update or whatever action name) > >> # sets up a build environment with artifacts from the specified mirror path >> (replaces generate-cgcs-centos-repo.sh and populate_downloads.sh) >> stx --build-env > > stxb environment create [-mirror ] > >> # builds specified package or all packages (replaces build-pkgs) >> stx --build-pkgs [pkg_name] > > stxb package build [ ...] > >> # Produces an ISO from current build (replaces build-iso) >> stx --build-iso > > stxb iso build > I think it would be better if was more like stxb build iso stxb build all I know this is different than the mirror actions above, but the all does not ma >> # Runs previous steps (I’m not sure if running --build-env during build-all >> is a good idea, but perhaps we could skip the --build-env if no mirror_path >> is specified) >> stx --build-all [mirror_path] > > stxb all build [-mirror ] > I think it would be better if was more like stxb build package stxb build iso stxb build all I know this is different than the mirror actions above, but the "all" does not make sense to me in this usage. Sau! > > dt > From ada.cabrales at intel.com Wed Sep 5 17:50:20 2018 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Wed, 5 Sep 2018 17:50:20 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> Hello all, As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. [0] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary Regards Ada From dtroyer at gmail.com Wed Sep 5 17:53:32 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 5 Sep 2018 12:53:32 -0500 Subject: [Starlingx-discuss] [Build] unified build command suggestions In-Reply-To: <5e4d9d83-93f8-c04f-47b5-46b795d4287a@linux.intel.com> References: <5e4d9d83-93f8-c04f-47b5-46b795d4287a@linux.intel.com> Message-ID: On Wed, Sep 5, 2018 at 12:16 PM, Saul Wold wrote: > I agree with this, similar to what git and some other tools do also, I like > the examples you provided below. Sooooo..... git should mostly not be used as an example UI for most purposes, it is a bit of a mess :) git remote add ... (ok, but...) git branch -m ... (not branch move? branch is sometimes an object and sometimes a verb depending on the options!!) > I think it would be better if was more like > > stxb build iso > stxb build all > > I know this is different than the mirror actions above, but the "all" does > not make sense to me in this usage. This is the what-comes-first question, the object or the action? VMS is still leaking from my brain in that I also prefer the action (verb) to be first. OSC reversed itself 5 years ago because of the bash-completion issue, we use cliff to implement the command parser (built on top of argparse) and doing verb-first and bash completion turned out to be a mess. That is an implementation driving design, which is not always great, but was acceptable to the team at the time. Which ever order is settled on, PLEASE make all commands the same. The UX studies we did with OSC always showed this consistency to be very important to both new and experienced users. dt -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Wed Sep 5 17:56:06 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 5 Sep 2018 17:56:06 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> Should the bugs coming out of this be tagged/fixed for the October release? Related bugs: https://bugs.launchpad.net/starlingx/+bug/1790213 https://bugs.launchpad.net/starlingx/+bug/1790514 https://bugs.launchpad.net/starlingx/+bug/1790716 https://bugs.launchpad.net/starlingx/+bug/1790718 -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Wednesday, September 5, 2018 10:50 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hello all, As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. [0] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary Regards Ada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Jason.McKenna at windriver.com Wed Sep 5 18:02:06 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Wed, 5 Sep 2018 18:02:06 +0000 Subject: [Starlingx-discuss] [Build] unified build command suggestions In-Reply-To: References: <5e4d9d83-93f8-c04f-47b5-46b795d4287a@linux.intel.com> Message-ID: > -----Original Message----- > From: Dean Troyer > Sent: September 5, 2018 1:54 PM > To: Saul Wold > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [Build] unified build command suggestions > > On Wed, Sep 5, 2018 at 12:16 PM, Saul Wold wrote: > > I agree with this, similar to what git and some other tools do also, I > > like the examples you provided below. > > Sooooo..... git should mostly not be used as an example UI for most > purposes, it is a bit of a mess :) > > git remote add ... (ok, but...) > git branch -m ... (not branch move? branch is sometimes an > object and sometimes a verb depending on the options!!) > > > I think it would be better if was more like > > > > stxb build iso > > stxb build all > > > > I know this is different than the mirror actions above, but the "all" > > does not make sense to me in this usage. > > This is the what-comes-first question, the object or the action? VMS is still > leaking from my brain in that I also prefer the action (verb) to be first. OSC > reversed itself 5 years ago because of the bash-completion issue, we use cliff > to implement the command parser (built on top of argparse) and doing verb- > first and bash completion turned out to be a mess. That is an > implementation driving design, which is not always great, but was acceptable > to the team at the time. > > Which ever order is settled on, PLEASE make all commands the same. > The UX studies we did with OSC always showed this consistency to be very > important to both new and experienced users. > +1 on consistency :) I think we need discussion around what we're really trying to accomplish. Going back to Cesar's initial proposal, the problem he wanted solved was that his team felt that there were too many commands required to produce an ISO after you've downloaded the mirrors (generate-cgcs-centos-repo.sh, build-pkgs, build-iso) and wanted to wrap those in a single command. Please correct me if I've misstated the problem, Cesar. Furthermore, I think you were looking for a command which did the steps that a developer would execute and not do the steps that a developer would not (downloading the mirror, is intended to be done at a per-site level, not a per-developer level, and would not necessarily be included in the single-command). Finally, the command was intended to be expandable and adaptable in the future (again, please correct me if I've misstated anything). Other than the "meet all conceivable future needs" requirement, I don't see much that couldn't be done with something like a Makefile: make mirror make environment make build make iso especially if you have the "iso" target depend on the "build" target which depends on the "environment" target, etc, then the whole process boils down to one "make iso" command for a developer (2 commands if they have to download the mirror themselves). Note that I'm not proposing "make" as a solution, I understand the concern that make wouldn't meet our needs in the future, and make can be less than pretty. I'm more engaging in the thought exercise of "what problem are we really trying to solve and has anyone solved it in the past" If we're wrapping or re-writing the build commands to make it simpler/easier for a developer, we should define proper use cases and make sure we're solving the right problems. To go off on a tangent, I find the illegible output of the build commands to be much more a stumbling block than the fact that I have to execute 3 commands rather than 1 to produce a build. > dt > > -- > > Dean Troyer > dtroyer at gmail.com > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From elio.martinez.monroy at intel.com Wed Sep 5 18:22:53 2018 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Wed, 5 Sep 2018 18:22:53 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> My opinion below -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, September 5, 2018 12:56 PM To: Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Should the bugs coming out of this be tagged/fixed for the October release? Related bugs: https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all instances need at least one compute for multimode https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Wednesday, September 5, 2018 10:50 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hello all, As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. [0] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary Regards Ada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Wed Sep 5 18:28:23 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 5 Sep 2018 18:28:23 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB25C493@ALA-MBD.corp.ad.wrs.com> Certainly the last one. It is dependent on the completion of stx-gui which is gating. The other 3 have questions/actions. I think we need that information first before deciding Brent -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, September 5, 2018 1:56 PM To: Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Should the bugs coming out of this be tagged/fixed for the October release? Related bugs: https://bugs.launchpad.net/starlingx/+bug/1790213 https://bugs.launchpad.net/starlingx/+bug/1790514 https://bugs.launchpad.net/starlingx/+bug/1790716 https://bugs.launchpad.net/starlingx/+bug/1790718 -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Wednesday, September 5, 2018 10:50 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hello all, As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. [0] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary Regards Ada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cesar.lara at intel.com Wed Sep 5 20:42:19 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 5 Sep 2018 20:42:19 +0000 Subject: [Starlingx-discuss] [Build] unified build command suggestions In-Reply-To: References: Message-ID: <0B566C62EC792145B40E29EFEBF1AB47104FEAC3@fmsmsx104.amr.corp.intel.com> This is a great suggestion, we'll see how to integrate this to the build command Regards Cesar Lara From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Wednesday, September 5, 2018 8:31 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Build] unified build command suggestions Hi Cesar and build team, I've been thinking about the proposal for the unified build command as discussed in the last build team meeting. "stx --build-iso" or "stx --create-iso" was suggested as command for building all targets - source rpms, binary rpms, and the final ISO. We should probably change that command name to "stx --build-all" or something similar. This would meet the immediate request of providing a single command to wrap around the existing steps, and would allow us to grow the tool's functionality without tying us to the concept of "an ISO == a build". As a bonus, it allows us to improve the granularity the build commands while maintaining a consistent command naming convention. A potential first cut of commands could be: # Download items specified in lst files (replaces download_mirror.sh) stx --mirror-download # Places downloaded items in the specified mirror path stx --mirror-populate # Do all mirror steps stx --mirror-all # sets up a build environment with artifacts from the specified mirror path (replaces generate-cgcs-centos-repo.sh and populate_downloads.sh) stx --build-env # builds specified package or all packages (replaces build-pkgs) stx --build-pkgs [pkg_name] # Produces an ISO from current build (replaces build-iso) stx --build-iso # Runs previous steps (I'm not sure if running --build-env during build-all is a good idea, but perhaps we could skip the --build-env if no mirror_path is specified) stx --build-all [mirror_path] Future commands like --build-patch or --sign-pkgs or --project-integrate or wherever this grows, could be added as more advanced use cases are fleshed out. Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed Sep 5 21:20:35 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 5 Sep 2018 16:20:35 -0500 Subject: [Starlingx-discuss] PTG information and agenda Message-ID: <945D239A-8E30-47C2-945D-BECAA6CBE33C@gmail.com> Hi, The next PTG (https://www.openstack.org/ptg) is just around the corner staring next Monday (Sept 10) and ends on Friday (Sept 14). As most of you know this is a developer focused event to provide space and time for face to face technical discussions relevant to the work the project teams are doing and for cross-project collaboration. To emphasize on collaboration you will find representation from all the projects under the OpenStack Foundation umbrella and the event is also co-located with the OpenStack Ops Meetup. StarlingX is meeting on Wednesday in the Winter Park room (https://web14.openstack.org/assets/ptg/Denver-map.pdf) from 9am MDT. You can find our agenda on this etherpad: https://etherpad.openstack.org/p/stx-PTG-agenda As mentioned earlier we will do our best to provide an option to participate remotely. I will post a Zoom link and dial-in info on the top of the etherpad above before the sessions start on Wednesday. I will also distribute the information here on the mailing list. As the time slots on the agenda are estimates we are using a dedicated web page (http://ptg.openstack.org/ptg.html) to track the current and next topics and also a dedicated IRC channel (#openstack-ptg) for communication and news sharing. You can find the links to all PTG related resources here: http://ptg.openstack.org As one of the related groups the Edge Computing Group is meeting on Tuesday in Ballroom A starting at 9am MDT. You can find the agenda on this etherpad: https://etherpad.openstack.org/p/EdgeComputingGroupPTG4 Note the joint sessions with Glance, Keystone and Nova that are relevant to StarlingX and the session on collaboration between StarlingX and the Edge group throughout the day. Please let me know if you have any questions about the event or the sessions. Thanks and Best Regards, Ildikó From Ghada.Khalil at windriver.com Wed Sep 5 21:38:48 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 5 Sep 2018 21:38:48 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> Please see inline. There are notes in all the launchpads as well. I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. -----Original Message----- From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Wednesday, September 05, 2018 2:23 PM To: Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted My opinion below -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, September 5, 2018 12:56 PM To: Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Should the bugs coming out of this be tagged/fixed for the October release? Related bugs: https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all instances need at least one compute for multimode [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. The test team points to internal instructions which we have no access to. The supported install recipes need to be on the wiki. I think it is an invalid bug https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Wednesday, September 5, 2018 10:50 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hello all, As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. [0] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary Regards Ada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From mario.alfredo.c.arevalo at intel.com Wed Sep 5 22:12:49 2018 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Wed, 5 Sep 2018 22:12:49 +0000 Subject: [Starlingx-discuss] [Build] unified build command suggestions In-Reply-To: References: <5e4d9d83-93f8-c04f-47b5-46b795d4287a@linux.intel.com> , Message-ID: <6594B51DBE477C48AAE23675314E6C465993BF85@fmsmsx107.amr.corp.intel.com> Hi team, Related to the tool name, a good point was mentioned, StarlingX is the core project, “stx” should be reserved for the core things. The building tool will be called “stx-build-tool” or “stx-bt” and it is good to keep consistency with the current stuff. And about the different options/subcommands proposed by Jason, they can exist, the idea is to cover both sides, develop and user sides. It is possible to have users that maybe would not like to involve in the development process and they just want to get ISO image, this is a valid point and our build tool should allow that way, the next proposed commands should be enough for a “Quick user guide”. $ stx-build-tool mirror create $ stx-build-tool iso build By the other hand the developers need more granularity about the processes, then the subcommands proposed by Jason are welcome. The implementation of this script will be modular, then it will be easy to implement relevant and needed subcommands in a future just calling the required functions. An related to the comment about Makefile rules, I think it could be better to use shell commands directly instead to wrap them in a Makefile, due to it is easier to customized values on command line. Using Makefiles it is possible to do it too, but I think it is a little less friendly. Best Regards. Mario. ________________________________________ From: McKenna, Jason [Jason.McKenna at windriver.com] Sent: Wednesday, September 05, 2018 11:02 AM To: Dean Troyer; Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Build] unified build command suggestions > -----Original Message----- > From: Dean Troyer > Sent: September 5, 2018 1:54 PM > To: Saul Wold > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [Build] unified build command suggestions > > On Wed, Sep 5, 2018 at 12:16 PM, Saul Wold wrote: > > I agree with this, similar to what git and some other tools do also, I > > like the examples you provided below. > > Sooooo..... git should mostly not be used as an example UI for most > purposes, it is a bit of a mess :) > > git remote add ... (ok, but...) > git branch -m ... (not branch move? branch is sometimes an > object and sometimes a verb depending on the options!!) > > > I think it would be better if was more like > > > > stxb build iso > > stxb build all > > > > I know this is different than the mirror actions above, but the "all" > > does not make sense to me in this usage. > > This is the what-comes-first question, the object or the action? VMS is still > leaking from my brain in that I also prefer the action (verb) to be first. OSC > reversed itself 5 years ago because of the bash-completion issue, we use cliff > to implement the command parser (built on top of argparse) and doing verb- > first and bash completion turned out to be a mess. That is an > implementation driving design, which is not always great, but was acceptable > to the team at the time. > > Which ever order is settled on, PLEASE make all commands the same. > The UX studies we did with OSC always showed this consistency to be very > important to both new and experienced users. > +1 on consistency :) I think we need discussion around what we're really trying to accomplish. Going back to Cesar's initial proposal, the problem he wanted solved was that his team felt that there were too many commands required to produce an ISO after you've downloaded the mirrors (generate-cgcs-centos-repo.sh, build-pkgs, build-iso) and wanted to wrap those in a single command. Please correct me if I've misstated the problem, Cesar. Furthermore, I think you were looking for a command which did the steps that a developer would execute and not do the steps that a developer would not (downloading the mirror, is intended to be done at a per-site level, not a per-developer level, and would not necessarily be included in the single-command). Finally, the command was intended to be expandable and adaptable in the future (again, please correct me if I've misstated anything). Other than the "meet all conceivable future needs" requirement, I don't see much that couldn't be done with something like a Makefile: make mirror make environment make build make iso especially if you have the "iso" target depend on the "build" target which depends on the "environment" target, etc, then the whole process boils down to one "make iso" command for a developer (2 commands if they have to download the mirror themselves). Note that I'm not proposing "make" as a solution, I understand the concern that make wouldn't meet our needs in the future, and make can be less than pretty. I'm more engaging in the thought exercise of "what problem are we really trying to solve and has anyone solved it in the past" If we're wrapping or re-writing the build commands to make it simpler/easier for a developer, we should define proper use cases and make sure we're solving the right problems. To go off on a tangent, I find the illegible output of the build commands to be much more a stumbling block than the fact that I have to execute 3 commands rather than 1 to produce a build. > dt > > -- > > Dean Troyer > dtroyer at gmail.com > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Wed Sep 5 22:29:43 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 5 Sep 2018 22:29:43 +0000 Subject: [Starlingx-discuss] [Build] unified build command suggestions In-Reply-To: <6594B51DBE477C48AAE23675314E6C465993BF85@fmsmsx107.amr.corp.intel.com> References: <5e4d9d83-93f8-c04f-47b5-46b795d4287a@linux.intel.com> , <6594B51DBE477C48AAE23675314E6C465993BF85@fmsmsx107.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB58831F@fmsmsx115.amr.corp.intel.com> My $0.02, for what it's worth. The name stx-build-tool is too long. +1 to stxb from a previous note in this thread. brucej -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Wednesday, September 5, 2018 3:13 PM To: McKenna, Jason ; Dean Troyer ; Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Build] unified build command suggestions Hi team, Related to the tool name, a good point was mentioned, StarlingX is the core project, “stx” should be reserved for the core things. The building tool will be called “stx-build-tool” or “stx-bt” and it is good to keep consistency with the current stuff. And about the different options/subcommands proposed by Jason, they can exist, the idea is to cover both sides, develop and user sides. It is possible to have users that maybe would not like to involve in the development process and they just want to get ISO image, this is a valid point and our build tool should allow that way, the next proposed commands should be enough for a “Quick user guide”. $ stx-build-tool mirror create $ stx-build-tool iso build By the other hand the developers need more granularity about the processes, then the subcommands proposed by Jason are welcome. The implementation of this script will be modular, then it will be easy to implement relevant and needed subcommands in a future just calling the required functions. An related to the comment about Makefile rules, I think it could be better to use shell commands directly instead to wrap them in a Makefile, due to it is easier to customized values on command line. Using Makefiles it is possible to do it too, but I think it is a little less friendly. Best Regards. Mario. ________________________________________ From: McKenna, Jason [Jason.McKenna at windriver.com] Sent: Wednesday, September 05, 2018 11:02 AM To: Dean Troyer; Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Build] unified build command suggestions > -----Original Message----- > From: Dean Troyer > Sent: September 5, 2018 1:54 PM > To: Saul Wold > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [Build] unified build command > suggestions > > On Wed, Sep 5, 2018 at 12:16 PM, Saul Wold wrote: > > I agree with this, similar to what git and some other tools do also, > > I like the examples you provided below. > > Sooooo..... git should mostly not be used as an example UI for most > purposes, it is a bit of a mess :) > > git remote add ... (ok, but...) > git branch -m ... (not branch move? branch is sometimes an > object and sometimes a verb depending on the options!!) > > > I think it would be better if was more like > > > > stxb build iso > > stxb build all > > > > I know this is different than the mirror actions above, but the "all" > > does not make sense to me in this usage. > > This is the what-comes-first question, the object or the action? VMS > is still leaking from my brain in that I also prefer the action (verb) > to be first. OSC reversed itself 5 years ago because of the > bash-completion issue, we use cliff to implement the command parser > (built on top of argparse) and doing verb- first and bash completion > turned out to be a mess. That is an implementation driving design, > which is not always great, but was acceptable to the team at the time. > > Which ever order is settled on, PLEASE make all commands the same. > The UX studies we did with OSC always showed this consistency to be > very important to both new and experienced users. > +1 on consistency :) I think we need discussion around what we're really trying to accomplish. Going back to Cesar's initial proposal, the problem he wanted solved was that his team felt that there were too many commands required to produce an ISO after you've downloaded the mirrors (generate-cgcs-centos-repo.sh, build-pkgs, build-iso) and wanted to wrap those in a single command. Please correct me if I've misstated the problem, Cesar. Furthermore, I think you were looking for a command which did the steps that a developer would execute and not do the steps that a developer would not (downloading the mirror, is intended to be done at a per-site level, not a per-developer level, and would not necessarily be included in the single-command). Finally, the command was intended to be expandable and adaptable in the future (again, please correct me if I've misstated anything). Other than the "meet all conceivable future needs" requirement, I don't see much that couldn't be done with something like a Makefile: make mirror make environment make build make iso especially if you have the "iso" target depend on the "build" target which depends on the "environment" target, etc, then the whole process boils down to one "make iso" command for a developer (2 commands if they have to download the mirror themselves). Note that I'm not proposing "make" as a solution, I understand the concern that make wouldn't meet our needs in the future, and make can be less than pretty. I'm more engaging in the thought exercise of "what problem are we really trying to solve and has anyone solved it in the past" If we're wrapping or re-writing the build commands to make it simpler/easier for a developer, we should define proper use cases and make sure we're solving the right problems. To go off on a tangent, I find the illegible output of the build commands to be much more a stumbling block than the fact that I have to execute 3 commands rather than 1 to produce a build. > dt > > -- > > Dean Troyer > dtroyer at gmail.com > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cesar.lara at intel.com Wed Sep 5 22:41:20 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 5 Sep 2018 22:41:20 +0000 Subject: [Starlingx-discuss] [Build] unified build command suggestions In-Reply-To: <9A85D2917C58154C960D95352B22818BAB58831F@fmsmsx115.amr.corp.intel.com> References: <5e4d9d83-93f8-c04f-47b5-46b795d4287a@linux.intel.com> , <6594B51DBE477C48AAE23675314E6C465993BF85@fmsmsx107.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB58831F@fmsmsx115.amr.corp.intel.com> Message-ID: <0B566C62EC792145B40E29EFEBF1AB47104FECD8@fmsmsx104.amr.corp.intel.com> Thank god for autocomplete *clicks tab* :P Regards Cesar Lara -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, September 5, 2018 5:30 PM To: Arevalo, Mario Alfredo C ; McKenna, Jason ; Dean Troyer ; Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Build] unified build command suggestions My $0.02, for what it's worth. The name stx-build-tool is too long. +1 to stxb from a previous note in this thread. brucej -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Wednesday, September 5, 2018 3:13 PM To: McKenna, Jason ; Dean Troyer ; Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Build] unified build command suggestions Hi team, Related to the tool name, a good point was mentioned, StarlingX is the core project, “stx” should be reserved for the core things. The building tool will be called “stx-build-tool” or “stx-bt” and it is good to keep consistency with the current stuff. And about the different options/subcommands proposed by Jason, they can exist, the idea is to cover both sides, develop and user sides. It is possible to have users that maybe would not like to involve in the development process and they just want to get ISO image, this is a valid point and our build tool should allow that way, the next proposed commands should be enough for a “Quick user guide”. $ stx-build-tool mirror create $ stx-build-tool iso build By the other hand the developers need more granularity about the processes, then the subcommands proposed by Jason are welcome. The implementation of this script will be modular, then it will be easy to implement relevant and needed subcommands in a future just calling the required functions. An related to the comment about Makefile rules, I think it could be better to use shell commands directly instead to wrap them in a Makefile, due to it is easier to customized values on command line. Using Makefiles it is possible to do it too, but I think it is a little less friendly. Best Regards. Mario. ________________________________________ From: McKenna, Jason [Jason.McKenna at windriver.com] Sent: Wednesday, September 05, 2018 11:02 AM To: Dean Troyer; Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Build] unified build command suggestions > -----Original Message----- > From: Dean Troyer > Sent: September 5, 2018 1:54 PM > To: Saul Wold > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [Build] unified build command > suggestions > > On Wed, Sep 5, 2018 at 12:16 PM, Saul Wold wrote: > > I agree with this, similar to what git and some other tools do also, > > I like the examples you provided below. > > Sooooo..... git should mostly not be used as an example UI for most > purposes, it is a bit of a mess :) > > git remote add ... (ok, but...) > git branch -m ... (not branch move? branch is sometimes an > object and sometimes a verb depending on the options!!) > > > I think it would be better if was more like > > > > stxb build iso > > stxb build all > > > > I know this is different than the mirror actions above, but the "all" > > does not make sense to me in this usage. > > This is the what-comes-first question, the object or the action? VMS > is still leaking from my brain in that I also prefer the action (verb) > to be first. OSC reversed itself 5 years ago because of the > bash-completion issue, we use cliff to implement the command parser > (built on top of argparse) and doing verb- first and bash completion > turned out to be a mess. That is an implementation driving design, > which is not always great, but was acceptable to the team at the time. > > Which ever order is settled on, PLEASE make all commands the same. > The UX studies we did with OSC always showed this consistency to be > very important to both new and experienced users. > +1 on consistency :) I think we need discussion around what we're really trying to accomplish. Going back to Cesar's initial proposal, the problem he wanted solved was that his team felt that there were too many commands required to produce an ISO after you've downloaded the mirrors (generate-cgcs-centos-repo.sh, build-pkgs, build-iso) and wanted to wrap those in a single command. Please correct me if I've misstated the problem, Cesar. Furthermore, I think you were looking for a command which did the steps that a developer would execute and not do the steps that a developer would not (downloading the mirror, is intended to be done at a per-site level, not a per-developer level, and would not necessarily be included in the single-command). Finally, the command was intended to be expandable and adaptable in the future (again, please correct me if I've misstated anything). Other than the "meet all conceivable future needs" requirement, I don't see much that couldn't be done with something like a Makefile: make mirror make environment make build make iso especially if you have the "iso" target depend on the "build" target which depends on the "environment" target, etc, then the whole process boils down to one "make iso" command for a developer (2 commands if they have to download the mirror themselves). Note that I'm not proposing "make" as a solution, I understand the concern that make wouldn't meet our needs in the future, and make can be less than pretty. I'm more engaging in the thought exercise of "what problem are we really trying to solve and has anyone solved it in the past" If we're wrapping or re-writing the build commands to make it simpler/easier for a developer, we should define proper use cases and make sure we're solving the right problems. To go off on a tangent, I find the illegible output of the build commands to be much more a stumbling block than the fact that I have to execute 3 commands rather than 1 to produce a build. > dt > > -- > > Dean Troyer > dtroyer at gmail.com > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Wed Sep 5 22:41:36 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 5 Sep 2018 22:41:36 +0000 Subject: [Starlingx-discuss] [Build] unified build command suggestions In-Reply-To: References: <5e4d9d83-93f8-c04f-47b5-46b795d4287a@linux.intel.com> Message-ID: <1a59d580e0fbac47136be0d7d94b6cab0a746078.camel@intel.com> Hi, I think that Saul uses git as a reference in terms of how the git command redirects the input to the subcommands. If you run git foo, internally will try to run git-foo, so git-foo could be a bash script and it will work. We created a etherpad to capture features and use cases. You can see it here: https://etherpad.openstack.org/p/stx-build-tool-features The "Implement command line utility that works as a gateway for subcommands" feature covers this proposal. -Erich On Wed, 2018-09-05 at 12:53 -0500, Dean Troyer wrote: > On Wed, Sep 5, 2018 at 12:16 PM, Saul Wold > wrote: > > I agree with this, similar to what git and some other tools do > > also, I like > > the examples you provided below. > > Sooooo..... git should mostly not be used as an example UI for most > purposes, it is a bit of a mess :) > > git remote add ... (ok, but...) > git branch -m ... (not branch move? branch is sometimes an > object and sometimes a verb depending on the options!!) > > > I think it would be better if was more like > > > > stxb build iso > > stxb build all > > > > I know this is different than the mirror actions above, but the > > "all" does > > not make sense to me in this usage. > > This is the what-comes-first question, the object or the action? VMS > is still leaking from my brain in that I also prefer the action > (verb) > to be first. OSC reversed itself 5 years ago because of the > bash-completion issue, we use cliff to implement the command parser > (built on top of argparse) and doing verb-first and bash completion > turned out to be a mess. That is an implementation driving design, > which is not always great, but was acceptable to the team at the > time. > > Which ever order is settled on, PLEASE make all commands the same. > The UX studies we did with OSC always showed this consistency to be > very important to both new and experienced users. > > dt > From erich.cordoba.malibran at intel.com Wed Sep 5 22:55:19 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 5 Sep 2018 22:55:19 +0000 Subject: [Starlingx-discuss] [Build] unified build command suggestions In-Reply-To: References: <5e4d9d83-93f8-c04f-47b5-46b795d4287a@linux.intel.com> Message-ID: > > +1 on consistency :) > > I think we need discussion around what we're really trying to > accomplish. Going back to Cesar's initial proposal, the problem he > wanted solved was that his team felt that there were too many > commands required to produce an ISO after you've downloaded the > mirrors (generate-cgcs-centos-repo.sh, build-pkgs, build-iso) and > wanted to wrap those in a single command. Please correct me if I've > misstated the problem, Cesar. Furthermore, I think you were looking > for a command which did the steps that a developer would execute and > not do the steps that a developer would not (downloading the mirror, > is intended to be done at a per-site level, not a per-developer > level, and would not necessarily be included in the single-command). I think the biggest motivation behind this effort is to simplify the build procedure for newcomers. It is true that in well established infrastructure there will be commands that won't be part of the common workflow for developers. However, since we started to build StarlingX we faced problems to understand and to repeat the procedure. From some emails in the mailing list we can see that new people trying to build have problems of different kinds. It would be good to have something that can tell "You can't start a build because you don't have a mirror downloaded" or "You have packages in the .lst files that are not in your mirror, try to update your mirror". I think that in opensource, adoption is one of the key parts. We need to improve the procedure for new people so they can continue using our project, otherwise they will jump to another, more easy think to build. -Erich From Ghada.Khalil at windriver.com Wed Sep 5 23:48:25 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 5 Sep 2018 23:48:25 +0000 Subject: [Starlingx-discuss] Minutes: October Release Kick-Off Meeting - 8/5/2018 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA44FCDF@ALA-MBD.corp.ad.wrs.com> Thanks for everyone who attended the release kick-off meeting today. Minutes are kept at: https://etherpad.openstack.org/p/stx-releases I strongly recommend that all Team Leads review the minutes and respond with any questions/concerns. Please note that we will forgo weekly meetings on Tuesday for now and will add release topics as an item on the Wednesday community meeting. Ad hoc meetings will be called as needed. Code Freeze Count-Down: 3wks Minutes: * Align on release deliverables ? We have something related to this documented on the wiki already: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Definition * Team validated the assumption that STX is a source-only project, so the above release definition is still accurate * Content ? What to do with target content that doesn't make it at the code freeze date? * STX releases are time-based. Content that doesn't make it is moved to the next release by default (or abandoned). * Features: Move to the next release (i.e. re-tag) o No feature content after the code freeze date * Bugs: Ideally we want current gating bugs to have been addressed by the code freeze, but can consider deferring some to the RC period. * Mechanics for creating the release branch/tags ? Do we want an RC period? If so, how do we want to handle it? * Reference: For Openstack, code freeze happens first; this is a hard date where master is frozen for a period. Then they enter the RC period: each project creates their branch and tags it as RC1. After some stability period,eachproject re-tags until the relase date. OpenStack RCs are actually re-tagged for the release if there are no changes at release time. * For StarlingX, we agreed on code freeze (hard date: Sept 26), then have a review to decide when to create the branch (may want to wait for a few items that are close). This approach gives us the flexibility. o After code freeze, master is frozen until the release branch is created. o The release branch will be created for all repo's at the same time. o The release branch will be called: r/2018.10 and will initially be tagged as 2018.10.0 (RC1). ? Re-tagging frequency TBD * Release Branch Creation Criteria: o Build Successful o Sanity Passed o Release stake-holders review and agree to create release branch * Test activities/plan once release branch is created ? Daily automated sanity will continue on master as well as the release branch ? Test team is working on defining test-cases to be run on the release branch. Target is 300 TCs to be run manually. ? AR: Ada to share list of TCs with the team once available. Target: Sept19 ? All configuration will be covered: multi-node w/ storage, multi-node w/o storage, simplex, duplex ? Testing will cover baremetal as well as the virtual environment * Bug Management during the RC period ? Use Bug template ? Always source in master first ? Criteria for which bugs gate the release and require a cherry-pick to the release branch. Who is responsible for cherry-picking? * Ghada will continue to tag bugs with the appropriate sub-project tag to make the bugs visible to the appropriate sub-team - pinging TLs as needed. * Ghada will also add the Launchpad query (Bugs Needing Triage) to the wiki to make it more accessible to all sub-teams. * Each sub-team will decide whether a reported bug gates the release as they are in the best position to articulate the impact. If gating, the bug must be tagged with stx.2018.10 * Each designer is responsible for cherry picking the fix from the master branch to the release branch. Only bugs tagged with stx.2018.10 should be cherry-picked. * AR: Team Leads should be able to assign bugs to their team members. Ghada to figure out if team membership is the requirement to be able to do this * Documentation ? Content to include: * Release Notes o Agreed to generate high level release notes only o Doc team is automating the generation of the release notes. Infrastructure should be ready by next week. o Automated release notes are created per repo. ? stx-metal is currently used as the first repo to generate release notes as well as general documentation and api-reference guides ? Each sub-team will create high level release note place-holders and populate them once the process is proven and published. ? api-ref documentation will be handled by the documentation team o High level list of features ? Each sub-team to decide whether to list some key features or at least an introduction to the sub-project (main functionality, etc) o Limitations/Caveats ? No plan to document a list of fixed/open bugs for this release ? Each sub-team can decide what limitations/caveats they want to document in their per-repo o If we want overall StarlingX release notes, these need to be hand crafted. ? TBD whether we will do this o Review Release Notes Management email: http://lists.starlingx.io/pipermail/starlingx-discuss/2018-August/000690.html o Release Notes Tracking ? https://wiki.openstack.org/wiki/StarlingX/Releases/Release_Notes * Standard Documentation - Developer Guide / API / others o Documentation Tracking ? https://wiki.openstack.org/wiki/StarlingX/Documentation o API Reference Tracking ? https://wiki.openstack.org/wiki/StarlingX/Developer_Guide/API_Documentation o Doc team has this under control; no specific items discussed ? Format * I believe the doc team have a plan for this already o See above Tracking links for Documentation, Release Notes and API Reference o See notes above * Weekly Calls ? Get agreement on weekly calls -- Proposal: Tuesday 9am Eastern / several options for afternoon slots if China not attending (Tuesday 5pm / Thursday 1pm or 3pm) ? Agreed to cover the release topics in the Wednesday community meeting. If there are major issues, then we can book an ad-hoc meeting as required Regards, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Thu Sep 6 00:52:06 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 05 Sep 2018 19:52:06 -0500 Subject: [Starlingx-discuss] 6 days left for the Forum Brainstorming Period... Message-ID: <5B907A36.3060901@openstack.org> Hello All! The Forum Brainstorming session ends September 11 and the topic submission phase begins September 12. Thank you to all of the projects that have created a wiki and begun the Brainstorming Phase. I'd like to encourage projects that have not yet created an etherpad to do so at https://wiki.openstack.org/wiki/Forum/Berlin2018 This is an opportunity to get feedback, vet ideas, and garner support from the community on your ideas. Don't rely only on a PTL to make the agenda... step on up and place the items you consider important front and center :) If you have questions or concerns about the process, please don't hesitate to reach out. Cheers, Jimmy From xiaoyan.li at intel.com Thu Sep 6 01:59:04 2018 From: xiaoyan.li at intel.com (Li, Xiaoyan) Date: Thu, 6 Sep 2018 01:59:04 +0000 Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Message-ID: Hi all, This email is about Raw caching function in StarlingX. This feature is to cache an image in backend storage like Ceph when we first create a volume in this backend storage. In fact, Cinder upstream has already had a similar function in Pike release. https://specs.openstack.org/openstack/cinder-specs/specs/liberty/image-volume-cache.html So I want to revert Raw caching function in StarlingX, and use Cinder generic image cache instead. The problem is that we need to update Cinder config in StarlingX. Any comments? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Thu Sep 6 02:01:59 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 6 Sep 2018 02:01:59 +0000 Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB25D46B@ALA-MBD.corp.ad.wrs.com> We would need to review this feature to ensure it provides equivalent functionality first. If it does, great, we can look at reverting and enabling this cinder functionality. Brent From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com] Sent: Wednesday, September 5, 2018 9:59 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi all, This email is about Raw caching function in StarlingX. This feature is to cache an image in backend storage like Ceph when we first create a volume in this backend storage. In fact, Cinder upstream has already had a similar function in Pike release. https://specs.openstack.org/openstack/cinder-specs/specs/liberty/image-volume-cache.html So I want to revert Raw caching function in StarlingX, and use Cinder generic image cache instead. The problem is that we need to update Cinder config in StarlingX. Any comments? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Sep 6 02:07:14 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 6 Sep 2018 02:07:14 +0000 Subject: [Starlingx-discuss] python-eventlet upgrade issue In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655355AEF@SHSMSX101.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C7655356ECC@SHSMSX101.ccr.corp.intel.com> Thanks Dean. I checked eventlet 0.20.0. It has the same issue. https://github.com/eventlet/eventlet/issues/413 Also I cannot find 0.20.0 in centos repo. So I will keep current 0.18.4 version, which also meet the global-requirements for pike. I will try to go through the packages upgraded with the global-requirements and upper-constraints. Will try to match them if possible. https://github.com/openstack/requirements/blob/stable/pike/global-requirements.txt https://github.com/openstack/requirements/blob/stable/pike/upper-constraints.txt#L377 Best Regards Shuicheng -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Thursday, September 6, 2018 12:58 AM To: Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] python-eventlet upgrade issue On Wed, Aug 29, 2018 at 9:51 PM, Lin, Shuicheng wrote: > Anyone familiar with python-eventlet? I meet a problem when upgrade > python-eventlet from “0.18.4-2” to “0.20.1-2”, when do CentOS7.5 upgrade. [...] > The issue is that, after upgrade to 0.20.1-2 version, these functions > don’t work as expected. Looking at upstream OpenStack requirements for Pike, eventlet is listed in global-requirements (the minimum required version) as eventlet!=0.18.3,>=0.18.2,!=0.20.1,<0.21.0 # MIT and in upper-contraints.txt (what is actually tests in the gate) as eventlet===0.20.0 In order to be co-installable with OpenStack we must maintain similar versions for the STX services. FWIW, rocky's versions of the above are similar: eventlet!=0.18.3,!=0.20.1,!=0.21.0,!=0.23.0 and eventlet===0.20.0 Also note that OpenStack is preparing[0] to raise the u-c version of eventlet to 0.24.1, which I believe is current master. We should be preparing 0.20.0 for packaging. Even though OpenStack master is mostly ready for 0.24.1 I doubt that Pike is nor will it be made so... Background OpenStack maintains both minimum and maximum version requirements for Python dependencies that must be shared by all OpenStack projects. This is to maintain co-installability since Python can not install multiple versions of a package without resorting to techniques such as virtual environments. There are CI jobs for checking these, and projects are free to be stricter in their reqirements.txt files as long as they fit within the globally defined min/max. StarlingX services (flock) need to be compatible with Pike, although it is not currently enforced. dt [0] http://lists.openstack.org/pipermail/openstack-dev/2018-August/133728.html -- Dean Troyer dtroyer at gmail.com From scottk at optimcloud.com Thu Sep 6 02:55:47 2018 From: scottk at optimcloud.com (scottk at optimcloud.com) Date: Thu, 06 Sep 2018 02:55:47 +0000 Subject: [Starlingx-discuss] Developer Guide / build failures Message-ID: <42b787ac2c187c5ec28196b26bc91587@optimcloud.com> going through the latest docs from https://wiki.openstack.org/wiki/StarlingX/Developer_Guide (https://wiki.openstack.org/wiki/StarlingX/Developer_Guide) ive gone through all steps as desccribed and getting a final iso built still is not possible 17:37:53 Recreate repodata 17:38:07 17:38:07 Failed to build packages: integrity-kmod-4.12-0.tis.5.src.rpm ######## Wed Sep 5 17:38:07 UTC 2018: build-rpm-parallel --std failed with rc=1 Wed Sep 5 17:38:07 UTC 2018: build-rpm-parallel --std failed with rc=1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dehao.shang at intel.com Thu Sep 6 05:40:33 2018 From: dehao.shang at intel.com (Shang, Dehao) Date: Thu, 6 Sep 2018 05:40:33 +0000 Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status In-Reply-To: References: <371DF9A763E9F44F924F4A821FC070264C4993FF@SHSMSX104.ccr.corp.intel.com> Message-ID: <71AECFE5078153419EB7B8DBE0644B26386360C9@shsmsx102.ccr.corp.intel.com> Hi, yong: We have successfully built starlingx image. Now, then just replace old version ceph with ceph 13.2.0 version. So, I can think that current all error are caused by new version ceph. Thanks Dehao From: Hu, Yong Sent: Wednesday, September 5, 2018 10:02 PM To: Zhu, Vivian ; starlingx-discuss at lists.starlingx.io Cc: Shang, Dehao Subject: Re: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Quick question: Before switching to newer version (ceph 13.2.0), have you ever built out the packages and ISO? From: "Zhu, Vivian" > Date: Wednesday, 5 September 2018 at 9:54 PM To: "starlingx-discuss at lists.starlingx.io" > Cc: "Shang, Dehao" > Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Hi Anyone who is familiar with stx-tools or build flow, Our storage team (Dehao etc.) have worked on Ceph upgrading on starlingX project and we are still staggering to resolve issues one-by-one, now we fail to build ISO, the log points to “These RPMS had problems (likely version conflicts) “. Here is our build steps and according action we did. We are looking for help to solve it, if anyone who can give some hints to narrow down/address issue or point out the wrong step here. That’s really helpful to unblock Ceph upgrade to catch up Sep.26 code freeze. Build flow step 1: download_mirror ---> container 1 | step 2: manually check *_miss_*.txt and *_fails_*.txt file, then download miss and fails package | step 3: to ensure that all package listed by rpms_from_3rd_parties.list and rpms_from_centos_repo.lst are downloaded | step 4: create work space : mkdir -p $HOME/starlingx/mirror/Centos | step 5: copy mirror to workspace which can be used by container 2 | step 6: edit Dockerfile, create image, then run container, and so on. | step 7 : clone all source using "repo sync" → container 2 | step 8: at git folder, using ceph 13.2.0 to replace ceph 10.2.6 | step 9: using ceph tools "make-srpm.sh" to create 13.2.0 ceph.spec file. | step 10 : modify new ceph.spec file according to stx-ceph's ceph.spec file | step 11: copy stx-ceph's wrs folder to ceph 13.2.0 | step 12: build-pkgs --serial | step 13: build_iso <-----------------------------fails !!! | step 14 : success building What we had done 1:can build starlingx image 2:ceph 13.2.0’s ceph.spec file can works. 3: build-pkgs can build all package What part we are gating when building ISO, deps can’t be resolved. we tried steps but failed. Stalingx log give one error conclusion as following: 22:14:55 Debug: Packages still unresolved: 22:14:55 22:14:56 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 22:14:56 These RPMS had problems (likely version conflicts) 22:14:56 librados.so.2()(64bit) 22:14:56 Could not install dependencies What’s the next step 1: Talked with Qi mingyuan, plan to compare every ceph 13.2.0 depes package with mirror’s package. 2: Deploy one starlingx cluster, check package and env. Help needed If we can get stx-tools design, implement overview or building flow, it can help us speed up the debug/upgrading. Thanks! - Vivian SSG OTC NST Storage Tel: (8621)61167437 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dehao.shang at intel.com Thu Sep 6 05:45:12 2018 From: dehao.shang at intel.com (Shang, Dehao) Date: Thu, 6 Sep 2018 05:45:12 +0000 Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status In-Reply-To: <9700A18779F35F49AF027300A49E7C7655356CF0@SHSMSX101.ccr.corp.intel.com> References: <371DF9A763E9F44F924F4A821FC070264C4993FF@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C7655356CF0@SHSMSX101.ccr.corp.intel.com> Message-ID: <71AECFE5078153419EB7B8DBE0644B26386360E2@shsmsx102.ccr.corp.intel.com> Hi, shuicheng: I have check this deps.txt file, but it just show that “librados.so.2().(64bit)”. [dehao at 89dc575105d5 /]$ cat /localdisk/loadbuild/dehao/starlingx/export/deps.txt librados.so.2()(64bit) [dehao at 89dc575105d5 /]$ Thanks Dehao From: Lin, Shuicheng Sent: Wednesday, September 5, 2018 10:14 PM To: Hu, Yong ; Zhu, Vivian ; starlingx-discuss at lists.starlingx.io Cc: Shang, Dehao Subject: RE: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status For the build-iso failure, it should be due to dependency check. There should be another file “deps-detail.txt” under the same folder as deps.txt. (/localdisk/loadbuild/dehao/starlingx/export/deps.txt) You could get more info from this file. Best Regards Shuicheng From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Wednesday, September 5, 2018 10:02 PM To: Zhu, Vivian >; starlingx-discuss at lists.starlingx.io Cc: Shang, Dehao > Subject: Re: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Quick question: Before switching to newer version (ceph 13.2.0), have you ever built out the packages and ISO? From: "Zhu, Vivian" > Date: Wednesday, 5 September 2018 at 9:54 PM To: "starlingx-discuss at lists.starlingx.io" > Cc: "Shang, Dehao" > Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Hi Anyone who is familiar with stx-tools or build flow, Our storage team (Dehao etc.) have worked on Ceph upgrading on starlingX project and we are still staggering to resolve issues one-by-one, now we fail to build ISO, the log points to “These RPMS had problems (likely version conflicts) “. Here is our build steps and according action we did. We are looking for help to solve it, if anyone who can give some hints to narrow down/address issue or point out the wrong step here. That’s really helpful to unblock Ceph upgrade to catch up Sep.26 code freeze. Build flow step 1: download_mirror ---> container 1 | step 2: manually check *_miss_*.txt and *_fails_*.txt file, then download miss and fails package | step 3: to ensure that all package listed by rpms_from_3rd_parties.list and rpms_from_centos_repo.lst are downloaded | step 4: create work space : mkdir -p $HOME/starlingx/mirror/Centos | step 5: copy mirror to workspace which can be used by container 2 | step 6: edit Dockerfile, create image, then run container, and so on. | step 7 : clone all source using "repo sync" → container 2 | step 8: at git folder, using ceph 13.2.0 to replace ceph 10.2.6 | step 9: using ceph tools "make-srpm.sh" to create 13.2.0 ceph.spec file. | step 10 : modify new ceph.spec file according to stx-ceph's ceph.spec file | step 11: copy stx-ceph's wrs folder to ceph 13.2.0 | step 12: build-pkgs --serial | step 13: build_iso <-----------------------------fails !!! | step 14 : success building What we had done 1:can build starlingx image 2:ceph 13.2.0’s ceph.spec file can works. 3: build-pkgs can build all package What part we are gating when building ISO, deps can’t be resolved. we tried steps but failed. Stalingx log give one error conclusion as following: 22:14:55 Debug: Packages still unresolved: 22:14:55 22:14:56 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 22:14:56 These RPMS had problems (likely version conflicts) 22:14:56 librados.so.2()(64bit) 22:14:56 Could not install dependencies What’s the next step 1: Talked with Qi mingyuan, plan to compare every ceph 13.2.0 depes package with mirror’s package. 2: Deploy one starlingx cluster, check package and env. Help needed If we can get stx-tools design, implement overview or building flow, it can help us speed up the debug/upgrading. Thanks! - Vivian SSG OTC NST Storage Tel: (8621)61167437 -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Sep 6 07:08:44 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 6 Sep 2018 07:08:44 +0000 Subject: [Starlingx-discuss] Developer Guide / build failures In-Reply-To: <42b787ac2c187c5ec28196b26bc91587@optimcloud.com> References: <42b787ac2c187c5ec28196b26bc91587@optimcloud.com> Message-ID: <9700A18779F35F49AF027300A49E7C7655356F70@SHSMSX101.ccr.corp.intel.com> Hi, Please check the build log. It will have similar issue as below: 16:22:50 ERROR: Exception(/localdisk/loadbuild/slin14/starlingx/std/rpmbuild/SRPMS/syslog-ng-3.5.6-3.el7.tis.20.src.rpm) Config(mock/b0) 0 minutes 32 seconds 16:22:50 INFO: Results and/or logs in: /localdisk/loadbuild/slin14/starlingx/std/results/slin14-starlingx-tis-r5-pike-std/syslog-ng-3.5.6-3.el7.tis.20 Then you could check the build.log in upper folder. It will show you why there is build failure. Best Regards Shuicheng From: scottk at optimcloud.com [mailto:scottk at optimcloud.com] Sent: Thursday, September 6, 2018 10:56 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Developer Guide / build failures going through the latest docs from https://wiki.openstack.org/wiki/StarlingX/Developer_Guide ive gone through all steps as desccribed and getting a final iso built still is not possible 17:37:53 Recreate repodata 17:38:07 17:38:07 Failed to build packages: integrity-kmod-4.12-0.tis.5.src.rpm ######## Wed Sep 5 17:38:07 UTC 2018: build-rpm-parallel --std failed with rc=1 Wed Sep 5 17:38:07 UTC 2018: build-rpm-parallel --std failed with rc=1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From scottk at optimcloud.com Thu Sep 6 10:18:22 2018 From: scottk at optimcloud.com (scottk at optimcloud.com) Date: Thu, 06 Sep 2018 10:18:22 +0000 Subject: [Starlingx-discuss] Command line error: no such option: --arcgglist Message-ID: <3296850131893933794b3ac9f351cfa2@optimcloud.com> so trying this a fifth time, i see the following errors numerous times for various packages during the bash download_mirror.sh phase of the process as documented in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide (https://wiki.openstack.org/wiki/StarlingX/Developer_Guide) Warning: infinipath-psm-3.3-26_g604758e_open.2.el7.x86_64.rpm not found ------ using info-5.1-4.el7 to search info-5.1-4.el7.x86_64.rpm ------ Looking for info-5.1-4.el7.x86_64.rpm... --> run: sudo -E yumdownloader -q -C --releasever=7 info-5.1-4.el7 --arcgglist=noarch,x86_64 Command line error: no such option: --arcgglist Usage: "yumdownloader [options] package1 [package2] [package..] -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Sep 6 11:59:08 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 6 Sep 2018 11:59:08 +0000 Subject: [Starlingx-discuss] Command line error: no such option: --arcgglist In-Reply-To: <3296850131893933794b3ac9f351cfa2@optimcloud.com> References: <3296850131893933794b3ac9f351cfa2@optimcloud.com> Message-ID: <9700A18779F35F49AF027300A49E7C76553570AB@SHSMSX101.ccr.corp.intel.com> Hi, This is a code error. Please change the “arcgglist” to “archlist”. slin14 at slin14-nuc2:~/GIT/stx-tools$ git diff diff --git a/centos-mirror-tools/dl_rpms.sh b/centos-mirror-tools/dl_rpms.sh index 67cf792..09f6751 100755 --- a/centos-mirror-tools/dl_rpms.sh +++ b/centos-mirror-tools/dl_rpms.sh @@ -220,7 +220,7 @@ download () { download_cmd="${SUDOCMD} yumdownloader -q ${YUMCONFOPT} ${RELEASEVER} -C --source $SFILE" download_url_cmd="${SUDOCMD} yumdownloader --urls -q ${YUMCONFOPT} ${RELEASEVER} -C --source $SFILE" else - download_cmd="${SUDOCMD} yumdownloader -q -C ${YUMCONFOPT} ${RELEASEVER} $SFILE --arcgglist=noarch,x86_64" + download_cmd="${SUDOCMD} yumdownloader -q -C ${YUMCONFOPT} ${RELEASEVER} $SFILE --archlist=noarch,x86_64" download_url_cmd="${SUDOCMD} yumdownloader --urls -q -C ${YUMCONFOPT} ${RELEASEVER} $SFILE --archlist=noarch,x86_64" fi fi Best Regards Shuicheng From: scottk at optimcloud.com [mailto:scottk at optimcloud.com] Sent: Thursday, September 6, 2018 6:18 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Command line error: no such option: --arcgglist so trying this a fifth time, i see the following errors numerous times for various packages during the bash download_mirror.sh phase of the process as documented in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide Warning: infinipath-psm-3.3-26_g604758e_open.2.el7.x86_64.rpm not found ------ using info-5.1-4.el7 to search info-5.1-4.el7.x86_64.rpm ------ Looking for info-5.1-4.el7.x86_64.rpm... --> run: sudo -E yumdownloader -q -C --releasever=7 info-5.1-4.el7 --arcgglist=noarch,x86_64 Command line error: no such option: --arcgglist Usage: "yumdownloader [options] package1 [package2] [package..] -------------- next part -------------- An HTML attachment was scrubbed... URL: From scottk at optimcloud.com Thu Sep 6 12:07:43 2018 From: scottk at optimcloud.com (scottk at optimcloud.com) Date: Thu, 06 Sep 2018 12:07:43 +0000 Subject: [Starlingx-discuss] Command line error: no such option: --arcgglist In-Reply-To: <9700A18779F35F49AF027300A49E7C76553570AB@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76553570AB@SHSMSX101.ccr.corp.intel.com> <3296850131893933794b3ac9f351cfa2@optimcloud.com> Message-ID: I am also recieving this continuously, like nothing in the list even exists and is a 404... how is that possible? arning: gsm-1.0.13-11.el7.x86_64.rpm not found Looking for gstreamer-0.10.36-7.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer/0.10.36/7.el7/x86_64/gstreamer-0.10.36-7.el7.x86_64.rpm) --2018-09-06 12:06:35-- https://kojipkgs.fedoraproject.org/packages/gstreamer/0.10.36/7.el7/x86_64/gstreamer-0.10.36-7.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:06:36 ERROR 404: Not Found. Warning: gstreamer-0.10.36-7.el7.x86_64.rpm not found Looking for gstreamer-plugins-base-0.10.36-10.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer-plugins-base/0.10.36/10.el7/x86_64/gstreamer-plugins-base-0.10.36-10.el7.x86_64.rpm) --2018-09-06 12:06:36-- https://kojipkgs.fedoraproject.org/packages/gstreamer-plugins-base/0.10.36/10.el7/x86_64/gstreamer-plugins-base-0.10.36-10.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:06:37 ERROR 404: Not Found. Warning: gstreamer-plugins-base-0.10.36-10.el7.x86_64.rpm not found Looking for gstreamer-plugins-good-0.10.31-13.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer-plugins-good/0.10.31/13.el7/x86_64/gstreamer-plugins-good-0.10.31-13.el7.x86_64.rpm) --2018-09-06 12:06:37-- https://kojipkgs.fedoraproject.org/packages/gstreamer-plugins-good/0.10.31/13.el7/x86_64/gstreamer-plugins-good-0.10.31-13.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:06:38 ERROR 404: Not Found. Warning: gstreamer-plugins-good-0.10.31-13.el7.x86_64.rpm not found Looking for gstreamer-tools-0.10.36-7.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer-tools/0.10.36/7.el7/x86_64/gstreamer-tools-0.10.36-7.el7.x86_64.rpm) --2018-09-06 12:06:38-- https://kojipkgs.fedoraproject.org/packages/gstreamer-tools/0.10.36/7.el7/x86_64/gstreamer-tools-0.10.36-7.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:06:39 ERROR 404: Not Found. Warning: gstreamer-tools-0.10.36-7.el7.x86_64.rpm not found Looking for gtk2-2.24.31-1.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/gtk2/2.24.31/1.el7/x86_64/gtk2-2.24.31-1.el7.x86_64.rpm) --2018-09-06 12:06:39-- https://kojipkgs.fedoraproject.org/packages/gtk2/2.24.31/1.el7/x86_64/gtk2-2.24.31-1.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:06:40 ERROR 404: Not Found. September 6, 2018 1:59 PM, "Lin, Shuicheng" )> wrote: Hi, This is a code error. Please change the “arcgglist” to “archlist”. slin14 at slin14-nuc2:~/GIT/stx-tools$ git diff diff --git a/centos-mirror-tools/dl_rpms.sh b/centos-mirror-tools/dl_rpms.sh index 67cf792..09f6751 100755 --- a/centos-mirror-tools/dl_rpms.sh +++ b/centos-mirror-tools/dl_rpms.sh @@ -220,7 +220,7 @@ download () { download_cmd="${SUDOCMD} yumdownloader -q ${YUMCONFOPT} ${RELEASEVER} -C --source $SFILE" download_url_cmd="${SUDOCMD} yumdownloader --urls -q ${YUMCONFOPT} ${RELEASEVER} -C --source $SFILE" else - download_cmd="${SUDOCMD} yumdownloader -q -C ${YUMCONFOPT} ${RELEASEVER} $SFILE --arcgglist=noarch,x86_64" + download_cmd="${SUDOCMD} yumdownloader -q -C ${YUMCONFOPT} ${RELEASEVER} $SFILE --archlist=noarch,x86_64" download_url_cmd="${SUDOCMD} yumdownloader --urls -q -C ${YUMCONFOPT} ${RELEASEVER} $SFILE --archlist=noarch,x86_64" fi fi Best Regards Shuicheng From: scottk at optimcloud.com (mailto:scottk at optimcloud.com) [mailto:scottk at optimcloud.com (mailto:scottk at optimcloud.com)] Sent: Thursday, September 6, 2018 6:18 PM To: starlingx-discuss at lists.starlingx.io (mailto:starlingx-discuss at lists.starlingx.io) Subject: [Starlingx-discuss] Command line error: no such option: --arcgglist so trying this a fifth time, i see the following errors numerous times for various packages during the bash download_mirror.sh phase of the process as documented in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide (https://wiki.openstack.org/wiki/StarlingX/Developer_Guide) Warning: infinipath-psm-3.3-26_g604758e_open.2.el7.x86_64.rpm not found ------ using info-5.1-4.el7 to search info-5.1-4.el7.x86_64.rpm ------ Looking for info-5.1-4.el7.x86_64.rpm... --> run: sudo -E yumdownloader -q -C --releasever=7 info-5.1-4.el7 --arcgglist=noarch,x86_64 Command line error: no such option: --arcgglist Usage: "yumdownloader [options] package1 [package2] [package..] -------------- next part -------------- An HTML attachment was scrubbed... URL: From scottk at optimcloud.com Thu Sep 6 12:18:52 2018 From: scottk at optimcloud.com (scottk at optimcloud.com) Date: Thu, 06 Sep 2018 12:18:52 +0000 Subject: [Starlingx-discuss] ALL kojipkgs.fedoraproject.org packages result in 404 Not Found Message-ID: <24629478a312ae5c46862d8ac5269b2b@optimcloud.com> ALL kojipkgs.fedoraproject.org packages result in 404 Not Found Warning: kbd-legacy-1.15.5-13.el7.noarch.rpm not found Looking for kbd-misc-1.15.5-13.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/kbd-misc/1.15.5/13.el7/noarch/kbd-misc-1.15.5-13.el7.noarch.rpm) --2018-09-06 12:08:12-- https://kojipkgs.fedoraproject.org/packages/kbd-misc/1.15.5/13.el7/noarch/kbd-misc-1.15.5-13.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:13 ERROR 404: Not Found. Warning: kbd-misc-1.15.5-13.el7.noarch.rpm not found Looking for kde-filesystem-4-47.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/kde-filesystem/4/47.el7/x86_64/kde-filesystem-4-47.el7.x86_64.rpm) --2018-09-06 12:08:13-- https://kojipkgs.fedoraproject.org/packages/kde-filesystem/4/47.el7/x86_64/kde-filesystem-4-47.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:14 ERROR 404: Not Found. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Sep 6 12:23:39 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 6 Sep 2018 12:23:39 +0000 Subject: [Starlingx-discuss] Command line error: no such option: --arcgglist In-Reply-To: References: <9700A18779F35F49AF027300A49E7C76553570AB@SHSMSX101.ccr.corp.intel.com> <3296850131893933794b3ac9f351cfa2@optimcloud.com> Message-ID: <9700A18779F35F49AF027300A49E7C76553570D5@SHSMSX101.ccr.corp.intel.com> I guess there is something wrong with latest mirror script. The packages you list here, should be download from centos repo after you correct the script. Only the packages cannot get from repo will try to use koji. And I am not sure why below link is not correct. To quick workaround it, please revert below change in build-tools: “read releasever from yum.conf iff -c yum.conf is set” Best Regards Shuicheng From: scottk at optimcloud.com [mailto:scottk at optimcloud.com] Sent: Thursday, September 6, 2018 8:08 PM To: Lin, Shuicheng ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Command line error: no such option: --arcgglist I am also recieving this continuously, like nothing in the list even exists and is a 404... how is that possible? arning: gsm-1.0.13-11.el7.x86_64.rpm not found Looking for gstreamer-0.10.36-7.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer/0.10.36/7.el7/x86_64/gstreamer-0.10.36-7.el7.x86_64.rpm) --2018-09-06 12:06:35-- https://kojipkgs.fedoraproject.org/packages/gstreamer/0.10.36/7.el7/x86_64/gstreamer-0.10.36-7.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:06:36 ERROR 404: Not Found. Warning: gstreamer-0.10.36-7.el7.x86_64.rpm not found Looking for gstreamer-plugins-base-0.10.36-10.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer-plugins-base/0.10.36/10.el7/x86_64/gstreamer-plugins-base-0.10.36-10.el7.x86_64.rpm) --2018-09-06 12:06:36-- https://kojipkgs.fedoraproject.org/packages/gstreamer-plugins-base/0.10.36/10.el7/x86_64/gstreamer-plugins-base-0.10.36-10.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:06:37 ERROR 404: Not Found. Warning: gstreamer-plugins-base-0.10.36-10.el7.x86_64.rpm not found Looking for gstreamer-plugins-good-0.10.31-13.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer-plugins-good/0.10.31/13.el7/x86_64/gstreamer-plugins-good-0.10.31-13.el7.x86_64.rpm) --2018-09-06 12:06:37-- https://kojipkgs.fedoraproject.org/packages/gstreamer-plugins-good/0.10.31/13.el7/x86_64/gstreamer-plugins-good-0.10.31-13.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:06:38 ERROR 404: Not Found. Warning: gstreamer-plugins-good-0.10.31-13.el7.x86_64.rpm not found Looking for gstreamer-tools-0.10.36-7.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer-tools/0.10.36/7.el7/x86_64/gstreamer-tools-0.10.36-7.el7.x86_64.rpm) --2018-09-06 12:06:38-- https://kojipkgs.fedoraproject.org/packages/gstreamer-tools/0.10.36/7.el7/x86_64/gstreamer-tools-0.10.36-7.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:06:39 ERROR 404: Not Found. Warning: gstreamer-tools-0.10.36-7.el7.x86_64.rpm not found Looking for gtk2-2.24.31-1.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/gtk2/2.24.31/1.el7/x86_64/gtk2-2.24.31-1.el7.x86_64.rpm) --2018-09-06 12:06:39-- https://kojipkgs.fedoraproject.org/packages/gtk2/2.24.31/1.el7/x86_64/gtk2-2.24.31-1.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:06:40 ERROR 404: Not Found. September 6, 2018 1:59 PM, "Lin, Shuicheng" > wrote: Hi, This is a code error. Please change the “arcgglist” to “archlist”. slin14 at slin14-nuc2:~/GIT/stx-tools$ git diff diff --git a/centos-mirror-tools/dl_rpms.sh b/centos-mirror-tools/dl_rpms.sh index 67cf792..09f6751 100755 --- a/centos-mirror-tools/dl_rpms.sh +++ b/centos-mirror-tools/dl_rpms.sh @@ -220,7 +220,7 @@ download () { download_cmd="${SUDOCMD} yumdownloader -q ${YUMCONFOPT} ${RELEASEVER} -C --source $SFILE" download_url_cmd="${SUDOCMD} yumdownloader --urls -q ${YUMCONFOPT} ${RELEASEVER} -C --source $SFILE" else - download_cmd="${SUDOCMD} yumdownloader -q -C ${YUMCONFOPT} ${RELEASEVER} $SFILE --arcgglist=noarch,x86_64" + download_cmd="${SUDOCMD} yumdownloader -q -C ${YUMCONFOPT} ${RELEASEVER} $SFILE --archlist=noarch,x86_64" download_url_cmd="${SUDOCMD} yumdownloader --urls -q -C ${YUMCONFOPT} ${RELEASEVER} $SFILE --archlist=noarch,x86_64" fi fi Best Regards Shuicheng From: scottk at optimcloud.com [mailto:scottk at optimcloud.com] Sent: Thursday, September 6, 2018 6:18 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Command line error: no such option: --arcgglist so trying this a fifth time, i see the following errors numerous times for various packages during the bash download_mirror.sh phase of the process as documented in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide Warning: infinipath-psm-3.3-26_g604758e_open.2.el7.x86_64.rpm not found ------ using info-5.1-4.el7 to search info-5.1-4.el7.x86_64.rpm ------ Looking for info-5.1-4.el7.x86_64.rpm... --> run: sudo -E yumdownloader -q -C --releasever=7 info-5.1-4.el7 --arcgglist=noarch,x86_64 Command line error: no such option: --arcgglist Usage: "yumdownloader [options] package1 [package2] [package..] -------------- next part -------------- An HTML attachment was scrubbed... URL: From scottk at optimcloud.com Thu Sep 6 12:15:48 2018 From: scottk at optimcloud.com (scottk at optimcloud.com) Date: Thu, 06 Sep 2018 12:15:48 +0000 Subject: [Starlingx-discuss] ALL kojipkgs.fedoraproject.org 404 Not Found Message-ID: seems also ALL kojipkgs.fedoraproject.org based packages resumt in a 404 Not Found Warning: ipa-pmincho-fonts-003.03-5.el7.noarch.rpm not found Looking for iperf3-3.1.7-2.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/iperf3/3.1.7/2.el7/x86_64/iperf3-3.1.7-2.el7.x86_64.rpm) --2018-09-06 12:07:28-- https://kojipkgs.fedoraproject.org/packages/iperf3/3.1.7/2.el7/x86_64/iperf3-3.1.7-2.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:29 ERROR 404: Not Found. Warning: iperf3-3.1.7-2.el7.x86_64.rpm not found Looking for ipmitool-1.8.18-7.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/ipmitool/1.8.18/7.el7/x86_64/ipmitool-1.8.18-7.el7.x86_64.rpm) --2018-09-06 12:07:29-- https://kojipkgs.fedoraproject.org/packages/ipmitool/1.8.18/7.el7/x86_64/ipmitool-1.8.18-7.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:30 ERROR 404: Not Found. Warning: ipmitool-1.8.18-7.el7.x86_64.rpm not found Looking for iproute-3.10.0-74.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/iproute/3.10.0/74.el7/x86_64/iproute-3.10.0-74.el7.x86_64.rpm) --2018-09-06 12:07:30-- https://kojipkgs.fedoraproject.org/packages/iproute/3.10.0/74.el7/x86_64/iproute-3.10.0-74.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:31 ERROR 404: Not Found. Warning: iproute-3.10.0-74.el7.x86_64.rpm not found Looking for ipset-6.29-1.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/ipset/6.29/1.el7/x86_64/ipset-6.29-1.el7.x86_64.rpm) --2018-09-06 12:07:31-- https://kojipkgs.fedoraproject.org/packages/ipset/6.29/1.el7/x86_64/ipset-6.29-1.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:32 ERROR 404: Not Found. Warning: ipset-6.29-1.el7.x86_64.rpm not found Looking for ipset-libs-6.29-1.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/ipset-libs/6.29/1.el7/x86_64/ipset-libs-6.29-1.el7.x86_64.rpm) --2018-09-06 12:07:32-- https://kojipkgs.fedoraproject.org/packages/ipset-libs/6.29/1.el7/x86_64/ipset-libs-6.29-1.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:33 ERROR 404: Not Found. Warning: ipset-libs-6.29-1.el7.x86_64.rpm not found Looking for iputils-20160308-10.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/iputils/20160308/10.el7/x86_64/iputils-20160308-10.el7.x86_64.rpm) --2018-09-06 12:07:33-- https://kojipkgs.fedoraproject.org/packages/iputils/20160308/10.el7/x86_64/iputils-20160308-10.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:34 ERROR 404: Not Found. Warning: iputils-20160308-10.el7.x86_64.rpm not found Looking for ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/ipxe-roms-qemu/20170123/1.git4e85b27.el7_4.1/noarch/ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm) --2018-09-06 12:07:34-- https://kojipkgs.fedoraproject.org/packages/ipxe-roms-qemu/20170123/1.git4e85b27.el7_4.1/noarch/ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:35 ERROR 404: Not Found. Warning: ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm not found Looking for iso-codes-3.46-2.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/iso-codes/3.46/2.el7/noarch/iso-codes-3.46-2.el7.noarch.rpm) --2018-09-06 12:07:35-- https://kojipkgs.fedoraproject.org/packages/iso-codes/3.46/2.el7/noarch/iso-codes-3.46-2.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:37 ERROR 404: Not Found. Warning: iso-codes-3.46-2.el7.noarch.rpm not found Looking for isomd5sum-1.0.10-5.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/isomd5sum/1.0.10/5.el7/x86_64/isomd5sum-1.0.10-5.el7.x86_64.rpm) --2018-09-06 12:07:37-- https://kojipkgs.fedoraproject.org/packages/isomd5sum/1.0.10/5.el7/x86_64/isomd5sum-1.0.10-5.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:38 ERROR 404: Not Found. Warning: isomd5sum-1.0.10-5.el7.x86_64.rpm not found Looking for ivykis-0.36.2-2.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/ivykis/0.36.2/2.el7/x86_64/ivykis-0.36.2-2.el7.x86_64.rpm) --2018-09-06 12:07:38-- https://kojipkgs.fedoraproject.org/packages/ivykis/0.36.2/2.el7/x86_64/ivykis-0.36.2-2.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:39 ERROR 404: Not Found. Warning: ivykis-0.36.2-2.el7.x86_64.rpm not found Looking for ivykis-devel-0.36.2-2.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/ivykis-devel/0.36.2/2.el7/x86_64/ivykis-devel-0.36.2-2.el7.x86_64.rpm) --2018-09-06 12:07:39-- https://kojipkgs.fedoraproject.org/packages/ivykis-devel/0.36.2/2.el7/x86_64/ivykis-devel-0.36.2-2.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:40 ERROR 404: Not Found. Warning: ivykis-devel-0.36.2-2.el7.x86_64.rpm not found Looking for jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jakarta-commons-httpclient/3.1/16.el7_0/noarch/jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm) --2018-09-06 12:07:40-- https://kojipkgs.fedoraproject.org/packages/jakarta-commons-httpclient/3.1/16.el7_0/noarch/jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:41 ERROR 404: Not Found. Warning: jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm not found Looking for jansson-2.10-1.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jansson/2.10/1.el7/x86_64/jansson-2.10-1.el7.x86_64.rpm) --2018-09-06 12:07:41-- https://kojipkgs.fedoraproject.org/packages/jansson/2.10/1.el7/x86_64/jansson-2.10-1.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:42 ERROR 404: Not Found. Warning: jansson-2.10-1.el7.x86_64.rpm not found Looking for jasper-devel-1.900.1-31.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jasper-devel/1.900.1/31.el7/x86_64/jasper-devel-1.900.1-31.el7.x86_64.rpm) --2018-09-06 12:07:42-- https://kojipkgs.fedoraproject.org/packages/jasper-devel/1.900.1/31.el7/x86_64/jasper-devel-1.900.1-31.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:43 ERROR 404: Not Found. Warning: jasper-devel-1.900.1-31.el7.x86_64.rpm not found Looking for jasper-libs-1.900.1-31.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jasper-libs/1.900.1/31.el7/x86_64/jasper-libs-1.900.1-31.el7.x86_64.rpm) --2018-09-06 12:07:43-- https://kojipkgs.fedoraproject.org/packages/jasper-libs/1.900.1/31.el7/x86_64/jasper-libs-1.900.1-31.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:44 ERROR 404: Not Found. Warning: jasper-libs-1.900.1-31.el7.x86_64.rpm not found Looking for javamail-1.4.6-8.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/javamail/1.4.6/8.el7/noarch/javamail-1.4.6-8.el7.noarch.rpm) --2018-09-06 12:07:44-- https://kojipkgs.fedoraproject.org/packages/javamail/1.4.6/8.el7/noarch/javamail-1.4.6-8.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:45 ERROR 404: Not Found. Warning: javamail-1.4.6-8.el7.noarch.rpm not found Looking for javapackages-tools-3.4.1-11.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/javapackages-tools/3.4.1/11.el7/noarch/javapackages-tools-3.4.1-11.el7.noarch.rpm) --2018-09-06 12:07:46-- https://kojipkgs.fedoraproject.org/packages/javapackages-tools/3.4.1/11.el7/noarch/javapackages-tools-3.4.1-11.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:46 ERROR 404: Not Found. Warning: javapackages-tools-3.4.1-11.el7.noarch.rpm not found Looking for javassist-3.16.1-10.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/javassist/3.16.1/10.el7/noarch/javassist-3.16.1-10.el7.noarch.rpm) --2018-09-06 12:07:47-- https://kojipkgs.fedoraproject.org/packages/javassist/3.16.1/10.el7/noarch/javassist-3.16.1-10.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:48 ERROR 404: Not Found. Warning: javassist-3.16.1-10.el7.noarch.rpm not found Looking for jbigkit-libs-2.0-11.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jbigkit-libs/2.0/11.el7/x86_64/jbigkit-libs-2.0-11.el7.x86_64.rpm) --2018-09-06 12:07:48-- https://kojipkgs.fedoraproject.org/packages/jbigkit-libs/2.0/11.el7/x86_64/jbigkit-libs-2.0-11.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:49 ERROR 404: Not Found. Warning: jbigkit-libs-2.0-11.el7.x86_64.rpm not found Looking for jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jboss-ejb-3.1-api/1.0.2/10.el7/noarch/jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm) --2018-09-06 12:07:49-- https://kojipkgs.fedoraproject.org/packages/jboss-ejb-3.1-api/1.0.2/10.el7/noarch/jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:50 ERROR 404: Not Found. Warning: jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm not found Looking for jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jboss-el-2.2-api/1.0.1/0.7.20120212git2fabd8.el7/noarch/jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm) --2018-09-06 12:07:50-- https://kojipkgs.fedoraproject.org/packages/jboss-el-2.2-api/1.0.1/0.7.20120212git2fabd8.el7/noarch/jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:51 ERROR 404: Not Found. Warning: jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm not found Looking for jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jboss-interceptors-1.1-api/1.0.2/0.9.20120319git49a904.el7/noarch/jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm) --2018-09-06 12:07:51-- https://kojipkgs.fedoraproject.org/packages/jboss-interceptors-1.1-api/1.0.2/0.9.20120319git49a904.el7/noarch/jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:52 ERROR 404: Not Found. Warning: jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm not found Looking for jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jboss-jaxrpc-1.1-api/1.0.1/7.el7/noarch/jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm) --2018-09-06 12:07:52-- https://kojipkgs.fedoraproject.org/packages/jboss-jaxrpc-1.1-api/1.0.1/7.el7/noarch/jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:53 ERROR 404: Not Found. Warning: jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm not found Looking for jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jboss-servlet-3.0-api/1.0.1/9.el7/noarch/jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm) --2018-09-06 12:07:53-- https://kojipkgs.fedoraproject.org/packages/jboss-servlet-3.0-api/1.0.1/9.el7/noarch/jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:54 ERROR 404: Not Found. Warning: jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm not found Looking for jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jboss-transaction-1.1-api/1.0.1/8.el7/noarch/jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm) --2018-09-06 12:07:54-- https://kojipkgs.fedoraproject.org/packages/jboss-transaction-1.1-api/1.0.1/8.el7/noarch/jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:55 ERROR 404: Not Found. Warning: jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm not found Looking for jline-1.0-8.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jline/1.0/8.el7/noarch/jline-1.0-8.el7.noarch.rpm) --2018-09-06 12:07:55-- https://kojipkgs.fedoraproject.org/packages/jline/1.0/8.el7/noarch/jline-1.0-8.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:57 ERROR 404: Not Found. Warning: jline-1.0-8.el7.noarch.rpm not found Looking for jomolhari-fonts-0.003-17.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jomolhari-fonts/0.003/17.el7/noarch/jomolhari-fonts-0.003-17.el7.noarch.rpm) --2018-09-06 12:07:57-- https://kojipkgs.fedoraproject.org/packages/jomolhari-fonts/0.003/17.el7/noarch/jomolhari-fonts-0.003-17.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:58 ERROR 404: Not Found. Warning: jomolhari-fonts-0.003-17.el7.noarch.rpm not found Looking for js-1.8.5-19.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/js/1.8.5/19.el7/x86_64/js-1.8.5-19.el7.x86_64.rpm) --2018-09-06 12:07:58-- https://kojipkgs.fedoraproject.org/packages/js/1.8.5/19.el7/x86_64/js-1.8.5-19.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:07:59 ERROR 404: Not Found. Warning: js-1.8.5-19.el7.x86_64.rpm not found Looking for jsch-0.1.50-5.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jsch/0.1.50/5.el7/noarch/jsch-0.1.50-5.el7.noarch.rpm) --2018-09-06 12:07:59-- https://kojipkgs.fedoraproject.org/packages/jsch/0.1.50/5.el7/noarch/jsch-0.1.50-5.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:00 ERROR 404: Not Found. Warning: jsch-0.1.50-5.el7.noarch.rpm not found Looking for json-c-0.11-4.el7_0.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/json-c/0.11/4.el7_0/x86_64/json-c-0.11-4.el7_0.x86_64.rpm) --2018-09-06 12:08:00-- https://kojipkgs.fedoraproject.org/packages/json-c/0.11/4.el7_0/x86_64/json-c-0.11-4.el7_0.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:01 ERROR 404: Not Found. Warning: json-c-0.11-4.el7_0.x86_64.rpm not found Looking for json-c-devel-0.11-4.el7_0.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/json-c-devel/0.11/4.el7_0/x86_64/json-c-devel-0.11-4.el7_0.x86_64.rpm) --2018-09-06 12:08:01-- https://kojipkgs.fedoraproject.org/packages/json-c-devel/0.11/4.el7_0/x86_64/json-c-devel-0.11-4.el7_0.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:02 ERROR 404: Not Found. Warning: json-c-devel-0.11-4.el7_0.x86_64.rpm not found Looking for json-glib-1.2.6-1.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/json-glib/1.2.6/1.el7/x86_64/json-glib-1.2.6-1.el7.x86_64.rpm) --2018-09-06 12:08:02-- https://kojipkgs.fedoraproject.org/packages/json-glib/1.2.6/1.el7/x86_64/json-glib-1.2.6-1.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:03 ERROR 404: Not Found. Warning: json-glib-1.2.6-1.el7.x86_64.rpm not found Looking for json-glib-devel-1.2.6-1.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/json-glib-devel/1.2.6/1.el7/x86_64/json-glib-devel-1.2.6-1.el7.x86_64.rpm) --2018-09-06 12:08:04-- https://kojipkgs.fedoraproject.org/packages/json-glib-devel/1.2.6/1.el7/x86_64/json-glib-devel-1.2.6-1.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:05 ERROR 404: Not Found. Warning: json-glib-devel-1.2.6-1.el7.x86_64.rpm not found Looking for jsoup-1.6.1-10.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jsoup/1.6.1/10.el7/noarch/jsoup-1.6.1-10.el7.noarch.rpm) --2018-09-06 12:08:05-- https://kojipkgs.fedoraproject.org/packages/jsoup/1.6.1/10.el7/noarch/jsoup-1.6.1-10.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:06 ERROR 404: Not Found. Warning: jsoup-1.6.1-10.el7.noarch.rpm not found Looking for julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/julietaula-montserrat-fonts/7.200/1.el7/noarch/julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm) --2018-09-06 12:08:06-- https://kojipkgs.fedoraproject.org/packages/julietaula-montserrat-fonts/7.200/1.el7/noarch/julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:07 ERROR 404: Not Found. Warning: julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm not found Looking for junit-4.11-8.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/junit/4.11/8.el7/noarch/junit-4.11-8.el7.noarch.rpm) --2018-09-06 12:08:08-- https://kojipkgs.fedoraproject.org/packages/junit/4.11/8.el7/noarch/junit-4.11-8.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:09 ERROR 404: Not Found. Warning: junit-4.11-8.el7.noarch.rpm not found Looking for jzlib-1.1.1-6.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/jzlib/1.1.1/6.el7/noarch/jzlib-1.1.1-6.el7.noarch.rpm) --2018-09-06 12:08:09-- https://kojipkgs.fedoraproject.org/packages/jzlib/1.1.1/6.el7/noarch/jzlib-1.1.1-6.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:10 ERROR 404: Not Found. Warning: jzlib-1.1.1-6.el7.noarch.rpm not found Looking for kbd-1.15.5-13.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/kbd/1.15.5/13.el7/x86_64/kbd-1.15.5-13.el7.x86_64.rpm) --2018-09-06 12:08:10-- https://kojipkgs.fedoraproject.org/packages/kbd/1.15.5/13.el7/x86_64/kbd-1.15.5-13.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:11 ERROR 404: Not Found. Warning: kbd-1.15.5-13.el7.x86_64.rpm not found Looking for kbd-legacy-1.15.5-13.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/kbd-legacy/1.15.5/13.el7/noarch/kbd-legacy-1.15.5-13.el7.noarch.rpm) --2018-09-06 12:08:11-- https://kojipkgs.fedoraproject.org/packages/kbd-legacy/1.15.5/13.el7/noarch/kbd-legacy-1.15.5-13.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:12 ERROR 404: Not Found. Warning: kbd-legacy-1.15.5-13.el7.noarch.rpm not found Looking for kbd-misc-1.15.5-13.el7.noarch.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/kbd-misc/1.15.5/13.el7/noarch/kbd-misc-1.15.5-13.el7.noarch.rpm) --2018-09-06 12:08:12-- https://kojipkgs.fedoraproject.org/packages/kbd-misc/1.15.5/13.el7/noarch/kbd-misc-1.15.5-13.el7.noarch.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:13 ERROR 404: Not Found. Warning: kbd-misc-1.15.5-13.el7.noarch.rpm not found Looking for kde-filesystem-4-47.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/kde-filesystem/4/47.el7/x86_64/kde-filesystem-4-47.el7.x86_64.rpm) --2018-09-06 12:08:13-- https://kojipkgs.fedoraproject.org/packages/kde-filesystem/4/47.el7/x86_64/kde-filesystem-4-47.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:14 ERROR 404: Not Found. Warning: kde-filesystem-4-47.el7.x86_64.rpm not found Looking for keepalived-1.3.5-6.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/keepalived/1.3.5/6.el7/x86_64/keepalived-1.3.5-6.el7.x86_64.rpm) --2018-09-06 12:08:14-- https://kojipkgs.fedoraproject.org/packages/keepalived/1.3.5/6.el7/x86_64/keepalived-1.3.5-6.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-09-06 12:08:15 ERROR 404: Not Found. Warning: keepalived-1.3.5-6.el7.x86_64.rpm not found Looking for kernel-headers-3.10.0-862.6.3.el7.x86_64.rpm... --> run: wget https://kojipkgs.fedoraproject.org/packages/kernel-headers/3.10.0/862.6.3.el7/x86_64/kernel-headers-3.10.0-862.6.3.el7.x86_64.rpm) --2018-09-06 12:08:16-- https://kojipkgs.fedoraproject.org/packages/kernel-headers/3.10.0/862.6.3.el7/x86_64/kernel-headers-3.10.0-862.6.3.el7.x86_64.rpm) Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. HTTP request sent, awaiting response... ^C -------------- next part -------------- An HTML attachment was scrubbed... URL: From kailun.qin at intel.com Thu Sep 6 14:09:24 2018 From: kailun.qin at intel.com (Qin, Kailun) Date: Thu, 6 Sep 2018 14:09:24 +0000 Subject: [Starlingx-discuss] Questions about StarlingX OVS-DPDK firewall driver enhancement Message-ID: Hi Matt, We are doing some ground work for https://storyboard.openstack.org/#!/story/2002944 regarding the StarlingX OVS-DPDK firewall driver enhancement. To better understand the requirement, we may need your help on the following question. There are 3 security group implementations in neutron OVS-DPDK agent. 1. Iptables based security group The OVS agent and Compute service use a Linux bridge between each instance (VM) and the OVS integration bridge br-int to implement security groups. This implementation is stateful but cause scalability and performance problems. 2. Openflow based security group This implementation is stateless and based in OpenFlow 'learn action', which uses a firewall driver in networking-ovs-dpdk project. https://github.com/openstack/networking-ovs-dpdk/blob/master/networking_ovs_dpdk/agent/ovs_dpdk_firewall.py 3. Openflow + conntrack based security group This implementation is stateful, which uses a native firewall driver. https://docs.openstack.org/newton/networking-guide/config-ovsfwdriver.html http://docs.openvswitch.org/en/latest/tutorials/ovs-conntrack/ The requirement from the enhancement description is that we're going to adopt implementation option 2 for StarlingX OVS-DPDK security group. Compared with option 3 which is stateful and uses a native firewall driver, what is our consideration on taking option 2 as our target? Please kindly see the attached doc for further details. Just let me know if anything unclear. Thanks a lot! BR, Kailun -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Neutron OVSDPDK + Security Group.pdf Type: application/pdf Size: 47866 bytes Desc: Neutron OVSDPDK + Security Group.pdf URL: From Greg.Waines at windriver.com Thu Sep 6 14:27:48 2018 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 6 Sep 2018 14:27:48 +0000 Subject: [Starlingx-discuss] Requesting suggestions for Berlin / Stein OpenStack Summit Forum topics from StarlingX Team Message-ID: <8F3DE5D5-0B6D-477A-92B8-47F4156FBA49@windriver.com> I am gathering potential Topics for ‘Forum’ sessions at the Berlin / Stein OpenStack Summit, from the StarlingX Team. If you are not familiar with ‘Forum’ sessions at the Summit, see end of email. I have done some initial brainstorming with the StarlingX Architecture Team to start things off. See the following etherpad: https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming Please either email me directly or update the etherpad at bottom (with your name/email) with any ‘Forum’ –type topics that you would like to see considered for the Berlin / Stein OpenStack Summit. Greg. p.s. If you're not familiar with the Forum, the quick summary is a collaboration between various teams to help identify problems, ideas, and needs for future development. It's comprised of rooms set up in fishbowl/conversational style, unlike the formal presentations of the OpenStack Summit. It's been instrumental in helping OpenStack developers set the course for the coming development cycle, and we hope it's a format that will work well for StarlingX as well. Examples of typical sessions that make for a great Forum: · Strategic, whole-of-community discussions, to think about the big picture, including beyond just one release cycle and new technologies o eg Making OpenStack One Platform for containers/VMs/Bare Metal (Strategic session) the entire community congregates to share opinions on how to make OpenStack achieve its integration engine goal · Cross-project sessions, in a similar vein to what has happened at past forums, but with increased emphasis on issues that are of relevant to all areas of the community o eg Rolling Upgrades at Scale (Cross-Project session) – the Large Deployments Team collaborates with Nova, Cinder and Keystone to tackle issues that come up with rolling upgrades when there’s a large number of machines. · Project-specific sessions, where community members most interested in a specific project can discuss their experience with the project over the last release and provide feedback, collaborate on priorities, and present or generate 'blue sky' ideas for the next release o eg Neutron Pain Points (Project-Specific session) – Co-organized by neutron developers and users. Neutron developers bring some specific questions about implementation and usage. Neutron users bring feedback from the latest release. All community members interested in Neutron discuss ideas about the future. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Sep 6 15:33:11 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 6 Sep 2018 15:33:11 +0000 Subject: [Starlingx-discuss] Launchpad team created for Bug Triage Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4500A5@ALA-MBD.corp.ad.wrs.com> Hello all, I have created a launchpad team that has privileges as the Bug Supervisor for StarlingX. https://launchpad.net/~stx-bugs Members of this team have privileges to do the following: - Mark a bug as triaged - Assign a bug to someone - Assign a milestone to a bug (future ...we're not using milestones yet) The Project Leads of each sub-team should join this team. I have added the people I found on Launchpad already. Regards, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Thu Sep 6 17:00:01 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 6 Sep 2018 17:00:01 +0000 Subject: [Starlingx-discuss] Developer Guide / build failures In-Reply-To: <9700A18779F35F49AF027300A49E7C7655356F70@SHSMSX101.ccr.corp.intel.com> References: <42b787ac2c187c5ec28196b26bc91587@optimcloud.com> <9700A18779F35F49AF027300A49E7C7655356F70@SHSMSX101.ccr.corp.intel.com> Message-ID: <700dabf803130a958676d0dcbff8b6a081cadf20.camel@intel.com> Hi, I'm sorry you are still having problems to build, however this is progress and you are almost in a complete build :) > 17:37:53 Recreate repodata > 17:38:07 > 17:38:07 Failed to build packages: integrity-kmod-4.12- > 0.tis.5.src.rpm > > ######## Wed Sep 5 17:38:07 UTC 2018: build-rpm-parallel --std failed > with rc=1 > integrity-kmod failed in your build, now you'll need to debug on why you get that failure. If you go into /localdisk/loadbuild///std you'll see all the artifacts and logs created by the std (standard) stage of the build. Inside that folder, if you go into results/--tis-r5- pike-std, you'll see all the building logs for each generated rpm. Look for the integrity-kmod-4.12-0.tis.5 folder and the build.log file. Please share the content of that file. This is just a guest, but probably the integrity-kmod-e6aef069.tar.gz was corrupted in the download. you can try to download again (just that file, manually) and then run: build-pkgs --clean integrity-kmod build-pkgs integrity-kmod and see if that solves the problem. My integrity-kmod has this MD5: ee4c39a91c507482832718f174e73814 > Wed Sep 5 17:38:07 UTC 2018: build-rpm-parallel --std failed with > rc=1 > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Thu Sep 6 17:03:04 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 6 Sep 2018 17:03:04 +0000 Subject: [Starlingx-discuss] Command line error: no such option: --arcgglist In-Reply-To: <9700A18779F35F49AF027300A49E7C76553570D5@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76553570AB@SHSMSX101.ccr.corp.intel.com> <3296850131893933794b3ac9f351cfa2@optimcloud.com> <9700A18779F35F49AF027300A49E7C76553570D5@SHSMSX101.ccr.corp.intel.com> Message-ID: Hi, In this review[0] we did a refactor on that file and that issue is solved. Meanwhile is not integrated you can checkout that change with: - After git pull to get the latest master: git fetch https://git.openstack.org/openstack/stx-tools refs/changes/52/600252/1 && git cherry-pick FETCH_HEAD I hope this helps -Erich [0] https://review.openstack.org/#/c/600252/ On Thu, 2018-09-06 at 12:23 +0000, Lin, Shuicheng wrote: > I guess there is something wrong with latest mirror script. > The packages you list here, should be download from centos repo after > you correct the script. > Only the packages cannot get from repo will try to use koji. And I am > not sure why below link is not correct. > > To quick workaround it, please revert below change in build-tools: > “read releasever from yum.conf iff -c yum.conf is set” > > Best Regards > Shuicheng > > From: scottk at optimcloud.com [mailto:scottk at optimcloud.com] > Sent: Thursday, September 6, 2018 8:08 PM > To: Lin, Shuicheng ; starlingx-discuss at lists > .starlingx.io > Subject: Re: [Starlingx-discuss] Command line error: no such option: > --arcgglist > > I am also recieving this continuously, like nothing in the list even > exists and is a 404... how is that possible? > > > arning: gsm-1.0.13-11.el7.x86_64.rpm not found > Looking for gstreamer-0.10.36-7.el7.x86_64.rpm... > --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer/0 > .10.36/7.el7/x86_64/gstreamer-0.10.36-7.el7.x86_64.rpm) > --2018-09-06 12:06:35-- https://kojipkgs.fedoraproject.org/packages/g > streamer/0.10.36/7.el7/x86_64/gstreamer-0.10.36-7.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:06:36 ERROR 404: Not Found. > > Warning: gstreamer-0.10.36-7.el7.x86_64.rpm not found > Looking for gstreamer-plugins-base-0.10.36-10.el7.x86_64.rpm... > --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer-p > lugins-base/0.10.36/10.el7/x86_64/gstreamer-plugins-base-0.10.36- > 10.el7.x86_64.rpm) > --2018-09-06 12:06:36-- https://kojipkgs.fedoraproject.org/packages/g > streamer-plugins-base/0.10.36/10.el7/x86_64/gstreamer-plugins-base- > 0.10.36-10.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:06:37 ERROR 404: Not Found. > > Warning: gstreamer-plugins-base-0.10.36-10.el7.x86_64.rpm not found > Looking for gstreamer-plugins-good-0.10.31-13.el7.x86_64.rpm... > --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer-p > lugins-good/0.10.31/13.el7/x86_64/gstreamer-plugins-good-0.10.31- > 13.el7.x86_64.rpm) > --2018-09-06 12:06:37-- https://kojipkgs.fedoraproject.org/packages/g > streamer-plugins-good/0.10.31/13.el7/x86_64/gstreamer-plugins-good- > 0.10.31-13.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:06:38 ERROR 404: Not Found. > > Warning: gstreamer-plugins-good-0.10.31-13.el7.x86_64.rpm not found > Looking for gstreamer-tools-0.10.36-7.el7.x86_64.rpm... > --> run: wget https://kojipkgs.fedoraproject.org/packages/gstreamer-t > ools/0.10.36/7.el7/x86_64/gstreamer-tools-0.10.36-7.el7.x86_64.rpm) > --2018-09-06 12:06:38-- https://kojipkgs.fedoraproject.org/packages/g > streamer-tools/0.10.36/7.el7/x86_64/gstreamer-tools-0.10.36- > 7.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:06:39 ERROR 404: Not Found. > > Warning: gstreamer-tools-0.10.36-7.el7.x86_64.rpm not found > Looking for gtk2-2.24.31-1.el7.x86_64.rpm... > --> run: wget https://kojipkgs.fedoraproject.org/packages/gtk2/2.24.3 > 1/1.el7/x86_64/gtk2-2.24.31-1.el7.x86_64.rpm) > --2018-09-06 12:06:39-- https://kojipkgs.fedoraproject.org/packages/g > tk2/2.24.31/1.el7/x86_64/gtk2-2.24.31-1.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:06:40 ERROR 404: Not Found. > > > September 6, 2018 1:59 PM, "Lin, Shuicheng" > wrote: > > Hi, > > This is a code error. > > Please change the “arcgglist” to “archlist”. > > slin14 at slin14-nuc2:~/GIT/stx-tools$ git diff > > diff --git a/centos-mirror-tools/dl_rpms.sh b/centos-mirror- > > tools/dl_rpms.sh > > index 67cf792..09f6751 100755 > > --- a/centos-mirror-tools/dl_rpms.sh > > +++ b/centos-mirror-tools/dl_rpms.sh > > @@ -220,7 +220,7 @@ download () { > > download_cmd="${SUDOCMD} yumdownloader -q ${YUMCONFOPT} > > ${RELEASEVER} -C --source $SFILE" > > download_url_cmd="${SUDOCMD} yumdownloader --urls -q ${YUMCONFOPT} > > ${RELEASEVER} -C --source $SFILE" > > else > > - download_cmd="${SUDOCMD} yumdownloader -q -C ${YUMCONFOPT} > > ${RELEASEVER} $SFILE --arcgglist=noarch,x86_64" > > + download_cmd="${SUDOCMD} yumdownloader -q -C ${YUMCONFOPT} > > ${RELEASEVER} $SFILE --archlist=noarch,x86_64" > > download_url_cmd="${SUDOCMD} yumdownloader --urls -q -C > > ${YUMCONFOPT} ${RELEASEVER} $SFILE --archlist=noarch,x86_64" > > fi > > fi > > Best Regards > > Shuicheng > > From: scottk at optimcloud.com [mailto:scottk at optimcloud.com] > > Sent: Thursday, September 6, 2018 6:18 PM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] Command line error: no such option: -- > > arcgglist > > so trying this a fifth time, i see the following errors numerous > > times for various packages during the bash download_mirror.sh phase > > of the process as documented > > in > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > Warning: infinipath-psm-3.3-26_g604758e_open.2.el7.x86_64.rpm not > > found > > ------ using info-5.1-4.el7 to search info-5.1-4.el7.x86_64.rpm - > > ----- > > Looking for info-5.1-4.el7.x86_64.rpm... > > --> run: sudo -E yumdownloader -q -C --releasever=7 info-5.1-4.el7 > > --arcgglist=noarch,x86_64 > > Command line error: no such option: --arcgglist > > Usage: "yumdownloader [options] package1 [package2] [package..] > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Thu Sep 6 18:12:10 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 6 Sep 2018 13:12:10 -0500 Subject: [Starlingx-discuss] [distcloud] The Distributed Cloud repos are up Message-ID: The DC repos (stx-distcloud[0] and stx-distcloud-client[1]) are alive in Gerrit. There is one review in each repo to get the basic Gerrit/Zuul functionality working [2][3]. Once those are merged we can change the master manifest to pull these from Gerrit, then I will rename the repos in starlingx-staging to make them fail in outdated configurations followed by eventual removal. We should now consider the DC staging repos to be read-only, any further commits there will be lost. I did hack on tox.ini in both to get working linters and pep8 tests, some repair will likely be necessary to restore the others. There are some hard-coded paths that I hope can be made ignorable for CI testing. dt [0] https://git.starlingx.io/cgit/stx-distcloud/ [1] https://git.starlingx.io/cgit/stx-distcloud-client/ [2] https://review.openstack.org/600488 [3] https://review.openstack.org/600492 -- Dean Troyer dtroyer at gmail.com From elio.martinez.monroy at intel.com Thu Sep 6 22:41:56 2018 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Thu, 6 Sep 2018 22:41:56 +0000 Subject: [Starlingx-discuss] Centos 7.05 Update Status Message-ID: <1466AF2176E6F040BD63860D0A241BBD1ED5408A@FMSMSX109.amr.corp.intel.com> Hello guys, Just sharing latest status for StarlingX update for Centos7.05 The following report reflects about the 90% of the update progress Our Sanity Test Results ./runner.py --run-suite Setup ============================================================================== Setup :: Tests for Install and Configuration of a controller node. ============================================================================== Test Qemu Libvirt VMs Setup :: Test Qemu-Libvirt VMs setup and con... | PASS | ------------------------------------------------------------------------------ Test GRUB Checker For vBIOS :: Check grub cmd boot line against th... | PASS | ------------------------------------------------------------------------------ Test Install ISO :: Test installation on controller node and defin... | PASS | ------------------------------------------------------------------------------ Test Config Controller :: Configure controller with specified conf... | PASS | ------------------------------------------------------------------------------ Setup :: Tests for Install and Configuration of a controller node. | PASS | 4 critical tests, 4 passed, 0 failed 4 tests total, 4 passed, 0 failed ./runner.py --run-suite Sanity-Test ============================================================================== Sanity-Test ============================================================================== Sanity-Test.01-Controller-Unlock-Provisioning :: Test for provisioning and ... ============================================================================== Test_Unlock_Master_Controller :: Validates that master controller ... | PASS | ------------------------------------------------------------------------------ Test_Install_And_Unlock_Second_Controller :: Validates that second... | PASS | ------------------------------------------------------------------------------ Test_Add_Computes_To_Inventory :: Validates that computes are adde... | PASS | ------------------------------------------------------------------------------ Test_Provisioning_Computes :: Validate that provisioning is perfor... | PASS | ------------------------------------------------------------------------------ Sanity-Test.01-Controller-Unlock-Provisioning :: Test for provisio... | PASS | 4 critical tests, 4 passed, 0 failed 4 tests total, 4 passed, 0 failed ============================================================================== Sanity-Test.Centos-Instance :: Test to create an instance with CentOS. ============================================================================== Launch Centos Instance :: Launch a CentOS instance. | PASS | ------------------------------------------------------------------------------ Suspend Resume Centos Instance :: Suspend and Resume CentOS instance. | PASS | ------------------------------------------------------------------------------ Set Error Active Flags Centos Instance :: Set 'Error' and 'Active'... | PASS | ------------------------------------------------------------------------------ Evacuate Instances From Computes :: Evacuate all instances from Co... | PASS | ------------------------------------------------------------------------------ Sanity-Test.Centos-Instance :: Test to create an instance with Cen... | PASS | 4 critical tests, 4 passed, 0 failed 4 tests total, 4 passed, 0 failed ============================================================================== Sanity-Test.Cirros-Instance :: Test to create an instance with Cirros. ============================================================================== Launch Cirros Instance :: Launch a Cirros instance. | PASS | ------------------------------------------------------------------------------ Suspend Resume Cirros Instance :: Suspend and Resume Cirros instance. | PASS | ------------------------------------------------------------------------------ Set Error Active Flags Cirros Instance :: Set 'Error' and 'Active'... | PASS | ------------------------------------------------------------------------------ Sanity-Test.Cirros-Instance :: Test to create an instance with Cir... | PASS | 3 critical tests, 3 passed, 0 failed 3 tests total, 3 passed, 0 failed ============================================================================== Sanity-Test.Ubuntu-Instance :: Validate different behaviors on created Ubun... ============================================================================== Launch Ubuntu Instance :: Validates that Ubuntu instance can be la... | PASS | ------------------------------------------------------------------------------ Suspend Resume Ubuntu Instance :: Suspend and Resume Ubuntu instance. | PASS | ------------------------------------------------------------------------------ Set Error Active Flags Ubuntu Instance :: Set 'Error' and 'Active'... | PASS | ------------------------------------------------------------------------------ Sanity-Test.Ubuntu-Instance :: Validate different behaviors on cre... | PASS | 3 critical tests, 3 passed, 0 failed 3 tests total, 3 passed, 0 failed ============================================================================== Sanity-Test | PASS | 14 critical tests, 14 passed, 0 failed 14 tests total, 14 passed, 0 failed Attaching Rar file with all logs, I just want to play a little bit more with this ISO and see what I can find. Thanks [cid:image001.png at 01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer. Open-source Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4914 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CentOS7.05_migration_results.rar Type: application/octet-stream Size: 606737 bytes Desc: CentOS7.05_migration_results.rar URL: From shuicheng.lin at intel.com Fri Sep 7 05:32:09 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 7 Sep 2018 05:32:09 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From scottk at optimcloud.com Fri Sep 7 09:10:21 2018 From: scottk at optimcloud.com (scottk at optimcloud.com) Date: Fri, 07 Sep 2018 09:10:21 +0000 Subject: [Starlingx-discuss] Developer Guide / build failures In-Reply-To: <700dabf803130a958676d0dcbff8b6a081cadf20.camel@intel.com> References: <700dabf803130a958676d0dcbff8b6a081cadf20.camel@intel.com> <42b787ac2c187c5ec28196b26bc91587@optimcloud.com> <9700A18779F35F49AF027300A49E7C7655356F70@SHSMSX101.ccr.corp.intel.com> Message-ID: <12e78df0996fb7ff2498eaa3db99ef2c@optimcloud.com> 09:08:57 Setting supported flag to 0 09:09:03 MAKING /localdisk/loadbuild/dingo/starlingx/export/report.txt 09:09:04 ISO REPORT: /localdisk/loadbuild/dingo/starlingx/export/report.txt 09:09:04 Done.Output file: /localdisk/loadbuild/dingo/starlingx/export/bootimage.iso 09:09:04 [dingo at d7d4a6ca3fd1 starlingx]$ seems we now have an iso, time to try to install it September 6, 2018 7:00 PM, "Cordoba Malibran, Erich" wrote: > Hi, > > I'm sorry you are still having problems to build, however this is > progress and you are almost in a complete build :) > >> 17:37:53 Recreate repodata >> 17:38:07 >> 17:38:07 Failed to build packages: integrity-kmod-4.12- >> 0.tis.5.src.rpm >> >> ######## Wed Sep 5 17:38:07 UTC 2018: build-rpm-parallel --std failed >> with rc=1 > > integrity-kmod failed in your build, now you'll need to debug on why > you get that failure. > > If you go into /localdisk/loadbuild///std > you'll see all the artifacts and logs created by the std (standard) > stage of the build. > > Inside that folder, if you go into results/--tis-r5- > pike-std, you'll see all the building logs for each generated rpm. > > Look for the integrity-kmod-4.12-0.tis.5 folder and the build.log file. > Please share the content of that file. > > This is just a guest, but probably the integrity-kmod-e6aef069.tar.gz > was corrupted in the download. you can try to download again (just that > file, manually) and then run: > > build-pkgs --clean integrity-kmod > build-pkgs integrity-kmod > > and see if that solves the problem. My integrity-kmod has this MD5: > ee4c39a91c507482832718f174e73814 > >> Wed Sep 5 17:38:07 UTC 2018: build-rpm-parallel --std failed with >> rc=1 >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scottk at optimcloud.com Fri Sep 7 12:15:19 2018 From: scottk at optimcloud.com (scottk at optimcloud.com) Date: Fri, 07 Sep 2018 12:15:19 +0000 Subject: [Starlingx-discuss] Installation_Guide_Virtual_Environment / Ubuntu Specific Message-ID: <2ad3aa544f22e8e08007dc1e56dc118b@optimcloud.com> ok so, Ive gotten my ISO built finally and decided to move forward, it did actually install and run under kvm on fedora 28, alas it would not let me run i hunted around and got the interface up on dhcp and logged in... sudo config_controller as it requires 4 interfaces to start up so hunted the wiki a bit and found this guide https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment (https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Duplex) where it plainly states Software Requirements A workstation computer with: Operating System: Freshly installed Ubuntu 16.04 LTS 64-bit Proxy settings configured (if applies) Git KVM/VirtManager Libvirt Library QEMU Full System Emulation Binaries project StarlingX ISO Image Deployment Environment Setup This section describes how to set up a StarlingX Controller Storage system in a workstation computer. After completing these steps, you will be able to deploy and run your StarlingX system on the following Linux distribution: Ubuntu 16.04 LTS 64-bit ... Now I have to ask Why.... Seriously? We dont all use Ubuntu... StarlingX isnt even based on Ubuntu.... and you actualy put more effort into making it ubuntu specific then was needed to allow for other hosts operating systems. Okay, any way to proceed i ran networking config, no worries, went to run ./setup_allinone.sh -i bootimage.iso and sorry failed..... read the script... WTF ?? dont need this.... diff -ruN setup_allinone.sh.orig setup_allinone.sh --- setup_allinone.sh.orig 2018-09-07 13:25:06.514256691 +0200 +++ setup_allinone.sh 2018-09-07 13:25:23.148154595 +0200 @@ -28,10 +28,6 @@ ISOIMAGE=$(readlink -f "$ISOIMAGE") FILETYPE=$(file --mime-type -b ${ISOIMAGE}) -if ([ "$FILETYPE" != "application/x-iso9660-image" ]); then - echo "$ISOIMAGE is not an application/x-iso9660-image type" - exit -1 -fi BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr} CONTROLLER=${CONTROLLER:-controller-allinone} edited, run it again, gui pops up ... console says ./setup_allinone.sh -i bootimage.iso   13:36  07.09.18  45.93G RAM Formatting '/var/lib/libvirt/images/controller-allinone-0-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16 Formatting '/var/lib/libvirt/images/controller-allinone-0-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16 error: Failed to define domain from vms/controller-allinone-0.xml error: operation failed: domain 'controller-allinone-0' already exists with uuid 8414049f-c910-4605-a880-05fc8d35b683 error: Failed to start domain controller-allinone-0 error: unsupported configuration: Unable to find security driver for model apparmor Formatting '/var/lib/libvirt/images/controller-allinone-1-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16 Formatting '/var/lib/libvirt/images/controller-allinone-1-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16 error: Failed to define domain from vms/controller-allinone-1.xml error: operation failed: domain 'controller-allinone-1' already exists with uuid f66ed9f5-226b-47ce-ab23-47ee99b2f257 OMG... KILL ME NOW.... edit edit edit ./setup_allinone.sh -i bootimage.iso   13:39  07.09.18  45.88G RAM Formatting '/var/lib/libvirt/images/controller-allinone-0-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16 Formatting '/var/lib/libvirt/images/controller-allinone-0-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16 Domain controller-allinone-0 defined from vms/controller-allinone-0.xml error: Failed to start domain controller-allinone-0 error: internal error: process exited while connecting to monitor: 2018-09-07T11:40:02.994268Z qemu-system-x86_64: -machine pc-i440fx-xenial,accel=kvm,usb=off,dump-guest-core=off: unsupported machine type Use -machine help to list supported machines Formatting '/var/lib/libvirt/images/controller-allinone-1-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16 Formatting '/var/lib/libvirt/images/controller-allinone-1-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16 Domain controller-allinone-1 defined from vms/controller-allinone-1.xml REALLY NOW.... EDIT EDIT EDIT..... ./setup_allinone.sh -i bootimage.iso   13:44  07.09.18  45.86G RAM Formatting '/var/lib/libvirt/images/controller-allinone-0-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16 Formatting '/var/lib/libvirt/images/controller-allinone-0-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16 Domain controller-allinone-0 defined from vms/controller-allinone-0.xml Domain controller-allinone-0 started Formatting '/var/lib/libvirt/images/controller-allinone-1-0.img', fmt=qcow2 size=644245094400 cluster_size=65536 lazy_refcounts=off refcount_bits=16 Formatting '/var/lib/libvirt/images/controller-allinone-1-1.img', fmt=qcow2 size=214748364800 cluster_size=65536 lazy_refcounts=off refcount_bits=16 Domain controller-allinone-1 defined from vms/controller-allinone-1.xml and ... TADA..... functionally working on Fedora 28 and actually installing at this moment..... so... seriously i have to ask.... when do you want to offer me a job..... because this shouldnt be happening..... anyway..... I find it awesome that you used CentOS for the platform, great choice... but why would you force uus to use Ubuntu as the host... personally from an R&D perspective, We all know theres more then one decent desktop distribution. I would alone ask that some attention maybe be paid to making it more distro friendly, because i can almost guarantee I wount be the first one to go down this path. Maybe im ranting a bit... but 5 days to get to this point on something you would like to be considered as a viable openstack platform.... Yes, i understand its development, its always in flux, though I fought to achieve just getting this far.... I am almost positive others wount be as patient, because we all know when a corporation delivers something new and shiny, users well... they just want it to work... and if it doesnt its going to potentially give the distro and the company behind it a black eye.... This is just my observations.... from a senior level management perspective of what Ive seen in the industry... if yyou want to be accepted, I belive you will maybe need more polishh... but so fgar great work, in sight of a few things maybe over looked. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Sep 7 13:36:04 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 7 Sep 2018 13:36:04 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> Thanks Shuicheng. We'll run some tests in Wind River. Numan will be priming this activity. He'll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jason.McKenna at windriver.com Fri Sep 7 14:07:39 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Fri, 7 Sep 2018 14:07:39 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they've moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We'll run some tests in Wind River. Numan will be priming this activity. He'll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Fri Sep 7 14:15:31 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 7 Sep 2018 14:15:31 +0000 Subject: [Starlingx-discuss] Installation_Guide_Virtual_Environment / Ubuntu Specific In-Reply-To: <2ad3aa544f22e8e08007dc1e56dc118b@optimcloud.com> References: <2ad3aa544f22e8e08007dc1e56dc118b@optimcloud.com> Message-ID: Million thanks for your feedback Scott! > ok so, Ive gotten my ISO built finally and decided to move forward, it did > actually install and run under kvm on fedora 28, alas it would not let me run i > hunted around and got the interface up on dhcp and logged in... > > sudo config_controller as it requires 4 interfaces to start up > > so hunted the wiki a bit and found this guide > > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environ > ment > nment/Duplex> Yep! This is the begging of the installation instructions where all setup is described. You will see some changes happening in the next days due to the addition of Bare Metal Installation and once that is done, we will have a team of Tech Writers to polish to a level our community feels comfortable with. > where it plainly states > > Software Requirements > A workstation computer with: > > Operating System: Freshly installed Ubuntu 16.04 LTS 64-bit Proxy settings > configured (if applies) Git KVM/VirtManager Libvirt Library QEMU Full System > Emulation Binaries project StarlingX ISO Image > Deployment Environment Setup This section describes how to set up a > StarlingX Controller Storage system in a workstation computer. After > completing these steps, you will be able to deploy and run your StarlingX > system on the following Linux distribution: > > Ubuntu 16.04 LTS 64-bit > > ... Now I have to ask Why.... Seriously? From the Virtual installation perspective, we wanted one Linux distribution so everyone could be aligned with but this shall not be the only distro to support mid term. We will appreciate also your feedback once we include our Bare Metal installation instructions. > We dont all use Ubuntu... StarlingX isnt even based on Ubuntu.... and you > actualy put more effort into making it ubuntu specific then was needed to > allow for other hosts operating systems. Okay, any way to proceed i ran > networking config, no worries, went to run Some changes has been done at the wiki level to include the setup of network interfaces which was recently added. > and ... TADA..... functionally working on Fedora 28 and actually installing at > this moment..... so... seriously i have to ask.... > > when do you want to offer me a job..... because this shouldnt be > happening..... anyway..... I find it awesome that you used CentOS for the > platform, great choice... > but why would you force uus to use Ubuntu as the host... personally from an > R&D perspective, We all know theres more then one decent desktop > distribution. I would alone ask that some attention maybe be paid to making > it more distro friendly, because i can almost guarantee I wount be the first > one to go down this path. You are the first to ask and this is enough to prioritize and make it more distro friendly. > Maybe im ranting a bit... but 5 days to get to this point on something you > would like to be considered as a viable openstack platform.... Yes, i > understand its development, its always in flux, though I fought to achieve just > getting this far.... I am almost positive others wount be as patient, because we > all know when a corporation delivers something new and shiny, users well... > they just want it to work... and if it doesnt its going to potentially give the > distro and the company behind it a black eye.... That is the goal, and you are helping this community shape it so once again, thank you for taking your time to build, install and feedback. > This is just my observations.... from a senior level management perspective of > what Ive seen in the industry... if yyou want to be accepted, I belive you will > maybe need more polishh... but so fgar great work, in sight of a few things > maybe over looked. All observations are welcome so please allow us to keep this channel open with you to get more of your validation of changes and new observations. From Matt.Peters at windriver.com Fri Sep 7 15:00:53 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Fri, 7 Sep 2018 15:00:53 +0000 Subject: [Starlingx-discuss] Analysis report about Network Trunk feature for StartlingX upstreaming In-Reply-To: <76647BD697F40748B1FA4F56DA02AA0B4D4EDBFE@SHSMSX104.ccr.corp.intel.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D4EB222@SHSMSX104.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB577F1B@fmsmsx115.amr.corp.intel.com> <76647BD697F40748B1FA4F56DA02AA0B4D4EB495@SHSMSX104.ccr.corp.intel.com> <304C67CB-BAE4-4E42-A613-1C848535F166@windriver.com> <76647BD697F40748B1FA4F56DA02AA0B4D4EDBFE@SHSMSX104.ccr.corp.intel.com> Message-ID: See inline for specific responses to the review information. Responses marked with [MP>] From: Le, Huifeng [mailto:huifeng.le at intel.com] Sent: Sunday, August 19, 2018 10:32 PM To: Jolliffe, Ian; Jones, Bruce E; Rowsell, Brent; Peters, Matt Cc: Zhao, Forrest; Troyer, Dean; starlingx-discuss at lists.starlingx.io Subject: RE: Analysis report about Network Trunk feature for StartlingX upstreaming Ian, Thanks very much for the comments. some comments below for you reference, and please help to review, thanks much! Best Regards, Le, Huifeng From: Jolliffe, Ian [mailto:Ian.Jolliffe at windriver.com] Sent: Saturday, August 18, 2018 4:16 AM To: Le, Huifeng ; Jones, Bruce E ; Rowsell, Brent ; Peters, Matt Cc: Zhao, Forrest ; Troyer, Dean ; starlingx-discuss at lists.starlingx.io Subject: Re: Analysis report about Network Trunk feature for StartlingX upstreaming Hi Huifeng; Thanks for the updates/analysis, comments below. Ian Ian/Brent/Matt, We did analysis about the Network trunk related patches for StartingX upstream, below are the suggestions for upstreaming, could you please help to review and comment? Thanks much! 1. ba9d9f60a7a2665194cacb92a05e0acd2dc3de41: Add rpc notification for trunk updates Function: sent notification to the agent when a trunk is updated Analysis: (1)Trunk’s AFTER_UPDATE event is generated for API call: PUT /v2.0/trunks/{trunk-id} The update request is only for changing fields like name, description or admin_state_up. Setting the admin_state_up to False locks the trunk in that it prevents operations such as adding/removing subports. In Neutron upstream, admin_state_up is used in server side, e.g. add_subports, remove subports, delete_trunk and not used in agent side (2)OVS trunk agent driver uses OVSDB event to handle trunk event, no need to manually trigger trunk update event (3)Linux trunk agent driver will handle trunk update event triggered by server, while it will need apply the patch only in case admin_state_up update need to be handled Suggestion: Not a bug for Neutron upstream, suggest not to upstream If this is not upstreamed, are the dependencies or changes required in the StarlingX code base? What are the implications of not upstreaming? [hle2] for STX, trunk_updated event will force the trunk’s parent-port to refresh (e.g. handle_trunks->mark_port_for_refresh(trunk['port_id']) etc.) to get the new “admin_state_up” value from server and this value will be used in handle_updated_port() to determine whether it is allowed to update port/device status in server side. “admin_state_up” is mainly used to control operation at neutron server side like add_subports, remove subports, delete_trunk etc. and all these 3 operations will force port to refresh (handle_trunks/handle_subports->mark_port_for_refresh), so suppose, the general flow will not be impacted whether to handle trunk_updated event or not. But in some wired cases, add “admin_state_up” check in agent side may cause issues (please help to review whether it is make sense), e.g for below calling flow (suppose trunk’s ‘admin_state_up’ is ‘up’): (1) add_subports (2) set “admin_state_up” to ‘down’, step(1) may fail to set device’s state at agent side in case aws agent’s handle_updated_port() (in daemon loop) executed after step (2) So to my understanding: (1) if using OVS agent in STX, no impact for not upstream (2) if using AVS agent + STX, suggest removing “admin_state_up” check in AVS agent (in function handle_updated_port () of avs/agent.py) like below. if trunk_details and trunk_details['admin_state_up']: … [MP>] Thanks for the detailed analysis. The suggested change will need to be tested to see if it full resolves the original issue. However, since the driver could be used by other agents (beyond just the AVS agent), I think it would not hurt to have the additional notification sent to complete the driver definition for the set of RPC notifications. 2. 6955351c5eca6e37061fb0140d11ea53693fe0e1: Add support to delete bound network Function: enable delete trunk if it is can_be_trunked (not bounded or driver’s can_trunk_bound_port=true) Analysis: Applied for LinuxBridge Driver and AVS bridge Driver (can_trunk_bound_port=True), no impact for OVSTrunkDriver (can_trunk_bound_port=False). workaround also available for linux bridge (e.g. unbind the port first then delete the trunk) Suggestion: it is a low priority bug for Neutron upstream (only applied for linux bridge and workround available), suggest not to upstream I think you need to propose a fix. Or this will need to be carried long term. [hle2] yes, let’s try to propose a fix for upstream. [MP>] Agree. 3. 43a684946e781a25d21a4f50b8dc67d61be42809: Enable trunk service by default Function: add “trunk” in DEFAULT_SERVICE_PLUGINS Analysis: It is a deploy configuration for downstream product Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. 4. c54d804792f10b7f505de6794274c4df4768f6f0: Include trunk presence in port details Function: add trunk_port (bool) flag in port_details to identify whether this port is a parent port for a trunk Analysis: It is a performance improvement for AVS agent by reducing RPC call from agent to server. OVS agent has different implementation with no improvement by introducing this field Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. 5. 3eed837ebd236e6b1959ea88d9ab5322c9eef6b9: Ignore trunk subports on same vlan as vlan-subnet ports Function: Ignore trunk subports on same vlan as vlan-subnet ports Analysis: It is a bug fix for AVS agent Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From dehao.shang at intel.com Fri Sep 7 15:09:16 2018 From: dehao.shang at intel.com (Shang, Dehao) Date: Fri, 7 Sep 2018 15:09:16 +0000 Subject: [Starlingx-discuss] restapi-doc source code building Message-ID: <71AECFE5078153419EB7B8DBE0644B263863654B@shsmsx102.ccr.corp.intel.com> Hi: At these days, i setup new environments and am building new starlingx image. When running build-pkgs, one source code repo called restapt-doc can't be normally build. At previous, I ever build successfully restapt-doc package. Compare previous version and current version, I found some new commits. I don't know whether these new commit cause building fails. I also check $MY_WORKSPACE/std/results/dehao-starlingx-tis-r5-pike-std/restapi-doc-1.9.1-27.tis/root.log, everythings seem normal. But $MY_WORKSPACE/std/results/dehao-starlingx-tis-r5-pike-std/restapi-doc-1.9.1-27.tis/build.log, it show some error, and I can't understand these error cause. The following shows log file and new commits. . Thanks Dehao ==================== $MY_WORKSPACE/std/results/dehao-starlingx-tis-r5-pike-std/restapi-doc-1.9.1-27.tis/root.log mvn clean generate-sources -o -Dmaven.repo.local=./mvn.repo/ [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] parent-pom [INFO] Titanium Cloud API Complete Reference [INFO] Titanium REST API Reference Guide [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building parent-pom 1.0.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ parent-pom --- [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] parent-pom ........................................ FAILURE [0.065s] [INFO] Titanium Cloud API Complete Reference ............. SKIPPED [INFO] Titanium REST API Reference Guide ................. SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.160s [INFO] Finished at: Fri Sep 07 06:37:11 UTC 2018 [INFO] Final Memory: 14M/964M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.4.1:clean (default-clean) on project parent-pom: Execution default-clean of goal org.apache.maven.plugins:maven-clean-plugin:2.4.1:clean failed: Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to collect dependencies for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1 (): Failed to read artifact descriptor for org.apache.maven:maven-plugin-api:jar:2.0.6: The repository system is offline but the artifact org.apache.maven:maven-parent:pom:5 is not available in the local repository. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException BUILDSTDERR: make: *** [build] Error 1 RPM build errors: BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.cFbbrh (%build) BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.cFbbrh (%build) Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line 96, in trace result = func(*args, **kw) File "/usr/lib/python2.7/site-packages/mockbuild/util.py", line 634, in do raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode) Error: Command failed: # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/restapi-doc.spec ======================= commit 7b86cd14dfed473780befe2e5f7d2e4749751037 Author: Andreas Jaeger Date: Wed Sep 5 20:33:52 2018 +0200 Add explicit noop gate job This repo defines jobs in check queue, so we can remove the noop-jobs template usage from project-config. To allow that, add a noop job to gate queue. Change-Id: Ie204c40291c17365887793bb5f114652fa24b360 commit 73c7dbc0aec99563d42fee2432e5ad5c33377157 Merge: 8e60299 a98bf51 Author: Zuul Date: Wed Sep 5 15:38:58 2018 +0000 Merge "Remove OCF script code to monitor I/F status" commit a98bf512c4907e05c62188bdff8fbf6510f4656c Author: Bin Qian Date: Tue Sep 4 13:44:27 2018 -0400 Remove OCF script code to monitor I/F status Remove OCF script code to monitor I/F status and fail the service when the I/F is down. On the other change, the monitor work is done by SM, to perform swact based on healthy state of both controllers. Depends: Ifa7453136f34768b99e2bcd741d1065e69ef452e Story: 2003577 Task: 24900 Change-Id: Ie3da54940054ef5c1880dae718272be1663026d8 Signed-off-by: Bin Qian -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Sep 7 16:06:59 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 7 Sep 2018 12:06:59 -0400 Subject: [Starlingx-discuss] ALL kojipkgs.fedoraproject.org 404 Not Found In-Reply-To: References: Message-ID: <06d8ee7b-c4bd-5ceb-ec6d-657c307af14a@windriver.com> kojipkgs.fedoraproject.org as a best effort fallback when the primary source for the rpm has failed. It's not guaranteed to have the package we seek, and 404's are not unexpected. What IS unexpected is that so many packages have gone missing from the primary sources.  Some transient server or network issues? I see from other posts that you eventually succeeded in building an ISO.  I assume you reran download_mirror.sh and succeeded based on primary sources? Scott On 18-09-06 08:15 AM, scottk at optimcloud.com wrote: > > seems also ALL kojipkgs.fedoraproject.org based packages resumt in a > 404 Not Found > > Warning: ipa-pmincho-fonts-003.03-5.el7.noarch.rpm not found > Looking for iperf3-3.1.7-2.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/iperf3/3.1.7/2.el7/x86_64/iperf3-3.1.7-2.el7.x86_64.rpm) > --2018-09-06 12:07:28-- > https://kojipkgs.fedoraproject.org/packages/iperf3/3.1.7/2.el7/x86_64/iperf3-3.1.7-2.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:29 ERROR 404: Not Found. > > Warning: iperf3-3.1.7-2.el7.x86_64.rpm not found > Looking for ipmitool-1.8.18-7.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/ipmitool/1.8.18/7.el7/x86_64/ipmitool-1.8.18-7.el7.x86_64.rpm) > --2018-09-06 12:07:29-- > https://kojipkgs.fedoraproject.org/packages/ipmitool/1.8.18/7.el7/x86_64/ipmitool-1.8.18-7.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:30 ERROR 404: Not Found. > > Warning: ipmitool-1.8.18-7.el7.x86_64.rpm not found > Looking for iproute-3.10.0-74.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/iproute/3.10.0/74.el7/x86_64/iproute-3.10.0-74.el7.x86_64.rpm) > --2018-09-06 12:07:30-- > https://kojipkgs.fedoraproject.org/packages/iproute/3.10.0/74.el7/x86_64/iproute-3.10.0-74.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:31 ERROR 404: Not Found. > > Warning: iproute-3.10.0-74.el7.x86_64.rpm not found > Looking for ipset-6.29-1.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/ipset/6.29/1.el7/x86_64/ipset-6.29-1.el7.x86_64.rpm) > --2018-09-06 12:07:31-- > https://kojipkgs.fedoraproject.org/packages/ipset/6.29/1.el7/x86_64/ipset-6.29-1.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:32 ERROR 404: Not Found. > > Warning: ipset-6.29-1.el7.x86_64.rpm not found > Looking for ipset-libs-6.29-1.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/ipset-libs/6.29/1.el7/x86_64/ipset-libs-6.29-1.el7.x86_64.rpm) > --2018-09-06 12:07:32-- > https://kojipkgs.fedoraproject.org/packages/ipset-libs/6.29/1.el7/x86_64/ipset-libs-6.29-1.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:33 ERROR 404: Not Found. > > Warning: ipset-libs-6.29-1.el7.x86_64.rpm not found > Looking for iputils-20160308-10.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/iputils/20160308/10.el7/x86_64/iputils-20160308-10.el7.x86_64.rpm) > --2018-09-06 12:07:33-- > https://kojipkgs.fedoraproject.org/packages/iputils/20160308/10.el7/x86_64/iputils-20160308-10.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:34 ERROR 404: Not Found. > > Warning: iputils-20160308-10.el7.x86_64.rpm not found > Looking for ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/ipxe-roms-qemu/20170123/1.git4e85b27.el7_4.1/noarch/ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm) > --2018-09-06 12:07:34-- > https://kojipkgs.fedoraproject.org/packages/ipxe-roms-qemu/20170123/1.git4e85b27.el7_4.1/noarch/ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:35 ERROR 404: Not Found. > > Warning: ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm not found > Looking for iso-codes-3.46-2.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/iso-codes/3.46/2.el7/noarch/iso-codes-3.46-2.el7.noarch.rpm) > --2018-09-06 12:07:35-- > https://kojipkgs.fedoraproject.org/packages/iso-codes/3.46/2.el7/noarch/iso-codes-3.46-2.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:37 ERROR 404: Not Found. > > Warning: iso-codes-3.46-2.el7.noarch.rpm not found > Looking for isomd5sum-1.0.10-5.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/isomd5sum/1.0.10/5.el7/x86_64/isomd5sum-1.0.10-5.el7.x86_64.rpm) > --2018-09-06 12:07:37-- > https://kojipkgs.fedoraproject.org/packages/isomd5sum/1.0.10/5.el7/x86_64/isomd5sum-1.0.10-5.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:38 ERROR 404: Not Found. > > Warning: isomd5sum-1.0.10-5.el7.x86_64.rpm not found > Looking for ivykis-0.36.2-2.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/ivykis/0.36.2/2.el7/x86_64/ivykis-0.36.2-2.el7.x86_64.rpm) > --2018-09-06 12:07:38-- > https://kojipkgs.fedoraproject.org/packages/ivykis/0.36.2/2.el7/x86_64/ivykis-0.36.2-2.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:39 ERROR 404: Not Found. > > Warning: ivykis-0.36.2-2.el7.x86_64.rpm not found > Looking for ivykis-devel-0.36.2-2.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/ivykis-devel/0.36.2/2.el7/x86_64/ivykis-devel-0.36.2-2.el7.x86_64.rpm) > --2018-09-06 12:07:39-- > https://kojipkgs.fedoraproject.org/packages/ivykis-devel/0.36.2/2.el7/x86_64/ivykis-devel-0.36.2-2.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:40 ERROR 404: Not Found. > > Warning: ivykis-devel-0.36.2-2.el7.x86_64.rpm not found > Looking for jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jakarta-commons-httpclient/3.1/16.el7_0/noarch/jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm) > --2018-09-06 12:07:40-- > https://kojipkgs.fedoraproject.org/packages/jakarta-commons-httpclient/3.1/16.el7_0/noarch/jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:41 ERROR 404: Not Found. > > Warning: jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm not found > Looking for jansson-2.10-1.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jansson/2.10/1.el7/x86_64/jansson-2.10-1.el7.x86_64.rpm) > --2018-09-06 12:07:41-- > https://kojipkgs.fedoraproject.org/packages/jansson/2.10/1.el7/x86_64/jansson-2.10-1.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:42 ERROR 404: Not Found. > > Warning: jansson-2.10-1.el7.x86_64.rpm not found > Looking for jasper-devel-1.900.1-31.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jasper-devel/1.900.1/31.el7/x86_64/jasper-devel-1.900.1-31.el7.x86_64.rpm) > --2018-09-06 12:07:42-- > https://kojipkgs.fedoraproject.org/packages/jasper-devel/1.900.1/31.el7/x86_64/jasper-devel-1.900.1-31.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:43 ERROR 404: Not Found. > > Warning: jasper-devel-1.900.1-31.el7.x86_64.rpm not found > Looking for jasper-libs-1.900.1-31.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jasper-libs/1.900.1/31.el7/x86_64/jasper-libs-1.900.1-31.el7.x86_64.rpm) > --2018-09-06 12:07:43-- > https://kojipkgs.fedoraproject.org/packages/jasper-libs/1.900.1/31.el7/x86_64/jasper-libs-1.900.1-31.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:44 ERROR 404: Not Found. > > Warning: jasper-libs-1.900.1-31.el7.x86_64.rpm not found > Looking for javamail-1.4.6-8.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/javamail/1.4.6/8.el7/noarch/javamail-1.4.6-8.el7.noarch.rpm) > --2018-09-06 12:07:44-- > https://kojipkgs.fedoraproject.org/packages/javamail/1.4.6/8.el7/noarch/javamail-1.4.6-8.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:45 ERROR 404: Not Found. > > Warning: javamail-1.4.6-8.el7.noarch.rpm not found > Looking for javapackages-tools-3.4.1-11.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/javapackages-tools/3.4.1/11.el7/noarch/javapackages-tools-3.4.1-11.el7.noarch.rpm) > --2018-09-06 12:07:46-- > https://kojipkgs.fedoraproject.org/packages/javapackages-tools/3.4.1/11.el7/noarch/javapackages-tools-3.4.1-11.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:46 ERROR 404: Not Found. > > Warning: javapackages-tools-3.4.1-11.el7.noarch.rpm not found > Looking for javassist-3.16.1-10.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/javassist/3.16.1/10.el7/noarch/javassist-3.16.1-10.el7.noarch.rpm) > --2018-09-06 12:07:47-- > https://kojipkgs.fedoraproject.org/packages/javassist/3.16.1/10.el7/noarch/javassist-3.16.1-10.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:48 ERROR 404: Not Found. > > Warning: javassist-3.16.1-10.el7.noarch.rpm not found > Looking for jbigkit-libs-2.0-11.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jbigkit-libs/2.0/11.el7/x86_64/jbigkit-libs-2.0-11.el7.x86_64.rpm) > --2018-09-06 12:07:48-- > https://kojipkgs.fedoraproject.org/packages/jbigkit-libs/2.0/11.el7/x86_64/jbigkit-libs-2.0-11.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:49 ERROR 404: Not Found. > > Warning: jbigkit-libs-2.0-11.el7.x86_64.rpm not found > Looking for jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jboss-ejb-3.1-api/1.0.2/10.el7/noarch/jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm) > --2018-09-06 12:07:49-- > https://kojipkgs.fedoraproject.org/packages/jboss-ejb-3.1-api/1.0.2/10.el7/noarch/jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:50 ERROR 404: Not Found. > > Warning: jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm not found > Looking for jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jboss-el-2.2-api/1.0.1/0.7.20120212git2fabd8.el7/noarch/jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm) > --2018-09-06 12:07:50-- > https://kojipkgs.fedoraproject.org/packages/jboss-el-2.2-api/1.0.1/0.7.20120212git2fabd8.el7/noarch/jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:51 ERROR 404: Not Found. > > Warning: jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm > not found > Looking for > jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jboss-interceptors-1.1-api/1.0.2/0.9.20120319git49a904.el7/noarch/jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm) > --2018-09-06 12:07:51-- > https://kojipkgs.fedoraproject.org/packages/jboss-interceptors-1.1-api/1.0.2/0.9.20120319git49a904.el7/noarch/jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:52 ERROR 404: Not Found. > > Warning: > jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm > not found > Looking for jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jboss-jaxrpc-1.1-api/1.0.1/7.el7/noarch/jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm) > --2018-09-06 12:07:52-- > https://kojipkgs.fedoraproject.org/packages/jboss-jaxrpc-1.1-api/1.0.1/7.el7/noarch/jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:53 ERROR 404: Not Found. > > Warning: jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm not found > Looking for jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jboss-servlet-3.0-api/1.0.1/9.el7/noarch/jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm) > --2018-09-06 12:07:53-- > https://kojipkgs.fedoraproject.org/packages/jboss-servlet-3.0-api/1.0.1/9.el7/noarch/jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:54 ERROR 404: Not Found. > > Warning: jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm not found > Looking for jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jboss-transaction-1.1-api/1.0.1/8.el7/noarch/jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm) > --2018-09-06 12:07:54-- > https://kojipkgs.fedoraproject.org/packages/jboss-transaction-1.1-api/1.0.1/8.el7/noarch/jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:55 ERROR 404: Not Found. > > Warning: jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm not found > Looking for jline-1.0-8.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jline/1.0/8.el7/noarch/jline-1.0-8.el7.noarch.rpm) > --2018-09-06 12:07:55-- > https://kojipkgs.fedoraproject.org/packages/jline/1.0/8.el7/noarch/jline-1.0-8.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:57 ERROR 404: Not Found. > > Warning: jline-1.0-8.el7.noarch.rpm not found > Looking for jomolhari-fonts-0.003-17.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jomolhari-fonts/0.003/17.el7/noarch/jomolhari-fonts-0.003-17.el7.noarch.rpm) > --2018-09-06 12:07:57-- > https://kojipkgs.fedoraproject.org/packages/jomolhari-fonts/0.003/17.el7/noarch/jomolhari-fonts-0.003-17.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:58 ERROR 404: Not Found. > > Warning: jomolhari-fonts-0.003-17.el7.noarch.rpm not found > Looking for js-1.8.5-19.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/js/1.8.5/19.el7/x86_64/js-1.8.5-19.el7.x86_64.rpm) > --2018-09-06 12:07:58-- > https://kojipkgs.fedoraproject.org/packages/js/1.8.5/19.el7/x86_64/js-1.8.5-19.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:07:59 ERROR 404: Not Found. > > Warning: js-1.8.5-19.el7.x86_64.rpm not found > Looking for jsch-0.1.50-5.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jsch/0.1.50/5.el7/noarch/jsch-0.1.50-5.el7.noarch.rpm) > --2018-09-06 12:07:59-- > https://kojipkgs.fedoraproject.org/packages/jsch/0.1.50/5.el7/noarch/jsch-0.1.50-5.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:00 ERROR 404: Not Found. > > Warning: jsch-0.1.50-5.el7.noarch.rpm not found > Looking for json-c-0.11-4.el7_0.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/json-c/0.11/4.el7_0/x86_64/json-c-0.11-4.el7_0.x86_64.rpm) > --2018-09-06 12:08:00-- > https://kojipkgs.fedoraproject.org/packages/json-c/0.11/4.el7_0/x86_64/json-c-0.11-4.el7_0.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:01 ERROR 404: Not Found. > > Warning: json-c-0.11-4.el7_0.x86_64.rpm not found > Looking for json-c-devel-0.11-4.el7_0.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/json-c-devel/0.11/4.el7_0/x86_64/json-c-devel-0.11-4.el7_0.x86_64.rpm) > --2018-09-06 12:08:01-- > https://kojipkgs.fedoraproject.org/packages/json-c-devel/0.11/4.el7_0/x86_64/json-c-devel-0.11-4.el7_0.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:02 ERROR 404: Not Found. > > Warning: json-c-devel-0.11-4.el7_0.x86_64.rpm not found > Looking for json-glib-1.2.6-1.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/json-glib/1.2.6/1.el7/x86_64/json-glib-1.2.6-1.el7.x86_64.rpm) > --2018-09-06 12:08:02-- > https://kojipkgs.fedoraproject.org/packages/json-glib/1.2.6/1.el7/x86_64/json-glib-1.2.6-1.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:03 ERROR 404: Not Found. > > Warning: json-glib-1.2.6-1.el7.x86_64.rpm not found > Looking for json-glib-devel-1.2.6-1.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/json-glib-devel/1.2.6/1.el7/x86_64/json-glib-devel-1.2.6-1.el7.x86_64.rpm) > --2018-09-06 12:08:04-- > https://kojipkgs.fedoraproject.org/packages/json-glib-devel/1.2.6/1.el7/x86_64/json-glib-devel-1.2.6-1.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:05 ERROR 404: Not Found. > > Warning: json-glib-devel-1.2.6-1.el7.x86_64.rpm not found > Looking for jsoup-1.6.1-10.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jsoup/1.6.1/10.el7/noarch/jsoup-1.6.1-10.el7.noarch.rpm) > --2018-09-06 12:08:05-- > https://kojipkgs.fedoraproject.org/packages/jsoup/1.6.1/10.el7/noarch/jsoup-1.6.1-10.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:06 ERROR 404: Not Found. > > Warning: jsoup-1.6.1-10.el7.noarch.rpm not found > Looking for julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/julietaula-montserrat-fonts/7.200/1.el7/noarch/julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm) > --2018-09-06 12:08:06-- > https://kojipkgs.fedoraproject.org/packages/julietaula-montserrat-fonts/7.200/1.el7/noarch/julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:07 ERROR 404: Not Found. > > Warning: julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm not found > Looking for junit-4.11-8.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/junit/4.11/8.el7/noarch/junit-4.11-8.el7.noarch.rpm) > --2018-09-06 12:08:08-- > https://kojipkgs.fedoraproject.org/packages/junit/4.11/8.el7/noarch/junit-4.11-8.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:09 ERROR 404: Not Found. > > Warning: junit-4.11-8.el7.noarch.rpm not found > Looking for jzlib-1.1.1-6.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/jzlib/1.1.1/6.el7/noarch/jzlib-1.1.1-6.el7.noarch.rpm) > --2018-09-06 12:08:09-- > https://kojipkgs.fedoraproject.org/packages/jzlib/1.1.1/6.el7/noarch/jzlib-1.1.1-6.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:10 ERROR 404: Not Found. > > Warning: jzlib-1.1.1-6.el7.noarch.rpm not found > Looking for kbd-1.15.5-13.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/kbd/1.15.5/13.el7/x86_64/kbd-1.15.5-13.el7.x86_64.rpm) > --2018-09-06 12:08:10-- > https://kojipkgs.fedoraproject.org/packages/kbd/1.15.5/13.el7/x86_64/kbd-1.15.5-13.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:11 ERROR 404: Not Found. > > Warning: kbd-1.15.5-13.el7.x86_64.rpm not found > Looking for kbd-legacy-1.15.5-13.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/kbd-legacy/1.15.5/13.el7/noarch/kbd-legacy-1.15.5-13.el7.noarch.rpm) > --2018-09-06 12:08:11-- > https://kojipkgs.fedoraproject.org/packages/kbd-legacy/1.15.5/13.el7/noarch/kbd-legacy-1.15.5-13.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:12 ERROR 404: Not Found. > > Warning: kbd-legacy-1.15.5-13.el7.noarch.rpm not found > Looking for kbd-misc-1.15.5-13.el7.noarch.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/kbd-misc/1.15.5/13.el7/noarch/kbd-misc-1.15.5-13.el7.noarch.rpm) > --2018-09-06 12:08:12-- > https://kojipkgs.fedoraproject.org/packages/kbd-misc/1.15.5/13.el7/noarch/kbd-misc-1.15.5-13.el7.noarch.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:13 ERROR 404: Not Found. > > Warning: kbd-misc-1.15.5-13.el7.noarch.rpm not found > Looking for kde-filesystem-4-47.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/kde-filesystem/4/47.el7/x86_64/kde-filesystem-4-47.el7.x86_64.rpm) > --2018-09-06 12:08:13-- > https://kojipkgs.fedoraproject.org/packages/kde-filesystem/4/47.el7/x86_64/kde-filesystem-4-47.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:14 ERROR 404: Not Found. > > Warning: kde-filesystem-4-47.el7.x86_64.rpm not found > Looking for keepalived-1.3.5-6.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/keepalived/1.3.5/6.el7/x86_64/keepalived-1.3.5-6.el7.x86_64.rpm) > --2018-09-06 12:08:14-- > https://kojipkgs.fedoraproject.org/packages/keepalived/1.3.5/6.el7/x86_64/keepalived-1.3.5-6.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2018-09-06 12:08:15 ERROR 404: Not Found. > > Warning: keepalived-1.3.5-6.el7.x86_64.rpm not found > Looking for kernel-headers-3.10.0-862.6.3.el7.x86_64.rpm... > --> run: wget > https://kojipkgs.fedoraproject.org/packages/kernel-headers/3.10.0/862.6.3.el7/x86_64/kernel-headers-3.10.0-862.6.3.el7.x86_64.rpm) > --2018-09-06 12:08:16-- > https://kojipkgs.fedoraproject.org/packages/kernel-headers/3.10.0/862.6.3.el7/x86_64/kernel-headers-3.10.0-862.6.3.el7.x86_64.rpm) > Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... > 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... > Connecting to kojipkgs.fedoraproject.org > (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. > HTTP request sent, awaiting response... ^C > > > _______________________________________________ > 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 David.Sullivan at windriver.com Fri Sep 7 16:21:33 2018 From: David.Sullivan at windriver.com (Sullivan, David) Date: Fri, 7 Sep 2018 16:21:33 +0000 Subject: [Starlingx-discuss] The stx-gui challenge In-Reply-To: References: Message-ID: The packaging of stx-gui is complete. The panels present in stx-gui are packaged as starlingx-dashboard and included in the iso build. The manual steps listed below are no longer required, everything is integrated into the build process. David From: Ramirez, Eddie [mailto:eddie.ramirez at intel.com] Sent: Wednesday, August 22, 2018 9:43 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] The stx-gui challenge Hi all, The last few months working on stx-horizon have given me a broad understanding of the customizations, new dependencies, additions and removals of LOCs that WRS have added on top of Horizon. For simplicity, let’s imagine stx-horizon as a superset of horizon that makes stx-specific functionality a reality. The downside of having and maintaining a custom “superset” of horizon is that catching up with upstream is expensive, painful and time-consuming that requires a having solid understanding of this project. In an attempt to alleviate the tedious, rebase work after every upstream release, a pluggable python package that would carry stx-specific functionality was the most sound option and architecture to adopt. Horizon supports “plugins”, the recommended way to extend and add to the functionality that already exists and, after removing more than 25,000 lines of code from stx-horizon, the stx-gui horizon was born. [cid:image001.png at 01D4469C.30AB6B50] *the stx-horizon superset of horizon is smaller now* What does the plugin do? Stx-gui isolates new panels (System Inventory, Fault Management, Server Groups, etc), API wrappers for clients (cgtsclient, cgcs_patch, sysinv, etc) and many other utility functions that are specific to the StarlingX project. This architecture helps us to: 1. Significantly improve the way we deal with technical debt: rebases will be easier as more LOCs are moved from stx-horizon to stx-gui, until we end up using the upstream version of horizon ☺ 2. Follow a community well-known architecture for extending horizon: “want to add custom functionality to horizon? Write a plugin”… that’s what you’d hear from the community Another side-benefits from doing this splitting 1. Detected additions that can make horizon upstream better: this process threw light on the upstreaming work that I do in parallel. 2. Detected dead code: some files are still holding portions of code that are never executed 3. Found and documented hard dependencies that must be defined somewhere (requirements.txt) 4. An x-ray for understanding what the development documentation would look like 5. Understanding the dimension of the customizations made by WRS: horizon acts as a proxy between operators/users and API endpoints through python-clients. Future modifications to python-clients and APIs will certainly affect the way Horizon talks to them. What does NOT the plugin do? * It does not remove all of the customizations made to the internals of Horizon, that includes: * Any modification done to existing panels (built in panels like Instances, Containers, etc) * The horizon Framework (the way tables are rendered or respond to user actions) * Fixes to JS files, etc. * Tests * Tabs added to Horizon Panels: Network->Routers->Port Forwarding is an example * It does not specify what dependencies it needs (but they are documented) How do I use it? The steps below are ONLY for development and assuming you’re developing outside of the VM running StarlingX. 1. Git clone stx-horizon and switch to branch post-stx-gui-cleanup, you can find the branch on my github profile or check the PR. 2. cd stx-horizon and create a virtualenv with py27 in it. 3. Install Horizon dependencies:pip install -r requirements.txt 4. Git clone stx-gui in a different directory outside of stx-horizon 5. cd stx-gui and using the same virtualenvironment for stx-horizon, run python setup.py install. This will create a packaged version of the plugin that is accessible by stx-horizon’s venv. 6. Install all stx-gui dependencies 7. Copy enable files inside of stx-gui/starlingx_dashboard/enabled/ to stx-horizon/openstack_dashboard/local/enabled/ 8. Finally, inside of stx-horizon, run the horizon dev server with “python manage.py runserver” The installation can be simplified and automated when building an ISO. I’m not familiar with the process but I can guide by explaining what steps must be followed and in what order. It basically involves moving to the right branches, cloning stx-gui, creating a package and copying files to one directory. Please read the extensive documentation I’ve put on this etherpad for more instructions for better format. What’s next? There will be a number of things to keep in mind from now on, answering some questions can help to understand if a change goes to stx-horizon or stx-gui. Also, the long work to make stx-gui work with Upstream Horizon is still pending, but fairly documented thanks to the splitting process. The developer experience is important too, how can we make working with stx-gui an inviting place for others? Py3 compatibility and many other things that are aligned to our priorities and commitments. Eddie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 25451 bytes Desc: image001.png URL: From abraham.arce.moreno at intel.com Fri Sep 7 16:29:40 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 7 Sep 2018 16:29:40 +0000 Subject: [Starlingx-discuss] restapi-doc source code building In-Reply-To: <71AECFE5078153419EB7B8DBE0644B263863654B@shsmsx102.ccr.corp.intel.com> References: <71AECFE5078153419EB7B8DBE0644B263863654B@shsmsx102.ccr.corp.intel.com> Message-ID: > At previous, I ever build successfully restapt-doc package. Compare > previous version and current version, I found some new commits. I don't > know whether these new commit cause building fails. > Do you have a previous mvn.tar.gz file available generated under [0] based on: !mvn.repo.tgz#mvn#https://repo.maven.apache.org/maven2 > I also check $MY_WORKSPACE/std/results/dehao-starlingx-tis-r5-pike- > std/restapi-doc-1.9.1-27.tis/root.log, everythings seem normal. > > But $MY_WORKSPACE/std/results/dehao-starlingx-tis-r5-pike- > std/restapi-doc-1.9.1-27.tis/build.log, it show some error, and I can't > understand these error cause. > > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean- > plugin:2.4.1:clean (default-clean) on project parent-pom: Execution default- > clean of goal org.apache.maven.plugins:maven-clean-plugin:2.4.1:clean > failed: Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of > its dependencies could not be resolved: Failed to collect dependencies for > org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1 (): Failed to read > artifact descriptor for org.apache.maven:maven-plugin-api:jar:2.0.6: The > repository system is offline but the artifact org.apache.maven:maven- > parent:pom:5 is not available in the local repository. -> [Help 1] I have successfully built today after doing a repo sync and also launched the individual compilation of restapi-doc without issues. Please use a previous mvn.tar.gz file or download again. [0] https://git.openstack.org/cgit/openstack/stx-tools/tree/centos-mirror-tools/dl_tarball.sh From scott.little at windriver.com Fri Sep 7 16:26:42 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 7 Sep 2018 12:26:42 -0400 Subject: [Starlingx-discuss] ALL kojipkgs.fedoraproject.org 404 Not Found In-Reply-To: <06d8ee7b-c4bd-5ceb-ec6d-657c307af14a@windriver.com> References: <06d8ee7b-c4bd-5ceb-ec6d-657c307af14a@windriver.com> Message-ID: I see from another thread it was a bad update to the dl_rpms.sh script. On 18-09-07 12:06 PM, Scott Little wrote: > kojipkgs.fedoraproject.org as a best effort fallback when the primary > source for the rpm has failed. It's not guaranteed to have the package > we seek, and 404's are not unexpected. > > What IS unexpected is that so many packages have gone missing from the > primary sources.  Some transient server or network issues? > > I see from other posts that you eventually succeeded in building an > ISO.  I assume you reran download_mirror.sh and succeeded based on > primary sources? > > Scott > > > On 18-09-06 08:15 AM, scottk at optimcloud.com wrote: >> >> seems also ALL kojipkgs.fedoraproject.org based packages resumt in a >> 404 Not Found >> >> Warning: ipa-pmincho-fonts-003.03-5.el7.noarch.rpm not found >> Looking for iperf3-3.1.7-2.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/iperf3/3.1.7/2.el7/x86_64/iperf3-3.1.7-2.el7.x86_64.rpm) >> --2018-09-06 12:07:28-- >> https://kojipkgs.fedoraproject.org/packages/iperf3/3.1.7/2.el7/x86_64/iperf3-3.1.7-2.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:29 ERROR 404: Not Found. >> >> Warning: iperf3-3.1.7-2.el7.x86_64.rpm not found >> Looking for ipmitool-1.8.18-7.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/ipmitool/1.8.18/7.el7/x86_64/ipmitool-1.8.18-7.el7.x86_64.rpm) >> --2018-09-06 12:07:29-- >> https://kojipkgs.fedoraproject.org/packages/ipmitool/1.8.18/7.el7/x86_64/ipmitool-1.8.18-7.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:30 ERROR 404: Not Found. >> >> Warning: ipmitool-1.8.18-7.el7.x86_64.rpm not found >> Looking for iproute-3.10.0-74.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/iproute/3.10.0/74.el7/x86_64/iproute-3.10.0-74.el7.x86_64.rpm) >> --2018-09-06 12:07:30-- >> https://kojipkgs.fedoraproject.org/packages/iproute/3.10.0/74.el7/x86_64/iproute-3.10.0-74.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:31 ERROR 404: Not Found. >> >> Warning: iproute-3.10.0-74.el7.x86_64.rpm not found >> Looking for ipset-6.29-1.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/ipset/6.29/1.el7/x86_64/ipset-6.29-1.el7.x86_64.rpm) >> --2018-09-06 12:07:31-- >> https://kojipkgs.fedoraproject.org/packages/ipset/6.29/1.el7/x86_64/ipset-6.29-1.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:32 ERROR 404: Not Found. >> >> Warning: ipset-6.29-1.el7.x86_64.rpm not found >> Looking for ipset-libs-6.29-1.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/ipset-libs/6.29/1.el7/x86_64/ipset-libs-6.29-1.el7.x86_64.rpm) >> --2018-09-06 12:07:32-- >> https://kojipkgs.fedoraproject.org/packages/ipset-libs/6.29/1.el7/x86_64/ipset-libs-6.29-1.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:33 ERROR 404: Not Found. >> >> Warning: ipset-libs-6.29-1.el7.x86_64.rpm not found >> Looking for iputils-20160308-10.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/iputils/20160308/10.el7/x86_64/iputils-20160308-10.el7.x86_64.rpm) >> --2018-09-06 12:07:33-- >> https://kojipkgs.fedoraproject.org/packages/iputils/20160308/10.el7/x86_64/iputils-20160308-10.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:34 ERROR 404: Not Found. >> >> Warning: iputils-20160308-10.el7.x86_64.rpm not found >> Looking for ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/ipxe-roms-qemu/20170123/1.git4e85b27.el7_4.1/noarch/ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm) >> --2018-09-06 12:07:34-- >> https://kojipkgs.fedoraproject.org/packages/ipxe-roms-qemu/20170123/1.git4e85b27.el7_4.1/noarch/ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:35 ERROR 404: Not Found. >> >> Warning: ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch.rpm not >> found >> Looking for iso-codes-3.46-2.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/iso-codes/3.46/2.el7/noarch/iso-codes-3.46-2.el7.noarch.rpm) >> --2018-09-06 12:07:35-- >> https://kojipkgs.fedoraproject.org/packages/iso-codes/3.46/2.el7/noarch/iso-codes-3.46-2.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:37 ERROR 404: Not Found. >> >> Warning: iso-codes-3.46-2.el7.noarch.rpm not found >> Looking for isomd5sum-1.0.10-5.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/isomd5sum/1.0.10/5.el7/x86_64/isomd5sum-1.0.10-5.el7.x86_64.rpm) >> --2018-09-06 12:07:37-- >> https://kojipkgs.fedoraproject.org/packages/isomd5sum/1.0.10/5.el7/x86_64/isomd5sum-1.0.10-5.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:38 ERROR 404: Not Found. >> >> Warning: isomd5sum-1.0.10-5.el7.x86_64.rpm not found >> Looking for ivykis-0.36.2-2.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/ivykis/0.36.2/2.el7/x86_64/ivykis-0.36.2-2.el7.x86_64.rpm) >> --2018-09-06 12:07:38-- >> https://kojipkgs.fedoraproject.org/packages/ivykis/0.36.2/2.el7/x86_64/ivykis-0.36.2-2.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:39 ERROR 404: Not Found. >> >> Warning: ivykis-0.36.2-2.el7.x86_64.rpm not found >> Looking for ivykis-devel-0.36.2-2.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/ivykis-devel/0.36.2/2.el7/x86_64/ivykis-devel-0.36.2-2.el7.x86_64.rpm) >> --2018-09-06 12:07:39-- >> https://kojipkgs.fedoraproject.org/packages/ivykis-devel/0.36.2/2.el7/x86_64/ivykis-devel-0.36.2-2.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:40 ERROR 404: Not Found. >> >> Warning: ivykis-devel-0.36.2-2.el7.x86_64.rpm not found >> Looking for jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jakarta-commons-httpclient/3.1/16.el7_0/noarch/jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm) >> --2018-09-06 12:07:40-- >> https://kojipkgs.fedoraproject.org/packages/jakarta-commons-httpclient/3.1/16.el7_0/noarch/jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:41 ERROR 404: Not Found. >> >> Warning: jakarta-commons-httpclient-3.1-16.el7_0.noarch.rpm not found >> Looking for jansson-2.10-1.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jansson/2.10/1.el7/x86_64/jansson-2.10-1.el7.x86_64.rpm) >> --2018-09-06 12:07:41-- >> https://kojipkgs.fedoraproject.org/packages/jansson/2.10/1.el7/x86_64/jansson-2.10-1.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:42 ERROR 404: Not Found. >> >> Warning: jansson-2.10-1.el7.x86_64.rpm not found >> Looking for jasper-devel-1.900.1-31.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jasper-devel/1.900.1/31.el7/x86_64/jasper-devel-1.900.1-31.el7.x86_64.rpm) >> --2018-09-06 12:07:42-- >> https://kojipkgs.fedoraproject.org/packages/jasper-devel/1.900.1/31.el7/x86_64/jasper-devel-1.900.1-31.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:43 ERROR 404: Not Found. >> >> Warning: jasper-devel-1.900.1-31.el7.x86_64.rpm not found >> Looking for jasper-libs-1.900.1-31.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jasper-libs/1.900.1/31.el7/x86_64/jasper-libs-1.900.1-31.el7.x86_64.rpm) >> --2018-09-06 12:07:43-- >> https://kojipkgs.fedoraproject.org/packages/jasper-libs/1.900.1/31.el7/x86_64/jasper-libs-1.900.1-31.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:44 ERROR 404: Not Found. >> >> Warning: jasper-libs-1.900.1-31.el7.x86_64.rpm not found >> Looking for javamail-1.4.6-8.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/javamail/1.4.6/8.el7/noarch/javamail-1.4.6-8.el7.noarch.rpm) >> --2018-09-06 12:07:44-- >> https://kojipkgs.fedoraproject.org/packages/javamail/1.4.6/8.el7/noarch/javamail-1.4.6-8.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:45 ERROR 404: Not Found. >> >> Warning: javamail-1.4.6-8.el7.noarch.rpm not found >> Looking for javapackages-tools-3.4.1-11.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/javapackages-tools/3.4.1/11.el7/noarch/javapackages-tools-3.4.1-11.el7.noarch.rpm) >> --2018-09-06 12:07:46-- >> https://kojipkgs.fedoraproject.org/packages/javapackages-tools/3.4.1/11.el7/noarch/javapackages-tools-3.4.1-11.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:46 ERROR 404: Not Found. >> >> Warning: javapackages-tools-3.4.1-11.el7.noarch.rpm not found >> Looking for javassist-3.16.1-10.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/javassist/3.16.1/10.el7/noarch/javassist-3.16.1-10.el7.noarch.rpm) >> --2018-09-06 12:07:47-- >> https://kojipkgs.fedoraproject.org/packages/javassist/3.16.1/10.el7/noarch/javassist-3.16.1-10.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:48 ERROR 404: Not Found. >> >> Warning: javassist-3.16.1-10.el7.noarch.rpm not found >> Looking for jbigkit-libs-2.0-11.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jbigkit-libs/2.0/11.el7/x86_64/jbigkit-libs-2.0-11.el7.x86_64.rpm) >> --2018-09-06 12:07:48-- >> https://kojipkgs.fedoraproject.org/packages/jbigkit-libs/2.0/11.el7/x86_64/jbigkit-libs-2.0-11.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:49 ERROR 404: Not Found. >> >> Warning: jbigkit-libs-2.0-11.el7.x86_64.rpm not found >> Looking for jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jboss-ejb-3.1-api/1.0.2/10.el7/noarch/jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm) >> --2018-09-06 12:07:49-- >> https://kojipkgs.fedoraproject.org/packages/jboss-ejb-3.1-api/1.0.2/10.el7/noarch/jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:50 ERROR 404: Not Found. >> >> Warning: jboss-ejb-3.1-api-1.0.2-10.el7.noarch.rpm not found >> Looking for >> jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jboss-el-2.2-api/1.0.1/0.7.20120212git2fabd8.el7/noarch/jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm) >> --2018-09-06 12:07:50-- >> https://kojipkgs.fedoraproject.org/packages/jboss-el-2.2-api/1.0.1/0.7.20120212git2fabd8.el7/noarch/jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:51 ERROR 404: Not Found. >> >> Warning: jboss-el-2.2-api-1.0.1-0.7.20120212git2fabd8.el7.noarch.rpm >> not found >> Looking for >> jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jboss-interceptors-1.1-api/1.0.2/0.9.20120319git49a904.el7/noarch/jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm) >> --2018-09-06 12:07:51-- >> https://kojipkgs.fedoraproject.org/packages/jboss-interceptors-1.1-api/1.0.2/0.9.20120319git49a904.el7/noarch/jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:52 ERROR 404: Not Found. >> >> Warning: >> jboss-interceptors-1.1-api-1.0.2-0.9.20120319git49a904.el7.noarch.rpm >> not found >> Looking for jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jboss-jaxrpc-1.1-api/1.0.1/7.el7/noarch/jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm) >> --2018-09-06 12:07:52-- >> https://kojipkgs.fedoraproject.org/packages/jboss-jaxrpc-1.1-api/1.0.1/7.el7/noarch/jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:53 ERROR 404: Not Found. >> >> Warning: jboss-jaxrpc-1.1-api-1.0.1-7.el7.noarch.rpm not found >> Looking for jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jboss-servlet-3.0-api/1.0.1/9.el7/noarch/jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm) >> --2018-09-06 12:07:53-- >> https://kojipkgs.fedoraproject.org/packages/jboss-servlet-3.0-api/1.0.1/9.el7/noarch/jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:54 ERROR 404: Not Found. >> >> Warning: jboss-servlet-3.0-api-1.0.1-9.el7.noarch.rpm not found >> Looking for jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jboss-transaction-1.1-api/1.0.1/8.el7/noarch/jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm) >> --2018-09-06 12:07:54-- >> https://kojipkgs.fedoraproject.org/packages/jboss-transaction-1.1-api/1.0.1/8.el7/noarch/jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:55 ERROR 404: Not Found. >> >> Warning: jboss-transaction-1.1-api-1.0.1-8.el7.noarch.rpm not found >> Looking for jline-1.0-8.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jline/1.0/8.el7/noarch/jline-1.0-8.el7.noarch.rpm) >> --2018-09-06 12:07:55-- >> https://kojipkgs.fedoraproject.org/packages/jline/1.0/8.el7/noarch/jline-1.0-8.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:57 ERROR 404: Not Found. >> >> Warning: jline-1.0-8.el7.noarch.rpm not found >> Looking for jomolhari-fonts-0.003-17.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jomolhari-fonts/0.003/17.el7/noarch/jomolhari-fonts-0.003-17.el7.noarch.rpm) >> --2018-09-06 12:07:57-- >> https://kojipkgs.fedoraproject.org/packages/jomolhari-fonts/0.003/17.el7/noarch/jomolhari-fonts-0.003-17.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:58 ERROR 404: Not Found. >> >> Warning: jomolhari-fonts-0.003-17.el7.noarch.rpm not found >> Looking for js-1.8.5-19.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/js/1.8.5/19.el7/x86_64/js-1.8.5-19.el7.x86_64.rpm) >> --2018-09-06 12:07:58-- >> https://kojipkgs.fedoraproject.org/packages/js/1.8.5/19.el7/x86_64/js-1.8.5-19.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:07:59 ERROR 404: Not Found. >> >> Warning: js-1.8.5-19.el7.x86_64.rpm not found >> Looking for jsch-0.1.50-5.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jsch/0.1.50/5.el7/noarch/jsch-0.1.50-5.el7.noarch.rpm) >> --2018-09-06 12:07:59-- >> https://kojipkgs.fedoraproject.org/packages/jsch/0.1.50/5.el7/noarch/jsch-0.1.50-5.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:00 ERROR 404: Not Found. >> >> Warning: jsch-0.1.50-5.el7.noarch.rpm not found >> Looking for json-c-0.11-4.el7_0.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/json-c/0.11/4.el7_0/x86_64/json-c-0.11-4.el7_0.x86_64.rpm) >> --2018-09-06 12:08:00-- >> https://kojipkgs.fedoraproject.org/packages/json-c/0.11/4.el7_0/x86_64/json-c-0.11-4.el7_0.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:01 ERROR 404: Not Found. >> >> Warning: json-c-0.11-4.el7_0.x86_64.rpm not found >> Looking for json-c-devel-0.11-4.el7_0.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/json-c-devel/0.11/4.el7_0/x86_64/json-c-devel-0.11-4.el7_0.x86_64.rpm) >> --2018-09-06 12:08:01-- >> https://kojipkgs.fedoraproject.org/packages/json-c-devel/0.11/4.el7_0/x86_64/json-c-devel-0.11-4.el7_0.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:02 ERROR 404: Not Found. >> >> Warning: json-c-devel-0.11-4.el7_0.x86_64.rpm not found >> Looking for json-glib-1.2.6-1.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/json-glib/1.2.6/1.el7/x86_64/json-glib-1.2.6-1.el7.x86_64.rpm) >> --2018-09-06 12:08:02-- >> https://kojipkgs.fedoraproject.org/packages/json-glib/1.2.6/1.el7/x86_64/json-glib-1.2.6-1.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:03 ERROR 404: Not Found. >> >> Warning: json-glib-1.2.6-1.el7.x86_64.rpm not found >> Looking for json-glib-devel-1.2.6-1.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/json-glib-devel/1.2.6/1.el7/x86_64/json-glib-devel-1.2.6-1.el7.x86_64.rpm) >> --2018-09-06 12:08:04-- >> https://kojipkgs.fedoraproject.org/packages/json-glib-devel/1.2.6/1.el7/x86_64/json-glib-devel-1.2.6-1.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:05 ERROR 404: Not Found. >> >> Warning: json-glib-devel-1.2.6-1.el7.x86_64.rpm not found >> Looking for jsoup-1.6.1-10.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jsoup/1.6.1/10.el7/noarch/jsoup-1.6.1-10.el7.noarch.rpm) >> --2018-09-06 12:08:05-- >> https://kojipkgs.fedoraproject.org/packages/jsoup/1.6.1/10.el7/noarch/jsoup-1.6.1-10.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:06 ERROR 404: Not Found. >> >> Warning: jsoup-1.6.1-10.el7.noarch.rpm not found >> Looking for julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/julietaula-montserrat-fonts/7.200/1.el7/noarch/julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm) >> --2018-09-06 12:08:06-- >> https://kojipkgs.fedoraproject.org/packages/julietaula-montserrat-fonts/7.200/1.el7/noarch/julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:07 ERROR 404: Not Found. >> >> Warning: julietaula-montserrat-fonts-7.200-1.el7.noarch.rpm not found >> Looking for junit-4.11-8.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/junit/4.11/8.el7/noarch/junit-4.11-8.el7.noarch.rpm) >> --2018-09-06 12:08:08-- >> https://kojipkgs.fedoraproject.org/packages/junit/4.11/8.el7/noarch/junit-4.11-8.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:09 ERROR 404: Not Found. >> >> Warning: junit-4.11-8.el7.noarch.rpm not found >> Looking for jzlib-1.1.1-6.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/jzlib/1.1.1/6.el7/noarch/jzlib-1.1.1-6.el7.noarch.rpm) >> --2018-09-06 12:08:09-- >> https://kojipkgs.fedoraproject.org/packages/jzlib/1.1.1/6.el7/noarch/jzlib-1.1.1-6.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:10 ERROR 404: Not Found. >> >> Warning: jzlib-1.1.1-6.el7.noarch.rpm not found >> Looking for kbd-1.15.5-13.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/kbd/1.15.5/13.el7/x86_64/kbd-1.15.5-13.el7.x86_64.rpm) >> --2018-09-06 12:08:10-- >> https://kojipkgs.fedoraproject.org/packages/kbd/1.15.5/13.el7/x86_64/kbd-1.15.5-13.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:11 ERROR 404: Not Found. >> >> Warning: kbd-1.15.5-13.el7.x86_64.rpm not found >> Looking for kbd-legacy-1.15.5-13.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/kbd-legacy/1.15.5/13.el7/noarch/kbd-legacy-1.15.5-13.el7.noarch.rpm) >> --2018-09-06 12:08:11-- >> https://kojipkgs.fedoraproject.org/packages/kbd-legacy/1.15.5/13.el7/noarch/kbd-legacy-1.15.5-13.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:12 ERROR 404: Not Found. >> >> Warning: kbd-legacy-1.15.5-13.el7.noarch.rpm not found >> Looking for kbd-misc-1.15.5-13.el7.noarch.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/kbd-misc/1.15.5/13.el7/noarch/kbd-misc-1.15.5-13.el7.noarch.rpm) >> --2018-09-06 12:08:12-- >> https://kojipkgs.fedoraproject.org/packages/kbd-misc/1.15.5/13.el7/noarch/kbd-misc-1.15.5-13.el7.noarch.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:13 ERROR 404: Not Found. >> >> Warning: kbd-misc-1.15.5-13.el7.noarch.rpm not found >> Looking for kde-filesystem-4-47.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/kde-filesystem/4/47.el7/x86_64/kde-filesystem-4-47.el7.x86_64.rpm) >> --2018-09-06 12:08:13-- >> https://kojipkgs.fedoraproject.org/packages/kde-filesystem/4/47.el7/x86_64/kde-filesystem-4-47.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:14 ERROR 404: Not Found. >> >> Warning: kde-filesystem-4-47.el7.x86_64.rpm not found >> Looking for keepalived-1.3.5-6.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/keepalived/1.3.5/6.el7/x86_64/keepalived-1.3.5-6.el7.x86_64.rpm) >> --2018-09-06 12:08:14-- >> https://kojipkgs.fedoraproject.org/packages/keepalived/1.3.5/6.el7/x86_64/keepalived-1.3.5-6.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.15, 209.132.181.16, 2402:800:ffff:ffff:0:1:d184:b510, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.15|:443... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2018-09-06 12:08:15 ERROR 404: Not Found. >> >> Warning: keepalived-1.3.5-6.el7.x86_64.rpm not found >> Looking for kernel-headers-3.10.0-862.6.3.el7.x86_64.rpm... >> --> run: wget >> https://kojipkgs.fedoraproject.org/packages/kernel-headers/3.10.0/862.6.3.el7/x86_64/kernel-headers-3.10.0-862.6.3.el7.x86_64.rpm) >> --2018-09-06 12:08:16-- >> https://kojipkgs.fedoraproject.org/packages/kernel-headers/3.10.0/862.6.3.el7/x86_64/kernel-headers-3.10.0-862.6.3.el7.x86_64.rpm) >> Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)... >> 209.132.181.16, 209.132.181.15, 2402:800:ffff:ffff:0:1:d184:b50f, ... >> Connecting to kojipkgs.fedoraproject.org >> (kojipkgs.fedoraproject.org)|209.132.181.16|:443... connected. >> HTTP request sent, awaiting response... ^C >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jason.McKenna at windriver.com Fri Sep 7 19:47:09 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Fri, 7 Sep 2018 19:47:09 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Shuicheng, I've completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason Sent: September 7, 2018 10:08 AM To: Khalil, Ghada ; Lin, Shuicheng ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they've moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We'll run some tests in Wind River. Numan will be priming this activity. He'll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Fri Sep 7 20:09:25 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 7 Sep 2018 15:09:25 -0500 Subject: [Starlingx-discuss] Installation_Guide_Virtual_Environment / Ubuntu Specific In-Reply-To: <2ad3aa544f22e8e08007dc1e56dc118b@optimcloud.com> References: <2ad3aa544f22e8e08007dc1e56dc118b@optimcloud.com> Message-ID: On Fri, Sep 7, 2018 at 7:15 AM, wrote: > so hunted the wiki a bit and found this guide > > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment I just finished (belatedly) updating the wiki to reflect the recent changes to the libvirt scripts with what was already in the README. This still needs to be better integrated into the Installation Guide. https://wiki.openstack.org/wiki/Installation_libvirt_qemu > Ubuntu 16.04 LTS 64-bit > ... Now I have to ask Why.... Seriously? The short answer is that Ubuntu is what is on the boxes we initially had available to use. As you found, there is nothing inherently exclusive to Ubuntu in here, and with a little work this will get more OS-agnostic. > and ... TADA..... functionally working on Fedora 28 and actually installing > at this moment..... so... seriously i have to ask.... > > when do you want to offer me a job..... because this shouldnt be > happening..... anyway..... I find it awesome that you used CentOS for the > platform, great choice... > but why would you force uus to use Ubuntu as the host... personally from an We don't force you, that is simply what those scripts were written for and what was documented thus far. I'm sure had you written this it would be CentOS/Fedora oriented... Also, your job offer is in the next sentence. :) Since you are clearly capable of adjusting this to fit your environment I would invite you to help the next person to come along that doesn't use Ubuntu and submit those changes to the stx-tools repo and help make this particular corner of the world a better place. > This is just my observations.... from a senior level management perspective > of what Ive seen in the industry... if yyou want to be accepted, I belive > you will maybe need more polishh... but so fgar great work, in sight of a > few things maybe over looked. We are painfully aware that this has a long way to go before it is anything close to a download, build and install kind of system. StarlingX is one enormous complex beast that does a complex job. Thanks for taking the time to fight through this build process and for this feedback, it is valuable to see this process from the eyes of someone who isn't already familiar with it. dt -- Dean Troyer dtroyer at gmail.com From Ghada.Khalil at windriver.com Fri Sep 7 21:43:13 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 7 Sep 2018 21:43:13 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> Hi Elio/Ada, Are there any updates from your side on these two Launchpads? https://bugs.launchpad.net/starlingx/+bug/1790213 https://bugs.launchpad.net/starlingx/+bug/1790716 Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team. As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup). Please let us know if you need any further help from us. Thanks, Ghada -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, September 05, 2018 5:39 PM To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Please see inline. There are notes in all the launchpads as well. I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. -----Original Message----- From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Wednesday, September 05, 2018 2:23 PM To: Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted My opinion below -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, September 5, 2018 12:56 PM To: Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Should the bugs coming out of this be tagged/fixed for the October release? Related bugs: https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all instances need at least one compute for multimode [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. The test team points to internal instructions which we have no access to. The supported install recipes need to be on the wiki. I think it is an invalid bug https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Wednesday, September 5, 2018 10:50 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hello all, As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. [0] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary Regards Ada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Fri Sep 7 22:51:53 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 7 Sep 2018 16:51:53 -0600 Subject: [Starlingx-discuss] [docs] Setting up the docs.starlingx.io website In-Reply-To: References: <1466AF2176E6F040BD63860D0A241BBD1ED52E41@FMSMSX109.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED52E88@FMSMSX109.amr.corp.intel.com> Message-ID: <9F465F00-8838-4CC2-A52F-7AEEDFE68EC8@gmail.com> Hi, For third-party CI systems that run on premise we don’t provide a log server but recommend to have a machine to which your job runner can push logs onto (via scp or ftp or rsync or...) with apache with autoindexing turned on to make the log files available. We have a puppet module a lot of third-party CI deployments use which incorporates a log publishing website: https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/manifests/logserver.pp It might be a bit more than what you would want as a first run as it does colorization and interactive filtering of common log formats via a WSGI backend, it depends on your preference which route you go down on. In either case you probably also want to have some means of purging logs after they reach a certain age so it doesn't grow out of control (that puppet module I linked above includes a cron-driven script to do that too). Please let me know if you have any questions. Thanks and Best Regards, Ildikó > On 2018. Sep 3., at 15:07, Arce Moreno, Abraham wrote: > >>> Are we considering to include some path in the site in order to upload >> reports?, should we open a thread for this as well? >> >> This is a static site built from Sphinx docs. What sort of report are you >> thinking about? > > Reports containing results coming from our regular functional tests, > an example of the output in xml: > > - > - > + > + > + > Tests for Install and Configuration of a controller node. Author(s): - Jose Perez... > > > + > > > > We were thinking where it could make sense to upload / post those results: > - Wiki > - Launchpad > - Repository > > We also looked at how OpenStack reports results: > - For every repo, under Gerrit giving a Pass / Fail > - For RefStack, under their homepage page "community results" [0] > - Any other that could fit our needs? > > Some ideas how to share StarlingX test reports: > > - Test wiki page to show executive summary results parsed from the given xml: > - Today this is how we report under our Test wiki page [1] > - Partially automated > - stx-docs hosting those results parsed from the given xml to rst format: > - Fully automated taking advantage of tox infrastructure, how about using "tox -e results"? > - Results uploaded to doc.starlingx.io/results? > > [0] https://refstack.openstack.org/#/community_results > [1] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Fri Sep 7 23:29:40 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Fri, 7 Sep 2018 23:29:40 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B33BD66@SHSMSX104.ccr.corp.intel.com> As previously, we found lighttpd 1.4.49 and 1.4.50 both have runtime issues, there is one help-needed email to Brent see attached. If we have to switch to 1.4.50, then let's prioritize the trouble-shooting together on this. @Jason, if you can help Zhipeng on debugging this issue, that will be very much helpful: https://review.openstack.org/#/c/596263/ thanks. - cindy From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason ; Khalil, Ghada ; Lin, Shuicheng ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I've completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they've moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We'll run some tests in Wind River. Numan will be priming this activity. He'll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: "Rowsell, Brent" Subject: RE: Upgrade lighttpd to CentOS 7.5 version Date: Fri, 31 Aug 2018 15:33:41 +0000 Size: 60452 URL: From shuicheng.lin at intel.com Sat Sep 8 01:22:41 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Sat, 8 Sep 2018 01:22:41 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason ; Khalil, Ghada ; Lin, Shuicheng ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I've completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don't have this issue. I used last week's master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let's further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they've moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We'll run some tests in Wind River. Numan will be priming this activity. He'll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Sat Sep 8 12:58:37 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Sat, 8 Sep 2018 12:58:37 +0000 Subject: [Starlingx-discuss] WRS word replacement Message-ID: <9700A18779F35F49AF027300A49E7C765535791B@SHSMSX101.ccr.corp.intel.com> Hi all, In our code, there are still many comments with WRS/Titanium, especially in the patch file. My first question is should we remove them, or just keep them? If we prefer to remove them, then which words should be used to replace them? I prefer to use STX to replace WRS, and StarlingX to replace Titanium. Any better idea? Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Sat Sep 8 13:13:37 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Sat, 8 Sep 2018 13:13:37 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I've completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don't have this issue. I used last week's master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let's further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they've moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We'll run some tests in Wind River. Numan will be priming this activity. He'll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Sat Sep 8 13:56:22 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Sat, 8 Sep 2018 13:56:22 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> Hi Jason, I have fixed the issue you mentioned below. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. https://review.openstack.org/#/c/600920/ Thanks! Zhipeng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: 2018年9月8日 21:14 To: McKenna, Jason ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I’ve completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don’t have this issue. I used last week’s master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they’ve moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be priming this activity. He’ll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From scottk at optimcloud.com Sat Sep 8 15:50:47 2018 From: scottk at optimcloud.com (scottk at optimcloud.com) Date: Sat, 08 Sep 2018 15:50:47 +0000 Subject: [Starlingx-discuss] =?utf-8?q?=28no_subject=29?= Message-ID: <9ad852126da29008b77cb83ce672b3a1@optimcloud.com> Okay this guide appears completely out dated..... starting here https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment (https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment) PLEASE NOTE: DO NOT DO THIS ON FEDORA .... IT BREAKS LIBVIRT ENVIRONMENTS Install the required packages: $ bash install_packages.sh NO NO NO..... We could actually remedy the scripts if $HOST Fed, Cento/RedHat then elif Debi, Ubuntu anyway..... Deployment Options Standard Controller StarlingX Cloud with Dedicated Storage Virtual Environment StarlingX Cloud with Controller Storage Virtual Environment All-in-one StarlingX Cloud Duplex Virtual Environment StarlingX Cloud Simplex Virtual Environment I chose https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Duplex (https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Duplex) Ive gotten as far as launching ./setup_allinone -i bootimage.iso As stated When i arrive at Configuring Controller-0 The guide is pretty straight forward it would seem however, what i see if a bunch of questions being asked that im somewhat unclear how they should be answered, yes .. run sudo config_controller date/time ... ok system mode ok it then asks me a series of other questions re: vlan, interface... etc etc etc it does not go right to Applying configuration (this will take several minutes): 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... DONE 03/08: Persisting local configuration ... DONE 04/08: Populating initial system inventory ... DONE 05:08: Creating system configuration ... DONE 06:08: Applying controller manifest ... DONE 07:08: Finalize controller configuration ... DONE 08:08: Waiting for service activation ... DONE Configuration was applied so a bit more confusing later on after hitting enter at most of the prompts anyway i did get passed to conffiguration was applied moving forward at system host-disk-list controller-0 it lists 2 disks, where the guide shows 3.... ok.... this isnt going to fly.... and the rest of the directions are based on 3 drives..... but setup_allinone only has 2 configured..... WOW... what to do now.... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jim.Einarsson at windriver.com Sat Sep 8 15:50:19 2018 From: Jim.Einarsson at windriver.com (Einarsson, Jim) Date: Sat, 8 Sep 2018 15:50:19 +0000 Subject: [Starlingx-discuss] WRS word replacement Message-ID: <38713B7817E1A049AB469EA7F6EEF69EBBF7AF68@ALA-MBD.corp.ad.wrs.com> For the Patch file, references to WRS and Titanium should stay, this is public information and is useful history. We should discuss and agree on criteria for editing the comments. Things to remove: References to anybody's proprietary code References to WR internal identifiers (Case #, Jira # User story ID.....) References to commercial customers -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io [mailto:starlingx-discuss-request at lists.starlingx.io] Sent: Saturday, September 08, 2018 9:14 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 4, Issue 39 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. WRS word replacement (Lin, Shuicheng) 2. Re: CentOS 7.5 upgrade status update (Lin, Shuicheng) ---------------------------------------------------------------------- Message: 1 Date: Sat, 8 Sep 2018 12:58:37 +0000 From: "Lin, Shuicheng" To: "'starlingx-discuss at lists.starlingx.io'" Subject: [Starlingx-discuss] WRS word replacement Message-ID: <9700A18779F35F49AF027300A49E7C765535791B at SHSMSX101.ccr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Hi all, In our code, there are still many comments with WRS/Titanium, especially in the patch file. My first question is should we remove them, or just keep them? If we prefer to remove them, then which words should be used to replace them? I prefer to use STX to replace WRS, and StarlingX to replace Titanium. Any better idea? Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Sat, 8 Sep 2018 13:13:37 +0000 From: "Lin, Shuicheng" To: "McKenna, Jason" , "Khalil, Ghada" , "'starlingx-discuss at lists.starlingx.io'" , "Xie, Cindy" , "Waheed, Numan" Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Message-ID: <9700A18779F35F49AF027300A49E7C765535793D at SHSMSX101.ccr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I've completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don't have this issue. I used last week's master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let's further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they've moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We'll run some tests in Wind River. Numan will be priming this activity. He'll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 4, Issue 39 ************************************************ From dehao.shang at intel.com Sun Sep 9 13:13:21 2018 From: dehao.shang at intel.com (Shang, Dehao) Date: Sun, 9 Sep 2018 13:13:21 +0000 Subject: [Starlingx-discuss] building ceph 13.2.0 Message-ID: <71AECFE5078153419EB7B8DBE0644B263863669E@shsmsx102.ccr.corp.intel.com> Hi: I re-setup new building environment, and can successfully build starlingx image. Based on this new environments, I directly use ceph 13.2.0 to replace ceph 10.2.0, build-pkgs ceph, then directly run "build-pkgs ceph ". Build-std.log show the following error: 02:01:23 Error: No Package found for CUnit-devel 02:01:23 Error: No Package found for devtoolset-7-gcc-c++ 02:01:23 Error: No Package found for jq 02:01:23 Error: No Package found for libbabeltrace-devel 02:01:23 Error: No Package found for liboath-devel 02:01:23 Error: No Package found for lttng-ust-devel 02:01:23 Error: No Package found for lz4-devel >= 1.7 02:01:23 Error: No Package found for python34-Cython 02:01:23 Error: No Package found for python34-devel 02:01:23 Error: No Package found for python34-setuptools 02:01:23 Error: No Package found for sharutils So, when i check ceph.spec file of 13.2.0, find some new BuildRequests, for example: BuildRequires: CUnit-devel BuildRequires: devtoolset-7-gcc-c++ ...... ...... ...... My methods is as following: Step 1 : wget get corresponding rpm, then put it into mirror's corresponding folder. Step 2: create package link, namely : ln -sf xxxx yyyy Then, when i run build-pkgs ceph again, found that one deps CUnit-devel is resolved, but other package still can't be found. Build-std.log is as following: 02:01:23 Error: No Package found for devtoolset-7-gcc-c++ 02:01:23 Error: No Package found for jq 02:01:23 Error: No Package found for libbabeltrace-devel 02:01:23 Error: No Package found for liboath-devel 02:01:23 Error: No Package found for lttng-ust-devel 02:01:23 Error: No Package found for lz4-devel >= 1.7 02:01:23 Error: No Package found for python34-Cython 02:01:23 Error: No Package found for python34-devel 02:01:23 Error: No Package found for python34-setuptools 02:01:23 Error: No Package found for sharutils So, I want to ask whether this method is correct ? Based on this method, why one package can be resolved and other package can't be found ? Thanks Dehao -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Mon Sep 10 00:21:26 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Mon, 10 Sep 2018 00:21:26 +0000 Subject: [Starlingx-discuss] WRS word replacement In-Reply-To: <38713B7817E1A049AB469EA7F6EEF69EBBF7AF68@ALA-MBD.corp.ad.wrs.com> References: <38713B7817E1A049AB469EA7F6EEF69EBBF7AF68@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C7655357B78@SHSMSX101.ccr.corp.intel.com> Hi Jim, Get it. Thanks for the classification. Best Regards Shuicheng -----Original Message----- From: Einarsson, Jim [mailto:Jim.Einarsson at windriver.com] Sent: Saturday, September 8, 2018 11:50 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] WRS word replacement For the Patch file, references to WRS and Titanium should stay, this is public information and is useful history. We should discuss and agree on criteria for editing the comments. Things to remove: References to anybody's proprietary code References to WR internal identifiers (Case #, Jira # User story ID.....) References to commercial customers -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io [mailto:starlingx-discuss-request at lists.starlingx.io] Sent: Saturday, September 08, 2018 9:14 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 4, Issue 39 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. WRS word replacement (Lin, Shuicheng) 2. Re: CentOS 7.5 upgrade status update (Lin, Shuicheng) ---------------------------------------------------------------------- Message: 1 Date: Sat, 8 Sep 2018 12:58:37 +0000 From: "Lin, Shuicheng" To: "'starlingx-discuss at lists.starlingx.io'" Subject: [Starlingx-discuss] WRS word replacement Message-ID: <9700A18779F35F49AF027300A49E7C765535791B at SHSMSX101.ccr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Hi all, In our code, there are still many comments with WRS/Titanium, especially in the patch file. My first question is should we remove them, or just keep them? If we prefer to remove them, then which words should be used to replace them? I prefer to use STX to replace WRS, and StarlingX to replace Titanium. Any better idea? Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Sat, 8 Sep 2018 13:13:37 +0000 From: "Lin, Shuicheng" To: "McKenna, Jason" , "Khalil, Ghada" , "'starlingx-discuss at lists.starlingx.io'" , "Xie, Cindy" , "Waheed, Numan" Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Message-ID: <9700A18779F35F49AF027300A49E7C765535793D at SHSMSX101.ccr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I've completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don't have this issue. I used last week's master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let's further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they've moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We'll run some tests in Wind River. Numan will be priming this activity. He'll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 4, Issue 39 ************************************************ _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From shuicheng.lin at intel.com Mon Sep 10 00:40:37 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Mon, 10 Sep 2018 00:40:37 +0000 Subject: [Starlingx-discuss] building ceph 13.2.0 In-Reply-To: <71AECFE5078153419EB7B8DBE0644B263863669E@shsmsx102.ccr.corp.intel.com> References: <71AECFE5078153419EB7B8DBE0644B263863669E@shsmsx102.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C7655357BAE@SHSMSX101.ccr.corp.intel.com> Hi Dehao, Please have a try with "build-pkgs" after "ln -sf xxxx yyyy". The reason is the build system will search the package from the repodata, and "build-pkgs" will add the new package to the repodata. Best Regards Shuicheng From: Shang, Dehao [mailto:dehao.shang at intel.com] Sent: Sunday, September 9, 2018 9:13 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] building ceph 13.2.0 Hi: I re-setup new building environment, and can successfully build starlingx image. Based on this new environments, I directly use ceph 13.2.0 to replace ceph 10.2.0, build-pkgs ceph, then directly run "build-pkgs ceph ". Build-std.log show the following error: 02:01:23 Error: No Package found for CUnit-devel 02:01:23 Error: No Package found for devtoolset-7-gcc-c++ 02:01:23 Error: No Package found for jq 02:01:23 Error: No Package found for libbabeltrace-devel 02:01:23 Error: No Package found for liboath-devel 02:01:23 Error: No Package found for lttng-ust-devel 02:01:23 Error: No Package found for lz4-devel >= 1.7 02:01:23 Error: No Package found for python34-Cython 02:01:23 Error: No Package found for python34-devel 02:01:23 Error: No Package found for python34-setuptools 02:01:23 Error: No Package found for sharutils So, when i check ceph.spec file of 13.2.0, find some new BuildRequests, for example: BuildRequires: CUnit-devel BuildRequires: devtoolset-7-gcc-c++ ...... ...... ...... My methods is as following: Step 1 : wget get corresponding rpm, then put it into mirror's corresponding folder. Step 2: create package link, namely : ln -sf xxxx yyyy Then, when i run build-pkgs ceph again, found that one deps CUnit-devel is resolved, but other package still can't be found. Build-std.log is as following: 02:01:23 Error: No Package found for devtoolset-7-gcc-c++ 02:01:23 Error: No Package found for jq 02:01:23 Error: No Package found for libbabeltrace-devel 02:01:23 Error: No Package found for liboath-devel 02:01:23 Error: No Package found for lttng-ust-devel 02:01:23 Error: No Package found for lz4-devel >= 1.7 02:01:23 Error: No Package found for python34-Cython 02:01:23 Error: No Package found for python34-devel 02:01:23 Error: No Package found for python34-setuptools 02:01:23 Error: No Package found for sharutils So, I want to ask whether this method is correct ? Based on this method, why one package can be resolved and other package can't be found ? Thanks Dehao -------------- next part -------------- An HTML attachment was scrubbed... URL: From dehao.shang at intel.com Mon Sep 10 01:00:53 2018 From: dehao.shang at intel.com (Shang, Dehao) Date: Mon, 10 Sep 2018 01:00:53 +0000 Subject: [Starlingx-discuss] building ceph 13.2.0 In-Reply-To: <9700A18779F35F49AF027300A49E7C7655357BAE@SHSMSX101.ccr.corp.intel.com> References: <71AECFE5078153419EB7B8DBE0644B263863669E@shsmsx102.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C7655357BAE@SHSMSX101.ccr.corp.intel.com> Message-ID: <71AECFE5078153419EB7B8DBE0644B263863679C@shsmsx102.ccr.corp.intel.com> Hi, Shuicheng: I have run "build-pkgs", but error log still showed that can't found corresponding package. Thanks Dehao build-pkgs Log: 16:40:07 Error: No Package found for devtoolset-7-gcc-c++ 16:40:07 Error: No Package found for jq 16:40:07 Error: No Package found for libbabeltrace-devel 16:40:07 Error: No Package found for liboath-devel 16:40:07 Error: No Package found for lttng-ust-devel 16:40:07 Error: No Package found for lz4-devel >= 1.7 16:40:07 Error: No Package found for python34-Cython 16:40:07 Error: No Package found for python34-devel 16:40:07 Error: No Package found for python34-setuptools 16:40:07 Error: No Package found for sharutils 16:40:07 16:40:07 End build on 'b0': /localdisk/loadbuild/dehao/starlingx/std/rpmbuild/SRPMS/ceph-13.2.0-0.el7.tis.1.src.rpm 16:40:07 Error building ceph-13.2.0-0.el7.tis.1.src.rpm on 'b0'. 16:40:07 Will try to build again (if some other package will succeed). 16:40:07 ===== iteration 2 complete ===== 16:40:07 failed=['/localdisk/loadbuild/dehao/starlingx/std/rpmbuild/SRPMS/ceph-13.2.0-0.el7.tis.1.src.rpm'] 16:40:07 to_be_built=['/localdisk/loadbuild/dehao/starlingx/std/rpmbuild/SRPMS/ceph-13.2.0-0.el7.tis.1.src.rpm'] 16:40:07 ===== [dehao at 9f9456a3d92b cgcs-root]$ ls cgcs-centos-repo/Binary/x86_64/devtoolset-7-gcc-c++-7.3.1-5.10.el7.x86_64.rpm cgcs-centos-repo/Binary/x86_64/devtoolset-7-gcc-c++-7.3.1-5.10.el7.x86_64.rpm [dehao at 9f9456a3d92b cgcs-root]$ ll cgcs-centos-repo/Binary/x86_64/devtoolset-7-gcc-c++-7.3.1-5.10.el7.x86_64.rpm lrwxrwxrwx 1 root root 102 Sep 8 20:11 cgcs-centos-repo/Binary/x86_64/devtoolset-7-gcc-c++-7.3.1-5.10.el7.x86_64.rpm -> /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/x86_64/devtoolset-7-gcc-c++-7.3.1-5.10.el7.x86_64.rpm [dehao at 9f9456a3d92b cgcs-root]$ ll cgcs-centos-repo/Binary/x86_64/libbabeltrace-devel-1.2.4-3.el7.x86_64.rpm lrwxrwxrwx 1 root root 98 Sep 8 20:39 cgcs-centos-repo/Binary/x86_64/libbabeltrace-devel-1.2.4-3.el7.x86_64.rpm -> /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/x86_64/libbabeltrace-devel-1.2.4-3.el7.x86_64.rpm [dehao at 9f9456a3d92b cgcs-root]$ ll cgcs-centos-repo/Binary/x86_64/lldpad-1.0.1-3.git036e314.el7.x86_64.rpm lrwxrwxrwx 1 dehao cgts 96 Sep 8 19:47 cgcs-centos-repo/Binary/x86_64/lldpad-1.0.1-3.git036e314.el7.x86_64.rpm -> /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/x86_64/lldpad-1.0.1-3.git036e314.el7.x86_64.rpm From: Lin, Shuicheng Sent: Monday, September 10, 2018 8:41 AM To: Shang, Dehao ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] building ceph 13.2.0 Hi Dehao, Please have a try with "build-pkgs" after "ln -sf xxxx yyyy". The reason is the build system will search the package from the repodata, and "build-pkgs" will add the new package to the repodata. Best Regards Shuicheng From: Shang, Dehao [mailto:dehao.shang at intel.com] Sent: Sunday, September 9, 2018 9:13 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] building ceph 13.2.0 Hi: I re-setup new building environment, and can successfully build starlingx image. Based on this new environments, I directly use ceph 13.2.0 to replace ceph 10.2.0, build-pkgs ceph, then directly run "build-pkgs ceph ". Build-std.log show the following error: 02:01:23 Error: No Package found for CUnit-devel 02:01:23 Error: No Package found for devtoolset-7-gcc-c++ 02:01:23 Error: No Package found for jq 02:01:23 Error: No Package found for libbabeltrace-devel 02:01:23 Error: No Package found for liboath-devel 02:01:23 Error: No Package found for lttng-ust-devel 02:01:23 Error: No Package found for lz4-devel >= 1.7 02:01:23 Error: No Package found for python34-Cython 02:01:23 Error: No Package found for python34-devel 02:01:23 Error: No Package found for python34-setuptools 02:01:23 Error: No Package found for sharutils So, when i check ceph.spec file of 13.2.0, find some new BuildRequests, for example: BuildRequires: CUnit-devel BuildRequires: devtoolset-7-gcc-c++ ...... ...... ...... My methods is as following: Step 1 : wget get corresponding rpm, then put it into mirror's corresponding folder. Step 2: create package link, namely : ln -sf xxxx yyyy Then, when i run build-pkgs ceph again, found that one deps CUnit-devel is resolved, but other package still can't be found. Build-std.log is as following: 02:01:23 Error: No Package found for devtoolset-7-gcc-c++ 02:01:23 Error: No Package found for jq 02:01:23 Error: No Package found for libbabeltrace-devel 02:01:23 Error: No Package found for liboath-devel 02:01:23 Error: No Package found for lttng-ust-devel 02:01:23 Error: No Package found for lz4-devel >= 1.7 02:01:23 Error: No Package found for python34-Cython 02:01:23 Error: No Package found for python34-devel 02:01:23 Error: No Package found for python34-setuptools 02:01:23 Error: No Package found for sharutils So, I want to ask whether this method is correct ? Based on this method, why one package can be resolved and other package can't be found ? Thanks Dehao -------------- next part -------------- An HTML attachment was scrubbed... URL: From huifeng.le at intel.com Mon Sep 10 02:04:35 2018 From: huifeng.le at intel.com (Le, Huifeng) Date: Mon, 10 Sep 2018 02:04:35 +0000 Subject: [Starlingx-discuss] Analysis report about Network Trunk feature for StartlingX upstreaming In-Reply-To: References: <76647BD697F40748B1FA4F56DA02AA0B4D4EB222@SHSMSX104.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB577F1B@fmsmsx115.amr.corp.intel.com> <76647BD697F40748B1FA4F56DA02AA0B4D4EB495@SHSMSX104.ccr.corp.intel.com> <304C67CB-BAE4-4E42-A613-1C848535F166@windriver.com> <76647BD697F40748B1FA4F56DA02AA0B4D4EDBFE@SHSMSX104.ccr.corp.intel.com> Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D4F001D@SHSMSX104.ccr.corp.intel.com> Matt, Thanks much for the comments! Some comments for upstream in line, please help to review, thanks! Best Regards, Le, Huifeng From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Friday, September 7, 2018 11:01 PM To: Le, Huifeng ; Jolliffe, Ian ; Jones, Bruce E ; Rowsell, Brent Cc: Zhao, Forrest ; Troyer, Dean ; starlingx-discuss at lists.starlingx.io Subject: RE: Analysis report about Network Trunk feature for StartlingX upstreaming See inline for specific responses to the review information. Responses marked with [MP>] From: Le, Huifeng [mailto:huifeng.le at intel.com] Sent: Sunday, August 19, 2018 10:32 PM To: Jolliffe, Ian; Jones, Bruce E; Rowsell, Brent; Peters, Matt Cc: Zhao, Forrest; Troyer, Dean; starlingx-discuss at lists.starlingx.io Subject: RE: Analysis report about Network Trunk feature for StartlingX upstreaming Ian, Thanks very much for the comments. some comments below for you reference, and please help to review, thanks much! Best Regards, Le, Huifeng From: Jolliffe, Ian [mailto:Ian.Jolliffe at windriver.com] Sent: Saturday, August 18, 2018 4:16 AM To: Le, Huifeng >; Jones, Bruce E >; Rowsell, Brent >; Peters, Matt > Cc: Zhao, Forrest >; Troyer, Dean >; starlingx-discuss at lists.starlingx.io Subject: Re: Analysis report about Network Trunk feature for StartlingX upstreaming Hi Huifeng; Thanks for the updates/analysis, comments below. Ian Ian/Brent/Matt, We did analysis about the Network trunk related patches for StartingX upstream, below are the suggestions for upstreaming, could you please help to review and comment? Thanks much! 1. ba9d9f60a7a2665194cacb92a05e0acd2dc3de41: Add rpc notification for trunk updates Function: sent notification to the agent when a trunk is updated Analysis: (1)Trunk’s AFTER_UPDATE event is generated for API call: PUT /v2.0/trunks/{trunk-id} The update request is only for changing fields like name, description or admin_state_up. Setting the admin_state_up to False locks the trunk in that it prevents operations such as adding/removing subports. In Neutron upstream, admin_state_up is used in server side, e.g. add_subports, remove subports, delete_trunk and not used in agent side (2)OVS trunk agent driver uses OVSDB event to handle trunk event, no need to manually trigger trunk update event (3)Linux trunk agent driver will handle trunk update event triggered by server, while it will need apply the patch only in case admin_state_up update need to be handled Suggestion: Not a bug for Neutron upstream, suggest not to upstream If this is not upstreamed, are the dependencies or changes required in the StarlingX code base? What are the implications of not upstreaming? [hle2] for STX, trunk_updated event will force the trunk’s parent-port to refresh (e.g. handle_trunks->mark_port_for_refresh(trunk['port_id']) etc.) to get the new “admin_state_up” value from server and this value will be used in handle_updated_port() to determine whether it is allowed to update port/device status in server side. “admin_state_up” is mainly used to control operation at neutron server side like add_subports, remove subports, delete_trunk etc. and all these 3 operations will force port to refresh (handle_trunks/handle_subports->mark_port_for_refresh), so suppose, the general flow will not be impacted whether to handle trunk_updated event or not. But in some wired cases, add “admin_state_up” check in agent side may cause issues (please help to review whether it is make sense), e.g for below calling flow (suppose trunk’s ‘admin_state_up’ is ‘up’): (1) add_subports (2) set “admin_state_up” to ‘down’, step(1) may fail to set device’s state at agent side in case aws agent’s handle_updated_port() (in daemon loop) executed after step (2) So to my understanding: (1) if using OVS agent in STX, no impact for not upstream (2) if using AVS agent + STX, suggest removing “admin_state_up” check in AVS agent (in function handle_updated_port () of avs/agent.py) like below. if trunk_details and trunk_details['admin_state_up']: … [MP>] Thanks for the detailed analysis. The suggested change will need to be tested to see if it full resolves the original issue. However, since the driver could be used by other agents (beyond just the AVS agent), I think it would not hurt to have the additional notification sent to complete the driver definition for the set of RPC notifications. [hle2] yes, it is not hurt to have additional notification sent to complete the driver definition for PRC notification. And do you think it is need for upstream in case it is not a bug for OVS and linux bridge driver? if yes, do you have any strong reason which can convince community to buy in the change? Thanks! 2. 6955351c5eca6e37061fb0140d11ea53693fe0e1: Add support to delete bound network Function: enable delete trunk if it is can_be_trunked (not bounded or driver’s can_trunk_bound_port=true) Analysis: Applied for LinuxBridge Driver and AVS bridge Driver (can_trunk_bound_port=True), no impact for OVSTrunkDriver (can_trunk_bound_port=False). workaround also available for linux bridge (e.g. unbind the port first then delete the trunk) Suggestion: it is a low priority bug for Neutron upstream (only applied for linux bridge and workround available), suggest not to upstream I think you need to propose a fix. Or this will need to be carried long term. [hle2] yes, let’s try to propose a fix for upstream. [MP>] Agree. [hle2] Since this issue is not applied for OVS/OVS DPDK, suggest to put it as low priority and try to solve it after other high issues. make sense? 3. 43a684946e781a25d21a4f50b8dc67d61be42809: Enable trunk service by default Function: add “trunk” in DEFAULT_SERVICE_PLUGINS Analysis: It is a deploy configuration for downstream product Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. 4. c54d804792f10b7f505de6794274c4df4768f6f0: Include trunk presence in port details Function: add trunk_port (bool) flag in port_details to identify whether this port is a parent port for a trunk Analysis: It is a performance improvement for AVS agent by reducing RPC call from agent to server. OVS agent has different implementation with no improvement by introducing this field Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. 5. 3eed837ebd236e6b1959ea88d9ab5322c9eef6b9: Ignore trunk subports on same vlan as vlan-subnet ports Function: Ignore trunk subports on same vlan as vlan-subnet ports Analysis: It is a bug fix for AVS agent Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Teresa.Ho at windriver.com Mon Sep 10 03:31:02 2018 From: Teresa.Ho at windriver.com (Ho, Teresa) Date: Mon, 10 Sep 2018 03:31:02 +0000 Subject: [Starlingx-discuss] Heads up: interface and network configuration changes Message-ID: <918130236148D14B982C7B8BC1C06EA16710C9E0@ALA-MBD.corp.ad.wrs.com> This is to inform you that the upcoming feature story "Generalized interface and network configuration" will impact system setup. A review will be posted shortly. For more background information, please refer to the Story: https://storyboard.openstack.org/#!/story/2003087 The following describes the user interface changes for interface and network configuration. * Network CLI commands * The parameters mtu, link_capacity and vlan_id are removed from the network table * New network-add and network-delete usage: system network-add Add a network. Positional arguments: Name of network [REQUIRED] Type of network [REQUIRED] dynamic [REQUIRED] The uuid of the address pool [REQUIRED] usage: system network-delete Delete a network Positional arguments: UUID of network entry * Interface CLI commands * The new interface class parameter replaces the existing networktype parameter. usage: system host-if-add [-a ] [-x ] [-V ] [-m ] [-c ] [--networks ] [--ipv4-mode ] [--ipv6-mode ] [--ipv4-pool ] [--ipv6-pool ] [] [] [ ...] Add an interface. Positional arguments: Name or ID of host [REQUIRED] Name of interface [REQUIRED] Type of the interface The provider network attached to the interface (default: None) [REQUIRED when interface class is data or pci-passthrough Name of port(s) or interface(s) [REQUIRED] Optional arguments: -a , --aemode The AE mode (balanced or active_standby or 802.3ad) -x , --txhashpolicy The balanced tx distribution hash policy -V , --vlan_id The VLAN id of the interface -m , --imtu The MTU of the interface -c , --ifclass The class of the interface --networks Name or ID of network --ipv4-mode The IPv4 address mode of the interface --ipv6-mode The IPv6 address mode of the interface --ipv4-pool The IPv4 address pool name or uuid if mode is set to 'pool' --ipv6-pool The IPv6 address pool name or uuid if mode is set to 'pool' usage: system host-if-modify [-n ] [-m ] [-p ] [-a ] [-x ] [-c ] [--networks ] [--ipv4-mode ] [--ipv6-mode ] [--ipv4-pool ] [--ipv6-pool ] [-N ] Modify interface attributes. Positional arguments: Name or ID of host [REQUIRED] Name or UUID of interface [REQUIRED] Optional arguments: -n , --ifname The new name of the interface -m , --imtu The MTU of the interface -p , --providernetworks The provider network attached to the interface [REQUIRED] -a , --aemode The AE mode (balanced or active_standby or 802.3ad) -x , --txhashpolicy The balanced tx distribution hash policy -c , --ifclass The class of the interface --networks Name or ID of network --ipv4-mode The IPv4 address mode of the interface --ipv6-mode The IPv6 address mode of the interface --ipv4-pool The IPv4 address pool name or uuid if mode is set to 'pool' --ipv6-pool The IPv6 address pool name or uuid if mode is set to 'pool' -N , --num-vfs The number of SR-IOV VFs of the interface * Interface network associations Multiple networks can be assigned to an interface. usage: system interface-network-assign Assign a network to an interface. Positional arguments: Name or ID of host [REQUIRED] Name of interface [REQUIRED] Name of UUID of IP network [REQUIRED] usage: system interface-network-remove Remove an assigned network from an interface. Positional arguments: UUID of interface network entry Teresa Ho -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Mon Sep 10 03:56:15 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Mon, 10 Sep 2018 03:56:15 +0000 Subject: [Starlingx-discuss] building ceph 13.2.0 In-Reply-To: <71AECFE5078153419EB7B8DBE0644B263863679C@shsmsx102.ccr.corp.intel.com> References: <71AECFE5078153419EB7B8DBE0644B263863669E@shsmsx102.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C7655357BAE@SHSMSX101.ccr.corp.intel.com> <71AECFE5078153419EB7B8DBE0644B263863679C@shsmsx102.ccr.corp.intel.com> Message-ID: Hi, This is something that you might need to try inside mock. To go into mock run: $ cd /localdisk/loadbuild///std # First, copy the SRPM of ceph into mock $ mock -r --tis-r5-pike-std.cfg –copyin /tmp # I like to use /tmp but it could be whatever path you like. # Start a shell in mock $ mock -r --tis-r5-pike-std.cfg --shell # the initial startup will install a set of default packages. # then try to build your srpm with rpmbuild $ cd /tmp; rpmbuild --rebuild .src.rpm # Try to install missing dependencies with yum, here you can install the missing devtoolset-7-gcc-c++ package. # If you look into the /etc/yum.conf file you’ll see that the cgcs-centos-repo file is set as a repository served through a web server, you can see if the package is actually there. I hope this can help. -Erich From: "Shang, Dehao" Date: Sunday, September 9, 2018 at 8:02 PM To: "Lin, Shuicheng" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] building ceph 13.2.0 Hi, Shuicheng: I have run “build-pkgs”, but error log still showed that can’t found corresponding package. Thanks Dehao build-pkgs Log: 16:40:07 Error: No Package found for devtoolset-7-gcc-c++ 16:40:07 Error: No Package found for jq 16:40:07 Error: No Package found for libbabeltrace-devel 16:40:07 Error: No Package found for liboath-devel 16:40:07 Error: No Package found for lttng-ust-devel 16:40:07 Error: No Package found for lz4-devel >= 1.7 16:40:07 Error: No Package found for python34-Cython 16:40:07 Error: No Package found for python34-devel 16:40:07 Error: No Package found for python34-setuptools 16:40:07 Error: No Package found for sharutils 16:40:07 16:40:07 End build on 'b0': /localdisk/loadbuild/dehao/starlingx/std/rpmbuild/SRPMS/ceph-13.2.0-0.el7.tis.1.src.rpm 16:40:07 Error building ceph-13.2.0-0.el7.tis.1.src.rpm on 'b0'. 16:40:07 Will try to build again (if some other package will succeed). 16:40:07 ===== iteration 2 complete ===== 16:40:07 failed=['/localdisk/loadbuild/dehao/starlingx/std/rpmbuild/SRPMS/ceph-13.2.0-0.el7.tis.1.src.rpm'] 16:40:07 to_be_built=['/localdisk/loadbuild/dehao/starlingx/std/rpmbuild/SRPMS/ceph-13.2.0-0.el7.tis.1.src.rpm'] 16:40:07 ===== [dehao at 9f9456a3d92b cgcs-root]$ ls cgcs-centos-repo/Binary/x86_64/devtoolset-7-gcc-c++-7.3.1-5.10.el7.x86_64.rpm cgcs-centos-repo/Binary/x86_64/devtoolset-7-gcc-c++-7.3.1-5.10.el7.x86_64.rpm [dehao at 9f9456a3d92b cgcs-root]$ ll cgcs-centos-repo/Binary/x86_64/devtoolset-7-gcc-c++-7.3.1-5.10.el7.x86_64.rpm lrwxrwxrwx 1 root root 102 Sep 8 20:11 cgcs-centos-repo/Binary/x86_64/devtoolset-7-gcc-c++-7.3.1-5.10.el7.x86_64.rpm -> /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/x86_64/devtoolset-7-gcc-c++-7.3.1-5.10.el7.x86_64.rpm [dehao at 9f9456a3d92b cgcs-root]$ ll cgcs-centos-repo/Binary/x86_64/libbabeltrace-devel-1.2.4-3.el7.x86_64.rpm lrwxrwxrwx 1 root root 98 Sep 8 20:39 cgcs-centos-repo/Binary/x86_64/libbabeltrace-devel-1.2.4-3.el7.x86_64.rpm -> /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/x86_64/libbabeltrace-devel-1.2.4-3.el7.x86_64.rpm [dehao at 9f9456a3d92b cgcs-root]$ ll cgcs-centos-repo/Binary/x86_64/lldpad-1.0.1-3.git036e314.el7.x86_64.rpm lrwxrwxrwx 1 dehao cgts 96 Sep 8 19:47 cgcs-centos-repo/Binary/x86_64/lldpad-1.0.1-3.git036e314.el7.x86_64.rpm -> /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/x86_64/lldpad-1.0.1-3.git036e314.el7.x86_64.rpm From: Lin, Shuicheng Sent: Monday, September 10, 2018 8:41 AM To: Shang, Dehao ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] building ceph 13.2.0 Hi Dehao, Please have a try with “build-pkgs” after “ln –sf xxxx yyyy”. The reason is the build system will search the package from the repodata, and “build-pkgs” will add the new package to the repodata. Best Regards Shuicheng From: Shang, Dehao [mailto:dehao.shang at intel.com] Sent: Sunday, September 9, 2018 9:13 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] building ceph 13.2.0 Hi: I re-setup new building environment, and can successfully build starlingx image. Based on this new environments, I directly use ceph 13.2.0 to replace ceph 10.2.0, build-pkgs ceph, then directly run “build-pkgs ceph ”. Build-std.log show the following error: 02:01:23 Error: No Package found for CUnit-devel 02:01:23 Error: No Package found for devtoolset-7-gcc-c++ 02:01:23 Error: No Package found for jq 02:01:23 Error: No Package found for libbabeltrace-devel 02:01:23 Error: No Package found for liboath-devel 02:01:23 Error: No Package found for lttng-ust-devel 02:01:23 Error: No Package found for lz4-devel >= 1.7 02:01:23 Error: No Package found for python34-Cython 02:01:23 Error: No Package found for python34-devel 02:01:23 Error: No Package found for python34-setuptools 02:01:23 Error: No Package found for sharutils So, when i check ceph.spec file of 13.2.0, find some new BuildRequests, for example: BuildRequires: CUnit-devel BuildRequires: devtoolset-7-gcc-c++ …… …… …… My methods is as following: Step 1 : wget get corresponding rpm, then put it into mirror’s corresponding folder. Step 2: create package link, namely : ln –sf xxxx yyyy Then, when i run build-pkgs ceph again, found that one deps CUnit-devel is resolved, but other package still can’t be found. Build-std.log is as following: 02:01:23 Error: No Package found for devtoolset-7-gcc-c++ 02:01:23 Error: No Package found for jq 02:01:23 Error: No Package found for libbabeltrace-devel 02:01:23 Error: No Package found for liboath-devel 02:01:23 Error: No Package found for lttng-ust-devel 02:01:23 Error: No Package found for lz4-devel >= 1.7 02:01:23 Error: No Package found for python34-Cython 02:01:23 Error: No Package found for python34-devel 02:01:23 Error: No Package found for python34-setuptools 02:01:23 Error: No Package found for sharutils So, I want to ask whether this method is correct ? Based on this method, why one package can be resolved and other package can’t be found ? Thanks Dehao -------------- next part -------------- An HTML attachment was scrubbed... URL: From scottk at optimcloud.com Mon Sep 10 03:57:40 2018 From: scottk at optimcloud.com (scottk at optimcloud.com) Date: Mon, 10 Sep 2018 03:57:40 +0000 Subject: [Starlingx-discuss] Fedora Libvirt patch - required to deploy on Fedora 28, probably other non-ubuntu specific Message-ID: <81e0cc73b05fc5eb4a44939c8769dbd3@optimcloud.com> sending in my fedora modifications needed to spin up on Fedora 28, removing the Ubuntu specific items, created on my local tree with git format-patch -1 437353d3b108e7a92c0d5c48c81d334f07940dc3 (the git rev is my specific commit to my local tree) noted the machine='pc-i440fx-xenial' and seclabel pieces are not required in Fedora, also note in the docs Installing Requirements and Dependencies Install the required packages and configure QEMU. This only needs to be done once per host. (NOTE: this script only knows about Ubuntu at this time): $SCRIPTS/install_packages.sh the above breaks permissions on libvirt in Fedora and most likely others rendering it useless we dont use user = "root" group = "root" and obviously, we (IMHO) shouldnt be running it as group root anyway, in Fedora there is a libvirt group 0001-fixup-for-fedora.patch From 437353d3b108e7a92c0d5c48c81d334f07940dc3 Mon Sep 17 00:00:00 2001 From: OutBack Dingo Date: Mon, 10 Sep 2018 05:46:58 +0200 Subject: [PATCH] fixup for fedora --- deployment/libvirt/compute.xml | 6 +----- deployment/libvirt/controller.xml | 6 +----- deployment/libvirt/controller_allinone.xml | 6 +----- deployment/libvirt/setup_allinone.sh | 4 ---- 4 files changed, 3 insertions(+), 19 deletions(-) diff --git a/deployment/libvirt/compute.xml b/deployment/libvirt/compute.xml index 85474c0..4bdc812 100644 --- a/deployment/libvirt/compute.xml +++ b/deployment/libvirt/compute.xml @@ -7,7 +7,7 @@ /machine - hvm + hvm @@ -108,8 +108,4 @@
- - - libvirt-608ab5c8-8d11-4bdd-885f-f8b5fee12ff0 - diff --git a/deployment/libvirt/controller.xml b/deployment/libvirt/controller.xml index e346813..65c4d01 100644 --- a/deployment/libvirt/controller.xml +++ b/deployment/libvirt/controller.xml @@ -7,7 +7,7 @@ /machine - hvm + hvm @@ -122,9 +122,5 @@
- - - libvirt-6afab2ba-0ed0-45cb-b1bd-985e211a48de - diff --git a/deployment/libvirt/controller_allinone.xml b/deployment/libvirt/controller_allinone.xml index 9249183..83e8fe6 100644 --- a/deployment/libvirt/controller_allinone.xml +++ b/deployment/libvirt/controller_allinone.xml @@ -7,7 +7,7 @@ /machine - hvm + hvm @@ -122,9 +122,5 @@
- - - libvirt-6afab2ba-0ed0-45cb-b1bd-985e211a48de - diff --git a/deployment/libvirt/setup_allinone.sh b/deployment/libvirt/setup_allinone.sh index b228efc..dcf1607 100755 --- a/deployment/libvirt/setup_allinone.sh +++ b/deployment/libvirt/setup_allinone.sh @@ -28,10 +28,6 @@ fi ISOIMAGE=$(readlink -f "$ISOIMAGE") FILETYPE=$(file --mime-type -b ${ISOIMAGE}) -if ([ "$FILETYPE" != "application/x-iso9660-image" ]); then - echo "$ISOIMAGE is not an application/x-iso9660-image type" - exit -1 -fi BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr} CONTROLLER=${CONTROLLER:-controller-allinone} -- 2.17.1 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-fixup-for-fedora.patch Type: application/octet-stream Size: 3349 bytes Desc: not available URL: From erich.cordoba.malibran at intel.com Mon Sep 10 04:15:52 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Mon, 10 Sep 2018 04:15:52 +0000 Subject: [Starlingx-discuss] Fedora Libvirt patch - required to deploy on Fedora 28, probably other non-ubuntu specific In-Reply-To: <81e0cc73b05fc5eb4a44939c8769dbd3@optimcloud.com> References: <81e0cc73b05fc5eb4a44939c8769dbd3@optimcloud.com> Message-ID: Hi, Thanks for the patch. I'm also using Fedora for the deployment and I've seen this problems as well as other in the creation of the docker images[0] for building. This part of the building and deployment process is in an early stage of development and thus, there are bugs and lack of functionality on some parts. Like you pointed out, the support for more flavors in hosts for virtual deployments is one of the missing parts and we are happy to receive feedback :) What you think about sending this patch as a review for the stx-tools[1] repository? It would be good to have it landed. Anyway, I have two open questions regarding you patch (not necessary question to you). 1) Is it possible to remove the seclabel from the ubuntu version as well? Having this will block us to have these xml definitions, we would need to "generate" this xml files based on the host that we will use. 2) Why was needed to remove the check for "application/x-iso9660-image"? Thanks again for all your feedback. -Erich [0] https://storyboard.openstack.org/#!/story/2002560 [1] http://git.starlingx.io/cgit/stx-tools From: "scottk at optimcloud.com" Date: Sunday, September 9, 2018 at 10:57 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Fedora Libvirt patch - required to deploy on Fedora 28, probably other non-ubuntu specific From scottk at optimcloud.com Mon Sep 10 06:03:59 2018 From: scottk at optimcloud.com (scottk at optimcloud.com) Date: Mon, 10 Sep 2018 06:03:59 +0000 Subject: [Starlingx-discuss] Fedora Libvirt patch - required to deploy on Fedora 28, probably other non-ubuntu specific In-Reply-To: References: <81e0cc73b05fc5eb4a44939c8769dbd3@optimcloud.com> Message-ID: <1c7da17a35add8d68c2fb03c7fdd0356@optimcloud.com> September 10, 2018 6:16 AM, "Cordoba Malibran, Erich" wrote: > Hi, > > Thanks for the patch. I'm also using Fedora for the deployment and I've seen this problems as well > as other in the creation of the docker images[0] for building. I had 0 issues creating the docker images on fedora 28 that was all pretty straight forward using docker-ce other then some things in the guide from inside the image, after they got fixed up i did get an iso > > This part of the building and deployment process is in an early stage of development and thus, > there are bugs and lack of functionality on some parts. Like you pointed out, the support for more > flavors in hosts for virtual deployments is one of the missing parts and we are happy to receive > feedback :) My thoughts as well but it seems these were the tools used originally for the work, i believe its now they are starting to work slowly towards a more generic structure > > What you think about sending this patch as a review for the stx-tools[1] repository? It would be > good to have it landed. Id be happy to even help further, and forward it to the list, but I would prefer to wait for the invite, plus i probably need creds and such setup so i could. Its gone to the mailing list as of now, they also from a prior email have already negated the libvirt iso file check https://github.com/Nossiac/mtk-openwrt-feeds/blob/master/about-mtk-wifi.md it plainly didnt work on my system, as soon as it was removed it moved me forward > Anyway, I have two open questions regarding you patch (not necessary question to you). > 1) Is it possible to remove the seclabel from the ubuntu version as well? Having this will block us > to have these xml definitions, we would need to "generate" this xml files based on the host that we > will use. Youll see in my patch i also edited the XML defs, across the board i belive they can also be made more generic and still be functional > 2) Why was needed to remove the check for "application/x-iso9660-image"? The call simply errored out on my system under KDE, its a mime-type def also i dont see what it would be required, as we could use gcow2 or raw filesystem images also in the future. I saw it as not needed. > Thanks again for all your feedback. > > -Erich > > [0] https://storyboard.openstack.org/#!/story/2002560 > [1] http://git.starlingx.io/cgit/stx-tools > > From: "scottk at optimcloud.com" > Date: Sunday, September 9, 2018 at 10:57 PM > To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Fedora Libvirt patch - required to deploy on Fedora 28, probably other > non-ubuntu specific From dtroyer at gmail.com Mon Sep 10 07:31:45 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 10 Sep 2018 02:31:45 -0500 Subject: [Starlingx-discuss] Fedora Libvirt patch - required to deploy on Fedora 28, probably other non-ubuntu specific In-Reply-To: <1c7da17a35add8d68c2fb03c7fdd0356@optimcloud.com> References: <81e0cc73b05fc5eb4a44939c8769dbd3@optimcloud.com> <1c7da17a35add8d68c2fb03c7fdd0356@optimcloud.com> Message-ID: On Mon, Sep 10, 2018 at 1:03 AM, wrote: > Id be happy to even help further, and forward it to the list, but I would prefer to wait for the invite, plus i probably need creds and such setup so i could. Here is your invitation. Some legal theories say that we are unable to contribute your patch from an email to Gerrit because the required declarations are not met with that process. No matter, we want to encourage direct contributions anyway. You need to set up an Ubuntu One account (I know, right?) because that is what OpenStack's Gerrit (which we also use) uses for single sign-on. If you have one already, great! The steps to setting up Gerrit are in the "Account Setup" section of the OpenStack Developer's Guide [0] One thing that StarlingX does do differently than OpenStack is we require a Signed-Off-By footer in the commit messages, which of course git will do for you with 'git commit -s'. > Its gone to the mailing list as of now, they also from a prior email have already negated the libvirt iso file check > > https://github.com/Nossiac/mtk-openwrt-feeds/blob/master/about-mtk-wifi.md As much as I love OpenWRT this doesn't seem to be the link you intended... dt [0] https://docs.openstack.org/infra/manual/developers.html#account-setup -- Dean Troyer dtroyer at gmail.com From scottk at optimcloud.com Mon Sep 10 07:44:59 2018 From: scottk at optimcloud.com (scottk at optimcloud.com) Date: Mon, 10 Sep 2018 07:44:59 +0000 Subject: [Starlingx-discuss] Fedora Libvirt patch - required to deploy on Fedora 28, probably other non-ubuntu specific In-Reply-To: References: <81e0cc73b05fc5eb4a44939c8769dbd3@optimcloud.com> <1c7da17a35add8d68c2fb03c7fdd0356@optimcloud.com> Message-ID: <54df6d7f5d6e9ee36dc7365c895b852e@optimcloud.com> September 10, 2018 9:31 AM, "Dean Troyer" wrote: > On Mon, Sep 10, 2018 at 1:03 AM, wrote: > >> Id be happy to even help further, and forward it to the list, but I would prefer to wait for the >> invite, plus i probably need creds and such setup so i could. > > Here is your invitation. Some legal theories say that we are unable > to contribute your patch from an email to Gerrit because the required > declarations are not met with that process. No matter, we want to > encourage direct contributions anyway. > > You need to set up an Ubuntu One account (I know, right?) because that OOOOMG..... my furby just burst into flames..... > is what OpenStack's Gerrit (which we also use) uses for single > sign-on. If you have one already, great! The steps to setting up > Gerrit are in the "Account Setup" section of the OpenStack Developer's > Guide [0] I probably have a UBONE account from previous work ages ago :) > > One thing that StarlingX does do differently than OpenStack is we > require a Signed-Off-By footer in the commit messages, which of course > git will do for you with 'git commit -s'. > Yupp got it.... same for WRT, and others :) >> Its gone to the mailing list as of now, they also from a prior email have already negated the >> libvirt iso file check >> >> https://github.com/Nossiac/mtk-openwrt-feeds/blob/master/about-mtk-wifi.md > > As much as I love OpenWRT this doesn't seem to be the link you intended... LOL no it wasnt, the link i intended was https://review.openstack.org/600877 > > dt > > [0] https://docs.openstack.org/infra/manual/developers.html#account-setup > > -- > > Dean Troyer > dtroyer at gmail.com From dehao.shang at intel.com Mon Sep 10 12:41:14 2018 From: dehao.shang at intel.com (Shang, Dehao) Date: Mon, 10 Sep 2018 12:41:14 +0000 Subject: [Starlingx-discuss] python interpreter version problem. Message-ID: <71AECFE5078153419EB7B8DBE0644B26386368D2@shsmsx102.ccr.corp.intel.com> Hi, When upgrading ceph to 13.2.0, i have resolved all deps package of new package, but now being stuck at python interpreter version. Now, starlingx just support python2, and don't support more high python version. But ceph 13.2.0 need python3 interpreter to interpret corresponding ceph package. I have tried to modify python3 into python2.7 at ceph.spec file, but still don't work. Does anyone know how to resolve it? Thanks for your help. build-std.log : -- Performing Test COMPILER_SUPPORTS_GNU99 -- Performing Test COMPILER_SUPPORTS_GNU99 - Success -- Performing Test HAVE_STDLIB_MAP_SPLICING -- Performing Test HAVE_STDLIB_MAP_SPLICING - Success -- Performing Test COMPILER_SUPPORTS_DIAGNOSTICS_COLOR -- Performing Test COMPILER_SUPPORTS_DIAGNOSTICS_COLOR - Success -- Ceph/.git directory not found, parsing /builddir/build/BUILD/ceph-13.2.0/src/.git_version for CEPH_GIT_VER and CEPH_GIT_NICE_VER BUILDSTDERR: CMake Error at src/CMakeLists.txt:241 (file): BUILDSTDERR: file STRINGS file "/builddir/build/BUILD/ceph-13.2.0/src/.git_version" BUILDSTDERR: cannot be read. -- Found Java: /bin/java (found version "1.8.0.144") -- Found JNI: /usr/lib/jvm/jre/lib/amd64/libjawt.so -- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.5", minimum required is "2") -- Found PythonLibs: /usr/lib64/libpython2.7.so (found suitable version "2.7.5", minimum required is "2") BUILDSTDERR: CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:108 (message): BUILDSTDERR: Could NOT find Python3Interp: Found unsuitable version "2.7.5", but BUILDSTDERR: required is at least "3" (found /usr/bin/python) BUILDSTDERR: Call Stack (most recent call first): BUILDSTDERR: /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:313 (_FPHSA_FAILURE_MESSAGE) BUILDSTDERR: cmake/modules/FindPython3Interp.cmake:146 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) BUILDSTDERR: src/CMakeLists.txt:282 (find_package) -- Configuring incomplete, errors occurred! See also "/builddir/build/BUILD/ceph-13.2.0/build/CMakeFiles/CMakeOutput.log". See also "/builddir/build/BUILD/ceph-13.2.0/build/CMakeFiles/CMakeError.log". RPM build errors: BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.IJLMMD (%build) BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.IJLMMD (%build) Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line 96, in trace result = func(*args, **kw) File "/usr/lib/python2.7/site-packages/mockbuild/util.py", line 634, in do raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode) Error: Command failed: # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/ceph.spec -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Mon Sep 10 13:11:36 2018 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Mon, 10 Sep 2018 13:11:36 +0000 Subject: [Starlingx-discuss] python interpreter version problem. In-Reply-To: <71AECFE5078153419EB7B8DBE0644B26386368D2@shsmsx102.ccr.corp.intel.com> References: <71AECFE5078153419EB7B8DBE0644B26386368D2@shsmsx102.ccr.corp.intel.com> Message-ID: I downloaded the src rpm for ceph 13.2.0 and extracted it to look at the ceph.spec file I think this section is giving you grief. %if 0%{?suse_version} >= 1500 %bcond_with python2 %else %bcond_without python2 %endif %if 0%{without python2} %global _defined_if_python2_absent 1 %endif By not setting "defined_if_python2_absent" it should use the python2 code, as far as I can tell. See what happens if you comment it out, or remove it. Al From: Shang, Dehao [mailto:dehao.shang at intel.com] Sent: Monday, September 10, 2018 8:41 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] python interpreter version problem. Hi, When upgrading ceph to 13.2.0, i have resolved all deps package of new package, but now being stuck at python interpreter version. Now, starlingx just support python2, and don't support more high python version. But ceph 13.2.0 need python3 interpreter to interpret corresponding ceph package. I have tried to modify python3 into python2.7 at ceph.spec file, but still don't work. Does anyone know how to resolve it? Thanks for your help. build-std.log : -- Performing Test COMPILER_SUPPORTS_GNU99 -- Performing Test COMPILER_SUPPORTS_GNU99 - Success -- Performing Test HAVE_STDLIB_MAP_SPLICING -- Performing Test HAVE_STDLIB_MAP_SPLICING - Success -- Performing Test COMPILER_SUPPORTS_DIAGNOSTICS_COLOR -- Performing Test COMPILER_SUPPORTS_DIAGNOSTICS_COLOR - Success -- Ceph/.git directory not found, parsing /builddir/build/BUILD/ceph-13.2.0/src/.git_version for CEPH_GIT_VER and CEPH_GIT_NICE_VER BUILDSTDERR: CMake Error at src/CMakeLists.txt:241 (file): BUILDSTDERR: file STRINGS file "/builddir/build/BUILD/ceph-13.2.0/src/.git_version" BUILDSTDERR: cannot be read. -- Found Java: /bin/java (found version "1.8.0.144") -- Found JNI: /usr/lib/jvm/jre/lib/amd64/libjawt.so -- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.5", minimum required is "2") -- Found PythonLibs: /usr/lib64/libpython2.7.so (found suitable version "2.7.5", minimum required is "2") BUILDSTDERR: CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:108 (message): BUILDSTDERR: Could NOT find Python3Interp: Found unsuitable version "2.7.5", but BUILDSTDERR: required is at least "3" (found /usr/bin/python) BUILDSTDERR: Call Stack (most recent call first): BUILDSTDERR: /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:313 (_FPHSA_FAILURE_MESSAGE) BUILDSTDERR: cmake/modules/FindPython3Interp.cmake:146 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) BUILDSTDERR: src/CMakeLists.txt:282 (find_package) -- Configuring incomplete, errors occurred! See also "/builddir/build/BUILD/ceph-13.2.0/build/CMakeFiles/CMakeOutput.log". See also "/builddir/build/BUILD/ceph-13.2.0/build/CMakeFiles/CMakeError.log". RPM build errors: BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.IJLMMD (%build) BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.IJLMMD (%build) Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line 96, in trace result = func(*args, **kw) File "/usr/lib/python2.7/site-packages/mockbuild/util.py", line 634, in do raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode) Error: Command failed: # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/ceph.spec -------------- next part -------------- An HTML attachment was scrubbed... URL: From dehao.shang at intel.com Mon Sep 10 14:42:10 2018 From: dehao.shang at intel.com (Shang, Dehao) Date: Mon, 10 Sep 2018 14:42:10 +0000 Subject: [Starlingx-discuss] python interpreter version problem. In-Reply-To: References: <71AECFE5078153419EB7B8DBE0644B26386368D2@shsmsx102.ccr.corp.intel.com> Message-ID: <71AECFE5078153419EB7B8DBE0644B263863697B@shsmsx102.ccr.corp.intel.com> Hi AI: Thanks for your explanations and helps. According to your suggestions, i modify it into as following: %if 0%{?suse_version} >= 1500 %bcond_with python2 %else %bcond_without python2 %endif %if 0%{without python2} %global _defined_if_python2_absent 0 %endif Then use make-srpm.sh to re-generate ceph.spec, then build-pkgs. The same error still exist. Thanks Dehao ==== log ======= -- Performing Test COMPILER_SUPPORTS_CXX17 -- Performing Test COMPILER_SUPPORTS_CXX17 - Success -- Performing Test COMPILER_SUPPORTS_GNU99 -- Performing Test COMPILER_SUPPORTS_GNU99 - Success -- Performing Test HAVE_STDLIB_MAP_SPLICING -- Performing Test HAVE_STDLIB_MAP_SPLICING - Success -- Performing Test COMPILER_SUPPORTS_DIAGNOSTICS_COLOR -- Performing Test COMPILER_SUPPORTS_DIAGNOSTICS_COLOR - Success -- Ceph/.git directory not found, parsing /builddir/build/BUILD/ceph-13.2.0/src/.git_version for CEPH_GIT_VER and CEPH_GIT_NICE_VER BUILDSTDERR: CMake Error at src/CMakeLists.txt:241 (file): BUILDSTDERR: file STRINGS file "/builddir/build/BUILD/ceph-13.2.0/src/.git_version" BUILDSTDERR: cannot be read. -- Found Java: /bin/java (found version "1.8.0.144") -- Found JNI: /usr/lib/jvm/jre/lib/amd64/libjawt.so -- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.5", minimum required is "2") -- Found PythonLibs: /usr/lib64/libpython2.7.so (found suitable version "2.7.5", minimum required is "2") BUILDSTDERR: CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:108 (message): BUILDSTDERR: Could NOT find Python3Interp: Found unsuitable version "2.7.5", but BUILDSTDERR: required is at least "3" (found /usr/bin/python) BUILDSTDERR: Call Stack (most recent call first): BUILDSTDERR: /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:313 (_FPHSA_FAILURE_MESSAGE) BUILDSTDERR: cmake/modules/FindPython3Interp.cmake:146 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) BUILDSTDERR: src/CMakeLists.txt:282 (find_package) -- Configuring incomplete, errors occurred! See also "/builddir/build/BUILD/ceph-13.2.0/build/CMakeFiles/CMakeOutput.log". See also "/builddir/build/BUILD/ceph-13.2.0/build/CMakeFiles/CMakeError.log". RPM build errors: BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.b6h1Ql (%build) BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.b6h1Ql (%build) Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line 96, in trace result = func(*args, **kw) File "/usr/lib/python2.7/site-packages/mockbuild/util.py", line 634, in do raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode) Error: Command failed: # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/ceph.spec From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Monday, September 10, 2018 9:12 PM To: Shang, Dehao ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] python interpreter version problem. I downloaded the src rpm for ceph 13.2.0 and extracted it to look at the ceph.spec file I think this section is giving you grief. %if 0%{?suse_version} >= 1500 %bcond_with python2 %else %bcond_without python2 %endif %if 0%{without python2} %global _defined_if_python2_absent 1 %endif By not setting "defined_if_python2_absent" it should use the python2 code, as far as I can tell. See what happens if you comment it out, or remove it. Al From: Shang, Dehao [mailto:dehao.shang at intel.com] Sent: Monday, September 10, 2018 8:41 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] python interpreter version problem. Hi, When upgrading ceph to 13.2.0, i have resolved all deps package of new package, but now being stuck at python interpreter version. Now, starlingx just support python2, and don't support more high python version. But ceph 13.2.0 need python3 interpreter to interpret corresponding ceph package. I have tried to modify python3 into python2.7 at ceph.spec file, but still don't work. Does anyone know how to resolve it? Thanks for your help. build-std.log : -- Performing Test COMPILER_SUPPORTS_GNU99 -- Performing Test COMPILER_SUPPORTS_GNU99 - Success -- Performing Test HAVE_STDLIB_MAP_SPLICING -- Performing Test HAVE_STDLIB_MAP_SPLICING - Success -- Performing Test COMPILER_SUPPORTS_DIAGNOSTICS_COLOR -- Performing Test COMPILER_SUPPORTS_DIAGNOSTICS_COLOR - Success -- Ceph/.git directory not found, parsing /builddir/build/BUILD/ceph-13.2.0/src/.git_version for CEPH_GIT_VER and CEPH_GIT_NICE_VER BUILDSTDERR: CMake Error at src/CMakeLists.txt:241 (file): BUILDSTDERR: file STRINGS file "/builddir/build/BUILD/ceph-13.2.0/src/.git_version" BUILDSTDERR: cannot be read. -- Found Java: /bin/java (found version "1.8.0.144") -- Found JNI: /usr/lib/jvm/jre/lib/amd64/libjawt.so -- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.5", minimum required is "2") -- Found PythonLibs: /usr/lib64/libpython2.7.so (found suitable version "2.7.5", minimum required is "2") BUILDSTDERR: CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:108 (message): BUILDSTDERR: Could NOT find Python3Interp: Found unsuitable version "2.7.5", but BUILDSTDERR: required is at least "3" (found /usr/bin/python) BUILDSTDERR: Call Stack (most recent call first): BUILDSTDERR: /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:313 (_FPHSA_FAILURE_MESSAGE) BUILDSTDERR: cmake/modules/FindPython3Interp.cmake:146 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) BUILDSTDERR: src/CMakeLists.txt:282 (find_package) -- Configuring incomplete, errors occurred! See also "/builddir/build/BUILD/ceph-13.2.0/build/CMakeFiles/CMakeOutput.log". See also "/builddir/build/BUILD/ceph-13.2.0/build/CMakeFiles/CMakeError.log". RPM build errors: BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.IJLMMD (%build) BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.IJLMMD (%build) Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line 96, in trace result = func(*args, **kw) File "/usr/lib/python2.7/site-packages/mockbuild/util.py", line 634, in do raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode) Error: Command failed: # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/ceph.spec -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.thebeau at windriver.com Mon Sep 10 14:49:24 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 10 Sep 2018 10:49:24 -0400 Subject: [Starlingx-discuss] stx-tools changes related to bugs 1790213, 1790716 Message-ID: <989114d2-da5d-557c-f233-df8a1e7cf283@windriver.com> Hi, I was able to launch and test StarlingX under virtualization according to the wiki: https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment and in particular, I booted "Controller_Storage" with four nodes, and I proceeded to test the system according to Wind River's internal wiki for the this purpose up to booting instances from image and volume.  I saw several known bugs including alarm/health query not working and a networking problem for instances.  The build I used was dated 2018-09-04. I made some textual changes to the "Controller_Storage" wiki, one of which was an omitted instruction to "Enable LVM Backend.", which would have left the controllers with storage in a "adding on unlock" state. I've submitted several code reviews for stx-tools based on my experience: https://review.openstack.org/#/c/601275/  (deployment: libvirt: make use of rm command safer) https://review.openstack.org/#/c/601276/  (deployment: libvirt: remove macs from xml) https://review.openstack.org/#/c/601278/  (deployment: libvirt: remove pci, bus, controllers) https://review.openstack.org/#/c/601279/  (deployment: libvirt: update machine type and model) https://review.openstack.org/#/c/601280/  (deployment: libvirt: correct internal/external net) https://review.openstack.org/#/c/601282/  (deployment: libvirt: refer to Starlingx wiki) These changes build upon the commit from Dean and Abraham: https://review.openstack.org/#/c/585588/  (Add virtual environemnt deployment scripts) Thanks, that was fun :) M From Jason.McKenna at windriver.com Mon Sep 10 16:02:41 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Mon, 10 Sep 2018 16:02:41 +0000 Subject: [Starlingx-discuss] [Build] Feedback on stxb demo Message-ID: Hi build team, Many thanks for the demo today, I think we're on the right track. As promised, here are a few feedback points on the demo, from the perspective of a developer: - I really like how the creation of the docker image is streamlined. - The system as currently demo'd as two copies of the repos. One in /(developers_path)/, and a second in /(developers_path)/stx-tools/(docker_image_root_dir)/localdisk/designer/builder/starlingx/. There should only one repo downloaded. o As a related point, a developer working on changes to a file would expect to make their changes to the repo in /(developers_path)/, rather than to the version in the docker image's filesystem. If I edited a puppet manifest (for example) /(developers_path)/cgcs-root/stx/stx-config/.../ then I would expect the build command to detect and use my changes if I do a build. - I'm a bit confused on the syntax regarding specifying and using localized mirrors, specifically with the -n and -p options. Would you provide examples of what commands I'd execute for use cases 1 and 2 below? I'm pretty sure these usages are supported, but am just seeking clarification. - Very happy do see it down to 1 docker image, rather than 2 :) - Native build - Being able to build in a docker image is great, but the would ideally be an option to perform a native build, rather than have to use a container - Minor nit - logs should be in a user directory (like $MY_REPO_ROOT_DIR/logs/) rather than in /var/log, as a non-privileged user wouldn't be able to log to /var/log. - Question - what privileges are required to create the docker image? Does the script assume the user has sudo privileges? - I'm unclear on what would happen with use cases 3-5 below. Have these types of uses been considered yet? Thanks again for the demo, -Jason Use Case 1: I am an organization with a site who is working with StarlingX. I want to provide a local mirror for my employees to use so they don't have to download all artifacts from the external internet every time. I want to create an automated job which I will run daily to download all artifacts from the Internet (if they do not already exist) and place them in directory /export/mirrors/starlingx. Assume the user running the automated job has permissions to write to /export/mirrors/starlingx Use Case 2: I am a developer within an organization which has a local mirror of artifacts available in /import/mirrors/starlingx. I want to build a StarlingX ISO without downloading rpms or src.rpms from the external internet. Use Case 3A: After doing a build, I just performed a repo sync, and the .lst files were not updated. If I perform another build of the ISO, will the system attempt to redownload external artifacts, even though nothing has changed? Use Case 3B: After doing a build, I just performed a repo sync, and noticed that the .lst files have been updated. If I perform another build of the ISO, will the stale mirror content be detected and the new additions downloaded (while not re-downloading anything which has not changed)? Use Case 4: I have manually made a change to a puppet manifest in sysinv (stx-config git) but want to test before I commit anything. How can I build a new ISO with my changes incorporated? Use Case 5: I want to test StarlingX with my own additional program (foobar.x86_64.rpm) on the ISO. How would I perform a build with this file added? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jason.McKenna at windriver.com Mon Sep 10 16:12:58 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Mon, 10 Sep 2018 16:12:58 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> Message-ID: Status update. The build from the centos75 branch does not install on our hardware. The error message we are seeing is: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. -Jason From: Liu, ZhipengS Sent: September 8, 2018 9:56 AM To: Lin, Shuicheng ; McKenna, Jason ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: RE: CentOS 7.5 upgrade status update Hi Jason, I have fixed the issue you mentioned below. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. https://review.openstack.org/#/c/600920/ Thanks! Zhipeng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: 2018年9月8日 21:14 To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I’ve completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don’t have this issue. I used last week’s master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they’ve moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be priming this activity. He’ll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Mon Sep 10 16:52:31 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 10 Sep 2018 16:52:31 +0000 Subject: [Starlingx-discuss] [Build] Feedback on stxb demo In-Reply-To: References: Message-ID: > Use Case 1: > > I am an organization with a site who is working with StarlingX. I want > to provide a local mirror for my employees to use so they don't have to > download all artifacts from the external internet every time. I want to create > an automated job which I will run daily to download all artifacts from the > Internet (if they do not already exist) and place them in directory > /export/mirrors/starlingx. Assume the user running the automated job has > permissions to write to /export/mirrors/starlingx > > Use Case 2: > > I am a developer within an organization which has a local mirror of > artifacts available in /import/mirrors/starlingx. I want to build a StarlingX ISO > without downloading rpms or src.rpms from the external internet. Initial documentation on Regional Office > Regional Mirror found at https://wiki.openstack.org/wiki/StarlingX/Developer_Guide/Regional_Mirror From michel.thebeau at windriver.com Mon Sep 10 17:28:21 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 10 Sep 2018 13:28:21 -0400 Subject: [Starlingx-discuss] Fedora Libvirt patch - required to deploy on Fedora 28, probably other non-ubuntu specific In-Reply-To: <81e0cc73b05fc5eb4a44939c8769dbd3@optimcloud.com> References: <81e0cc73b05fc5eb4a44939c8769dbd3@optimcloud.com> Message-ID: Hi Scott, Please add me to the review when you get it to gerrit.  I've made similar changes. I recently touched xml in this commits under review: https://review.openstack.org/#/c/601276/ (deployment: libvirt: remove macs from xml) https://review.openstack.org/#/c/601278/ (deployment: libvirt: remove pci, bus, controllers) https://review.openstack.org/#/c/601279/ (deployment: libvirt: update machine type and model) On 2018-09-09 11:57 PM, scottk at optimcloud.com wrote: > sending in my fedora modifications needed to spin up on Fedora 28, removing the Ubuntu specific items, > created on my local tree with git format-patch -1 437353d3b108e7a92c0d5c48c81d334f07940dc3 (the git rev is my specific commit to my local tree) > > noted the machine='pc-i440fx-xenial' and seclabel pieces are not required in Fedora, also note in the docs I recommend being explicit about the hardware models (machine and cpu model), in order to stabilize testing across host machines.  I want to suggest using q35 because it is newer.  But 'pc-i440fx-xenial' is listed as default in "kvm -M ?" > > Installing Requirements and Dependencies > Install the required packages and configure QEMU. This only needs to be done once per host. (NOTE: this script only knows about Ubuntu at this time): > > $SCRIPTS/install_packages.sh > > the above breaks permissions on libvirt in Fedora and most likely others rendering it useless > > we dont use > user = "root" > group = "root" > > and obviously, we (IMHO) shouldnt be running it as group root anyway, in Fedora there is a libvirt group > 0001-fixup-for-fedora.patch > From 437353d3b108e7a92c0d5c48c81d334f07940dc3 Mon Sep 17 00:00:00 2001 > From: OutBack Dingo > Date: Mon, 10 Sep 2018 05:46:58 +0200 > Subject: [PATCH] fixup for fedora > > --- > deployment/libvirt/compute.xml | 6 +----- > deployment/libvirt/controller.xml | 6 +----- > deployment/libvirt/controller_allinone.xml | 6 +----- > deployment/libvirt/setup_allinone.sh | 4 ---- > 4 files changed, 3 insertions(+), 19 deletions(-) > > diff --git a/deployment/libvirt/compute.xml b/deployment/libvirt/compute.xml > index 85474c0..4bdc812 100644 > --- a/deployment/libvirt/compute.xml > +++ b/deployment/libvirt/compute.xml > @@ -7,7 +7,7 @@ > /machine > > > - hvm > + hvm I'd want to be explicit with a machine here so that all users run the same emulated hardware. > > > > @@ -108,8 +108,4 @@ >
> > > - > - > - libvirt-608ab5c8-8d11-4bdd-885f-f8b5fee12ff0 > - libvirt will add it back into the DOMAIN xml when the domain is defined, so I agree that one would not want it in the xml template used to define the nodes. M > > diff --git a/deployment/libvirt/controller.xml b/deployment/libvirt/controller.xml > index e346813..65c4d01 100644 > --- a/deployment/libvirt/controller.xml > +++ b/deployment/libvirt/controller.xml > @@ -7,7 +7,7 @@ > /machine > > > - hvm > + hvm > > > > @@ -122,9 +122,5 @@ >
> > > - > - > - libvirt-6afab2ba-0ed0-45cb-b1bd-985e211a48de > - > > diff --git a/deployment/libvirt/controller_allinone.xml b/deployment/libvirt/controller_allinone.xml > index 9249183..83e8fe6 100644 > --- a/deployment/libvirt/controller_allinone.xml > +++ b/deployment/libvirt/controller_allinone.xml > @@ -7,7 +7,7 @@ > /machine > > > - hvm > + hvm > > > > @@ -122,9 +122,5 @@ >
> > > - > - > - libvirt-6afab2ba-0ed0-45cb-b1bd-985e211a48de > - > > diff --git a/deployment/libvirt/setup_allinone.sh b/deployment/libvirt/setup_allinone.sh > index b228efc..dcf1607 100755 > --- a/deployment/libvirt/setup_allinone.sh > +++ b/deployment/libvirt/setup_allinone.sh > @@ -28,10 +28,6 @@ fi > ISOIMAGE=$(readlink -f "$ISOIMAGE") > FILETYPE=$(file --mime-type -b ${ISOIMAGE}) > -if ([ "$FILETYPE" != "application/x-iso9660-image" ]); then > - echo "$ISOIMAGE is not an application/x-iso9660-image type" > - exit -1 > -fi > BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr} > CONTROLLER=${CONTROLLER:-controller-allinone} > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Mon Sep 10 17:33:03 2018 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 10 Sep 2018 10:33:03 -0700 Subject: [Starlingx-discuss] [Build] Feedback on stxb demo In-Reply-To: References: Message-ID: <12f082a2-f28d-ad8e-6fa2-336c0d945513@linux.intel.com> Sorry I missed this today, I am in Denver. Can you point me at the repo you are working in please? On 09/10/2018 09:02 AM, McKenna, Jason wrote: > Hi build team, > > Many thanks for the demo today, I think we’re on the right track.  As > promised, here are a few feedback points on the demo, from the > perspective of a developer: > > -I really like how the creation of the docker image is streamlined. > > -The system as currently demo’d as two copies of the repos.  One in > /(developers_path)/, and a second in > /(developers_path)/stx-tools/(docker_image_root_dir)/localdisk/designer/builder/starlingx/. > There should only one repo downloaded. > > oAs a related point, a developer working on changes to a file would > expect to make their changes to the repo in /(developers_path)/, rather > than to the version in the docker image’s filesystem.  If I edited a > puppet manifest (for example) > /(developers_path)/cgcs-root/stx/stx-config/…/ then I would expect the > build command to detect and use my changes if I do a build. > > -I’m a bit confused on the syntax regarding specifying and using > localized mirrors, specifically with the –n and –p options.  Would you > provide examples of what commands I’d execute for use cases 1 and 2 > below? I’m pretty sure these usages are supported, but am just seeking > clarification. > > -Very happy do see it down to 1 docker image, rather than 2 J > > -Native build – Being able to build in a docker image is great, but the > would ideally be an option to perform a native build, rather than have > to use a container > > -Minor nit - logs should be in a user directory (like > $MY_REPO_ROOT_DIR/logs/) rather than in /var/log, as a non-privileged > user wouldn’t be able to log to /var/log. > > -Question – what privileges are required to create the docker image? > Does the script assume the user has sudo privileges? > > -I’m unclear on what would happen with use cases 3-5 below.  Have these > types of uses been considered yet? > Jason, Thanks for this feedback and the use case suggestions below, see additional comments. > Thanks again for the demo, > > -Jason > > Use Case 1: > >                 I am an organization with a site who is working with > StarlingX.  I want to provide a local mirror for my employees to use so > they don’t have to download all artifacts from the external internet > every time. I want to create an automated job which I will run daily to > download all artifacts from the Internet (if they do not already exist) > and place them in directory /export/mirrors/starlingx.  Assume the user > running the automated job has permissions to write to > /export/mirrors/starlingx > Based on your usage of /export and /import below, /export is on a server machine and /import is on the local developer build machine, just for clarification. Also, this job would run native on the host Linux OS not containerized? > Use Case 2: > >                 I am a developer within an organization which has a > local mirror of artifacts available in /import/mirrors/starlingx.  I > want to build a StarlingX ISO without downloading rpms or src.rpms from > the external internet. > To further clarify this one, the remote mirror could contain all binary rpms along with their cooresponding src rpm, such that if no changes all the building of an ISO would be done from the mirror rpms, no actual local rpm build required unless it changes (use case 4/5 below). > Use Case 3A: > >                 After doing a build, I just performed a repo sync, and > the .lst files were not updated.  If I perform another build of the ISO, > will the system attempt to redownload external artifacts, even though > nothing has changed? > > Use Case 3B: > >                 After doing a build, I just performed a repo sync, and > noticed that the .lst files have been updated.  If I perform another > build of the ISO, will the stale mirror content be detected and the new > additions downloaded (while not re-downloading anything which has not > changed)? > > Use Case 4: > >                 I have manually made a change to a puppet manifest in > sysinv (stx-config git) but want to test before I commit anything.  How > can I build a new ISO with my changes incorporated? > I would say not just puppet manifest, but any change to files in the repos. > Use Case 5: > >                 I want to test StarlingX with my own additional program > (foobar.x86_64.rpm) on the ISO.  How would I perform a build with this > file added? > I look forward to seeing the demo also. Sau! > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From michel.thebeau at windriver.com Mon Sep 10 17:35:34 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 10 Sep 2018 13:35:34 -0400 Subject: [Starlingx-discuss] Fedora Libvirt patch - required to deploy on Fedora 28, probably other non-ubuntu specific In-Reply-To: <1c7da17a35add8d68c2fb03c7fdd0356@optimcloud.com> References: <81e0cc73b05fc5eb4a44939c8769dbd3@optimcloud.com> <1c7da17a35add8d68c2fb03c7fdd0356@optimcloud.com> Message-ID: <5087676c-cfa9-51b5-ff37-f9acb6e5a9a7@windriver.com> On 2018-09-10 02:03 AM, scottk at optimcloud.com wrote: > September 10, 2018 6:16 AM, "Cordoba Malibran, Erich" wrote: > >> Hi, >> >> Thanks for the patch. I'm also using Fedora for the deployment and I've seen this problems as well >> as other in the creation of the docker images[0] for building. > I had 0 issues creating the docker images on fedora 28 that was all pretty straight forward using docker-ce > other then some things in the guide from inside the image, after they got fixed up i did get an iso > >> This part of the building and deployment process is in an early stage of development and thus, >> there are bugs and lack of functionality on some parts. Like you pointed out, the support for more >> flavors in hosts for virtual deployments is one of the missing parts and we are happy to receive >> feedback :) > My thoughts as well but it seems these were the tools used originally for the work, i believe its now they are starting to work slowly towards a more generic structure > >> What you think about sending this patch as a review for the stx-tools[1] repository? It would be >> good to have it landed. > Id be happy to even help further, and forward it to the list, but I would prefer to wait for the invite, plus i probably need creds and such setup so i could. > > Its gone to the mailing list as of now, they also from a prior email have already negated the libvirt iso file check > > https://github.com/Nossiac/mtk-openwrt-feeds/blob/master/about-mtk-wifi.md > > it plainly didnt work on my system, as soon as it was removed it moved me forward > >> Anyway, I have two open questions regarding you patch (not necessary question to you). >> 1) Is it possible to remove the seclabel from the ubuntu version as well? Having this will block us >> to have these xml definitions, we would need to "generate" this xml files based on the host that we >> will use. > Youll see in my patch i also edited the XML defs, across the board i belive they can also be made more generic and still be functional > >> 2) Why was needed to remove the check for "application/x-iso9660-image"? > The call simply errored out on my system under KDE, its a mime-type def also i dont see what it would be required, as we could use gcow2 or raw filesystem images also in the future. I saw it as not needed. > I'd like to understand why it errored on your system.  What is the value of $FILETYPE for you? The command line option for variable "ISOIMAGE" is "-i: StarlingX ISO image".  And is inserted into xml as:                     #  <=== sed "s;ISO;$ISOIMAGE;" Let's defer changes to the parameter checking until gcow2/raw are considered as options.  Or, if you know that those fs types can be inserted into a CDROM, then also rephrase the usage() text and variable "ISOIMAGE". M >> Thanks again for all your feedback. >> >> -Erich >> >> [0] https://storyboard.openstack.org/#!/story/2002560 >> [1] http://git.starlingx.io/cgit/stx-tools >> >> From: "scottk at optimcloud.com" >> Date: Sunday, September 9, 2018 at 10:57 PM >> To: "starlingx-discuss at lists.starlingx.io" >> Subject: [Starlingx-discuss] Fedora Libvirt patch - required to deploy on Fedora 28, probably other >> non-ubuntu specific > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From juan.carlos.alonso at intel.com Mon Sep 10 17:50:27 2018 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Mon, 10 Sep 2018 17:50:27 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> Message-ID: <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> Hi, Such launchpads were updated. A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two issues. Michael will upload his ISO, then we will re test witch each iso in our environment. An script is being developed to get the differences between ISOs. Regards. Juan Carlos Alonso -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Friday, September 7, 2018 4:43 PM To: Khalil, Ghada ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io; Thebeau, Michel Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hi Elio/Ada, Are there any updates from your side on these two Launchpads? https://bugs.launchpad.net/starlingx/+bug/1790213 https://bugs.launchpad.net/starlingx/+bug/1790716 Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team. As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup). Please let us know if you need any further help from us. Thanks, Ghada -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, September 05, 2018 5:39 PM To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Please see inline. There are notes in all the launchpads as well. I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. -----Original Message----- From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Wednesday, September 05, 2018 2:23 PM To: Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted My opinion below -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, September 5, 2018 12:56 PM To: Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Should the bugs coming out of this be tagged/fixed for the October release? Related bugs: https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all instances need at least one compute for multimode [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. The test team points to internal instructions which we have no access to. The supported install recipes need to be on the wiki. I think it is an invalid bug https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Wednesday, September 5, 2018 10:50 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hello all, As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. [0] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary Regards Ada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ken.Young at windriver.com Mon Sep 10 20:43:18 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Mon, 10 Sep 2018 20:43:18 +0000 Subject: [Starlingx-discuss] [Security] How to Report Security Issues to Starling X Message-ID: <367D6EC2-AFC8-43CD-8BBC-ABC5095352CC@windriver.com> Team, The Security Subproject has formalized a method for the community to raise security issues. The procedure is summarized here: https://wiki.openstack.org/wiki/StarlingX/Security#How_to_report_security_issues_to_Starling_X This follows the methods used by the OpenStack security team. If there are any questions or concerns, please let me know. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From mario.alfredo.c.arevalo at intel.com Mon Sep 10 20:56:55 2018 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Mon, 10 Sep 2018 20:56:55 +0000 Subject: [Starlingx-discuss] [Build] Feedback on stxb demo In-Reply-To: <12f082a2-f28d-ad8e-6fa2-336c0d945513@linux.intel.com> References: , <12f082a2-f28d-ad8e-6fa2-336c0d945513@linux.intel.com> Message-ID: <6594B51DBE477C48AAE23675314E6C465993F282@fmsmsx107.amr.corp.intel.com> Hi folks, I have been seen excellent ideas that we can to add to the tool, however I think we are walking a little out of the first scope, what do you think if we include this as first version a we can post our ideas in the storyboard?: https://storyboard.openstack.org/#!/story/2003712 Then we can track all ideas suggested :) Best regards. Mario. ________________________________________ From: Saul Wold [sgw at linux.intel.com] Sent: Monday, September 10, 2018 10:33 AM To: McKenna, Jason; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] [Build] Feedback on stxb demo Sorry I missed this today, I am in Denver. Can you point me at the repo you are working in please? On 09/10/2018 09:02 AM, McKenna, Jason wrote: > Hi build team, > > Many thanks for the demo today, I think we’re on the right track. As > promised, here are a few feedback points on the demo, from the > perspective of a developer: > > -I really like how the creation of the docker image is streamlined. > > -The system as currently demo’d as two copies of the repos. One in > /(developers_path)/, and a second in > /(developers_path)/stx-tools/(docker_image_root_dir)/localdisk/designer/builder/starlingx/. > There should only one repo downloaded. > > oAs a related point, a developer working on changes to a file would > expect to make their changes to the repo in /(developers_path)/, rather > than to the version in the docker image’s filesystem. If I edited a > puppet manifest (for example) > /(developers_path)/cgcs-root/stx/stx-config/…/ then I would expect the > build command to detect and use my changes if I do a build. > > -I’m a bit confused on the syntax regarding specifying and using > localized mirrors, specifically with the –n and –p options. Would you > provide examples of what commands I’d execute for use cases 1 and 2 > below? I’m pretty sure these usages are supported, but am just seeking > clarification. > > -Very happy do see it down to 1 docker image, rather than 2 J > > -Native build – Being able to build in a docker image is great, but the > would ideally be an option to perform a native build, rather than have > to use a container > > -Minor nit - logs should be in a user directory (like > $MY_REPO_ROOT_DIR/logs/) rather than in /var/log, as a non-privileged > user wouldn’t be able to log to /var/log. > > -Question – what privileges are required to create the docker image? > Does the script assume the user has sudo privileges? > > -I’m unclear on what would happen with use cases 3-5 below. Have these > types of uses been considered yet? > Jason, Thanks for this feedback and the use case suggestions below, see additional comments. > Thanks again for the demo, > > -Jason > > Use Case 1: > > I am an organization with a site who is working with > StarlingX. I want to provide a local mirror for my employees to use so > they don’t have to download all artifacts from the external internet > every time. I want to create an automated job which I will run daily to > download all artifacts from the Internet (if they do not already exist) > and place them in directory /export/mirrors/starlingx. Assume the user > running the automated job has permissions to write to > /export/mirrors/starlingx > Based on your usage of /export and /import below, /export is on a server machine and /import is on the local developer build machine, just for clarification. Also, this job would run native on the host Linux OS not containerized? > Use Case 2: > > I am a developer within an organization which has a > local mirror of artifacts available in /import/mirrors/starlingx. I > want to build a StarlingX ISO without downloading rpms or src.rpms from > the external internet. > To further clarify this one, the remote mirror could contain all binary rpms along with their cooresponding src rpm, such that if no changes all the building of an ISO would be done from the mirror rpms, no actual local rpm build required unless it changes (use case 4/5 below). > Use Case 3A: > > After doing a build, I just performed a repo sync, and > the .lst files were not updated. If I perform another build of the ISO, > will the system attempt to redownload external artifacts, even though > nothing has changed? > > Use Case 3B: > > After doing a build, I just performed a repo sync, and > noticed that the .lst files have been updated. If I perform another > build of the ISO, will the stale mirror content be detected and the new > additions downloaded (while not re-downloading anything which has not > changed)? > > Use Case 4: > > I have manually made a change to a puppet manifest in > sysinv (stx-config git) but want to test before I commit anything. How > can I build a new ISO with my changes incorporated? > I would say not just puppet manifest, but any change to files in the repos. > Use Case 5: > > I want to test StarlingX with my own additional program > (foobar.x86_64.rpm) on the ISO. How would I perform a build with this > file added? > I look forward to seeing the demo also. Sau! > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From jesus.ornelas.aguayo at intel.com Mon Sep 10 21:06:06 2018 From: jesus.ornelas.aguayo at intel.com (Ornelas Aguayo, Jesus) Date: Mon, 10 Sep 2018 21:06:06 +0000 Subject: [Starlingx-discuss] [Build] Feedback on stxb demo In-Reply-To: <12f082a2-f28d-ad8e-6fa2-336c0d945513@linux.intel.com> References: <12f082a2-f28d-ad8e-6fa2-336c0d945513@linux.intel.com> Message-ID: <02E34809-88D7-420B-87B1-59528A5DC0D0@intel.com> From: Saul Wold Date: Monday, September 10, 2018 at 12:33 PM To: "McKenna, Jason" , "'starlingx-discuss at lists.starlingx.io'" Subject: Re: [Starlingx-discuss] [Build] Feedback on stxb demo Sorry I missed this today, I am in Denver. Can you point me at the repo you are working in please? https://review.openstack.org/#/c/601366/ https://review.openstack.org/#/c/601306/ https://review.openstack.org/#/c/601308/ https://review.openstack.org/#/c/601309/ On 09/10/2018 09:02 AM, McKenna, Jason wrote: > Hi build team, > > Many thanks for the demo today, I think we’re on the right track. As > promised, here are a few feedback points on the demo, from the > perspective of a developer: > > -I really like how the creation of the docker image is streamlined. > > -The system as currently demo’d as two copies of the repos. One in > /(developers_path)/, and a second in > /(developers_path)/stx-tools/(docker_image_root_dir)/localdisk/designer/builder/starlingx/. > There should only one repo downloaded. > oAs a related point, a developer working on changes to a file would > expect to make their changes to the repo in /(developers_path)/, rather > than to the version in the docker image’s filesystem. If I edited a > puppet manifest (for example) Hi, I think there are a lot of user scenarios that we need to consider, and we Should be adding functionality step by step, so far the commits mentioned simplify The building process to new users and can be used to add more functionality Four our next steps, I think we should create an storyboard to extend the Functionality by adding the scenario that need to be covered, starting with the ones Jason mentioned in this email: What about using two flags set by opts , one to use a local repo path and another one And another one to specify if the user wants to use a repo from a different Manifest and url. > /(developers_path)/cgcs-root/stx/stx-config/…/ then I would expect the > build command to detect and use my changes if I do a build. It could be an update flag, it the value is false, then it could skip the Updates/downloads and use the local content only > -I’m a bit confused on the syntax regarding specifying and using > localized mirrors, specifically with the –n and –p options. Would you > provide examples of what commands I’d execute for use cases 1 and 2 > below? I’m pretty sure these usages are supported, but am just seeking > clarification. `stxb build mirror`creates a defauilt mirror in the local workspace/mirror if no opts are given, In the current path ($PWD/starlingx/mirror), If the `stx build mirror -n my-staging-mirror` is given the path would be $PWD/starlingx/my-staging-mirror If the `stx build mirror -p /mnt/nfs` is given the path would be /mnt/nfs/mirror If the `stx build mirror -p /mnt/nfs/ww11/ -n monday` is given the path would be /mnt/nfs/mirror/www11/Monday > -Very happy do see it down to 1 docker image, rather than 2 J > > -Native build – Being able to build in a docker image is great, but the > would ideally be an option to perform a native build, rather than have > to use a container > -Minor nit - logs should be in a user directory (like > $MY_REPO_ROOT_DIR/logs/) rather than in /var/log, as a non-privileged > user wouldn’t be able to log to /var/log. The PR changed the path to use the ${WORKSPACE}, and specify another Another path if needed with the opt `-p` > -Question – what privileges are required to create the docker image? > Does the script assume the user has sudo privileges? So far I've running it without using sudo, using a user with docker group Permissions > -I’m unclear on what would happen with use cases 3-5 below. Have these > types of uses been considered yet? > From cesar.lara at intel.com Mon Sep 10 21:53:28 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Mon, 10 Sep 2018 21:53:28 +0000 Subject: [Starlingx-discuss] [build] meeting minutes 9/10/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB4710502CC6@fmsmsx104.amr.corp.intel.com> Agenda for 9/10/2018 Single command demo Storyboard grooming opens meeting minutes Attendees: Hayde, Marcela, Erich, Mario, Chuy, Jason, Abraham, Cesar stxb tool demo comments about the tool on Mailing List provided by Jason Please update storyboard with progress on [build] tasks no time for opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Tue Sep 11 01:35:26 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 11 Sep 2018 01:35:26 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> Hi Jason, I just tried my last Friday’s image at bare metal machine. There is no issue to install controller node. Will you help check what cause the install error in your environment? I am syncing my code to latest to double confirm it. Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 12:13 AM To: Liu, ZhipengS ; Lin, Shuicheng ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: RE: CentOS 7.5 upgrade status update Status update. The build from the centos75 branch does not install on our hardware. The error message we are seeing is: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. -Jason From: Liu, ZhipengS > Sent: September 8, 2018 9:56 AM To: Lin, Shuicheng >; McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Jason, I have fixed the issue you mentioned below. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. https://review.openstack.org/#/c/600920/ Thanks! Zhipeng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: 2018年9月8日 21:14 To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I’ve completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don’t have this issue. I used last week’s master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they’ve moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be priming this activity. He’ll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Sep 11 00:05:13 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 11 Sep 2018 00:05:13 +0000 Subject: [Starlingx-discuss] Agenda for 9/12 non-OpenStack Distro weekly meeting Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B33ECF7@SHSMSX104.ccr.corp.intel.com> Please let me know if you'd add new items below. Agenda for 9/12 meetings: . AR Reviews (Cindy) . non-OpenStack patch analysis status (Saul) . CentOS 7.5 upgrade & test status (Shuicheng, Elio, Ghada/Jason) . Libvirt/qemu upgrade status (Ghada/Jim) . Ceph upgrade status (Vivian) . Open topics (Brent, Saul, Ghada)     From shuicheng.lin at intel.com Tue Sep 11 06:16:47 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 11 Sep 2018 06:16:47 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> Hi Jason, Just finished deploy image with latest code, I could config controller successfully in bare metal environment. Manifest is created for you reference. There are two patches I add manually: https://review.openstack.org/596855 for python-horizon from master https://review.openstack.org/599892 for build-iso There is an issue found when reboot controller node. After the OS selection menu, it will show below error. And it will auto continue boot after around 8 seconds. I will check the issue later. “ Error: no symbol table. Press any key to continue… “ Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, September 11, 2018 9:35 AM To: McKenna, Jason ; Liu, ZhipengS ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I just tried my last Friday’s image at bare metal machine. There is no issue to install controller node. Will you help check what cause the install error in your environment? I am syncing my code to latest to double confirm it. Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 12:13 AM To: Liu, ZhipengS >; Lin, Shuicheng >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Status update. The build from the centos75 branch does not install on our hardware. The error message we are seeing is: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. -Jason From: Liu, ZhipengS > Sent: September 8, 2018 9:56 AM To: Lin, Shuicheng >; McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Jason, I have fixed the issue you mentioned below. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. https://review.openstack.org/#/c/600920/ Thanks! Zhipeng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: 2018年9月8日 21:14 To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I’ve completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don’t have this issue. I used last week’s master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they’ve moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be priming this activity. He’ll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: manifest.zip Type: application/x-zip-compressed Size: 2608 bytes Desc: manifest.zip URL: From Numan.Waheed at windriver.com Tue Sep 11 12:49:42 2018 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Tue, 11 Sep 2018 12:49:42 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> Adding Nimalini From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: September-11-18 2:17 AM To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Waheed, Numan Subject: RE: CentOS 7.5 upgrade status update Hi Jason, Just finished deploy image with latest code, I could config controller successfully in bare metal environment. Manifest is created for you reference. There are two patches I add manually: https://review.openstack.org/596855 for python-horizon from master https://review.openstack.org/599892 for build-iso There is an issue found when reboot controller node. After the OS selection menu, it will show below error. And it will auto continue boot after around 8 seconds. I will check the issue later. “ Error: no symbol table. Press any key to continue… “ Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, September 11, 2018 9:35 AM To: McKenna, Jason ; Liu, ZhipengS ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy ; Waheed, Numan Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I just tried my last Friday’s image at bare metal machine. There is no issue to install controller node. Will you help check what cause the install error in your environment? I am syncing my code to latest to double confirm it. Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 12:13 AM To: Liu, ZhipengS >; Lin, Shuicheng >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Status update. The build from the centos75 branch does not install on our hardware. The error message we are seeing is: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. -Jason From: Liu, ZhipengS > Sent: September 8, 2018 9:56 AM To: Lin, Shuicheng >; McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Jason, I have fixed the issue you mentioned below. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. https://review.openstack.org/#/c/600920/ Thanks! Zhipeng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: 2018年9月8日 21:14 To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I’ve completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don’t have this issue. I used last week’s master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they’ve moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be priming this activity. He’ll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Nimalini.Rasa at windriver.com Tue Sep 11 13:05:47 2018 From: Nimalini.Rasa at windriver.com (Rasa, Nimalini) Date: Tue, 11 Sep 2018 13:05:47 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> Message-ID: <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> It is not booting in my case. After the following , it just hangs there: “Error: no symbol table. Press any key to continue…” -Nimalini From: Waheed, Numan Sent: Tuesday, September 11, 2018 8:50 AM To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, Nimalini Subject: RE: CentOS 7.5 upgrade status update Adding Nimalini From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: September-11-18 2:17 AM To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Waheed, Numan Subject: RE: CentOS 7.5 upgrade status update Hi Jason, Just finished deploy image with latest code, I could config controller successfully in bare metal environment. Manifest is created for you reference. There are two patches I add manually: https://review.openstack.org/596855 for python-horizon from master https://review.openstack.org/599892 for build-iso There is an issue found when reboot controller node. After the OS selection menu, it will show below error. And it will auto continue boot after around 8 seconds. I will check the issue later. “ Error: no symbol table. Press any key to continue… “ Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, September 11, 2018 9:35 AM To: McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I just tried my last Friday’s image at bare metal machine. There is no issue to install controller node. Will you help check what cause the install error in your environment? I am syncing my code to latest to double confirm it. Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 12:13 AM To: Liu, ZhipengS >; Lin, Shuicheng >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Status update. The build from the centos75 branch does not install on our hardware. The error message we are seeing is: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. -Jason From: Liu, ZhipengS > Sent: September 8, 2018 9:56 AM To: Lin, Shuicheng >; McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Jason, I have fixed the issue you mentioned below. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. https://review.openstack.org/#/c/600920/ Thanks! Zhipeng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: 2018年9月8日 21:14 To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I’ve completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don’t have this issue. I used last week’s master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they’ve moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be priming this activity. He’ll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Sep 11 13:22:03 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 11 Sep 2018 13:22:03 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> Is this the same issue as yesterday’s build? or this is different issue now? From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Tuesday, September 11, 2018 9:06 PM To: Waheed, Numan ; Lin, Shuicheng ; McKenna, Jason ; Liu, ZhipengS ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' ; Xie, Cindy Subject: RE: CentOS 7.5 upgrade status update It is not booting in my case. After the following , it just hangs there: “Error: no symbol table. Press any key to continue…” -Nimalini From: Waheed, Numan Sent: Tuesday, September 11, 2018 8:50 AM To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, Nimalini Subject: RE: CentOS 7.5 upgrade status update Adding Nimalini From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: September-11-18 2:17 AM To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Waheed, Numan Subject: RE: CentOS 7.5 upgrade status update Hi Jason, Just finished deploy image with latest code, I could config controller successfully in bare metal environment. Manifest is created for you reference. There are two patches I add manually: https://review.openstack.org/596855 for python-horizon from master https://review.openstack.org/599892 for build-iso There is an issue found when reboot controller node. After the OS selection menu, it will show below error. And it will auto continue boot after around 8 seconds. I will check the issue later. “ Error: no symbol table. Press any key to continue… “ Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, September 11, 2018 9:35 AM To: McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I just tried my last Friday’s image at bare metal machine. There is no issue to install controller node. Will you help check what cause the install error in your environment? I am syncing my code to latest to double confirm it. Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 12:13 AM To: Liu, ZhipengS >; Lin, Shuicheng >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Status update. The build from the centos75 branch does not install on our hardware. The error message we are seeing is: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. -Jason From: Liu, ZhipengS > Sent: September 8, 2018 9:56 AM To: Lin, Shuicheng >; McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Jason, I have fixed the issue you mentioned below. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. https://review.openstack.org/#/c/600920/ Thanks! Zhipeng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: 2018年9月8日 21:14 To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I’ve completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don’t have this issue. I used last week’s master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they’ve moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be priming this activity. He’ll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Nimalini.Rasa at windriver.com Tue Sep 11 13:25:21 2018 From: Nimalini.Rasa at windriver.com (Rasa, Nimalini) Date: Tue, 11 Sep 2018 13:25:21 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> Message-ID: <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> This is on the same build (yesterday’s build). From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Tuesday, September 11, 2018 9:22 AM To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' Subject: RE: CentOS 7.5 upgrade status update Is this the same issue as yesterday’s build? or this is different issue now? From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Tuesday, September 11, 2018 9:06 PM To: Waheed, Numan >; Lin, Shuicheng >; McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy > Subject: RE: CentOS 7.5 upgrade status update It is not booting in my case. After the following , it just hangs there: “Error: no symbol table. Press any key to continue…” -Nimalini From: Waheed, Numan Sent: Tuesday, September 11, 2018 8:50 AM To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, Nimalini Subject: RE: CentOS 7.5 upgrade status update Adding Nimalini From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: September-11-18 2:17 AM To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Waheed, Numan Subject: RE: CentOS 7.5 upgrade status update Hi Jason, Just finished deploy image with latest code, I could config controller successfully in bare metal environment. Manifest is created for you reference. There are two patches I add manually: https://review.openstack.org/596855 for python-horizon from master https://review.openstack.org/599892 for build-iso There is an issue found when reboot controller node. After the OS selection menu, it will show below error. And it will auto continue boot after around 8 seconds. I will check the issue later. “ Error: no symbol table. Press any key to continue… “ Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, September 11, 2018 9:35 AM To: McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I just tried my last Friday’s image at bare metal machine. There is no issue to install controller node. Will you help check what cause the install error in your environment? I am syncing my code to latest to double confirm it. Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 12:13 AM To: Liu, ZhipengS >; Lin, Shuicheng >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Status update. The build from the centos75 branch does not install on our hardware. The error message we are seeing is: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. -Jason From: Liu, ZhipengS > Sent: September 8, 2018 9:56 AM To: Lin, Shuicheng >; McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Jason, I have fixed the issue you mentioned below. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. https://review.openstack.org/#/c/600920/ Thanks! Zhipeng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: 2018年9月8日 21:14 To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I’ve completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don’t have this issue. I used last week’s master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they’ve moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be priming this activity. He’ll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Sep 11 13:31:59 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 11 Sep 2018 13:31:59 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> But as Jason reported yesterday, the build cannot be installed with error messages: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. We cannot debug without more information, the ISO installs in Intel’s HW. Thus Shuicheng created a new build and attached a manifest in this email thread. Did WindRiver has a chance to create a new ISO using today’s manifest file and re-run the test? Thx. - cindy From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Tuesday, September 11, 2018 9:25 PM To: Xie, Cindy ; Waheed, Numan ; Lin, Shuicheng ; McKenna, Jason ; Liu, ZhipengS ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: CentOS 7.5 upgrade status update This is on the same build (yesterday’s build). From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Tuesday, September 11, 2018 9:22 AM To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' Subject: RE: CentOS 7.5 upgrade status update Is this the same issue as yesterday’s build? or this is different issue now? From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Tuesday, September 11, 2018 9:06 PM To: Waheed, Numan >; Lin, Shuicheng >; McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy > Subject: RE: CentOS 7.5 upgrade status update It is not booting in my case. After the following , it just hangs there: “Error: no symbol table. Press any key to continue…” -Nimalini From: Waheed, Numan Sent: Tuesday, September 11, 2018 8:50 AM To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, Nimalini Subject: RE: CentOS 7.5 upgrade status update Adding Nimalini From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: September-11-18 2:17 AM To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Waheed, Numan Subject: RE: CentOS 7.5 upgrade status update Hi Jason, Just finished deploy image with latest code, I could config controller successfully in bare metal environment. Manifest is created for you reference. There are two patches I add manually: https://review.openstack.org/596855 for python-horizon from master https://review.openstack.org/599892 for build-iso There is an issue found when reboot controller node. After the OS selection menu, it will show below error. And it will auto continue boot after around 8 seconds. I will check the issue later. “ Error: no symbol table. Press any key to continue… “ Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, September 11, 2018 9:35 AM To: McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I just tried my last Friday’s image at bare metal machine. There is no issue to install controller node. Will you help check what cause the install error in your environment? I am syncing my code to latest to double confirm it. Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 12:13 AM To: Liu, ZhipengS >; Lin, Shuicheng >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Status update. The build from the centos75 branch does not install on our hardware. The error message we are seeing is: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. -Jason From: Liu, ZhipengS > Sent: September 8, 2018 9:56 AM To: Lin, Shuicheng >; McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Jason, I have fixed the issue you mentioned below. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. https://review.openstack.org/#/c/600920/ Thanks! Zhipeng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: 2018年9月8日 21:14 To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I’ve completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don’t have this issue. I used last week’s master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they’ve moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be priming this activity. He’ll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jason.McKenna at windriver.com Tue Sep 11 13:50:00 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Tue, 11 Sep 2018 13:50:00 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Cindy, We got past the installation device error, but are coming up against the symbol table error. Our system hangs after this message. I suspect a kernel issue. I see there is an open code review to refactor some kernel patches to a rebased kernel (https://review.openstack.org/#/c/601204/) but I do not know if that is expected to resolve the issue -J From: Xie, Cindy Sent: September 11, 2018 9:32 AM To: Rasa, Nimalini ; Waheed, Numan ; Lin, Shuicheng ; McKenna, Jason ; Liu, ZhipengS ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: CentOS 7.5 upgrade status update But as Jason reported yesterday, the build cannot be installed with error messages: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. We cannot debug without more information, the ISO installs in Intel’s HW. Thus Shuicheng created a new build and attached a manifest in this email thread. Did WindRiver has a chance to create a new ISO using today’s manifest file and re-run the test? Thx. - cindy From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Tuesday, September 11, 2018 9:25 PM To: Xie, Cindy >; Waheed, Numan >; Lin, Shuicheng >; McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: CentOS 7.5 upgrade status update This is on the same build (yesterday’s build). From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Tuesday, September 11, 2018 9:22 AM To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' Subject: RE: CentOS 7.5 upgrade status update Is this the same issue as yesterday’s build? or this is different issue now? From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Tuesday, September 11, 2018 9:06 PM To: Waheed, Numan >; Lin, Shuicheng >; McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy > Subject: RE: CentOS 7.5 upgrade status update It is not booting in my case. After the following , it just hangs there: “Error: no symbol table. Press any key to continue…” -Nimalini From: Waheed, Numan Sent: Tuesday, September 11, 2018 8:50 AM To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, Nimalini Subject: RE: CentOS 7.5 upgrade status update Adding Nimalini From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: September-11-18 2:17 AM To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Waheed, Numan Subject: RE: CentOS 7.5 upgrade status update Hi Jason, Just finished deploy image with latest code, I could config controller successfully in bare metal environment. Manifest is created for you reference. There are two patches I add manually: https://review.openstack.org/596855 for python-horizon from master https://review.openstack.org/599892 for build-iso There is an issue found when reboot controller node. After the OS selection menu, it will show below error. And it will auto continue boot after around 8 seconds. I will check the issue later. “ Error: no symbol table. Press any key to continue… “ Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, September 11, 2018 9:35 AM To: McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I just tried my last Friday’s image at bare metal machine. There is no issue to install controller node. Will you help check what cause the install error in your environment? I am syncing my code to latest to double confirm it. Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 12:13 AM To: Liu, ZhipengS >; Lin, Shuicheng >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Status update. The build from the centos75 branch does not install on our hardware. The error message we are seeing is: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. -Jason From: Liu, ZhipengS > Sent: September 8, 2018 9:56 AM To: Lin, Shuicheng >; McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Jason, I have fixed the issue you mentioned below. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. https://review.openstack.org/#/c/600920/ Thanks! Zhipeng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: 2018年9月8日 21:14 To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I’ve completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don’t have this issue. I used last week’s master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they’ve moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be priming this activity. He’ll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Tue Sep 11 13:53:23 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 11 Sep 2018 13:53:23 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> Hello Juan, I read the notes in the Launchpad. And, just to confirm, are you following the instructions under: https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Controller_Storage and still reproducing the two issues below? I was not able to definitively tell from the Launchpad notes. It's important that both our teams are comparing apples to apples. Thanks, Ghada -----Original Message----- From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Monday, September 10, 2018 1:50 PM To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel Subject: RE: [ Test ] Sanity results - summary posted Hi, Such launchpads were updated. A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two issues. Michael will upload his ISO, then we will re test witch each iso in our environment. An script is being developed to get the differences between ISOs. Regards. Juan Carlos Alonso -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Friday, September 7, 2018 4:43 PM To: Khalil, Ghada ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io; Thebeau, Michel Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hi Elio/Ada, Are there any updates from your side on these two Launchpads? https://bugs.launchpad.net/starlingx/+bug/1790213 https://bugs.launchpad.net/starlingx/+bug/1790716 Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team. As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup). Please let us know if you need any further help from us. Thanks, Ghada -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, September 05, 2018 5:39 PM To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Please see inline. There are notes in all the launchpads as well. I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. -----Original Message----- From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Wednesday, September 05, 2018 2:23 PM To: Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted My opinion below -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, September 5, 2018 12:56 PM To: Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Should the bugs coming out of this be tagged/fixed for the October release? Related bugs: https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all instances need at least one compute for multimode [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. The test team points to internal instructions which we have no access to. The supported install recipes need to be on the wiki. I think it is an invalid bug https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Wednesday, September 5, 2018 10:50 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hello all, As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. [0] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary Regards Ada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Tue Sep 11 13:56:15 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 11 Sep 2018 13:56:15 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> Shuicheng saw the symbol table error issue as well but it recovers in 8s, he is still working on debugging it. But 601204 is just kernel upgrade but not intended to solve this issues. Are you running bare metal? I am wondering if this is HW config and driver issue. Is it possible that you try to deploy it in virtual environment? Thx. - cindy From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 9:50 PM To: Xie, Cindy ; Rasa, Nimalini ; Waheed, Numan ; Lin, Shuicheng ; Liu, ZhipengS ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: CentOS 7.5 upgrade status update Hi Cindy, We got past the installation device error, but are coming up against the symbol table error. Our system hangs after this message. I suspect a kernel issue. I see there is an open code review to refactor some kernel patches to a rebased kernel (https://review.openstack.org/#/c/601204/) but I do not know if that is expected to resolve the issue -J From: Xie, Cindy > Sent: September 11, 2018 9:32 AM To: Rasa, Nimalini >; Waheed, Numan >; Lin, Shuicheng >; McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: CentOS 7.5 upgrade status update But as Jason reported yesterday, the build cannot be installed with error messages: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. We cannot debug without more information, the ISO installs in Intel’s HW. Thus Shuicheng created a new build and attached a manifest in this email thread. Did WindRiver has a chance to create a new ISO using today’s manifest file and re-run the test? Thx. - cindy From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Tuesday, September 11, 2018 9:25 PM To: Xie, Cindy >; Waheed, Numan >; Lin, Shuicheng >; McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: CentOS 7.5 upgrade status update This is on the same build (yesterday’s build). From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Tuesday, September 11, 2018 9:22 AM To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' Subject: RE: CentOS 7.5 upgrade status update Is this the same issue as yesterday’s build? or this is different issue now? From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Tuesday, September 11, 2018 9:06 PM To: Waheed, Numan >; Lin, Shuicheng >; McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy > Subject: RE: CentOS 7.5 upgrade status update It is not booting in my case. After the following , it just hangs there: “Error: no symbol table. Press any key to continue…” -Nimalini From: Waheed, Numan Sent: Tuesday, September 11, 2018 8:50 AM To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, Nimalini Subject: RE: CentOS 7.5 upgrade status update Adding Nimalini From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: September-11-18 2:17 AM To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io'; Xie, Cindy; Waheed, Numan Subject: RE: CentOS 7.5 upgrade status update Hi Jason, Just finished deploy image with latest code, I could config controller successfully in bare metal environment. Manifest is created for you reference. There are two patches I add manually: https://review.openstack.org/596855 for python-horizon from master https://review.openstack.org/599892 for build-iso There is an issue found when reboot controller node. After the OS selection menu, it will show below error. And it will auto continue boot after around 8 seconds. I will check the issue later. “ Error: no symbol table. Press any key to continue… “ Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, September 11, 2018 9:35 AM To: McKenna, Jason >; Liu, ZhipengS >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I just tried my last Friday’s image at bare metal machine. There is no issue to install controller node. Will you help check what cause the install error in your environment? I am syncing my code to latest to double confirm it. Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 12:13 AM To: Liu, ZhipengS >; Lin, Shuicheng >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Status update. The build from the centos75 branch does not install on our hardware. The error message we are seeing is: Installation failed. ERROR: Specified installation (sda) or boot (sda) device is invalid. -Jason From: Liu, ZhipengS > Sent: September 8, 2018 9:56 AM To: Lin, Shuicheng >; McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Jason, I have fixed the issue you mentioned below. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. https://review.openstack.org/#/c/600920/ Thanks! Zhipeng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: 2018年9月8日 21:14 To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, I have fixed the error in the openstack-aodh. Patch is updated: https://review.openstack.org/#/c/598388/ It is due to my local version is not the latest one. Sorry for the trouble caused, and thanks for your test. Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Saturday, September 8, 2018 9:23 AM To: McKenna, Jason >; Khalil, Ghada >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Jason, Thanks very much for such detail feedback. I added some comments inline, and will check the issue in my environment also. Feel free to submit patch if you have to fix them. :) Best Regards Shuicheng From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Saturday, September 8, 2018 3:47 AM To: McKenna, Jason >; Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update Hi Shuicheng, I’ve completed a build of the code. We have not yet run run-time tests, but here are the build-time issues I encountered: - The .lst file contains lighttpd-1.4.49, but this is no longer available for download, and the download_mirrors.sh step fails. It appears than CentOS has updated to lighttpd-1.4.50. I manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst - Even though the .lst file specifies lighttpd-1.4.49, the code still references 1.4.45 - At build-pkgs time (the build-srpms step), the meta-patches to openstack-aodh do not apply, as two of them are malformed. https://review.openstack.org/#/c/598388/6/openstack/openstack-aodh/centos/meta_patches/0001-Modify-service-files-and-create-expirer-cron-script.patch -- In the new version, on line 190, the patch states that the old code covered 6 lines, and the new code covers 9 lines (-283,6 +286,9). But there are only two lines inserted by the patch. There is also a new blank line in the patch at line 194. Removing this blank line and editing the hunk description to only insert 2 lines resolves the issue for this hunk (there are other similar issues in this patch, and in 0001-meta-modify-aodh-api.patch) [slin14]: Let me double check it. - At binary build time, I had build failures on python-django-horizon and some magnum packages. I had to pull in https://review.openstack.org/#/c/596855/2 (from the master branch, but not in the centos75 branch of stx-upstream) to get past this. [slin14]: It is due to I have not synced latest master code, so I don’t have this issue. I used last week’s master code. - After building all packages, I attempted to build the ISO. The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should be added to the .lst files. [slin14]: This package is already in the lst. - Furthermore, the tpm2-tools package was requesting version tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I hacked the spec file for tpm2-tools and rebuilt it to require the version mentioned, but there is some rework to be done there. [slin14]: I have the same issue also. Let’s further check it to find the root cause. I use rebuild tpm2-tools/tss2 to workaround it without any code. After these changes, I was able to produce a .iso -Jason From: McKenna, Jason > Sent: September 7, 2018 10:08 AM To: Khalil, Ghada >; Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, As a download_mirrors.sh time issue, the version of lighttpd has been changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or CentOS servers, as they’ve moved to 1.4.50. I am attempting to locate an archived version of the 1.4.49 .src rpm. -Jason From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' >; Xie, Cindy >; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be priming this activity. He’ll share the results with the team sometime next week. Regards, Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 07, 2018 1:32 AM To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy Subject: CentOS 7.5 upgrade status update Hi all, Most task of CentOS7.5 upgrade in story 2003389 is done. Please go ahead to have a try and verify it. I expect there should be some issue due to we just did limited deploy test yet. Here is the detail status update of this week. For the total 44 srpm we plan to upgrade: 38 already merged in feature branch. 3 kept as original version. Anaconda upgrade is not needed. python-os-vif has higher version than 7.5. python-eventlet kept due to new src rpm itself have known issue. 2 under review with code ready. Puppet-haproxy and openstack-aodh. 1 under debug. Lighttpd. Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. Here is the build instruction: 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx-upstream/stx-root. Cherry-pick below un-merged patch: For puppet-haproxy: https://review.openstack.org/600369 https://review.openstack.org/600359 For openstack-aodh: https://review.openstack.org/598388 https://review.openstack.org/600591 For build-iso: https://review.openstack.org/599892 For build-pkgs: https://review.openstack.org/599901 https://review.openstack.org/600639 2. Run mirror script to get the upgraded src rpm and related rpm. 3. Try to build packages and ISO. For the detail status of CentOS7.5 upgrade, please check below story: https://storyboard.openstack.org/#!/story/2003389 Feel free to contact me if you have trouble on it. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Sep 11 14:58:48 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 11 Sep 2018 08:58:48 -0600 Subject: [Starlingx-discuss] PTG information and agenda Message-ID: <8F5A73B4-F30C-4579-9D43-B691B3AD209B@gmail.com> Hi, We are having our whole day sessions at the PTG around edge related topics. You can dial in remotely using the following call details: • Zoom link: https://zoom.us/j/736245798 • 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: 736 245 798 • International numbers available: https://zoom.us/u/ed95sU7aQ For the agenda please see the following etherpad: https://etherpad.openstack.org/p/EdgeComputingGroupPTG4 For the daily progress please monitor #openstack-ptg on IRC and/or the following web page: http://ptg.openstack.org/ptg.html Please let me know if you have any questions. Thanks and Best Regards, Ildikó (IRC: ildikov) From erich.cordoba.malibran at intel.com Tue Sep 11 15:17:18 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 11 Sep 2018 15:17:18 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi You can add "debug loglevel=8" to the kernel boot option to get a more detailed output of the crash (if any) -Erich On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > Shuicheng saw the symbol table error issue as well but it recovers in > 8s, he is still working on debugging it. But 601204 is just kernel > upgrade but not intended to solve this issues. Are you running bare > metal? I am wondering if this is HW config and driver issue. > > Is it possible that you try to deploy it in virtual environment? > > Thx. - cindy > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Tuesday, September 11, 2018 9:50 PM > To: Xie, Cindy ; Rasa, Nimalini indriver.com>; Waheed, Numan ; Lin, > Shuicheng ; Liu, ZhipengS l.com>; Khalil, Ghada ; 'starlingx-discus > s at lists.starlingx.io' > Subject: RE: CentOS 7.5 upgrade status update > > Hi Cindy, > > We got past the installation device error, but are coming up against > the symbol table error. Our system hangs after this message. I > suspect a kernel issue. I see there is an open code review to > refactor some kernel patches to a rebased kernel (https://review.open > stack.org/#/c/601204/) but I do not know if that is expected to > resolve the issue > > -J > > From: Xie, Cindy > Sent: September 11, 2018 9:32 AM > To: Rasa, Nimalini ; Waheed, Numan n.Waheed at windriver.com>; Lin, Shuicheng ; > McKenna, Jason ; Liu, ZhipengS .liu at intel.com>; Khalil, Ghada ; 'starlin > gx-discuss at lists.starlingx.io' > Subject: RE: CentOS 7.5 upgrade status update > > But as Jason reported yesterday, the build cannot be installed with > error messages: > > Installation failed. > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > We cannot debug without more information, the ISO installs in Intel’s > HW. Thus Shuicheng created a new build and attached a manifest in > this email thread. Did WindRiver has a chance to create a new ISO > using today’s manifest file and re-run the test? > > Thx. - cindy > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > Sent: Tuesday, September 11, 2018 9:25 PM > To: Xie, Cindy ; Waheed, Numan driver.com>; Lin, Shuicheng ; McKenna, Jason > ; Liu, ZhipengS > ; Khalil, Ghada ; 'starlingx-discuss at list > s.starlingx.io' > Subject: RE: CentOS 7.5 upgrade status update > > This is on the same build (yesterday’s build). > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > Sent: Tuesday, September 11, 2018 9:22 AM > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; > Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: CentOS 7.5 upgrade status update > > Is this the same issue as yesterday’s build? or this is different > issue now? > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > Sent: Tuesday, September 11, 2018 9:06 PM > To: Waheed, Numan ; Lin, Shuicheng heng.lin at intel.com>; McKenna, Jason ; > Liu, ZhipengS ; Khalil, Ghada indriver.com>; 'starlingx-discuss at lists.starlingx.io' uss at lists.starlingx.io>; Xie, Cindy > Subject: RE: CentOS 7.5 upgrade status update > > It is not booting in my case. After the following , it just hangs > there: > “Error: no symbol table. > Press any key to continue…” > > -Nimalini > > From: Waheed, Numan > Sent: Tuesday, September 11, 2018 8:50 AM > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'st > arlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, Nimalini > Subject: RE: CentOS 7.5 upgrade status update > > Adding Nimalini > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > Sent: September-11-18 2:17 AM > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss@ > lists.starlingx.io'; Xie, Cindy; Waheed, Numan > Subject: RE: CentOS 7.5 upgrade status update > > Hi Jason, > Just finished deploy image with latest code, I could config > controller successfully in bare metal environment. > Manifest is created for you reference. There are two patches I add > manually: > https://review.openstack.org/596855           for python-horizon > from master > https://review.openstack.org/599892           for build-iso > > > There is an issue found when reboot controller node. > After the OS selection menu, it will show below error. And it will > auto continue boot after around 8 seconds. I will check the issue > later. > “ > Error: no symbol table. > Press any key to continue… > “ > > Best Regards > Shuicheng > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > Sent: Tuesday, September 11, 2018 9:35 AM > To: McKenna, Jason ; Liu, ZhipengS engs.liu at intel.com>; Khalil, Ghada ; 'sta > rlingx-discuss at lists.starlingx.io' .io>; Xie, Cindy ; Waheed, Numan indriver.com> > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Jason, > I just tried my last Friday’s image at bare metal machine. There is > no issue to install controller node. > Will you help check what cause the install error in your environment? > > I am syncing my code to latest to double confirm it. > > Best Regards > Shuicheng > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Tuesday, September 11, 2018 12:13 AM > To: Liu, ZhipengS ; Lin, Shuicheng .lin at intel.com>; Khalil, Ghada ; 'starlin > gx-discuss at lists.starlingx.io' > ; Xie, Cindy ; Waheed, Numan iver.com> > Subject: RE: CentOS 7.5 upgrade status update > > Status update. The build from the centos75 branch does not install > on our hardware. The error message we are seeing is: > > Installation failed. > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > -Jason > > From: Liu, ZhipengS > Sent: September 8, 2018 9:56 AM > To: Lin, Shuicheng ; McKenna, Jason cKenna at windriver.com>; Khalil, Ghada ; 's > tarlingx-discuss at lists.starlingx.io' gx.io>; Xie, Cindy ; Waheed, Numan @windriver.com> > Subject: RE: CentOS 7.5 upgrade status update > > Hi Jason, > > I have fixed the issue you mentioned below. > - Furthermore, the tpm2-tools package was requesting version > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > hacked the spec file for tpm2-tools and rebuilt it to require the > version mentioned, but there is some rework to be done there. > [slin14]: I have the same issue also. Let’s further check it to find > the root cause. I use rebuild tpm2-tools/tss2 to workaround it > without any code. > > https://review.openstack.org/#/c/600920/ > > Thanks! > Zhipeng > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > Sent: 2018年9月8日 21:14 > To: McKenna, Jason ; Khalil, Ghada a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' lingx-discuss at lists.starlingx.io>; Xie, Cindy ; > Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Jason, > I have fixed the error in the openstack-aodh. Patch is updated: > https://review.openstack.org/#/c/598388/ > > It is due to my local version is not the latest one. > Sorry for the trouble caused, and thanks for your test. > > Best Regards > Shuicheng > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > Sent: Saturday, September 8, 2018 9:23 AM > To: McKenna, Jason ; Khalil, Ghada a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' lingx-discuss at lists.starlingx.io>; Xie, Cindy ; > Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Jason, > Thanks very much for such detail feedback. > I added some comments inline, and will check the issue in my > environment also. > Feel free to submit patch if you have to fix them. J > > > Best Regards > Shuicheng > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Saturday, September 8, 2018 3:47 AM > To: McKenna, Jason ; Khalil, Ghada a.Khalil at windriver.com>; Lin, Shuicheng ; 's > tarlingx-discuss at lists.starlingx.io' gx.io>; Xie, Cindy ; Waheed, Numan @windriver.com> > Subject: RE: CentOS 7.5 upgrade status update > > Hi Shuicheng, > > I’ve completed a build of the code. We have not yet run run-time > tests, but here are the build-time issues I encountered: > > - The .lst file contains lighttpd-1.4.49, but this is no > longer available for download, and the download_mirrors.sh step > fails. It appears than CentOS has updated to lighttpd-1.4.50. I > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > - Even though the .lst file specifies lighttpd-1.4.49, the > code still references 1.4.45 > - At build-pkgs time (the build-srpms step), the meta-patches > to openstack-aodh do not apply, as two of them are malformed. https: > //review.openstack.org/#/c/598388/6/openstack/openstack- > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > expirer-cron-script.patch -- In the new version, on line 190, the > patch states that the old code covered 6 lines, and the new code > covers 9 lines (-283,6 +286,9). But there are only two lines > inserted by the patch. There is also a new blank line in the patch > at line 194. Removing this blank line and editing the hunk > description to only insert 2 lines resolves the issue for this hunk > (there are other similar issues in this patch, and in 0001-meta- > modify-aodh-api.patch) > [slin14]: Let me double check it. > - At binary build time, I had build failures on python-django- > horizon and some magnum packages. I had to pull in https://review.op > enstack.org/#/c/596855/2 (from the master branch, but not in the > centos75 branch of stx-upstream) to get past this. > [slin14]: It is due to I have not synced latest master code, so I > don’t have this issue. I used last week’s master code. > - After building all packages, I attempted to build the ISO. > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should > be added to the .lst files. > [slin14]: This package is already in the lst. > - Furthermore, the tpm2-tools package was requesting version > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > hacked the spec file for tpm2-tools and rebuilt it to require the > version mentioned, but there is some rework to be done there. > [slin14]: I have the same issue also. Let’s further check it to find > the root cause. I use rebuild tpm2-tools/tss2 to workaround it > without any code. > > After these changes, I was able to produce a .iso > > -Jason > > From: McKenna, Jason > Sent: September 7, 2018 10:08 AM > To: Khalil, Ghada ; Lin, Shuicheng heng.lin at intel.com>; 'starlingx-discuss at lists.starlingx.io' x-discuss at lists.starlingx.io>; Xie, Cindy ; > Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Shuicheng, > > As a download_mirrors.sh time issue, the version of lighttpd has been > changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm > file no longer exists on EPEL or CentOS servers, as they’ve moved to > 1.4.50. I am attempting to locate an archived version of the 1.4.49 > .src rpm. > > -Jason > > From: Khalil, Ghada > Sent: September 7, 2018 9:36 AM > To: Lin, Shuicheng ; 'starlingx-discuss at list > s.starlingx.io' ; Xie, Cindy indy.xie at intel.com>; Waheed, Numan > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be > priming this activity. He’ll share the results with the team sometime > next week. > > Regards, > Ghada > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > Sent: Friday, September 07, 2018 1:32 AM > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy > Subject: CentOS 7.5 upgrade status update > > Hi all, > Most task of CentOS7.5 upgrade in story 2003389 is done. Please go > ahead to have a try and verify it. > I expect there should be some issue due to we just did limited deploy > test yet. > > Here is the detail status update of this week. > For the total 44 srpm we plan to upgrade: > 38 already merged in feature branch. > 3 kept as original version. Anaconda upgrade is not needed. python- > os-vif has higher version than 7.5. python-eventlet kept due to new > src rpm itself have known issue. > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > 1 under debug. Lighttpd. > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > Here is the build instruction: > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > upstream/stx-root. > Cherry-pick below un-merged patch: > For puppet-haproxy: > https://review.openstack.org/600369 > https://review.openstack.org/600359 > For openstack-aodh: > https://review.openstack.org/598388 > https://review.openstack.org/600591 > For build-iso: > https://review.openstack.org/599892 > For build-pkgs: > https://review.openstack.org/599901 > https://review.openstack.org/600639 > > 2. Run mirror script to get the upgraded src rpm and related > rpm. > 3. Try to build packages and ISO. > > For the detail status of CentOS7.5 upgrade, please check below story: > https://storyboard.openstack.org/#!/story/2003389 > > Feel free to contact me if you have trouble on it. > > Best Regards > Shuicheng > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Tue Sep 11 15:36:13 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 11 Sep 2018 10:36:13 -0500 Subject: [Starlingx-discuss] [distcloud] The Distributed Cloud repos are up In-Reply-To: References: Message-ID: On Thu, Sep 6, 2018 at 1:12 PM, Dean Troyer wrote: > Once those are merged we can change the master manifest to pull these > from Gerrit, then I will rename the repos in starlingx-staging to make > them fail in outdated configurations followed by eventual removal. The change to the master manifest merged last Friday, I will rename the Github repos [0][1] this Friday (14 Sep) if there are no objections. > We should now consider the DC staging repos to be read-only, any > further commits there will be lost. dt [0] https://git.starlingx.io/cgit/stx-distcloud/ [1] https://git.starlingx.io/cgit/stx-distcloud-client/ -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Tue Sep 11 15:46:12 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 11 Sep 2018 15:46:12 +0000 Subject: [Starlingx-discuss] Project meeting Wednesday Sep 12 Message-ID: <9A85D2917C58154C960D95352B22818BAB58C3B0@fmsmsx115.amr.corp.intel.com> Here is the current agenda for our project team call on Wednesday Sep 12th 7AM PDT / 1400 UTC. Please feel free to add any other topics to the etherpad [0]. Agenda and notes for the 9/12 meeting * Let's try to hold this to a 30 minute call * Mainline bugs that already under debug: o https://bugs.launchpad.net/starlingx/+bug/1790213 o https://bugs.launchpad.net/starlingx/+bug/1790716 * CentOS7.5 feature branch merge back. * Build issues - different results between Intel and WR * Other release issues * Other urgent topics - help needed, blocking bugs, etc... [0] https://etherpad.openstack.org/p/stx-status -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Tue Sep 11 15:54:18 2018 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 11 Sep 2018 15:54:18 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> Message-ID: <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> Hi Ghada, Yes, before shared our ISOs I followed such steps and got the same issues. As I mention in the issue (https://bugs.launchpad.net/starlingx/+bug/1790213), I could get the ISO from Michel and testes in our infrastructure, issues not found. I guess there are differences between the way an ISO is built by Intel and Wind River since Intel got issues but Wind River does not. I think we should sync about this. Besides, our test infrastructure uses other commands to generate VMs, add/install hosts (controllers and computes), such commands was gotten from "tic_vb" repo, such repo was given by China team, if I am not wrong such repo was based on Wind River documentation; our test framework is based on "tic_vb". Anyway both ways got the same results. Regards. Juan Carlos Alonso -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, September 11, 2018 8:53 AM To: Alonso, Juan Carlos ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io; Thebeau, Michel Subject: RE: [ Test ] Sanity results - summary posted Hello Juan, I read the notes in the Launchpad. And, just to confirm, are you following the instructions under: https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Controller_Storage and still reproducing the two issues below? I was not able to definitively tell from the Launchpad notes. It's important that both our teams are comparing apples to apples. Thanks, Ghada -----Original Message----- From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Monday, September 10, 2018 1:50 PM To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel Subject: RE: [ Test ] Sanity results - summary posted Hi, Such launchpads were updated. A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two issues. Michael will upload his ISO, then we will re test witch each iso in our environment. An script is being developed to get the differences between ISOs. Regards. Juan Carlos Alonso -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Friday, September 7, 2018 4:43 PM To: Khalil, Ghada ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io; Thebeau, Michel Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hi Elio/Ada, Are there any updates from your side on these two Launchpads? https://bugs.launchpad.net/starlingx/+bug/1790213 https://bugs.launchpad.net/starlingx/+bug/1790716 Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team. As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup). Please let us know if you need any further help from us. Thanks, Ghada -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, September 05, 2018 5:39 PM To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Please see inline. There are notes in all the launchpads as well. I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. -----Original Message----- From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Wednesday, September 05, 2018 2:23 PM To: Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted My opinion below -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, September 5, 2018 12:56 PM To: Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Should the bugs coming out of this be tagged/fixed for the October release? Related bugs: https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all instances need at least one compute for multimode [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. The test team points to internal instructions which we have no access to. The supported install recipes need to be on the wiki. I think it is an invalid bug https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Wednesday, September 5, 2018 10:50 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hello all, As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. [0] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary Regards Ada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Jason.McKenna at windriver.com Tue Sep 11 16:21:27 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Tue, 11 Sep 2018 16:21:27 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Cindy, With the latest centos75 branch (and the cherry-picks you mentioned) I am unable to produce a build. There seems to be several source rpm files missing from the currently pushed version of the .lst files (or the .lst files pull down the wrong version). Most of the missing files I can download manually, however the checked in patches for dhcp and centos-release packages do not apply against the version of the source RPM which I can manually find on the Internet. For example, the version of centos-release called out in the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the version called out in the checked in code base is the slightly different centos-release-7-5.1804.el7.centos.1.x86_64.rpm, and the patches checked in do not apply against either package. Until the centos75 branch of the lst files pulls down the correct rpms, I will be unable to continue the validation effort. -J > -----Original Message----- > From: Cordoba Malibran, Erich > Sent: September 11, 2018 11:17 AM > To: Waheed, Numan ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; Liu, > ZhipengS ; Khalil, Ghada > ; Lin, Shuicheng ; > McKenna, Jason ; Xie, Cindy > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi > > You can add "debug loglevel=8" to the kernel boot option to get a more > detailed output of the crash (if any) > > -Erich > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > Shuicheng saw the symbol table error issue as well but it recovers in > > 8s, he is still working on debugging it. But 601204 is just kernel > > upgrade but not intended to solve this issues. Are you running bare > > metal? I am wondering if this is HW config and driver issue. > > > > Is it possible that you try to deploy it in virtual environment? > > > > Thx. - cindy > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Tuesday, September 11, 2018 9:50 PM > > To: Xie, Cindy ; Rasa, Nimalini > indriver.com>; Waheed, Numan ; Lin, > > Shuicheng ; Liu, ZhipengS > l.com>; Khalil, Ghada ; 'starlingx-discus > > s at lists.starlingx.io' > > Subject: RE: CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > We got past the installation device error, but are coming up against > > the symbol table error. Our system hangs after this message. I > > suspect a kernel issue. I see there is an open code review to > > refactor some kernel patches to a rebased kernel (https://review.open > > stack.org/#/c/601204/) but I do not know if that is expected to > > resolve the issue > > > > -J > > > > From: Xie, Cindy > > Sent: September 11, 2018 9:32 AM > > To: Rasa, Nimalini ; Waheed, Numan > > n.Waheed at windriver.com>; Lin, Shuicheng ; > > McKenna, Jason ; Liu, ZhipengS > > .liu at intel.com>; Khalil, Ghada ; 'starlin > > gx-discuss at lists.starlingx.io' > > Subject: RE: CentOS 7.5 upgrade status update > > > > But as Jason reported yesterday, the build cannot be installed with > > error messages: > > > > Installation failed. > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > We cannot debug without more information, the ISO installs in Intel’s > > HW. Thus Shuicheng created a new build and attached a manifest in this > > email thread. Did WindRiver has a chance to create a new ISO using > > today’s manifest file and re-run the test? > > > > Thx. - cindy > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > Sent: Tuesday, September 11, 2018 9:25 PM > > To: Xie, Cindy ; Waheed, Numan > > driver.com>; Lin, Shuicheng ; McKenna, Jason > > ; Liu, ZhipengS > > > ; Khalil, Ghada ; 'starlingx-discuss at list > > s.starlingx.io' > > Subject: RE: CentOS 7.5 upgrade status update > > > > This is on the same build (yesterday’s build). > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > Sent: Tuesday, September 11, 2018 9:22 AM > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; > > Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: CentOS 7.5 upgrade status update > > > > Is this the same issue as yesterday’s build? or this is different > > issue now? > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > Sent: Tuesday, September 11, 2018 9:06 PM > > To: Waheed, Numan ; Lin, Shuicheng > > heng.lin at intel.com>; McKenna, Jason ; > > Liu, ZhipengS ; Khalil, Ghada > indriver.com>; 'starlingx-discuss at lists.starlingx.io' > uss at lists.starlingx.io>; Xie, Cindy > > Subject: RE: CentOS 7.5 upgrade status update > > > > It is not booting in my case. After the following , it just hangs > > there: > > “Error: no symbol table. > > Press any key to continue…” > > > > -Nimalini > > > > From: Waheed, Numan > > Sent: Tuesday, September 11, 2018 8:50 AM > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'st > > arlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, Nimalini > > Subject: RE: CentOS 7.5 upgrade status update > > > > Adding Nimalini > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > Sent: September-11-18 2:17 AM > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss@ > > lists.starlingx.io'; Xie, Cindy; Waheed, Numan > > Subject: RE: CentOS 7.5 upgrade status update > > > > Hi Jason, > > Just finished deploy image with latest code, I could config controller > > successfully in bare metal environment. > > Manifest is created for you reference. There are two patches I add > > manually: > > https://review.openstack.org/596855           for python-horizon from > > master > > https://review.openstack.org/599892           for build-iso > > > > > > There is an issue found when reboot controller node. > > After the OS selection menu, it will show below error. And it will > > auto continue boot after around 8 seconds. I will check the issue > > later. > > “ > > Error: no symbol table. > > Press any key to continue… > > “ > > > > Best Regards > > Shuicheng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > Sent: Tuesday, September 11, 2018 9:35 AM > > To: McKenna, Jason ; Liu, ZhipengS > > engs.liu at intel.com>; Khalil, Ghada ; 'sta > > rlingx-discuss at lists.starlingx.io' > .io>; Xie, Cindy ; Waheed, Numan > > indriver.com> > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > I just tried my last Friday’s image at bare metal machine. There is no > > issue to install controller node. > > Will you help check what cause the install error in your environment? > > > > I am syncing my code to latest to double confirm it. > > > > Best Regards > > Shuicheng > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Tuesday, September 11, 2018 12:13 AM > > To: Liu, ZhipengS ; Lin, Shuicheng > .lin at intel.com>; Khalil, Ghada ; 'starlin > > gx-discuss at lists.starlingx.io' > > ; Xie, Cindy ; Waheed, Numan > > iver.com> > > Subject: RE: CentOS 7.5 upgrade status update > > > > Status update. The build from the centos75 branch does not install on > > our hardware. The error message we are seeing is: > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > -Jason > > > > From: Liu, ZhipengS > > Sent: September 8, 2018 9:56 AM > > To: Lin, Shuicheng ; McKenna, Jason > cKenna at windriver.com>; Khalil, Ghada ; 's > > tarlingx-discuss at lists.starlingx.io' > gx.io>; Xie, Cindy ; Waheed, Numan > > @windriver.com> > > Subject: RE: CentOS 7.5 upgrade status update > > > > Hi Jason, > > > > I have fixed the issue you mentioned below. > > - Furthermore, the tpm2-tools package was requesting version > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > hacked the spec file for tpm2-tools and rebuilt it to require the > > version mentioned, but there is some rework to be done there. > > [slin14]: I have the same issue also. Let’s further check it to find > > the root cause. I use rebuild tpm2-tools/tss2 to workaround it without > > any code. > > > > https://review.openstack.org/#/c/600920/ > > > > Thanks! > > Zhipeng > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > Sent: 2018年9月8日 21:14 > > To: McKenna, Jason ; Khalil, Ghada > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > lingx-discuss at lists.starlingx.io>; Xie, Cindy ; > > Waheed, Numan > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > I have fixed the error in the openstack-aodh. Patch is updated: > > https://review.openstack.org/#/c/598388/ > > > > It is due to my local version is not the latest one. > > Sorry for the trouble caused, and thanks for your test. > > > > Best Regards > > Shuicheng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > Sent: Saturday, September 8, 2018 9:23 AM > > To: McKenna, Jason ; Khalil, Ghada > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > lingx-discuss at lists.starlingx.io>; Xie, Cindy ; > > Waheed, Numan > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Thanks very much for such detail feedback. > > I added some comments inline, and will check the issue in my > > environment also. > > Feel free to submit patch if you have to fix them. J > > > > > > Best Regards > > Shuicheng > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Saturday, September 8, 2018 3:47 AM > > To: McKenna, Jason ; Khalil, Ghada > > a.Khalil at windriver.com>; Lin, Shuicheng ; 's > > tarlingx-discuss at lists.starlingx.io' > gx.io>; Xie, Cindy ; Waheed, Numan > > @windriver.com> > > Subject: RE: CentOS 7.5 upgrade status update > > > > Hi Shuicheng, > > > > I’ve completed a build of the code. We have not yet run run-time > > tests, but here are the build-time issues I encountered: > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > longer available for download, and the download_mirrors.sh step fails. > > It appears than CentOS has updated to lighttpd-1.4.50. I manually > > built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > - Even though the .lst file specifies lighttpd-1.4.49, the > > code still references 1.4.45 > > - At build-pkgs time (the build-srpms step), the meta-patches > > to openstack-aodh do not apply, as two of them are malformed. https: > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > expirer-cron-script.patch -- In the new version, on line 190, the > > patch states that the old code covered 6 lines, and the new code > > covers 9 lines (-283,6 +286,9). But there are only two lines inserted > > by the patch. There is also a new blank line in the patch at line > > 194. Removing this blank line and editing the hunk description to > > only insert 2 lines resolves the issue for this hunk (there are other > > similar issues in this patch, and in 0001-meta- > > modify-aodh-api.patch) > > [slin14]: Let me double check it. > > - At binary build time, I had build failures on python-django- > > horizon and some magnum packages. I had to pull in https://review.op > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > centos75 branch of stx-upstream) to get past this. > > [slin14]: It is due to I have not synced latest master code, so I > > don’t have this issue. I used last week’s master code. > > - After building all packages, I attempted to build the ISO. > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should > > be added to the .lst files. > > [slin14]: This package is already in the lst. > > - Furthermore, the tpm2-tools package was requesting version > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > hacked the spec file for tpm2-tools and rebuilt it to require the > > version mentioned, but there is some rework to be done there. > > [slin14]: I have the same issue also. Let’s further check it to find > > the root cause. I use rebuild tpm2-tools/tss2 to workaround it without > > any code. > > > > After these changes, I was able to produce a .iso > > > > -Jason > > > > From: McKenna, Jason > > Sent: September 7, 2018 10:08 AM > > To: Khalil, Ghada ; Lin, Shuicheng > heng.lin at intel.com>; 'starlingx-discuss at lists.starlingx.io' > x-discuss at lists.starlingx.io>; Xie, Cindy ; > > Waheed, Numan > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Shuicheng, > > > > As a download_mirrors.sh time issue, the version of lighttpd has been > > changed from 1.4.45 to 1.4.49. The lighttpd-1.4.49-1.el7.src.rpm file > > no longer exists on EPEL or CentOS servers, as they’ve moved to > > 1.4.50. I am attempting to locate an archived version of the 1.4.49 > > .src rpm. > > > > -Jason > > > > From: Khalil, Ghada > > Sent: September 7, 2018 9:36 AM > > To: Lin, Shuicheng ; 'starlingx-discuss at list > > s.starlingx.io' ; Xie, Cindy > indy.xie at intel.com>; Waheed, Numan > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be > > priming this activity. He’ll share the results with the team sometime > > next week. > > > > Regards, > > Ghada > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > Sent: Friday, September 07, 2018 1:32 AM > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, Cindy > > Subject: CentOS 7.5 upgrade status update > > > > Hi all, > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please go > > ahead to have a try and verify it. > > I expect there should be some issue due to we just did limited deploy > > test yet. > > > > Here is the detail status update of this week. > > For the total 44 srpm we plan to upgrade: > > 38 already merged in feature branch. > > 3 kept as original version. Anaconda upgrade is not needed. python- > > os-vif has higher version than 7.5. python-eventlet kept due to new > > src rpm itself have known issue. > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > 1 under debug. Lighttpd. > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > Here is the build instruction: > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > upstream/stx-root. > > Cherry-pick below un-merged patch: > > For puppet-haproxy: > > https://review.openstack.org/600369 > > https://review.openstack.org/600359 > > For openstack-aodh: > > https://review.openstack.org/598388 > > https://review.openstack.org/600591 > > For build-iso: > > https://review.openstack.org/599892 > > For build-pkgs: > > https://review.openstack.org/599901 > > https://review.openstack.org/600639 > > > > 2. Run mirror script to get the upgraded src rpm and related > > rpm. > > 3. Try to build packages and ISO. > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > https://storyboard.openstack.org/#!/story/2003389 > > > > Feel free to contact me if you have trouble on it. > > > > Best Regards > > Shuicheng > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From jose.perez.carranza at intel.com Tue Sep 11 16:29:23 2018 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Tue, 11 Sep 2018 16:29:23 +0000 Subject: [Starlingx-discuss] Bi-Weekly StarlingX Test meeting - 9:00 PDT In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A8CD540@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A8CD540@fmsmsx101.amr.corp.intel.com> Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A8CEB35@fmsmsx101.amr.corp.intel.com> Hi All Today's meeting was postponed due lack of quorum, most of people was on PTG Meeting. @Ada are you able to reschedule for next week please. Regards, José -----Original Appointment----- From: Cabrales, Ada Sent: Tuesday, September 4, 2018 4:51 PM To: Cabrales, Ada; Alonso, Juan Carlos; Anaya casas, Hazzim I; Gomez, Juan P; Hernandez Gonzalez, Fernando; Martinez Monroy, Elio; Perez Carranza, Jose; Perez Ibarra, Maria G; Perez, Ricardo O; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Bi-Weekly StarlingX Test meeting - 9:00 PDT When: Tuesday, September 11, 2018 11:00 AM-12:00 PM (UTC-06:00) Guadalajara, Mexico City, Monterrey. Where: https://zoom.us/j/342730236 Bi-weekly meetings on Tuesdays at 9am PDT / 1600 UTC * Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes: https://etherpad.openstack.org/p/stx-test -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jason.McKenna at windriver.com Tue Sep 11 16:32:12 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Tue, 11 Sep 2018 16:32:12 +0000 Subject: [Starlingx-discuss] [Build] Feedback on stxb demo In-Reply-To: <6594B51DBE477C48AAE23675314E6C465993F282@fmsmsx107.amr.corp.intel.com> References: , <12f082a2-f28d-ad8e-6fa2-336c0d945513@linux.intel.com> <6594B51DBE477C48AAE23675314E6C465993F282@fmsmsx107.amr.corp.intel.com> Message-ID: Hi Mario, > -----Original Message----- > From: Arevalo, Mario Alfredo C > Sent: September 10, 2018 4:57 PM > To: Saul Wold ; McKenna, Jason > ; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: [Starlingx-discuss] [Build] Feedback on stxb demo > > Hi folks, > > I have been seen excellent ideas that we can to add to the tool, however I > think we are walking a little out of the first scope, what do you think if we > include this as first version a we can post our ideas in the storyboard?: I agree that we can put it out as a first preview version, however I would have strong reservations about changing the wiki documentation to suggest that this is "the official way to build" at this time. > > https://storyboard.openstack.org/#!/story/2003712 +1 to the consolidation of docker images, and it sounds like that part's done. Good job! > > Then we can track all ideas suggested :) Yeah, I think we should have ideally had a discussion about use cases and requirements before the tool was designed. In particular, I do not think the tool (as demoed) is usable by developers. I understand that your requirements are to come up with an end-to-end tool that would produce a build with as few commands as possible, but the current architecture of having a second repo inside the docker container is a deal-breaker for any developer trying to work on the code. I'm all for designing and using better tools, but we shouldn't make this the official way of doing things if it places a new non-trivial burden on the devs. There might be some wiggle room on my suggestion to support a native (rather than containerized) build. As a tangential note, are you able to confirm that the use of a local mirror of packages rather than a download into the container from the Internet is working? We don't want to introduce a change that would unnecessarily add hours to a build. > > Best regards. > Mario. > ________________________________________ > From: Saul Wold [sgw at linux.intel.com] > Sent: Monday, September 10, 2018 10:33 AM > To: McKenna, Jason; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] [Build] Feedback on stxb demo > > Sorry I missed this today, I am in Denver. > > Can you point me at the repo you are working in please? > > On 09/10/2018 09:02 AM, McKenna, Jason wrote: > > Hi build team, > > > > Many thanks for the demo today, I think we're on the right track. As > > promised, here are a few feedback points on the demo, from the > > perspective of a developer: > > > > -I really like how the creation of the docker image is streamlined. > > > > -The system as currently demo'd as two copies of the repos. One in > > /(developers_path)/, and a second in > > /(developers_path)/stx- > tools/(docker_image_root_dir)/localdisk/designer/builder/starlingx/. > > There should only one repo downloaded. > > > > oAs a related point, a developer working on changes to a file would > > expect to make their changes to the repo in /(developers_path)/, > > rather than to the version in the docker image's filesystem. If I > > edited a puppet manifest (for example) > > /(developers_path)/cgcs-root/stx/stx-config/.../ then I would expect the > > build command to detect and use my changes if I do a build. > > > > -I'm a bit confused on the syntax regarding specifying and using > > localized mirrors, specifically with the -n and -p options. Would you > > provide examples of what commands I'd execute for use cases 1 and 2 > > below? I'm pretty sure these usages are supported, but am just seeking > > clarification. > > > > -Very happy do see it down to 1 docker image, rather than 2 J > > > > -Native build - Being able to build in a docker image is great, but > > the would ideally be an option to perform a native build, rather than > > have to use a container > > > > -Minor nit - logs should be in a user directory (like > > $MY_REPO_ROOT_DIR/logs/) rather than in /var/log, as a non-privileged > > user wouldn't be able to log to /var/log. > > > > -Question - what privileges are required to create the docker image? > > Does the script assume the user has sudo privileges? > > > > -I'm unclear on what would happen with use cases 3-5 below. Have > > these types of uses been considered yet? > > > Jason, > > Thanks for this feedback and the use case suggestions below, see additional > comments. > > > Thanks again for the demo, > > > > -Jason > > > > Use Case 1: > > > > I am an organization with a site who is working with > > StarlingX. I want to provide a local mirror for my employees to use > > so they don't have to download all artifacts from the external > > internet every time. I want to create an automated job which I will > > run daily to download all artifacts from the Internet (if they do not > > already exist) and place them in directory /export/mirrors/starlingx. > > Assume the user running the automated job has permissions to write to > > /export/mirrors/starlingx > > > Based on your usage of /export and /import below, /export is on a server > machine and /import is on the local developer build machine, just for > clarification. > > Also, this job would run native on the host Linux OS not containerized? > > > > Use Case 2: > > > > I am a developer within an organization which has a > > local mirror of artifacts available in /import/mirrors/starlingx. I > > want to build a StarlingX ISO without downloading rpms or src.rpms > > from the external internet. > > > To further clarify this one, the remote mirror could contain all binary rpms > along with their cooresponding src rpm, such that if no changes all the > building of an ISO would be done from the mirror rpms, no actual local rpm > build required unless it changes (use case 4/5 below). > > > Use Case 3A: > > > > After doing a build, I just performed a repo sync, > > and the .lst files were not updated. If I perform another build of > > the ISO, will the system attempt to redownload external artifacts, > > even though nothing has changed? > > > > Use Case 3B: > > > > After doing a build, I just performed a repo sync, > > and noticed that the .lst files have been updated. If I perform > > another build of the ISO, will the stale mirror content be detected > > and the new additions downloaded (while not re-downloading anything > > which has not changed)? > > > > Use Case 4: > > > > I have manually made a change to a puppet manifest in > > sysinv (stx-config git) but want to test before I commit anything. > > How can I build a new ISO with my changes incorporated? > > > I would say not just puppet manifest, but any change to files in the repos. > > > Use Case 5: > > > > I want to test StarlingX with my own additional > > program > > (foobar.x86_64.rpm) on the ISO. How would I perform a build with this > > file added? > > > I look forward to seeing the demo also. > > Sau! > > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Tue Sep 11 17:24:57 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 11 Sep 2018 12:24:57 -0500 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> Message-ID: On Tue, Sep 11, 2018 at 11:21 AM, McKenna, Jason wrote: > Until the centos75 branch of the lst files pulls down the correct rpms, I will be unable to continue the validation effort. The f/centos75 branch is only periodically rebased on master, it sounds like this is what you need. I will do a test run to see if it is clean soon... (at PTG) dt -- Dean Troyer dtroyer at gmail.com From cesar.lara at intel.com Tue Sep 11 17:43:46 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Tue, 11 Sep 2018 17:43:46 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> Message-ID: <0B566C62EC792145B40E29EFEBF1AB4710503768@fmsmsx104.amr.corp.intel.com> Hi all, Just wanted to point out that, to be able to reproduce the issues from Intel's ISO, somebody will need to go and create a build environment from scratch, using external upstream repositories to generate a new mirror, just the way we are doing it in our environment. Failing to do this will result in a apples to oranges comparison. Regards Cesar Lara -----Original Message----- From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Tuesday, September 11, 2018 10:54 AM To: Khalil, Ghada ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io; Thebeau, Michel Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hi Ghada, Yes, before shared our ISOs I followed such steps and got the same issues. As I mention in the issue (https://bugs.launchpad.net/starlingx/+bug/1790213), I could get the ISO from Michel and testes in our infrastructure, issues not found. I guess there are differences between the way an ISO is built by Intel and Wind River since Intel got issues but Wind River does not. I think we should sync about this. Besides, our test infrastructure uses other commands to generate VMs, add/install hosts (controllers and computes), such commands was gotten from "tic_vb" repo, such repo was given by China team, if I am not wrong such repo was based on Wind River documentation; our test framework is based on "tic_vb". Anyway both ways got the same results. Regards. Juan Carlos Alonso -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, September 11, 2018 8:53 AM To: Alonso, Juan Carlos ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io; Thebeau, Michel Subject: RE: [ Test ] Sanity results - summary posted Hello Juan, I read the notes in the Launchpad. And, just to confirm, are you following the instructions under: https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Controller_Storage and still reproducing the two issues below? I was not able to definitively tell from the Launchpad notes. It's important that both our teams are comparing apples to apples. Thanks, Ghada -----Original Message----- From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Monday, September 10, 2018 1:50 PM To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel Subject: RE: [ Test ] Sanity results - summary posted Hi, Such launchpads were updated. A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two issues. Michael will upload his ISO, then we will re test witch each iso in our environment. An script is being developed to get the differences between ISOs. Regards. Juan Carlos Alonso -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Friday, September 7, 2018 4:43 PM To: Khalil, Ghada ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io; Thebeau, Michel Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hi Elio/Ada, Are there any updates from your side on these two Launchpads? https://bugs.launchpad.net/starlingx/+bug/1790213 https://bugs.launchpad.net/starlingx/+bug/1790716 Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team. As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup). Please let us know if you need any further help from us. Thanks, Ghada -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, September 05, 2018 5:39 PM To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Please see inline. There are notes in all the launchpads as well. I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. -----Original Message----- From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Wednesday, September 05, 2018 2:23 PM To: Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted My opinion below -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, September 5, 2018 12:56 PM To: Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Should the bugs coming out of this be tagged/fixed for the October release? Related bugs: https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all instances need at least one compute for multimode [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. The test team points to internal instructions which we have no access to. The supported install recipes need to be on the wiki. I think it is an invalid bug https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Wednesday, September 5, 2018 10:50 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted Hello all, As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. [0] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary Regards Ada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Tue Sep 11 18:07:23 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 11 Sep 2018 13:07:23 -0500 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> Message-ID: On Tue, Sep 11, 2018 at 12:24 PM, Dean Troyer wrote: > The f/centos75 branch is only periodically rebased on master, it > sounds like this is what you need. I will do a test run to see if it > is clean soon... (at PTG) The only conflict is in stx-integ in .zuul.yaml, which I can clean up easily enough. We need to do this before merging back in to master anyway...shall I go ahead with the rebase? dt -- Dean Troyer dtroyer at gmail.com From Jason.McKenna at windriver.com Tue Sep 11 18:12:24 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Tue, 11 Sep 2018 18:12:24 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> Message-ID: > -----Original Message----- > From: Dean Troyer > Sent: September 11, 2018 2:07 PM > To: McKenna, Jason > Cc: Cordoba Malibran, Erich ; Waheed, > Numan ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; Liu, > ZhipengS ; Khalil, Ghada > ; Lin, Shuicheng ; > Xie, Cindy > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > On Tue, Sep 11, 2018 at 12:24 PM, Dean Troyer wrote: > > The f/centos75 branch is only periodically rebased on master, it > > sounds like this is what you need. I will do a test run to see if it > > is clean soon... (at PTG) > > The only conflict is in stx-integ in .zuul.yaml, which I can clean up easily > enough. > > We need to do this before merging back in to master anyway...shall I go > ahead with the rebase? Hi Dean, It doesn't seem like the issue is a rebase. It's that code in some repos (stx-integ, for example) was updated to build against new versions of source rpms, but the .lst files currently (or at least as of when I sync'd) checked in in stx-tools call out old or different versions to be downloaded and put into the build environment. Most of the out-of-sync files can be downloaded manually, but some of them aren't accepting the checked in patches. > > dt > > -- > > Dean Troyer > dtroyer at gmail.com From michel.thebeau at windriver.com Tue Sep 11 19:09:07 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Tue, 11 Sep 2018 15:09:07 -0400 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Ghada, I have posted a comment on #1790716 recommending closing that bug, but referring everyone to #1790213. I have not yet received the iso named stx-2018-08-30-97, but the iso stx-2018-08-28-88 presented a broken installer on the controller-1 console: " Error populating transaction after 10 retries: failure: Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm from anaconda: [Errno 256] No more mirrors to try." I think one could refocus on finding out why the installer broke after 2018-08-25-81, before 2018-08-28-88 M On 2018-09-11 09:53 AM, Khalil, Ghada wrote: > Hello Juan, > I read the notes in the Launchpad. > > And, just to confirm, are you following the instructions under: https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Controller_Storage > and still reproducing the two issues below? > > I was not able to definitively tell from the Launchpad notes. It's important that both our teams are comparing apples to apples. > > Thanks, > Ghada > > -----Original Message----- > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > Sent: Monday, September 10, 2018 1:50 PM > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > Subject: RE: [ Test ] Sanity results - summary posted > > Hi, > > Such launchpads were updated. > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two issues. Michael will upload his ISO, then we will re test witch each iso in our environment. > > An script is being developed to get the differences between ISOs. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Friday, September 7, 2018 4:43 PM > To: Khalil, Ghada ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hi Elio/Ada, > Are there any updates from your side on these two Launchpads? > https://bugs.launchpad.net/starlingx/+bug/1790213 > https://bugs.launchpad.net/starlingx/+bug/1790716 > > Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team. > As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup). > > Please let us know if you need any further help from us. > > Thanks, > Ghada > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Wednesday, September 05, 2018 5:39 PM > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Please see inline. There are notes in all the launchpads as well. > > I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. > > -----Original Message----- > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > Sent: Wednesday, September 05, 2018 2:23 PM > To: Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > My opinion below > > -----Original Message----- > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > Sent: Wednesday, September 5, 2018 12:56 PM > To: Cabrales, Ada ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Should the bugs coming out of this be tagged/fixed for the October release? > > Related bugs: > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all instances need at least one compute for multimode [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. The test team points to internal instructions which we have no access to. The supported install recipes need to be on the wiki. I think it is an invalid bug > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. > > -----Original Message----- > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > Sent: Wednesday, September 5, 2018 10:50 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hello all, > > As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). > > Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. > > > [0] https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary > > Regards > Ada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Tue Sep 11 19:46:38 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 11 Sep 2018 13:46:38 -0600 Subject: [Starlingx-discuss] Edge sessions on the PTG, afternoon slot started Message-ID: The afternoon sessions have just started, the dial-in information and links are the same as we used in the morning: • Zoom link: https://zoom.us/j/736245798 • 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: 736 245 798 • International numbers available: https://zoom.us/u/ed95sU7aQ For the agenda please see the following etherpad: https://etherpad.openstack.org/p/EdgeComputingGroupPTG4 For the daily progress please monitor #openstack-ptg on IRC and/or the following web page: http://ptg.openstack.org/ptg.html Thanks, Ildikó From eddie.ramirez at intel.com Tue Sep 11 17:32:56 2018 From: eddie.ramirez at intel.com (Ramirez, Eddie) Date: Tue, 11 Sep 2018 17:32:56 +0000 Subject: [Starlingx-discuss] The stx-gui challenge Message-ID: This very good news, thank you all! From: "Sullivan, David" Date: Friday, September 7, 2018 at 11:23 AM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] The stx-gui challenge The packaging of stx-gui is complete. The panels present in stx-gui are packaged as starlingx-dashboard and included in the iso build. The manual steps listed below are no longer required, everything is integrated into the build process. David From: Ramirez, Eddie [mailto:eddie.ramirez at intel.com] Sent: Wednesday, August 22, 2018 9:43 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] The stx-gui challenge Hi all, The last few months working on stx-horizon have given me a broad understanding of the customizations, new dependencies, additions and removals of LOCs that WRS have added on top of Horizon. For simplicity, let’s imagine stx-horizon as a superset of horizon that makes stx-specific functionality a reality. The downside of having and maintaining a custom “superset” of horizon is that catching up with upstream is expensive, painful and time-consuming that requires a having solid understanding of this project. In an attempt to alleviate the tedious, rebase work after every upstream release, a pluggable python package that would carry stx-specific functionality was the most sound option and architecture to adopt. Horizon supports “plugins”, the recommended way to extend and add to the functionality that already exists and, after removing more than 25,000 lines of code from stx-horizon, the stx-gui horizon was born. [cid:image001.png at 01D449CB.90B2E960] *the stx-horizon superset of horizon is smaller now* What does the plugin do? Stx-gui isolates new panels (System Inventory, Fault Management, Server Groups, etc), API wrappers for clients (cgtsclient, cgcs_patch, sysinv, etc) and many other utility functions that are specific to the StarlingX project. This architecture helps us to: 1. Significantly improve the way we deal with technical debt: rebases will be easier as more LOCs are moved from stx-horizon to stx-gui, until we end up using the upstream version of horizon ☺ 2. Follow a community well-known architecture for extending horizon: “want to add custom functionality to horizon? Write a plugin”… that’s what you’d hear from the community Another side-benefits from doing this splitting 1. Detected additions that can make horizon upstream better: this process threw light on the upstreaming work that I do in parallel. 2. Detected dead code: some files are still holding portions of code that are never executed 3. Found and documented hard dependencies that must be defined somewhere (requirements.txt) 4. An x-ray for understanding what the development documentation would look like 5. Understanding the dimension of the customizations made by WRS: horizon acts as a proxy between operators/users and API endpoints through python-clients. Future modifications to python-clients and APIs will certainly affect the way Horizon talks to them. What does NOT the plugin do? * It does not remove all of the customizations made to the internals of Horizon, that includes: * Any modification done to existing panels (built in panels like Instances, Containers, etc) * The horizon Framework (the way tables are rendered or respond to user actions) * Fixes to JS files, etc. * Tests * Tabs added to Horizon Panels: Network->Routers->Port Forwarding is an example * It does not specify what dependencies it needs (but they are documented) How do I use it? The steps below are ONLY for development and assuming you’re developing outside of the VM running StarlingX. 1. Git clone stx-horizon and switch to branch post-stx-gui-cleanup, you can find the branch on my github profile or check the PR. 2. cd stx-horizon and create a virtualenv with py27 in it. 3. Install Horizon dependencies:pip install -r requirements.txt 4. Git clone stx-gui in a different directory outside of stx-horizon 5. cd stx-gui and using the same virtualenvironment for stx-horizon, run python setup.py install. This will create a packaged version of the plugin that is accessible by stx-horizon’s venv. 6. Install all stx-gui dependencies 7. Copy enable files inside of stx-gui/starlingx_dashboard/enabled/ to stx-horizon/openstack_dashboard/local/enabled/ 8. Finally, inside of stx-horizon, run the horizon dev server with “python manage.py runserver” The installation can be simplified and automated when building an ISO. I’m not familiar with the process but I can guide by explaining what steps must be followed and in what order. It basically involves moving to the right branches, cloning stx-gui, creating a package and copying files to one directory. Please read the extensive documentation I’ve put on this etherpad for more instructions for better format. What’s next? There will be a number of things to keep in mind from now on, answering some questions can help to understand if a change goes to stx-horizon or stx-gui. Also, the long work to make stx-gui work with Upstream Horizon is still pending, but fairly documented thanks to the splitting process. The developer experience is important too, how can we make working with stx-gui an inviting place for others? Py3 compatibility and many other things that are aligned to our priorities and commitments. Eddie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 25452 bytes Desc: image001.png URL: From Jason.McKenna at windriver.com Tue Sep 11 19:02:17 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Tue, 11 Sep 2018 19:02:17 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <0B566C62EC792145B40E29EFEBF1AB4710503768@fmsmsx104.amr.corp.intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503768@fmsmsx104.amr.corp.intel.com> Message-ID: Hi Cesar, Would you elaborate on what differences you'd expect to see in an empty mirror populated by the download tool, compared to an existing mirror which was updated by the download tool? The mirror tools were written specifically to contain multiple versions of packages. The build environment population tools take the .lst file you have checked out, and places that version from the mirror into your local environment guaranteeing that your build env matches the .lst file. If your mirror contains versions 1.0.0, 1.2.3, and 2.0.0 of a given package, then your environment will only use the version called out in the .lst file you have checked out. This allows the same mirror to be used for multiple branches, for multiple releases, for multiple development environments, etc, and guarantees that a build can be reproduced down the road even if the build inputs disappear from the Internet at some point in the future. As long as all the artifacts named in the .lst file have been downloaded at some point in the past, the build environment produced from a fresh mirror vs a continually updated mirror will be identical. The issue we are observing with the CentOS 7.5 update is that the versions of packages called out in the .lst files for the centos75 branch of stx-tools do not match the versions of packages called out in centos75 branch of the other repos, like stx-integ. The other branches are attempting to patch a (new) version of the source code, but the .lst file is only bringing in (or downloading) and older version of the source. -Jason > -----Original Message----- > From: Lara, Cesar > Sent: September 11, 2018 1:44 PM > To: Alonso, Juan Carlos ; Khalil, Ghada > ; Martinez Monroy, Elio > ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hi all, > > Just wanted to point out that, to be able to reproduce the issues from Intel's > ISO, somebody will need to go and create a build environment from scratch, > using external upstream repositories to generate a new mirror, just the way > we are doing it in our environment. Failing to do this will result in a apples to > oranges comparison. > > Regards > Cesar Lara > > -----Original Message----- > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > Sent: Tuesday, September 11, 2018 10:54 AM > To: Khalil, Ghada ; Martinez Monroy, Elio > ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hi Ghada, > > Yes, before shared our ISOs I followed such steps and got the same issues. > > As I mention in the issue > (https://bugs.launchpad.net/starlingx/+bug/1790213), I could get the ISO > from Michel and testes in our infrastructure, issues not found. I guess there > are differences between the way an ISO is built by Intel and Wind River since > Intel got issues but Wind River does not. I think we should sync about this. > > Besides, our test infrastructure uses other commands to generate VMs, > add/install hosts (controllers and computes), such commands was gotten > from "tic_vb" repo, such repo was given by China team, if I am not wrong > such repo was based on Wind River documentation; our test framework is > based on "tic_vb". Anyway both ways got the same results. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Tuesday, September 11, 2018 8:53 AM > To: Alonso, Juan Carlos ; Martinez Monroy, > Elio ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: RE: [ Test ] Sanity results - summary posted > > Hello Juan, > I read the notes in the Launchpad. > > And, just to confirm, are you following the instructions under: > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Enviro > nment/Controller_Storage > and still reproducing the two issues below? > > I was not able to definitively tell from the Launchpad notes. It's important > that both our teams are comparing apples to apples. > > Thanks, > Ghada > > -----Original Message----- > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > Sent: Monday, September 10, 2018 1:50 PM > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > Subject: RE: [ Test ] Sanity results - summary posted > > Hi, > > Such launchpads were updated. > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two > issues. Michael will upload his ISO, then we will re test witch each iso in our > environment. > > An script is being developed to get the differences between ISOs. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Friday, September 7, 2018 4:43 PM > To: Khalil, Ghada ; Martinez Monroy, Elio > ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hi Elio/Ada, > Are there any updates from your side on these two Launchpads? > https://bugs.launchpad.net/starlingx/+bug/1790213 > https://bugs.launchpad.net/starlingx/+bug/1790716 > > Michel Thebeau (Wind River) has been trying to reproduce these two issues > (following the starlingx wikis) without success for two days now. He has been > adding his findings to the bugs and communicating with your team. > As a result of his investigation, he will be pushing some small fixes to stx- > tools shortly (some cleanup). > > Please let us know if you need any further help from us. > > Thanks, > Ghada > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Wednesday, September 05, 2018 5:39 PM > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx- > discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Please see inline. There are notes in all the launchpads as well. > > I have tagged the last bug for the October release. The rest need more > information to determine whether they gate or not: two maybe procedural > and one requires more information. > > -----Original Message----- > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > Sent: Wednesday, September 05, 2018 2:23 PM > To: Jones, Bruce E; Cabrales, Ada; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > My opinion below > > -----Original Message----- > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > Sent: Wednesday, September 5, 2018 12:56 PM > To: Cabrales, Ada ; starlingx- > discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Should the bugs coming out of this be tagged/fixed for the October release? > > Related bugs: > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is > related with 2nd controller provisioning [[GK]] Using the instructions > published on the wiki, our designer was not able to reproduce this issue. > What instructions are the test team using? > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other > issues are solved, will fail some test cases related to SSH [[GK]] Requested > more information. This cannot be debugged further without this information. > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all instances > need at least one compute for multimode [[GK]] Using the instructions > published on the wiki, our designer was not able to reproduce this issue. The > test team points to internal instructions which we have no access to. The > supported install recipes need to be on the wiki. I think it is an invalid bug > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is > related to FM , test cases will fail [[GK]] As Brent pointed out, this is > dependent on the integration of stx-gui which is in progress. > > -----Original Message----- > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > Sent: Wednesday, September 5, 2018 10:50 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hello all, > > As mentioned on the project meeting today, we're posting the summary of > the sanity test runs on the Test wiki [0]. The sanity is triggered each time an > ISO is generated (a daily task). > > Right now we are posting the results manually, and working on a way for > automating it. Logs of the run are not included, if you want to have them, > you can contact Elio to get them sent to you. > > > [0] > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_S > ummary > > Regards > Ada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cesar.lara at intel.com Tue Sep 11 20:03:43 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Tue, 11 Sep 2018 20:03:43 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503768@fmsmsx104.amr.corp.intel.com> Message-ID: <0B566C62EC792145B40E29EFEBF1AB4710503931@fmsmsx104.amr.corp.intel.com> I just wanted to make sure that we are able to reproduce the issue regardless of the build environment. AFAIK CentOS 7.5 upgrade is a different issue/thread, but at the end we can fine tune a process in which we are in the same conditions to be able to replicate errors in any given build environment. Regards Cesar Lara -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 2:02 PM To: Lara, Cesar ; Alonso, Juan Carlos ; Khalil, Ghada ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io; Thebeau, Michel ; Young, Ken ; Little, Scott Subject: RE: [ Test ] Sanity results - summary posted Hi Cesar, Would you elaborate on what differences you'd expect to see in an empty mirror populated by the download tool, compared to an existing mirror which was updated by the download tool? The mirror tools were written specifically to contain multiple versions of packages. The build environment population tools take the .lst file you have checked out, and places that version from the mirror into your local environment guaranteeing that your build env matches the .lst file. If your mirror contains versions 1.0.0, 1.2.3, and 2.0.0 of a given package, then your environment will only use the version called out in the .lst file you have checked out. This allows the same mirror to be used for multiple branches, for multiple releases, for multiple development environments, etc, and guarantees that a build can be reproduced down the road even if the build inputs disappear from the Internet at some point in the future. As long as all the artifacts named in the .lst file have been downloaded at some point in the past, the build environment produced from a fresh mirror vs a continually updated mirror will be identical. The issue we are observing with the CentOS 7.5 update is that the versions of packages called out in the .lst files for the centos75 branch of stx-tools do not match the versions of packages called out in centos75 branch of the other repos, like stx-integ. The other branches are attempting to patch a (new) version of the source code, but the .lst file is only bringing in (or downloading) and older version of the source. -Jason > -----Original Message----- > From: Lara, Cesar > Sent: September 11, 2018 1:44 PM > To: Alonso, Juan Carlos ; Khalil, Ghada > ; Martinez Monroy, Elio > ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Hi all, > > Just wanted to point out that, to be able to reproduce the issues from > Intel's ISO, somebody will need to go and create a build environment > from scratch, using external upstream repositories to generate a new > mirror, just the way we are doing it in our environment. Failing to do > this will result in a apples to oranges comparison. > > Regards > Cesar Lara > > -----Original Message----- > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > Sent: Tuesday, September 11, 2018 10:54 AM > To: Khalil, Ghada ; Martinez Monroy, Elio > ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Hi Ghada, > > Yes, before shared our ISOs I followed such steps and got the same issues. > > As I mention in the issue > (https://bugs.launchpad.net/starlingx/+bug/1790213), I could get the > ISO from Michel and testes in our infrastructure, issues not found. I > guess there are differences between the way an ISO is built by Intel > and Wind River since Intel got issues but Wind River does not. I think we should sync about this. > > Besides, our test infrastructure uses other commands to generate VMs, > add/install hosts (controllers and computes), such commands was gotten > from "tic_vb" repo, such repo was given by China team, if I am not > wrong such repo was based on Wind River documentation; our test > framework is based on "tic_vb". Anyway both ways got the same results. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Tuesday, September 11, 2018 8:53 AM > To: Alonso, Juan Carlos ; Martinez > Monroy, Elio ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: RE: [ Test ] Sanity results - summary posted > > Hello Juan, > I read the notes in the Launchpad. > > And, just to confirm, are you following the instructions under: > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_E > nviro > nment/Controller_Storage > and still reproducing the two issues below? > > I was not able to definitively tell from the Launchpad notes. It's > important that both our teams are comparing apples to apples. > > Thanks, > Ghada > > -----Original Message----- > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > Sent: Monday, September 10, 2018 1:50 PM > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > Subject: RE: [ Test ] Sanity results - summary posted > > Hi, > > Such launchpads were updated. > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present > two issues. Michael will upload his ISO, then we will re test witch > each iso in our environment. > > An script is being developed to get the differences between ISOs. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Friday, September 7, 2018 4:43 PM > To: Khalil, Ghada ; Martinez Monroy, Elio > ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Hi Elio/Ada, > Are there any updates from your side on these two Launchpads? > https://bugs.launchpad.net/starlingx/+bug/1790213 > https://bugs.launchpad.net/starlingx/+bug/1790716 > > Michel Thebeau (Wind River) has been trying to reproduce these two > issues (following the starlingx wikis) without success for two days > now. He has been adding his findings to the bugs and communicating with your team. > As a result of his investigation, he will be pushing some small fixes > to stx- tools shortly (some cleanup). > > Please let us know if you need any further help from us. > > Thanks, > Ghada > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Wednesday, September 05, 2018 5:39 PM > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; starlingx- > discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Please see inline. There are notes in all the launchpads as well. > > I have tagged the last bug for the October release. The rest need more > information to determine whether they gate or not: two maybe > procedural and one requires more information. > > -----Original Message----- > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > Sent: Wednesday, September 05, 2018 2:23 PM > To: Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > My opinion below > > -----Original Message----- > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > Sent: Wednesday, September 5, 2018 12:56 PM > To: Cabrales, Ada ; starlingx- > discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Should the bugs coming out of this be tagged/fixed for the October release? > > Related bugs: > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug > is related with 2nd controller provisioning [[GK]] Using the > instructions published on the wiki, our designer was not able to reproduce this issue. > What instructions are the test team using? > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until > other issues are solved, will fail some test cases related to SSH > [[GK]] Requested more information. This cannot be debugged further without this information. > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all > instances need at least one compute for multimode [[GK]] Using the > instructions published on the wiki, our designer was not able to > reproduce this issue. The test team points to internal instructions > which we have no access to. The supported install recipes need to be > on the wiki. I think it is an invalid bug > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since > is related to FM , test cases will fail [[GK]] As Brent pointed out, > this is dependent on the integration of stx-gui which is in progress. > > -----Original Message----- > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > Sent: Wednesday, September 5, 2018 10:50 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hello all, > > As mentioned on the project meeting today, we're posting the > summary of the sanity test runs on the Test wiki [0]. The sanity is > triggered each time an ISO is generated (a daily task). > > Right now we are posting the results manually, and working on a way > for automating it. Logs of the run are not included, if you want to > have them, you can contact Elio to get them sent to you. > > > [0] > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity > _S > ummary > > Regards > Ada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From juan.carlos.alonso at intel.com Tue Sep 11 20:04:32 2018 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 11 Sep 2018 20:04:32 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> Message-ID: <8557B550001AFB46A43A0CCC314BF8514422FE11@fmsmsx101.amr.corp.intel.com> Hi, I also posted a comment on 1790213 with some findings. About the ISO sharing, I don't know if we are still able to continue with it. The installation fail on compute nodes have the same behavior. Regards. Juan Carlos Alonso -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau at windriver.com] Sent: Tuesday, September 11, 2018 2:09 PM To: Khalil, Ghada ; Alonso, Juan Carlos ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [ Test ] Sanity results - summary posted Hi Ghada, I have posted a comment on #1790716 recommending closing that bug, but referring everyone to #1790213. I have not yet received the iso named stx-2018-08-30-97, but the iso stx-2018-08-28-88 presented a broken installer on the controller-1 console: " Error populating transaction after 10 retries: failure: Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm from anaconda: [Errno 256] No more mirrors to try." I think one could refocus on finding out why the installer broke after 2018-08-25-81, before 2018-08-28-88 M On 2018-09-11 09:53 AM, Khalil, Ghada wrote: > Hello Juan, > I read the notes in the Launchpad. > > And, just to confirm, are you following the instructions under: > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_E > nvironment/Controller_Storage and still reproducing the two issues > below? > > I was not able to definitively tell from the Launchpad notes. It's important that both our teams are comparing apples to apples. > > Thanks, > Ghada > > -----Original Message----- > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > Sent: Monday, September 10, 2018 1:50 PM > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > Subject: RE: [ Test ] Sanity results - summary posted > > Hi, > > Such launchpads were updated. > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two issues. Michael will upload his ISO, then we will re test witch each iso in our environment. > > An script is being developed to get the differences between ISOs. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Friday, September 7, 2018 4:43 PM > To: Khalil, Ghada ; Martinez Monroy, Elio > ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Hi Elio/Ada, > Are there any updates from your side on these two Launchpads? > https://bugs.launchpad.net/starlingx/+bug/1790213 > https://bugs.launchpad.net/starlingx/+bug/1790716 > > Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team. > As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup). > > Please let us know if you need any further help from us. > > Thanks, > Ghada > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Wednesday, September 05, 2018 5:39 PM > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Please see inline. There are notes in all the launchpads as well. > > I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. > > -----Original Message----- > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > Sent: Wednesday, September 05, 2018 2:23 PM > To: Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > My opinion below > > -----Original Message----- > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > Sent: Wednesday, September 5, 2018 12:56 PM > To: Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Should the bugs coming out of this be tagged/fixed for the October release? > > Related bugs: > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all > instances need at least one compute for multimode [[GK]] Using the > instructions published on the wiki, our designer was not able to > reproduce this issue. The test team points to internal instructions > which we have no access to. The supported install recipes need to be > on the wiki. I think it is an invalid bug > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. > > -----Original Message----- > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > Sent: Wednesday, September 5, 2018 10:50 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hello all, > > As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). > > Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. > > > [0] > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity > _Summary > > Regards > Ada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ken.Young at windriver.com Tue Sep 11 20:18:36 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Tue, 11 Sep 2018 20:18:36 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted Message-ID: Juan Carlos, I am confused. Why are we looking at the behaviour of ISOs from August? That seems like a waste of time. If I look at the sanity page, ISOs have been produced since then: https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary The latest used there is Sept 6th? I believe that Mitch's ISO is more recent than that; I would have to check. Is there a reason we are not discussing the September 10th build? Does it display the same installer error on the console of controller-1? Certainly, we have not seen that virtually or physically on any system. Regards, Ken Y On 2018-09-11, 4:07 PM, "Alonso, Juan Carlos" wrote: Hi, I also posted a comment on 1790213 with some findings. About the ISO sharing, I don't know if we are still able to continue with it. The installation fail on compute nodes have the same behavior. Regards. Juan Carlos Alonso -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau at windriver.com] Sent: Tuesday, September 11, 2018 2:09 PM To: Khalil, Ghada ; Alonso, Juan Carlos ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [ Test ] Sanity results - summary posted Hi Ghada, I have posted a comment on #1790716 recommending closing that bug, but referring everyone to #1790213. I have not yet received the iso named stx-2018-08-30-97, but the iso stx-2018-08-28-88 presented a broken installer on the controller-1 console: " Error populating transaction after 10 retries: failure: Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm from anaconda: [Errno 256] No more mirrors to try." I think one could refocus on finding out why the installer broke after 2018-08-25-81, before 2018-08-28-88 M On 2018-09-11 09:53 AM, Khalil, Ghada wrote: > Hello Juan, > I read the notes in the Launchpad. > > And, just to confirm, are you following the instructions under: > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_E > nvironment/Controller_Storage and still reproducing the two issues > below? > > I was not able to definitively tell from the Launchpad notes. It's important that both our teams are comparing apples to apples. > > Thanks, > Ghada > > -----Original Message----- > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > Sent: Monday, September 10, 2018 1:50 PM > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > Subject: RE: [ Test ] Sanity results - summary posted > > Hi, > > Such launchpads were updated. > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two issues. Michael will upload his ISO, then we will re test witch each iso in our environment. > > An script is being developed to get the differences between ISOs. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Friday, September 7, 2018 4:43 PM > To: Khalil, Ghada ; Martinez Monroy, Elio > ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Hi Elio/Ada, > Are there any updates from your side on these two Launchpads? > https://bugs.launchpad.net/starlingx/+bug/1790213 > https://bugs.launchpad.net/starlingx/+bug/1790716 > > Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team. > As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup). > > Please let us know if you need any further help from us. > > Thanks, > Ghada > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Wednesday, September 05, 2018 5:39 PM > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Please see inline. There are notes in all the launchpads as well. > > I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. > > -----Original Message----- > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > Sent: Wednesday, September 05, 2018 2:23 PM > To: Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > My opinion below > > -----Original Message----- > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > Sent: Wednesday, September 5, 2018 12:56 PM > To: Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Should the bugs coming out of this be tagged/fixed for the October release? > > Related bugs: > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all > instances need at least one compute for multimode [[GK]] Using the > instructions published on the wiki, our designer was not able to > reproduce this issue. The test team points to internal instructions > which we have no access to. The supported install recipes need to be > on the wiki. I think it is an invalid bug > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. > > -----Original Message----- > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > Sent: Wednesday, September 5, 2018 10:50 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hello all, > > As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). > > Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. > > > [0] > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity > _Summary > > Regards > Ada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From juan.carlos.alonso at intel.com Tue Sep 11 20:33:42 2018 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 11 Sep 2018 20:33:42 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: References: Message-ID: <8557B550001AFB46A43A0CCC314BF8514422FE3B@fmsmsx101.amr.corp.intel.com> Hi Ken, Because the issues started from August's ISOs and followed ISOs have the same issues. We focused to find from what ISO the issues started, we did it. Now we are focusing on confirm if such package is the root cause of issues, if it is then latest ISOs should work well. Regards. Juan Carlos Alonso -----Original Message----- From: Young, Ken [mailto:Ken.Young at windriver.com] Sent: Tuesday, September 11, 2018 3:19 PM To: Alonso, Juan Carlos Cc: Thebeau, Michel ; Khalil, Ghada ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Juan Carlos, I am confused. Why are we looking at the behaviour of ISOs from August? That seems like a waste of time. If I look at the sanity page, ISOs have been produced since then: https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary The latest used there is Sept 6th? I believe that Mitch's ISO is more recent than that; I would have to check. Is there a reason we are not discussing the September 10th build? Does it display the same installer error on the console of controller-1? Certainly, we have not seen that virtually or physically on any system. Regards, Ken Y On 2018-09-11, 4:07 PM, "Alonso, Juan Carlos" wrote: Hi, I also posted a comment on 1790213 with some findings. About the ISO sharing, I don't know if we are still able to continue with it. The installation fail on compute nodes have the same behavior. Regards. Juan Carlos Alonso -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau at windriver.com] Sent: Tuesday, September 11, 2018 2:09 PM To: Khalil, Ghada ; Alonso, Juan Carlos ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [ Test ] Sanity results - summary posted Hi Ghada, I have posted a comment on #1790716 recommending closing that bug, but referring everyone to #1790213. I have not yet received the iso named stx-2018-08-30-97, but the iso stx-2018-08-28-88 presented a broken installer on the controller-1 console: " Error populating transaction after 10 retries: failure: Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm from anaconda: [Errno 256] No more mirrors to try." I think one could refocus on finding out why the installer broke after 2018-08-25-81, before 2018-08-28-88 M On 2018-09-11 09:53 AM, Khalil, Ghada wrote: > Hello Juan, > I read the notes in the Launchpad. > > And, just to confirm, are you following the instructions under: > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_E > nvironment/Controller_Storage and still reproducing the two issues > below? > > I was not able to definitively tell from the Launchpad notes. It's important that both our teams are comparing apples to apples. > > Thanks, > Ghada > > -----Original Message----- > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > Sent: Monday, September 10, 2018 1:50 PM > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > Subject: RE: [ Test ] Sanity results - summary posted > > Hi, > > Such launchpads were updated. > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two issues. Michael will upload his ISO, then we will re test witch each iso in our environment. > > An script is being developed to get the differences between ISOs. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Friday, September 7, 2018 4:43 PM > To: Khalil, Ghada ; Martinez Monroy, Elio > ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Hi Elio/Ada, > Are there any updates from your side on these two Launchpads? > https://bugs.launchpad.net/starlingx/+bug/1790213 > https://bugs.launchpad.net/starlingx/+bug/1790716 > > Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team. > As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup). > > Please let us know if you need any further help from us. > > Thanks, > Ghada > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Wednesday, September 05, 2018 5:39 PM > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Please see inline. There are notes in all the launchpads as well. > > I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. > > -----Original Message----- > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > Sent: Wednesday, September 05, 2018 2:23 PM > To: Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > My opinion below > > -----Original Message----- > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > Sent: Wednesday, September 5, 2018 12:56 PM > To: Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Should the bugs coming out of this be tagged/fixed for the October release? > > Related bugs: > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all > instances need at least one compute for multimode [[GK]] Using the > instructions published on the wiki, our designer was not able to > reproduce this issue. The test team points to internal instructions > which we have no access to. The supported install recipes need to be > on the wiki. I think it is an invalid bug > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. > > -----Original Message----- > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > Sent: Wednesday, September 5, 2018 10:50 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hello all, > > As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). > > Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. > > > [0] > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity > _Summary > > Regards > Ada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Tue Sep 11 23:51:01 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 11 Sep 2018 23:51:01 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B34044A@SHSMSX104.ccr.corp.intel.com> Hi, Jason, Did you use the manifest Shuicheng provided to get the exact commitID in each repo? I am not sure if this is going to make difference, but we were trying to avoid other code changes (in mainline) to impact the build stability. Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Wednesday, September 12, 2018 2:12 AM To: Dean Troyer Cc: Cordoba Malibran, Erich ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io; Liu, ZhipengS ; Khalil, Ghada ; Lin, Shuicheng ; Xie, Cindy Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > -----Original Message----- > From: Dean Troyer > Sent: September 11, 2018 2:07 PM > To: McKenna, Jason > Cc: Cordoba Malibran, Erich ; > Waheed, Numan ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Lin, Shuicheng > ; Xie, Cindy > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > On Tue, Sep 11, 2018 at 12:24 PM, Dean Troyer wrote: > > The f/centos75 branch is only periodically rebased on master, it > > sounds like this is what you need. I will do a test run to see if > > it is clean soon... (at PTG) > > The only conflict is in stx-integ in .zuul.yaml, which I can clean up > easily enough. > > We need to do this before merging back in to master anyway...shall I > go ahead with the rebase? Hi Dean, It doesn't seem like the issue is a rebase. It's that code in some repos (stx-integ, for example) was updated to build against new versions of source rpms, but the .lst files currently (or at least as of when I sync'd) checked in in stx-tools call out old or different versions to be downloaded and put into the build environment. Most of the out-of-sync files can be downloaded manually, but some of them aren't accepting the checked in patches. > > dt > > -- > > Dean Troyer > dtroyer at gmail.com From shuicheng.lin at intel.com Wed Sep 12 00:43:32 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 12 Sep 2018 00:43:32 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> Hi Jason, Here is the dhcp src rpm we are using: [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source dhcp http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5-68.el7.centos.1.src.rpm For centos-release, there are two packages in the mirror lst, 1 src rpm for build, and 1 rpm for the mock environment. And it has the "slightly difference" in the names as you mentioned. Both of them could be found in the centos repo with the exact name. ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source centos-release-7-5.1804.1.el7.centos http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos-release-7-5.1804.1.el7.centos.src.rpm [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url centos-release-7-5.1804.el7.centos.x86_64 http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos-release-7-5.1804.el7.centos.x86_64.rpm If there is still some other rpm missing, you could try to find them from the repo. I have try my best to keep my local mirror the same as the lst. But it is still possible some package missed to be added to the repo lst. Please feel free to notify me or correct the error directly. Thanks. Best Regards Shuicheng -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Wednesday, September 12, 2018 12:21 AM To: Cordoba Malibran, Erich ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io; Liu, ZhipengS ; Khalil, Ghada ; Lin, Shuicheng ; Xie, Cindy Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, With the latest centos75 branch (and the cherry-picks you mentioned) I am unable to produce a build. There seems to be several source rpm files missing from the currently pushed version of the .lst files (or the .lst files pull down the wrong version). Most of the missing files I can download manually, however the checked in patches for dhcp and centos-release packages do not apply against the version of the source RPM which I can manually find on the Internet. For example, the version of centos-release called out in the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the version called out in the checked in code base is the slightly different centos-release-7-5.1804.el7.centos.1.x86_64.rpm, and the patches checked in do not apply against either package. Until the centos75 branch of the lst files pulls down the correct rpms, I will be unable to continue the validation effort. -J > -----Original Message----- > From: Cordoba Malibran, Erich > Sent: September 11, 2018 11:17 AM > To: Waheed, Numan ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Lin, Shuicheng > ; McKenna, Jason > ; Xie, Cindy > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi > > You can add "debug loglevel=8" to the kernel boot option to get a more > detailed output of the crash (if any) > > -Erich > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > Shuicheng saw the symbol table error issue as well but it recovers > > in 8s, he is still working on debugging it. But 601204 is just > > kernel upgrade but not intended to solve this issues. Are you > > running bare metal? I am wondering if this is HW config and driver issue. > > > > Is it possible that you try to deploy it in virtual environment? > > > > Thx. - cindy > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Tuesday, September 11, 2018 9:50 PM > > To: Xie, Cindy ; Rasa, Nimalini > > ; Waheed, Numan > > ; Lin, Shuicheng > > ; Liu, ZhipengS ; > > Khalil, Ghada ; 'starlingx-discus > > s at lists.starlingx.io' > > Subject: RE: CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > We got past the installation device error, but are coming up against > > the symbol table error. Our system hangs after this message. I > > suspect a kernel issue. I see there is an open code review to > > refactor some kernel patches to a rebased kernel > > (https://review.open > > stack.org/#/c/601204/) but I do not know if that is expected to > > resolve the issue > > > > -J > > > > From: Xie, Cindy > > Sent: September 11, 2018 9:32 AM > > To: Rasa, Nimalini ; Waheed, Numan > > n.Waheed at windriver.com>; Lin, Shuicheng ; > > McKenna, Jason ; Liu, ZhipengS > > .liu at intel.com>; Khalil, Ghada ; > > 'starlin gx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > But as Jason reported yesterday, the build cannot be installed with > > error messages: > > > > Installation failed. > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > We cannot debug without more information, the ISO installs in > > Intel’s HW. Thus Shuicheng created a new build and attached a > > manifest in this email thread. Did WindRiver has a chance to create > > a new ISO using today’s manifest file and re-run the test? > > > > Thx. - cindy > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > Sent: Tuesday, September 11, 2018 9:25 PM > > To: Xie, Cindy ; Waheed, Numan > > driver.com>; Lin, Shuicheng ; McKenna, > > Jason ; Liu, ZhipengS > > > ; Khalil, Ghada ; > > 'starlingx-discuss at list s.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > This is on the same build (yesterday’s build). > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > Sent: Tuesday, September 11, 2018 9:22 AM > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; > > Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: CentOS 7.5 upgrade status update > > > > Is this the same issue as yesterday’s build? or this is different > > issue now? > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > Sent: Tuesday, September 11, 2018 9:06 PM > > To: Waheed, Numan ; Lin, Shuicheng > > heng.lin at intel.com>; McKenna, Jason ; > > Liu, ZhipengS ; Khalil, Ghada > > ; > > 'starlingx-discuss at lists.starlingx.io' > uss at lists.starlingx.io>; Xie, Cindy > > Subject: RE: CentOS 7.5 upgrade status update > > > > It is not booting in my case. After the following , it just hangs > > there: > > “Error: no symbol table. > > Press any key to continue…” > > > > -Nimalini > > > > From: Waheed, Numan > > Sent: Tuesday, September 11, 2018 8:50 AM > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, Nimalini > > Subject: RE: CentOS 7.5 upgrade status update > > > > Adding Nimalini > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > Sent: September-11-18 2:17 AM > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, Numan > > Subject: RE: CentOS 7.5 upgrade status update > > > > Hi Jason, > > Just finished deploy image with latest code, I could config > > controller successfully in bare metal environment. > > Manifest is created for you reference. There are two patches I add > > manually: > > https://review.openstack.org/596855           for python-horizon > > from master > > https://review.openstack.org/599892           for build-iso > > > > > > There is an issue found when reboot controller node. > > After the OS selection menu, it will show below error. And it will > > auto continue boot after around 8 seconds. I will check the issue > > later. > > “ > > Error: no symbol table. > > Press any key to continue… > > “ > > > > Best Regards > > Shuicheng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > Sent: Tuesday, September 11, 2018 9:35 AM > > To: McKenna, Jason ; Liu, ZhipengS > > engs.liu at intel.com>; Khalil, Ghada ; > > 'sta rlingx-discuss at lists.starlingx.io' > > > .io>; Xie, Cindy ; Waheed, Numan > > indriver.com> > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > I just tried my last Friday’s image at bare metal machine. There is > > no issue to install controller node. > > Will you help check what cause the install error in your environment? > > > > I am syncing my code to latest to double confirm it. > > > > Best Regards > > Shuicheng > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Tuesday, September 11, 2018 12:13 AM > > To: Liu, ZhipengS ; Lin, Shuicheng > > ; Khalil, Ghada > > ; 'starlin > > gx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy ; Waheed, Numan > > iver.com> > > Subject: RE: CentOS 7.5 upgrade status update > > > > Status update. The build from the centos75 branch does not install > > on our hardware. The error message we are seeing is: > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > -Jason > > > > From: Liu, ZhipengS > > Sent: September 8, 2018 9:56 AM > > To: Lin, Shuicheng ; McKenna, Jason > > ; Khalil, Ghada > > ; 's > > tarlingx-discuss at lists.starlingx.io' > > ; Xie, Cindy > > ; Waheed, Numan > > @windriver.com> > > Subject: RE: CentOS 7.5 upgrade status update > > > > Hi Jason, > > > > I have fixed the issue you mentioned below. > > - Furthermore, the tpm2-tools package was requesting version > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > hacked the spec file for tpm2-tools and rebuilt it to require the > > version mentioned, but there is some rework to be done there. > > [slin14]: I have the same issue also. Let’s further check it to find > > the root cause. I use rebuild tpm2-tools/tss2 to workaround it > > without any code. > > > > https://review.openstack.org/#/c/600920/ > > > > Thanks! > > Zhipeng > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > Sent: 2018年9月8日 21:14 > > To: McKenna, Jason ; Khalil, Ghada > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > ; Xie, Cindy > > ; Waheed, Numan > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > I have fixed the error in the openstack-aodh. Patch is updated: > > https://review.openstack.org/#/c/598388/ > > > > It is due to my local version is not the latest one. > > Sorry for the trouble caused, and thanks for your test. > > > > Best Regards > > Shuicheng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > Sent: Saturday, September 8, 2018 9:23 AM > > To: McKenna, Jason ; Khalil, Ghada > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > ; Xie, Cindy > > ; Waheed, Numan > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Thanks very much for such detail feedback. > > I added some comments inline, and will check the issue in my > > environment also. > > Feel free to submit patch if you have to fix them. J > > > > > > Best Regards > > Shuicheng > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Saturday, September 8, 2018 3:47 AM > > To: McKenna, Jason ; Khalil, Ghada > > a.Khalil at windriver.com>; Lin, Shuicheng ; > > 's tarlingx-discuss at lists.starlingx.io' > > ; Xie, Cindy > > ; Waheed, Numan > > @windriver.com> > > Subject: RE: CentOS 7.5 upgrade status update > > > > Hi Shuicheng, > > > > I’ve completed a build of the code. We have not yet run run-time > > tests, but here are the build-time issues I encountered: > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > longer available for download, and the download_mirrors.sh step fails. > > It appears than CentOS has updated to lighttpd-1.4.50. I manually > > built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > - Even though the .lst file specifies lighttpd-1.4.49, the > > code still references 1.4.45 > > - At build-pkgs time (the build-srpms step), the meta-patches > > to openstack-aodh do not apply, as two of them are malformed. https: > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > expirer-cron-script.patch -- In the new version, on line 190, the > > patch states that the old code covered 6 lines, and the new code > > covers 9 lines (-283,6 +286,9). But there are only two lines > > inserted by the patch. There is also a new blank line in the patch > > at line 194. Removing this blank line and editing the hunk > > description to only insert 2 lines resolves the issue for this hunk > > (there are other similar issues in this patch, and in 0001-meta- > > modify-aodh-api.patch) > > [slin14]: Let me double check it. > > - At binary build time, I had build failures on python-django- > > horizon and some magnum packages. I had to pull in > > https://review.op > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > centos75 branch of stx-upstream) to get past this. > > [slin14]: It is due to I have not synced latest master code, so I > > don’t have this issue. I used last week’s master code. > > - After building all packages, I attempted to build the ISO. > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should > > be added to the .lst files. > > [slin14]: This package is already in the lst. > > - Furthermore, the tpm2-tools package was requesting version > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > hacked the spec file for tpm2-tools and rebuilt it to require the > > version mentioned, but there is some rework to be done there. > > [slin14]: I have the same issue also. Let’s further check it to find > > the root cause. I use rebuild tpm2-tools/tss2 to workaround it > > without any code. > > > > After these changes, I was able to produce a .iso > > > > -Jason > > > > From: McKenna, Jason > > Sent: September 7, 2018 10:08 AM > > To: Khalil, Ghada ; Lin, Shuicheng > > ; 'starlingx-discuss at lists.starlingx.io' > > ; Xie, Cindy > > ; Waheed, Numan > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Shuicheng, > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > been changed from 1.4.45 to 1.4.49. The > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > locate an archived version of the 1.4.49 .src rpm. > > > > -Jason > > > > From: Khalil, Ghada > > Sent: September 7, 2018 9:36 AM > > To: Lin, Shuicheng ; > > 'starlingx-discuss at list s.starlingx.io' > > ; Xie, Cindy > indy.xie at intel.com>; Waheed, Numan > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be > > priming this activity. He’ll share the results with the team > > sometime next week. > > > > Regards, > > Ghada > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > Sent: Friday, September 07, 2018 1:32 AM > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > Cindy > > Subject: CentOS 7.5 upgrade status update > > > > Hi all, > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please go > > ahead to have a try and verify it. > > I expect there should be some issue due to we just did limited > > deploy test yet. > > > > Here is the detail status update of this week. > > For the total 44 srpm we plan to upgrade: > > 38 already merged in feature branch. > > 3 kept as original version. Anaconda upgrade is not needed. python- > > os-vif has higher version than 7.5. python-eventlet kept due to new > > src rpm itself have known issue. > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > 1 under debug. Lighttpd. > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > Here is the build instruction: > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > upstream/stx-root. > > Cherry-pick below un-merged patch: > > For puppet-haproxy: > > https://review.openstack.org/600369 > > https://review.openstack.org/600359 > > For openstack-aodh: > > https://review.openstack.org/598388 > > https://review.openstack.org/600591 > > For build-iso: > > https://review.openstack.org/599892 > > For build-pkgs: > > https://review.openstack.org/599901 > > https://review.openstack.org/600639 > > > > 2. Run mirror script to get the upgraded src rpm and related > > rpm. > > 3. Try to build packages and ISO. > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > https://storyboard.openstack.org/#!/story/2003389 > > > > Feel free to contact me if you have trouble on it. > > > > Best Regards > > Shuicheng > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Wed Sep 12 01:50:31 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 12 Sep 2018 01:50:31 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <8557B550001AFB46A43A0CCC314BF8514422FE3B@fmsmsx101.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF8514422FE3B@fmsmsx101.amr.corp.intel.com> Message-ID: <8A52A9F8-C353-401E-B9C2-061C51618346@intel.com> I have narrowed down a little bit the issue, these are my findings. - I compared the bootimage_michel.iso with the stx-2018-09-11-111.iso, which is today's ISO. - The are not significant package differences between them, minor versions has changed in some packages. - The issue is that once the kernel has been loaded through PXE, anaconda is unable to find python2-qpid package. Not sure if this is the first package that is requested. - From the anaconda shell I can see the http://pxecontroller/ serving the files and the repodata seems to be updated there. I installed yum manually and I was able to install python2-qpid package, (and any other available). - The content of the pxe-network-installer package is not the same, WR squashfs.img file has the kernel 3.10.0-693.2.2 but ours has 3.10.0- 862.6.3. We regenerate those files when the kernel was upgraded. (maybe this matches with the date where the issue started to arise..) So, my guess now is that the problem could be caused by the pxe-network-installer package. We create those files with the update- network-installer script. That's the same used in WR to generate these files? I'll keep diging in the generation of these files to see if there is any problem. -Erich On 9/11/18, 3:34 PM, "Alonso, Juan Carlos" wrote: Hi Ken, Because the issues started from August's ISOs and followed ISOs have the same issues. We focused to find from what ISO the issues started, we did it. Now we are focusing on confirm if such package is the root cause of issues, if it is then latest ISOs should work well. Regards. Juan Carlos Alonso -----Original Message----- From: Young, Ken [mailto:Ken.Young at windriver.com] Sent: Tuesday, September 11, 2018 3:19 PM To: Alonso, Juan Carlos Cc: Thebeau, Michel ; Khalil, Ghada ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Juan Carlos, I am confused. Why are we looking at the behaviour of ISOs from August? That seems like a waste of time. If I look at the sanity page, ISOs have been produced since then: https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary The latest used there is Sept 6th? I believe that Mitch's ISO is more recent than that; I would have to check. Is there a reason we are not discussing the September 10th build? Does it display the same installer error on the console of controller-1? Certainly, we have not seen that virtually or physically on any system. Regards, Ken Y On 2018-09-11, 4:07 PM, "Alonso, Juan Carlos" wrote: Hi, I also posted a comment on 1790213 with some findings. About the ISO sharing, I don't know if we are still able to continue with it. The installation fail on compute nodes have the same behavior. Regards. Juan Carlos Alonso -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau at windriver.com] Sent: Tuesday, September 11, 2018 2:09 PM To: Khalil, Ghada ; Alonso, Juan Carlos ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [ Test ] Sanity results - summary posted Hi Ghada, I have posted a comment on #1790716 recommending closing that bug, but referring everyone to #1790213. I have not yet received the iso named stx-2018-08-30-97, but the iso stx-2018-08-28-88 presented a broken installer on the controller-1 console: " Error populating transaction after 10 retries: failure: Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm from anaconda: [Errno 256] No more mirrors to try." I think one could refocus on finding out why the installer broke after 2018-08-25-81, before 2018-08-28-88 M On 2018-09-11 09:53 AM, Khalil, Ghada wrote: > Hello Juan, > I read the notes in the Launchpad. > > And, just to confirm, are you following the instructions under: > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_E > nvironment/Controller_Storage and still reproducing the two issues > below? > > I was not able to definitively tell from the Launchpad notes. It's important that both our teams are comparing apples to apples. > > Thanks, > Ghada > > -----Original Message----- > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > Sent: Monday, September 10, 2018 1:50 PM > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > Subject: RE: [ Test ] Sanity results - summary posted > > Hi, > > Such launchpads were updated. > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two issues. Michael will upload his ISO, then we will re test witch each iso in our environment. > > An script is being developed to get the differences between ISOs. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Friday, September 7, 2018 4:43 PM > To: Khalil, Ghada ; Martinez Monroy, Elio > ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Hi Elio/Ada, > Are there any updates from your side on these two Launchpads? > https://bugs.launchpad.net/starlingx/+bug/1790213 > https://bugs.launchpad.net/starlingx/+bug/1790716 > > Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team. > As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup). > > Please let us know if you need any further help from us. > > Thanks, > Ghada > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Wednesday, September 05, 2018 5:39 PM > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Please see inline. There are notes in all the launchpads as well. > > I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. > > -----Original Message----- > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > Sent: Wednesday, September 05, 2018 2:23 PM > To: Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > My opinion below > > -----Original Message----- > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > Sent: Wednesday, September 5, 2018 12:56 PM > To: Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Should the bugs coming out of this be tagged/fixed for the October release? > > Related bugs: > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all > instances need at least one compute for multimode [[GK]] Using the > instructions published on the wiki, our designer was not able to > reproduce this issue. The test team points to internal instructions > which we have no access to. The supported install recipes need to be > on the wiki. I think it is an invalid bug > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. > > -----Original Message----- > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > Sent: Wednesday, September 5, 2018 10:50 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hello all, > > As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). > > Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. > > > [0] > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity > _Summary > > Regards > Ada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From wei.w.hu at intel.com Wed Sep 12 08:00:20 2018 From: wei.w.hu at intel.com (Hu, Wei W) Date: Wed, 12 Sep 2018 08:00:20 +0000 Subject: [Starlingx-discuss] StarlingX Release Sub-Projects In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA403D2D@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB575A46@fmsmsx115.amr.corp.intel.com> Message-ID: hi, Arce, I checked the link and found that no content there. Is there any process there? We have a PRC partner that would like to discuss with us for use case for StarlingX. -Wei Hu -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Wednesday, August 08, 2018 11:09 PM To: Jones, Bruce E ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] StarlingX Release Sub-Projects > I don’t think we need a sub-project called Use Cases but I'd sure like > to see a document on that topic. I think it makes sense to add this > to the work list for the Documentation team. In fact, I've already > done so. :) > > https://storyboard.openstack.org/#!/story/2003331 Thanks Bruce: StarlingX Use Cases [0] Initial idea behind this page is to create proposal drafts for use cases under StarlingX and once there is a proof of concept it can be taken to OpenStack Edge Computing Group [1] [0] https://wiki.openstack.org/wiki/StarlingX/Use_Cases [1] https://wiki.openstack.org/wiki/Edge_Computing_Group _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Wed Sep 12 13:08:58 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 12 Sep 2018 13:08:58 +0000 Subject: [Starlingx-discuss] [Build] Feedback on stxb demo In-Reply-To: References: , <12f082a2-f28d-ad8e-6fa2-336c0d945513@linux.intel.com> <6594B51DBE477C48AAE23675314E6C465993F282@fmsmsx107.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA451D65@ALA-MBD.corp.ad.wrs.com> Hello all, +1 for Jason's suggestion ...we cannot have the community transition to this tool as the official way of building at this time. We need to all agree as a community when to trial new tools to get feedback and when to make them official. We are driving hard to achieve code freeze for the October Release. We need to ensure everyone is building the same official way to avoid inconsistent results. As a side note, based on the review with the Build Project Lead (Cesar), there were no build improvements planned for the October release except for https://storyboard.openstack.org/#!/story/2002835 As the StarlingX release prime, I have tagged the new story for the March release (stx.2019.03). Please plan accordingly. Code submissions can still go in master, but cannot alter the documented build process and tools currently used. This story should not be considered complete until there is agreement to move the community to it and update the official documentation at some point after the October release. Regards, Ghada -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Tuesday, September 11, 2018 12:32 PM To: Arevalo, Mario Alfredo C; Saul Wold; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] [Build] Feedback on stxb demo Hi Mario, > -----Original Message----- > From: Arevalo, Mario Alfredo C > Sent: September 10, 2018 4:57 PM > To: Saul Wold ; McKenna, Jason > ; 'starlingx-discuss at lists.starlingx.io' > > Subject: RE: [Starlingx-discuss] [Build] Feedback on stxb demo > > Hi folks, > > I have been seen excellent ideas that we can to add to the tool, > however I think we are walking a little out of the first scope, what > do you think if we include this as first version a we can post our ideas in the storyboard?: I agree that we can put it out as a first preview version, however I would have strong reservations about changing the wiki documentation to suggest that this is "the official way to build" at this time. > > https://storyboard.openstack.org/#!/story/2003712 +1 to the consolidation of docker images, and it sounds like that part's done. Good job! > > Then we can track all ideas suggested :) Yeah, I think we should have ideally had a discussion about use cases and requirements before the tool was designed. In particular, I do not think the tool (as demoed) is usable by developers. I understand that your requirements are to come up with an end-to-end tool that would produce a build with as few commands as possible, but the current architecture of having a second repo inside the docker container is a deal-breaker for any developer trying to work on the code. I'm all for designing and using better tools, but we shouldn't make this the official way of doing things if it places a new non-trivial burden on the devs. There might be some wiggle room on my suggestion to support a native (rather than containerized) build. As a tangential note, are you able to confirm that the use of a local mirror of packages rather than a download into the container from the Internet is working? We don't want to introduce a change that would unnecessarily add hours to a build. > > Best regards. > Mario. > ________________________________________ > From: Saul Wold [sgw at linux.intel.com] > Sent: Monday, September 10, 2018 10:33 AM > To: McKenna, Jason; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] [Build] Feedback on stxb demo > > Sorry I missed this today, I am in Denver. > > Can you point me at the repo you are working in please? > > On 09/10/2018 09:02 AM, McKenna, Jason wrote: > > Hi build team, > > > > Many thanks for the demo today, I think we're on the right track. > > As promised, here are a few feedback points on the demo, from the > > perspective of a developer: > > > > -I really like how the creation of the docker image is streamlined. > > > > -The system as currently demo'd as two copies of the repos. One in > > /(developers_path)/, and a second in > > /(developers_path)/stx- > tools/(docker_image_root_dir)/localdisk/designer/builder/starlingx/. > > There should only one repo downloaded. > > > > oAs a related point, a developer working on changes to a file would > > expect to make their changes to the repo in /(developers_path)/, > > rather than to the version in the docker image's filesystem. If I > > edited a puppet manifest (for example) > > /(developers_path)/cgcs-root/stx/stx-config/.../ then I would expect > > the build command to detect and use my changes if I do a build. > > > > -I'm a bit confused on the syntax regarding specifying and using > > localized mirrors, specifically with the -n and -p options. Would > > you provide examples of what commands I'd execute for use cases 1 > > and 2 below? I'm pretty sure these usages are supported, but am just > > seeking clarification. > > > > -Very happy do see it down to 1 docker image, rather than 2 J > > > > -Native build - Being able to build in a docker image is great, but > > the would ideally be an option to perform a native build, rather > > than have to use a container > > > > -Minor nit - logs should be in a user directory (like > > $MY_REPO_ROOT_DIR/logs/) rather than in /var/log, as a > > non-privileged user wouldn't be able to log to /var/log. > > > > -Question - what privileges are required to create the docker image? > > Does the script assume the user has sudo privileges? > > > > -I'm unclear on what would happen with use cases 3-5 below. Have > > these types of uses been considered yet? > > > Jason, > > Thanks for this feedback and the use case suggestions below, see > additional comments. > > > Thanks again for the demo, > > > > -Jason > > > > Use Case 1: > > > > I am an organization with a site who is working > > with StarlingX. I want to provide a local mirror for my employees > > to use so they don't have to download all artifacts from the > > external internet every time. I want to create an automated job > > which I will run daily to download all artifacts from the Internet > > (if they do not already exist) and place them in directory /export/mirrors/starlingx. > > Assume the user running the automated job has permissions to write > > to /export/mirrors/starlingx > > > Based on your usage of /export and /import below, /export is on a > server machine and /import is on the local developer build machine, > just for clarification. > > Also, this job would run native on the host Linux OS not containerized? > > > > Use Case 2: > > > > I am a developer within an organization which has a > > local mirror of artifacts available in /import/mirrors/starlingx. I > > want to build a StarlingX ISO without downloading rpms or src.rpms > > from the external internet. > > > To further clarify this one, the remote mirror could contain all > binary rpms along with their cooresponding src rpm, such that if no > changes all the building of an ISO would be done from the mirror rpms, > no actual local rpm build required unless it changes (use case 4/5 below). > > > Use Case 3A: > > > > After doing a build, I just performed a repo sync, > > and the .lst files were not updated. If I perform another build of > > the ISO, will the system attempt to redownload external artifacts, > > even though nothing has changed? > > > > Use Case 3B: > > > > After doing a build, I just performed a repo sync, > > and noticed that the .lst files have been updated. If I perform > > another build of the ISO, will the stale mirror content be detected > > and the new additions downloaded (while not re-downloading anything > > which has not changed)? > > > > Use Case 4: > > > > I have manually made a change to a puppet manifest > > in sysinv (stx-config git) but want to test before I commit anything. > > How can I build a new ISO with my changes incorporated? > > > I would say not just puppet manifest, but any change to files in the repos. > > > Use Case 5: > > > > I want to test StarlingX with my own additional > > program > > (foobar.x86_64.rpm) on the ISO. How would I perform a build with > > this file added? > > > I look forward to seeing the demo also. > > Sau! > > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Wed Sep 12 13:49:24 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 12 Sep 2018 13:49:24 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack Distro meeting, 9/12 notes Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B3419D1@SHSMSX104.ccr.corp.intel.com> Agenda and notes for 9/12 meetings: 1. AR Reviews (Cindy) - AR: Saul to define a more realistic goal for # of patch reductions (10%, 50% & 90% today) - let's discuss this during patch analysis. update from Saul: 10% by end of 2018, we may exceed that. Stretch goal 30% given we find solution for init/config. Saul: kernel patches review with WR continue but may not be the best component to do upstream. - AR: Shuicheng to scope what is the kernel drivers needs to be upgraded (push it to Mar's release) file a storyboard already, will be after 9/26 code freeze date. - AR: Elio to take the question (about test on bare-metal) to Ada and Ghada take this into test sub-project meeting for tracking. [close in this track and Ada is tracking] - AR: Elio to send out the test report to the mailing list for the ISO built last Friday. [DONE] - AR: Vivian to send your quesitons and ask help to StarlingX mailing list. [DONE] 2. non-OpenStack patch analysis status (Saul) Saul: system init & config patch analysis, Zhipeng Liu from SH team is working on this. 3. CentOS 7.5 upgrade & test status (Shuicheng, Elio, Ghada/Jason) - Shuicheng status: finished sRPM upgrade; upgraded all ~260 RPMs to latest version. 2nd test ISO to GDC for testing last Friday; build instructions given to WR.  Kernel upgraded to the version in 7.5, patch pending review. most of upgrade work is done. Focusing on internal issue reported from WR and GDC, will fix it as soon as the report defects. - GDC test report: bug 1790213 share w/ mainline; other test cases passed: 22/25 passed.  - WR: Jason has some issues on creating ISO. WR is using bare-metal for testing (not virtualize). Inconsistencies btw mirrors and what's required as part of build.  Ken will have Jason to provide more details about failures from Jason's side;  Progress on the ISO made last week: 1st controller node can be installed. 2nd controller failed, same issue as 1790213 (with last Friday's build). Correction from Numan: not able to config the 1st controller. Numan to send out the test report for this ISO build by Jason last weekend. - Tomorrow: getting Martin's results/report; Jason's build debug info. 4. Libvirt/qemu upgrade status (Ghada/Jim) Jim is back from vacation. will follow-up by email about 3 storyboards readiness before 9/26. 5. Ceph upgrade status (Vivian) Vivian is on travel and Dehao from storage team is debugging Ceph upgrade issues, still encounter Python2 dependencies.  6. Open topics (Brent, Saul, Ghada)     From mario.alfredo.c.arevalo at intel.com Wed Sep 12 13:57:17 2018 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Wed, 12 Sep 2018 13:57:17 +0000 Subject: [Starlingx-discuss] [Build] Feedback on stxb demo In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA451D65@ALA-MBD.corp.ad.wrs.com> References: , <12f082a2-f28d-ad8e-6fa2-336c0d945513@linux.intel.com> <6594B51DBE477C48AAE23675314E6C465993F282@fmsmsx107.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA451D65@ALA-MBD.corp.ad.wrs.com> Message-ID: <1536760633.18798.5.camel@intel.com> On Wed, 2018-09-12 at 13:08 +0000, Khalil, Ghada wrote: Hi Folks, > Hello all, > +1 for Jason's suggestion ...we cannot have the community transition > to this tool as the official way of building at this time. We need to > all agree as a community when to trial new tools to get feedback and > when to make them official.  If you take a look to the tool's PRs, the first objective is not to do a transition for the moment, basically the ISO process involves a series of steps that might be painful for new users, and we have noticed that in the mailing list. For us, StarlingX team, those steps are easy because we deal with them every day, but we need to think of those who are not interested in become a developer for the moment and just want to make an ISO image, that is the first use case for the stxb tool. The current building process will continue working in the same way, stxb tool just automates those steps. The biggest change in the stxb tool development and the building tools core is the unification of dockerfiles, however it does not involve huge changes in documentation and it is open to feedback. > > We are driving hard to achieve code freeze for the October Release. > We need to ensure everyone is building the same official way to avoid > inconsistent results. Completely agree :) > As a side note, based on the review with the Build Project Lead > (Cesar), there were no build improvements planned for the October > release except for https://storyboard.openstack.org/#!/story/2002835 > > As the StarlingX release prime, I have tagged the new story for the > March release (stx.2019.03). Please plan accordingly. Code > submissions can still go in master, but cannot alter the documented > build process and tools currently used. This story should not be > considered complete until there is agreement to move the community to > it and update the official documentation at some point after the > October release. Best Regards. Mario. > > Regards, > Ghada > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com]  > Sent: Tuesday, September 11, 2018 12:32 PM > To: Arevalo, Mario Alfredo C; Saul Wold; 'starlingx-discuss at lists.sta > rlingx.io' > Subject: Re: [Starlingx-discuss] [Build] Feedback on stxb demo > > Hi Mario, > > > > > -----Original Message----- > > From: Arevalo, Mario Alfredo C > > Sent: September 10, 2018 4:57 PM > > To: Saul Wold ; McKenna, Jason  > > ; 'starlingx-discuss at lists.starlingx.i > > o' > > > > Subject: RE: [Starlingx-discuss] [Build] Feedback on stxb demo > > > > Hi folks, > > > > I have been seen excellent ideas that we can to add to the tool,  > > however I think we are walking a little out of the first scope, > > what  > > do you think if we include this as first version a we can post our > > ideas in the storyboard?: > I agree that we can put it out as a first preview version, however I > would have strong reservations about changing the wiki documentation > to suggest that this is "the official way to build" at this time. > > > > > > > https://storyboard.openstack.org/#!/story/2003712 > +1 to the consolidation of docker images, and it sounds like that > part's done.  Good job! > > > > > > > Then we can track all ideas suggested :) > Yeah, I think we should have ideally had a discussion about use cases > and requirements before the tool was designed.  In particular, I do > not think the tool (as demoed) is usable by developers.  I understand > that your requirements are to come up with an end-to-end tool that > would produce a build with as few commands as possible, but the > current architecture of having a second repo inside the docker > container is a deal-breaker for any developer trying to work on the > code.  I'm all for designing and using better tools, but we shouldn't > make this the official way of doing things if it places a new non- > trivial burden on the devs.  There might be some wiggle room on my > suggestion to support a native (rather than containerized) build. > > As a tangential note, are you able to confirm that the use of a local > mirror of packages rather than a download into the container from the > Internet is working?  We don't want to introduce a change that would > unnecessarily add hours to a build. > > > > > > > Best regards. > > Mario. > > ________________________________________ > > From: Saul Wold [sgw at linux.intel.com] > > Sent: Monday, September 10, 2018 10:33 AM > > To: McKenna, Jason; 'starlingx-discuss at lists.starlingx.io' > > Subject: Re: [Starlingx-discuss] [Build] Feedback on stxb demo > > > > Sorry I missed this today, I am in Denver. > > > > Can you point me at the repo you are working in please? > > > > On 09/10/2018 09:02 AM, McKenna, Jason wrote: > > > > > > Hi build team, > > > > > > Many thanks for the demo today, I think we're on the right > > > track.   > > > As promised, here are a few feedback points on the demo, from > > > the  > > > perspective of a developer: > > > > > > -I really like how the creation of the docker image is > > > streamlined. > > > > > > -The system as currently demo'd as two copies of the repos.  One > > > in  > > > /(developers_path)/, and a second in > > > /(developers_path)/stx- > > tools/(docker_image_root_dir)/localdisk/designer/builder/starlingx/ > > . > > > > > > There should only one repo downloaded. > > > > > > oAs a related point, a developer working on changes to a file > > > would  > > > expect to make their changes to the repo in /(developers_path)/,  > > > rather than to the version in the docker image's filesystem.  If > > > I  > > > edited a puppet manifest (for example)  > > > /(developers_path)/cgcs-root/stx/stx-config/.../ then I would > > > expect  > > > the build command to detect and use my changes if I do a build. > > > > > > -I'm a bit confused on the syntax regarding specifying and using  > > > localized mirrors, specifically with the -n and -p > > > options.  Would  > > > you provide examples of what commands I'd execute for use cases > > > 1  > > > and 2 below? I'm pretty sure these usages are supported, but am > > > just  > > > seeking clarification. > > > > > > -Very happy do see it down to 1 docker image, rather than 2 J > > > > > > -Native build - Being able to build in a docker image is great, > > > but  > > > the would ideally be an option to perform a native build, rather  > > > than have to use a container > > > > > > -Minor nit - logs should be in a user directory (like > > > $MY_REPO_ROOT_DIR/logs/) rather than in /var/log, as a  > > > non-privileged user wouldn't be able to log to /var/log. > > > > > > -Question - what privileges are required to create the docker > > > image? > > > Does the script assume the user has sudo privileges? > > > > > > -I'm unclear on what would happen with use cases 3-5 > > > below.  Have  > > > these types of uses been considered yet? > > > > > Jason, > > > > Thanks for this feedback and the use case suggestions below, see  > > additional comments. > > > > > > > > Thanks again for the demo, > > > > > > -Jason > > > > > > Use Case 1: > > > > > >                  I am an organization with a site who is working  > > > with StarlingX.  I want to provide a local mirror for my > > > employees  > > > to use so they don't have to download all artifacts from the  > > > external internet every time. I want to create an automated job  > > > which I will run daily to download all artifacts from the > > > Internet  > > > (if they do not already exist) and place them in directory > > > /export/mirrors/starlingx. > > > Assume the user running the automated job has permissions to > > > write  > > > to /export/mirrors/starlingx > > > > > Based on your usage of /export and /import below, /export is on a  > > server machine and /import is on the local developer build > > machine,  > > just for clarification. > > > > Also, this job would run native on the host Linux OS not > > containerized? > > > > > > > > > > Use Case 2: > > > > > >                  I am a developer within an organization which > > > has a  > > > local mirror of artifacts available in > > > /import/mirrors/starlingx.  I  > > > want to build a StarlingX ISO without downloading rpms or > > > src.rpms  > > > from the external internet. > > > > > To further clarify this one, the remote mirror could contain all  > > binary rpms along with their cooresponding src rpm, such that if > > no  > > changes all the building of an ISO would be done from the mirror > > rpms,  > > no actual local rpm build required unless it changes (use case 4/5 > > below). > > > > > > > > Use Case 3A: > > > > > >                  After doing a build, I just performed a repo > > > sync,  > > > and the .lst files were not updated.  If I perform another build > > > of  > > > the ISO, will the system attempt to redownload external > > > artifacts,  > > > even though nothing has changed? > > > > > > Use Case 3B: > > > > > >                  After doing a build, I just performed a repo > > > sync,  > > > and noticed that the .lst files have been updated.  If I perform  > > > another build of the ISO, will the stale mirror content be > > > detected  > > > and the new additions downloaded (while not re-downloading > > > anything  > > > which has not changed)? > > > > > > Use Case 4: > > > > > >                  I have manually made a change to a puppet > > > manifest  > > > in sysinv (stx-config git) but want to test before I commit > > > anything. > > > How can I build a new ISO with my changes incorporated? > > > > > I would say not just puppet manifest, but any change to files in > > the repos. > > > > > > > > Use Case 5: > > > > > >                  I want to test StarlingX with my own additional  > > > program > > > (foobar.x86_64.rpm) on the ISO.  How would I perform a build > > > with  > > > this file added? > > > > > I look forward to seeing the demo also. > > > > Sau! > > > > > > > > > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > > uss > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Wed Sep 12 14:04:35 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 12 Sep 2018 14:04:35 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <8A52A9F8-C353-401E-B9C2-061C51618346@intel.com> References: <8557B550001AFB46A43A0CCC314BF8514422FE3B@fmsmsx101.amr.corp.intel.com> <8A52A9F8-C353-401E-B9C2-061C51618346@intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3A890B@ALA-MBD.corp.ad.wrs.com> I'm not familiar with the "update-network-installer" script. I assume it's an Intel creation? We hand-manage updates to the installer images, with steps described in stx-metal/installer/initrd/README, updating the images only as needed. The kickstarts provide "repo" directives to Anaconda to point it at the repos under /www/ on the controller, with the base load being in /www/pages/feed/rel-XXXX. Anaconda should be able to install everything from there. -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, September 11, 2018 9:51 PM To: Alonso, Juan Carlos; Young, Ken Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted I have narrowed down a little bit the issue, these are my findings. - I compared the bootimage_michel.iso with the stx-2018-09-11-111.iso, which is today's ISO. - The are not significant package differences between them, minor versions has changed in some packages. - The issue is that once the kernel has been loaded through PXE, anaconda is unable to find python2-qpid package. Not sure if this is the first package that is requested. - From the anaconda shell I can see the http://pxecontroller/ serving the files and the repodata seems to be updated there. I installed yum manually and I was able to install python2-qpid package, (and any other available). - The content of the pxe-network-installer package is not the same, WR squashfs.img file has the kernel 3.10.0-693.2.2 but ours has 3.10.0- 862.6.3. We regenerate those files when the kernel was upgraded. (maybe this matches with the date where the issue started to arise..) So, my guess now is that the problem could be caused by the pxe-network-installer package. We create those files with the update- network-installer script. That's the same used in WR to generate these files? I'll keep diging in the generation of these files to see if there is any problem. -Erich On 9/11/18, 3:34 PM, "Alonso, Juan Carlos" wrote: Hi Ken, Because the issues started from August's ISOs and followed ISOs have the same issues. We focused to find from what ISO the issues started, we did it. Now we are focusing on confirm if such package is the root cause of issues, if it is then latest ISOs should work well. Regards. Juan Carlos Alonso -----Original Message----- From: Young, Ken [mailto:Ken.Young at windriver.com] Sent: Tuesday, September 11, 2018 3:19 PM To: Alonso, Juan Carlos Cc: Thebeau, Michel ; Khalil, Ghada ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Juan Carlos, I am confused. Why are we looking at the behaviour of ISOs from August? That seems like a waste of time. If I look at the sanity page, ISOs have been produced since then: https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary The latest used there is Sept 6th? I believe that Mitch's ISO is more recent than that; I would have to check. Is there a reason we are not discussing the September 10th build? Does it display the same installer error on the console of controller-1? Certainly, we have not seen that virtually or physically on any system. Regards, Ken Y On 2018-09-11, 4:07 PM, "Alonso, Juan Carlos" wrote: Hi, I also posted a comment on 1790213 with some findings. About the ISO sharing, I don't know if we are still able to continue with it. The installation fail on compute nodes have the same behavior. Regards. Juan Carlos Alonso -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau at windriver.com] Sent: Tuesday, September 11, 2018 2:09 PM To: Khalil, Ghada ; Alonso, Juan Carlos ; Martinez Monroy, Elio ; Jones, Bruce E ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [ Test ] Sanity results - summary posted Hi Ghada, I have posted a comment on #1790716 recommending closing that bug, but referring everyone to #1790213. I have not yet received the iso named stx-2018-08-30-97, but the iso stx-2018-08-28-88 presented a broken installer on the controller-1 console: " Error populating transaction after 10 retries: failure: Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm from anaconda: [Errno 256] No more mirrors to try." I think one could refocus on finding out why the installer broke after 2018-08-25-81, before 2018-08-28-88 M On 2018-09-11 09:53 AM, Khalil, Ghada wrote: > Hello Juan, > I read the notes in the Launchpad. > > And, just to confirm, are you following the instructions under: > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_E > nvironment/Controller_Storage and still reproducing the two issues > below? > > I was not able to definitively tell from the Launchpad notes. It's important that both our teams are comparing apples to apples. > > Thanks, > Ghada > > -----Original Message----- > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > Sent: Monday, September 10, 2018 1:50 PM > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > Subject: RE: [ Test ] Sanity results - summary posted > > Hi, > > Such launchpads were updated. > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two issues. Michael will upload his ISO, then we will re test witch each iso in our environment. > > An script is being developed to get the differences between ISOs. > > Regards. > Juan Carlos Alonso > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Friday, September 7, 2018 4:43 PM > To: Khalil, Ghada ; Martinez Monroy, Elio > ; Jones, Bruce E > ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Hi Elio/Ada, > Are there any updates from your side on these two Launchpads? > https://bugs.launchpad.net/starlingx/+bug/1790213 > https://bugs.launchpad.net/starlingx/+bug/1790716 > > Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team. > As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup). > > Please let us know if you need any further help from us. > > Thanks, > Ghada > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Wednesday, September 05, 2018 5:39 PM > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Please see inline. There are notes in all the launchpads as well. > > I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information. > > -----Original Message----- > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > Sent: Wednesday, September 05, 2018 2:23 PM > To: Jones, Bruce E; Cabrales, Ada; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > My opinion below > > -----Original Message----- > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > Sent: Wednesday, September 5, 2018 12:56 PM > To: Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Should the bugs coming out of this be tagged/fixed for the October release? > > Related bugs: > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using? > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information. > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all > instances need at least one compute for multimode [[GK]] Using the > instructions published on the wiki, our designer was not able to > reproduce this issue. The test team points to internal instructions > which we have no access to. The supported install recipes need to be > on the wiki. I think it is an invalid bug > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress. > > -----Original Message----- > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > Sent: Wednesday, September 5, 2018 10:50 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Hello all, > > As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task). > > Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you. > > > [0] > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity > _Summary > > Regards > Ada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Wed Sep 12 14:27:50 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 12 Sep 2018 14:27:50 +0000 Subject: [Starlingx-discuss] Meeting nodes from the project team call Sep 12 2018 Message-ID: <9A85D2917C58154C960D95352B22818BAB58CE6E@fmsmsx115.amr.corp.intel.com> Agenda and Notes of the meeting of September 12 Let's keep this in a 30 minute call o Main line bugs under active debug that are potential release blockers. These look to be the same defect right now. Further debug needed to root cause. * https://bugs.launchpad.net/starlingx/+bug/1790213 o https://bugs.launchpad.net/starlingx/+bug/1790716 * CentOS 7.5 function branch merge back. o Plan is to merge this week but the risk is high. ISO send to GDC team last Friday and build instructions to Wind River. Test results from GDC are accetable - seeing the 0213 issue just like mainline. Discussion of debugging the current issues we're seeing both in mainline and on the CentOS branch. o Branch merge critieria - need to complete Sanity and Regression tests, need the symbol table resolved, and need to have basic function and configurations (simplex, duplex, multinode) working o Need to rebase the branch to main soon and often. -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.thebeau at windriver.com Wed Sep 12 15:23:42 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Wed, 12 Sep 2018 11:23:42 -0400 Subject: [Starlingx-discuss] Stories for stx-tools deployment Message-ID: <511d268b-c23c-2520-152c-fcf7e9286e09@windriver.com> Hi Dean, Abraham, I've been working through the wikis under "https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment". After I've finished reviewing "standard Controller Storage" and "all-in-one" configurations under virtualization, I'd like consider stories for stx-tools/deployement such as "running multiple clusters on a host" and "testing networking for instances". I do not see anything in storyboard: https://storyboard.openstack.org/#!/project/openstack/stx-tools Do you know if there are plans for those things? M From Jason.McKenna at windriver.com Wed Sep 12 20:23:54 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Wed, 12 Sep 2018 20:23:54 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> Message-ID: > -----Original Message----- > From: Lin, Shuicheng > Sent: September 11, 2018 8:44 PM > To: McKenna, Jason ; Cordoba Malibran, > Erich ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; Liu, > ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Jason, > Here is the dhcp src rpm we are using: > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source dhcp > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5- > 68.el7.centos.1.src.rpm > > For centos-release, there are two packages in the mirror lst, 1 src rpm for > build, and 1 rpm for the mock environment. And it has the "slightly > difference" in the names as you mentioned. > Both of them could be found in the centos repo with the exact name. > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source centos- > release-7-5.1804.1.el7.centos > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > release-7-5.1804.1.el7.centos.src.rpm > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url centos-release-7- > 5.1804.el7.centos.x86_64 > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > release-7-5.1804.el7.centos.x86_64.rpm > > If there is still some other rpm missing, you could try to find them from the > repo. > I have try my best to keep my local mirror the same as the lst. But it is still > possible some package missed to be added to the repo lst. Please feel free > to notify me or correct the error directly. > Thanks. With the latest commits to stx-tools I am now able to download the rpms and produce a build. I'll let you know how testing goes > > Best Regards > Shuicheng > > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Wednesday, September 12, 2018 12:21 AM > To: Cordoba Malibran, Erich ; Waheed, > Numan ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; Liu, > ZhipengS ; Khalil, Ghada > ; Lin, Shuicheng ; > Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Cindy, > > With the latest centos75 branch (and the cherry-picks you mentioned) I am > unable to produce a build. There seems to be several source rpm files > missing from the currently pushed version of the .lst files (or the .lst files pull > down the wrong version). Most of the missing files I can download manually, > however the checked in patches for dhcp and centos-release packages do > not apply against the version of the source RPM which I can manually find on > the Internet. For example, the version of centos-release called out in the .lst > is centos-release-7-5.1804.el7.centos.x86_64.rpm, the version called out in > the checked in code base is the slightly different centos-release-7- > 5.1804.el7.centos.1.x86_64.rpm, and the patches checked in do not apply > against either package. > > Until the centos75 branch of the lst files pulls down the correct rpms, I will be > unable to continue the validation effort. > > -J > > > -----Original Message----- > > From: Cordoba Malibran, Erich > > Sent: September 11, 2018 11:17 AM > > To: Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; McKenna, Jason > > ; Xie, Cindy > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi > > > > You can add "debug loglevel=8" to the kernel boot option to get a more > > detailed output of the crash (if any) > > > > -Erich > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > Shuicheng saw the symbol table error issue as well but it recovers > > > in 8s, he is still working on debugging it. But 601204 is just > > > kernel upgrade but not intended to solve this issues. Are you > > > running bare metal? I am wondering if this is HW config and driver issue. > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > Thx. - cindy > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > To: Xie, Cindy ; Rasa, Nimalini > > > ; Waheed, Numan > > > ; Lin, Shuicheng > > > ; Liu, ZhipengS ; > > > Khalil, Ghada ; 'starlingx-discus > > > s at lists.starlingx.io' > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Cindy, > > > > > > We got past the installation device error, but are coming up against > > > the symbol table error. Our system hangs after this message. I > > > suspect a kernel issue. I see there is an open code review to > > > refactor some kernel patches to a rebased kernel > > > (https://review.open > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > resolve the issue > > > > > > -J > > > > > > From: Xie, Cindy > > > Sent: September 11, 2018 9:32 AM > > > To: Rasa, Nimalini ; Waheed, Numan > > > > n.Waheed at windriver.com>; Lin, Shuicheng ; > > > McKenna, Jason ; Liu, ZhipengS > > > > .liu at intel.com>; Khalil, Ghada ; > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > But as Jason reported yesterday, the build cannot be installed with > > > error messages: > > > > > > Installation failed. > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > We cannot debug without more information, the ISO installs in > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > manifest in this email thread. Did WindRiver has a chance to create > > > a new ISO using today’s manifest file and re-run the test? > > > > > > Thx. - cindy > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > To: Xie, Cindy ; Waheed, Numan > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > Jason ; Liu, ZhipengS > > > > > ; Khalil, Ghada ; > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > This is on the same build (yesterday’s build). > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; > > > Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Is this the same issue as yesterday’s build? or this is different > > > issue now? > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > To: Waheed, Numan ; Lin, Shuicheng > > > > heng.lin at intel.com>; McKenna, Jason > ; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; > > > 'starlingx-discuss at lists.starlingx.io' > > uss at lists.starlingx.io>; Xie, Cindy > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > It is not booting in my case. After the following , it just hangs > > > there: > > > “Error: no symbol table. > > > Press any key to continue…” > > > > > > -Nimalini > > > > > > From: Waheed, Numan > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, Nimalini > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Adding Nimalini > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: September-11-18 2:17 AM > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, Numan > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > Just finished deploy image with latest code, I could config > > > controller successfully in bare metal environment. > > > Manifest is created for you reference. There are two patches I add > > > manually: > > > https://review.openstack.org/596855           for python-horizon > > > from master > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > There is an issue found when reboot controller node. > > > After the OS selection menu, it will show below error. And it will > > > auto continue boot after around 8 seconds. I will check the issue > > > later. > > > “ > > > Error: no symbol table. > > > Press any key to continue… > > > “ > > > > > > Best Regards > > > Shuicheng > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > To: McKenna, Jason ; Liu, ZhipengS > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > indriver.com> > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > I just tried my last Friday’s image at bare metal machine. There is > > > no issue to install controller node. > > > Will you help check what cause the install error in your environment? > > > > > > I am syncing my code to latest to double confirm it. > > > > > > Best Regards > > > Shuicheng > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > ; Khalil, Ghada > > > ; 'starlin > > > gx-discuss at lists.starlingx.io' > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > iver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Status update. The build from the centos75 branch does not install > > > on our hardware. The error message we are seeing is: > > > > > > Installation failed. > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > -Jason > > > > > > From: Liu, ZhipengS > > > Sent: September 8, 2018 9:56 AM > > > To: Lin, Shuicheng ; McKenna, Jason > > > ; Khalil, Ghada > > > ; 's > > > tarlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > @windriver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > > > > I have fixed the issue you mentioned below. > > > - Furthermore, the tpm2-tools package was requesting version > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > > hacked the spec file for tpm2-tools and rebuilt it to require the > > > version mentioned, but there is some rework to be done there. > > > [slin14]: I have the same issue also. Let’s further check it to find > > > the root cause. I use rebuild tpm2-tools/tss2 to workaround it > > > without any code. > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > Thanks! > > > Zhipeng > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: 2018年9月8日 21:14 > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > https://review.openstack.org/#/c/598388/ > > > > > > It is due to my local version is not the latest one. > > > Sorry for the trouble caused, and thanks for your test. > > > > > > Best Regards > > > Shuicheng > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Saturday, September 8, 2018 9:23 AM > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > Thanks very much for such detail feedback. > > > I added some comments inline, and will check the issue in my > > > environment also. > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > Best Regards > > > Shuicheng > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Saturday, September 8, 2018 3:47 AM > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; Lin, Shuicheng ; > > > 's tarlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > @windriver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Shuicheng, > > > > > > I’ve completed a build of the code. We have not yet run run-time > > > tests, but here are the build-time issues I encountered: > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > longer available for download, and the download_mirrors.sh step fails. > > > It appears than CentOS has updated to lighttpd-1.4.50. I manually > > > built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > code still references 1.4.45 > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > expirer-cron-script.patch -- In the new version, on line 190, the > > > patch states that the old code covered 6 lines, and the new code > > > covers 9 lines (-283,6 +286,9). But there are only two lines > > > inserted by the patch. There is also a new blank line in the patch > > > at line 194. Removing this blank line and editing the hunk > > > description to only insert 2 lines resolves the issue for this hunk > > > (there are other similar issues in this patch, and in 0001-meta- > > > modify-aodh-api.patch) > > > [slin14]: Let me double check it. > > > - At binary build time, I had build failures on python-django- > > > horizon and some magnum packages. I had to pull in > > > https://review.op > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > centos75 branch of stx-upstream) to get past this. > > > [slin14]: It is due to I have not synced latest master code, so I > > > don’t have this issue. I used last week’s master code. > > > - After building all packages, I attempted to build the ISO. > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and should > > > be added to the .lst files. > > > [slin14]: This package is already in the lst. > > > - Furthermore, the tpm2-tools package was requesting version > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > > hacked the spec file for tpm2-tools and rebuilt it to require the > > > version mentioned, but there is some rework to be done there. > > > [slin14]: I have the same issue also. Let’s further check it to find > > > the root cause. I use rebuild tpm2-tools/tss2 to workaround it > > > without any code. > > > > > > After these changes, I was able to produce a .iso > > > > > > -Jason > > > > > > From: McKenna, Jason > > > Sent: September 7, 2018 10:08 AM > > > To: Khalil, Ghada ; Lin, Shuicheng > > > ; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Shuicheng, > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > been changed from 1.4.45 to 1.4.49. The > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > -Jason > > > > > > From: Khalil, Ghada > > > Sent: September 7, 2018 9:36 AM > > > To: Lin, Shuicheng ; > > > 'starlingx-discuss at list s.starlingx.io' > > > ; Xie, Cindy > > indy.xie at intel.com>; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will be > > > priming this activity. He’ll share the results with the team > > > sometime next week. > > > > > > Regards, > > > Ghada > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Friday, September 07, 2018 1:32 AM > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > Cindy > > > Subject: CentOS 7.5 upgrade status update > > > > > > Hi all, > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please go > > > ahead to have a try and verify it. > > > I expect there should be some issue due to we just did limited > > > deploy test yet. > > > > > > Here is the detail status update of this week. > > > For the total 44 srpm we plan to upgrade: > > > 38 already merged in feature branch. > > > 3 kept as original version. Anaconda upgrade is not needed. python- > > > os-vif has higher version than 7.5. python-eventlet kept due to new > > > src rpm itself have known issue. > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > 1 under debug. Lighttpd. > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > Here is the build instruction: > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > upstream/stx-root. > > > Cherry-pick below un-merged patch: > > > For puppet-haproxy: > > > https://review.openstack.org/600369 > > > https://review.openstack.org/600359 > > > For openstack-aodh: > > > https://review.openstack.org/598388 > > > https://review.openstack.org/600591 > > > For build-iso: > > > https://review.openstack.org/599892 > > > For build-pkgs: > > > https://review.openstack.org/599901 > > > https://review.openstack.org/600639 > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > rpm. > > > 3. Try to build packages and ISO. > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > Feel free to contact me if you have trouble on it. > > > > > > Best Regards > > > Shuicheng > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ken.Young at windriver.com Wed Sep 12 20:31:04 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Wed, 12 Sep 2018 20:31:04 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <8e1b97a9bee74d40e2cc5802d62c95f8659006ec.camel@intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503768@fmsmsx104.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503931@fmsmsx104.amr.corp.intel.com> <8e1b97a9bee74d40e2cc5802d62c95f8659006ec.camel@intel.com> Message-ID: <15C75A68-7BE3-480B-85E9-A8642238B7FD@windriver.com> Erich, A couple of data points on our side. For our builds, we are using stock CentOS installer for 7.4. These are unchanged and we have not seen this issue on our side. Have you isolated when you made the changes to the installer? Is it the same time you started seeing this error? Does it make sense to revert to the stock installer while we get to the bottom of this issue to continue sanity? Regards, Ken Y On 2018-09-11, 8:30 PM, "Cordoba Malibran, Erich" wrote: I have narrowed down a little bit the issue, these are my findings. - I compared the bootimage_michel.iso with the stx-2018-09-11- 111.iso, which is today's ISO. - The are not significant package differences between them, minor versions has changed in some packages. - The issue is that once the kernel has been loaded through PXE, anaconda is unable to find python2-qpid package. Not sure if this is the first package that is requested. - From the anaconda shell I can see the http://pxecontroller/ serving the files and the repodata seems to be updated there. I installed yum manually and I was able to install python2-qpid package, (and any other available). - The content of the pxe-network-installer package is not the same, WR squashfs.img file has the kernel 3.10.0-693.2.2 but ours has 3.10.0- 862.6.3. We regenerate those files when the kernel was upgraded. (maybe this matches with the date where the issue started to arise..) So, my guess now is that the problem could be caused by the pxe- network-installer package. We create those files with the update- network-installer script. That's the same used in WR to generate these files? I'll keep diging in the generation of these files to see if there is any problem. -Erich On Tue, 2018-09-11 at 20:03 +0000, Lara, Cesar wrote: > I just wanted to make sure that we are able to reproduce the issue > regardless of the build environment. > > AFAIK CentOS 7.5 upgrade is a different issue/thread, but at the end > we can fine tune a process in which we are in the same conditions to > be able to replicate errors in any given build environment. > > Regards > Cesar Lara > > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Tuesday, September 11, 2018 2:02 PM > To: Lara, Cesar ; Alonso, Juan Carlos los.alonso at intel.com>; Khalil, Ghada ; > Martinez Monroy, Elio ; Jones, Bruce > E ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel @windriver.com>; Young, Ken ; Little, Scott > > Subject: RE: [ Test ] Sanity results - summary posted > > Hi Cesar, > > Would you elaborate on what differences you'd expect to see in an > empty mirror populated by the download tool, compared to an existing > mirror which was updated by the download tool? > > The mirror tools were written specifically to contain multiple > versions of packages. The build environment population tools take > the .lst file you have checked out, and places that version from the > mirror into your local environment guaranteeing that your build env > matches the .lst file. If your mirror contains versions 1.0.0, > 1.2.3, and 2.0.0 of a given package, then your environment will only > use the version called out in the .lst file you have checked out. > > This allows the same mirror to be used for multiple branches, for > multiple releases, for multiple development environments, etc, and > guarantees that a build can be reproduced down the road even if the > build inputs disappear from the Internet at some point in the > future. As long as all the artifacts named in the .lst file have > been downloaded at some point in the past, the build environment > produced from a fresh mirror vs a continually updated mirror will be > identical. > > The issue we are observing with the CentOS 7.5 update is that the > versions of packages called out in the .lst files for the centos75 > branch of stx-tools do not match the versions of packages called out > in centos75 branch of the other repos, like stx-integ. The other > branches are attempting to patch a (new) version of the source code, > but the .lst file is only bringing in (or downloading) and older > version of the source. > > -Jason > > > -----Original Message----- > > From: Lara, Cesar > > Sent: September 11, 2018 1:44 PM > > To: Alonso, Juan Carlos ; Khalil, > > Ghada > > ; Martinez Monroy, Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi all, > > > > Just wanted to point out that, to be able to reproduce the issues > > from > > Intel's ISO, somebody will need to go and create a build > > environment > > from scratch, using external upstream repositories to generate a > > new > > mirror, just the way we are doing it in our environment. Failing to > > do > > this will result in a apples to oranges comparison. > > > > Regards > > Cesar Lara > > > > -----Original Message----- > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > > Sent: Tuesday, September 11, 2018 10:54 AM > > To: Khalil, Ghada ; Martinez Monroy, > > Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi Ghada, > > > > Yes, before shared our ISOs I followed such steps and got the same > > issues. > > > > As I mention in the issue > > (https://bugs.launchpad.net/starlingx/+bug/1790213), I could get > > the > > ISO from Michel and testes in our infrastructure, issues not found. > > I > > guess there are differences between the way an ISO is built by > > Intel > > and Wind River since Intel got issues but Wind River does not. I > > think we should sync about this. > > > > Besides, our test infrastructure uses other commands to generate > > VMs, > > add/install hosts (controllers and computes), such commands was > > gotten > > from "tic_vb" repo, such repo was given by China team, if I am not > > wrong such repo was based on Wind River documentation; our test > > framework is based on "tic_vb". Anyway both ways got the same > > results. > > > > Regards. > > Juan Carlos Alonso > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Tuesday, September 11, 2018 8:53 AM > > To: Alonso, Juan Carlos ; Martinez > > Monroy, Elio ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > Hello Juan, > > I read the notes in the Launchpad. > > > > And, just to confirm, are you following the instructions under: > > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtua > > l_E > > nviro > > nment/Controller_Storage > > and still reproducing the two issues below? > > > > I was not able to definitively tell from the Launchpad notes. It's > > important that both our teams are comparing apples to apples. > > > > Thanks, > > Ghada > > > > -----Original Message----- > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > > Sent: Monday, September 10, 2018 1:50 PM > > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; > > Cabrales, > > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: RE: [ Test ] Sanity results - summary posted > > > > Hi, > > > > Such launchpads were updated. > > > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO > > present > > two issues. Michael will upload his ISO, then we will re test > > witch > > each iso in our environment. > > > > An script is being developed to get the differences between ISOs. > > > > Regards. > > Juan Carlos Alonso > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Friday, September 7, 2018 4:43 PM > > To: Khalil, Ghada ; Martinez Monroy, > > Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi Elio/Ada, > > Are there any updates from your side on these two Launchpads? > > https://bugs.launchpad.net/starlingx/+bug/1790213 > > https://bugs.launchpad.net/starlingx/+bug/1790716 > > > > Michel Thebeau (Wind River) has been trying to reproduce these two > > issues (following the starlingx wikis) without success for two > > days > > now. He has been adding his findings to the bugs and communicating > > with your team. > > As a result of his investigation, he will be pushing some small > > fixes > > to stx- tools shortly (some cleanup). > > > > Please let us know if you need any further help from us. > > > > Thanks, > > Ghada > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Wednesday, September 05, 2018 5:39 PM > > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > > starlingx- > > discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Please see inline. There are notes in all the launchpads as well. > > > > I have tagged the last bug for the October release. The rest need > > more > > information to determine whether they gate or not: two maybe > > procedural and one requires more information. > > > > -----Original Message----- > > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > > Sent: Wednesday, September 05, 2018 2:23 PM > > To: Jones, Bruce E; Cabrales, Ada; > > starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > My opinion below > > > > -----Original Message----- > > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > > Sent: Wednesday, September 5, 2018 12:56 PM > > To: Cabrales, Ada ; starlingx- > > discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Should the bugs coming out of this be tagged/fixed for the October > > release? > > > > Related bugs: > > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this > > bug > > is related with 2nd controller provisioning [[GK]] Using the > > instructions published on the wiki, our designer was not able to > > reproduce this issue. > > What instructions are the test team using? > > > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait > > until > > other issues are solved, will fail some test cases related to SSH > > [[GK]] Requested more information. This cannot be debugged further > > without this information. > > > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all > > instances need at least one compute for multimode [[GK]] Using the > > instructions published on the wiki, our designer was not able to > > reproduce this issue. The test team points to internal > > instructions > > which we have no access to. The supported install recipes need to > > be > > on the wiki. I think it is an invalid bug > > > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait > > since > > is related to FM , test cases will fail [[GK]] As Brent pointed > > out, > > this is dependent on the integration of stx-gui which is in > > progress. > > > > -----Original Message----- > > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > > Sent: Wednesday, September 5, 2018 10:50 AM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hello all, > > > > As mentioned on the project meeting today, we're posting the > > summary of the sanity test runs on the Test wiki [0]. The sanity > > is > > triggered each time an ISO is generated (a daily task). > > > > Right now we are posting the results manually, and working on a > > way > > for automating it. Logs of the run are not included, if you want > > to > > have them, you can contact Elio to get them sent to you. > > > > > > [0] > > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_San > > ity > > _S > > ummary > > > > Regards > > Ada > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ken.Young at windriver.com Wed Sep 12 20:53:26 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Wed, 12 Sep 2018 20:53:26 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <15C75A68-7BE3-480B-85E9-A8642238B7FD@windriver.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503768@fmsmsx104.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503931@fmsmsx104.amr.corp.intel.com> <8e1b97a9bee74d40e2cc5802d62c95f8659006ec.camel@intel.com> <15C75A68-7BE3-480B-85E9-A8642238B7FD@windriver.com> Message-ID: <6EEDEF7D-AFE8-4E59-8CF0-1B0D6A3DD800@windriver.com> Erich, One correction below: we are using a Wind River version of the installer (I am confusing this thread with another thread). This is the installer we shipped Titanium Cloud Release 5. This begs the question: what installer were you using before the changes to the kernel? /KenY On 2018-09-12, 4:36 PM, "Young, Ken" wrote: Erich, A couple of data points on our side. For our builds, we are using stock CentOS installer for 7.4. These are unchanged and we have not seen this issue on our side. Have you isolated when you made the changes to the installer? Is it the same time you started seeing this error? Does it make sense to revert to the stock installer while we get to the bottom of this issue to continue sanity? Regards, Ken Y On 2018-09-11, 8:30 PM, "Cordoba Malibran, Erich" wrote: I have narrowed down a little bit the issue, these are my findings. - I compared the bootimage_michel.iso with the stx-2018-09-11- 111.iso, which is today's ISO. - The are not significant package differences between them, minor versions has changed in some packages. - The issue is that once the kernel has been loaded through PXE, anaconda is unable to find python2-qpid package. Not sure if this is the first package that is requested. - From the anaconda shell I can see the http://pxecontroller/ serving the files and the repodata seems to be updated there. I installed yum manually and I was able to install python2-qpid package, (and any other available). - The content of the pxe-network-installer package is not the same, WR squashfs.img file has the kernel 3.10.0-693.2.2 but ours has 3.10.0- 862.6.3. We regenerate those files when the kernel was upgraded. (maybe this matches with the date where the issue started to arise..) So, my guess now is that the problem could be caused by the pxe- network-installer package. We create those files with the update- network-installer script. That's the same used in WR to generate these files? I'll keep diging in the generation of these files to see if there is any problem. -Erich On Tue, 2018-09-11 at 20:03 +0000, Lara, Cesar wrote: > I just wanted to make sure that we are able to reproduce the issue > regardless of the build environment. > > AFAIK CentOS 7.5 upgrade is a different issue/thread, but at the end > we can fine tune a process in which we are in the same conditions to > be able to replicate errors in any given build environment. > > Regards > Cesar Lara > > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Tuesday, September 11, 2018 2:02 PM > To: Lara, Cesar ; Alonso, Juan Carlos los.alonso at intel.com>; Khalil, Ghada ; > Martinez Monroy, Elio ; Jones, Bruce > E ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel @windriver.com>; Young, Ken ; Little, Scott > > Subject: RE: [ Test ] Sanity results - summary posted > > Hi Cesar, > > Would you elaborate on what differences you'd expect to see in an > empty mirror populated by the download tool, compared to an existing > mirror which was updated by the download tool? > > The mirror tools were written specifically to contain multiple > versions of packages. The build environment population tools take > the .lst file you have checked out, and places that version from the > mirror into your local environment guaranteeing that your build env > matches the .lst file. If your mirror contains versions 1.0.0, > 1.2.3, and 2.0.0 of a given package, then your environment will only > use the version called out in the .lst file you have checked out. > > This allows the same mirror to be used for multiple branches, for > multiple releases, for multiple development environments, etc, and > guarantees that a build can be reproduced down the road even if the > build inputs disappear from the Internet at some point in the > future. As long as all the artifacts named in the .lst file have > been downloaded at some point in the past, the build environment > produced from a fresh mirror vs a continually updated mirror will be > identical. > > The issue we are observing with the CentOS 7.5 update is that the > versions of packages called out in the .lst files for the centos75 > branch of stx-tools do not match the versions of packages called out > in centos75 branch of the other repos, like stx-integ. The other > branches are attempting to patch a (new) version of the source code, > but the .lst file is only bringing in (or downloading) and older > version of the source. > > -Jason > > > -----Original Message----- > > From: Lara, Cesar > > Sent: September 11, 2018 1:44 PM > > To: Alonso, Juan Carlos ; Khalil, > > Ghada > > ; Martinez Monroy, Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi all, > > > > Just wanted to point out that, to be able to reproduce the issues > > from > > Intel's ISO, somebody will need to go and create a build > > environment > > from scratch, using external upstream repositories to generate a > > new > > mirror, just the way we are doing it in our environment. Failing to > > do > > this will result in a apples to oranges comparison. > > > > Regards > > Cesar Lara > > > > -----Original Message----- > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > > Sent: Tuesday, September 11, 2018 10:54 AM > > To: Khalil, Ghada ; Martinez Monroy, > > Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi Ghada, > > > > Yes, before shared our ISOs I followed such steps and got the same > > issues. > > > > As I mention in the issue > > (https://bugs.launchpad.net/starlingx/+bug/1790213), I could get > > the > > ISO from Michel and testes in our infrastructure, issues not found. > > I > > guess there are differences between the way an ISO is built by > > Intel > > and Wind River since Intel got issues but Wind River does not. I > > think we should sync about this. > > > > Besides, our test infrastructure uses other commands to generate > > VMs, > > add/install hosts (controllers and computes), such commands was > > gotten > > from "tic_vb" repo, such repo was given by China team, if I am not > > wrong such repo was based on Wind River documentation; our test > > framework is based on "tic_vb". Anyway both ways got the same > > results. > > > > Regards. > > Juan Carlos Alonso > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Tuesday, September 11, 2018 8:53 AM > > To: Alonso, Juan Carlos ; Martinez > > Monroy, Elio ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > Hello Juan, > > I read the notes in the Launchpad. > > > > And, just to confirm, are you following the instructions under: > > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtua > > l_E > > nviro > > nment/Controller_Storage > > and still reproducing the two issues below? > > > > I was not able to definitively tell from the Launchpad notes. It's > > important that both our teams are comparing apples to apples. > > > > Thanks, > > Ghada > > > > -----Original Message----- > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > > Sent: Monday, September 10, 2018 1:50 PM > > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; > > Cabrales, > > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: RE: [ Test ] Sanity results - summary posted > > > > Hi, > > > > Such launchpads were updated. > > > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO > > present > > two issues. Michael will upload his ISO, then we will re test > > witch > > each iso in our environment. > > > > An script is being developed to get the differences between ISOs. > > > > Regards. > > Juan Carlos Alonso > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Friday, September 7, 2018 4:43 PM > > To: Khalil, Ghada ; Martinez Monroy, > > Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi Elio/Ada, > > Are there any updates from your side on these two Launchpads? > > https://bugs.launchpad.net/starlingx/+bug/1790213 > > https://bugs.launchpad.net/starlingx/+bug/1790716 > > > > Michel Thebeau (Wind River) has been trying to reproduce these two > > issues (following the starlingx wikis) without success for two > > days > > now. He has been adding his findings to the bugs and communicating > > with your team. > > As a result of his investigation, he will be pushing some small > > fixes > > to stx- tools shortly (some cleanup). > > > > Please let us know if you need any further help from us. > > > > Thanks, > > Ghada > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Wednesday, September 05, 2018 5:39 PM > > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > > starlingx- > > discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Please see inline. There are notes in all the launchpads as well. > > > > I have tagged the last bug for the October release. The rest need > > more > > information to determine whether they gate or not: two maybe > > procedural and one requires more information. > > > > -----Original Message----- > > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > > Sent: Wednesday, September 05, 2018 2:23 PM > > To: Jones, Bruce E; Cabrales, Ada; > > starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > My opinion below > > > > -----Original Message----- > > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > > Sent: Wednesday, September 5, 2018 12:56 PM > > To: Cabrales, Ada ; starlingx- > > discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Should the bugs coming out of this be tagged/fixed for the October > > release? > > > > Related bugs: > > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this > > bug > > is related with 2nd controller provisioning [[GK]] Using the > > instructions published on the wiki, our designer was not able to > > reproduce this issue. > > What instructions are the test team using? > > > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait > > until > > other issues are solved, will fail some test cases related to SSH > > [[GK]] Requested more information. This cannot be debugged further > > without this information. > > > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all > > instances need at least one compute for multimode [[GK]] Using the > > instructions published on the wiki, our designer was not able to > > reproduce this issue. The test team points to internal > > instructions > > which we have no access to. The supported install recipes need to > > be > > on the wiki. I think it is an invalid bug > > > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait > > since > > is related to FM , test cases will fail [[GK]] As Brent pointed > > out, > > this is dependent on the integration of stx-gui which is in > > progress. > > > > -----Original Message----- > > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > > Sent: Wednesday, September 5, 2018 10:50 AM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hello all, > > > > As mentioned on the project meeting today, we're posting the > > summary of the sanity test runs on the Test wiki [0]. The sanity > > is > > triggered each time an ISO is generated (a daily task). > > > > Right now we are posting the results manually, and working on a > > way > > for automating it. Logs of the run are not included, if you want > > to > > have them, you can contact Elio to get them sent to you. > > > > > > [0] > > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_San > > ity > > _S > > ummary > > > > Regards > > Ada > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Wed Sep 12 21:28:50 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 12 Sep 2018 21:28:50 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <6EEDEF7D-AFE8-4E59-8CF0-1B0D6A3DD800@windriver.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503768@fmsmsx104.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503931@fmsmsx104.amr.corp.intel.com> <8e1b97a9bee74d40e2cc5802d62c95f8659006ec.camel@intel.com> <15C75A68-7BE3-480B-85E9-A8642238B7FD@windriver.com> <6EEDEF7D-AFE8-4E59-8CF0-1B0D6A3DD800@windriver.com> Message-ID: HI, I think I found the root cause. Running the anaconda-yum through strace I found that the webserver was returning a Forbidden error, then checking the lighttpd.conf differences I saw that in the WR image, the user and group fields weren't set. In our /etc/lighttpd/lighttpd.conf we have: ## change uid to (default: don't care) server.username = "www" ## change uid to (default: don't care) server.groupname = "wrs_protected" However on WR image, these are not set. Commenting this lines unblocks the installer. I'm still not sure on what changed, new package version, some puppet recipe or another thing. Even more weird, why these files are different between ISOs. -Erich On 9/12/18, 3:53 PM, "Young, Ken" wrote: Erich, One correction below: we are using a Wind River version of the installer (I am confusing this thread with another thread). This is the installer we shipped Titanium Cloud Release 5. This begs the question: what installer were you using before the changes to the kernel? /KenY On 2018-09-12, 4:36 PM, "Young, Ken" wrote: Erich, A couple of data points on our side. For our builds, we are using stock CentOS installer for 7.4. These are unchanged and we have not seen this issue on our side. Have you isolated when you made the changes to the installer? Is it the same time you started seeing this error? Does it make sense to revert to the stock installer while we get to the bottom of this issue to continue sanity? Regards, Ken Y On 2018-09-11, 8:30 PM, "Cordoba Malibran, Erich" wrote: I have narrowed down a little bit the issue, these are my findings. - I compared the bootimage_michel.iso with the stx-2018-09-11- 111.iso, which is today's ISO. - The are not significant package differences between them, minor versions has changed in some packages. - The issue is that once the kernel has been loaded through PXE, anaconda is unable to find python2-qpid package. Not sure if this is the first package that is requested. - From the anaconda shell I can see the http://pxecontroller/ serving the files and the repodata seems to be updated there. I installed yum manually and I was able to install python2-qpid package, (and any other available). - The content of the pxe-network-installer package is not the same, WR squashfs.img file has the kernel 3.10.0-693.2.2 but ours has 3.10.0- 862.6.3. We regenerate those files when the kernel was upgraded. (maybe this matches with the date where the issue started to arise..) So, my guess now is that the problem could be caused by the pxe- network-installer package. We create those files with the update- network-installer script. That's the same used in WR to generate these files? I'll keep diging in the generation of these files to see if there is any problem. -Erich On Tue, 2018-09-11 at 20:03 +0000, Lara, Cesar wrote: > I just wanted to make sure that we are able to reproduce the issue > regardless of the build environment. > > AFAIK CentOS 7.5 upgrade is a different issue/thread, but at the end > we can fine tune a process in which we are in the same conditions to > be able to replicate errors in any given build environment. > > Regards > Cesar Lara > > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Tuesday, September 11, 2018 2:02 PM > To: Lara, Cesar ; Alonso, Juan Carlos los.alonso at intel.com>; Khalil, Ghada ; > Martinez Monroy, Elio ; Jones, Bruce > E ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel @windriver.com>; Young, Ken ; Little, Scott > > Subject: RE: [ Test ] Sanity results - summary posted > > Hi Cesar, > > Would you elaborate on what differences you'd expect to see in an > empty mirror populated by the download tool, compared to an existing > mirror which was updated by the download tool? > > The mirror tools were written specifically to contain multiple > versions of packages. The build environment population tools take > the .lst file you have checked out, and places that version from the > mirror into your local environment guaranteeing that your build env > matches the .lst file. If your mirror contains versions 1.0.0, > 1.2.3, and 2.0.0 of a given package, then your environment will only > use the version called out in the .lst file you have checked out. > > This allows the same mirror to be used for multiple branches, for > multiple releases, for multiple development environments, etc, and > guarantees that a build can be reproduced down the road even if the > build inputs disappear from the Internet at some point in the > future. As long as all the artifacts named in the .lst file have > been downloaded at some point in the past, the build environment > produced from a fresh mirror vs a continually updated mirror will be > identical. > > The issue we are observing with the CentOS 7.5 update is that the > versions of packages called out in the .lst files for the centos75 > branch of stx-tools do not match the versions of packages called out > in centos75 branch of the other repos, like stx-integ. The other > branches are attempting to patch a (new) version of the source code, > but the .lst file is only bringing in (or downloading) and older > version of the source. > > -Jason > > > -----Original Message----- > > From: Lara, Cesar > > Sent: September 11, 2018 1:44 PM > > To: Alonso, Juan Carlos ; Khalil, > > Ghada > > ; Martinez Monroy, Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi all, > > > > Just wanted to point out that, to be able to reproduce the issues > > from > > Intel's ISO, somebody will need to go and create a build > > environment > > from scratch, using external upstream repositories to generate a > > new > > mirror, just the way we are doing it in our environment. Failing to > > do > > this will result in a apples to oranges comparison. > > > > Regards > > Cesar Lara > > > > -----Original Message----- > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > > Sent: Tuesday, September 11, 2018 10:54 AM > > To: Khalil, Ghada ; Martinez Monroy, > > Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi Ghada, > > > > Yes, before shared our ISOs I followed such steps and got the same > > issues. > > > > As I mention in the issue > > (https://bugs.launchpad.net/starlingx/+bug/1790213), I could get > > the > > ISO from Michel and testes in our infrastructure, issues not found. > > I > > guess there are differences between the way an ISO is built by > > Intel > > and Wind River since Intel got issues but Wind River does not. I > > think we should sync about this. > > > > Besides, our test infrastructure uses other commands to generate > > VMs, > > add/install hosts (controllers and computes), such commands was > > gotten > > from "tic_vb" repo, such repo was given by China team, if I am not > > wrong such repo was based on Wind River documentation; our test > > framework is based on "tic_vb". Anyway both ways got the same > > results. > > > > Regards. > > Juan Carlos Alonso > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Tuesday, September 11, 2018 8:53 AM > > To: Alonso, Juan Carlos ; Martinez > > Monroy, Elio ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > Hello Juan, > > I read the notes in the Launchpad. > > > > And, just to confirm, are you following the instructions under: > > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtua > > l_E > > nviro > > nment/Controller_Storage > > and still reproducing the two issues below? > > > > I was not able to definitively tell from the Launchpad notes. It's > > important that both our teams are comparing apples to apples. > > > > Thanks, > > Ghada > > > > -----Original Message----- > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > > Sent: Monday, September 10, 2018 1:50 PM > > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; > > Cabrales, > > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: RE: [ Test ] Sanity results - summary posted > > > > Hi, > > > > Such launchpads were updated. > > > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO > > present > > two issues. Michael will upload his ISO, then we will re test > > witch > > each iso in our environment. > > > > An script is being developed to get the differences between ISOs. > > > > Regards. > > Juan Carlos Alonso > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Friday, September 7, 2018 4:43 PM > > To: Khalil, Ghada ; Martinez Monroy, > > Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi Elio/Ada, > > Are there any updates from your side on these two Launchpads? > > https://bugs.launchpad.net/starlingx/+bug/1790213 > > https://bugs.launchpad.net/starlingx/+bug/1790716 > > > > Michel Thebeau (Wind River) has been trying to reproduce these two > > issues (following the starlingx wikis) without success for two > > days > > now. He has been adding his findings to the bugs and communicating > > with your team. > > As a result of his investigation, he will be pushing some small > > fixes > > to stx- tools shortly (some cleanup). > > > > Please let us know if you need any further help from us. > > > > Thanks, > > Ghada > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Wednesday, September 05, 2018 5:39 PM > > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > > starlingx- > > discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Please see inline. There are notes in all the launchpads as well. > > > > I have tagged the last bug for the October release. The rest need > > more > > information to determine whether they gate or not: two maybe > > procedural and one requires more information. > > > > -----Original Message----- > > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > > Sent: Wednesday, September 05, 2018 2:23 PM > > To: Jones, Bruce E; Cabrales, Ada; > > starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > My opinion below > > > > -----Original Message----- > > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > > Sent: Wednesday, September 5, 2018 12:56 PM > > To: Cabrales, Ada ; starlingx- > > discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Should the bugs coming out of this be tagged/fixed for the October > > release? > > > > Related bugs: > > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this > > bug > > is related with 2nd controller provisioning [[GK]] Using the > > instructions published on the wiki, our designer was not able to > > reproduce this issue. > > What instructions are the test team using? > > > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait > > until > > other issues are solved, will fail some test cases related to SSH > > [[GK]] Requested more information. This cannot be debugged further > > without this information. > > > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all > > instances need at least one compute for multimode [[GK]] Using the > > instructions published on the wiki, our designer was not able to > > reproduce this issue. The test team points to internal > > instructions > > which we have no access to. The supported install recipes need to > > be > > on the wiki. I think it is an invalid bug > > > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait > > since > > is related to FM , test cases will fail [[GK]] As Brent pointed > > out, > > this is dependent on the integration of stx-gui which is in > > progress. > > > > -----Original Message----- > > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > > Sent: Wednesday, September 5, 2018 10:50 AM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hello all, > > > > As mentioned on the project meeting today, we're posting the > > summary of the sanity test runs on the Test wiki [0]. The sanity > > is > > triggered each time an ISO is generated (a daily task). > > > > Right now we are posting the results manually, and working on a > > way > > for automating it. Logs of the run are not included, if you want > > to > > have them, you can contact Elio to get them sent to you. > > > > > > [0] > > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_San > > ity > > _S > > ummary > > > > Regards > > Ada > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Wed Sep 12 21:37:18 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 12 Sep 2018 21:37:18 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <6EEDEF7D-AFE8-4E59-8CF0-1B0D6A3DD800@windriver.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503768@fmsmsx104.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503931@fmsmsx104.amr.corp.intel.com> <8e1b97a9bee74d40e2cc5802d62c95f8659006ec.camel@intel.com> <15C75A68-7BE3-480B-85E9-A8642238B7FD@windriver.com> <6EEDEF7D-AFE8-4E59-8CF0-1B0D6A3DD800@windriver.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3A91AD@ALA-MBD.corp.ad.wrs.com> The problem is one of permissions. In the /www/var/log/lighttpd-access.log file, you can see the http access request is being rejected with a 403 status code, indicating access is forbidden: 192.168.204.85 pxecontroller - [12/Sep/2018:09:30:52 +0000] "GET /feed/rel-18.08/Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm HTTP/1.1" 403 345 "-" "urlgrabber/3.10 yum/3.4.3" You can see this also with a wget command: localhost:/home/wrsroot# wget http://localhost/feed/rel-18.08/Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm --2018-09-12 20:54:19-- http://localhost/feed/rel-18.08/Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm Resolving localhost (localhost)... ::1, 127.0.0.1 Connecting to localhost (localhost)|::1|:80... connected. HTTP request sent, awaiting response... 403 Forbidden 2018-09-12 20:54:19 ERROR 403: Forbidden. The problem is that two of the RPMs on the ISO have 600 permissions, where all other RPMs are 644. This is carried over when the files are copied to the controller during the post-install phase: controller-0:~$ ls -l /mnt/iso/Packages/ | grep -- --- -rw------- 1 1001 users 258624 Aug 28 12:04 python2-qpid-proton-0.24.0-1.el7.x86_64.rpm -rw------- 1 1001 users 190128 Aug 28 12:04 qpid-proton-c-0.24.0-1.el7.x86_64.rpm controller-0:~$ ls -l /www/pages/feed/rel-18.08/Packages/ |grep -- --- -rw-------. 1 root root 258624 Sep 12 20:33 python2-qpid-proton-0.24.0-1.el7.x86_64.rpm -rw-------. 1 root root 190128 Sep 12 20:33 qpid-proton-c-0.24.0-1.el7.x86_64.rpm The lighttpd server runs as a non-root user, and cannot access these files. Change the permissions on the files, and the installation of controller-1 should be successful. -----Original Message----- From: Young, Ken [mailto:Ken.Young at windriver.com] Sent: Wednesday, September 12, 2018 4:53 PM To: Cordoba Malibran, Erich Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted Erich, One correction below: we are using a Wind River version of the installer (I am confusing this thread with another thread). This is the installer we shipped Titanium Cloud Release 5. This begs the question: what installer were you using before the changes to the kernel? /KenY On 2018-09-12, 4:36 PM, "Young, Ken" wrote: Erich, A couple of data points on our side. For our builds, we are using stock CentOS installer for 7.4. These are unchanged and we have not seen this issue on our side. Have you isolated when you made the changes to the installer? Is it the same time you started seeing this error? Does it make sense to revert to the stock installer while we get to the bottom of this issue to continue sanity? Regards, Ken Y On 2018-09-11, 8:30 PM, "Cordoba Malibran, Erich" wrote: I have narrowed down a little bit the issue, these are my findings. - I compared the bootimage_michel.iso with the stx-2018-09-11- 111.iso, which is today's ISO. - The are not significant package differences between them, minor versions has changed in some packages. - The issue is that once the kernel has been loaded through PXE, anaconda is unable to find python2-qpid package. Not sure if this is the first package that is requested. - From the anaconda shell I can see the http://pxecontroller/ serving the files and the repodata seems to be updated there. I installed yum manually and I was able to install python2-qpid package, (and any other available). - The content of the pxe-network-installer package is not the same, WR squashfs.img file has the kernel 3.10.0-693.2.2 but ours has 3.10.0- 862.6.3. We regenerate those files when the kernel was upgraded. (maybe this matches with the date where the issue started to arise..) So, my guess now is that the problem could be caused by the pxe- network-installer package. We create those files with the update- network-installer script. That's the same used in WR to generate these files? I'll keep diging in the generation of these files to see if there is any problem. -Erich On Tue, 2018-09-11 at 20:03 +0000, Lara, Cesar wrote: > I just wanted to make sure that we are able to reproduce the issue > regardless of the build environment. > > AFAIK CentOS 7.5 upgrade is a different issue/thread, but at the end > we can fine tune a process in which we are in the same conditions to > be able to replicate errors in any given build environment. > > Regards > Cesar Lara > > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Tuesday, September 11, 2018 2:02 PM > To: Lara, Cesar ; Alonso, Juan Carlos los.alonso at intel.com>; Khalil, Ghada ; > Martinez Monroy, Elio ; Jones, Bruce > E ; Cabrales, Ada ; > starlingx-discuss at lists.starlingx.io; Thebeau, Michel @windriver.com>; Young, Ken ; Little, Scott > > Subject: RE: [ Test ] Sanity results - summary posted > > Hi Cesar, > > Would you elaborate on what differences you'd expect to see in an > empty mirror populated by the download tool, compared to an existing > mirror which was updated by the download tool? > > The mirror tools were written specifically to contain multiple > versions of packages. The build environment population tools take > the .lst file you have checked out, and places that version from the > mirror into your local environment guaranteeing that your build env > matches the .lst file. If your mirror contains versions 1.0.0, > 1.2.3, and 2.0.0 of a given package, then your environment will only > use the version called out in the .lst file you have checked out. > > This allows the same mirror to be used for multiple branches, for > multiple releases, for multiple development environments, etc, and > guarantees that a build can be reproduced down the road even if the > build inputs disappear from the Internet at some point in the > future. As long as all the artifacts named in the .lst file have > been downloaded at some point in the past, the build environment > produced from a fresh mirror vs a continually updated mirror will be > identical. > > The issue we are observing with the CentOS 7.5 update is that the > versions of packages called out in the .lst files for the centos75 > branch of stx-tools do not match the versions of packages called out > in centos75 branch of the other repos, like stx-integ. The other > branches are attempting to patch a (new) version of the source code, > but the .lst file is only bringing in (or downloading) and older > version of the source. > > -Jason > > > -----Original Message----- > > From: Lara, Cesar > > Sent: September 11, 2018 1:44 PM > > To: Alonso, Juan Carlos ; Khalil, > > Ghada > > ; Martinez Monroy, Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi all, > > > > Just wanted to point out that, to be able to reproduce the issues > > from > > Intel's ISO, somebody will need to go and create a build > > environment > > from scratch, using external upstream repositories to generate a > > new > > mirror, just the way we are doing it in our environment. Failing to > > do > > this will result in a apples to oranges comparison. > > > > Regards > > Cesar Lara > > > > -----Original Message----- > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > > Sent: Tuesday, September 11, 2018 10:54 AM > > To: Khalil, Ghada ; Martinez Monroy, > > Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi Ghada, > > > > Yes, before shared our ISOs I followed such steps and got the same > > issues. > > > > As I mention in the issue > > (https://bugs.launchpad.net/starlingx/+bug/1790213), I could get > > the > > ISO from Michel and testes in our infrastructure, issues not found. > > I > > guess there are differences between the way an ISO is built by > > Intel > > and Wind River since Intel got issues but Wind River does not. I > > think we should sync about this. > > > > Besides, our test infrastructure uses other commands to generate > > VMs, > > add/install hosts (controllers and computes), such commands was > > gotten > > from "tic_vb" repo, such repo was given by China team, if I am not > > wrong such repo was based on Wind River documentation; our test > > framework is based on "tic_vb". Anyway both ways got the same > > results. > > > > Regards. > > Juan Carlos Alonso > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Tuesday, September 11, 2018 8:53 AM > > To: Alonso, Juan Carlos ; Martinez > > Monroy, Elio ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > Hello Juan, > > I read the notes in the Launchpad. > > > > And, just to confirm, are you following the instructions under: > > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtua > > l_E > > nviro > > nment/Controller_Storage > > and still reproducing the two issues below? > > > > I was not able to definitively tell from the Launchpad notes. It's > > important that both our teams are comparing apples to apples. > > > > Thanks, > > Ghada > > > > -----Original Message----- > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] > > Sent: Monday, September 10, 2018 1:50 PM > > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; > > Cabrales, > > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > Subject: RE: [ Test ] Sanity results - summary posted > > > > Hi, > > > > Such launchpads were updated. > > > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO > > present > > two issues. Michael will upload his ISO, then we will re test > > witch > > each iso in our environment. > > > > An script is being developed to get the differences between ISOs. > > > > Regards. > > Juan Carlos Alonso > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Friday, September 7, 2018 4:43 PM > > To: Khalil, Ghada ; Martinez Monroy, > > Elio > > ; Jones, Bruce E > > ; Cabrales, Ada ; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi Elio/Ada, > > Are there any updates from your side on these two Launchpads? > > https://bugs.launchpad.net/starlingx/+bug/1790213 > > https://bugs.launchpad.net/starlingx/+bug/1790716 > > > > Michel Thebeau (Wind River) has been trying to reproduce these two > > issues (following the starlingx wikis) without success for two > > days > > now. He has been adding his findings to the bugs and communicating > > with your team. > > As a result of his investigation, he will be pushing some small > > fixes > > to stx- tools shortly (some cleanup). > > > > Please let us know if you need any further help from us. > > > > Thanks, > > Ghada > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > Sent: Wednesday, September 05, 2018 5:39 PM > > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > > starlingx- > > discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Please see inline. There are notes in all the launchpads as well. > > > > I have tagged the last bug for the October release. The rest need > > more > > information to determine whether they gate or not: two maybe > > procedural and one requires more information. > > > > -----Original Message----- > > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] > > Sent: Wednesday, September 05, 2018 2:23 PM > > To: Jones, Bruce E; Cabrales, Ada; > > starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > My opinion below > > > > -----Original Message----- > > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > > Sent: Wednesday, September 5, 2018 12:56 PM > > To: Cabrales, Ada ; starlingx- > > discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Should the bugs coming out of this be tagged/fixed for the October > > release? > > > > Related bugs: > > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this > > bug > > is related with 2nd controller provisioning [[GK]] Using the > > instructions published on the wiki, our designer was not able to > > reproduce this issue. > > What instructions are the test team using? > > > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait > > until > > other issues are solved, will fail some test cases related to SSH > > [[GK]] Requested more information. This cannot be debugged further > > without this information. > > > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all > > instances need at least one compute for multimode [[GK]] Using the > > instructions published on the wiki, our designer was not able to > > reproduce this issue. The test team points to internal > > instructions > > which we have no access to. The supported install recipes need to > > be > > on the wiki. I think it is an invalid bug > > > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait > > since > > is related to FM , test cases will fail [[GK]] As Brent pointed > > out, > > this is dependent on the integration of stx-gui which is in > > progress. > > > > -----Original Message----- > > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > > Sent: Wednesday, September 5, 2018 10:50 AM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hello all, > > > > As mentioned on the project meeting today, we're posting the > > summary of the sanity test runs on the Test wiki [0]. The sanity > > is > > triggered each time an ISO is generated (a daily task). > > > > Right now we are posting the results manually, and working on a > > way > > for automating it. Logs of the run are not included, if you want > > to > > have them, you can contact Elio to get them sent to you. > > > > > > [0] > > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_San > > ity > > _S > > ummary > > > > Regards > > Ada > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Wed Sep 12 23:49:37 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 12 Sep 2018 23:49:37 +0000 Subject: [Starlingx-discuss] Notes from today's StarlingX PTG meeting Message-ID: <9A85D2917C58154C960D95352B22818BAB58D219@fmsmsx115.amr.corp.intel.com> Here my notes from our StarlingX PTG session today. Slides reviewed in the meeting are attached. PTG Results and Decisions * Bruce reviewed and got feedback on his draft Feature Planning proposal, o Action: Bruce to publish an updated draft to the wiki and seek community feedback * Bruce also reviewed and got feedback on the draft Governance o Action: Bruce to publish the updated version to the wiki and seek feedback * Brent led a discussion of when and how to rebase our OpenStack content. Rebasing has been found to take up to six months in the past. While rebasing isnt directly tied to our patch upstreaming efforts, rebasing the carried patches is a big part of the work. o Action: We agreed to defer an OpenStack update until the July'19 release which will use Stein. Work needs to start in Jan'19 to allow us to meet that date. We should expect the effort to be large and complex. o Action: We agreed that for now we will update OpenStack once per year. o Action: We agreed to look at prioritizing patch upstreaming that would more quickly lead to zero patch content for some components, which might not lower the patch count as much but would lower the number of patched components. * Bruce led a brief discussion on the Python2->3 transition. o Action We agreed to get the stx services Python3 clean for the March'19 release. * Brent led a discussion on Multi-OS support. It evolved into a discussion on how to enable Clear Linux and how to _not_ waste effort - we want to leverage the work the Intel team does to enable Clear to help us accelerate Multi-OS support for StarlingX. o Action: The TSC approves a new sub-project for Multi-OS. The current/proposed Clear Linux sub-project will be changed to be a deliverable of the Multi-OS sub-project. We will also deliver Ubuntu support. Team Lead candidates Bruce, TBD.. Project Lead candidates Brent, Saul, tbd.. Team TBD. We are looking for volunteers who can help contribute - in a lead role or as a developer. Help from the Ubuntu community would be awesome. Experts in StarlingX SW Update and Patching especially needed. o Action: This work will get much easier as we work the carrier patch backlog down. Additional devs needed to help with this. * Saul led a discussion on Build issues. He proposes using Zulu (UTC) timestamps for the build optimization effort. Long term as we move toward Multi-OS we should continue to use the build containers which are easy to build for any OS. o Action: We agree with Saul's proposal, Saul to communicate with the Build team. Meanwhile Chuy is working on a wrapper script to wrap the build commands to allow one command list - the code is in review. * Brent presented an update on the initial plans for containerization. o A set of specs will be prepared for review for the first phase of the work (containerized OpenStack Services) * Brent presented an update on the service de-coupling. o Action: A spec is needed for post-October de-coupling work. * Greg presented an update from the Edge WG that had a very intense discussion yesterday about how to define a MVP architecture for Edge. It's based on a Federated Keystone and has two main implementation options. There are two key changes that need to be made to enable the architecture, one to be driver by Wind River, the other by James (from Oath/Verizon). * We discussed the need for Zuul jobs and for Zuul-based test content, including DevStack API level tests. We would like to accelerate these efforts. * Bruce provided an update on the Security team's work, which is following the OpenStack Security team process. Most of the work will be hidden from public view as we work through identifying potential security issues in an embargoed forum. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: MVP-Architecture_edge-computing_PTG.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 4186871 bytes Desc: MVP-Architecture_edge-computing_PTG.pptx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: StarlingX PTG Denver 2018.pdf Type: application/pdf Size: 101254 bytes Desc: StarlingX PTG Denver 2018.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ptg_decoupling.pdf Type: application/pdf Size: 589008 bytes Desc: ptg_decoupling.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ptg_containers.pdf Type: application/pdf Size: 1081180 bytes Desc: ptg_containers.pdf URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ptg_multi_os.pdf Type: application/pdf Size: 669053 bytes Desc: ptg_multi_os.pdf URL: From cindy.xie at intel.com Thu Sep 13 06:43:38 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 13 Sep 2018 06:43:38 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> Elio, We will provide you an updated ISO later today with the following: - kernel upgrade to 3.10.0-862.11.6 - symbol issue fixed: https://bugs.launchpad.net/starlingx/+bug/1792257 Please help to do a sanity test based on this new ISO from Shuicheng on VE. @Jason, Please re-generate a build using today's manifest with above fix. Shuicheng shall be able to provide manifest with exact commitID. @Numan, please abort your current testing w/ old ISO once you get a new one from Jason and continue your sanity and regression on bare-metal. I am not sure how long it takes, but please take priority as we want merge back to mainline early next week. Thanks all for the support. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 4:24 AM To: Lin, Shuicheng ; Cordoba Malibran, Erich ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io; Liu, ZhipengS ; Khalil, Ghada ; Xie, Cindy Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > -----Original Message----- > From: Lin, Shuicheng > Sent: September 11, 2018 8:44 PM > To: McKenna, Jason ; Cordoba Malibran, > Erich ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Jason, > Here is the dhcp src rpm we are using: > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source dhcp > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5- > 68.el7.centos.1.src.rpm > > For centos-release, there are two packages in the mirror lst, 1 src > rpm for build, and 1 rpm for the mock environment. And it has the > "slightly difference" in the names as you mentioned. > Both of them could be found in the centos repo with the exact name. > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > centos- release-7-5.1804.1.el7.centos > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > release-7-5.1804.1.el7.centos.src.rpm > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > centos-release-7- > 5.1804.el7.centos.x86_64 > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > release-7-5.1804.el7.centos.x86_64.rpm > > If there is still some other rpm missing, you could try to find them > from the repo. > I have try my best to keep my local mirror the same as the lst. But it > is still possible some package missed to be added to the repo lst. > Please feel free to notify me or correct the error directly. > Thanks. With the latest commits to stx-tools I am now able to download the rpms and produce a build. I'll let you know how testing goes > > Best Regards > Shuicheng > > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Wednesday, September 12, 2018 12:21 AM > To: Cordoba Malibran, Erich ; > Waheed, Numan ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Lin, Shuicheng > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Cindy, > > With the latest centos75 branch (and the cherry-picks you mentioned) I > am unable to produce a build. There seems to be several source rpm > files missing from the currently pushed version of the .lst files (or > the .lst files pull down the wrong version). Most of the missing > files I can download manually, however the checked in patches for dhcp > and centos-release packages do not apply against the version of the > source RPM which I can manually find on the Internet. For example, > the version of centos-release called out in the .lst is > centos-release-7-5.1804.el7.centos.x86_64.rpm, the version called out > in the checked in code base is the slightly different > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches checked in do not apply against either package. > > Until the centos75 branch of the lst files pulls down the correct > rpms, I will be unable to continue the validation effort. > > -J > > > -----Original Message----- > > From: Cordoba Malibran, Erich > > Sent: September 11, 2018 11:17 AM > > To: Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; McKenna, Jason > > ; Xie, Cindy > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > more detailed output of the crash (if any) > > > > -Erich > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > Shuicheng saw the symbol table error issue as well but it recovers > > > in 8s, he is still working on debugging it. But 601204 is just > > > kernel upgrade but not intended to solve this issues. Are you > > > running bare metal? I am wondering if this is HW config and driver issue. > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > Thx. - cindy > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > To: Xie, Cindy ; Rasa, Nimalini > > > ; Waheed, Numan > > > ; Lin, Shuicheng > > > ; Liu, ZhipengS > > l.com>; Khalil, Ghada ; > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Cindy, > > > > > > We got past the installation device error, but are coming up > > > against the symbol table error. Our system hangs after this > > > message. I suspect a kernel issue. I see there is an open code > > > review to refactor some kernel patches to a rebased kernel > > > (https://review.open > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > resolve the issue > > > > > > -J > > > > > > From: Xie, Cindy > > > Sent: September 11, 2018 9:32 AM > > > To: Rasa, Nimalini ; Waheed, Numan > > > > n.Waheed at windriver.com>; Lin, Shuicheng ; > > > McKenna, Jason ; Liu, ZhipengS > > > > .liu at intel.com>; Khalil, Ghada ; > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > But as Jason reported yesterday, the build cannot be installed > > > with error messages: > > > > > > Installation failed. > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > We cannot debug without more information, the ISO installs in > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > manifest in this email thread. Did WindRiver has a chance to > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > Thx. - cindy > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > To: Xie, Cindy ; Waheed, Numan > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > Jason ; Liu, ZhipengS > > > > > ; Khalil, Ghada ; > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > This is on the same build (yesterday’s build). > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; > > > Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Is this the same issue as yesterday’s build? or this is different > > > issue now? > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > To: Waheed, Numan ; Lin, Shuicheng > > > > heng.lin at intel.com>; McKenna, Jason > ; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; > > > 'starlingx-discuss at lists.starlingx.io' > > uss at lists.starlingx.io>; Xie, Cindy > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > It is not booting in my case. After the following , it just hangs > > > there: > > > “Error: no symbol table. > > > Press any key to continue…” > > > > > > -Nimalini > > > > > > From: Waheed, Numan > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, > > > Nimalini > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Adding Nimalini > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: September-11-18 2:17 AM > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, Numan > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > Just finished deploy image with latest code, I could config > > > controller successfully in bare metal environment. > > > Manifest is created for you reference. There are two patches I add > > > manually: > > > https://review.openstack.org/596855           for python-horizon > > > from master > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > There is an issue found when reboot controller node. > > > After the OS selection menu, it will show below error. And it will > > > auto continue boot after around 8 seconds. I will check the issue > > > later. > > > “ > > > Error: no symbol table. > > > Press any key to continue… > > > “ > > > > > > Best Regards > > > Shuicheng > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > To: McKenna, Jason ; Liu, ZhipengS > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > indriver.com> > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > I just tried my last Friday’s image at bare metal machine. There > > > is no issue to install controller node. > > > Will you help check what cause the install error in your environment? > > > > > > I am syncing my code to latest to double confirm it. > > > > > > Best Regards > > > Shuicheng > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > ; Khalil, Ghada > > > ; 'starlin > > > gx-discuss at lists.starlingx.io' > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > iver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Status update. The build from the centos75 branch does not > > > install on our hardware. The error message we are seeing is: > > > > > > Installation failed. > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > -Jason > > > > > > From: Liu, ZhipengS > > > Sent: September 8, 2018 9:56 AM > > > To: Lin, Shuicheng ; McKenna, Jason > > > ; Khalil, Ghada > > > ; 's > > > tarlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > @windriver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > > > > I have fixed the issue you mentioned below. > > > - Furthermore, the tpm2-tools package was requesting version > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > > hacked the spec file for tpm2-tools and rebuilt it to require the > > > version mentioned, but there is some rework to be done there. > > > [slin14]: I have the same issue also. Let’s further check it to > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > it without any code. > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > Thanks! > > > Zhipeng > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: 2018年9月8日 21:14 > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > https://review.openstack.org/#/c/598388/ > > > > > > It is due to my local version is not the latest one. > > > Sorry for the trouble caused, and thanks for your test. > > > > > > Best Regards > > > Shuicheng > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Saturday, September 8, 2018 9:23 AM > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > Thanks very much for such detail feedback. > > > I added some comments inline, and will check the issue in my > > > environment also. > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > Best Regards > > > Shuicheng > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Saturday, September 8, 2018 3:47 AM > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; Lin, Shuicheng ; > > > 's tarlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > @windriver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Shuicheng, > > > > > > I’ve completed a build of the code. We have not yet run run-time > > > tests, but here are the build-time issues I encountered: > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > longer available for download, and the download_mirrors.sh step fails. > > > It appears than CentOS has updated to lighttpd-1.4.50. I manually > > > built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > code still references 1.4.45 > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > expirer-cron-script.patch -- In the new version, on line 190, the > > > patch states that the old code covered 6 lines, and the new code > > > covers 9 lines (-283,6 +286,9). But there are only two lines > > > inserted by the patch. There is also a new blank line in the > > > patch at line 194. Removing this blank line and editing the hunk > > > description to only insert 2 lines resolves the issue for this > > > hunk (there are other similar issues in this patch, and in > > > 0001-meta- > > > modify-aodh-api.patch) > > > [slin14]: Let me double check it. > > > - At binary build time, I had build failures on python-django- > > > horizon and some magnum packages. I had to pull in > > > https://review.op > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > centos75 branch of stx-upstream) to get past this. > > > [slin14]: It is due to I have not synced latest master code, so I > > > don’t have this issue. I used last week’s master code. > > > - After building all packages, I attempted to build the ISO. > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > should be added to the .lst files. > > > [slin14]: This package is already in the lst. > > > - Furthermore, the tpm2-tools package was requesting version > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > > hacked the spec file for tpm2-tools and rebuilt it to require the > > > version mentioned, but there is some rework to be done there. > > > [slin14]: I have the same issue also. Let’s further check it to > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > it without any code. > > > > > > After these changes, I was able to produce a .iso > > > > > > -Jason > > > > > > From: McKenna, Jason > > > Sent: September 7, 2018 10:08 AM > > > To: Khalil, Ghada ; Lin, Shuicheng > > > ; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Shuicheng, > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > been changed from 1.4.45 to 1.4.49. The > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > -Jason > > > > > > From: Khalil, Ghada > > > Sent: September 7, 2018 9:36 AM > > > To: Lin, Shuicheng ; > > > 'starlingx-discuss at list s.starlingx.io' > > > ; Xie, Cindy > > indy.xie at intel.com>; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > be priming this activity. He’ll share the results with the team > > > sometime next week. > > > > > > Regards, > > > Ghada > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Friday, September 07, 2018 1:32 AM > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > Cindy > > > Subject: CentOS 7.5 upgrade status update > > > > > > Hi all, > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please go > > > ahead to have a try and verify it. > > > I expect there should be some issue due to we just did limited > > > deploy test yet. > > > > > > Here is the detail status update of this week. > > > For the total 44 srpm we plan to upgrade: > > > 38 already merged in feature branch. > > > 3 kept as original version. Anaconda upgrade is not needed. > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > due to new src rpm itself have known issue. > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > 1 under debug. Lighttpd. > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > Here is the build instruction: > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > upstream/stx-root. > > > Cherry-pick below un-merged patch: > > > For puppet-haproxy: > > > https://review.openstack.org/600369 > > > https://review.openstack.org/600359 > > > For openstack-aodh: > > > https://review.openstack.org/598388 > > > https://review.openstack.org/600591 > > > For build-iso: > > > https://review.openstack.org/599892 > > > For build-pkgs: > > > https://review.openstack.org/599901 > > > https://review.openstack.org/600639 > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > rpm. > > > 3. Try to build packages and ISO. > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > Feel free to contact me if you have trouble on it. > > > > > > Best Regards > > > Shuicheng > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discu > > > ss From ran1.an at intel.com Thu Sep 13 07:31:23 2018 From: ran1.an at intel.com (An, Ran1) Date: Thu, 13 Sep 2018 07:31:23 +0000 Subject: [Starlingx-discuss] [Container] Story of Initial Kubernetes Integration Message-ID: <9BAB5B7CAF57C3459E4636391F1071CECAE993@shsmsx102.ccr.corp.intel.com> Hi I am going to take task 24909 and 24910 under story initial kubernetes integration , anyone has concerns? Details: story: https://storyboard.openstack.org/#!/story/2002843 , Task 24909- Add unit tests for nfv kubernetes api Task 24910- Use SSL/TLS in nfv kubernetes client Thanks Ran -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Sep 13 08:22:22 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 13 Sep 2018 08:22:22 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C7655359B32@SHSMSX101.ccr.corp.intel.com> Hi Jason, I have not synced my local code. So you could use the same manifest file. You just need sync the latest code for stx-integ. And update mirror with the latest lst in stx-tools. Here is the patch list you need apply: https://review.openstack.org/596855 for python-horizon https://review.openstack.org/599892 for build-iso https://review.openstack.org/602238 for update-pxe-network-installer Best Regards Shuicheng -----Original Message----- From: Xie, Cindy Sent: Thursday, September 13, 2018 2:44 PM To: Martinez Monroy, Elio ; McKenna, Jason ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Elio, We will provide you an updated ISO later today with the following: - kernel upgrade to 3.10.0-862.11.6 - symbol issue fixed: https://bugs.launchpad.net/starlingx/+bug/1792257 Please help to do a sanity test based on this new ISO from Shuicheng on VE. @Jason, Please re-generate a build using today's manifest with above fix. Shuicheng shall be able to provide manifest with exact commitID. @Numan, please abort your current testing w/ old ISO once you get a new one from Jason and continue your sanity and regression on bare-metal. I am not sure how long it takes, but please take priority as we want merge back to mainline early next week. Thanks all for the support. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 4:24 AM To: Lin, Shuicheng ; Cordoba Malibran, Erich ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io; Liu, ZhipengS ; Khalil, Ghada ; Xie, Cindy Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > -----Original Message----- > From: Lin, Shuicheng > Sent: September 11, 2018 8:44 PM > To: McKenna, Jason ; Cordoba Malibran, > Erich ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Jason, > Here is the dhcp src rpm we are using: > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source dhcp > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5- > 68.el7.centos.1.src.rpm > > For centos-release, there are two packages in the mirror lst, 1 src > rpm for build, and 1 rpm for the mock environment. And it has the > "slightly difference" in the names as you mentioned. > Both of them could be found in the centos repo with the exact name. > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > centos- release-7-5.1804.1.el7.centos > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > release-7-5.1804.1.el7.centos.src.rpm > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > centos-release-7- > 5.1804.el7.centos.x86_64 > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > release-7-5.1804.el7.centos.x86_64.rpm > > If there is still some other rpm missing, you could try to find them > from the repo. > I have try my best to keep my local mirror the same as the lst. But it > is still possible some package missed to be added to the repo lst. > Please feel free to notify me or correct the error directly. > Thanks. With the latest commits to stx-tools I am now able to download the rpms and produce a build. I'll let you know how testing goes > > Best Regards > Shuicheng > > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Wednesday, September 12, 2018 12:21 AM > To: Cordoba Malibran, Erich ; > Waheed, Numan ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Lin, Shuicheng > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Cindy, > > With the latest centos75 branch (and the cherry-picks you mentioned) I > am unable to produce a build. There seems to be several source rpm > files missing from the currently pushed version of the .lst files (or > the .lst files pull down the wrong version). Most of the missing > files I can download manually, however the checked in patches for dhcp > and centos-release packages do not apply against the version of the > source RPM which I can manually find on the Internet. For example, > the version of centos-release called out in the .lst is > centos-release-7-5.1804.el7.centos.x86_64.rpm, the version called out > in the checked in code base is the slightly different > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches checked in do not apply against either package. > > Until the centos75 branch of the lst files pulls down the correct > rpms, I will be unable to continue the validation effort. > > -J > > > -----Original Message----- > > From: Cordoba Malibran, Erich > > Sent: September 11, 2018 11:17 AM > > To: Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; McKenna, Jason > > ; Xie, Cindy > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > more detailed output of the crash (if any) > > > > -Erich > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > Shuicheng saw the symbol table error issue as well but it recovers > > > in 8s, he is still working on debugging it. But 601204 is just > > > kernel upgrade but not intended to solve this issues. Are you > > > running bare metal? I am wondering if this is HW config and driver issue. > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > Thx. - cindy > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > To: Xie, Cindy ; Rasa, Nimalini > > > ; Waheed, Numan > > > ; Lin, Shuicheng > > > ; Liu, ZhipengS > > l.com>; Khalil, Ghada ; > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Cindy, > > > > > > We got past the installation device error, but are coming up > > > against the symbol table error. Our system hangs after this > > > message. I suspect a kernel issue. I see there is an open code > > > review to refactor some kernel patches to a rebased kernel > > > (https://review.open > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > resolve the issue > > > > > > -J > > > > > > From: Xie, Cindy > > > Sent: September 11, 2018 9:32 AM > > > To: Rasa, Nimalini ; Waheed, Numan > > > > n.Waheed at windriver.com>; Lin, Shuicheng ; > > > McKenna, Jason ; Liu, ZhipengS > > > > .liu at intel.com>; Khalil, Ghada ; > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > But as Jason reported yesterday, the build cannot be installed > > > with error messages: > > > > > > Installation failed. > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > We cannot debug without more information, the ISO installs in > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > manifest in this email thread. Did WindRiver has a chance to > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > Thx. - cindy > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > To: Xie, Cindy ; Waheed, Numan > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > Jason ; Liu, ZhipengS > > > > > ; Khalil, Ghada ; > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > This is on the same build (yesterday’s build). > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; > > > Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Is this the same issue as yesterday’s build? or this is different > > > issue now? > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > To: Waheed, Numan ; Lin, Shuicheng > > > > heng.lin at intel.com>; McKenna, Jason > ; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; > > > 'starlingx-discuss at lists.starlingx.io' > > uss at lists.starlingx.io>; Xie, Cindy > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > It is not booting in my case. After the following , it just hangs > > > there: > > > “Error: no symbol table. > > > Press any key to continue…” > > > > > > -Nimalini > > > > > > From: Waheed, Numan > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, > > > Nimalini > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Adding Nimalini > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: September-11-18 2:17 AM > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, Numan > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > Just finished deploy image with latest code, I could config > > > controller successfully in bare metal environment. > > > Manifest is created for you reference. There are two patches I add > > > manually: > > > https://review.openstack.org/596855           for python-horizon > > > from master > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > There is an issue found when reboot controller node. > > > After the OS selection menu, it will show below error. And it will > > > auto continue boot after around 8 seconds. I will check the issue > > > later. > > > “ > > > Error: no symbol table. > > > Press any key to continue… > > > “ > > > > > > Best Regards > > > Shuicheng > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > To: McKenna, Jason ; Liu, ZhipengS > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > indriver.com> > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > I just tried my last Friday’s image at bare metal machine. There > > > is no issue to install controller node. > > > Will you help check what cause the install error in your environment? > > > > > > I am syncing my code to latest to double confirm it. > > > > > > Best Regards > > > Shuicheng > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > ; Khalil, Ghada > > > ; 'starlin > > > gx-discuss at lists.starlingx.io' > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > iver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Status update. The build from the centos75 branch does not > > > install on our hardware. The error message we are seeing is: > > > > > > Installation failed. > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > -Jason > > > > > > From: Liu, ZhipengS > > > Sent: September 8, 2018 9:56 AM > > > To: Lin, Shuicheng ; McKenna, Jason > > > ; Khalil, Ghada > > > ; 's > > > tarlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > @windriver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > > > > I have fixed the issue you mentioned below. > > > - Furthermore, the tpm2-tools package was requesting version > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > > hacked the spec file for tpm2-tools and rebuilt it to require the > > > version mentioned, but there is some rework to be done there. > > > [slin14]: I have the same issue also. Let’s further check it to > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > it without any code. > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > Thanks! > > > Zhipeng > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: 2018年9月8日 21:14 > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > https://review.openstack.org/#/c/598388/ > > > > > > It is due to my local version is not the latest one. > > > Sorry for the trouble caused, and thanks for your test. > > > > > > Best Regards > > > Shuicheng > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Saturday, September 8, 2018 9:23 AM > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > Thanks very much for such detail feedback. > > > I added some comments inline, and will check the issue in my > > > environment also. > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > Best Regards > > > Shuicheng > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Saturday, September 8, 2018 3:47 AM > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; Lin, Shuicheng ; > > > 's tarlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > @windriver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Shuicheng, > > > > > > I’ve completed a build of the code. We have not yet run run-time > > > tests, but here are the build-time issues I encountered: > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > longer available for download, and the download_mirrors.sh step fails. > > > It appears than CentOS has updated to lighttpd-1.4.50. I manually > > > built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > code still references 1.4.45 > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > expirer-cron-script.patch -- In the new version, on line 190, the > > > patch states that the old code covered 6 lines, and the new code > > > covers 9 lines (-283,6 +286,9). But there are only two lines > > > inserted by the patch. There is also a new blank line in the > > > patch at line 194. Removing this blank line and editing the hunk > > > description to only insert 2 lines resolves the issue for this > > > hunk (there are other similar issues in this patch, and in > > > 0001-meta- > > > modify-aodh-api.patch) > > > [slin14]: Let me double check it. > > > - At binary build time, I had build failures on python-django- > > > horizon and some magnum packages. I had to pull in > > > https://review.op > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > centos75 branch of stx-upstream) to get past this. > > > [slin14]: It is due to I have not synced latest master code, so I > > > don’t have this issue. I used last week’s master code. > > > - After building all packages, I attempted to build the ISO. > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > should be added to the .lst files. > > > [slin14]: This package is already in the lst. > > > - Furthermore, the tpm2-tools package was requesting version > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > > hacked the spec file for tpm2-tools and rebuilt it to require the > > > version mentioned, but there is some rework to be done there. > > > [slin14]: I have the same issue also. Let’s further check it to > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > it without any code. > > > > > > After these changes, I was able to produce a .iso > > > > > > -Jason > > > > > > From: McKenna, Jason > > > Sent: September 7, 2018 10:08 AM > > > To: Khalil, Ghada ; Lin, Shuicheng > > > ; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Shuicheng, > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > been changed from 1.4.45 to 1.4.49. The > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > -Jason > > > > > > From: Khalil, Ghada > > > Sent: September 7, 2018 9:36 AM > > > To: Lin, Shuicheng ; > > > 'starlingx-discuss at list s.starlingx.io' > > > ; Xie, Cindy > > indy.xie at intel.com>; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > be priming this activity. He’ll share the results with the team > > > sometime next week. > > > > > > Regards, > > > Ghada > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Friday, September 07, 2018 1:32 AM > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > Cindy > > > Subject: CentOS 7.5 upgrade status update > > > > > > Hi all, > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please go > > > ahead to have a try and verify it. > > > I expect there should be some issue due to we just did limited > > > deploy test yet. > > > > > > Here is the detail status update of this week. > > > For the total 44 srpm we plan to upgrade: > > > 38 already merged in feature branch. > > > 3 kept as original version. Anaconda upgrade is not needed. > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > due to new src rpm itself have known issue. > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > 1 under debug. Lighttpd. > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > Here is the build instruction: > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > upstream/stx-root. > > > Cherry-pick below un-merged patch: > > > For puppet-haproxy: > > > https://review.openstack.org/600369 > > > https://review.openstack.org/600359 > > > For openstack-aodh: > > > https://review.openstack.org/598388 > > > https://review.openstack.org/600591 > > > For build-iso: > > > https://review.openstack.org/599892 > > > For build-pkgs: > > > https://review.openstack.org/599901 > > > https://review.openstack.org/600639 > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > rpm. > > > 3. Try to build packages and ISO. > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > Feel free to contact me if you have trouble on it. > > > > > > Best Regards > > > Shuicheng > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discu > > > ss From Frank.Miller at windriver.com Thu Sep 13 13:15:38 2018 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 13 Sep 2018 13:15:38 +0000 Subject: [Starlingx-discuss] [Container] Story of Initial Kubernetes Integration In-Reply-To: <9BAB5B7CAF57C3459E4636391F1071CECAE993@shsmsx102.ccr.corp.intel.com> References: <9BAB5B7CAF57C3459E4636391F1071CECAE993@shsmsx102.ccr.corp.intel.com> Message-ID: Ran: That's for your offer to assist. You can take the 24909 task to add unit tests. Please add Al Bailey and Bart Wensley as reviewers when you are ready. But let's leave the 24910 task unassigned for the moment as we think this may not be required. I have an action to discuss this one with the technical leads. Frank Miller Containers Project Lead From: An, Ran1 [mailto:ran1.an at intel.com] Sent: Thursday, September 13, 2018 3:31 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Container] Story of Initial Kubernetes Integration Hi I am going to take task 24909 and 24910 under story initial kubernetes integration , anyone has concerns? Details: story: https://storyboard.openstack.org/#!/story/2002843 , Task 24909- Add unit tests for nfv kubernetes api Task 24910- Use SSL/TLS in nfv kubernetes client Thanks Ran -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jason.McKenna at windriver.com Thu Sep 13 13:35:15 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Thu, 13 Sep 2018 13:35:15 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. Shuicheng > shall be able to provide manifest with exact commitID. @Numan, please > abort your current testing w/ old ISO once you get a new one from Jason and > continue your sanity and regression on bare-metal. I am not sure how long it > takes, but please take priority as we want merge back to mainline early next > week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; Liu, > ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5- > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But it > > is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the rpms and > produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) I > > am unable to produce a build. There seems to be several source rpm > > files missing from the currently pushed version of the .lst files (or > > the .lst files pull down the wrong version). Most of the missing > > files I can download manually, however the checked in patches for dhcp > > and centos-release packages do not apply against the version of the > > source RPM which I can manually find on the Internet. For example, > > the version of centos-release called out in the .lst is > > centos-release-7-5.1804.el7.centos.x86_64.rpm, the version called out > > in the checked in code base is the slightly different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it recovers > > > > in 8s, he is still working on debugging it. But 601204 is just > > > > kernel upgrade but not intended to solve this issues. Are you > > > > running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; > > > > Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is different > > > > issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, > > > > Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I add > > > > manually: > > > > https://review.openstack.org/596855           for python-horizon > > > > from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it will > > > > auto continue boot after around 8 seconds. I will check the issue > > > > later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > > > hacked the spec file for tpm2-tools and rebuilt it to require the > > > > version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng ; > > > > 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run run-time > > > > tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I manually > > > > built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, the > > > > patch states that the old code covered 6 lines, and the new code > > > > covers 9 lines (-283,6 +286,9). But there are only two lines > > > > inserted by the patch. There is also a new blank line in the > > > > patch at line 194. Removing this blank line and editing the hunk > > > > description to only insert 2 lines resolves the issue for this > > > > hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so I > > > > don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > > > hacked the spec file for tpm2-tools and rebuilt it to require the > > > > version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please go > > > > ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discu > > > > ss -------------- next part -------------- An embedded message was scrubbed... From: svc-cgcsauto Subject: TiS Sanity Test Report IP_1_4 [n/a] - YELLOW Date: Thu, 13 Sep 2018 00:43:14 +0000 Size: 3052 URL: -------------- next part -------------- An embedded message was scrubbed... From: svc-cgcsauto Subject: TiS Nightly Test Report IP_1_4 [n/a] - YELLOW Date: Thu, 13 Sep 2018 03:44:09 +0000 Size: 13566 URL: From cindy.xie at intel.com Thu Sep 13 14:05:20 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 13 Sep 2018 14:05:20 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss From ran1.an at intel.com Thu Sep 13 14:11:27 2018 From: ran1.an at intel.com (An, Ran1) Date: Thu, 13 Sep 2018 14:11:27 +0000 Subject: [Starlingx-discuss] [Container] Story of Initial Kubernetes Integration In-Reply-To: References: <9BAB5B7CAF57C3459E4636391F1071CECAE993@shsmsx102.ccr.corp.intel.com> Message-ID: <9BAB5B7CAF57C3459E4636391F1071CECAEA05@shsmsx102.ccr.corp.intel.com> Hi Miller Thanks for reply. I'll take 24909 task. Ran From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Thursday, September 13, 2018 9:16 PM To: An, Ran1 ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [Container] Story of Initial Kubernetes Integration Ran: That's for your offer to assist. You can take the 24909 task to add unit tests. Please add Al Bailey and Bart Wensley as reviewers when you are ready. But let's leave the 24910 task unassigned for the moment as we think this may not be required. I have an action to discuss this one with the technical leads. Frank Miller Containers Project Lead From: An, Ran1 [mailto:ran1.an at intel.com] Sent: Thursday, September 13, 2018 3:31 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Container] Story of Initial Kubernetes Integration Hi I am going to take task 24909 and 24910 under story initial kubernetes integration , anyone has concerns? Details: story: https://storyboard.openstack.org/#!/story/2002843 , Task 24909- Add unit tests for nfv kubernetes api Task 24910- Use SSL/TLS in nfv kubernetes client Thanks Ran -------------- next part -------------- An HTML attachment was scrubbed... URL: From elio.martinez.monroy at intel.com Thu Sep 13 14:51:11 2018 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Thu, 13 Sep 2018 14:51:11 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD1ED56DE5@FMSMSX109.amr.corp.intel.com> Will try to have it today! Thanks -----Original Message----- From: Xie, Cindy Sent: Thursday, September 13, 2018 1:44 AM To: Martinez Monroy, Elio ; McKenna, Jason ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Elio, We will provide you an updated ISO later today with the following: - kernel upgrade to 3.10.0-862.11.6 - symbol issue fixed: https://bugs.launchpad.net/starlingx/+bug/1792257 Please help to do a sanity test based on this new ISO from Shuicheng on VE. @Jason, Please re-generate a build using today's manifest with above fix. Shuicheng shall be able to provide manifest with exact commitID. @Numan, please abort your current testing w/ old ISO once you get a new one from Jason and continue your sanity and regression on bare-metal. I am not sure how long it takes, but please take priority as we want merge back to mainline early next week. Thanks all for the support. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 4:24 AM To: Lin, Shuicheng ; Cordoba Malibran, Erich ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io; Liu, ZhipengS ; Khalil, Ghada ; Xie, Cindy Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > -----Original Message----- > From: Lin, Shuicheng > Sent: September 11, 2018 8:44 PM > To: McKenna, Jason ; Cordoba Malibran, > Erich ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Jason, > Here is the dhcp src rpm we are using: > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source dhcp > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5- > 68.el7.centos.1.src.rpm > > For centos-release, there are two packages in the mirror lst, 1 src > rpm for build, and 1 rpm for the mock environment. And it has the > "slightly difference" in the names as you mentioned. > Both of them could be found in the centos repo with the exact name. > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > centos- release-7-5.1804.1.el7.centos > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > release-7-5.1804.1.el7.centos.src.rpm > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > centos-release-7- > 5.1804.el7.centos.x86_64 > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > release-7-5.1804.el7.centos.x86_64.rpm > > If there is still some other rpm missing, you could try to find them > from the repo. > I have try my best to keep my local mirror the same as the lst. But it > is still possible some package missed to be added to the repo lst. > Please feel free to notify me or correct the error directly. > Thanks. With the latest commits to stx-tools I am now able to download the rpms and produce a build. I'll let you know how testing goes > > Best Regards > Shuicheng > > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Wednesday, September 12, 2018 12:21 AM > To: Cordoba Malibran, Erich ; > Waheed, Numan ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Lin, Shuicheng > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Cindy, > > With the latest centos75 branch (and the cherry-picks you mentioned) I > am unable to produce a build. There seems to be several source rpm > files missing from the currently pushed version of the .lst files (or > the .lst files pull down the wrong version). Most of the missing > files I can download manually, however the checked in patches for dhcp > and centos-release packages do not apply against the version of the > source RPM which I can manually find on the Internet. For example, > the version of centos-release called out in the .lst is > centos-release-7-5.1804.el7.centos.x86_64.rpm, the version called out > in the checked in code base is the slightly different > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches checked in do not apply against either package. > > Until the centos75 branch of the lst files pulls down the correct > rpms, I will be unable to continue the validation effort. > > -J > > > -----Original Message----- > > From: Cordoba Malibran, Erich > > Sent: September 11, 2018 11:17 AM > > To: Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; McKenna, Jason > > ; Xie, Cindy > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > more detailed output of the crash (if any) > > > > -Erich > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > Shuicheng saw the symbol table error issue as well but it recovers > > > in 8s, he is still working on debugging it. But 601204 is just > > > kernel upgrade but not intended to solve this issues. Are you > > > running bare metal? I am wondering if this is HW config and driver issue. > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > Thx. - cindy > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > To: Xie, Cindy ; Rasa, Nimalini > > > ; Waheed, Numan > > > ; Lin, Shuicheng > > > ; Liu, ZhipengS > > l.com>; Khalil, Ghada ; > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Cindy, > > > > > > We got past the installation device error, but are coming up > > > against the symbol table error. Our system hangs after this > > > message. I suspect a kernel issue. I see there is an open code > > > review to refactor some kernel patches to a rebased kernel > > > (https://review.open > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > resolve the issue > > > > > > -J > > > > > > From: Xie, Cindy > > > Sent: September 11, 2018 9:32 AM > > > To: Rasa, Nimalini ; Waheed, Numan > > > > n.Waheed at windriver.com>; Lin, Shuicheng ; > > > McKenna, Jason ; Liu, ZhipengS > > > > .liu at intel.com>; Khalil, Ghada ; > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > But as Jason reported yesterday, the build cannot be installed > > > with error messages: > > > > > > Installation failed. > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > We cannot debug without more information, the ISO installs in > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > manifest in this email thread. Did WindRiver has a chance to > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > Thx. - cindy > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > To: Xie, Cindy ; Waheed, Numan > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > Jason ; Liu, ZhipengS > > > > > ; Khalil, Ghada ; > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > This is on the same build (yesterday’s build). > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, Jason; > > > Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Is this the same issue as yesterday’s build? or this is different > > > issue now? > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > To: Waheed, Numan ; Lin, Shuicheng > > > > heng.lin at intel.com>; McKenna, Jason > ; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; > > > 'starlingx-discuss at lists.starlingx.io' > > uss at lists.starlingx.io>; Xie, Cindy > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > It is not booting in my case. After the following , it just hangs > > > there: > > > “Error: no symbol table. > > > Press any key to continue…” > > > > > > -Nimalini > > > > > > From: Waheed, Numan > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; Rasa, > > > Nimalini > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Adding Nimalini > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: September-11-18 2:17 AM > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, Numan > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > Just finished deploy image with latest code, I could config > > > controller successfully in bare metal environment. > > > Manifest is created for you reference. There are two patches I add > > > manually: > > > https://review.openstack.org/596855           for python-horizon > > > from master > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > There is an issue found when reboot controller node. > > > After the OS selection menu, it will show below error. And it will > > > auto continue boot after around 8 seconds. I will check the issue > > > later. > > > “ > > > Error: no symbol table. > > > Press any key to continue… > > > “ > > > > > > Best Regards > > > Shuicheng > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > To: McKenna, Jason ; Liu, ZhipengS > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > indriver.com> > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > I just tried my last Friday’s image at bare metal machine. There > > > is no issue to install controller node. > > > Will you help check what cause the install error in your environment? > > > > > > I am syncing my code to latest to double confirm it. > > > > > > Best Regards > > > Shuicheng > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > ; Khalil, Ghada > > > ; 'starlin > > > gx-discuss at lists.starlingx.io' > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > iver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Status update. The build from the centos75 branch does not > > > install on our hardware. The error message we are seeing is: > > > > > > Installation failed. > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > -Jason > > > > > > From: Liu, ZhipengS > > > Sent: September 8, 2018 9:56 AM > > > To: Lin, Shuicheng ; McKenna, Jason > > > ; Khalil, Ghada > > > ; 's > > > tarlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > @windriver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > > > > I have fixed the issue you mentioned below. > > > - Furthermore, the tpm2-tools package was requesting version > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > > hacked the spec file for tpm2-tools and rebuilt it to require the > > > version mentioned, but there is some rework to be done there. > > > [slin14]: I have the same issue also. Let’s further check it to > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > it without any code. > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > Thanks! > > > Zhipeng > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: 2018年9月8日 21:14 > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > https://review.openstack.org/#/c/598388/ > > > > > > It is due to my local version is not the latest one. > > > Sorry for the trouble caused, and thanks for your test. > > > > > > Best Regards > > > Shuicheng > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Saturday, September 8, 2018 9:23 AM > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Jason, > > > Thanks very much for such detail feedback. > > > I added some comments inline, and will check the issue in my > > > environment also. > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > Best Regards > > > Shuicheng > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Saturday, September 8, 2018 3:47 AM > > > To: McKenna, Jason ; Khalil, Ghada > > > > a.Khalil at windriver.com>; Lin, Shuicheng ; > > > 's tarlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > @windriver.com> > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > Hi Shuicheng, > > > > > > I’ve completed a build of the code. We have not yet run run-time > > > tests, but here are the build-time issues I encountered: > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > longer available for download, and the download_mirrors.sh step fails. > > > It appears than CentOS has updated to lighttpd-1.4.50. I manually > > > built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > code still references 1.4.45 > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > expirer-cron-script.patch -- In the new version, on line 190, the > > > patch states that the old code covered 6 lines, and the new code > > > covers 9 lines (-283,6 +286,9). But there are only two lines > > > inserted by the patch. There is also a new blank line in the > > > patch at line 194. Removing this blank line and editing the hunk > > > description to only insert 2 lines resolves the issue for this > > > hunk (there are other similar issues in this patch, and in > > > 0001-meta- > > > modify-aodh-api.patch) > > > [slin14]: Let me double check it. > > > - At binary build time, I had build failures on python-django- > > > horizon and some magnum packages. I had to pull in > > > https://review.op > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > centos75 branch of stx-upstream) to get past this. > > > [slin14]: It is due to I have not synced latest master code, so I > > > don’t have this issue. I used last week’s master code. > > > - After building all packages, I attempted to build the ISO. > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > should be added to the .lst files. > > > [slin14]: This package is already in the lst. > > > - Furthermore, the tpm2-tools package was requesting version > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). I > > > hacked the spec file for tpm2-tools and rebuilt it to require the > > > version mentioned, but there is some rework to be done there. > > > [slin14]: I have the same issue also. Let’s further check it to > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > it without any code. > > > > > > After these changes, I was able to produce a .iso > > > > > > -Jason > > > > > > From: McKenna, Jason > > > Sent: September 7, 2018 10:08 AM > > > To: Khalil, Ghada ; Lin, Shuicheng > > > ; 'starlingx-discuss at lists.starlingx.io' > > > ; Xie, Cindy > > > ; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi Shuicheng, > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > been changed from 1.4.45 to 1.4.49. The > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > -Jason > > > > > > From: Khalil, Ghada > > > Sent: September 7, 2018 9:36 AM > > > To: Lin, Shuicheng ; > > > 'starlingx-discuss at list s.starlingx.io' > > > ; Xie, Cindy > > indy.xie at intel.com>; Waheed, Numan > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > be priming this activity. He’ll share the results with the team > > > sometime next week. > > > > > > Regards, > > > Ghada > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > Sent: Friday, September 07, 2018 1:32 AM > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > Cindy > > > Subject: CentOS 7.5 upgrade status update > > > > > > Hi all, > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please go > > > ahead to have a try and verify it. > > > I expect there should be some issue due to we just did limited > > > deploy test yet. > > > > > > Here is the detail status update of this week. > > > For the total 44 srpm we plan to upgrade: > > > 38 already merged in feature branch. > > > 3 kept as original version. Anaconda upgrade is not needed. > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > due to new src rpm itself have known issue. > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > 1 under debug. Lighttpd. > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > Here is the build instruction: > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > upstream/stx-root. > > > Cherry-pick below un-merged patch: > > > For puppet-haproxy: > > > https://review.openstack.org/600369 > > > https://review.openstack.org/600359 > > > For openstack-aodh: > > > https://review.openstack.org/598388 > > > https://review.openstack.org/600591 > > > For build-iso: > > > https://review.openstack.org/599892 > > > For build-pkgs: > > > https://review.openstack.org/599901 > > > https://review.openstack.org/600639 > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > rpm. > > > 3. Try to build packages and ISO. > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > Feel free to contact me if you have trouble on it. > > > > > > Best Regards > > > Shuicheng > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discu > > > ss From erich.cordoba.malibran at intel.com Thu Sep 13 18:46:25 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 13 Sep 2018 18:46:25 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA3A91AD@ALA-MBD.corp.ad.wrs.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503768@fmsmsx104.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503931@fmsmsx104.amr.corp.intel.com> <8e1b97a9bee74d40e2cc5802d62c95f8659006ec.camel@intel.com> <15C75A68-7BE3-480B-85E9-A8642238B7FD@windriver.com> <6EEDEF7D-AFE8-4E59-8CF0-1B0D6A3DD800@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3A91AD@ALA-MBD.corp.ad.wrs.com> Message-ID: <4d0c64940fea4c1ad13151e616a537266b6ffa5c.camel@intel.com> Indeed, those two files had the 600 permissions in our mirror and the permissions were transfered into the ISO and then to the /ww/pages/feed folder. Changing the permissions now let the compute to be installed. I have two questions regarding this: - Which component is responsible to populate the /www/pages/feed folder with the rpms. I'm wondering if some permission checking/set needs to be done here. - lighttpd runs as non-root user, but the content on /www/pages/feed is owned by root. Should this folder be owned by the same user as the one that runs lighttpd? Thanks -Erich On Wed, 2018-09-12 at 21:37 +0000, Penney, Don wrote: > The problem is one of permissions. In the /www/var/log/lighttpd- > access.log file, you can see the http access request is being > rejected with a 403 status code, indicating access is forbidden: > > 192.168.204.85 pxecontroller - [12/Sep/2018:09:30:52 +0000] "GET > /feed/rel-18.08/Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm > HTTP/1.1" 403 345 "-" "urlgrabber/3.10 yum/3.4.3" > > You can see this also with a wget command: > localhost:/home/wrsroot# wget http://localhost/feed/rel-18.08/Package > s/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm > --2018-09-12 20:54:19-- http://localhost/feed/rel-18.08/Packages/pyt > hon2-qpid-proton-0.24.0-1.el7.x86_64.rpm > Resolving localhost (localhost)... ::1, 127.0.0.1 > Connecting to localhost (localhost)|::1|:80... connected. > HTTP request sent, awaiting response... 403 Forbidden > 2018-09-12 20:54:19 ERROR 403: Forbidden. > > > The problem is that two of the RPMs on the ISO have 600 permissions, > where all other RPMs are 644. This is carried over when the files are > copied to the controller during the post-install phase: > > controller-0:~$ ls -l /mnt/iso/Packages/ | grep -- --- > -rw------- 1 1001 users 258624 Aug 28 12:04 python2-qpid-proton- > 0.24.0-1.el7.x86_64.rpm > -rw------- 1 1001 users 190128 Aug 28 12:04 qpid-proton-c-0.24.0- > 1.el7.x86_64.rpm > > controller-0:~$ ls -l /www/pages/feed/rel-18.08/Packages/ |grep -- -- > - > -rw-------. 1 root root 258624 Sep 12 20:33 python2-qpid-proton- > 0.24.0-1.el7.x86_64.rpm > -rw-------. 1 root root 190128 Sep 12 20:33 qpid-proton-c-0.24.0- > 1.el7.x86_64.rpm > > > The lighttpd server runs as a non-root user, and cannot access these > files. Change the permissions on the files, and the installation of > controller-1 should be successful. > > > -----Original Message----- > From: Young, Ken [mailto:Ken.Young at windriver.com] > Sent: Wednesday, September 12, 2018 4:53 PM > To: Cordoba Malibran, Erich > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > posted > > Erich, > > One correction below: we are using a Wind River version of the > installer (I am confusing this thread with another thread). This is > the installer we shipped Titanium Cloud Release 5. > > This begs the question: what installer were you using before the > changes to the kernel? > > /KenY > > On 2018-09-12, 4:36 PM, "Young, Ken" > wrote: > > Erich, > > A couple of data points on our side. For our builds, we are > using stock CentOS installer for 7.4. These are unchanged and we > have not seen this issue on our side. > > Have you isolated when you made the changes to the installer? Is > it the same time you started seeing this error? Does it make sense > to revert to the stock installer while we get to the bottom of this > issue to continue sanity? > > Regards, > Ken Y > > On 2018-09-11, 8:30 PM, "Cordoba Malibran, Erich" malibran at intel.com> wrote: > > I have narrowed down a little bit the issue, these are my > findings. > > - I compared the bootimage_michel.iso with the stx-2018-09- > 11- > 111.iso, which is today's ISO. > - The are not significant package differences between them, > minor > versions has changed in some packages. > - The issue is that once the kernel has been loaded through > PXE, > anaconda is unable to find python2-qpid package. Not sure if > this is > the first package that is requested. > - From the anaconda shell I can see the http://pxecontrolle > r/ serving > the files and the repodata seems to be updated there. I > installed yum > manually and I was able to install python2-qpid package, (and > any other > available). > - The content of the pxe-network-installer package is not > the same, > WR squashfs.img file has the kernel 3.10.0-693.2.2 but ours > has 3.10.0- > 862.6.3. We regenerate those files when the kernel was > upgraded. (maybe > this matches with the date where the issue started to > arise..) > > So, my guess now is that the problem could be caused by the > pxe- > network-installer package. We create those files with the > update- > network-installer script. That's the same used in WR to > generate these > files? > > I'll keep diging in the generation of these files to see if > there is > any problem. > > -Erich > > On Tue, 2018-09-11 at 20:03 +0000, Lara, Cesar wrote: > > I just wanted to make sure that we are able to reproduce > the issue > > regardless of the build environment. > > > > AFAIK CentOS 7.5 upgrade is a different issue/thread, but > at the end > > we can fine tune a process in which we are in the same > conditions to > > be able to replicate errors in any given build > environment. > > > > Regards > > Cesar Lara > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Tuesday, September 11, 2018 2:02 PM > > To: Lara, Cesar ; Alonso, Juan Carlos > > los.alonso at intel.com>; Khalil, Ghada r.com>; > > Martinez Monroy, Elio ; > Jones, Bruce > > E ; Cabrales, Ada tel.com>; > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > @windriver.com>; Young, Ken ; > Little, Scott > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > Hi Cesar, > > > > Would you elaborate on what differences you'd expect to see > in an > > empty mirror populated by the download tool, compared to an > existing > > mirror which was updated by the download tool? > > > > The mirror tools were written specifically to contain > multiple > > versions of packages. The build environment population > tools take > > the .lst file you have checked out, and places that version > from the > > mirror into your local environment guaranteeing that your > build env > > matches the .lst file. If your mirror contains versions > 1.0.0, > > 1.2.3, and 2.0.0 of a given package, then your environment > will only > > use the version called out in the .lst file you have > checked out. > > > > This allows the same mirror to be used for multiple > branches, for > > multiple releases, for multiple development environments, > etc, and > > guarantees that a build can be reproduced down the road > even if the > > build inputs disappear from the Internet at some point in > the > > future. As long as all the artifacts named in the .lst > file have > > been downloaded at some point in the past, the build > environment > > produced from a fresh mirror vs a continually updated > mirror will be > > identical. > > > > The issue we are observing with the CentOS 7.5 update is > that the > > versions of packages called out in the .lst files for the > centos75 > > branch of stx-tools do not match the versions of packages > called out > > in centos75 branch of the other repos, like stx-integ. The > other > > branches are attempting to patch a (new) version of the > source code, > > but the .lst file is only bringing in (or downloading) and > older > > version of the source. > > > > -Jason > > > > > -----Original Message----- > > > From: Lara, Cesar > > > Sent: September 11, 2018 1:44 PM > > > To: Alonso, Juan Carlos ; > Khalil, > > > Ghada > > > ; Martinez Monroy, Elio > > > ; Jones, Bruce E > > > ; Cabrales, Ada tel.com>; > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > - summary > > > posted > > > > > > Hi all, > > > > > > Just wanted to point out that, to be able to reproduce > the issues > > > from > > > Intel's ISO, somebody will need to go and create a build > > > environment > > > from scratch, using external upstream repositories to > generate a > > > new > > > mirror, just the way we are doing it in our environment. > Failing to > > > do > > > this will result in a apples to oranges comparison. > > > > > > Regards > > > Cesar Lara > > > > > > -----Original Message----- > > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at inte > l.com] > > > Sent: Tuesday, September 11, 2018 10:54 AM > > > To: Khalil, Ghada ; Martinez > Monroy, > > > Elio > > > ; Jones, Bruce E > > > ; Cabrales, Ada tel.com>; > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > - summary > > > posted > > > > > > Hi Ghada, > > > > > > Yes, before shared our ISOs I followed such steps and got > the same > > > issues. > > > > > > As I mention in the issue > > > (https://bugs.launchpad.net/starlingx/+bug/1790213), I > could get > > > the > > > ISO from Michel and testes in our infrastructure, issues > not found. > > > I > > > guess there are differences between the way an ISO is > built by > > > Intel > > > and Wind River since Intel got issues but Wind River does > not. I > > > think we should sync about this. > > > > > > Besides, our test infrastructure uses other commands to > generate > > > VMs, > > > add/install hosts (controllers and computes), such > commands was > > > gotten > > > from "tic_vb" repo, such repo was given by China team, if > I am not > > > wrong such repo was based on Wind River documentation; > our test > > > framework is based on "tic_vb". Anyway both ways got the > same > > > results. > > > > > > Regards. > > > Juan Carlos Alonso > > > > > > -----Original Message----- > > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > > Sent: Tuesday, September 11, 2018 8:53 AM > > > To: Alonso, Juan Carlos ; > Martinez > > > Monroy, Elio ; Jones, > Bruce E > > > ; Cabrales, Ada tel.com>; > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > > > Hello Juan, > > > I read the notes in the Launchpad. > > > > > > And, just to confirm, are you following the instructions > under: > > > https://wiki.openstack.org/wiki/StarlingX/Installation_Gu > ide_Virtua > > > l_E > > > nviro > > > nment/Controller_Storage > > > and still reproducing the two issues below? > > > > > > I was not able to definitively tell from the Launchpad > notes. It's > > > important that both our teams are comparing apples to > apples. > > > > > > Thanks, > > > Ghada > > > > > > -----Original Message----- > > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at inte > l.com] > > > Sent: Monday, September 10, 2018 1:50 PM > > > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; > > > Cabrales, > > > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, > Michel > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > > > Hi, > > > > > > Such launchpads were updated. > > > > > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such > ISO > > > present > > > two issues. Michael will upload his ISO, then we will re > test > > > witch > > > each iso in our environment. > > > > > > An script is being developed to get the differences > between ISOs. > > > > > > Regards. > > > Juan Carlos Alonso > > > > > > -----Original Message----- > > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > > Sent: Friday, September 7, 2018 4:43 PM > > > To: Khalil, Ghada ; Martinez > Monroy, > > > Elio > > > ; Jones, Bruce E > > > ; Cabrales, Ada tel.com>; > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > - summary > > > posted > > > > > > Hi Elio/Ada, > > > Are there any updates from your side on these two > Launchpads? > > > https://bugs.launchpad.net/starlingx/+bug/1790213 > > > https://bugs.launchpad.net/starlingx/+bug/1790716 > > > > > > Michel Thebeau (Wind River) has been trying to reproduce > these two > > > issues (following the starlingx wikis) without success > for two > > > days > > > now. He has been adding his findings to the bugs and > communicating > > > with your team. > > > As a result of his investigation, he will be pushing some > small > > > fixes > > > to stx- tools shortly (some cleanup). > > > > > > Please let us know if you need any further help from us. > > > > > > Thanks, > > > Ghada > > > > > > -----Original Message----- > > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > > Sent: Wednesday, September 05, 2018 5:39 PM > > > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > > > starlingx- > > > discuss at lists.starlingx.io > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > - summary > > > posted > > > > > > Please see inline. There are notes in all the launchpads > as well. > > > > > > I have tagged the last bug for the October release. The > rest need > > > more > > > information to determine whether they gate or not: two > maybe > > > procedural and one requires more information. > > > > > > -----Original Message----- > > > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy@ > intel.com] > > > Sent: Wednesday, September 05, 2018 2:23 PM > > > To: Jones, Bruce E; Cabrales, Ada; > > > starlingx-discuss at lists.starlingx.io > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > - summary > > > posted > > > > > > My opinion below > > > > > > -----Original Message----- > > > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > > > Sent: Wednesday, September 5, 2018 12:56 PM > > > To: Cabrales, Ada ; starlingx- > > > discuss at lists.starlingx.io > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > - summary > > > posted > > > > > > Should the bugs coming out of this be tagged/fixed for > the October > > > release? > > > > > > Related bugs: > > > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- > Must, this > > > bug > > > is related with 2nd controller provisioning [[GK]] Using > the > > > instructions published on the wiki, our designer was not > able to > > > reproduce this issue. > > > What instructions are the test team using? > > > > > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- > Can wait > > > until > > > other issues are solved, will fail some test cases > related to SSH > > > [[GK]] Requested more information. This cannot be > debugged further > > > without this information. > > > > > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- > Must, all > > > instances need at least one compute for multimode [[GK]] > Using the > > > instructions published on the wiki, our designer was not > able to > > > reproduce this issue. The test team points to internal > > > instructions > > > which we have no access to. The supported install recipes > need to > > > be > > > on the wiki. I think it is an invalid bug > > > > > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- > Can wait > > > since > > > is related to FM , test cases will fail [[GK]] As Brent > pointed > > > out, > > > this is dependent on the integration of stx-gui which is > in > > > progress. > > > > > > -----Original Message----- > > > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > > > Sent: Wednesday, September 5, 2018 10:50 AM > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: [Starlingx-discuss] [ Test ] Sanity results - > summary > > > posted > > > > > > Hello all, > > > > > > As mentioned on the project meeting today, we're > posting the > > > summary of the sanity test runs on the Test wiki [0]. The > sanity > > > is > > > triggered each time an ISO is generated (a daily task). > > > > > > Right now we are posting the results manually, and > working on a > > > way > > > for automating it. Logs of the run are not included, if > you want > > > to > > > have them, you can contact Elio to get them sent to you. > > > > > > > > > [0] > > > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO > _image_San > > > ity > > > _S > > > ummary > > > > > > Regards > > > Ada > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > ngx-discus > > > s > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > ngx-discus > > > s > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > ngx-discus > > > s > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > ngx-discus > > > s > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > ngx-discus > > > s > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > ngx-discus > > > s > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > ngx-discus > > > s > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starling > x-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > uss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Teresa.Ho at windriver.com Thu Sep 13 19:30:25 2018 From: Teresa.Ho at windriver.com (Ho, Teresa) Date: Thu, 13 Sep 2018 19:30:25 +0000 Subject: [Starlingx-discuss] interface and network configuration changes are merged Message-ID: <918130236148D14B982C7B8BC1C06EA16710D130@ALA-MBD.corp.ad.wrs.com> The commits for the Story https://storyboard.openstack.org/#!/story/2003087 have been merged. Teresa Ho From: Ho, Teresa Sent: Sunday, September 09, 2018 11:31 PM To: starlingx-discuss at lists.starlingx.io Subject: Heads up: interface and network configuration changes This is to inform you that the upcoming feature story "Generalized interface and network configuration" will impact system setup. A review will be posted shortly. For more background information, please refer to the Story: https://storyboard.openstack.org/#!/story/2003087 The following describes the user interface changes for interface and network configuration. * Network CLI commands * The parameters mtu, link_capacity and vlan_id are removed from the network table * New network-add and network-delete usage: system network-add Add a network. Positional arguments: Name of network [REQUIRED] Type of network [REQUIRED] dynamic [REQUIRED] The uuid of the address pool [REQUIRED] usage: system network-delete Delete a network Positional arguments: UUID of network entry * Interface CLI commands * The new interface class parameter replaces the existing networktype parameter. usage: system host-if-add [-a ] [-x ] [-V ] [-m ] [-c ] [--networks ] [--ipv4-mode ] [--ipv6-mode ] [--ipv4-pool ] [--ipv6-pool ] [] [] [ ...] Add an interface. Positional arguments: Name or ID of host [REQUIRED] Name of interface [REQUIRED] Type of the interface The provider network attached to the interface (default: None) [REQUIRED when interface class is data or pci-passthrough Name of port(s) or interface(s) [REQUIRED] Optional arguments: -a , --aemode The AE mode (balanced or active_standby or 802.3ad) -x , --txhashpolicy The balanced tx distribution hash policy -V , --vlan_id The VLAN id of the interface -m , --imtu The MTU of the interface -c , --ifclass The class of the interface --networks Name or ID of network --ipv4-mode The IPv4 address mode of the interface --ipv6-mode The IPv6 address mode of the interface --ipv4-pool The IPv4 address pool name or uuid if mode is set to 'pool' --ipv6-pool The IPv6 address pool name or uuid if mode is set to 'pool' usage: system host-if-modify [-n ] [-m ] [-p ] [-a ] [-x ] [-c ] [--networks ] [--ipv4-mode ] [--ipv6-mode ] [--ipv4-pool ] [--ipv6-pool ] [-N ] Modify interface attributes. Positional arguments: Name or ID of host [REQUIRED] Name or UUID of interface [REQUIRED] Optional arguments: -n , --ifname The new name of the interface -m , --imtu The MTU of the interface -p , --providernetworks The provider network attached to the interface [REQUIRED] -a , --aemode The AE mode (balanced or active_standby or 802.3ad) -x , --txhashpolicy The balanced tx distribution hash policy -c , --ifclass The class of the interface --networks Name or ID of network --ipv4-mode The IPv4 address mode of the interface --ipv6-mode The IPv6 address mode of the interface --ipv4-pool The IPv4 address pool name or uuid if mode is set to 'pool' --ipv6-pool The IPv6 address pool name or uuid if mode is set to 'pool' -N , --num-vfs The number of SR-IOV VFs of the interface * Interface network associations Multiple networks can be assigned to an interface. usage: system interface-network-assign Assign a network to an interface. Positional arguments: Name or ID of host [REQUIRED] Name of interface [REQUIRED] Name of UUID of IP network [REQUIRED] usage: system interface-network-remove Remove an assigned network from an interface. Positional arguments: UUID of interface network entry Teresa Ho -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jason.McKenna at windriver.com Thu Sep 13 19:50:16 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Thu, 13 Sep 2018 19:50:16 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: <4d0c64940fea4c1ad13151e616a537266b6ffa5c.camel@intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503768@fmsmsx104.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503931@fmsmsx104.amr.corp.intel.com> <8e1b97a9bee74d40e2cc5802d62c95f8659006ec.camel@intel.com> <15C75A68-7BE3-480B-85E9-A8642238B7FD@windriver.com> <6EEDEF7D-AFE8-4E59-8CF0-1B0D6A3DD800@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3A91AD@ALA-MBD.corp.ad.wrs.com> <4d0c64940fea4c1ad13151e616a537266b6ffa5c.camel@intel.com> Message-ID: > -----Original Message----- > From: Cordoba Malibran, Erich > Sent: September 13, 2018 2:46 PM > To: Young, Ken ; Penney, Don > > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Indeed, those two files had the 600 permissions in our mirror and the > permissions were transfered into the ISO and then to the /ww/pages/feed > folder. Changing the permissions now let the compute to be installed. > > I have two questions regarding this: > > - Which component is responsible to populate the /www/pages/feed folder > with the rpms. I'm wondering if some permission checking/set needs to be > done here. +1 > - lighttpd runs as non-root user, but the content on /www/pages/feed is > owned by root. Should this folder be owned by the same user as the one > that runs lighttpd? The data needs to be readable by the user running lighttpd, but its okay if it's owned by someone else (including root) > > Thanks > > -Erich > > On Wed, 2018-09-12 at 21:37 +0000, Penney, Don wrote: > > The problem is one of permissions. In the /www/var/log/lighttpd- > > access.log file, you can see the http access request is being rejected > > with a 403 status code, indicating access is forbidden: > > > > 192.168.204.85 pxecontroller - [12/Sep/2018:09:30:52 +0000] "GET > > /feed/rel-18.08/Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm > > HTTP/1.1" 403 345 "-" "urlgrabber/3.10 yum/3.4.3" > > > > You can see this also with a wget command: > > localhost:/home/wrsroot# wget http://localhost/feed/rel-18.08/Package > > s/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm > > --2018-09-12 20:54:19-- http://localhost/feed/rel-18.08/Packages/pyt > > hon2-qpid-proton-0.24.0-1.el7.x86_64.rpm > > Resolving localhost (localhost)... ::1, 127.0.0.1 Connecting to > > localhost (localhost)|::1|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2018-09-12 20:54:19 ERROR 403: Forbidden. > > > > > > The problem is that two of the RPMs on the ISO have 600 permissions, > > where all other RPMs are 644. This is carried over when the files are > > copied to the controller during the post-install phase: > > > > controller-0:~$ ls -l /mnt/iso/Packages/ | grep -- --- > > -rw------- 1 1001 users 258624 Aug 28 12:04 python2-qpid-proton- > > 0.24.0-1.el7.x86_64.rpm > > -rw------- 1 1001 users 190128 Aug 28 12:04 qpid-proton-c-0.24.0- > > 1.el7.x86_64.rpm > > > > controller-0:~$ ls -l /www/pages/feed/rel-18.08/Packages/ |grep -- -- > > - > > -rw-------. 1 root root 258624 Sep 12 20:33 python2-qpid-proton- > > 0.24.0-1.el7.x86_64.rpm > > -rw-------. 1 root root 190128 Sep 12 20:33 qpid-proton-c-0.24.0- > > 1.el7.x86_64.rpm > > > > > > The lighttpd server runs as a non-root user, and cannot access these > > files. Change the permissions on the files, and the installation of > > controller-1 should be successful. > > > > > > -----Original Message----- > > From: Young, Ken [mailto:Ken.Young at windriver.com] > > Sent: Wednesday, September 12, 2018 4:53 PM > > To: Cordoba Malibran, Erich > > Cc: starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Erich, > > > > One correction below: we are using a Wind River version of the > > installer (I am confusing this thread with another thread). This is > > the installer we shipped Titanium Cloud Release 5. > > > > This begs the question: what installer were you using before the > > changes to the kernel? > > > > /KenY > > > > On 2018-09-12, 4:36 PM, "Young, Ken" > > wrote: > > > > Erich, > > > > A couple of data points on our side. For our builds, we are using > > stock CentOS installer for 7.4. These are unchanged and we have not > > seen this issue on our side. > > > > Have you isolated when you made the changes to the installer? Is > > it the same time you started seeing this error? Does it make sense to > > revert to the stock installer while we get to the bottom of this issue > > to continue sanity? > > > > Regards, > > Ken Y > > > > On 2018-09-11, 8:30 PM, "Cordoba Malibran, Erich" > malibran at intel.com> wrote: > > > > I have narrowed down a little bit the issue, these are my > > findings. > > > > - I compared the bootimage_michel.iso with the stx-2018-09- > > 11- > > 111.iso, which is today's ISO. > > - The are not significant package differences between them, > > minor > > versions has changed in some packages. > > - The issue is that once the kernel has been loaded through > > PXE, > > anaconda is unable to find python2-qpid package. Not sure if > > this is > > the first package that is requested. > > - From the anaconda shell I can see the http://pxecontrolle > > r/ serving > > the files and the repodata seems to be updated there. I > > installed yum > > manually and I was able to install python2-qpid package, (and > > any other > > available). > > - The content of the pxe-network-installer package is not > > the same, > > WR squashfs.img file has the kernel 3.10.0-693.2.2 but ours > > has 3.10.0- > > 862.6.3. We regenerate those files when the kernel was > > upgraded. (maybe > > this matches with the date where the issue started to > > arise..) > > > > So, my guess now is that the problem could be caused by the > > pxe- > > network-installer package. We create those files with the > > update- > > network-installer script. That's the same used in WR to > > generate these > > files? > > > > I'll keep diging in the generation of these files to see if > > there is > > any problem. > > > > -Erich > > > > On Tue, 2018-09-11 at 20:03 +0000, Lara, Cesar wrote: > > > I just wanted to make sure that we are able to reproduce the > > issue > > > regardless of the build environment. > > > > > > AFAIK CentOS 7.5 upgrade is a different issue/thread, but at > > the end > > > we can fine tune a process in which we are in the same > > conditions to > > > be able to replicate errors in any given build environment. > > > > > > Regards > > > Cesar Lara > > > > > > > > > -----Original Message----- > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Tuesday, September 11, 2018 2:02 PM > > > To: Lara, Cesar ; Alonso, Juan Carlos > > > > los.alonso at intel.com>; Khalil, Ghada > r.com>; > > > Martinez Monroy, Elio ; > > Jones, Bruce > > > E ; Cabrales, Ada > tel.com>; > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > @windriver.com>; Young, Ken ; > > Little, Scott > > > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > > > Hi Cesar, > > > > > > Would you elaborate on what differences you'd expect to see > > in an > > > empty mirror populated by the download tool, compared to an > > existing > > > mirror which was updated by the download tool? > > > > > > The mirror tools were written specifically to contain > > multiple > > > versions of packages. The build environment population > > tools take > > > the .lst file you have checked out, and places that version > > from the > > > mirror into your local environment guaranteeing that your > > build env > > > matches the .lst file. If your mirror contains versions > > 1.0.0, > > > 1.2.3, and 2.0.0 of a given package, then your environment > > will only > > > use the version called out in the .lst file you have checked > > out. > > > > > > This allows the same mirror to be used for multiple > > branches, for > > > multiple releases, for multiple development environments, > > etc, and > > > guarantees that a build can be reproduced down the road even > > if the > > > build inputs disappear from the Internet at some point in > > the > > > future. As long as all the artifacts named in the .lst file > > have > > > been downloaded at some point in the past, the build > > environment > > > produced from a fresh mirror vs a continually updated mirror > > will be > > > identical. > > > > > > The issue we are observing with the CentOS 7.5 update is > > that the > > > versions of packages called out in the .lst files for the > > centos75 > > > branch of stx-tools do not match the versions of packages > > called out > > > in centos75 branch of the other repos, like stx-integ. The > > other > > > branches are attempting to patch a (new) version of the > > source code, > > > but the .lst file is only bringing in (or downloading) and > > older > > > version of the source. > > > > > > -Jason > > > > > > > -----Original Message----- > > > > From: Lara, Cesar > > > > Sent: September 11, 2018 1:44 PM > > > > To: Alonso, Juan Carlos ; > > Khalil, > > > > Ghada > > > > ; Martinez Monroy, Elio > > > > ; Jones, Bruce E > > > > ; Cabrales, Ada > tel.com>; > > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > Hi all, > > > > > > > > Just wanted to point out that, to be able to reproduce the > > issues > > > > from > > > > Intel's ISO, somebody will need to go and create a build > > > > environment > > > > from scratch, using external upstream repositories to > > generate a > > > > new > > > > mirror, just the way we are doing it in our environment. > > Failing to > > > > do > > > > this will result in a apples to oranges comparison. > > > > > > > > Regards > > > > Cesar Lara > > > > > > > > -----Original Message----- > > > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at inte > > l.com] > > > > Sent: Tuesday, September 11, 2018 10:54 AM > > > > To: Khalil, Ghada ; Martinez > > Monroy, > > > > Elio > > > > ; Jones, Bruce E > > > > ; Cabrales, Ada > tel.com>; > > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > Hi Ghada, > > > > > > > > Yes, before shared our ISOs I followed such steps and got > > the same > > > > issues. > > > > > > > > As I mention in the issue > > > > (https://bugs.launchpad.net/starlingx/+bug/1790213), I > > could get > > > > the > > > > ISO from Michel and testes in our infrastructure, issues > > not found. > > > > I > > > > guess there are differences between the way an ISO is > > built by > > > > Intel > > > > and Wind River since Intel got issues but Wind River does > > not. I > > > > think we should sync about this. > > > > > > > > Besides, our test infrastructure uses other commands to > > generate > > > > VMs, > > > > add/install hosts (controllers and computes), such > > commands was > > > > gotten > > > > from "tic_vb" repo, such repo was given by China team, if > > I am not > > > > wrong such repo was based on Wind River documentation; our > > test > > > > framework is based on "tic_vb". Anyway both ways got the > > same > > > > results. > > > > > > > > Regards. > > > > Juan Carlos Alonso > > > > > > > > -----Original Message----- > > > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > > > Sent: Tuesday, September 11, 2018 8:53 AM > > > > To: Alonso, Juan Carlos ; > > Martinez > > > > Monroy, Elio ; Jones, > > Bruce E > > > > ; Cabrales, Ada > tel.com>; > > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > > > > > Hello Juan, > > > > I read the notes in the Launchpad. > > > > > > > > And, just to confirm, are you following the instructions > > under: > > > > https://wiki.openstack.org/wiki/StarlingX/Installation_Gu > > ide_Virtua > > > > l_E > > > > nviro > > > > nment/Controller_Storage > > > > and still reproducing the two issues below? > > > > > > > > I was not able to definitively tell from the Launchpad > > notes. It's > > > > important that both our teams are comparing apples to > > apples. > > > > > > > > Thanks, > > > > Ghada > > > > > > > > -----Original Message----- > > > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at inte > > l.com] > > > > Sent: Monday, September 10, 2018 1:50 PM > > > > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; > > > > Cabrales, > > > > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > > > > > Hi, > > > > > > > > Such launchpads were updated. > > > > > > > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such > > ISO > > > > present > > > > two issues. Michael will upload his ISO, then we will re > > test > > > > witch > > > > each iso in our environment. > > > > > > > > An script is being developed to get the differences > > between ISOs. > > > > > > > > Regards. > > > > Juan Carlos Alonso > > > > > > > > -----Original Message----- > > > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > > > Sent: Friday, September 7, 2018 4:43 PM > > > > To: Khalil, Ghada ; Martinez > > Monroy, > > > > Elio > > > > ; Jones, Bruce E > > > > ; Cabrales, Ada > tel.com>; > > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > Hi Elio/Ada, > > > > Are there any updates from your side on these two > > Launchpads? > > > > https://bugs.launchpad.net/starlingx/+bug/1790213 > > > > https://bugs.launchpad.net/starlingx/+bug/1790716 > > > > > > > > Michel Thebeau (Wind River) has been trying to reproduce > > these two > > > > issues (following the starlingx wikis) without success for > > two > > > > days > > > > now. He has been adding his findings to the bugs and > > communicating > > > > with your team. > > > > As a result of his investigation, he will be pushing some > > small > > > > fixes > > > > to stx- tools shortly (some cleanup). > > > > > > > > Please let us know if you need any further help from us. > > > > > > > > Thanks, > > > > Ghada > > > > > > > > -----Original Message----- > > > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > > > Sent: Wednesday, September 05, 2018 5:39 PM > > > > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > > > > starlingx- > > > > discuss at lists.starlingx.io > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > Please see inline. There are notes in all the launchpads > > as well. > > > > > > > > I have tagged the last bug for the October release. The > > rest need > > > > more > > > > information to determine whether they gate or not: two > > maybe > > > > procedural and one requires more information. > > > > > > > > -----Original Message----- > > > > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy@ > > intel.com] > > > > Sent: Wednesday, September 05, 2018 2:23 PM > > > > To: Jones, Bruce E; Cabrales, Ada; > > > > starlingx-discuss at lists.starlingx.io > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > My opinion below > > > > > > > > -----Original Message----- > > > > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > > > > Sent: Wednesday, September 5, 2018 12:56 PM > > > > To: Cabrales, Ada ; starlingx- > > > > discuss at lists.starlingx.io > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > Should the bugs coming out of this be tagged/fixed for the > > October > > > > release? > > > > > > > > Related bugs: > > > > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- > > Must, this > > > > bug > > > > is related with 2nd controller provisioning [[GK]] Using > > the > > > > instructions published on the wiki, our designer was not > > able to > > > > reproduce this issue. > > > > What instructions are the test team using? > > > > > > > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- > > Can wait > > > > until > > > > other issues are solved, will fail some test cases related > > to SSH > > > > [[GK]] Requested more information. This cannot be debugged > > further > > > > without this information. > > > > > > > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- > > Must, all > > > > instances need at least one compute for multimode [[GK]] > > Using the > > > > instructions published on the wiki, our designer was not > > able to > > > > reproduce this issue. The test team points to internal > > > > instructions > > > > which we have no access to. The supported install recipes > > need to > > > > be > > > > on the wiki. I think it is an invalid bug > > > > > > > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- > > Can wait > > > > since > > > > is related to FM , test cases will fail [[GK]] As Brent > > pointed > > > > out, > > > > this is dependent on the integration of stx-gui which is > > in > > > > progress. > > > > > > > > -----Original Message----- > > > > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > > > > Sent: Wednesday, September 5, 2018 10:50 AM > > > > To: starlingx-discuss at lists.starlingx.io > > > > Subject: [Starlingx-discuss] [ Test ] Sanity results - > > summary > > > > posted > > > > > > > > Hello all, > > > > > > > > As mentioned on the project meeting today, we're > > posting the > > > > summary of the sanity test runs on the Test wiki [0]. The > > sanity > > > > is > > > > triggered each time an ISO is generated (a daily task). > > > > > > > > Right now we are posting the results manually, and > > working on a > > > > way > > > > for automating it. Logs of the run are not included, if > > you want > > > > to > > > > have them, you can contact Elio to get them sent to you. > > > > > > > > > > > > [0] > > > > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO > > _image_San > > > > ity > > > > _S > > > > ummary > > > > > > > > Regards > > > > Ada > > > > > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starling > > x-discuss > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > uss > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Thu Sep 13 23:42:34 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 13 Sep 2018 23:42:34 +0000 Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted In-Reply-To: References: <4F6AACE4B0F173488D033B02A8BB5B7E716E04D1@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB587F1D@fmsmsx115.amr.corp.intel.com> <1466AF2176E6F040BD63860D0A241BBD1ED53BDE@FMSMSX109.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA44FC2E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA450A68@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422F8AF@fmsmsx101.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45165A@ALA-MBD.corp.ad.wrs.com> <8557B550001AFB46A43A0CCC314BF8514422FD24@fmsmsx101.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503768@fmsmsx104.amr.corp.intel.com> <0B566C62EC792145B40E29EFEBF1AB4710503931@fmsmsx104.amr.corp.intel.com> <8e1b97a9bee74d40e2cc5802d62c95f8659006ec.camel@intel.com> <15C75A68-7BE3-480B-85E9-A8642238B7FD@windriver.com> <6EEDEF7D-AFE8-4E59-8CF0-1B0D6A3DD800@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3A91AD@ALA-MBD.corp.ad.wrs.com> <4d0c64940fea4c1ad13151e616a537266b6ffa5c.camel@intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3A997E@ALA-MBD.corp.ad.wrs.com> There are a couple of places where the permissions could be checked/updated. It's never been a problem before now, but could occur again as other users come on board. The build-iso tool is responsible for creating the ISO and could ensure that all files on the ISO have the necessary permissions (and probably root/root user/group for the ISO). The controller kickstarts copy or download the files to setup the repo, and could also include a permissions check. I think these files should continue to be root/root, but world-readable. Cheers, Don. -----Original Message----- From: McKenna, Jason Sent: Thursday, September 13, 2018 3:50 PM To: Cordoba Malibran, Erich; Young, Ken; Penney, Don Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [ Test ] Sanity results - summary posted > -----Original Message----- > From: Cordoba Malibran, Erich > Sent: September 13, 2018 2:46 PM > To: Young, Ken ; Penney, Don > > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted > > Indeed, those two files had the 600 permissions in our mirror and the > permissions were transfered into the ISO and then to the /ww/pages/feed > folder. Changing the permissions now let the compute to be installed. > > I have two questions regarding this: > > - Which component is responsible to populate the /www/pages/feed folder > with the rpms. I'm wondering if some permission checking/set needs to be > done here. +1 > - lighttpd runs as non-root user, but the content on /www/pages/feed is > owned by root. Should this folder be owned by the same user as the one > that runs lighttpd? The data needs to be readable by the user running lighttpd, but its okay if it's owned by someone else (including root) > > Thanks > > -Erich > > On Wed, 2018-09-12 at 21:37 +0000, Penney, Don wrote: > > The problem is one of permissions. In the /www/var/log/lighttpd- > > access.log file, you can see the http access request is being rejected > > with a 403 status code, indicating access is forbidden: > > > > 192.168.204.85 pxecontroller - [12/Sep/2018:09:30:52 +0000] "GET > > /feed/rel-18.08/Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm > > HTTP/1.1" 403 345 "-" "urlgrabber/3.10 yum/3.4.3" > > > > You can see this also with a wget command: > > localhost:/home/wrsroot# wget http://localhost/feed/rel-18.08/Package > > s/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm > > --2018-09-12 20:54:19-- http://localhost/feed/rel-18.08/Packages/pyt > > hon2-qpid-proton-0.24.0-1.el7.x86_64.rpm > > Resolving localhost (localhost)... ::1, 127.0.0.1 Connecting to > > localhost (localhost)|::1|:80... connected. > > HTTP request sent, awaiting response... 403 Forbidden > > 2018-09-12 20:54:19 ERROR 403: Forbidden. > > > > > > The problem is that two of the RPMs on the ISO have 600 permissions, > > where all other RPMs are 644. This is carried over when the files are > > copied to the controller during the post-install phase: > > > > controller-0:~$ ls -l /mnt/iso/Packages/ | grep -- --- > > -rw------- 1 1001 users 258624 Aug 28 12:04 python2-qpid-proton- > > 0.24.0-1.el7.x86_64.rpm > > -rw------- 1 1001 users 190128 Aug 28 12:04 qpid-proton-c-0.24.0- > > 1.el7.x86_64.rpm > > > > controller-0:~$ ls -l /www/pages/feed/rel-18.08/Packages/ |grep -- -- > > - > > -rw-------. 1 root root 258624 Sep 12 20:33 python2-qpid-proton- > > 0.24.0-1.el7.x86_64.rpm > > -rw-------. 1 root root 190128 Sep 12 20:33 qpid-proton-c-0.24.0- > > 1.el7.x86_64.rpm > > > > > > The lighttpd server runs as a non-root user, and cannot access these > > files. Change the permissions on the files, and the installation of > > controller-1 should be successful. > > > > > > -----Original Message----- > > From: Young, Ken [mailto:Ken.Young at windriver.com] > > Sent: Wednesday, September 12, 2018 4:53 PM > > To: Cordoba Malibran, Erich > > Cc: starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Erich, > > > > One correction below: we are using a Wind River version of the > > installer (I am confusing this thread with another thread). This is > > the installer we shipped Titanium Cloud Release 5. > > > > This begs the question: what installer were you using before the > > changes to the kernel? > > > > /KenY > > > > On 2018-09-12, 4:36 PM, "Young, Ken" > > wrote: > > > > Erich, > > > > A couple of data points on our side. For our builds, we are using > > stock CentOS installer for 7.4. These are unchanged and we have not > > seen this issue on our side. > > > > Have you isolated when you made the changes to the installer? Is > > it the same time you started seeing this error? Does it make sense to > > revert to the stock installer while we get to the bottom of this issue > > to continue sanity? > > > > Regards, > > Ken Y > > > > On 2018-09-11, 8:30 PM, "Cordoba Malibran, Erich" > malibran at intel.com> wrote: > > > > I have narrowed down a little bit the issue, these are my > > findings. > > > > - I compared the bootimage_michel.iso with the stx-2018-09- > > 11- > > 111.iso, which is today's ISO. > > - The are not significant package differences between them, > > minor > > versions has changed in some packages. > > - The issue is that once the kernel has been loaded through > > PXE, > > anaconda is unable to find python2-qpid package. Not sure if > > this is > > the first package that is requested. > > - From the anaconda shell I can see the http://pxecontrolle > > r/ serving > > the files and the repodata seems to be updated there. I > > installed yum > > manually and I was able to install python2-qpid package, (and > > any other > > available). > > - The content of the pxe-network-installer package is not > > the same, > > WR squashfs.img file has the kernel 3.10.0-693.2.2 but ours > > has 3.10.0- > > 862.6.3. We regenerate those files when the kernel was > > upgraded. (maybe > > this matches with the date where the issue started to > > arise..) > > > > So, my guess now is that the problem could be caused by the > > pxe- > > network-installer package. We create those files with the > > update- > > network-installer script. That's the same used in WR to > > generate these > > files? > > > > I'll keep diging in the generation of these files to see if > > there is > > any problem. > > > > -Erich > > > > On Tue, 2018-09-11 at 20:03 +0000, Lara, Cesar wrote: > > > I just wanted to make sure that we are able to reproduce the > > issue > > > regardless of the build environment. > > > > > > AFAIK CentOS 7.5 upgrade is a different issue/thread, but at > > the end > > > we can fine tune a process in which we are in the same > > conditions to > > > be able to replicate errors in any given build environment. > > > > > > Regards > > > Cesar Lara > > > > > > > > > -----Original Message----- > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > Sent: Tuesday, September 11, 2018 2:02 PM > > > To: Lara, Cesar ; Alonso, Juan Carlos > > > > los.alonso at intel.com>; Khalil, Ghada > r.com>; > > > Martinez Monroy, Elio ; > > Jones, Bruce > > > E ; Cabrales, Ada > tel.com>; > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > @windriver.com>; Young, Ken ; > > Little, Scott > > > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > > > Hi Cesar, > > > > > > Would you elaborate on what differences you'd expect to see > > in an > > > empty mirror populated by the download tool, compared to an > > existing > > > mirror which was updated by the download tool? > > > > > > The mirror tools were written specifically to contain > > multiple > > > versions of packages. The build environment population > > tools take > > > the .lst file you have checked out, and places that version > > from the > > > mirror into your local environment guaranteeing that your > > build env > > > matches the .lst file. If your mirror contains versions > > 1.0.0, > > > 1.2.3, and 2.0.0 of a given package, then your environment > > will only > > > use the version called out in the .lst file you have checked > > out. > > > > > > This allows the same mirror to be used for multiple > > branches, for > > > multiple releases, for multiple development environments, > > etc, and > > > guarantees that a build can be reproduced down the road even > > if the > > > build inputs disappear from the Internet at some point in > > the > > > future. As long as all the artifacts named in the .lst file > > have > > > been downloaded at some point in the past, the build > > environment > > > produced from a fresh mirror vs a continually updated mirror > > will be > > > identical. > > > > > > The issue we are observing with the CentOS 7.5 update is > > that the > > > versions of packages called out in the .lst files for the > > centos75 > > > branch of stx-tools do not match the versions of packages > > called out > > > in centos75 branch of the other repos, like stx-integ. The > > other > > > branches are attempting to patch a (new) version of the > > source code, > > > but the .lst file is only bringing in (or downloading) and > > older > > > version of the source. > > > > > > -Jason > > > > > > > -----Original Message----- > > > > From: Lara, Cesar > > > > Sent: September 11, 2018 1:44 PM > > > > To: Alonso, Juan Carlos ; > > Khalil, > > > > Ghada > > > > ; Martinez Monroy, Elio > > > > ; Jones, Bruce E > > > > ; Cabrales, Ada > tel.com>; > > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > Hi all, > > > > > > > > Just wanted to point out that, to be able to reproduce the > > issues > > > > from > > > > Intel's ISO, somebody will need to go and create a build > > > > environment > > > > from scratch, using external upstream repositories to > > generate a > > > > new > > > > mirror, just the way we are doing it in our environment. > > Failing to > > > > do > > > > this will result in a apples to oranges comparison. > > > > > > > > Regards > > > > Cesar Lara > > > > > > > > -----Original Message----- > > > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at inte > > l.com] > > > > Sent: Tuesday, September 11, 2018 10:54 AM > > > > To: Khalil, Ghada ; Martinez > > Monroy, > > > > Elio > > > > ; Jones, Bruce E > > > > ; Cabrales, Ada > tel.com>; > > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > Hi Ghada, > > > > > > > > Yes, before shared our ISOs I followed such steps and got > > the same > > > > issues. > > > > > > > > As I mention in the issue > > > > (https://bugs.launchpad.net/starlingx/+bug/1790213), I > > could get > > > > the > > > > ISO from Michel and testes in our infrastructure, issues > > not found. > > > > I > > > > guess there are differences between the way an ISO is > > built by > > > > Intel > > > > and Wind River since Intel got issues but Wind River does > > not. I > > > > think we should sync about this. > > > > > > > > Besides, our test infrastructure uses other commands to > > generate > > > > VMs, > > > > add/install hosts (controllers and computes), such > > commands was > > > > gotten > > > > from "tic_vb" repo, such repo was given by China team, if > > I am not > > > > wrong such repo was based on Wind River documentation; our > > test > > > > framework is based on "tic_vb". Anyway both ways got the > > same > > > > results. > > > > > > > > Regards. > > > > Juan Carlos Alonso > > > > > > > > -----Original Message----- > > > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > > > Sent: Tuesday, September 11, 2018 8:53 AM > > > > To: Alonso, Juan Carlos ; > > Martinez > > > > Monroy, Elio ; Jones, > > Bruce E > > > > ; Cabrales, Ada > tel.com>; > > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > > > > > Hello Juan, > > > > I read the notes in the Launchpad. > > > > > > > > And, just to confirm, are you following the instructions > > under: > > > > https://wiki.openstack.org/wiki/StarlingX/Installation_Gu > > ide_Virtua > > > > l_E > > > > nviro > > > > nment/Controller_Storage > > > > and still reproducing the two issues below? > > > > > > > > I was not able to definitively tell from the Launchpad > > notes. It's > > > > important that both our teams are comparing apples to > > apples. > > > > > > > > Thanks, > > > > Ghada > > > > > > > > -----Original Message----- > > > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at inte > > l.com] > > > > Sent: Monday, September 10, 2018 1:50 PM > > > > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; > > > > Cabrales, > > > > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > Subject: RE: [ Test ] Sanity results - summary posted > > > > > > > > Hi, > > > > > > > > Such launchpads were updated. > > > > > > > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such > > ISO > > > > present > > > > two issues. Michael will upload his ISO, then we will re > > test > > > > witch > > > > each iso in our environment. > > > > > > > > An script is being developed to get the differences > > between ISOs. > > > > > > > > Regards. > > > > Juan Carlos Alonso > > > > > > > > -----Original Message----- > > > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > > > Sent: Friday, September 7, 2018 4:43 PM > > > > To: Khalil, Ghada ; Martinez > > Monroy, > > > > Elio > > > > ; Jones, Bruce E > > > > ; Cabrales, Ada > tel.com>; > > > > starlingx-discuss at lists.starlingx.io; Thebeau, Michel > > > > > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > Hi Elio/Ada, > > > > Are there any updates from your side on these two > > Launchpads? > > > > https://bugs.launchpad.net/starlingx/+bug/1790213 > > > > https://bugs.launchpad.net/starlingx/+bug/1790716 > > > > > > > > Michel Thebeau (Wind River) has been trying to reproduce > > these two > > > > issues (following the starlingx wikis) without success for > > two > > > > days > > > > now. He has been adding his findings to the bugs and > > communicating > > > > with your team. > > > > As a result of his investigation, he will be pushing some > > small > > > > fixes > > > > to stx- tools shortly (some cleanup). > > > > > > > > Please let us know if you need any further help from us. > > > > > > > > Thanks, > > > > Ghada > > > > > > > > -----Original Message----- > > > > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > > > > Sent: Wednesday, September 05, 2018 5:39 PM > > > > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > > > > starlingx- > > > > discuss at lists.starlingx.io > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > Please see inline. There are notes in all the launchpads > > as well. > > > > > > > > I have tagged the last bug for the October release. The > > rest need > > > > more > > > > information to determine whether they gate or not: two > > maybe > > > > procedural and one requires more information. > > > > > > > > -----Original Message----- > > > > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy@ > > intel.com] > > > > Sent: Wednesday, September 05, 2018 2:23 PM > > > > To: Jones, Bruce E; Cabrales, Ada; > > > > starlingx-discuss at lists.starlingx.io > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > My opinion below > > > > > > > > -----Original Message----- > > > > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > > > > Sent: Wednesday, September 5, 2018 12:56 PM > > > > To: Cabrales, Ada ; starlingx- > > > > discuss at lists.starlingx.io > > > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results > > - summary > > > > posted > > > > > > > > Should the bugs coming out of this be tagged/fixed for the > > October > > > > release? > > > > > > > > Related bugs: > > > > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- > > Must, this > > > > bug > > > > is related with 2nd controller provisioning [[GK]] Using > > the > > > > instructions published on the wiki, our designer was not > > able to > > > > reproduce this issue. > > > > What instructions are the test team using? > > > > > > > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- > > Can wait > > > > until > > > > other issues are solved, will fail some test cases related > > to SSH > > > > [[GK]] Requested more information. This cannot be debugged > > further > > > > without this information. > > > > > > > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- > > Must, all > > > > instances need at least one compute for multimode [[GK]] > > Using the > > > > instructions published on the wiki, our designer was not > > able to > > > > reproduce this issue. The test team points to internal > > > > instructions > > > > which we have no access to. The supported install recipes > > need to > > > > be > > > > on the wiki. I think it is an invalid bug > > > > > > > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- > > Can wait > > > > since > > > > is related to FM , test cases will fail [[GK]] As Brent > > pointed > > > > out, > > > > this is dependent on the integration of stx-gui which is > > in > > > > progress. > > > > > > > > -----Original Message----- > > > > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > > > > Sent: Wednesday, September 5, 2018 10:50 AM > > > > To: starlingx-discuss at lists.starlingx.io > > > > Subject: [Starlingx-discuss] [ Test ] Sanity results - > > summary > > > > posted > > > > > > > > Hello all, > > > > > > > > As mentioned on the project meeting today, we're > > posting the > > > > summary of the sanity test runs on the Test wiki [0]. The > > sanity > > > > is > > > > triggered each time an ISO is generated (a daily task). > > > > > > > > Right now we are posting the results manually, and > > working on a > > > > way > > > > for automating it. Logs of the run are not included, if > > you want > > > > to > > > > have them, you can contact Elio to get them sent to you. > > > > > > > > > > > > [0] > > > > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO > > _image_San > > > > ity > > > > _S > > > > ummary > > > > > > > > Regards > > > > Ada > > > > > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starli > > ngx-discus > > > > s > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starling > > x-discuss > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > uss > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ken.Young at windriver.com Fri Sep 14 15:47:55 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Fri, 14 Sep 2018 15:47:55 +0000 Subject: [Starlingx-discuss] Build Meeting Agenda Item for Monday, Sept 17th Message-ID: Cesar / Sual, On Monday, I would like to discuss where we are with the installer for StarlingX. The following launchpad: https://bugs.launchpad.net/starlingx/+bug/1790213 revealed that Intel and Wind River are using different installers. I suspect that a general designer may be using a third installer. We need to get this down to 1 so when issues are reported, we are comparing apples to apples. I would like to quantify this problem and based upon interest, drive to a solution. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Fri Sep 14 16:40:12 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 14 Sep 2018 11:40:12 -0500 Subject: [Starlingx-discuss] CentOS 7.5 Upgrade - branch rebase Message-ID: I have rebased the f/centos75 branches to current master (as of 30-60 minutes before I typed this) in stx-integ, stx-root, stx-tools and stx-upstream. The merge commits need to be approved in Gerrit: https://review.openstack.org/#/q/topic:%22rebase+f/centos75%22 Note that stx-root has two due to an error on my part in initally creating the branch. I fixed the name and will keep the branch that Shuicheng is using in sync with the correct branch. dt -- Dean Troyer dtroyer at gmail.com From scott.little at windriver.com Fri Sep 14 16:40:36 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 14 Sep 2018 12:40:36 -0400 Subject: [Starlingx-discuss] [Build] Feedback on stxb demo In-Reply-To: <1536760633.18798.5.camel@intel.com> References: <12f082a2-f28d-ad8e-6fa2-336c0d945513@linux.intel.com> <6594B51DBE477C48AAE23675314E6C465993F282@fmsmsx107.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA451D65@ALA-MBD.corp.ad.wrs.com> <1536760633.18798.5.camel@intel.com> Message-ID: <4e5a2f14-ba87-365a-9c78-43603cfab164@windriver.com> Kudo's on the container unification. I'de like to see the underlying steps captured on the wiki. I'll second all of Jason's concerns.  There are a lot of assumptions built into the current draft of the tool that are a deal killer for a working designer, doubly so for designer working on a shared machine. Might be acceptable for a newcomer who wants to build his first load to try it out ... if he has a private box ... and sudo powers ... and doesn't really plan to change anything. As for everyone building the same way... correct goal.  But this tool is unusable in our shared build environments, so goal not yet achieved. Scott On 18-09-12 09:57 AM, Arevalo, Mario Alfredo C wrote: > On Wed, 2018-09-12 at 13:08 +0000, Khalil, Ghada wrote: > > Hi Folks, > >> Hello all, >> +1 for Jason's suggestion ...we cannot have the community transition >> to this tool as the official way of building at this time. We need to >> all agree as a community when to trial new tools to get feedback and >> when to make them official. > If you take a look to the tool's PRs, the first objective is not to do > a transition for the moment, basically the ISO process involves a > series of steps that might be painful for new users, and we have > noticed that in the mailing list. > > For us, StarlingX team, those steps are easy because we deal with them > every day, but we need to think of those who are not interested in > become a developer for the moment and just want to make an ISO image, > that is the first use case for the stxb tool. > > The current building process will continue working in the same way, > stxb tool just automates those steps. The biggest change in the stxb > tool development and the building tools core is the unification of > dockerfiles, however it does not involve huge changes in documentation > and it is open to feedback. > > >> We are driving hard to achieve code freeze for the October Release. >> We need to ensure everyone is building the same official way to avoid >> inconsistent results. > Completely agree :) > >> As a side note, based on the review with the Build Project Lead >> (Cesar), there were no build improvements planned for the October >> release except for https://storyboard.openstack.org/#!/story/2002835 >> >> As the StarlingX release prime, I have tagged the new story for the >> March release (stx.2019.03). Please plan accordingly. Code >> submissions can still go in master, but cannot alter the documented >> build process and tools currently used. This story should not be >> considered complete until there is agreement to move the community to >> it and update the official documentation at some point after the >> October release. > Best Regards. > Mario. > >> Regards, >> Ghada >> >> -----Original Message----- >> From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] >> Sent: Tuesday, September 11, 2018 12:32 PM >> To: Arevalo, Mario Alfredo C; Saul Wold; 'starlingx-discuss at lists.sta >> rlingx.io' >> Subject: Re: [Starlingx-discuss] [Build] Feedback on stxb demo >> >> Hi Mario, >> >>> -----Original Message----- >>> From: Arevalo, Mario Alfredo C >>> Sent: September 10, 2018 4:57 PM >>> To: Saul Wold ; McKenna, Jason >>> ; 'starlingx-discuss at lists.starlingx.i >>> o' >>> >>> Subject: RE: [Starlingx-discuss] [Build] Feedback on stxb demo >>> >>> Hi folks, >>> >>> I have been seen excellent ideas that we can to add to the tool, >>> however I think we are walking a little out of the first scope, >>> what >>> do you think if we include this as first version a we can post our >>> ideas in the storyboard?: >> I agree that we can put it out as a first preview version, however I >> would have strong reservations about changing the wiki documentation >> to suggest that this is "the official way to build" at this time. >> >>> >>> https://storyboard.openstack.org/#!/story/2003712 >> +1 to the consolidation of docker images, and it sounds like that >> part's done.  Good job! >> >>> >>> Then we can track all ideas suggested :) >> Yeah, I think we should have ideally had a discussion about use cases >> and requirements before the tool was designed.  In particular, I do >> not think the tool (as demoed) is usable by developers.  I understand >> that your requirements are to come up with an end-to-end tool that >> would produce a build with as few commands as possible, but the >> current architecture of having a second repo inside the docker >> container is a deal-breaker for any developer trying to work on the >> code.  I'm all for designing and using better tools, but we shouldn't >> make this the official way of doing things if it places a new non- >> trivial burden on the devs.  There might be some wiggle room on my >> suggestion to support a native (rather than containerized) build. >> >> As a tangential note, are you able to confirm that the use of a local >> mirror of packages rather than a download into the container from the >> Internet is working?  We don't want to introduce a change that would >> unnecessarily add hours to a build. >> >>> >>> Best regards. >>> Mario. >>> ________________________________________ >>> From: Saul Wold [sgw at linux.intel.com] >>> Sent: Monday, September 10, 2018 10:33 AM >>> To: McKenna, Jason; 'starlingx-discuss at lists.starlingx.io' >>> Subject: Re: [Starlingx-discuss] [Build] Feedback on stxb demo >>> >>> Sorry I missed this today, I am in Denver. >>> >>> Can you point me at the repo you are working in please? >>> >>> On 09/10/2018 09:02 AM, McKenna, Jason wrote: >>>> Hi build team, >>>> >>>> Many thanks for the demo today, I think we're on the right >>>> track. >>>> As promised, here are a few feedback points on the demo, from >>>> the >>>> perspective of a developer: >>>> >>>> -I really like how the creation of the docker image is >>>> streamlined. >>>> >>>> -The system as currently demo'd as two copies of the repos.  One >>>> in >>>> /(developers_path)/, and a second in >>>> /(developers_path)/stx- >>> tools/(docker_image_root_dir)/localdisk/designer/builder/starlingx/ >>> . >>>> There should only one repo downloaded. >>>> >>>> oAs a related point, a developer working on changes to a file >>>> would >>>> expect to make their changes to the repo in /(developers_path)/, >>>> rather than to the version in the docker image's filesystem.  If >>>> I >>>> edited a puppet manifest (for example) >>>> /(developers_path)/cgcs-root/stx/stx-config/.../ then I would >>>> expect >>>> the build command to detect and use my changes if I do a build. >>>> >>>> -I'm a bit confused on the syntax regarding specifying and using >>>> localized mirrors, specifically with the -n and -p >>>> options.  Would >>>> you provide examples of what commands I'd execute for use cases >>>> 1 >>>> and 2 below? I'm pretty sure these usages are supported, but am >>>> just >>>> seeking clarification. >>>> >>>> -Very happy do see it down to 1 docker image, rather than 2 J >>>> >>>> -Native build - Being able to build in a docker image is great, >>>> but >>>> the would ideally be an option to perform a native build, rather >>>> than have to use a container >>>> >>>> -Minor nit - logs should be in a user directory (like >>>> $MY_REPO_ROOT_DIR/logs/) rather than in /var/log, as a >>>> non-privileged user wouldn't be able to log to /var/log. >>>> >>>> -Question - what privileges are required to create the docker >>>> image? >>>> Does the script assume the user has sudo privileges? >>>> >>>> -I'm unclear on what would happen with use cases 3-5 >>>> below.  Have >>>> these types of uses been considered yet? >>>> >>> Jason, >>> >>> Thanks for this feedback and the use case suggestions below, see >>> additional comments. >>> >>>> Thanks again for the demo, >>>> >>>> -Jason >>>> >>>> Use Case 1: >>>> >>>>                  I am an organization with a site who is working >>>> with StarlingX.  I want to provide a local mirror for my >>>> employees >>>> to use so they don't have to download all artifacts from the >>>> external internet every time. I want to create an automated job >>>> which I will run daily to download all artifacts from the >>>> Internet >>>> (if they do not already exist) and place them in directory >>>> /export/mirrors/starlingx. >>>> Assume the user running the automated job has permissions to >>>> write >>>> to /export/mirrors/starlingx >>>> >>> Based on your usage of /export and /import below, /export is on a >>> server machine and /import is on the local developer build >>> machine, >>> just for clarification. >>> >>> Also, this job would run native on the host Linux OS not >>> containerized? >>> >>> >>>> Use Case 2: >>>> >>>>                  I am a developer within an organization which >>>> has a >>>> local mirror of artifacts available in >>>> /import/mirrors/starlingx.  I >>>> want to build a StarlingX ISO without downloading rpms or >>>> src.rpms >>>> from the external internet. >>>> >>> To further clarify this one, the remote mirror could contain all >>> binary rpms along with their cooresponding src rpm, such that if >>> no >>> changes all the building of an ISO would be done from the mirror >>> rpms, >>> no actual local rpm build required unless it changes (use case 4/5 >>> below). >>> >>>> Use Case 3A: >>>> >>>>                  After doing a build, I just performed a repo >>>> sync, >>>> and the .lst files were not updated.  If I perform another build >>>> of >>>> the ISO, will the system attempt to redownload external >>>> artifacts, >>>> even though nothing has changed? >>>> >>>> Use Case 3B: >>>> >>>>                  After doing a build, I just performed a repo >>>> sync, >>>> and noticed that the .lst files have been updated.  If I perform >>>> another build of the ISO, will the stale mirror content be >>>> detected >>>> and the new additions downloaded (while not re-downloading >>>> anything >>>> which has not changed)? >>>> >>>> Use Case 4: >>>> >>>>                  I have manually made a change to a puppet >>>> manifest >>>> in sysinv (stx-config git) but want to test before I commit >>>> anything. >>>> How can I build a new ISO with my changes incorporated? >>>> >>> I would say not just puppet manifest, but any change to files in >>> the repos. >>> >>>> Use Case 5: >>>> >>>>                  I want to test StarlingX with my own additional >>>> program >>>> (foobar.x86_64.rpm) on the ISO.  How would I perform a build >>>> with >>>> this file added? >>>> >>> I look forward to seeing the demo also. >>> >>> Sau! >>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc >>>> uss >>>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>> s >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Nimalini.Rasa at windriver.com Fri Sep 14 16:46:04 2018 From: Nimalini.Rasa at windriver.com (Rasa, Nimalini) Date: Fri, 14 Sep 2018 16:46:04 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> Message-ID: <65CE126717DEA145BD6B2C2842DC52D66C0C759F@ALA-MBD.corp.ad.wrs.com> Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss From cesar.lara at intel.com Fri Sep 14 18:53:05 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Fri, 14 Sep 2018 18:53:05 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meetup Agenda for sept 17th 2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB471050691C@fmsmsx104.amr.corp.intel.com> Agenda -Scoping and planning for first release of sxtb tool (all) -Installer consolidation for starling X https://bugs.launchpad.net/starlingx/+bug/1790213 -opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From Nimalini.Rasa at windriver.com Fri Sep 14 19:02:27 2018 From: Nimalini.Rasa at windriver.com (Rasa, Nimalini) Date: Fri, 14 Sep 2018 19:02:27 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> Message-ID: <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss From bruce.e.jones at intel.com Fri Sep 14 21:23:17 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 14 Sep 2018 21:23:17 +0000 Subject: [Starlingx-discuss] [Docs] RFC: Draft Feature Dev process Message-ID: <9A85D2917C58154C960D95352B22818BAB58E98E@fmsmsx115.amr.corp.intel.com> We held a review of an early draft of a Feature Development process at the PTG this week, and I've written up an updated version thanks to the group feedback. It's out on the wiki at https://wiki.openstack.org/wiki/StarlingX/Feature_Development_Process. I am looking for any and all feedback on the document and the process it describes. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Sep 14 22:09:05 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 14 Sep 2018 22:09:05 +0000 Subject: [Starlingx-discuss] Project call agenda open.. Message-ID: <9A85D2917C58154C960D95352B22818BAB58EAF4@fmsmsx115.amr.corp.intel.com> The agenda for our next project call is open. Please feel free to add items to be discussed. https://etherpad.openstack.org/p/stx-status Agenda and Notes for the Sep 19th call * PTG Update * Review comments on the draft Feature Dev process (Bruce) * Review comments on the Governance draft (Bruce) * New Multi-OS sub-project (Bruce) * Containerized Services update (Brent) * Project de-coupling update (Brent) * Investing in StoryBoard development (Bruce) * Edge WG Update / slides (Greg) * Release status (Ghada) * Status from other teams / issues * Help needed? -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Sat Sep 15 00:32:18 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Sat, 15 Sep 2018 00:32:18 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B344C22@SHSMSX104.ccr.corp.intel.com> Nimalini, Thanks for the report. Just to ensure, so the below 2 tests were passed in mainline build, correct? Thx. - cindy -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss From shuicheng.lin at intel.com Sat Sep 15 01:13:19 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Sat, 15 Sep 2018 01:13:19 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> Hi Nimalini, Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? " controller-0:~$ cat /proc/sys/kernel/tainted 4096 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss From dehao.shang at intel.com Sat Sep 15 11:01:09 2018 From: dehao.shang at intel.com (Shang, Dehao) Date: Sat, 15 Sep 2018 11:01:09 +0000 Subject: [Starlingx-discuss] py-bcrypt conflicts with python2-bcrypt Message-ID: <71AECFE5078153419EB7B8DBE0644B26386383E5@shsmsx102.ccr.corp.intel.com> Hi: Based on ceph13.2.0 binary package, now i am re-building python-cephclient. At building python-cephclient process, lack some packages. The most packages can be resolved by manually adding new packages. But for py_bcrypt, I can't resolve package confilect between python2-bcrypt and py-bcrypt. == More details process == Based on ceph13.2.0 binary packages, "build-pkgs python-cephclient" will show some error. The most can be manually resolved, but one error is as following: Error: Package: 2:ceph-mgr-13.2.0-0.el7.centos.x86_64 (1270018088_localdisk_loadbuild_dehao_starlingx_std_results_dehaostarlingxtisr5pikestd_) 01:51:09 Requires: py-bcrypt 01:51:09 You could try using --skip-broken to work around the problem 01:51:09 You could try running: rpm -Va --nofiles --nodigest check ceph-mgr-13.2.0-0.el7.centos.x86_64.rpm, and verify this deps. [dehao at 9f9456a3d92b RPMS]$ rpm -qp --requires ceph-mgr-13.2.0-0.el7.centos.x86_64.rpm | grep py_bcrypt. py_bcrypt so, when I manually download and add this packages, can successfully build python-cephclient. Next step, when run "build-iso", the conflict between py-bcrypt with python-bcrypt will occur as the below: 02:38:55 02:38:57 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 02:38:57 These RPMS had problems (likely version conflicts) 02:38:57 py-bcrypt conflicts with python2-bcrypt-3.1.2-3.el7.x86_64 02:38:57 Could not install dependencies I look up some materials, and find this is a bug, namely it's not possible to simultaneously install python-bcrybt and py-bcrybt packages dependent. Conflict bug: https://bugzilla.redhat.com/show_bug.cgi?id=1473018 I also check my building environments, and verify that these two packages simultaneously exist. [root_cluster4: x86_64]# rpm -qp --provides python2-bcrypt-3.1.2-3.el7.x86_64.rpm < ----------------------- other project need this package. python-bcrypt = 3.1.2-3.el7 python2-bcrypt = 3.1.2-3.el7 python2-bcrypt(x86-64) = 3.1.2-3.el7 [root_cluster4: x86_64]# rpm -qp --provides py-bcrypt-0.4-4.el7.x86_64.rpm < --------------------------- the ceph-mgr package of ceph 13.2.0 require this packages py-bcrypt = 0.4-4.el7 py-bcrypt(x86-64) = 0.4-4.el7 can anyone tell me how I can solve this problem. Thanks Dehao -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Sun Sep 16 23:53:55 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Sun, 16 Sep 2018 23:53:55 +0000 Subject: [Starlingx-discuss] download_mirror.sh error - bad repo? Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3B09A1@ALA-MBD.corp.ad.wrs.com> Hi folks, I'm running download_mirror.sh as per the README (build a docker image, run download_mirror.sh in a container), but it fails in the first stage: failure: repodata/0fa206724f7262cecd5a4832731024dbff9b2cce3d64676fff1038bf08222c03-primary.xml.gz from Starlingx-mirrors.isu.net.sa_pub_fedora_fedora-epel_7Server_x86_64: [Errno 256] No more mirrors to try. http://mirrors.isu.net.sa/pub/fedora/fedora-epel/7Server/x86_64/repodata/0fa206724f7262cecd5a4832731024dbff9b2cce3d64676fff1038bf08222c03-primary.xml.gz: [Errno 14] HTTP Error 404 - Not Found ERROR: Something wrong with downloading files listed in ./rpms_3rdparties.lst. Please check the log at /localdisk/logs/rpms_3rdparties_download_L1.log ! The repomd.xml file for this repo is pointing to non-existent files, and has a timestamp of Sept 11, 2018. Has this been broken since then? I was able to disable this repo in yum.repos.d and verify the pkgs I'm trying to add to the lst file are downloaded, but this issue would likely mean they won't get downloaded otherwise and would be unusable in the build until its resolved. Is anyone else seeing this error? Thanks, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Mon Sep 17 07:17:08 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Mon, 17 Sep 2018 07:17:08 +0000 Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming Message-ID: Hi Matt, We analyze the patch 4ae5a58 related to l2pop. An RFE has been written(You can find it in the attachment). Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: RFE_EXTEND_L2POP_FDB_INFORMATION.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 19201 bytes Desc: RFE_EXTEND_L2POP_FDB_INFORMATION.docx URL: From cindy.xie at intel.com Mon Sep 17 10:17:48 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 17 Sep 2018 10:17:48 +0000 Subject: [Starlingx-discuss] CentOS 7.5 Upgrade - branch rebase In-Reply-To: References: Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B346E76@SHSMSX104.ccr.corp.intel.com> Dean, I am wondering why the below 2 rebase patch still cannot be merged? https://review.openstack.org/#/c/602666/ https://review.openstack.org/#/c/602660/ they've already gathered enough +1, +2, but still shows as "needs verified lable"... thanks for checking. - cindy -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Saturday, September 15, 2018 12:40 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS 7.5 Upgrade - branch rebase I have rebased the f/centos75 branches to current master (as of 30-60 minutes before I typed this) in stx-integ, stx-root, stx-tools and stx-upstream. The merge commits need to be approved in Gerrit: https://review.openstack.org/#/q/topic:%22rebase+f/centos75%22 Note that stx-root has two due to an error on my part in initally creating the branch. I fixed the name and will keep the branch that Shuicheng is using in sync with the correct branch. dt -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Matt.Peters at windriver.com Mon Sep 17 10:41:03 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Mon, 17 Sep 2018 10:41:03 +0000 Subject: [Starlingx-discuss] Questions about StarlingX OVS-DPDK firewall driver enhancement In-Reply-To: References: Message-ID: Hello Kailun, I’m fine with exploring option #3 as an alternative to #2. I wasn’t aware that the native driver fully supported the netdev datapath, but if it can be supported, then I agree it would be a better choice. Regards, Matt From: "Qin, Kailun" Date: Thursday, September 6, 2018 at 10:09 AM To: "Peters, Matt" , "starlingx-discuss at lists.starlingx.io" Subject: Questions about StarlingX OVS-DPDK firewall driver enhancement Hi Matt, We are doing some ground work for https://storyboard.openstack.org/#!/story/2002944 regarding the StarlingX OVS-DPDK firewall driver enhancement. To better understand the requirement, we may need your help on the following question. There are 3 security group implementations in neutron OVS-DPDK agent. 1. Iptables based security group The OVS agent and Compute service use a Linux bridge between each instance (VM) and the OVS integration bridge br-int to implement security groups. This implementation is stateful but cause scalability and performance problems. 2. Openflow based security group This implementation is stateless and based in OpenFlow 'learn action', which uses a firewall driver in networking-ovs-dpdk project. https://github.com/openstack/networking-ovs-dpdk/blob/master/networking_ovs_dpdk/agent/ovs_dpdk_firewall.py 3. Openflow + conntrack based security group This implementation is stateful, which uses a native firewall driver. https://docs.openstack.org/newton/networking-guide/config-ovsfwdriver.html http://docs.openvswitch.org/en/latest/tutorials/ovs-conntrack/ The requirement from the enhancement description is that we're going to adopt implementation option 2 for StarlingX OVS-DPDK security group. Compared with option 3 which is stateful and uses a native firewall driver, what is our consideration on taking option 2 as our target? Please kindly see the attached doc for further details. Just let me know if anything unclear. Thanks a lot! BR, Kailun -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Mon Sep 17 10:55:12 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 17 Sep 2018 10:55:12 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 9/19 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B346F1B@SHSMSX104.ccr.corp.intel.com> [try to fix format issue] Agenda for 9/19 meeting: - CentOS 7.5 upgrade testing status (Shuicheng, Elio, Numan/Nimalini) - Decision required: feature branch merge back to master (Ghada, Brent/Dean) - Libvirt/qemu upgrade status (Ghada/Jim) - 2018.10 content review (Ghada) - Ceph upgrade status (Vivian/Dehao) - non-OpenStack patch analysis status (Saul/Zhipeng) - Opens (Brent, Saul, Ghada) For those people who has an agenda above, I am expecting you to attend; plus those signed up in non-OpenStack distro project also required. All others are welcome to attend. Thx. - cindy -----Original Message----- From: Xie, Cindy Sent: Monday, September 17, 2018 6:53 PM To: Lin, Shuicheng ; Martinez Monroy, Elio ; Waheed, Numan ; 'Rasa, Nimalini' ; Khalil, Ghada ; 'Rowsell, Brent' ; Troyer, Dean ; Somerville, Jim ; Zhu, Vivian ; Shang, Dehao ; Wold, Saul ; Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io Subject: Agenda: Weekly StarlingX non-OpenStack Distro meeting, 9/19 Agenda for 9/19 meeting: . CentOS 7.5 upgrade testing status (Shuicheng, Elio, Numan/Nimalini) . Decision required: feature branch merge back to master (Ghada, Brent/Dean) . Libvirt/qemu upgrade status (Ghada/Jim) . 2018.10 content review (Ghada) . Ceph upgrade status (Vivian/Dehao) . non-OpenStack patch analysis status (Saul/Zhipeng) . Opens (Brent, Saul, Ghada) For those people who has an agenda above, I am expecting you to attend; plus those signed up in non-OpenStack distro project also required. All others are welcome to attend. Thx. - cindy -----Original Appointment----- From: Xie, Cindy Sent: Friday, August 24, 2018 9:38 AM To: Xie, Cindy; Khalil, Ghada; Wold, Saul; Rowsell, Brent; Sun, Austin; Wang, Yi C; Lin, Shuicheng; Chen, Yan; Somerville, Jim; 'Ildiko Vancsa'; starlingx-discuss at lists.starlingx.io Cc: Perez Rodriguez, Humberto I; Hu, Yong; Zhu, Vivian; 'Chen, Jacky'; 'Leo Xu'; 'Waines, Greg'; 'Eslimi, Dariush'; 'Komiyama, Takeo'; Martinez Monroy, Elio; Jones, Bruce E; Hernandez Gonzalez, Fernando; Hu, Wei W; Qi, Mingyuan; 'Young, Ken'; Arce Moreno, Abraham; 'Seiler, Glenn'; Gomez, Juan P Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, September 19, 2018 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM EDT (9PM China time) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From Ian.Jolliffe at windriver.com Mon Sep 17 13:43:13 2018 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Mon, 17 Sep 2018 13:43:13 +0000 Subject: [Starlingx-discuss] PTG upstreaming discussion Message-ID: Hi all; Just a short note to share what Brent, Saul, Dean and I reviewed on Thursday at the PTG last week.  We went through the upstreaming backlog and the notes below summarize the outcomes.  This does not reflect the outcomes of the direct engagement with the Neutron and Nova teams, that summary will follow. We added a new tag – maintain, items which we know we will need to maintain.   Horizon: Eddie and Tyler to get together to review what is left out of STX-GUI and what additional refactoring may be required or patches left to upstream   Keystone: Nothing left after March release due to containerization of Openstack   Python-Clients: items need to map to main project server-side disposition.  Additionally, we agreed we should move the clients as close to master as possible, this can be done independently as this provides users backward compatibility.   Heat: most are related to underlying changes and should be mapped to those items as close as possible.  There are a few bug fixes that can be tackled easily.  Step 1 is to mapping out the dependencies so that the bugs can be focused on.   Glance: raw caching can it be replaced by cinder feature.  Removes several Glance patches.  Lisa and Brent to analyze – emails in flight.   Cinder: in good shape, but, there is work left to do.  We need to identify who can focus on these items up so we can retire the repo.   Ceilometer: Many can be retired, we did a scrub in real time.   Nova: 200 – 300 items to be worked on.  We discussed an approach to break down and focus our efforts in Nova.   We identified the following priority areas: (additional discussions were held on Friday, so this may change) 1. Anything to do with Live migration 2. Logging – improvements 3. vTPM – contribute to work in flight 4. Clean-up of PCI/SRIOV items 5. CAT – wait for T release   Operating system:  Reviewed a big chunk of items and discussed and updated in real time.   We made lots of updates to the google-spreadsheet in real time.  [0]   We agreed to meet again next week and again in 4 weeks.   Regards;   Ian [0] https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMjB7VIrfc/edit?usp=sharing From Brent.Rowsell at windriver.com Mon Sep 17 13:44:58 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Mon, 17 Sep 2018 13:44:58 +0000 Subject: [Starlingx-discuss] FW: PTG upstreaming discussion In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB27078E@ALA-MBD.corp.ad.wrs.com> Forwarding to the ML. Brent -----Original Message----- From: Jolliffe, Ian Sent: Monday, September 17, 2018 9:43 AM To: Rowsell, Brent ; Saul Wold ; Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: PTG upstreaming discussion Hi all; Just a short note to share what Brent, Saul, Dean and I reviewed on Thursday at the PTG last week.  We went through the upstreaming backlog and the notes below summarize the outcomes.  This does not reflect the outcomes of the direct engagement with the Neutron and Nova teams, that summary will follow. We added a new tag – maintain, items which we know we will need to maintain.   Horizon: Eddie and Tyler to get together to review what is left out of STX-GUI and what additional refactoring may be required or patches left to upstream   Keystone: Nothing left after March release due to containerization of Openstack   Python-Clients: items need to map to main project server-side disposition.  Additionally, we agreed we should move the clients as close to master as possible, this can be done independently as this provides users backward compatibility.   Heat: most are related to underlying changes and should be mapped to those items as close as possible.  There are a few bug fixes that can be tackled easily.  Step 1 is to mapping out the dependencies so that the bugs can be focused on.   Glance: raw caching can it be replaced by cinder feature.  Removes several Glance patches.  Lisa and Brent to analyze – emails in flight.   Cinder: in good shape, but, there is work left to do.  We need to identify who can focus on these items up so we can retire the repo.   Ceilometer: Many can be retired, we did a scrub in real time.   Nova: 200 – 300 items to be worked on.  We discussed an approach to break down and focus our efforts in Nova.   We identified the following priority areas: (additional discussions were held on Friday, so this may change) 1. Anything to do with Live migration 2. Logging – improvements 3. vTPM – contribute to work in flight 4. Clean-up of PCI/SRIOV items 5. CAT – wait for T release   Operating system:  Reviewed a big chunk of items and discussed and updated in real time.   We made lots of updates to the google-spreadsheet in real time.  [0]   We agreed to meet again next week and again in 4 weeks.   Regards;   Ian [0] https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMjB7VIrfc/edit?usp=sharing From abraham.arce.moreno at intel.com Mon Sep 17 15:30:28 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 17 Sep 2018 15:30:28 +0000 Subject: [Starlingx-discuss] StarlingX Release Notes Content Message-ID: To all StarlingX main and supporting projects leaders: In preparation to complete our documentation journey we need your help to write under this etherpad page [0] the content for your Release Notes including a Prelude and a couple of features to be added in your project repository, we are targeting this task to be completed if possible, end of this week. Please take a look at the example from Dean in the same etherpad page [0] submitted though a stx-tools gerrit review [1], we will take your information from the Etherpad and we will add it to the Release Notes commit. [0] https://etherpad.openstack.org/p/stx-docs [1] https://review.openstack.org/#/c/600198/3/releasenotes/notes/release-summary-9c35dd1bd9b020f1.yaml From jimmy at openstack.org Mon Sep 17 16:13:47 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Mon, 17 Sep 2018 11:13:47 -0500 Subject: [Starlingx-discuss] Forum Topic Submission Period Message-ID: <5B9FD2BB.3060806@openstack.org> Hello Everyone! The Forum Topic Submission session started September 12 and will run through September 26th. Now is the time to wrangle the topics you gathered during your Brainstorming Phase and start pushing forum topics through. Don't rely only on a PTL to make the agenda... step on up and place the items you consider important front and center. As you may have noticed on the Forum Wiki (https://wiki.openstack.org/wiki/Forum), we're reusing the normal CFP tool this year. We did our best to remove Summit specific language, but if you notice something, just know that you are submitting to the Forum. URL is here: https://www.openstack.org/summit/berlin-2018/call-for-presentations Looking forward to seeing everyone's submissions! If you have questions or concerns about the process, please don't hesitate to reach out. Cheers, Jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Mon Sep 17 16:12:02 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Mon, 17 Sep 2018 16:12:02 +0000 Subject: [Starlingx-discuss] Build installer instructions Message-ID: <036cf4d515df4e287fcd2d52dca3bb795c0a6fc4.camel@intel.com> Hi, I would like to share/discuss the instructions to generate the installer before are publish into the wiki. I couldn't find a previous version of these instructions, probably I confused with this warning from the download_mirror.sh[0]. The update-pxe-network-installer script follows the steps detailed here[1]. Build installer =============== To get your StarlingX ISO ready to use, you will need to create the init files that will be used to boot the ISO as well to boot additional controllers and compute nodes. Once you had run `build-iso`, run: ``` build-pkgs --installer ``` This will build `rpm` and `anaconda` packages. Then run: ``` update-pxe-network-installer ``` The update-pxe-network-installer` covers the steps detailed in `$MY_REPO/stx/stx-metal/installer/initrd/README`. This script will create three files on `/localdisk/loadbuild///pxe- network-installer/output` ``` new-initrd.img new-squashfs.img new-vmlinuz ``` Then, rename them to: ``` initrd.img-stx-0.2 squashfs.img-stx-0.2 vmlinuz-stx-0.2 ``` There are two ways to use these files: 1. Store the files in the '/import/mirror/CentOS/tis-installer/` folder for future use. 2. Store it in an arbitrary location and modify the `$MY_REPO/stx/stx- metal/installer/pxe-network-installer/centos/build_srpm.data` file to point to these files. Now, the `pxe-network-installer` package needs to be recreated and the ISO regenerated. ``` build-pkgs --clean pxe-network-installer build-pkgs pxe-network-installer build-iso ``` Now your ISO should be able to boot. Updating these files is not a common tasks, it is recommended only do it if the kernel version is upgraded or new kernel modules are added. ===================== End of documentation [0] http://git.starlingx.io/cgit/stx-tools/tree/centos-mirror-tools/download_mirror.sh#n264 [1] http://git.starlingx.io/cgit/stx-metal/tree/installer/initrd/README From Nimalini.Rasa at windriver.com Mon Sep 17 16:19:02 2018 From: Nimalini.Rasa at windriver.com (Rasa, Nimalini) Date: Mon, 17 Sep 2018 16:19:02 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B344C22@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B344C22@SHSMSX104.ccr.corp.intel.com> Message-ID: <65CE126717DEA145BD6B2C2842DC52D66C0C7865@ALA-MBD.corp.ad.wrs.com> Yes, the failed test cases were passing on mainline build. -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Friday, September 14, 2018 8:32 PM To: Rasa, Nimalini; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Nimalini, Thanks for the report. Just to ensure, so the below 2 tests were passed in mainline build, correct? Thx. - cindy -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss From Nimalini.Rasa at windriver.com Mon Sep 17 16:21:14 2018 From: Nimalini.Rasa at windriver.com (Rasa, Nimalini) Date: Mon, 17 Sep 2018 16:21:14 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> Message-ID: <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> Hi Shuicheng, In this test case, basically trying to allocate double the amount of 2M pages. For the kernel signature, I tried it on 3 different hardware labs and got the following: controller-0:~$ cat /proc/sys/kernel/tainted 12288 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: module verification failed: signature and/or required key missing - tainting kernel Thanks, Nimalini -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 14, 2018 9:13 PM To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Nimalini, Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? " controller-0:~$ cat /proc/sys/kernel/tainted 4096 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss From Don.Penney at windriver.com Mon Sep 17 16:40:44 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 17 Sep 2018 16:40:44 +0000 Subject: [Starlingx-discuss] Build installer instructions In-Reply-To: <036cf4d515df4e287fcd2d52dca3bb795c0a6fc4.camel@intel.com> References: <036cf4d515df4e287fcd2d52dca3bb795c0a6fc4.camel@intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3B1324@ALA-MBD.corp.ad.wrs.com> It's good to note that if you've already got installer images generated (ie. on a shared system, in /import/mirror/CentOS/tis-installer), you don't need to run "build-pkgs --installer". So presumably, this would not be part of a general designer workflow. Historically, we upversioned these images whenever they were updated, but this introduces some challenges under Starling-X. It may make sense to drop the version number from the images as referenced in the pxe-network-installer package build, essentially treating it as a .latest version. Individuals or groups could then manage their own installer version history as they see fit, ie. build images with 0.1, 0.2, 0.3, with symlinks to the latest perhaps. If these images aren't being hosted somewhere, if individuals/groups are generating their own, then the versioning shouldn't be in the build files. -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Monday, September 17, 2018 12:12 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Build installer instructions Hi, I would like to share/discuss the instructions to generate the installer before are publish into the wiki. I couldn't find a previous version of these instructions, probably I confused with this warning from the download_mirror.sh[0]. The update-pxe-network-installer script follows the steps detailed here[1]. Build installer =============== To get your StarlingX ISO ready to use, you will need to create the init files that will be used to boot the ISO as well to boot additional controllers and compute nodes. Once you had run `build-iso`, run: ``` build-pkgs --installer ``` This will build `rpm` and `anaconda` packages. Then run: ``` update-pxe-network-installer ``` The update-pxe-network-installer` covers the steps detailed in `$MY_REPO/stx/stx-metal/installer/initrd/README`. This script will create three files on `/localdisk/loadbuild///pxe- network-installer/output` ``` new-initrd.img new-squashfs.img new-vmlinuz ``` Then, rename them to: ``` initrd.img-stx-0.2 squashfs.img-stx-0.2 vmlinuz-stx-0.2 ``` There are two ways to use these files: 1. Store the files in the '/import/mirror/CentOS/tis-installer/` folder for future use. 2. Store it in an arbitrary location and modify the `$MY_REPO/stx/stx- metal/installer/pxe-network-installer/centos/build_srpm.data` file to point to these files. Now, the `pxe-network-installer` package needs to be recreated and the ISO regenerated. ``` build-pkgs --clean pxe-network-installer build-pkgs pxe-network-installer build-iso ``` Now your ISO should be able to boot. Updating these files is not a common tasks, it is recommended only do it if the kernel version is upgraded or new kernel modules are added. ===================== End of documentation [0] http://git.starlingx.io/cgit/stx-tools/tree/centos-mirror-tools/download_mirror.sh#n264 [1] http://git.starlingx.io/cgit/stx-metal/tree/installer/initrd/README _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Nimalini.Rasa at windriver.com Mon Sep 17 17:43:12 2018 From: Nimalini.Rasa at windriver.com (Rasa, Nimalini) Date: Mon, 17 Sep 2018 17:43:12 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> Message-ID: <65CE126717DEA145BD6B2C2842DC52D66C0C78BA@ALA-MBD.corp.ad.wrs.com> Hi Shuicheng, The "test_schedule_vm_mempage_config" passed on re-run, it seems like a timing issue where the VM memory has not been released or has not been updated by sysinv-agent audit after the host is locked...fyi Thanks, Nimalini -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 14, 2018 9:13 PM To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Nimalini, Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? " controller-0:~$ cat /proc/sys/kernel/tainted 4096 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss From sgw at linux.intel.com Mon Sep 17 19:58:48 2018 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 17 Sep 2018 12:58:48 -0700 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> Message-ID: <411ced98-b74c-dd7d-a27d-a0447d62c237@linux.intel.com> On 09/17/2018 09:21 AM, Rasa, Nimalini wrote: > Hi Shuicheng, > In this test case, basically trying to allocate double the amount of 2M pages. > > For the kernel signature, I tried it on 3 different hardware labs and got the following: > controller-0:~$ cat /proc/sys/kernel/tainted > 12288 > controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log > 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: module verification failed: signature and/or required key missing - tainting kernel > 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: module verification failed: signature and/or required key missing - tainting kernel > This could be a difference in HW that is being tested. Nimalini and Shuicheng, can you both share your test hardware? But, regardless of hardware it seems that something was not signed correctly or possibly rebuilt. Shuicheng, if you don't have the e1000e hardware, you could still try a modprobe of the kernel-module. Sau! > > Thanks, > Nimalini > > -----Original Message----- > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > Sent: Friday, September 14, 2018 9:13 PM > To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Nimalini, > Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? > > For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? > " > controller-0:~$ cat /proc/sys/kernel/tainted > 4096 > controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " > > Best Regards > Shuicheng > > -----Original Message----- > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > Sent: Saturday, September 15, 2018 3:02 AM > To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Cindy, > Adding more clarification of the test cases that are failed: > > FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] > Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. > > FAIL 20180914 07:57:34 test_kernel_module_signatures > Test case is doing the following: > - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: > - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules > - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module > > > Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. > > Thanks, > Nimalini > > -----Original Message----- > From: Rasa, Nimalini > Sent: Friday, September 14, 2018 12:46 PM > To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada; Lin, Shuicheng > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Cindy, > > Here is the last test update, I am reporting the failed test cases only here: > > From Sanity: > FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) > > From Nightly: > FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] > > LOG: > ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> > [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 > [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... > [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' > [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: > +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ > | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | > | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail > | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | > | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | > +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ > | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | > | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | > +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ > controller-1:~$ > [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' > [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: > 0 > controller-1:~$ > [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] > [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] > [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] > [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] > [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] > [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] > [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] > [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] > [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] > [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] > [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] > [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] > [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 > [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... > [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' > [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: > +--------------------------------+--------------------------------------+ > | Property | Value | > +--------------------------------+--------------------------------------+ > | Memory: Usable Total (MiB) | 7540 | > | Platform (MiB) | 8000 | > | Available (MiB) | 2420 | > | Huge Pages Configured | True | > | vSwitch Huge Pages: Size (MiB) | 1024 | > | Total | 1 | > | Available | 0 | > | VM Pages (4K): Total | 20992 | > | VM Huge Pages (2M): Total | 3258 | > | Total Pending | 2420 | > | Available | 1210 | > | VM Huge Pages (1G): Total | 0 | > | Available | 0 | > | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | > | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | > | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | > | created_at | 2018-09-14T02:30:56.591922+00:00 | > | updated_at | 2018-09-14T06:48:29.882522+00:00 | > +--------------------------------+--------------------------------------+ > controller-1:~$ > [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' > [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: > 0 > > EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: > [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' > [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: > Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 > > > FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] > This test failed b/c of the above test failure (Alarm was present, compute was in locked state) > > > FAIL 20180914 07:57:34 test_kernel_module_signatures > LOG > > [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: > ====================== Test Step 1: Check for unassigned kernel modules on controller-0 > [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... > [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' > [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: > 12288 > controller-0:~$ > [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' > [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: > 0 > controller-0:~$ > [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info > [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: > ====================== Test Step 2: Check kern.log for modules with failed verification > [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... > [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' > [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: > 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel > 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel > 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel > controller-0:~$ > [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' > [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: > 0 > controller-0:~$ > [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: > ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] > [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... > [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' > [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: > filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko > signer: CentOS Linux kernel signing key > sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC > sig_hashalgo: sha256 > controller-0:~$ > [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' > [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: > > > > Thanks, > Nimalini > > -----Original Message----- > From: Xie, Cindy [mailto:cindy.xie at intel.com] > Sent: Thursday, September 13, 2018 10:05 AM > To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada; Lin, Shuicheng > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. > > The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 > > Thanks. - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 9:35 PM > To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Cindy, > > Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. > > -Jason > >> -----Original Message----- >> From: Xie, Cindy >> Sent: September 13, 2018 2:44 AM >> To: Martinez Monroy, Elio ; McKenna, >> Jason ; Waheed, Numan >> ; Rasa, Nimalini >> ; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada ; Lin, Shuicheng >> >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Elio, >> We will provide you an updated ISO later today with the following: >> - kernel upgrade to 3.10.0-862.11.6 >> - symbol issue fixed: >> https://bugs.launchpad.net/starlingx/+bug/1792257 >> >> Please help to do a sanity test based on this new ISO from Shuicheng on VE. >> >> @Jason, >> Please re-generate a build using today's manifest with above fix. >> Shuicheng shall be able to provide manifest with exact commitID. >> @Numan, please abort your current testing w/ old ISO once you get a >> new one from Jason and continue your sanity and regression on >> bare-metal. I am not sure how long it takes, but please take priority >> as we want merge back to mainline early next week. >> >> Thanks all for the support. >> - cindy >> >> -----Original Message----- >> From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] >> Sent: Thursday, September 13, 2018 4:24 AM >> To: Lin, Shuicheng ; Cordoba Malibran, Erich >> ; Waheed, Numan >> ; Rasa, Nimalini >> ; starlingx-discuss at lists.starlingx.io; >> Liu, ZhipengS ; Khalil, Ghada >> ; Xie, Cindy >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >>> -----Original Message----- >>> From: Lin, Shuicheng >>> Sent: September 11, 2018 8:44 PM >>> To: McKenna, Jason ; Cordoba Malibran, >>> Erich ; Waheed, Numan >>> ; Rasa, Nimalini >>> ; starlingx-discuss at lists.starlingx.io; >>> Liu, ZhipengS ; Khalil, Ghada >>> ; Xie, Cindy >>> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >>> >>> Hi Jason, >>> Here is the dhcp src rpm we are using: >>> [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source >>> dhcp >>> http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 >>> - >>> 68.el7.centos.1.src.rpm >>> >>> For centos-release, there are two packages in the mirror lst, 1 src >>> rpm for build, and 1 rpm for the mock environment. And it has the >>> "slightly difference" in the names as you mentioned. >>> Both of them could be found in the centos repo with the exact name. >>> ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm >>> ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm >>> [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source >>> centos- release-7-5.1804.1.el7.centos >>> http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- >>> release-7-5.1804.1.el7.centos.src.rpm >>> [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url >>> centos-release-7- >>> 5.1804.el7.centos.x86_64 >>> http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- >>> release-7-5.1804.el7.centos.x86_64.rpm >>> >>> If there is still some other rpm missing, you could try to find them >>> from the repo. >>> I have try my best to keep my local mirror the same as the lst. But >>> it is still possible some package missed to be added to the repo lst. >>> Please feel free to notify me or correct the error directly. >>> Thanks. >> >> With the latest commits to stx-tools I am now able to download the >> rpms and produce a build. I'll let you know how testing goes >> >>> >>> Best Regards >>> Shuicheng >>> >>> >>> -----Original Message----- >>> From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] >>> Sent: Wednesday, September 12, 2018 12:21 AM >>> To: Cordoba Malibran, Erich ; >>> Waheed, Numan ; Rasa, Nimalini >>> ; starlingx-discuss at lists.starlingx.io; >>> Liu, ZhipengS ; Khalil, Ghada >>> ; Lin, Shuicheng >>> ; Xie, Cindy >>> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >>> >>> Hi Cindy, >>> >>> With the latest centos75 branch (and the cherry-picks you mentioned) >>> I am unable to produce a build. There seems to be several source >>> rpm files missing from the currently pushed version of the .lst >>> files (or the .lst files pull down the wrong version). Most of the >>> missing files I can download manually, however the checked in >>> patches for dhcp and centos-release packages do not apply against >>> the version of the source RPM which I can manually find on the >>> Internet. For example, the version of centos-release called out in >>> the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the >>> version called out in the checked in code base is the slightly >>> different >>> centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches >> checked in do not apply against either package. >>> >>> Until the centos75 branch of the lst files pulls down the correct >>> rpms, I will be unable to continue the validation effort. >>> >>> -J >>> >>>> -----Original Message----- >>>> From: Cordoba Malibran, Erich >>>> Sent: September 11, 2018 11:17 AM >>>> To: Waheed, Numan ; Rasa, Nimalini >>>> ; >>>> starlingx-discuss at lists.starlingx.io; >>>> Liu, ZhipengS ; Khalil, Ghada >>>> ; Lin, Shuicheng >>>> ; McKenna, Jason >>>> ; Xie, Cindy >>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update >>>> >>>> Hi >>>> >>>> You can add "debug loglevel=8" to the kernel boot option to get a >>>> more detailed output of the crash (if any) >>>> >>>> -Erich >>>> >>>> On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: >>>>> Shuicheng saw the symbol table error issue as well but it >>>>> recovers in 8s, he is still working on debugging it. But 601204 >>>>> is just kernel upgrade but not intended to solve this issues. >>>>> Are you running bare metal? I am wondering if this is HW config and driver issue. >>>>> >>>>> Is it possible that you try to deploy it in virtual environment? >>>>> >>>>> Thx. - cindy >>>>> >>>>> From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] >>>>> Sent: Tuesday, September 11, 2018 9:50 PM >>>>> To: Xie, Cindy ; Rasa, Nimalini >>>>> ; Waheed, Numan >>>>> ; Lin, Shuicheng >>>>> ; Liu, ZhipengS >>>> l.com>; Khalil, Ghada ; >>>>> 'starlingx-discus s at lists.starlingx.io' >>>>> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Hi Cindy, >>>>> >>>>> We got past the installation device error, but are coming up >>>>> against the symbol table error. Our system hangs after this >>>>> message. I suspect a kernel issue. I see there is an open code >>>>> review to refactor some kernel patches to a rebased kernel >>>>> (https://review.open >>>>> stack.org/#/c/601204/) but I do not know if that is expected to >>>>> resolve the issue >>>>> >>>>> -J >>>>> >>>>> From: Xie, Cindy >>>>> Sent: September 11, 2018 9:32 AM >>>>> To: Rasa, Nimalini ; Waheed, Numan >>>> >>>> n.Waheed at windriver.com>; Lin, Shuicheng >> ; >>>>> McKenna, Jason ; Liu, ZhipengS >>>> >>>> .liu at intel.com>; Khalil, Ghada ; >>>>> 'starlin gx-discuss at lists.starlingx.io' >>>>> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> But as Jason reported yesterday, the build cannot be installed >>>>> with error messages: >>>>> >>>>> Installation failed. >>>>> ERROR: Specified installation (sda) or boot (sda) device is invalid. >>>>> >>>>> We cannot debug without more information, the ISO installs in >>>>> Intel’s HW. Thus Shuicheng created a new build and attached a >>>>> manifest in this email thread. Did WindRiver has a chance to >>>>> create a new ISO using today’s manifest file and re-run the test? >>>>> >>>>> Thx. - cindy >>>>> >>>>> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] >>>>> Sent: Tuesday, September 11, 2018 9:25 PM >>>>> To: Xie, Cindy ; Waheed, Numan >>>> >>>> driver.com>; Lin, Shuicheng ; McKenna, >>>>> Jason ; Liu, ZhipengS >>>> >>>>> ; Khalil, Ghada ; >>>>> 'starlingx-discuss at list s.starlingx.io' >>>>> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> This is on the same build (yesterday’s build). >>>>> >>>>> From: Xie, Cindy [mailto:cindy.xie at intel.com] >>>>> Sent: Tuesday, September 11, 2018 9:22 AM >>>>> To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, >>>>> Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Is this the same issue as yesterday’s build? or this is >>>>> different issue now? >>>>> >>>>> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] >>>>> Sent: Tuesday, September 11, 2018 9:06 PM >>>>> To: Waheed, Numan ; Lin, >> Shuicheng >>>> >>>> heng.lin at intel.com>; McKenna, Jason >>> ; >>>>> Liu, ZhipengS ; Khalil, Ghada >>>>> ; >>>>> 'starlingx-discuss at lists.starlingx.io' >>>> uss at lists.starlingx.io>; Xie, Cindy >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> It is not booting in my case. After the following , it just >>>>> hangs >>>>> there: >>>>> “Error: no symbol table. >>>>> Press any key to continue…” >>>>> >>>>> -Nimalini >>>>> >>>>> From: Waheed, Numan >>>>> Sent: Tuesday, September 11, 2018 8:50 AM >>>>> To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, >>>>> Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; >>>>> Rasa, Nimalini >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Adding Nimalini >>>>> >>>>> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >>>>> Sent: September-11-18 2:17 AM >>>>> To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; >>>>> 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, >>>>> Numan >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Hi Jason, >>>>> Just finished deploy image with latest code, I could config >>>>> controller successfully in bare metal environment. >>>>> Manifest is created for you reference. There are two patches I >>>>> add >>>>> manually: >>>>> https://review.openstack.org/596855           for >>>>> python-horizon from master >>>>> https://review.openstack.org/599892           for build-iso >>>>> >>>>> >>>>> There is an issue found when reboot controller node. >>>>> After the OS selection menu, it will show below error. And it >>>>> will auto continue boot after around 8 seconds. I will check the >>>>> issue later. >>>>> “ >>>>> Error: no symbol table. >>>>> Press any key to continue… >>>>> “ >>>>> >>>>> Best Regards >>>>> Shuicheng >>>>> >>>>> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >>>>> Sent: Tuesday, September 11, 2018 9:35 AM >>>>> To: McKenna, Jason ; Liu, ZhipengS >>>> >>>> engs.liu at intel.com>; Khalil, Ghada ; >>>>> 'sta rlingx-discuss at lists.starlingx.io' >>>>> >>>> .io>; Xie, Cindy ; Waheed, Numan >>>> >>>> indriver.com> >>>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status >>>>> update >>>>> >>>>> Hi Jason, >>>>> I just tried my last Friday’s image at bare metal machine. There >>>>> is no issue to install controller node. >>>>> Will you help check what cause the install error in your environment? >>>>> >>>>> I am syncing my code to latest to double confirm it. >>>>> >>>>> Best Regards >>>>> Shuicheng >>>>> >>>>> From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] >>>>> Sent: Tuesday, September 11, 2018 12:13 AM >>>>> To: Liu, ZhipengS ; Lin, Shuicheng >>>>> ; Khalil, Ghada >>>>> ; 'starlin >>>>> gx-discuss at lists.starlingx.io' >>>>> >>>>> ; Xie, Cindy ; Waheed, Numan >>>> >>>> iver.com> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Status update. The build from the centos75 branch does not >>>>> install on our hardware. The error message we are seeing is: >>>>> >>>>> Installation failed. >>>>> >>>>> ERROR: Specified installation (sda) or boot (sda) device is invalid. >>>>> >>>>> -Jason >>>>> >>>>> From: Liu, ZhipengS >>>>> Sent: September 8, 2018 9:56 AM >>>>> To: Lin, Shuicheng ; McKenna, Jason >>>>> ; Khalil, Ghada >>>>> ; 's >>>>> tarlingx-discuss at lists.starlingx.io' >>>>> ; Xie, Cindy >>>>> ; Waheed, Numan >>>> >>>> @windriver.com> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Hi Jason, >>>>> >>>>> I have fixed the issue you mentioned below. >>>>> - Furthermore, the tpm2-tools package was requesting version >>>>> tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). >>>>> I hacked the spec file for tpm2-tools and rebuilt it to require >>>>> the version mentioned, but there is some rework to be done there. >>>>> [slin14]: I have the same issue also. Let’s further check it to >>>>> find the root cause. I use rebuild tpm2-tools/tss2 to workaround >>>>> it without any code. >>>>> >>>>> https://review.openstack.org/#/c/600920/ >>>>> >>>>> Thanks! >>>>> Zhipeng >>>>> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >>>>> Sent: 2018年9月8日 21:14 >>>>> To: McKenna, Jason ; Khalil, Ghada >>>> >>>> a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' >>>>> ; Xie, Cindy >>>>> ; Waheed, Numan >>> >>>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status >>>>> update >>>>> >>>>> Hi Jason, >>>>> I have fixed the error in the openstack-aodh. Patch is updated: >>>>> https://review.openstack.org/#/c/598388/ >>>>> >>>>> It is due to my local version is not the latest one. >>>>> Sorry for the trouble caused, and thanks for your test. >>>>> >>>>> Best Regards >>>>> Shuicheng >>>>> >>>>> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >>>>> Sent: Saturday, September 8, 2018 9:23 AM >>>>> To: McKenna, Jason ; Khalil, Ghada >>>> >>>> a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' >>>>> ; Xie, Cindy >>>>> ; Waheed, Numan >>> >>>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status >>>>> update >>>>> >>>>> Hi Jason, >>>>> Thanks very much for such detail feedback. >>>>> I added some comments inline, and will check the issue in my >>>>> environment also. >>>>> Feel free to submit patch if you have to fix them. J >>>>> >>>>> >>>>> Best Regards >>>>> Shuicheng >>>>> >>>>> From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] >>>>> Sent: Saturday, September 8, 2018 3:47 AM >>>>> To: McKenna, Jason ; Khalil, Ghada >>>> >>>> a.Khalil at windriver.com>; Lin, Shuicheng >>>>> ; 's tarlingx-discuss at lists.starlingx.io' >>>>> ; Xie, Cindy >>>>> ; Waheed, Numan >>>> >>>> @windriver.com> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Hi Shuicheng, >>>>> >>>>> I’ve completed a build of the code. We have not yet run >>>>> run-time tests, but here are the build-time issues I encountered: >>>>> >>>>> - The .lst file contains lighttpd-1.4.49, but this is no >>>>> longer available for download, and the download_mirrors.sh step fails. >>>>> It appears than CentOS has updated to lighttpd-1.4.50. I >>>>> manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst >>>>> - Even though the .lst file specifies lighttpd-1.4.49, the >>>>> code still references 1.4.45 >>>>> - At build-pkgs time (the build-srpms step), the meta-patches >>>>> to openstack-aodh do not apply, as two of them are malformed. https: >>>>> //review.openstack.org/#/c/598388/6/openstack/openstack- >>>>> aodh/centos/meta_patches/0001-Modify-service-files-and-create- >>>>> expirer-cron-script.patch -- In the new version, on line 190, >>>>> the patch states that the old code covered 6 lines, and the new >>>>> code covers 9 lines (-283,6 +286,9). But there are only two >>>>> lines inserted by the patch. There is also a new blank line in >>>>> the patch at line 194. Removing this blank line and editing the >>>>> hunk description to only insert 2 lines resolves the issue for >>>>> this hunk (there are other similar issues in this patch, and in >>>>> 0001-meta- >>>>> modify-aodh-api.patch) >>>>> [slin14]: Let me double check it. >>>>> - At binary build time, I had build failures on python-django- >>>>> horizon and some magnum packages. I had to pull in >>>>> https://review.op >>>>> enstack.org/#/c/596855/2 (from the master branch, but not in the >>>>> centos75 branch of stx-upstream) to get past this. >>>>> [slin14]: It is due to I have not synced latest master code, so >>>>> I don’t have this issue. I used last week’s master code. >>>>> - After building all packages, I attempted to build the ISO. >>>>> The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and >>>>> should be added to the .lst files. >>>>> [slin14]: This package is already in the lst. >>>>> - Furthermore, the tpm2-tools package was requesting version >>>>> tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). >>>>> I hacked the spec file for tpm2-tools and rebuilt it to require >>>>> the version mentioned, but there is some rework to be done there. >>>>> [slin14]: I have the same issue also. Let’s further check it to >>>>> find the root cause. I use rebuild tpm2-tools/tss2 to workaround >>>>> it without any code. >>>>> >>>>> After these changes, I was able to produce a .iso >>>>> >>>>> -Jason >>>>> >>>>> From: McKenna, Jason >>>>> Sent: September 7, 2018 10:08 AM >>>>> To: Khalil, Ghada ; Lin, Shuicheng >>>>> ; 'starlingx-discuss at lists.starlingx.io' >>>>> ; Xie, Cindy >>>>> ; Waheed, Numan >>> >>>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status >>>>> update >>>>> >>>>> Hi Shuicheng, >>>>> >>>>> As a download_mirrors.sh time issue, the version of lighttpd has >>>>> been changed from 1.4.45 to 1.4.49. The >>>>> lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or >>>>> CentOS servers, as they’ve moved to 1.4.50. I am attempting to >>>>> locate an archived version of the 1.4.49 .src rpm. >>>>> >>>>> -Jason >>>>> >>>>> From: Khalil, Ghada >>>>> Sent: September 7, 2018 9:36 AM >>>>> To: Lin, Shuicheng ; >>>>> 'starlingx-discuss at list s.starlingx.io' >>>>> ; Xie, Cindy >>>> indy.xie at intel.com>; Waheed, Numan >>> >>>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status >>>>> update >>>>> >>>>> Thanks Shuicheng. We’ll run some tests in Wind River. Numan will >>>>> be priming this activity. He’ll share the results with the team >>>>> sometime next week. >>>>> >>>>> Regards, >>>>> Ghada >>>>> >>>>> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >>>>> Sent: Friday, September 07, 2018 1:32 AM >>>>> To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, >>>>> Cindy >>>>> Subject: CentOS 7.5 upgrade status update >>>>> >>>>> Hi all, >>>>> Most task of CentOS7.5 upgrade in story 2003389 is done. Please >>>>> go ahead to have a try and verify it. >>>>> I expect there should be some issue due to we just did limited >>>>> deploy test yet. >>>>> >>>>> Here is the detail status update of this week. >>>>> For the total 44 srpm we plan to upgrade: >>>>> 38 already merged in feature branch. >>>>> 3 kept as original version. Anaconda upgrade is not needed. >>>>> python- os-vif has higher version than 7.5. python-eventlet kept >>>>> due to new src rpm itself have known issue. >>>>> 2 under review with code ready. Puppet-haproxy and openstack-aodh. >>>>> 1 under debug. Lighttpd. >>>>> >>>>> Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. >>>>> >>>>> Here is the build instruction: >>>>> 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- >>>>> upstream/stx-root. >>>>> Cherry-pick below un-merged patch: >>>>> For puppet-haproxy: >>>>> https://review.openstack.org/600369 >>>>> https://review.openstack.org/600359 >>>>> For openstack-aodh: >>>>> https://review.openstack.org/598388 >>>>> https://review.openstack.org/600591 >>>>> For build-iso: >>>>> https://review.openstack.org/599892 >>>>> For build-pkgs: >>>>> https://review.openstack.org/599901 >>>>> https://review.openstack.org/600639 >>>>> >>>>> 2. Run mirror script to get the upgraded src rpm and related >>>>> rpm. >>>>> 3. Try to build packages and ISO. >>>>> >>>>> For the detail status of CentOS7.5 upgrade, please check below story: >>>>> https://storyboard.openstack.org/#!/story/2003389 >>>>> >>>>> Feel free to contact me if you have trouble on it. >>>>> >>>>> Best Regards >>>>> Shuicheng >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis >>>>> cu >>>>> ss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From bruce.e.jones at intel.com Mon Sep 17 20:54:43 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 17 Sep 2018 20:54:43 +0000 Subject: [Starlingx-discuss] RFC: Updated governance doc on the wiki Message-ID: <9A85D2917C58154C960D95352B22818BAB58FEA1@fmsmsx115.amr.corp.intel.com> I have updated our draft Governance document based on feedback from the PTG. Please review and send me any feedback you have. https://wiki.openstack.org/wiki/Starlingx/Initial_Governance Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Numan.Waheed at windriver.com Mon Sep 17 20:58:55 2018 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Mon, 17 Sep 2018 20:58:55 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE481F6113@ALA-MBD.corp.ad.wrs.com> Hi, Following testing was done for testing CentOS7.5 on a custom build created by Jason: Load: SW_VERSION="18.08" BUILD_TARGET="Unknown" BUILD_TYPE="Informal" BUILD_ID="n/a" JOB="n/a" BUILD_BY="jmckenna" BUILD_NUMBER="n/a" BUILD_HOST="yow-cgts1-lx" BUILD_DATE="2018-09-13 10:42:03 -0400" BUILD_DIR="/" WRS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root" WRS_GIT_BRANCH="HEAD" CGCS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root/stx" CGCS_GIT_BRANCH="HEAD" Sanity - 23 Test Cases Nightly Regression - 46 Test Cases (1 Failure for Kernel module Signature – tested and reproduced on three different labs) Nova Regression - Executed on three labs (AIO-SX, Standard and Storage Lab) - Labs covered Mellanox, Niantic and Fortville NICs - AIO-SX: o Test Cases Executed: 209 o Passed: 204 o Failed: 5 (3 known issues, 1 Ping issue, 1 timing issue that passed on re-execution) - Standard Lab: o Test Cases Executed: 373 o Passed: 346 o Failed: 27 (6 known issues, 1 ping issue, 20 passed on re-execution) - Storage: o Test Cases Executed: 374 o Passed: 367 o Failed: 7 (6 issues also seen in STX branch without CentOS7.5, 1 test case passed on re-execution) Failed test cases were re-executed and majority of them passed on re-execution. The remaining failed test cases are also failing on STX build without CentOS7.5 update. Hence, the failures are not caused by CentOS7.5 update. The main issue seen so far is only about Kernel Signature. Another issue seen is no Inventory tab available in Horizon. However, that does not seem to be related to CentOS update. Thanks, Numan. -----Original Message----- From: Rasa, Nimalini Sent: September-17-18 12:21 PM To: Lin, Shuicheng; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, In this test case, basically trying to allocate double the amount of 2M pages. For the kernel signature, I tried it on 3 different hardware labs and got the following: controller-0:~$ cat /proc/sys/kernel/tainted 12288 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: module verification failed: signature and/or required key missing - tainting kernel Thanks, Nimalini -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 14, 2018 9:13 PM To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Nimalini, Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? " controller-0:~$ cat /proc/sys/kernel/tainted 4096 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss From bruce.e.jones at intel.com Mon Sep 17 21:55:19 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 17 Sep 2018 21:55:19 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE481F6113@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> <3CAA827B7A79BA46B15B280EC82088FE481F6113@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB58FF8E@fmsmsx115.amr.corp.intel.com> Numan, thank you, my take away from this is that the upgrade is looking pretty good. Is there a bug opened for the kernel signature issue? brucej -----Original Message----- From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] Sent: Monday, September 17, 2018 1:59 PM To: Rasa, Nimalini ; Lin, Shuicheng ; Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi, Following testing was done for testing CentOS7.5 on a custom build created by Jason: Load: SW_VERSION="18.08" BUILD_TARGET="Unknown" BUILD_TYPE="Informal" BUILD_ID="n/a" JOB="n/a" BUILD_BY="jmckenna" BUILD_NUMBER="n/a" BUILD_HOST="yow-cgts1-lx" BUILD_DATE="2018-09-13 10:42:03 -0400" BUILD_DIR="/" WRS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root" WRS_GIT_BRANCH="HEAD" CGCS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root/stx" CGCS_GIT_BRANCH="HEAD" Sanity - 23 Test Cases Nightly Regression - 46 Test Cases (1 Failure for Kernel module Signature – tested and reproduced on three different labs) Nova Regression - Executed on three labs (AIO-SX, Standard and Storage Lab) - Labs covered Mellanox, Niantic and Fortville NICs - AIO-SX: o Test Cases Executed: 209 o Passed: 204 o Failed: 5 (3 known issues, 1 Ping issue, 1 timing issue that passed on re-execution) - Standard Lab: o Test Cases Executed: 373 o Passed: 346 o Failed: 27 (6 known issues, 1 ping issue, 20 passed on re-execution) - Storage: o Test Cases Executed: 374 o Passed: 367 o Failed: 7 (6 issues also seen in STX branch without CentOS7.5, 1 test case passed on re-execution) Failed test cases were re-executed and majority of them passed on re-execution. The remaining failed test cases are also failing on STX build without CentOS7.5 update. Hence, the failures are not caused by CentOS7.5 update. The main issue seen so far is only about Kernel Signature. Another issue seen is no Inventory tab available in Horizon. However, that does not seem to be related to CentOS update. Thanks, Numan. -----Original Message----- From: Rasa, Nimalini Sent: September-17-18 12:21 PM To: Lin, Shuicheng; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, In this test case, basically trying to allocate double the amount of 2M pages. For the kernel signature, I tried it on 3 different hardware labs and got the following: controller-0:~$ cat /proc/sys/kernel/tainted 12288 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: module verification failed: signature and/or required key missing - tainting kernel Thanks, Nimalini -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 14, 2018 9:13 PM To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Nimalini, Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? " controller-0:~$ cat /proc/sys/kernel/tainted 4096 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Mon Sep 17 22:23:08 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 17 Sep 2018 22:23:08 +0000 Subject: [Starlingx-discuss] Bug Handling Process / Useful Launchpad Bugs / Focus on stx.2018.10 Bugs Message-ID: <151EE31B9FCCA54397A757BC674650F0BA453BF3@ALA-MBD.corp.ad.wrs.com> Hello all, I've documented details of the StarlingX Bug Handling process on the wiki: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process Please review and let me know if you have any feedback. All feedback is welcome. In the above wiki, I have included links to useful Launchpad bugs: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process#Key_StarlingX_Bug_Queries With the team's focus on stx.2018.10, I have created specific queries for the release. Project Leads, Please have a look at the unassigned stx.2018.10 bugs and assign to the team accordingly. Please also track all stx.2018.10 bugs to resolution as part of your regular team meetings/communication. Thanks, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273 skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Mon Sep 17 23:18:55 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 17 Sep 2018 18:18:55 -0500 Subject: [Starlingx-discuss] RFC: Updated governance doc on the wiki In-Reply-To: <9A85D2917C58154C960D95352B22818BAB58FEA1@fmsmsx115.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB58FEA1@fmsmsx115.amr.corp.intel.com> Message-ID: On Mon, Sep 17, 2018 at 3:54 PM, Jones, Bruce E wrote: > I have updated our draft Governance document based on feedback from the PTG. > Please review and send me any feedback you have. I made a minor formatting change to reduce the emphasis on company affiliation in the initial TSC membership and decided I wanted to do more for clarity without changing the intent. I will propose the changes here to include some rationale initially before further editing the wiki: > We are actively recruiting for additional Technical Steering Committee members Strike this, it does not feel appropriate for a governance doucment > In September 2019, 3 of the 7 seats will be up for election by the project's Contributors. Anyone who is a Contributor to the project will be eligible to run, and anyone who is a Contributor is eligible to vote. s/will be/is/.. Should use 'is' in both places in that sentence. > In that election the TSC positions held by one each of the members from Wind River and Intel will be opened for election, to be determined randomly. In April 2020, the remaining 4 seats will be up for election. In that election, the other initial TSC members from Wind River and Intel will be opened for election. Strike the last sentence above, it is redundant, suggest replace with: At that time all initially appointed TSC terms will have been replaced by elected terms. > TSC elections will continue on this staggered cycle (3 seats and 4 seats) every six months in order to allow new leaders to rise up and ensure some consistency across the terms. TSC members will serve at least one year terms after the initial bootstrapping phase. There are no term limits, but in order to encourage diversity, no more than 2 of the 7 seats can be filled by any one organization. Suggest alternative: TSC Elections will continue on a staggered six month cycle (3 seats and 4 seats) in order to ensure consistency across terms while allowing new leaders to begin to serve. There are no limits on the number of terms an individual may serve, but no single organization may be represented by more than two seats at any given time. For clarity, here is the rewritten paragraph: In September 2019, 3 of the 7 seats will be up for election by the project's Contributors. Anyone who is a Contributor to the project will be eligible to run, and anyone who is a Contributor is eligible to vote. In that election the TSC positions held by one each of the members from Wind River and Intel will be opened for election, to be determined randomly. In April 2020, the remaining 4 seats will be up for election. At that time all initially appointed TSC terms will have been replaced by elected terms. TSC Elections will continue on a staggered six month cycle (3 seats and 4 seats) in order to ensure consistency across terms while allowing new leaders to begin to serve. There are no limits on the number of terms an individual may serve, but no single organization may be represented by more than two seats at any given time. > The Technical Steering Committee will meet regularly in an open forum with times and locations published in community channels. The Technical Steering Committee can elect a Chair at its discretion. Meetings with be hosted and facilitated by the OpenStack Foundation. The meeting facillitation and hosting doesn't seem like something to be codified in governance? > Voting within the TSC requires a quorum of 5 members present. In the initial phase when the TSC does not have 5 members, a quorum will be 4 members. TSC members should seek consensus on most technical issues but if needed they can be resolved through a simple majority vote. Voting to create a new or archive an inactive StarlingX sub-project or to change the project's formal Governance document requires a 2/3rds super-majority. How about this: A quorum for the TSC requires more than half of the members. (When the TSC membership is an even number, this means half + 1.) The TSC should seek consensus on issues and decisions however a simple majority vote shall be sufficient for most resolutions. Certain resolutions, specifically changing the project formal governance (including this document) and changes to project structure (adding or removing a sub-project) require a two-thirds majority vote. ((If there are more super-majority things we need to list them here)) dt -- Dean Troyer dtroyer at gmail.com From cindy.xie at intel.com Mon Sep 17 23:24:36 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 17 Sep 2018 23:24:36 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9A85D2917C58154C960D95352B22818BAB58FF8E@fmsmsx115.amr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> <3CAA827B7A79BA46B15B280EC82088FE481F6113@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB58FF8E@fmsmsx115.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B3478E5@SHSMSX104.ccr.corp.intel.com> The case " test_kernel_module_signatures" seems passing on Shuicheng's system. We will provide the HW config to compare. But Numan, please open up a Launchpad ticket so that we can track there. My read for Numan's test report is also good. I think we are OK to merge back to mainline unless we hear objections? Thx. - cindy -----Original Message----- From: Jones, Bruce E Sent: Tuesday, September 18, 2018 5:55 AM To: Waheed, Numan ; Rasa, Nimalini ; Lin, Shuicheng ; Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Numan, thank you, my take away from this is that the upgrade is looking pretty good. Is there a bug opened for the kernel signature issue? brucej -----Original Message----- From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] Sent: Monday, September 17, 2018 1:59 PM To: Rasa, Nimalini ; Lin, Shuicheng ; Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi, Following testing was done for testing CentOS7.5 on a custom build created by Jason: Load: SW_VERSION="18.08" BUILD_TARGET="Unknown" BUILD_TYPE="Informal" BUILD_ID="n/a" JOB="n/a" BUILD_BY="jmckenna" BUILD_NUMBER="n/a" BUILD_HOST="yow-cgts1-lx" BUILD_DATE="2018-09-13 10:42:03 -0400" BUILD_DIR="/" WRS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root" WRS_GIT_BRANCH="HEAD" CGCS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root/stx" CGCS_GIT_BRANCH="HEAD" Sanity - 23 Test Cases Nightly Regression - 46 Test Cases (1 Failure for Kernel module Signature – tested and reproduced on three different labs) Nova Regression - Executed on three labs (AIO-SX, Standard and Storage Lab) - Labs covered Mellanox, Niantic and Fortville NICs - AIO-SX: o Test Cases Executed: 209 o Passed: 204 o Failed: 5 (3 known issues, 1 Ping issue, 1 timing issue that passed on re-execution) - Standard Lab: o Test Cases Executed: 373 o Passed: 346 o Failed: 27 (6 known issues, 1 ping issue, 20 passed on re-execution) - Storage: o Test Cases Executed: 374 o Passed: 367 o Failed: 7 (6 issues also seen in STX branch without CentOS7.5, 1 test case passed on re-execution) Failed test cases were re-executed and majority of them passed on re-execution. The remaining failed test cases are also failing on STX build without CentOS7.5 update. Hence, the failures are not caused by CentOS7.5 update. The main issue seen so far is only about Kernel Signature. Another issue seen is no Inventory tab available in Horizon. However, that does not seem to be related to CentOS update. Thanks, Numan. -----Original Message----- From: Rasa, Nimalini Sent: September-17-18 12:21 PM To: Lin, Shuicheng; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, In this test case, basically trying to allocate double the amount of 2M pages. For the kernel signature, I tried it on 3 different hardware labs and got the following: controller-0:~$ cat /proc/sys/kernel/tainted 12288 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: module verification failed: signature and/or required key missing - tainting kernel Thanks, Nimalini -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 14, 2018 9:13 PM To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Nimalini, Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? " controller-0:~$ cat /proc/sys/kernel/tainted 4096 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Mon Sep 17 23:25:35 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 17 Sep 2018 23:25:35 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B3478E5@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> <3CAA827B7A79BA46B15B280EC82088FE481F6113@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB58FF8E@fmsmsx115.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B3478E5@SHSMSX104.ccr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB59012F@fmsmsx115.amr.corp.intel.com> > My read for Numan's test report is also good. I think we are OK to merge back to mainline unless we hear objections? Suggest we discuss this at the project team call Wednesday morning but yes, it's looking good. brucej -----Original Message----- From: Xie, Cindy Sent: Monday, September 17, 2018 4:25 PM To: Jones, Bruce E ; Waheed, Numan ; Rasa, Nimalini ; Lin, Shuicheng ; McKenna, Jason ; Martinez Monroy, Elio ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update The case " test_kernel_module_signatures" seems passing on Shuicheng's system. We will provide the HW config to compare. But Numan, please open up a Launchpad ticket so that we can track there. My read for Numan's test report is also good. I think we are OK to merge back to mainline unless we hear objections? Thx. - cindy -----Original Message----- From: Jones, Bruce E Sent: Tuesday, September 18, 2018 5:55 AM To: Waheed, Numan ; Rasa, Nimalini ; Lin, Shuicheng ; Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Numan, thank you, my take away from this is that the upgrade is looking pretty good. Is there a bug opened for the kernel signature issue? brucej -----Original Message----- From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] Sent: Monday, September 17, 2018 1:59 PM To: Rasa, Nimalini ; Lin, Shuicheng ; Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi, Following testing was done for testing CentOS7.5 on a custom build created by Jason: Load: SW_VERSION="18.08" BUILD_TARGET="Unknown" BUILD_TYPE="Informal" BUILD_ID="n/a" JOB="n/a" BUILD_BY="jmckenna" BUILD_NUMBER="n/a" BUILD_HOST="yow-cgts1-lx" BUILD_DATE="2018-09-13 10:42:03 -0400" BUILD_DIR="/" WRS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root" WRS_GIT_BRANCH="HEAD" CGCS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root/stx" CGCS_GIT_BRANCH="HEAD" Sanity - 23 Test Cases Nightly Regression - 46 Test Cases (1 Failure for Kernel module Signature – tested and reproduced on three different labs) Nova Regression - Executed on three labs (AIO-SX, Standard and Storage Lab) - Labs covered Mellanox, Niantic and Fortville NICs - AIO-SX: o Test Cases Executed: 209 o Passed: 204 o Failed: 5 (3 known issues, 1 Ping issue, 1 timing issue that passed on re-execution) - Standard Lab: o Test Cases Executed: 373 o Passed: 346 o Failed: 27 (6 known issues, 1 ping issue, 20 passed on re-execution) - Storage: o Test Cases Executed: 374 o Passed: 367 o Failed: 7 (6 issues also seen in STX branch without CentOS7.5, 1 test case passed on re-execution) Failed test cases were re-executed and majority of them passed on re-execution. The remaining failed test cases are also failing on STX build without CentOS7.5 update. Hence, the failures are not caused by CentOS7.5 update. The main issue seen so far is only about Kernel Signature. Another issue seen is no Inventory tab available in Horizon. However, that does not seem to be related to CentOS update. Thanks, Numan. -----Original Message----- From: Rasa, Nimalini Sent: September-17-18 12:21 PM To: Lin, Shuicheng; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, In this test case, basically trying to allocate double the amount of 2M pages. For the kernel signature, I tried it on 3 different hardware labs and got the following: controller-0:~$ cat /proc/sys/kernel/tainted 12288 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: module verification failed: signature and/or required key missing - tainting kernel Thanks, Nimalini -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 14, 2018 9:13 PM To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Nimalini, Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? " controller-0:~$ cat /proc/sys/kernel/tainted 4096 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Mon Sep 17 23:32:22 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 17 Sep 2018 23:32:22 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9A85D2917C58154C960D95352B22818BAB59012F@fmsmsx115.amr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> <3CAA827B7A79BA46B15B280EC82088FE481F6113@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB58FF8E@fmsmsx115.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B3478E5@SHSMSX104.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB59012F@fmsmsx115.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B34793B@SHSMSX104.ccr.corp.intel.com> Yes, let's discuss that. I did send out the agenda including a decision required for merge back. -----Original Message----- From: Jones, Bruce E Sent: Tuesday, September 18, 2018 7:26 AM To: Xie, Cindy ; Waheed, Numan ; Rasa, Nimalini ; Lin, Shuicheng ; McKenna, Jason ; Martinez Monroy, Elio ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > My read for Numan's test report is also good. I think we are OK to merge back to mainline unless we hear objections? Suggest we discuss this at the project team call Wednesday morning but yes, it's looking good. brucej -----Original Message----- From: Xie, Cindy Sent: Monday, September 17, 2018 4:25 PM To: Jones, Bruce E ; Waheed, Numan ; Rasa, Nimalini ; Lin, Shuicheng ; McKenna, Jason ; Martinez Monroy, Elio ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update The case " test_kernel_module_signatures" seems passing on Shuicheng's system. We will provide the HW config to compare. But Numan, please open up a Launchpad ticket so that we can track there. My read for Numan's test report is also good. I think we are OK to merge back to mainline unless we hear objections? Thx. - cindy -----Original Message----- From: Jones, Bruce E Sent: Tuesday, September 18, 2018 5:55 AM To: Waheed, Numan ; Rasa, Nimalini ; Lin, Shuicheng ; Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Numan, thank you, my take away from this is that the upgrade is looking pretty good. Is there a bug opened for the kernel signature issue? brucej -----Original Message----- From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] Sent: Monday, September 17, 2018 1:59 PM To: Rasa, Nimalini ; Lin, Shuicheng ; Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi, Following testing was done for testing CentOS7.5 on a custom build created by Jason: Load: SW_VERSION="18.08" BUILD_TARGET="Unknown" BUILD_TYPE="Informal" BUILD_ID="n/a" JOB="n/a" BUILD_BY="jmckenna" BUILD_NUMBER="n/a" BUILD_HOST="yow-cgts1-lx" BUILD_DATE="2018-09-13 10:42:03 -0400" BUILD_DIR="/" WRS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root" WRS_GIT_BRANCH="HEAD" CGCS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root/stx" CGCS_GIT_BRANCH="HEAD" Sanity - 23 Test Cases Nightly Regression - 46 Test Cases (1 Failure for Kernel module Signature – tested and reproduced on three different labs) Nova Regression - Executed on three labs (AIO-SX, Standard and Storage Lab) - Labs covered Mellanox, Niantic and Fortville NICs - AIO-SX: o Test Cases Executed: 209 o Passed: 204 o Failed: 5 (3 known issues, 1 Ping issue, 1 timing issue that passed on re-execution) - Standard Lab: o Test Cases Executed: 373 o Passed: 346 o Failed: 27 (6 known issues, 1 ping issue, 20 passed on re-execution) - Storage: o Test Cases Executed: 374 o Passed: 367 o Failed: 7 (6 issues also seen in STX branch without CentOS7.5, 1 test case passed on re-execution) Failed test cases were re-executed and majority of them passed on re-execution. The remaining failed test cases are also failing on STX build without CentOS7.5 update. Hence, the failures are not caused by CentOS7.5 update. The main issue seen so far is only about Kernel Signature. Another issue seen is no Inventory tab available in Horizon. However, that does not seem to be related to CentOS update. Thanks, Numan. -----Original Message----- From: Rasa, Nimalini Sent: September-17-18 12:21 PM To: Lin, Shuicheng; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, In this test case, basically trying to allocate double the amount of 2M pages. For the kernel signature, I tried it on 3 different hardware labs and got the following: controller-0:~$ cat /proc/sys/kernel/tainted 12288 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: module verification failed: signature and/or required key missing - tainting kernel Thanks, Nimalini -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 14, 2018 9:13 PM To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Nimalini, Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? " controller-0:~$ cat /proc/sys/kernel/tainted 4096 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From abraham.arce.moreno at intel.com Tue Sep 18 00:53:49 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 18 Sep 2018 00:53:49 +0000 Subject: [Starlingx-discuss] stx-config Documentation Baseline Message-ID: Dean, I have taken the following patches from stx-tools related to documentation including your recent changes: - [0] [Doc] Building docs following Docs Contrib Guide - [1] [Doc] Release Notes Management - [2] Add docs, releasenotes jobs And created a new set of patches for stx-config, your recent changes [2] are included but split based on where they apply, either Documentation or Release Notes: - [3] [Doc] Building docs following Docs Contrib Guide - [4] [Doc] Release Notes Management - [5] [Doc] OpenStack API Reference Guide The following changes are not included on purpose: - "Create a release summary note" waiting for content [6] - "API Reference content" waiting for content Please let me know if changes look ok so we can take as a baseline to update or populate the rest of the projects. [0] https://review.openstack.org/#/c/590797/ [1] https://review.openstack.org/#/c/590798/ [2] https://review.openstack.org/#/c/600198/ [3] https://review.openstack.org/#/c/603256/ [4] https://review.openstack.org/#/c/603257/ [5] https://review.openstack.org/#/c/603258/ [6] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-September/001089.html From yong.hu at intel.com Tue Sep 18 01:07:01 2018 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 18 Sep 2018 01:07:01 +0000 Subject: [Starlingx-discuss] Build installer instructions Message-ID: <42B47897-0863-4D72-9979-CD7085BADBF9@intel.com> Originally here is a readme to describe how to make/update installer images: cgcs-root/stx/stx-metal/installer/initrd/README Later I made 2 scripts to automate the process descripted in that readme: cgcs-root/build-tools/update-pxe-network-installer cgcs-root/build-tools/make-installer-images.sh While, due to the hard-coding (referring to the mirror folder for a specified version, for example, /import/mirrors/CentOS/tis-installer/initrd.img-stx-0.4) in "~/cgcs-root/stx/stx-metal/installer/pxe-network-installer/centos/build_srpm.data", we have to manually edit this file every time. So, I would agree Don's suggest that we use the symlinks to the latest version to get rid of versions attached. Further, instead of using the hard-coded "/import/mirror/CentOS/tis-installer", we can use a relative directory, something like "~/cgcs-root/cgcs-centos-repo/tis-installer". Here "tis-installer" could be a symbol link to the actual place where the init images are placed. On 18/09/2018, 12:41 AM, "Penney, Don" wrote: It's good to note that if you've already got installer images generated (ie. on a shared system, in /import/mirror/CentOS/tis-installer), you don't need to run "build-pkgs --installer". So presumably, this would not be part of a general designer workflow. Historically, we upversioned these images whenever they were updated, but this introduces some challenges under Starling-X. It may make sense to drop the version number from the images as referenced in the pxe-network-installer package build, essentially treating it as a .latest version. Individuals or groups could then manage their own installer version history as they see fit, ie. build images with 0.1, 0.2, 0.3, with symlinks to the latest perhaps. If these images aren't being hosted somewhere, if individuals/groups are generating their own, then the versioning shouldn't be in the build files. -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Monday, September 17, 2018 12:12 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Build installer instructions Hi, I would like to share/discuss the instructions to generate the installer before are publish into the wiki. I couldn't find a previous version of these instructions, probably I confused with this warning from the download_mirror.sh[0]. The update-pxe-network-installer script follows the steps detailed here[1]. Build installer =============== To get your StarlingX ISO ready to use, you will need to create the init files that will be used to boot the ISO as well to boot additional controllers and compute nodes. Once you had run `build-iso`, run: ``` build-pkgs --installer ``` This will build `rpm` and `anaconda` packages. Then run: ``` update-pxe-network-installer ``` The update-pxe-network-installer` covers the steps detailed in `$MY_REPO/stx/stx-metal/installer/initrd/README`. This script will create three files on `/localdisk/loadbuild///pxe- network-installer/output` ``` new-initrd.img new-squashfs.img new-vmlinuz ``` Then, rename them to: ``` initrd.img-stx-0.2 squashfs.img-stx-0.2 vmlinuz-stx-0.2 ``` There are two ways to use these files: 1. Store the files in the '/import/mirror/CentOS/tis-installer/` folder for future use. 2. Store it in an arbitrary location and modify the `$MY_REPO/stx/stx- metal/installer/pxe-network-installer/centos/build_srpm.data` file to point to these files. Now, the `pxe-network-installer` package needs to be recreated and the ISO regenerated. ``` build-pkgs --clean pxe-network-installer build-pkgs pxe-network-installer build-iso ``` Now your ISO should be able to boot. Updating these files is not a common tasks, it is recommended only do it if the kernel version is upgraded or new kernel modules are added. ===================== End of documentation [0] http://git.starlingx.io/cgit/stx-tools/tree/centos-mirror-tools/download_mirror.sh#n264 [1] http://git.starlingx.io/cgit/stx-metal/tree/installer/initrd/README _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Tue Sep 18 01:12:47 2018 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 17 Sep 2018 18:12:47 -0700 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE481F6113@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> <3CAA827B7A79BA46B15B280EC82088FE481F6113@ALA-MBD.corp.ad.wrs.com> Message-ID: <2334693a-5e1b-04f3-27f7-227529b8a594@linux.intel.com> On 09/17/2018 01:58 PM, Waheed, Numan wrote: > Hi, > > Following testing was done for testing CentOS7.5 on a custom build created by Jason: > > Load: > SW_VERSION="18.08" > BUILD_TARGET="Unknown" > BUILD_TYPE="Informal" > BUILD_ID="n/a" > > JOB="n/a" > BUILD_BY="jmckenna" > BUILD_NUMBER="n/a" > BUILD_HOST="yow-cgts1-lx" > BUILD_DATE="2018-09-13 10:42:03 -0400" > > BUILD_DIR="/" > WRS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root" > WRS_GIT_BRANCH="HEAD" > CGCS_SRC_DIR="/localdisk/designer/jmckenna/starlingx-centos75/cgcs-root/stx" > CGCS_GIT_BRANCH="HEAD" > > Sanity > - 23 Test Cases > > Nightly Regression > - 46 Test Cases (1 Failure for Kernel module Signature – tested and reproduced on three different labs) > So, I checked with Shuicheng and he does have the e1000e signed module loading correctly, I wonder if the problem is related to your build of the kernel and signed modules. Can you confirm the signature is correct by getting the e1000e.ko to another machine and then running the kernel's extract-module-sig.pl (found in the kernel/scripts directory) extract-module-sig.pl -n e1000e.ko You should get output something like this: Read 431181 bytes from module file Found magic number at 431181 Found X.509 cert identifier Found 386 bytes of signature [01808b1c7c983aae1a50ffa4422a6a52] Found 20 bytes of key identifier [ff1d56e0f0f42602f2a4fc5cb641d1f4] Found 31 bytes of signer's name [CentOS Linux kernel signing key] CentOS Linux kernel signing key Could this be related to creating (or not creating) a new installer? Sau! > Nova Regression > - Executed on three labs (AIO-SX, Standard and Storage Lab) > - Labs covered Mellanox, Niantic and Fortville NICs > - AIO-SX: > o Test Cases Executed: 209 > o Passed: 204 > o Failed: 5 (3 known issues, 1 Ping issue, 1 timing issue that passed on re-execution) > > - Standard Lab: > o Test Cases Executed: 373 > o Passed: 346 > o Failed: 27 (6 known issues, 1 ping issue, 20 passed on re-execution) > > - Storage: > o Test Cases Executed: 374 > o Passed: 367 > o Failed: 7 (6 issues also seen in STX branch without CentOS7.5, 1 test case passed on re-execution) > > Failed test cases were re-executed and majority of them passed on re-execution. The remaining failed test cases are also failing on STX build without CentOS7.5 update. Hence, the failures are not caused by CentOS7.5 update. > > The main issue seen so far is only about Kernel Signature. Another issue seen is no Inventory tab available in Horizon. However, that does not seem to be related to CentOS update. > > Thanks, > > Numan. > > -----Original Message----- > From: Rasa, Nimalini > Sent: September-17-18 12:21 PM > To: Lin, Shuicheng; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Shuicheng, > In this test case, basically trying to allocate double the amount of 2M pages. > > For the kernel signature, I tried it on 3 different hardware labs and got the following: > controller-0:~$ cat /proc/sys/kernel/tainted > 12288 > controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log > 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: module verification failed: signature and/or required key missing - tainting kernel > 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: module verification failed: signature and/or required key missing - tainting kernel > > > Thanks, > Nimalini > > -----Original Message----- > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > Sent: Friday, September 14, 2018 9:13 PM > To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Nimalini, > Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? > > For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? > " > controller-0:~$ cat /proc/sys/kernel/tainted > 4096 > controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " > > Best Regards > Shuicheng > > -----Original Message----- > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > Sent: Saturday, September 15, 2018 3:02 AM > To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Cindy, > Adding more clarification of the test cases that are failed: > > FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] > Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. > > FAIL 20180914 07:57:34 test_kernel_module_signatures > Test case is doing the following: > - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: > - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules > - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module > > > Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. > > Thanks, > Nimalini > > -----Original Message----- > From: Rasa, Nimalini > Sent: Friday, September 14, 2018 12:46 PM > To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada; Lin, Shuicheng > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Cindy, > > Here is the last test update, I am reporting the failed test cases only here: > > From Sanity: > FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) > > From Nightly: > FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] > > LOG: > ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> > [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 > [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... > [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' > [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: > +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ > | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | > | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail > | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | > | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | > +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ > | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | > | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | > +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ > controller-1:~$ > [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' > [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: > 0 > controller-1:~$ > [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] > [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] > [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] > [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] > [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] > [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] > [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] > [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] > [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] > [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] > [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] > [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] > [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 > [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... > [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' > [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: > +--------------------------------+--------------------------------------+ > | Property | Value | > +--------------------------------+--------------------------------------+ > | Memory: Usable Total (MiB) | 7540 | > | Platform (MiB) | 8000 | > | Available (MiB) | 2420 | > | Huge Pages Configured | True | > | vSwitch Huge Pages: Size (MiB) | 1024 | > | Total | 1 | > | Available | 0 | > | VM Pages (4K): Total | 20992 | > | VM Huge Pages (2M): Total | 3258 | > | Total Pending | 2420 | > | Available | 1210 | > | VM Huge Pages (1G): Total | 0 | > | Available | 0 | > | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | > | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | > | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | > | created_at | 2018-09-14T02:30:56.591922+00:00 | > | updated_at | 2018-09-14T06:48:29.882522+00:00 | > +--------------------------------+--------------------------------------+ > controller-1:~$ > [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' > [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: > 0 > > EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: > [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' > [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: > Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 > > > FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] > This test failed b/c of the above test failure (Alarm was present, compute was in locked state) > > > FAIL 20180914 07:57:34 test_kernel_module_signatures > LOG > > [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: > ====================== Test Step 1: Check for unassigned kernel modules on controller-0 > [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... > [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' > [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: > 12288 > controller-0:~$ > [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' > [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: > 0 > controller-0:~$ > [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info > [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: > ====================== Test Step 2: Check kern.log for modules with failed verification > [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... > [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' > [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: > 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel > 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel > 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel > controller-0:~$ > [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' > [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: > 0 > controller-0:~$ > [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: > ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] > [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... > [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' > [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: > filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko > signer: CentOS Linux kernel signing key > sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC > sig_hashalgo: sha256 > controller-0:~$ > [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' > [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: > > > > Thanks, > Nimalini > > -----Original Message----- > From: Xie, Cindy [mailto:cindy.xie at intel.com] > Sent: Thursday, September 13, 2018 10:05 AM > To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada; Lin, Shuicheng > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. > > The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 > > Thanks. - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 9:35 PM > To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Cindy, > > Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. > > -Jason > >> -----Original Message----- >> From: Xie, Cindy >> Sent: September 13, 2018 2:44 AM >> To: Martinez Monroy, Elio ; McKenna, >> Jason ; Waheed, Numan >> ; Rasa, Nimalini >> ; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada ; Lin, Shuicheng >> >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Elio, >> We will provide you an updated ISO later today with the following: >> - kernel upgrade to 3.10.0-862.11.6 >> - symbol issue fixed: >> https://bugs.launchpad.net/starlingx/+bug/1792257 >> >> Please help to do a sanity test based on this new ISO from Shuicheng on VE. >> >> @Jason, >> Please re-generate a build using today's manifest with above fix. >> Shuicheng shall be able to provide manifest with exact commitID. >> @Numan, please abort your current testing w/ old ISO once you get a >> new one from Jason and continue your sanity and regression on >> bare-metal. I am not sure how long it takes, but please take priority >> as we want merge back to mainline early next week. >> >> Thanks all for the support. >> - cindy >> >> -----Original Message----- >> From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] >> Sent: Thursday, September 13, 2018 4:24 AM >> To: Lin, Shuicheng ; Cordoba Malibran, Erich >> ; Waheed, Numan >> ; Rasa, Nimalini >> ; starlingx-discuss at lists.starlingx.io; >> Liu, ZhipengS ; Khalil, Ghada >> ; Xie, Cindy >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >>> -----Original Message----- >>> From: Lin, Shuicheng >>> Sent: September 11, 2018 8:44 PM >>> To: McKenna, Jason ; Cordoba Malibran, >>> Erich ; Waheed, Numan >>> ; Rasa, Nimalini >>> ; starlingx-discuss at lists.starlingx.io; >>> Liu, ZhipengS ; Khalil, Ghada >>> ; Xie, Cindy >>> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >>> >>> Hi Jason, >>> Here is the dhcp src rpm we are using: >>> [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source >>> dhcp >>> http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 >>> - >>> 68.el7.centos.1.src.rpm >>> >>> For centos-release, there are two packages in the mirror lst, 1 src >>> rpm for build, and 1 rpm for the mock environment. And it has the >>> "slightly difference" in the names as you mentioned. >>> Both of them could be found in the centos repo with the exact name. >>> ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm >>> ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm >>> [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source >>> centos- release-7-5.1804.1.el7.centos >>> http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- >>> release-7-5.1804.1.el7.centos.src.rpm >>> [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url >>> centos-release-7- >>> 5.1804.el7.centos.x86_64 >>> http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- >>> release-7-5.1804.el7.centos.x86_64.rpm >>> >>> If there is still some other rpm missing, you could try to find them >>> from the repo. >>> I have try my best to keep my local mirror the same as the lst. But >>> it is still possible some package missed to be added to the repo lst. >>> Please feel free to notify me or correct the error directly. >>> Thanks. >> >> With the latest commits to stx-tools I am now able to download the >> rpms and produce a build. I'll let you know how testing goes >> >>> >>> Best Regards >>> Shuicheng >>> >>> >>> -----Original Message----- >>> From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] >>> Sent: Wednesday, September 12, 2018 12:21 AM >>> To: Cordoba Malibran, Erich ; >>> Waheed, Numan ; Rasa, Nimalini >>> ; starlingx-discuss at lists.starlingx.io; >>> Liu, ZhipengS ; Khalil, Ghada >>> ; Lin, Shuicheng >>> ; Xie, Cindy >>> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >>> >>> Hi Cindy, >>> >>> With the latest centos75 branch (and the cherry-picks you mentioned) >>> I am unable to produce a build. There seems to be several source >>> rpm files missing from the currently pushed version of the .lst >>> files (or the .lst files pull down the wrong version). Most of the >>> missing files I can download manually, however the checked in >>> patches for dhcp and centos-release packages do not apply against >>> the version of the source RPM which I can manually find on the >>> Internet. For example, the version of centos-release called out in >>> the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the >>> version called out in the checked in code base is the slightly >>> different >>> centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches >> checked in do not apply against either package. >>> >>> Until the centos75 branch of the lst files pulls down the correct >>> rpms, I will be unable to continue the validation effort. >>> >>> -J >>> >>>> -----Original Message----- >>>> From: Cordoba Malibran, Erich >>>> Sent: September 11, 2018 11:17 AM >>>> To: Waheed, Numan ; Rasa, Nimalini >>>> ; >>>> starlingx-discuss at lists.starlingx.io; >>>> Liu, ZhipengS ; Khalil, Ghada >>>> ; Lin, Shuicheng >>>> ; McKenna, Jason >>>> ; Xie, Cindy >>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update >>>> >>>> Hi >>>> >>>> You can add "debug loglevel=8" to the kernel boot option to get a >>>> more detailed output of the crash (if any) >>>> >>>> -Erich >>>> >>>> On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: >>>>> Shuicheng saw the symbol table error issue as well but it >>>>> recovers in 8s, he is still working on debugging it. But 601204 >>>>> is just kernel upgrade but not intended to solve this issues. >>>>> Are you running bare metal? I am wondering if this is HW config and driver issue. >>>>> >>>>> Is it possible that you try to deploy it in virtual environment? >>>>> >>>>> Thx. - cindy >>>>> >>>>> From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] >>>>> Sent: Tuesday, September 11, 2018 9:50 PM >>>>> To: Xie, Cindy ; Rasa, Nimalini >>>>> ; Waheed, Numan >>>>> ; Lin, Shuicheng >>>>> ; Liu, ZhipengS >>>> l.com>; Khalil, Ghada ; >>>>> 'starlingx-discus s at lists.starlingx.io' >>>>> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Hi Cindy, >>>>> >>>>> We got past the installation device error, but are coming up >>>>> against the symbol table error. Our system hangs after this >>>>> message. I suspect a kernel issue. I see there is an open code >>>>> review to refactor some kernel patches to a rebased kernel >>>>> (https://review.open >>>>> stack.org/#/c/601204/) but I do not know if that is expected to >>>>> resolve the issue >>>>> >>>>> -J >>>>> >>>>> From: Xie, Cindy >>>>> Sent: September 11, 2018 9:32 AM >>>>> To: Rasa, Nimalini ; Waheed, Numan >>>> >>>> n.Waheed at windriver.com>; Lin, Shuicheng >> ; >>>>> McKenna, Jason ; Liu, ZhipengS >>>> >>>> .liu at intel.com>; Khalil, Ghada ; >>>>> 'starlin gx-discuss at lists.starlingx.io' >>>>> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> But as Jason reported yesterday, the build cannot be installed >>>>> with error messages: >>>>> >>>>> Installation failed. >>>>> ERROR: Specified installation (sda) or boot (sda) device is invalid. >>>>> >>>>> We cannot debug without more information, the ISO installs in >>>>> Intel’s HW. Thus Shuicheng created a new build and attached a >>>>> manifest in this email thread. Did WindRiver has a chance to >>>>> create a new ISO using today’s manifest file and re-run the test? >>>>> >>>>> Thx. - cindy >>>>> >>>>> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] >>>>> Sent: Tuesday, September 11, 2018 9:25 PM >>>>> To: Xie, Cindy ; Waheed, Numan >>>> >>>> driver.com>; Lin, Shuicheng ; McKenna, >>>>> Jason ; Liu, ZhipengS >>>> >>>>> ; Khalil, Ghada ; >>>>> 'starlingx-discuss at list s.starlingx.io' >>>>> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> This is on the same build (yesterday’s build). >>>>> >>>>> From: Xie, Cindy [mailto:cindy.xie at intel.com] >>>>> Sent: Tuesday, September 11, 2018 9:22 AM >>>>> To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, >>>>> Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Is this the same issue as yesterday’s build? or this is >>>>> different issue now? >>>>> >>>>> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] >>>>> Sent: Tuesday, September 11, 2018 9:06 PM >>>>> To: Waheed, Numan ; Lin, >> Shuicheng >>>> >>>> heng.lin at intel.com>; McKenna, Jason >>> ; >>>>> Liu, ZhipengS ; Khalil, Ghada >>>>> ; >>>>> 'starlingx-discuss at lists.starlingx.io' >>>> uss at lists.starlingx.io>; Xie, Cindy >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> It is not booting in my case. After the following , it just >>>>> hangs >>>>> there: >>>>> “Error: no symbol table. >>>>> Press any key to continue…” >>>>> >>>>> -Nimalini >>>>> >>>>> From: Waheed, Numan >>>>> Sent: Tuesday, September 11, 2018 8:50 AM >>>>> To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, >>>>> Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; >>>>> Rasa, Nimalini >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Adding Nimalini >>>>> >>>>> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >>>>> Sent: September-11-18 2:17 AM >>>>> To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; >>>>> 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, >>>>> Numan >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Hi Jason, >>>>> Just finished deploy image with latest code, I could config >>>>> controller successfully in bare metal environment. >>>>> Manifest is created for you reference. There are two patches I >>>>> add >>>>> manually: >>>>> https://review.openstack.org/596855           for >>>>> python-horizon from master >>>>> https://review.openstack.org/599892           for build-iso >>>>> >>>>> >>>>> There is an issue found when reboot controller node. >>>>> After the OS selection menu, it will show below error. And it >>>>> will auto continue boot after around 8 seconds. I will check the >>>>> issue later. >>>>> “ >>>>> Error: no symbol table. >>>>> Press any key to continue… >>>>> “ >>>>> >>>>> Best Regards >>>>> Shuicheng >>>>> >>>>> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >>>>> Sent: Tuesday, September 11, 2018 9:35 AM >>>>> To: McKenna, Jason ; Liu, ZhipengS >>>> >>>> engs.liu at intel.com>; Khalil, Ghada ; >>>>> 'sta rlingx-discuss at lists.starlingx.io' >>>>> >>>> .io>; Xie, Cindy ; Waheed, Numan >>>> >>>> indriver.com> >>>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status >>>>> update >>>>> >>>>> Hi Jason, >>>>> I just tried my last Friday’s image at bare metal machine. There >>>>> is no issue to install controller node. >>>>> Will you help check what cause the install error in your environment? >>>>> >>>>> I am syncing my code to latest to double confirm it. >>>>> >>>>> Best Regards >>>>> Shuicheng >>>>> >>>>> From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] >>>>> Sent: Tuesday, September 11, 2018 12:13 AM >>>>> To: Liu, ZhipengS ; Lin, Shuicheng >>>>> ; Khalil, Ghada >>>>> ; 'starlin >>>>> gx-discuss at lists.starlingx.io' >>>>> >>>>> ; Xie, Cindy ; Waheed, Numan >>>> >>>> iver.com> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Status update. The build from the centos75 branch does not >>>>> install on our hardware. The error message we are seeing is: >>>>> >>>>> Installation failed. >>>>> >>>>> ERROR: Specified installation (sda) or boot (sda) device is invalid. >>>>> >>>>> -Jason >>>>> >>>>> From: Liu, ZhipengS >>>>> Sent: September 8, 2018 9:56 AM >>>>> To: Lin, Shuicheng ; McKenna, Jason >>>>> ; Khalil, Ghada >>>>> ; 's >>>>> tarlingx-discuss at lists.starlingx.io' >>>>> ; Xie, Cindy >>>>> ; Waheed, Numan >>>> >>>> @windriver.com> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Hi Jason, >>>>> >>>>> I have fixed the issue you mentioned below. >>>>> - Furthermore, the tpm2-tools package was requesting version >>>>> tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). >>>>> I hacked the spec file for tpm2-tools and rebuilt it to require >>>>> the version mentioned, but there is some rework to be done there. >>>>> [slin14]: I have the same issue also. Let’s further check it to >>>>> find the root cause. I use rebuild tpm2-tools/tss2 to workaround >>>>> it without any code. >>>>> >>>>> https://review.openstack.org/#/c/600920/ >>>>> >>>>> Thanks! >>>>> Zhipeng >>>>> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >>>>> Sent: 2018年9月8日 21:14 >>>>> To: McKenna, Jason ; Khalil, Ghada >>>> >>>> a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' >>>>> ; Xie, Cindy >>>>> ; Waheed, Numan >>> >>>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status >>>>> update >>>>> >>>>> Hi Jason, >>>>> I have fixed the error in the openstack-aodh. Patch is updated: >>>>> https://review.openstack.org/#/c/598388/ >>>>> >>>>> It is due to my local version is not the latest one. >>>>> Sorry for the trouble caused, and thanks for your test. >>>>> >>>>> Best Regards >>>>> Shuicheng >>>>> >>>>> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >>>>> Sent: Saturday, September 8, 2018 9:23 AM >>>>> To: McKenna, Jason ; Khalil, Ghada >>>> >>>> a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' >>>>> ; Xie, Cindy >>>>> ; Waheed, Numan >>> >>>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status >>>>> update >>>>> >>>>> Hi Jason, >>>>> Thanks very much for such detail feedback. >>>>> I added some comments inline, and will check the issue in my >>>>> environment also. >>>>> Feel free to submit patch if you have to fix them. J >>>>> >>>>> >>>>> Best Regards >>>>> Shuicheng >>>>> >>>>> From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] >>>>> Sent: Saturday, September 8, 2018 3:47 AM >>>>> To: McKenna, Jason ; Khalil, Ghada >>>> >>>> a.Khalil at windriver.com>; Lin, Shuicheng >>>>> ; 's tarlingx-discuss at lists.starlingx.io' >>>>> ; Xie, Cindy >>>>> ; Waheed, Numan >>>> >>>> @windriver.com> >>>>> Subject: RE: CentOS 7.5 upgrade status update >>>>> >>>>> Hi Shuicheng, >>>>> >>>>> I’ve completed a build of the code. We have not yet run >>>>> run-time tests, but here are the build-time issues I encountered: >>>>> >>>>> - The .lst file contains lighttpd-1.4.49, but this is no >>>>> longer available for download, and the download_mirrors.sh step fails. >>>>> It appears than CentOS has updated to lighttpd-1.4.50. I >>>>> manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst >>>>> - Even though the .lst file specifies lighttpd-1.4.49, the >>>>> code still references 1.4.45 >>>>> - At build-pkgs time (the build-srpms step), the meta-patches >>>>> to openstack-aodh do not apply, as two of them are malformed. https: >>>>> //review.openstack.org/#/c/598388/6/openstack/openstack- >>>>> aodh/centos/meta_patches/0001-Modify-service-files-and-create- >>>>> expirer-cron-script.patch -- In the new version, on line 190, >>>>> the patch states that the old code covered 6 lines, and the new >>>>> code covers 9 lines (-283,6 +286,9). But there are only two >>>>> lines inserted by the patch. There is also a new blank line in >>>>> the patch at line 194. Removing this blank line and editing the >>>>> hunk description to only insert 2 lines resolves the issue for >>>>> this hunk (there are other similar issues in this patch, and in >>>>> 0001-meta- >>>>> modify-aodh-api.patch) >>>>> [slin14]: Let me double check it. >>>>> - At binary build time, I had build failures on python-django- >>>>> horizon and some magnum packages. I had to pull in >>>>> https://review.op >>>>> enstack.org/#/c/596855/2 (from the master branch, but not in the >>>>> centos75 branch of stx-upstream) to get past this. >>>>> [slin14]: It is due to I have not synced latest master code, so >>>>> I don’t have this issue. I used last week’s master code. >>>>> - After building all packages, I attempted to build the ISO. >>>>> The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and >>>>> should be added to the .lst files. >>>>> [slin14]: This package is already in the lst. >>>>> - Furthermore, the tpm2-tools package was requesting version >>>>> tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). >>>>> I hacked the spec file for tpm2-tools and rebuilt it to require >>>>> the version mentioned, but there is some rework to be done there. >>>>> [slin14]: I have the same issue also. Let’s further check it to >>>>> find the root cause. I use rebuild tpm2-tools/tss2 to workaround >>>>> it without any code. >>>>> >>>>> After these changes, I was able to produce a .iso >>>>> >>>>> -Jason >>>>> >>>>> From: McKenna, Jason >>>>> Sent: September 7, 2018 10:08 AM >>>>> To: Khalil, Ghada ; Lin, Shuicheng >>>>> ; 'starlingx-discuss at lists.starlingx.io' >>>>> ; Xie, Cindy >>>>> ; Waheed, Numan >>> >>>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status >>>>> update >>>>> >>>>> Hi Shuicheng, >>>>> >>>>> As a download_mirrors.sh time issue, the version of lighttpd has >>>>> been changed from 1.4.45 to 1.4.49. The >>>>> lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or >>>>> CentOS servers, as they’ve moved to 1.4.50. I am attempting to >>>>> locate an archived version of the 1.4.49 .src rpm. >>>>> >>>>> -Jason >>>>> >>>>> From: Khalil, Ghada >>>>> Sent: September 7, 2018 9:36 AM >>>>> To: Lin, Shuicheng ; >>>>> 'starlingx-discuss at list s.starlingx.io' >>>>> ; Xie, Cindy >>>> indy.xie at intel.com>; Waheed, Numan >>> >>>>> Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status >>>>> update >>>>> >>>>> Thanks Shuicheng. We’ll run some tests in Wind River. Numan will >>>>> be priming this activity. He’ll share the results with the team >>>>> sometime next week. >>>>> >>>>> Regards, >>>>> Ghada >>>>> >>>>> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >>>>> Sent: Friday, September 07, 2018 1:32 AM >>>>> To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, >>>>> Cindy >>>>> Subject: CentOS 7.5 upgrade status update >>>>> >>>>> Hi all, >>>>> Most task of CentOS7.5 upgrade in story 2003389 is done. Please >>>>> go ahead to have a try and verify it. >>>>> I expect there should be some issue due to we just did limited >>>>> deploy test yet. >>>>> >>>>> Here is the detail status update of this week. >>>>> For the total 44 srpm we plan to upgrade: >>>>> 38 already merged in feature branch. >>>>> 3 kept as original version. Anaconda upgrade is not needed. >>>>> python- os-vif has higher version than 7.5. python-eventlet kept >>>>> due to new src rpm itself have known issue. >>>>> 2 under review with code ready. Puppet-haproxy and openstack-aodh. >>>>> 1 under debug. Lighttpd. >>>>> >>>>> Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. >>>>> >>>>> Here is the build instruction: >>>>> 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- >>>>> upstream/stx-root. >>>>> Cherry-pick below un-merged patch: >>>>> For puppet-haproxy: >>>>> https://review.openstack.org/600369 >>>>> https://review.openstack.org/600359 >>>>> For openstack-aodh: >>>>> https://review.openstack.org/598388 >>>>> https://review.openstack.org/600591 >>>>> For build-iso: >>>>> https://review.openstack.org/599892 >>>>> For build-pkgs: >>>>> https://review.openstack.org/599901 >>>>> https://review.openstack.org/600639 >>>>> >>>>> 2. Run mirror script to get the upgraded src rpm and related >>>>> rpm. >>>>> 3. Try to build packages and ISO. >>>>> >>>>> For the detail status of CentOS7.5 upgrade, please check below story: >>>>> https://storyboard.openstack.org/#!/story/2003389 >>>>> >>>>> Feel free to contact me if you have trouble on it. >>>>> >>>>> Best Regards >>>>> Shuicheng >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis >>>>> cu >>>>> ss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From shuicheng.lin at intel.com Tue Sep 18 01:16:07 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 18 Sep 2018 01:16:07 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765535A725@SHSMSX101.ccr.corp.intel.com> Hi Nimalini, For the kernel signature issue, could you help confirm whether the kernel version is 3.10.0-862.11.6 or not? You could check it with "uname -a" or search it in the kern.log file. Thanks. Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Tuesday, September 18, 2018 12:21 AM To: Lin, Shuicheng ; Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, In this test case, basically trying to allocate double the amount of 2M pages. For the kernel signature, I tried it on 3 different hardware labs and got the following: controller-0:~$ cat /proc/sys/kernel/tainted 12288 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: module verification failed: signature and/or required key missing - tainting kernel Thanks, Nimalini -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 14, 2018 9:13 PM To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Nimalini, Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? " controller-0:~$ cat /proc/sys/kernel/tainted 4096 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss From Don.Penney at windriver.com Tue Sep 18 01:23:35 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 18 Sep 2018 01:23:35 +0000 Subject: [Starlingx-discuss] Build installer instructions In-Reply-To: <42B47897-0863-4D72-9979-CD7085BADBF9@intel.com> References: <42B47897-0863-4D72-9979-CD7085BADBF9@intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3B17BA@ALA-MBD.corp.ad.wrs.com> I made the README file as a way to track changes I'd make to the installer over the last few years. I'd considered automating it, but never really had a need, so thank you for doing that. I added comments to a recent review adding lz4 to the installer, identifying pkgs that should be dropped, but haven't really looked through the make-installer-images.sh script yet. One reason I just did it manually was to ensure everything went smoothly, so I could catch any oddities along the way. There'd need to be a lot of error checking, to ensure the installer is updated safely. The idea of using a symlink is good. I'd suggest we include it in the stx/downloads dir. It could be created by the populate_downloads.sh script as an additional step, maybe with an environment variable or argument to point to a particular location, so there's no change in developer process (aside from maybe setting a new var) -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Monday, September 17, 2018 9:07 PM To: Penney, Don; Cordoba Malibran, Erich; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Build installer instructions Originally here is a readme to describe how to make/update installer images: cgcs-root/stx/stx-metal/installer/initrd/README Later I made 2 scripts to automate the process descripted in that readme: cgcs-root/build-tools/update-pxe-network-installer cgcs-root/build-tools/make-installer-images.sh While, due to the hard-coding (referring to the mirror folder for a specified version, for example, /import/mirrors/CentOS/tis-installer/initrd.img-stx-0.4) in "~/cgcs-root/stx/stx-metal/installer/pxe-network-installer/centos/build_srpm.data", we have to manually edit this file every time. So, I would agree Don's suggest that we use the symlinks to the latest version to get rid of versions attached. Further, instead of using the hard-coded "/import/mirror/CentOS/tis-installer", we can use a relative directory, something like "~/cgcs-root/cgcs-centos-repo/tis-installer". Here "tis-installer" could be a symbol link to the actual place where the init images are placed. On 18/09/2018, 12:41 AM, "Penney, Don" wrote: It's good to note that if you've already got installer images generated (ie. on a shared system, in /import/mirror/CentOS/tis-installer), you don't need to run "build-pkgs --installer". So presumably, this would not be part of a general designer workflow. Historically, we upversioned these images whenever they were updated, but this introduces some challenges under Starling-X. It may make sense to drop the version number from the images as referenced in the pxe-network-installer package build, essentially treating it as a .latest version. Individuals or groups could then manage their own installer version history as they see fit, ie. build images with 0.1, 0.2, 0.3, with symlinks to the latest perhaps. If these images aren't being hosted somewhere, if individuals/groups are generating their own, then the versioning shouldn't be in the build files. -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Monday, September 17, 2018 12:12 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Build installer instructions Hi, I would like to share/discuss the instructions to generate the installer before are publish into the wiki. I couldn't find a previous version of these instructions, probably I confused with this warning from the download_mirror.sh[0]. The update-pxe-network-installer script follows the steps detailed here[1]. Build installer =============== To get your StarlingX ISO ready to use, you will need to create the init files that will be used to boot the ISO as well to boot additional controllers and compute nodes. Once you had run `build-iso`, run: ``` build-pkgs --installer ``` This will build `rpm` and `anaconda` packages. Then run: ``` update-pxe-network-installer ``` The update-pxe-network-installer` covers the steps detailed in `$MY_REPO/stx/stx-metal/installer/initrd/README`. This script will create three files on `/localdisk/loadbuild///pxe- network-installer/output` ``` new-initrd.img new-squashfs.img new-vmlinuz ``` Then, rename them to: ``` initrd.img-stx-0.2 squashfs.img-stx-0.2 vmlinuz-stx-0.2 ``` There are two ways to use these files: 1. Store the files in the '/import/mirror/CentOS/tis-installer/` folder for future use. 2. Store it in an arbitrary location and modify the `$MY_REPO/stx/stx- metal/installer/pxe-network-installer/centos/build_srpm.data` file to point to these files. Now, the `pxe-network-installer` package needs to be recreated and the ISO regenerated. ``` build-pkgs --clean pxe-network-installer build-pkgs pxe-network-installer build-iso ``` Now your ISO should be able to boot. Updating these files is not a common tasks, it is recommended only do it if the kernel version is upgraded or new kernel modules are added. ===================== End of documentation [0] http://git.starlingx.io/cgit/stx-tools/tree/centos-mirror-tools/download_mirror.sh#n264 [1] http://git.starlingx.io/cgit/stx-metal/tree/installer/initrd/README _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From abraham.arce.moreno at intel.com Tue Sep 18 01:44:00 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 18 Sep 2018 01:44:00 +0000 Subject: [Starlingx-discuss] Stories for stx-tools deployment In-Reply-To: <511d268b-c23c-2520-152c-fcf7e9286e09@windriver.com> References: <511d268b-c23c-2520-152c-fcf7e9286e09@windriver.com> Message-ID: Michel, > I've been working through the wikis under > "https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Enviro > nment". We really appreciate and thank you for your support for the recent improvements made under stx-tools to support the StarlingX installation under a virtual environment. > After I've finished reviewing "standard Controller Storage" and "all-in-one" > configurations under virtualization, I'd like consider stories for stx- > tools/deployement such as "running multiple clusters on a host" and "testing > networking for instances". > > I do not see anything in storyboard: > https://storyboard.openstack.org/#!/project/openstack/stx-tools > > Do you know if there are plans for those things? From my understanding there are no more stories associated to virtualization since pushing out the initial commit based in Ubuntu and deploying the different configurations under a Virtual Environment were completed so please feel to create the next level of stories. Only pending thing based on feedback from Greg Waines is to take advantage of the existing documentation to add the deployment under Bare Metal so this might be a missing story, I will add it. Please let us know how we can help. From abraham.arce.moreno at intel.com Tue Sep 18 02:37:21 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 18 Sep 2018 02:37:21 +0000 Subject: [Starlingx-discuss] Developer Guide, Next Steps Message-ID: Based on recent recommendations to improve our sync up between our tools and documentation, we required your feedback on the required changes to our documentation regarding the build of our ISO. The high level structure of actual guides found under StarlingX main wiki [0] page how our community can interact is: - [1] Developer Guide - [2] Installation Guide Virtual Environment - [3] Testing Guide [ Profile of Users ] In preparation to our release and considering the upcoming work based on stxb tool [4] [5] which will simplify the build of an ISO, we are targeting two types of users which will impact the existing "Developer Guide" [1]: - Users "Profile A" building StarlingX using stbx tool with the only objective to have the ISO, no need to debug / modify / whatever our code. - Users "Profile B" with the need to get inside the container to debug / modify / whatever our code. Due to community culture / non-native English speakers we are, how would you called those 2 different "wiki pages" / "sections" where both Users "Profile A" and "Profile B" will find their instructions: - Users "Profile A": User Guide? Getting Started Guide? - Users "Profile B": Contributor Guide? Developer Guide? [ Sources of Documentation ] Regarding the source of documentation we have 3 places: - [1] The Developer Guide Wiki page, already populated, to be changed based in your feedback asked above. - [6] The README file under stx-tools repository, already populated. - [7] The doc/ directory under stx-tools repository, not populated and not for this release, mid-term scope. In preparation to our release and as a short term solution to keep updated one single place we are targeting to make our wiki [0] our official source, removing all content from the README [6] keeping only a link to the wiki page. If there is a another proposal please let us know. [0] https://wiki.openstack.org/wiki/StarlingX [1] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [2] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide [3] https://wiki.openstack.org/wiki/StarlingX/Testing_Guide [4] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-September/001001.html [5] https://review.openstack.org/#/c/601366/ [6] https://git.openstack.org/cgit/openstack/stx-tools/tree/README.rst [7] https://git.openstack.org/cgit/openstack/stx-tools/tree/doc/source/index.rst From yong.hu at intel.com Tue Sep 18 04:11:50 2018 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 18 Sep 2018 04:11:50 +0000 Subject: [Starlingx-discuss] when and how is squashfs.img used? Message-ID: <985E7A51-AC95-4038-B927-A7564B312561@intel.com> As a part of pxe-network-installer-1.0-27.tis.x86_64.rpm, my understanding is that Squashfs.img will be mounted by nodes (such as 2nd controller, compute nodes and storage nodes) during the process of PXE boot installation. However, these questions are in my mind: 1. Will be squashfs.img still being used *AFTER installation*? 2. Where is squashfs.img mounted? I checked /etc/fstab, and there is no such an item. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Sep 18 07:46:11 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 18 Sep 2018 09:46:11 +0200 Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming In-Reply-To: References: Message-ID: Hi, I think the attached document would be a great candidate to be proposed as a spec to stx-specs. That way you can send out the link to the Gerrit review which works better with the mail archive as well as it is accessible from there too. Gerrit also helps with reviews but doesn’t force you to keep all the discussions there you can always reference the review link in mail threads. What do you think about moving the document there? Thanks, Ildikó > On 2018. Sep 17., at 9:17, Xu, Chenjie wrote: > > > > Hi Matt, > We analyze the patch 4ae5a58 related to l2pop. An RFE has been written(You can find it in the attachment). Could you please help to review and comment? Thanks very much! > > > Best Regards, > Xu, Chenjie > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Tue Sep 18 09:34:42 2018 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 18 Sep 2018 09:34:42 +0000 Subject: [Starlingx-discuss] build is broken due to Message-ID: Hi All: Due to my change, the build-pkg-parallel is broken, sorry for in-convience caused I have revert it with change https://review.openstack.org/#/c/603342/ Could someone CR+2 and W+1 ? Sorry for it. Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Tue Sep 18 11:55:27 2018 From: Greg.Waines at windriver.com (Waines, Greg) Date: Tue, 18 Sep 2018 11:55:27 +0000 Subject: [Starlingx-discuss] Developer Guide, Next Steps Message-ID: See comments below, Greg. From: "Arce Moreno, Abraham" Date: Monday, September 17, 2018 at 10:37 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Developer Guide, Next Steps Based on recent recommendations to improve our sync up between our tools and documentation, we required your feedback on the required changes to our documentation regarding the build of our ISO. The high level structure of actual guides found under StarlingX main wiki [0] page how our community can interact is: - [1] Developer Guide - [2] Installation Guide Virtual Environment - [3] Testing Guide [Greg] Because a normal user has to build the ISO in order to use StarlingX, I would have the following top-level guides · Build Guide · Installation Guide · User Guide · Contributor Guide [ Profile of Users ] In preparation to our release and considering the upcoming work based on stxb tool [4] [5] which will simplify the build of an ISO, we are targeting two types of users which will impact the existing "Developer Guide" [1]: - Users "Profile A" building StarlingX using stbx tool with the only objective to have the ISO, no need to debug / modify / whatever our code. - Users "Profile B" with the need to get inside the container to debug / modify / whatever our code. Due to community culture / non-native English speakers we are, how would you called those 2 different "wiki pages" / "sections" where both Users "Profile A" and "Profile B" will find their instructions: - Users "Profile A": User Guide? Getting Started Guide? - Users "Profile B": Contributor Guide? Developer Guide? [Greg] I would use: · User Guide · Contributor Guide [ Sources of Documentation ] Regarding the source of documentation we have 3 places: - [1] The Developer Guide Wiki page, already populated, to be changed based in your feedback asked above. - [6] The README file under stx-tools repository, already populated. - [7] The doc/ directory under stx-tools repository, not populated and not for this release, mid-term scope. In preparation to our release and as a short term solution to keep updated one single place we are targeting to make our wiki [0] our official source, removing all content from the README [6] keeping only a link to the wiki page. If there is a another proposal please let us know. [0] https://wiki.openstack.org/wiki/StarlingX [1] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [2] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide [3] https://wiki.openstack.org/wiki/StarlingX/Testing_Guide [4] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-September/001001.html [5] https://review.openstack.org/#/c/601366/ [6] https://git.openstack.org/cgit/openstack/stx-tools/tree/README.rst [7] https://git.openstack.org/cgit/openstack/stx-tools/tree/doc/source/index.rst _______________________________________________ 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 Nimalini.Rasa at windriver.com Tue Sep 18 13:49:55 2018 From: Nimalini.Rasa at windriver.com (Rasa, Nimalini) Date: Tue, 18 Sep 2018 13:49:55 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <9700A18779F35F49AF027300A49E7C765535A725@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A725@SHSMSX101.ccr.corp.intel.com> Message-ID: <65CE126717DEA145BD6B2C2842DC52D66C0C7A53@ALA-MBD.corp.ad.wrs.com> Hi Shuicheng, It does have the correct version: controller-0:~$ uname -a Linux controller-0 3.10.0-862.11.6.el7.36.tis.x86_64 #1 SMP PREEMPT Thu Sep 13 10:48:38 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux Thanks, Nimalini -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, September 17, 2018 9:16 PM To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Nimalini, For the kernel signature issue, could you help confirm whether the kernel version is 3.10.0-862.11.6 or not? You could check it with "uname -a" or search it in the kern.log file. Thanks. Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Tuesday, September 18, 2018 12:21 AM To: Lin, Shuicheng ; Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Shuicheng, In this test case, basically trying to allocate double the amount of 2M pages. For the kernel signature, I tried it on 3 different hardware labs and got the following: controller-0:~$ cat /proc/sys/kernel/tainted 12288 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: module verification failed: signature and/or required key missing - tainting kernel Thanks, Nimalini -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, September 14, 2018 9:13 PM To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Nimalini, Could you share me the detail reproduce step for " test_schedule_vm_mempage_config"? For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual and bare metal environment, and both of them show 4096. Then what should I do next? " controller-0:~$ cat /proc/sys/kernel/tainted 4096 controller-0:~$ grep --color=never -i "module verification failed" /var/log/kern.log controller-0:~$ " Best Regards Shuicheng -----Original Message----- From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] Sent: Saturday, September 15, 2018 3:02 AM To: Xie, Cindy ; McKenna, Jason ; Martinez Monroy, Elio ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Adding more clarification of the test cases that are failed: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] Test case is trying to over allocate 2M pages, expected to reject the cli, in this case it's accepted. FAIL 20180914 07:57:34 test_kernel_module_signatures Test case is doing the following: - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following steps: - 'grep --color=never -i "module verification failed" /var/log/kern.log' to find out failed modules - 'modinfo | grep --color=never -E "sig|filename" to display signing info for each module Hope it clarifies bit more as to what the test cases it trying to do. If you have any questions please let me know. Thanks, Nimalini -----Original Message----- From: Rasa, Nimalini Sent: Friday, September 14, 2018 12:46 PM To: 'Xie, Cindy'; McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Here is the last test update, I am reporting the failed test cases only here: From Sanity: FAIL 20180914 04:32:46 test_evacuate_vms --> Ping Vms failed and this is seen intermittently on STX load as well (can be ignored for this testing puprpose) From Nightly: FAIL 20180914 06:54:06 test_schedule_vm_mempage_config[1048576] LOG: ====================== Setup Step 6: (module) Execute modify function: ._modify at 0x7fc023a03d08> [2018-09-14 06:55:20,035] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:20,035] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:20,036] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-list --nowrap compute-1' [2018-09-14 06:55:21,883] 382 DEBUG MainThread ssh.expect :: Output: +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | processor | mem_total(MiB) | mem_platform(MiB) | mem_avail(MiB) | | hugepages(hp)_configured | vs_hp_size(MiB) | vs_hp_total | vs_hp_avail | | vm_total_4K | vm_hp_total_2M | vm_hp_avail_2M | vm_hp_pending_2M | | vm_hp_total_1G | vm_hp_avail_1G | vm_hp_pending_1G | vm_hp_use_1G | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ | 0 | 7540 | 8000 | 2420 | True | 1024 | 1 | 0 | 20992 | 3258 | 1210 | None | 0 | 0 | None | True | | 1 | 13770 | 2000 | 12746 | True | 1024 | 1 | 0 | 0 | 6373 | 6373 | None | 0 | 0 | None | True | +-----------+----------------+-------------------+----------------+--------------------------+-----------------+-------------+-------------+-------------+----------------+----------------+------------------+----------------+----------------+------------------+--------------+ controller-1:~$ [2018-09-14 06:55:21,884] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:21,986] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-1:~$ [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,987] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['2420'] [2018-09-14 06:55:21,987] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 0: [0] [2018-09-14 06:55:21,988] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,988] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching mem_avail(MiB) value(s): ['12746'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,989] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_total_1G value(s): ['0'] [2018-09-14 06:55:21,989] 366 DEBUG MainThread table_parser.__get_row_indexes_string:: row index list for processor: 1: [1] [2018-09-14 06:55:21,990] 498 DEBUG MainThread table_parser.get_values:: Returning matching vm_hp_pending_1G value(s): ['None'] [2018-09-14 06:55:21,990] 1300 DEBUG MainThread ssh.get_active_controller:: Getting active controller client for ip_1_4 [2018-09-14 06:55:21,990] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 06:55:21,990] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 2420 compute-1 0' [2018-09-14 06:55:24,362] 382 DEBUG MainThread ssh.expect :: Output: +--------------------------------+--------------------------------------+ | Property | Value | +--------------------------------+--------------------------------------+ | Memory: Usable Total (MiB) | 7540 | | Platform (MiB) | 8000 | | Available (MiB) | 2420 | | Huge Pages Configured | True | | vSwitch Huge Pages: Size (MiB) | 1024 | | Total | 1 | | Available | 0 | | VM Pages (4K): Total | 20992 | | VM Huge Pages (2M): Total | 3258 | | Total Pending | 2420 | | Available | 1210 | | VM Huge Pages (1G): Total | 0 | | Available | 0 | | uuid | 8f317d7a-3bcd-4b2d-bd1e-704429d0e0c5 | | ihost_uuid | 4189d5c3-0c85-49b9-9fc9-1d54540c54ea | | inode_uuid | 96430065-9a83-4e33-ab78-c7de77cf8bc9 | | created_at | 2018-09-14T02:30:56.591922+00:00 | | updated_at | 2018-09-14T06:48:29.882522+00:00 | +--------------------------------+--------------------------------------+ controller-1:~$ [2018-09-14 06:55:24,362] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 06:55:24,465] 382 DEBUG MainThread ssh.expect :: Output: 0 EXPECTED TO REJECT: HERE IS AN EXAMPLE FROM PASSED LOG ON DIFF LOAD: [2018-09-14 12:37:33,741] 262 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-region-name RegionOne host-memory-modify -2M 53818 compute-1 0' [2018-09-14 12:37:36,023] 382 DEBUG MainThread ssh.expect :: Output: Processor 0:No available space for 2M huge page allocation, max 2M pages: 26848 FAIL 20180914 07:00:37 test_schedule_vm_mempage_config[small] This test failed b/c of the above test failure (Alarm was present, compute was in locked state) FAIL 20180914 07:57:34 test_kernel_module_signatures LOG [2018-09-14 07:57:37,946] 24 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 1: Check for unassigned kernel modules on controller-0 [2018-09-14 07:57:37,947] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:37,947] 262 DEBUG MainThread ssh.send :: Send 'cat /proc/sys/kernel/tainted' [2018-09-14 07:57:38,050] 382 DEBUG MainThread ssh.expect :: Output: 12288 controller-0:~$ [2018-09-14 07:57:38,050] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,152] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,153] 32 ERROR MainThread test_kernel_modules.test_kernel_module_signatures:: Kernel module verification(s) failed on controller-0. Collecting more info [2018-09-14 07:57:38,153] 34 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 2: Check kern.log for modules with failed verification [2018-09-14 07:57:38,153] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,153] 262 DEBUG MainThread ssh.send :: Send 'grep --color=never -i "module verification failed" /var/log/kern.log' [2018-09-14 07:57:38,265] 382 DEBUG MainThread ssh.expect :: Output: 2018-09-13T19:09:51.212 localhost kernel: notice [ 6.271466] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-13T19:51:42.174 controller-0 kernel: notice [ 6.133741] e1000e: module verification failed: signature and/or required key missing - tainting kernel 2018-09-14T03:33:29.054 controller-0 kernel: notice [ 6.183120] e1000e: module verification failed: signature and/or required key missing - tainting kernel controller-0:~$ [2018-09-14 07:57:38,265] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,367] 382 DEBUG MainThread ssh.expect :: Output: 0 controller-0:~$ [2018-09-14 07:57:38,368] 43 INFO MainThread test_kernel_modules.test_kernel_module_signatures:: ====================== Test Step 3: Display signing info for controller-0 failed kernel modules: ['e1000e'] [2018-09-14 07:57:38,368] 419 DEBUG MainThread ssh.exec_cmd:: Executing command... [2018-09-14 07:57:38,368] 262 DEBUG MainThread ssh.send :: Send 'modinfo e1000e | grep --color=never -E "sig|filename"' [2018-09-14 07:57:38,474] 382 DEBUG MainThread ssh.expect :: Output: filename: /lib/modules/3.10.0-862.11.6.el7.36.tis.x86_64/weak-updates/e1000e/e1000e.ko signer: CentOS Linux kernel signing key sig_key: 58:7B:E7:83:22:7A:67:CA:49:54:D2:3B:57:AF:99:45:D3:AC:99:AC sig_hashalgo: sha256 controller-0:~$ [2018-09-14 07:57:38,475] 262 DEBUG MainThread ssh.send :: Send 'echo $?' [2018-09-14 07:57:38,577] 382 DEBUG MainThread ssh.expect :: Output: Thanks, Nimalini -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Thursday, September 13, 2018 10:05 AM To: McKenna, Jason; Martinez Monroy, Elio; Waheed, Numan; Rasa, Nimalini; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Thanks Jason for the update. Appreciate you can have a new build generated according to Shuicheng's email earlier. @Nimalini, please report any finding back. The failure test cases in your both reports, is this the bug link? https://bugs.launchpad.net/starlingx/+bug/1791818 Thanks. - cindy -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, September 13, 2018 9:35 PM To: Xie, Cindy ; Martinez Monroy, Elio ; Waheed, Numan ; Rasa, Nimalini ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update Hi Cindy, Will do. In the meantime, Nimalini (one of our validation gurus) was able to boot a build which I had done a couple of days ago, and perform sanity and our nightly regression suite. The results (attached) align with the 7.4 based master branch of StarlingX. -Jason > -----Original Message----- > From: Xie, Cindy > Sent: September 13, 2018 2:44 AM > To: Martinez Monroy, Elio ; McKenna, > Jason ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Elio, > We will provide you an updated ISO later today with the following: > - kernel upgrade to 3.10.0-862.11.6 > - symbol issue fixed: > https://bugs.launchpad.net/starlingx/+bug/1792257 > > Please help to do a sanity test based on this new ISO from Shuicheng on VE. > > @Jason, > Please re-generate a build using today's manifest with above fix. > Shuicheng shall be able to provide manifest with exact commitID. > @Numan, please abort your current testing w/ old ISO once you get a > new one from Jason and continue your sanity and regression on > bare-metal. I am not sure how long it takes, but please take priority > as we want merge back to mainline early next week. > > Thanks all for the support. > - cindy > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > Sent: Thursday, September 13, 2018 4:24 AM > To: Lin, Shuicheng ; Cordoba Malibran, Erich > ; Waheed, Numan > ; Rasa, Nimalini > ; starlingx-discuss at lists.starlingx.io; > Liu, ZhipengS ; Khalil, Ghada > ; Xie, Cindy > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > -----Original Message----- > > From: Lin, Shuicheng > > Sent: September 11, 2018 8:44 PM > > To: McKenna, Jason ; Cordoba Malibran, > > Erich ; Waheed, Numan > > ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Jason, > > Here is the dhcp src rpm we are using: > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > dhcp > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/dhcp-4.2.5 > > - > > 68.el7.centos.1.src.rpm > > > > For centos-release, there are two packages in the mirror lst, 1 src > > rpm for build, and 1 rpm for the mock environment. And it has the > > "slightly difference" in the names as you mentioned. > > Both of them could be found in the centos repo with the exact name. > > ./rpms_centos.lst:135:centos-release-7-5.1804.1.el7.centos.src.rpm > > ./rpms_centos.lst:136:centos-release-7-5.1804.el7.centos.x86_64.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url --source > > centos- release-7-5.1804.1.el7.centos > > http://vault.centos.org/7.5.1804/updates/Source/SPackages/centos- > > release-7-5.1804.1.el7.centos.src.rpm > > [slin14 at f998ec953c85 /]$ sudo -E yumdownloader -C --url > > centos-release-7- > > 5.1804.el7.centos.x86_64 > > http://mirror.centos.org/centos/7.5.1804/os/x86_64/Packages/centos- > > release-7-5.1804.el7.centos.x86_64.rpm > > > > If there is still some other rpm missing, you could try to find them > > from the repo. > > I have try my best to keep my local mirror the same as the lst. But > > it is still possible some package missed to be added to the repo lst. > > Please feel free to notify me or correct the error directly. > > Thanks. > > With the latest commits to stx-tools I am now able to download the > rpms and produce a build. I'll let you know how testing goes > > > > > Best Regards > > Shuicheng > > > > > > -----Original Message----- > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > Sent: Wednesday, September 12, 2018 12:21 AM > > To: Cordoba Malibran, Erich ; > > Waheed, Numan ; Rasa, Nimalini > > ; starlingx-discuss at lists.starlingx.io; > > Liu, ZhipengS ; Khalil, Ghada > > ; Lin, Shuicheng > > ; Xie, Cindy > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > Hi Cindy, > > > > With the latest centos75 branch (and the cherry-picks you mentioned) > > I am unable to produce a build. There seems to be several source > > rpm files missing from the currently pushed version of the .lst > > files (or the .lst files pull down the wrong version). Most of the > > missing files I can download manually, however the checked in > > patches for dhcp and centos-release packages do not apply against > > the version of the source RPM which I can manually find on the > > Internet. For example, the version of centos-release called out in > > the .lst is centos-release-7-5.1804.el7.centos.x86_64.rpm, the > > version called out in the checked in code base is the slightly > > different > > centos-release-7- 5.1804.el7.centos.1.x86_64.rpm, and the patches > checked in do not apply against either package. > > > > Until the centos75 branch of the lst files pulls down the correct > > rpms, I will be unable to continue the validation effort. > > > > -J > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich > > > Sent: September 11, 2018 11:17 AM > > > To: Waheed, Numan ; Rasa, Nimalini > > > ; > > > starlingx-discuss at lists.starlingx.io; > > > Liu, ZhipengS ; Khalil, Ghada > > > ; Lin, Shuicheng > > > ; McKenna, Jason > > > ; Xie, Cindy > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > > > > Hi > > > > > > You can add "debug loglevel=8" to the kernel boot option to get a > > > more detailed output of the crash (if any) > > > > > > -Erich > > > > > > On Tue, 2018-09-11 at 13:56 +0000, Xie, Cindy wrote: > > > > Shuicheng saw the symbol table error issue as well but it > > > > recovers in 8s, he is still working on debugging it. But 601204 > > > > is just kernel upgrade but not intended to solve this issues. > > > > Are you running bare metal? I am wondering if this is HW config and driver issue. > > > > > > > > Is it possible that you try to deploy it in virtual environment? > > > > > > > > Thx. - cindy > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:50 PM > > > > To: Xie, Cindy ; Rasa, Nimalini > > > > ; Waheed, Numan > > > > ; Lin, Shuicheng > > > > ; Liu, ZhipengS > > > l.com>; Khalil, Ghada ; > > > > 'starlingx-discus s at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Cindy, > > > > > > > > We got past the installation device error, but are coming up > > > > against the symbol table error. Our system hangs after this > > > > message. I suspect a kernel issue. I see there is an open code > > > > review to refactor some kernel patches to a rebased kernel > > > > (https://review.open > > > > stack.org/#/c/601204/) but I do not know if that is expected to > > > > resolve the issue > > > > > > > > -J > > > > > > > > From: Xie, Cindy > > > > Sent: September 11, 2018 9:32 AM > > > > To: Rasa, Nimalini ; Waheed, Numan > > > > > > n.Waheed at windriver.com>; Lin, Shuicheng > ; > > > > McKenna, Jason ; Liu, ZhipengS > > > > > > .liu at intel.com>; Khalil, Ghada ; > > > > 'starlin gx-discuss at lists.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > But as Jason reported yesterday, the build cannot be installed > > > > with error messages: > > > > > > > > Installation failed. > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > We cannot debug without more information, the ISO installs in > > > > Intel’s HW. Thus Shuicheng created a new build and attached a > > > > manifest in this email thread. Did WindRiver has a chance to > > > > create a new ISO using today’s manifest file and re-run the test? > > > > > > > > Thx. - cindy > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:25 PM > > > > To: Xie, Cindy ; Waheed, Numan > > > > > > driver.com>; Lin, Shuicheng ; McKenna, > > > > Jason ; Liu, ZhipengS > > > > > > > ; Khalil, Ghada ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > This is on the same build (yesterday’s build). > > > > > > > > From: Xie, Cindy [mailto:cindy.xie at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:22 AM > > > > To: Rasa, Nimalini; Waheed, Numan; Lin, Shuicheng; McKenna, > > > > Jason; Liu, ZhipengS; Khalil, Ghada; 'starlingx-discuss at lists.starlingx.io' > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Is this the same issue as yesterday’s build? or this is > > > > different issue now? > > > > > > > > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > > > > Sent: Tuesday, September 11, 2018 9:06 PM > > > > To: Waheed, Numan ; Lin, > Shuicheng > > > > > > heng.lin at intel.com>; McKenna, Jason > > ; > > > > Liu, ZhipengS ; Khalil, Ghada > > > > ; > > > > 'starlingx-discuss at lists.starlingx.io' > > > uss at lists.starlingx.io>; Xie, Cindy > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > It is not booting in my case. After the following , it just > > > > hangs > > > > there: > > > > “Error: no symbol table. > > > > Press any key to continue…” > > > > > > > > -Nimalini > > > > > > > > From: Waheed, Numan > > > > Sent: Tuesday, September 11, 2018 8:50 AM > > > > To: Lin, Shuicheng; McKenna, Jason; Liu, ZhipengS; Khalil, > > > > Ghada; 'st arlingx-discuss at lists.starlingx.io'; Xie, Cindy; > > > > Rasa, Nimalini > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Adding Nimalini > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: September-11-18 2:17 AM > > > > To: McKenna, Jason; Liu, ZhipengS; Khalil, Ghada; > > > > 'starlingx-discuss@ lists.starlingx.io'; Xie, Cindy; Waheed, > > > > Numan > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > Just finished deploy image with latest code, I could config > > > > controller successfully in bare metal environment. > > > > Manifest is created for you reference. There are two patches I > > > > add > > > > manually: > > > > https://review.openstack.org/596855           for > > > > python-horizon from master > > > > https://review.openstack.org/599892           for build-iso > > > > > > > > > > > > There is an issue found when reboot controller node. > > > > After the OS selection menu, it will show below error. And it > > > > will auto continue boot after around 8 seconds. I will check the > > > > issue later. > > > > “ > > > > Error: no symbol table. > > > > Press any key to continue… > > > > “ > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Tuesday, September 11, 2018 9:35 AM > > > > To: McKenna, Jason ; Liu, ZhipengS > > > > > > engs.liu at intel.com>; Khalil, Ghada ; > > > > 'sta rlingx-discuss at lists.starlingx.io' > > > > > > > .io>; Xie, Cindy ; Waheed, Numan > > > > > > indriver.com> > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I just tried my last Friday’s image at bare metal machine. There > > > > is no issue to install controller node. > > > > Will you help check what cause the install error in your environment? > > > > > > > > I am syncing my code to latest to double confirm it. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Tuesday, September 11, 2018 12:13 AM > > > > To: Liu, ZhipengS ; Lin, Shuicheng > > > > ; Khalil, Ghada > > > > ; 'starlin > > > > gx-discuss at lists.starlingx.io' > > > > > > > > ; Xie, Cindy ; Waheed, Numan > > > > > > iver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Status update. The build from the centos75 branch does not > > > > install on our hardware. The error message we are seeing is: > > > > > > > > Installation failed. > > > > > > > > ERROR: Specified installation (sda) or boot (sda) device is invalid. > > > > > > > > -Jason > > > > > > > > From: Liu, ZhipengS > > > > Sent: September 8, 2018 9:56 AM > > > > To: Lin, Shuicheng ; McKenna, Jason > > > > ; Khalil, Ghada > > > > ; 's > > > > tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Jason, > > > > > > > > I have fixed the issue you mentioned below. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > https://review.openstack.org/#/c/600920/ > > > > > > > > Thanks! > > > > Zhipeng > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: 2018年9月8日 21:14 > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > I have fixed the error in the openstack-aodh. Patch is updated: > > > > https://review.openstack.org/#/c/598388/ > > > > > > > > It is due to my local version is not the latest one. > > > > Sorry for the trouble caused, and thanks for your test. > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Saturday, September 8, 2018 9:23 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Jason, > > > > Thanks very much for such detail feedback. > > > > I added some comments inline, and will check the issue in my > > > > environment also. > > > > Feel free to submit patch if you have to fix them. J > > > > > > > > > > > > Best Regards > > > > Shuicheng > > > > > > > > From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] > > > > Sent: Saturday, September 8, 2018 3:47 AM > > > > To: McKenna, Jason ; Khalil, Ghada > > > > > > a.Khalil at windriver.com>; Lin, Shuicheng > > > > ; 's tarlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > @windriver.com> > > > > Subject: RE: CentOS 7.5 upgrade status update > > > > > > > > Hi Shuicheng, > > > > > > > > I’ve completed a build of the code. We have not yet run > > > > run-time tests, but here are the build-time issues I encountered: > > > > > > > > - The .lst file contains lighttpd-1.4.49, but this is no > > > > longer available for download, and the download_mirrors.sh step fails. > > > > It appears than CentOS has updated to lighttpd-1.4.50. I > > > > manually built a lighttpd-1.4.49-1.src.rpm to satisfy the .lst > > > > - Even though the .lst file specifies lighttpd-1.4.49, the > > > > code still references 1.4.45 > > > > - At build-pkgs time (the build-srpms step), the meta-patches > > > > to openstack-aodh do not apply, as two of them are malformed. https: > > > > //review.openstack.org/#/c/598388/6/openstack/openstack- > > > > aodh/centos/meta_patches/0001-Modify-service-files-and-create- > > > > expirer-cron-script.patch -- In the new version, on line 190, > > > > the patch states that the old code covered 6 lines, and the new > > > > code covers 9 lines (-283,6 +286,9). But there are only two > > > > lines inserted by the patch. There is also a new blank line in > > > > the patch at line 194. Removing this blank line and editing the > > > > hunk description to only insert 2 lines resolves the issue for > > > > this hunk (there are other similar issues in this patch, and in > > > > 0001-meta- > > > > modify-aodh-api.patch) > > > > [slin14]: Let me double check it. > > > > - At binary build time, I had build failures on python-django- > > > > horizon and some magnum packages. I had to pull in > > > > https://review.op > > > > enstack.org/#/c/596855/2 (from the master branch, but not in the > > > > centos75 branch of stx-upstream) to get past this. > > > > [slin14]: It is due to I have not synced latest master code, so > > > > I don’t have this issue. I used last week’s master code. > > > > - After building all packages, I attempted to build the ISO. > > > > The tpm2-tss-1.3.0-2.el7.x86_64.rpm package were missing, and > > > > should be added to the .lst files. > > > > [slin14]: This package is already in the lst. > > > > - Furthermore, the tpm2-tools package was requesting version > > > > tpm2-tss-1.3.0-2.el7.centos (rather than tpm2-tss-1.3.0-2.el7). > > > > I hacked the spec file for tpm2-tools and rebuilt it to require > > > > the version mentioned, but there is some rework to be done there. > > > > [slin14]: I have the same issue also. Let’s further check it to > > > > find the root cause. I use rebuild tpm2-tools/tss2 to workaround > > > > it without any code. > > > > > > > > After these changes, I was able to produce a .iso > > > > > > > > -Jason > > > > > > > > From: McKenna, Jason > > > > Sent: September 7, 2018 10:08 AM > > > > To: Khalil, Ghada ; Lin, Shuicheng > > > > ; 'starlingx-discuss at lists.starlingx.io' > > > > ; Xie, Cindy > > > > ; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Hi Shuicheng, > > > > > > > > As a download_mirrors.sh time issue, the version of lighttpd has > > > > been changed from 1.4.45 to 1.4.49. The > > > > lighttpd-1.4.49-1.el7.src.rpm file no longer exists on EPEL or > > > > CentOS servers, as they’ve moved to 1.4.50. I am attempting to > > > > locate an archived version of the 1.4.49 .src rpm. > > > > > > > > -Jason > > > > > > > > From: Khalil, Ghada > > > > Sent: September 7, 2018 9:36 AM > > > > To: Lin, Shuicheng ; > > > > 'starlingx-discuss at list s.starlingx.io' > > > > ; Xie, Cindy > > > indy.xie at intel.com>; Waheed, Numan > > > > > > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status > > > > update > > > > > > > > Thanks Shuicheng. We’ll run some tests in Wind River. Numan will > > > > be priming this activity. He’ll share the results with the team > > > > sometime next week. > > > > > > > > Regards, > > > > Ghada > > > > > > > > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > > > > Sent: Friday, September 07, 2018 1:32 AM > > > > To: 'starlingx-discuss at lists.starlingx.io'; Khalil, Ghada; Xie, > > > > Cindy > > > > Subject: CentOS 7.5 upgrade status update > > > > > > > > Hi all, > > > > Most task of CentOS7.5 upgrade in story 2003389 is done. Please > > > > go ahead to have a try and verify it. > > > > I expect there should be some issue due to we just did limited > > > > deploy test yet. > > > > > > > > Here is the detail status update of this week. > > > > For the total 44 srpm we plan to upgrade: > > > > 38 already merged in feature branch. > > > > 3 kept as original version. Anaconda upgrade is not needed. > > > > python- os-vif has higher version than 7.5. python-eventlet kept > > > > due to new src rpm itself have known issue. > > > > 2 under review with code ready. Puppet-haproxy and openstack-aodh. > > > > 1 under debug. Lighttpd. > > > > > > > > Besides srpm, we also upgraded 260+ rpm packages to 7.5 version. > > > > > > > > Here is the build instruction: > > > > 1. Switch to f/centos75 branch for stx-tools/stx-integ/stx- > > > > upstream/stx-root. > > > > Cherry-pick below un-merged patch: > > > > For puppet-haproxy: > > > > https://review.openstack.org/600369 > > > > https://review.openstack.org/600359 > > > > For openstack-aodh: > > > > https://review.openstack.org/598388 > > > > https://review.openstack.org/600591 > > > > For build-iso: > > > > https://review.openstack.org/599892 > > > > For build-pkgs: > > > > https://review.openstack.org/599901 > > > > https://review.openstack.org/600639 > > > > > > > > 2. Run mirror script to get the upgraded src rpm and related > > > > rpm. > > > > 3. Try to build packages and ISO. > > > > > > > > For the detail status of CentOS7.5 upgrade, please check below story: > > > > https://storyboard.openstack.org/#!/story/2003389 > > > > > > > > Feel free to contact me if you have trouble on it. > > > > > > > > Best Regards > > > > Shuicheng > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-dis > > > > cu > > > > ss From Ghada.Khalil at windriver.com Tue Sep 18 13:56:53 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 18 Sep 2018 13:56:53 +0000 Subject: [Starlingx-discuss] StarlingX Release Notes Content In-Reply-To: References: Message-ID: <151EE31B9FCCA54397A757BC674650F0BA454061@ALA-MBD.corp.ad.wrs.com> Thanks Abraham. It's great to see that the infrastructure is ready for the release notes. I want to send a few reminders to the project leads about the release notes (based on the October Release kick-off meeting held on Sept 5): o Agreed to generate high level release notes only (ex: no list of solved or open bugs, no list of every enhancement) o Doc team is automating the generation of the release notes. o Automated release notes are created per repo. o Each sub-team decides whether to list some key features or at least an introduction to the sub-project (main functionality, etc) Regards, Ghada -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Monday, September 17, 2018 11:30 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] StarlingX Release Notes Content To all StarlingX main and supporting projects leaders: In preparation to complete our documentation journey we need your help to write under this etherpad page [0] the content for your Release Notes including a Prelude and a couple of features to be added in your project repository, we are targeting this task to be completed if possible, end of this week. Please take a look at the example from Dean in the same etherpad page [0] submitted though a stx-tools gerrit review [1], we will take your information from the Etherpad and we will add it to the Release Notes commit. [0] https://etherpad.openstack.org/p/stx-docs [1] https://review.openstack.org/#/c/600198/3/releasenotes/notes/release-summary-9c35dd1bd9b020f1.yaml _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Tue Sep 18 14:27:02 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 18 Sep 2018 09:27:02 -0500 Subject: [Starlingx-discuss] FW: PTG upstreaming discussion In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB27078E@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB27078E@ALA-MBD.corp.ad.wrs.com> Message-ID: On Mon, 17 Sep 2018, Jolliffe, Ian wrote: > and the notes below summarize the outcomes. This does not reflect the outcomes of the > direct engagement with the Neutron and Nova teams, that summary will follow. Here are my notes from Friday afternoon's Nova session, line numbers are in the Nova etherpad as of writing this * Y: vcpu models (begins line 872): (patch 0012, more?) cfriesen to write a spec for listing CPU models in nova.conf * Y: read-only API additions (line 893): (part of patch 0024, others?) one spec and one microversion will cover the additional bits reported in server show returns (GET /servers) * N: non-default quotas (line 907): this is changed in the transition to unified limits in Keystone, can be handled in client libs * Y: I/O semaphore (line 910): (first part of patch 0015) new config option to limit concurrent high-IOPS operations * Y: Flavor extra spec and image validation (line 919): (patch 0022) validate the bits that are not virt driver-specific * Y: periodic orphan resource cleanup (line 927): (patch 0018) add a name check for configured prefixes marked as deleted in database, kill if still running * N: libvirt reboot timeout (line 936): (patch 0020) maybe document hard reboot alternative * N: compute node latency/power mgmt (line 941): new enough libvirt can do this? sean-k-mooney checking, preference to push this into hypervisor * Y: HPET (line 945): (patch 0068) no spec required, bp only; also implemented in cyborg * Y: NUMA-aware live migration (line 953): Artom will continue (spec https://review.openstack.org/#/c/599587/) > Python-Clients: items need to map to main project server-side disposition. Additionally, we > agreed we should move the clients as close to master as possible, this can be done > independently as this provides users backward compatibility. More details: client libs, OpenStack SDK and OpenStackClient are all released independently from the main release cycle, although there are cycle stable branches maintained for co-installability/dependency issues. The major client changes are in areas that can be maintained separately from the upstream (OSC plugins, SDK-like addon libs), I would like to consider keeping the user-facing bits as close to current release (maybe not quite on master) as possible. > We made lots of updates to the google-spreadsheet in real time. [0] I am going back through my notes to update Jira tickets to reflect the spreadsheet changes I made... dt -- Dean Troyer dtroyer at gmail.com From Jason.McKenna at windriver.com Tue Sep 18 14:27:52 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Tue, 18 Sep 2018 14:27:52 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <65CE126717DEA145BD6B2C2842DC52D66C0C7A53@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535753F@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA45056C@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C7655357876@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535793D@SHSMSX101.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F8417A@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765535812B@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553581C0@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481EC303@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6174@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FB92@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C6195@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FBFD@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B33FC84@SHSMSX104.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A725@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7A53@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi folks, I do not think the kernel signature item is a real issue, but an artifact of how we built the test image. The warning reported is basically saying that the driver was compiled against a different build of the kernel than is currently running. This is typical for intermediate builds where a kernel was compiled, the driver was compiled, and the kernel compiled again (which was the case when I was attempting to get the CentOS 7.5 test load built as the contents in the repos were changing). I will clean the kernel driver packages the next time I perform a build and we can verify that the error disappears. -J For anyone interested in technical details, the kernel regenerates a key pair every time it is built, and compiles one half into the kernel and puts the other half in the kernel-devel package. Packages (like kernel drivers) building against the kernel-devel package will sign themselves with the key from the package. Upon loading a driver, the kernel will validate that the signature on the driver matches the half of the key which the kernel has access to. A mismatched key indicates that the kernel running and kernel-devel package which the driver was built against came from 2 different builds of the kernel, and marks the kernel tainted as a warning. > -----Original Message----- > From: Rasa, Nimalini > Sent: September 18, 2018 9:50 AM > To: Lin, Shuicheng ; Xie, Cindy > ; McKenna, Jason ; > Martinez Monroy, Elio ; Waheed, Numan > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Shuicheng, > It does have the correct version: > controller-0:~$ uname -a > Linux controller-0 3.10.0-862.11.6.el7.36.tis.x86_64 #1 SMP PREEMPT Thu Sep > 13 10:48:38 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux > > Thanks, > Nimalini > > -----Original Message----- > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > Sent: Monday, September 17, 2018 9:16 PM > To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; > Waheed, Numan; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Nimalini, > For the kernel signature issue, could you help confirm whether the kernel > version is 3.10.0-862.11.6 or not? > You could check it with "uname -a" or search it in the kern.log file. > Thanks. > > Best Regards > Shuicheng > > > -----Original Message----- > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > Sent: Tuesday, September 18, 2018 12:21 AM > To: Lin, Shuicheng ; Xie, Cindy > ; McKenna, Jason ; > Martinez Monroy, Elio ; Waheed, Numan > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Shuicheng, > In this test case, basically trying to allocate double the amount of 2M pages. > > For the kernel signature, I tried it on 3 different hardware labs and got the > following: > controller-0:~$ cat /proc/sys/kernel/tainted > 12288 > controller-0:~$ grep --color=never -i "module verification failed" > /var/log/kern.log > 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: > module verification failed: signature and/or required key missing - tainting > kernel > 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: > module verification failed: signature and/or required key missing - tainting > kernel > > > Thanks, > Nimalini > > -----Original Message----- > From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > Sent: Friday, September 14, 2018 9:13 PM > To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; > Waheed, Numan; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Nimalini, > Could you share me the detail reproduce step for " > test_schedule_vm_mempage_config"? > > For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual > and bare metal environment, and both of them show 4096. Then what > should I do next? > " > controller-0:~$ cat /proc/sys/kernel/tainted > 4096 > controller-0:~$ grep --color=never -i "module verification failed" > /var/log/kern.log controller-0:~$ " > > Best Regards > Shuicheng > > -----Original Message----- > From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > Sent: Saturday, September 15, 2018 3:02 AM > To: Xie, Cindy ; McKenna, Jason > ; Martinez Monroy, Elio > ; Waheed, Numan > ; starlingx-discuss at lists.starlingx.io > Cc: Khalil, Ghada ; Lin, Shuicheng > > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > Hi Cindy, > Adding more clarification of the test cases that are failed: > > FAIL 20180914 06:54:06 > test_schedule_vm_mempage_config[1048576] > Test case is trying to over allocate 2M pages, expected to reject the cli, in > this case it's accepted. > > FAIL 20180914 07:57:34 test_kernel_module_signatures > Test case is doing the following: > - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following > steps: > - 'grep --color=never -i "module verification failed" /var/log/kern.log' to > find out failed modules > - 'modinfo | grep --color=never -E "sig|filename" to > display signing info for each module > > > Hope it clarifies bit more as to what the test cases it trying to do. If you have > any questions please let me know. > > Thanks, > Nimalini From Matt.Peters at windriver.com Tue Sep 18 14:56:17 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Tue, 18 Sep 2018 14:56:17 +0000 Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming In-Reply-To: References: Message-ID: <16E8ABC3-4BD3-4EC1-B32E-B8133A13A0CC@windriver.com> Hi Chenjie, I think the RFE looks good. I have no specific comments about the content, however, I think the references should be checked since there are duplicates. Everything else looks great. Regards, Matt From: "Xu, Chenjie" Date: Monday, September 17, 2018 at 3:18 AM To: "Peters, Matt" Cc: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming Hi Matt, We analyze the patch 4ae5a58 related to l2pop. An RFE has been written(You can find it in the attachment). Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Sep 18 14:58:01 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 18 Sep 2018 14:58:01 +0000 Subject: [Starlingx-discuss] when and how is squashfs.img used? In-Reply-To: <985E7A51-AC95-4038-B927-A7564B312561@intel.com> References: <985E7A51-AC95-4038-B927-A7564B312561@intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3B1B6D@ALA-MBD.corp.ad.wrs.com> When the nodes install via pxeboot, they’ll retrieve the initrd and vmlinuz (kernel) via TFTP from the active controller. The initrd and squashfs.img must contain the same kernel and modules. The initrd loads up the kernel and modules, detects NICs, and retrieves the squashfs.img via HTTP. Once downloaded, it’s mounted and is the rootfs for the installer, with a chroot. The installer runs, Anaconda is launched and downloads the appropriate kickstart file. Anaconda installs all the required software, does various post-install steps, then reboots the node. At this point, the system boots from disk, running the installed kernel and software, and the installer images are not used. From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Tuesday, September 18, 2018 12:12 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] when and how is squashfs.img used? As a part of pxe-network-installer-1.0-27.tis.x86_64.rpm, my understanding is that Squashfs.img will be mounted by nodes (such as 2nd controller, compute nodes and storage nodes) during the process of PXE boot installation. However, these questions are in my mind: 1. Will be squashfs.img still being used *AFTER installation*? 2. Where is squashfs.img mounted? I checked /etc/fstab, and there is no such an item. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Tue Sep 18 15:14:39 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Tue, 18 Sep 2018 15:14:39 +0000 Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming In-Reply-To: References: Message-ID: <516A4DFA-1915-4288-A547-CB08CF80836D@windriver.com> Hi Ildikó, This RFE is specific to neutron, therefore I think it makes sense to publish this to the neutron-specs for review rather than the stx-specs. I do agree that the mailing list is not the best way to exchange review comments and makes sense to ensure the docs are pushed to an appropriate spec repo as soon as possible. Regards, Matt On 2018-09-18, 3:46 AM, "Ildiko Vancsa" wrote: Hi, I think the attached document would be a great candidate to be proposed as a spec to stx-specs. That way you can send out the link to the Gerrit review which works better with the mail archive as well as it is accessible from there too. Gerrit also helps with reviews but doesn’t force you to keep all the discussions there you can always reference the review link in mail threads. What do you think about moving the document there? Thanks, Ildikó > On 2018. Sep 17., at 9:17, Xu, Chenjie wrote: > > > > Hi Matt, > We analyze the patch 4ae5a58 related to l2pop. An RFE has been written(You can find it in the attachment). Could you please help to review and comment? Thanks very much! > > > Best Regards, > Xu, Chenjie > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Tue Sep 18 15:25:46 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 18 Sep 2018 17:25:46 +0200 Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming In-Reply-To: <516A4DFA-1915-4288-A547-CB08CF80836D@windriver.com> References: <516A4DFA-1915-4288-A547-CB08CF80836D@windriver.com> Message-ID: <2D33A87F-DE93-4EF7-8E50-D447EDFCBB54@gmail.com> Hi Matt, I missed the Neutron bit, thanks for clarifying that. Totally agree to upload it to neutron-specs. Thanks, Ildikó > On 2018. Sep 18., at 17:14, Peters, Matt wrote: > > Hi Ildikó, > This RFE is specific to neutron, therefore I think it makes sense to publish this to the neutron-specs for review rather than the stx-specs. I do agree that the mailing list is not the best way to exchange review comments and makes sense to ensure the docs are pushed to an appropriate spec repo as soon as possible. > > Regards, Matt > > > On 2018-09-18, 3:46 AM, "Ildiko Vancsa" wrote: > > Hi, > > I think the attached document would be a great candidate to be proposed as a spec to stx-specs. That way you can send out the link to the Gerrit review which works better with the mail archive as well as it is accessible from there too. > > Gerrit also helps with reviews but doesn’t force you to keep all the discussions there you can always reference the review link in mail threads. > > What do you think about moving the document there? > > Thanks, > Ildikó > > >> On 2018. Sep 17., at 9:17, Xu, Chenjie wrote: >> >> >> >> Hi Matt, >> We analyze the patch 4ae5a58 related to l2pop. An RFE has been written(You can find it in the attachment). Could you please help to review and comment? Thanks very much! >> >> >> Best Regards, >> Xu, Chenjie >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > From erich.cordoba.malibran at intel.com Tue Sep 18 15:51:11 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 18 Sep 2018 15:51:11 +0000 Subject: [Starlingx-discuss] Build installer instructions In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA3B1324@ALA-MBD.corp.ad.wrs.com> References: <036cf4d515df4e287fcd2d52dca3bb795c0a6fc4.camel@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3B1324@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks for the feedback :) I updated the documentation in the wiki. I included the note that this procedure doesn't need to be done frequently.. Here is the wiki link: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Build_installer -Erich On Mon, 2018-09-17 at 16:40 +0000, Penney, Don wrote: > It's good to note that if you've already got installer images > generated (ie. on a shared system, in /import/mirror/CentOS/tis- > installer), you don't need to run "build-pkgs --installer". So > presumably, this would not be part of a general designer workflow. > > Historically, we upversioned these images whenever they were updated, > but this introduces some challenges under Starling-X. It may make > sense to drop the version number from the images as referenced in the > pxe-network-installer package build, essentially treating it as a > .latest version. Individuals or groups could then manage their own > installer version history as they see fit, ie. build images with 0.1, > 0.2, 0.3, with symlinks to the latest perhaps. If these images aren't > being hosted somewhere, if individuals/groups are generating their > own, then the versioning shouldn't be in the build files. > > > > -----Original Message----- > From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.co > m] > Sent: Monday, September 17, 2018 12:12 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Build installer instructions > > Hi, > > I would like to share/discuss the instructions to generate the > installer before are publish into the wiki. I couldn't find a > previous > version of these instructions, probably I confused with this warning > from the download_mirror.sh[0]. The update-pxe-network-installer > script > follows the steps detailed here[1]. > > Build installer > =============== > > To get your StarlingX ISO ready to use, you will need to create the > init files that will be used to boot the ISO as well to boot > additional > controllers and compute nodes. > > Once you had run `build-iso`, run: > > ``` > build-pkgs --installer > ``` > > This will build `rpm` and `anaconda` packages. Then run: > > ``` > update-pxe-network-installer > ``` > > The update-pxe-network-installer` covers the steps detailed in > `$MY_REPO/stx/stx-metal/installer/initrd/README`. This script will > create three files on `/localdisk/loadbuild///pxe- > network-installer/output` > > ``` > new-initrd.img > new-squashfs.img > new-vmlinuz > ``` > > Then, rename them to: > > ``` > initrd.img-stx-0.2 > squashfs.img-stx-0.2 > vmlinuz-stx-0.2 > ``` > > There are two ways to use these files: > > 1. Store the files in the '/import/mirror/CentOS/tis-installer/` > folder for future use. > 2. Store it in an arbitrary location and modify the > `$MY_REPO/stx/stx- > metal/installer/pxe-network-installer/centos/build_srpm.data` file to > point to these files. > > Now, the `pxe-network-installer` package needs to be recreated and > the > ISO regenerated. > > ``` > build-pkgs --clean pxe-network-installer > build-pkgs pxe-network-installer > build-iso > ``` > > Now your ISO should be able to boot. > > Updating these files is not a common tasks, it is recommended only do > it if the kernel version is upgraded or new kernel modules are added. > > > ===================== > End of documentation > > > > [0] http://git.starlingx.io/cgit/stx-tools/tree/centos-mirror-tools/d > ownload_mirror.sh#n264 > [1] http://git.starlingx.io/cgit/stx-metal/tree/installer/initrd/READ > ME > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Tue Sep 18 16:07:41 2018 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 18 Sep 2018 09:07:41 -0700 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A725@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7A53@ALA-MBD.corp.ad.wrs.com> Message-ID: Jason, So if I am understand this correct the test_kernel_module_signatures failure listed below is a not an issue due to the way WR built the kernel and modules? Why was this build differently by WR than you would normally build an image for testing? Wouldn't you always have this signature problem then? I am just trying to understand what differences in the way WR builds and the way that is documented, just as we had the issue with the installer setup. Nimalini: Given this information, do we have any blockers for the 7.5 upgrade? Thanks Sau! On 09/18/2018 07:27 AM, McKenna, Jason wrote: > Hi folks, > > I do not think the kernel signature item is a real issue, but an artifact of how we built the test image. > > The warning reported is basically saying that the driver was compiled against a different build of the kernel than is currently running. This is typical for intermediate builds where a kernel was compiled, the driver was compiled, and the kernel compiled again (which was the case when I was attempting to get the CentOS 7.5 test load built as the contents in the repos were changing). I will clean the kernel driver packages the next time I perform a build and we can verify that the error disappears. > > -J > > For anyone interested in technical details, the kernel regenerates a key pair every time it is built, and compiles one half into the kernel and puts the other half in the kernel-devel package. Packages (like kernel drivers) building against the kernel-devel package will sign themselves with the key from the package. Upon loading a driver, the kernel will validate that the signature on the driver matches the half of the key which the kernel has access to. A mismatched key indicates that the kernel running and kernel-devel package which the driver was built against came from 2 different builds of the kernel, and marks the kernel tainted as a warning. > >> -----Original Message----- >> From: Rasa, Nimalini >> Sent: September 18, 2018 9:50 AM >> To: Lin, Shuicheng ; Xie, Cindy >> ; McKenna, Jason ; >> Martinez Monroy, Elio ; Waheed, Numan >> ; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Hi Shuicheng, >> It does have the correct version: >> controller-0:~$ uname -a >> Linux controller-0 3.10.0-862.11.6.el7.36.tis.x86_64 #1 SMP PREEMPT Thu Sep >> 13 10:48:38 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux >> >> Thanks, >> Nimalini >> >> -----Original Message----- >> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >> Sent: Monday, September 17, 2018 9:16 PM >> To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; >> Waheed, Numan; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Hi Nimalini, >> For the kernel signature issue, could you help confirm whether the kernel >> version is 3.10.0-862.11.6 or not? >> You could check it with "uname -a" or search it in the kern.log file. >> Thanks. >> >> Best Regards >> Shuicheng >> >> >> -----Original Message----- >> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] >> Sent: Tuesday, September 18, 2018 12:21 AM >> To: Lin, Shuicheng ; Xie, Cindy >> ; McKenna, Jason ; >> Martinez Monroy, Elio ; Waheed, Numan >> ; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Hi Shuicheng, >> In this test case, basically trying to allocate double the amount of 2M pages. >> >> For the kernel signature, I tried it on 3 different hardware labs and got the >> following: >> controller-0:~$ cat /proc/sys/kernel/tainted >> 12288 >> controller-0:~$ grep --color=never -i "module verification failed" >> /var/log/kern.log >> 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: >> module verification failed: signature and/or required key missing - tainting >> kernel >> 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: >> module verification failed: signature and/or required key missing - tainting >> kernel >> >> >> Thanks, >> Nimalini >> >> -----Original Message----- >> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >> Sent: Friday, September 14, 2018 9:13 PM >> To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, Elio; >> Waheed, Numan; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Hi Nimalini, >> Could you share me the detail reproduce step for " >> test_schedule_vm_mempage_config"? >> >> For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in my virtual >> and bare metal environment, and both of them show 4096. Then what >> should I do next? >> " >> controller-0:~$ cat /proc/sys/kernel/tainted >> 4096 >> controller-0:~$ grep --color=never -i "module verification failed" >> /var/log/kern.log controller-0:~$ " >> >> Best Regards >> Shuicheng >> >> -----Original Message----- >> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] >> Sent: Saturday, September 15, 2018 3:02 AM >> To: Xie, Cindy ; McKenna, Jason >> ; Martinez Monroy, Elio >> ; Waheed, Numan >> ; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada ; Lin, Shuicheng >> >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Hi Cindy, >> Adding more clarification of the test cases that are failed: >> >> FAIL 20180914 06:54:06 >> test_schedule_vm_mempage_config[1048576] >> Test case is trying to over allocate 2M pages, expected to reject the cli, in >> this case it's accepted. >> >> FAIL 20180914 07:57:34 test_kernel_module_signatures >> Test case is doing the following: >> - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If not, do following >> steps: >> - 'grep --color=never -i "module verification failed" /var/log/kern.log' to >> find out failed modules >> - 'modinfo | grep --color=never -E "sig|filename" to >> display signing info for each module >> >> >> Hope it clarifies bit more as to what the test cases it trying to do. If you have >> any questions please let me know. >> >> Thanks, >> Nimalini > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Nimalini.Rasa at windriver.com Tue Sep 18 16:58:35 2018 From: Nimalini.Rasa at windriver.com (Rasa, Nimalini) Date: Tue, 18 Sep 2018 16:58:35 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A725@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7A53@ALA-MBD.corp.ad.wrs.com> Message-ID: <65CE126717DEA145BD6B2C2842DC52D66C0C7AB6@ALA-MBD.corp.ad.wrs.com> We don't have any blockers now. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, September 18, 2018 12:08 PM To: McKenna, Jason; Rasa, Nimalini; Lin, Shuicheng; Xie, Cindy; Martinez Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update Jason, So if I am understand this correct the test_kernel_module_signatures failure listed below is a not an issue due to the way WR built the kernel and modules? Why was this build differently by WR than you would normally build an image for testing? Wouldn't you always have this signature problem then? I am just trying to understand what differences in the way WR builds and the way that is documented, just as we had the issue with the installer setup. Nimalini: Given this information, do we have any blockers for the 7.5 upgrade? Thanks Sau! On 09/18/2018 07:27 AM, McKenna, Jason wrote: > Hi folks, > > I do not think the kernel signature item is a real issue, but an artifact of how we built the test image. > > The warning reported is basically saying that the driver was compiled against a different build of the kernel than is currently running. This is typical for intermediate builds where a kernel was compiled, the driver was compiled, and the kernel compiled again (which was the case when I was attempting to get the CentOS 7.5 test load built as the contents in the repos were changing). I will clean the kernel driver packages the next time I perform a build and we can verify that the error disappears. > > -J > > For anyone interested in technical details, the kernel regenerates a key pair every time it is built, and compiles one half into the kernel and puts the other half in the kernel-devel package. Packages (like kernel drivers) building against the kernel-devel package will sign themselves with the key from the package. Upon loading a driver, the kernel will validate that the signature on the driver matches the half of the key which the kernel has access to. A mismatched key indicates that the kernel running and kernel-devel package which the driver was built against came from 2 different builds of the kernel, and marks the kernel tainted as a warning. > >> -----Original Message----- >> From: Rasa, Nimalini >> Sent: September 18, 2018 9:50 AM >> To: Lin, Shuicheng ; Xie, Cindy >> ; McKenna, Jason ; >> Martinez Monroy, Elio ; Waheed, Numan >> ; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Hi Shuicheng, >> It does have the correct version: >> controller-0:~$ uname -a >> Linux controller-0 3.10.0-862.11.6.el7.36.tis.x86_64 #1 SMP PREEMPT >> Thu Sep >> 13 10:48:38 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux >> >> Thanks, >> Nimalini >> >> -----Original Message----- >> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >> Sent: Monday, September 17, 2018 9:16 PM >> To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, >> Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Hi Nimalini, >> For the kernel signature issue, could you help confirm whether the >> kernel version is 3.10.0-862.11.6 or not? >> You could check it with "uname -a" or search it in the kern.log file. >> Thanks. >> >> Best Regards >> Shuicheng >> >> >> -----Original Message----- >> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] >> Sent: Tuesday, September 18, 2018 12:21 AM >> To: Lin, Shuicheng ; Xie, Cindy >> ; McKenna, Jason ; >> Martinez Monroy, Elio ; Waheed, Numan >> ; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Hi Shuicheng, >> In this test case, basically trying to allocate double the amount of 2M pages. >> >> For the kernel signature, I tried it on 3 different hardware labs and >> got the >> following: >> controller-0:~$ cat /proc/sys/kernel/tainted >> 12288 >> controller-0:~$ grep --color=never -i "module verification failed" >> /var/log/kern.log >> 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: >> module verification failed: signature and/or required key missing - >> tainting kernel >> 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: >> module verification failed: signature and/or required key missing - >> tainting kernel >> >> >> Thanks, >> Nimalini >> >> -----Original Message----- >> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] >> Sent: Friday, September 14, 2018 9:13 PM >> To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, >> Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Hi Nimalini, >> Could you share me the detail reproduce step for " >> test_schedule_vm_mempage_config"? >> >> For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in >> my virtual and bare metal environment, and both of them show 4096. >> Then what should I do next? >> " >> controller-0:~$ cat /proc/sys/kernel/tainted >> 4096 >> controller-0:~$ grep --color=never -i "module verification failed" >> /var/log/kern.log controller-0:~$ " >> >> Best Regards >> Shuicheng >> >> -----Original Message----- >> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] >> Sent: Saturday, September 15, 2018 3:02 AM >> To: Xie, Cindy ; McKenna, Jason >> ; Martinez Monroy, Elio >> ; Waheed, Numan >> ; starlingx-discuss at lists.starlingx.io >> Cc: Khalil, Ghada ; Lin, Shuicheng >> >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update >> >> Hi Cindy, >> Adding more clarification of the test cases that are failed: >> >> FAIL 20180914 06:54:06 >> test_schedule_vm_mempage_config[1048576] >> Test case is trying to over allocate 2M pages, expected to reject >> the cli, in this case it's accepted. >> >> FAIL 20180914 07:57:34 test_kernel_module_signatures >> Test case is doing the following: >> - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If >> not, do following >> steps: >> - 'grep --color=never -i "module verification failed" >> /var/log/kern.log' to find out failed modules >> - 'modinfo | grep --color=never -E >> "sig|filename" to display signing info for each module >> >> >> Hope it clarifies bit more as to what the test cases it trying to do. >> If you have any questions please let me know. >> >> Thanks, >> Nimalini > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From bruce.e.jones at intel.com Tue Sep 18 17:28:58 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 18 Sep 2018 17:28:58 +0000 Subject: [Starlingx-discuss] StarlingX Release Notes Content In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA454061@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA454061@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5908B6@fmsmsx115.amr.corp.intel.com> I've created a wiki page we can use for draft release notes. I've included some initial content from a spreadsheet that Ghada prepared. Please feel free to update as needed. https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Release_Notes brucej -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, September 18, 2018 6:57 AM To: Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] StarlingX Release Notes Content Thanks Abraham. It's great to see that the infrastructure is ready for the release notes. I want to send a few reminders to the project leads about the release notes (based on the October Release kick-off meeting held on Sept 5): o Agreed to generate high level release notes only (ex: no list of solved or open bugs, no list of every enhancement) o Doc team is automating the generation of the release notes. o Automated release notes are created per repo. o Each sub-team decides whether to list some key features or at least an introduction to the sub-project (main functionality, etc) Regards, Ghada -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Monday, September 17, 2018 11:30 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] StarlingX Release Notes Content To all StarlingX main and supporting projects leaders: In preparation to complete our documentation journey we need your help to write under this etherpad page [0] the content for your Release Notes including a Prelude and a couple of features to be added in your project repository, we are targeting this task to be completed if possible, end of this week. Please take a look at the example from Dean in the same etherpad page [0] submitted though a stx-tools gerrit review [1], we will take your information from the Etherpad and we will add it to the Release Notes commit. [0] https://etherpad.openstack.org/p/stx-docs [1] https://review.openstack.org/#/c/600198/3/releasenotes/notes/release-summary-9c35dd1bd9b020f1.yaml _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From jose.perez.carranza at intel.com Tue Sep 18 17:32:07 2018 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Tue, 18 Sep 2018 17:32:07 +0000 Subject: [Starlingx-discuss] Simplex storage configuration Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A8CFD7C@fmsmsx101.amr.corp.intel.com> Hi folks I'm reviewing the wiki steps to install a simplex on virtual environment [1] and I noticed that 2 'local volume groups" are created, one for 'cinder-volumes' and another one for 'nova-local', why a 'cinder-volume' is needed on a simplex environment? Afaiu, a simplex system only needs a 'nova-local' volume group to be up and running, isn't it ? 1 - https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex Regards, José From Brent.Rowsell at windriver.com Tue Sep 18 17:33:21 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 18 Sep 2018 17:33:21 +0000 Subject: [Starlingx-discuss] Simplex storage configuration In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A8CFD7C@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A8CFD7C@fmsmsx101.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB2752DD@ALA-MBD.corp.ad.wrs.com> Cinder is a valid option on a simplex system Brent -----Original Message----- From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] Sent: Tuesday, September 18, 2018 1:32 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Simplex storage configuration Hi folks I'm reviewing the wiki steps to install a simplex on virtual environment [1] and I noticed that 2 'local volume groups" are created, one for 'cinder-volumes' and another one for 'nova-local', why a 'cinder-volume' is needed on a simplex environment? Afaiu, a simplex system only needs a 'nova-local' volume group to be up and running, isn't it ? 1 - https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex Regards, José _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Jason.McKenna at windriver.com Tue Sep 18 19:19:36 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Tue, 18 Sep 2018 19:19:36 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: <65CE126717DEA145BD6B2C2842DC52D66C0C7AB6@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A725@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7A53@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7AB6@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Saul, please see inline > -----Original Message----- > From: Rasa, Nimalini > Sent: September 18, 2018 12:59 PM > To: Saul Wold ; McKenna, Jason > ; Lin, Shuicheng > ; Xie, Cindy ; Martinez > Monroy, Elio ; Waheed, Numan > ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > We don't have any blockers now. > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Tuesday, September 18, 2018 12:08 PM > To: McKenna, Jason; Rasa, Nimalini; Lin, Shuicheng; Xie, Cindy; Martinez > Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > Jason, > > So if I am understand this correct the test_kernel_module_signatures failure > listed below is a not an issue due to the way WR built the kernel and > modules? > > Why was this build differently by WR than you would normally build an image > for testing? Wouldn't you always have this signature problem then? In this instance, after I had done a build, I was examining the commits and there was a head-scratcher in one of the build tools. I manually issued a rebuild of the kernel package to better observe the flow of the tool, which regenerated the signing keys in the kernel package. The tainted kernel notice would not normally appear. > > I am just trying to understand what differences in the way WR builds and the > way that is documented, just as we had the issue with the installer setup. That's touching on a bigger issue, I think. As you are aware there was no "documented" way to build the CentOS 7.5 branch. The email thread from last week discusses this in more detail, but involved the sending of manifest files through email, specifying some commits to cherry-pick from master into a build, using the revision of some gits specified in the manifest, but overriding the manifest and using the tip of the f/centos75 branch for other gits, etc. Because the build was hand managed, it opened the door to deviations like manually recompiling a package. So that was the immediate cause. I understand that for policy reasons binary artifacts cannot be exchanged, but we should come up with a general purpose better way to align our builds to reduce the chance of this kind of thing happening. > > Nimalini: Given this information, do we have any blockers for the 7.5 > upgrade? > > Thanks > Sau! > > > On 09/18/2018 07:27 AM, McKenna, Jason wrote: > > Hi folks, > > > > I do not think the kernel signature item is a real issue, but an artifact of how > we built the test image. > > > > The warning reported is basically saying that the driver was compiled > against a different build of the kernel than is currently running. This is typical > for intermediate builds where a kernel was compiled, the driver was > compiled, and the kernel compiled again (which was the case when I was > attempting to get the CentOS 7.5 test load built as the contents in the repos > were changing). I will clean the kernel driver packages the next time I > perform a build and we can verify that the error disappears. > > > > -J > > > > For anyone interested in technical details, the kernel regenerates a key pair > every time it is built, and compiles one half into the kernel and puts the other > half in the kernel-devel package. Packages (like kernel drivers) building > against the kernel-devel package will sign themselves with the key from the > package. Upon loading a driver, the kernel will validate that the signature on > the driver matches the half of the key which the kernel has access to. A > mismatched key indicates that the kernel running and kernel-devel package > which the driver was built against came from 2 different builds of the kernel, > and marks the kernel tainted as a warning. > > > >> -----Original Message----- > >> From: Rasa, Nimalini > >> Sent: September 18, 2018 9:50 AM > >> To: Lin, Shuicheng ; Xie, Cindy > >> ; McKenna, Jason > ; > >> Martinez Monroy, Elio ; Waheed, > Numan > >> ; starlingx-discuss at lists.starlingx.io > >> Cc: Khalil, Ghada > >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > >> > >> Hi Shuicheng, > >> It does have the correct version: > >> controller-0:~$ uname -a > >> Linux controller-0 3.10.0-862.11.6.el7.36.tis.x86_64 #1 SMP PREEMPT > >> Thu Sep > >> 13 10:48:38 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux > >> > >> Thanks, > >> Nimalini > >> > >> -----Original Message----- > >> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > >> Sent: Monday, September 17, 2018 9:16 PM > >> To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, > >> Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io > >> Cc: Khalil, Ghada > >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > >> > >> Hi Nimalini, > >> For the kernel signature issue, could you help confirm whether the > >> kernel version is 3.10.0-862.11.6 or not? > >> You could check it with "uname -a" or search it in the kern.log file. > >> Thanks. > >> > >> Best Regards > >> Shuicheng > >> > >> > >> -----Original Message----- > >> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > >> Sent: Tuesday, September 18, 2018 12:21 AM > >> To: Lin, Shuicheng ; Xie, Cindy > >> ; McKenna, Jason > ; > >> Martinez Monroy, Elio ; Waheed, > Numan > >> ; starlingx-discuss at lists.starlingx.io > >> Cc: Khalil, Ghada > >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > >> > >> Hi Shuicheng, > >> In this test case, basically trying to allocate double the amount of 2M > pages. > >> > >> For the kernel signature, I tried it on 3 different hardware labs and > >> got the > >> following: > >> controller-0:~$ cat /proc/sys/kernel/tainted > >> 12288 > >> controller-0:~$ grep --color=never -i "module verification failed" > >> /var/log/kern.log > >> 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: > >> module verification failed: signature and/or required key missing - > >> tainting kernel > >> 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: > >> module verification failed: signature and/or required key missing - > >> tainting kernel > >> > >> > >> Thanks, > >> Nimalini > >> > >> -----Original Message----- > >> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > >> Sent: Friday, September 14, 2018 9:13 PM > >> To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, > >> Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io > >> Cc: Khalil, Ghada > >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > >> > >> Hi Nimalini, > >> Could you share me the detail reproduce step for " > >> test_schedule_vm_mempage_config"? > >> > >> For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in > >> my virtual and bare metal environment, and both of them show 4096. > >> Then what should I do next? > >> " > >> controller-0:~$ cat /proc/sys/kernel/tainted > >> 4096 > >> controller-0:~$ grep --color=never -i "module verification failed" > >> /var/log/kern.log controller-0:~$ " > >> > >> Best Regards > >> Shuicheng > >> > >> -----Original Message----- > >> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > >> Sent: Saturday, September 15, 2018 3:02 AM > >> To: Xie, Cindy ; McKenna, Jason > >> ; Martinez Monroy, Elio > >> ; Waheed, Numan > >> ; starlingx-discuss at lists.starlingx.io > >> Cc: Khalil, Ghada ; Lin, Shuicheng > >> > >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > >> > >> Hi Cindy, > >> Adding more clarification of the test cases that are failed: > >> > >> FAIL 20180914 06:54:06 > >> test_schedule_vm_mempage_config[1048576] > >> Test case is trying to over allocate 2M pages, expected to reject > >> the cli, in this case it's accepted. > >> > >> FAIL 20180914 07:57:34 test_kernel_module_signatures > >> Test case is doing the following: > >> - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If > >> not, do following > >> steps: > >> - 'grep --color=never -i "module verification failed" > >> /var/log/kern.log' to find out failed modules > >> - 'modinfo | grep --color=never -E > >> "sig|filename" to display signing info for each module > >> > >> > >> Hope it clarifies bit more as to what the test cases it trying to do. > >> If you have any questions please let me know. > >> > >> Thanks, > >> Nimalini > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > From cesar.lara at intel.com Tue Sep 18 20:20:04 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Tue, 18 Sep 2018 20:20:04 +0000 Subject: [Starlingx-discuss] [build] stxb tool Message-ID: <0B566C62EC792145B40E29EFEBF1AB471050A191@fmsmsx104.amr.corp.intel.com> So, can we include the stxb tool as part of a "quick start guide" on the wiki? We have a couple groups interested in testing a deployment of StarlingX, final users, not necessarily contributors to the projects. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Tue Sep 18 20:22:05 2018 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 18 Sep 2018 13:22:05 -0700 Subject: [Starlingx-discuss] [build] stxb tool In-Reply-To: <0B566C62EC792145B40E29EFEBF1AB471050A191@fmsmsx104.amr.corp.intel.com> References: <0B566C62EC792145B40E29EFEBF1AB471050A191@fmsmsx104.amr.corp.intel.com> Message-ID: <02698dc7-c453-6817-699b-0f01ae57c1d7@linux.intel.com> On 09/18/2018 01:20 PM, Lara, Cesar wrote: > So, can we include the stxb tool as part of a “quick start guide” on the > wiki? We have a couple groups interested in testing a deployment of > StarlingX, final users, not necessarily contributors to the projects. > I am not sure it's ready for prime time yet, there are a number of review comments and I have not been able to use it successfully yet. I think it needs some changes still. Sorry Sau! > Regards > > *//* > > */Cesar Lara/* > > Software Engineering Manager > > OpenSource Technology Center > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From cesar.lara at intel.com Tue Sep 18 20:29:03 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Tue, 18 Sep 2018 20:29:03 +0000 Subject: [Starlingx-discuss] [build] stxb tool In-Reply-To: <02698dc7-c453-6817-699b-0f01ae57c1d7@linux.intel.com> References: <0B566C62EC792145B40E29EFEBF1AB471050A191@fmsmsx104.amr.corp.intel.com> <02698dc7-c453-6817-699b-0f01ae57c1d7@linux.intel.com> Message-ID: <0B566C62EC792145B40E29EFEBF1AB471050A1E3@fmsmsx104.amr.corp.intel.com> That's fair, we'll talk once we have those solved Regards Cesar Lara -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, September 18, 2018 3:22 PM To: Lara, Cesar ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build] stxb tool On 09/18/2018 01:20 PM, Lara, Cesar wrote: > So, can we include the stxb tool as part of a "quick start guide" on > the wiki? We have a couple groups interested in testing a deployment > of StarlingX, final users, not necessarily contributors to the projects. > I am not sure it's ready for prime time yet, there are a number of review comments and I have not been able to use it successfully yet. I think it needs some changes still. Sorry Sau! > Regards > > *//* > > */Cesar Lara/* > > Software Engineering Manager > > OpenSource Technology Center > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Ken.Young at windriver.com Tue Sep 18 21:20:53 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Tue, 18 Sep 2018 21:20:53 +0000 Subject: [Starlingx-discuss] [Security] Updated: How to Report Security Issues Message-ID: Team, The Security Subproject has updated the procedure for the community to raise security issues in StarlingX. The procedure is summarized here: https://wiki.openstack.org/wiki/StarlingX/Security#How_to_report_security_issues_to_Starling_X We have added a method to create reports in launchpad which makes tracking these issues much simpler. A big thank you to Fernando Hernandez Gonzalez for helping us work out this method. If there are any questions or concerns, please let me know. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ken.Young at windriver.com Tue Sep 18 21:33:10 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Tue, 18 Sep 2018 21:33:10 +0000 Subject: [Starlingx-discuss] CentOS 7.5 upgrade status update In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7655356001@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76553584C1@SHSMSX101.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B342A28@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B343082@SHSMSX104.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7604@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A067@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7877@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765535A725@SHSMSX101.ccr.corp.intel.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7A53@ALA-MBD.corp.ad.wrs.com> <65CE126717DEA145BD6B2C2842DC52D66C0C7AB6@ALA-MBD.corp.ad.wrs.com> Message-ID: <58DF1C34-BEC6-407E-8CE4-8677A89E9D35@windriver.com> See inline KWY+> On 2018-09-18, 3:19 PM, "McKenna, Jason" wrote: Hi Saul, please see inline > -----Original Message----- > From: Rasa, Nimalini > Sent: September 18, 2018 12:59 PM > To: Saul Wold ; McKenna, Jason > ; Lin, Shuicheng > ; Xie, Cindy ; Martinez > Monroy, Elio ; Waheed, Numan > ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > > We don't have any blockers now. > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Tuesday, September 18, 2018 12:08 PM > To: McKenna, Jason; Rasa, Nimalini; Lin, Shuicheng; Xie, Cindy; Martinez > Monroy, Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade status update > > > Jason, > > So if I am understand this correct the test_kernel_module_signatures failure > listed below is a not an issue due to the way WR built the kernel and > modules? > > Why was this build differently by WR than you would normally build an image > for testing? Wouldn't you always have this signature problem then? In this instance, after I had done a build, I was examining the commits and there was a head-scratcher in one of the build tools. I manually issued a rebuild of the kernel package to better observe the flow of the tool, which regenerated the signing keys in the kernel package. The tainted kernel notice would not normally appear. > > I am just trying to understand what differences in the way WR builds and the > way that is documented, just as we had the issue with the installer setup. That's touching on a bigger issue, I think. As you are aware there was no "documented" way to build the CentOS 7.5 branch. The email thread from last week discusses this in more detail, but involved the sending of manifest files through email, specifying some commits to cherry-pick from master into a build, using the revision of some gits specified in the manifest, but overriding the manifest and using the tip of the f/centos75 branch for other gits, etc. Because the build was hand managed, it opened the door to deviations like manually recompiling a package. So that was the immediate cause. I understand that for policy reasons binary artifacts cannot be exchanged, but we should come up with a general purpose better way to align our builds to reduce the chance of this kind of thing happening. KWY+> Let's get back to first principles. For the build to be reproducible, all the code needs to be in the branch. Otherwise, it is a designer build which is not acceptable for formal branch testing. > > Nimalini: Given this information, do we have any blockers for the 7.5 > upgrade? > > Thanks > Sau! > > > On 09/18/2018 07:27 AM, McKenna, Jason wrote: > > Hi folks, > > > > I do not think the kernel signature item is a real issue, but an artifact of how > we built the test image. > > > > The warning reported is basically saying that the driver was compiled > against a different build of the kernel than is currently running. This is typical > for intermediate builds where a kernel was compiled, the driver was > compiled, and the kernel compiled again (which was the case when I was > attempting to get the CentOS 7.5 test load built as the contents in the repos > were changing). I will clean the kernel driver packages the next time I > perform a build and we can verify that the error disappears. > > > > -J > > > > For anyone interested in technical details, the kernel regenerates a key pair > every time it is built, and compiles one half into the kernel and puts the other > half in the kernel-devel package. Packages (like kernel drivers) building > against the kernel-devel package will sign themselves with the key from the > package. Upon loading a driver, the kernel will validate that the signature on > the driver matches the half of the key which the kernel has access to. A > mismatched key indicates that the kernel running and kernel-devel package > which the driver was built against came from 2 different builds of the kernel, > and marks the kernel tainted as a warning. > > > >> -----Original Message----- > >> From: Rasa, Nimalini > >> Sent: September 18, 2018 9:50 AM > >> To: Lin, Shuicheng ; Xie, Cindy > >> ; McKenna, Jason > ; > >> Martinez Monroy, Elio ; Waheed, > Numan > >> ; starlingx-discuss at lists.starlingx.io > >> Cc: Khalil, Ghada > >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > >> > >> Hi Shuicheng, > >> It does have the correct version: > >> controller-0:~$ uname -a > >> Linux controller-0 3.10.0-862.11.6.el7.36.tis.x86_64 #1 SMP PREEMPT > >> Thu Sep > >> 13 10:48:38 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux > >> > >> Thanks, > >> Nimalini > >> > >> -----Original Message----- > >> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > >> Sent: Monday, September 17, 2018 9:16 PM > >> To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, > >> Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io > >> Cc: Khalil, Ghada > >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > >> > >> Hi Nimalini, > >> For the kernel signature issue, could you help confirm whether the > >> kernel version is 3.10.0-862.11.6 or not? > >> You could check it with "uname -a" or search it in the kern.log file. > >> Thanks. > >> > >> Best Regards > >> Shuicheng > >> > >> > >> -----Original Message----- > >> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > >> Sent: Tuesday, September 18, 2018 12:21 AM > >> To: Lin, Shuicheng ; Xie, Cindy > >> ; McKenna, Jason > ; > >> Martinez Monroy, Elio ; Waheed, > Numan > >> ; starlingx-discuss at lists.starlingx.io > >> Cc: Khalil, Ghada > >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > >> > >> Hi Shuicheng, > >> In this test case, basically trying to allocate double the amount of 2M > pages. > >> > >> For the kernel signature, I tried it on 3 different hardware labs and > >> got the > >> following: > >> controller-0:~$ cat /proc/sys/kernel/tainted > >> 12288 > >> controller-0:~$ grep --color=never -i "module verification failed" > >> /var/log/kern.log > >> 2018-09-14T19:55:12.495 localhost kernel: notice [ 8.016748] e1000e: > >> module verification failed: signature and/or required key missing - > >> tainting kernel > >> 2018-09-14T20:49:52.937 controller-0 kernel: notice [ 9.517476] e1000e: > >> module verification failed: signature and/or required key missing - > >> tainting kernel > >> > >> > >> Thanks, > >> Nimalini > >> > >> -----Original Message----- > >> From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > >> Sent: Friday, September 14, 2018 9:13 PM > >> To: Rasa, Nimalini; Xie, Cindy; McKenna, Jason; Martinez Monroy, > >> Elio; Waheed, Numan; starlingx-discuss at lists.starlingx.io > >> Cc: Khalil, Ghada > >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > >> > >> Hi Nimalini, > >> Could you share me the detail reproduce step for " > >> test_schedule_vm_mempage_config"? > >> > >> For the 2nd failure, I tried "'cat /proc/sys/kernel/tainted'" both in > >> my virtual and bare metal environment, and both of them show 4096. > >> Then what should I do next? > >> " > >> controller-0:~$ cat /proc/sys/kernel/tainted > >> 4096 > >> controller-0:~$ grep --color=never -i "module verification failed" > >> /var/log/kern.log controller-0:~$ " > >> > >> Best Regards > >> Shuicheng > >> > >> -----Original Message----- > >> From: Rasa, Nimalini [mailto:Nimalini.Rasa at windriver.com] > >> Sent: Saturday, September 15, 2018 3:02 AM > >> To: Xie, Cindy ; McKenna, Jason > >> ; Martinez Monroy, Elio > >> ; Waheed, Numan > >> ; starlingx-discuss at lists.starlingx.io > >> Cc: Khalil, Ghada ; Lin, Shuicheng > >> > >> Subject: RE: [Starlingx-discuss] CentOS 7.5 upgrade status update > >> > >> Hi Cindy, > >> Adding more clarification of the test cases that are failed: > >> > >> FAIL 20180914 06:54:06 > >> test_schedule_vm_mempage_config[1048576] > >> Test case is trying to over allocate 2M pages, expected to reject > >> the cli, in this case it's accepted. > >> > >> FAIL 20180914 07:57:34 test_kernel_module_signatures > >> Test case is doing the following: > >> - 'cat /proc/sys/kernel/tainted', ensure value is 4096. If > >> not, do following > >> steps: > >> - 'grep --color=never -i "module verification failed" > >> /var/log/kern.log' to find out failed modules > >> - 'modinfo | grep --color=never -E > >> "sig|filename" to display signing info for each module > >> > >> > >> Hope it clarifies bit more as to what the test cases it trying to do. > >> If you have any questions please let me know. > >> > >> Thanks, > >> Nimalini > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > From aragorn at intel.com Tue Sep 18 22:17:43 2018 From: aragorn at intel.com (aragorn at intel.com) Date: 18 Sep 2018 15:17:43 -0700 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#95] Missing packages - Results report Message-ID: [mirror-downloader][#95] Missing packages. Results report: - Missing: logs/K1_rpms_missing_centos.log adobe-source-code-pro-fonts-2.010.1.030-1.el7.noarch.rpm unifont-fonts-9.0.06-2.el7.noarch.rpm - Missing: logs/L1_rpms_missing_centos.log adobe-source-code-pro-fonts-2.010.1.030-1.el7.noarch.rpm unifont-fonts-9.0.06-2.el7.noarch.rpm - Missing: logs/L1_srpms_missing_centos.log lshell-0.9.16-5.el7.src.rpm From jimmy at openstack.org Tue Sep 18 22:40:27 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Tue, 18 Sep 2018 17:40:27 -0500 Subject: [Starlingx-discuss] [openstack-dev] Forum Topic Submission Period In-Reply-To: <5b5a669d-144c-bcc2-306c-c6410ef705ef@gmail.com> References: <5B9FD2BB.3060806@openstack.org> <5b5a669d-144c-bcc2-306c-c6410ef705ef@gmail.com> Message-ID: <5BA17EDB.5060701@openstack.org> Hey Matt, Matt Riedemann wrote: > > Just a process question. Good question. > I submitted a presentation for the normal marketing blitz part of the > summit which wasn't accepted (I'm still dealing with this emotionally, > btw...) If there's anything I can do... > but when I look at the CFP link for Forum topics, my thing shows up > there as "Received" so does that mean my non-Forum-at-all submission > is now automatically a candidate for the Forum because that would not > be my intended audience (only suits and big wigs please). Forum Submissions would be considered separate and non-Forum submissions will not be considered for the Forum. The submission process is based on the track you submit to and, in the case of the Forum, we separate this track out from the rest of the submission process. If you think there is still something funky, send me a note via speakersupport at openstack.org or jimmy at openstack.org and I'll work through it with you. Cheers, Jimmy From mriedemos at gmail.com Tue Sep 18 22:30:05 2018 From: mriedemos at gmail.com (Matt Riedemann) Date: Tue, 18 Sep 2018 17:30:05 -0500 Subject: [Starlingx-discuss] [openstack-dev] Forum Topic Submission Period In-Reply-To: <5B9FD2BB.3060806@openstack.org> References: <5B9FD2BB.3060806@openstack.org> Message-ID: <5b5a669d-144c-bcc2-306c-c6410ef705ef@gmail.com> On 9/17/2018 11:13 AM, Jimmy McArthur wrote: > Hello Everyone! > > The Forum Topic Submission session started September 12 and will run > through September 26th.  Now is the time to wrangle the topics you > gathered during your Brainstorming Phase and start pushing forum topics > through. Don't rely only on a PTL to make the agenda... step on up and > place the items you consider important front and center. > > As you may have noticed on the Forum Wiki > (https://wiki.openstack.org/wiki/Forum), we're reusing the normal CFP > tool this year. We did our best to remove Summit specific language, but > if you notice something, just know that you are submitting to the > Forum.  URL is here: > > https://www.openstack.org/summit/berlin-2018/call-for-presentations > > Looking forward to seeing everyone's submissions! > > If you have questions or concerns about the process, please don't > hesitate to reach out. > > Cheers, > Jimmy Just a process question. I submitted a presentation for the normal marketing blitz part of the summit which wasn't accepted (I'm still dealing with this emotionally, btw...) but when I look at the CFP link for Forum topics, my thing shows up there as "Received" so does that mean my non-Forum-at-all submission is now automatically a candidate for the Forum because that would not be my intended audience (only suits and big wigs please). -- Thanks, Matt From chenjie.xu at intel.com Wed Sep 19 02:23:54 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Wed, 19 Sep 2018 02:23:54 +0000 Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming In-Reply-To: <16E8ABC3-4BD3-4EC1-B32E-B8133A13A0CC@windriver.com> References: <16E8ABC3-4BD3-4EC1-B32E-B8133A13A0CC@windriver.com> Message-ID: Hi Matt, Thanks for your comment! The duplicate in the reference has been removed and the RFE has been checked again. Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, September 18, 2018 10:56 PM To: Xu, Chenjie Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming Hi Chenjie, I think the RFE looks good. I have no specific comments about the content, however, I think the references should be checked since there are duplicates. Everything else looks great. Regards, Matt From: "Xu, Chenjie" > Date: Monday, September 17, 2018 at 3:18 AM To: "Peters, Matt" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming Hi Matt, We analyze the patch 4ae5a58 related to l2pop. An RFE has been written(You can find it in the attachment). Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: RFE_EXTEND_L2POP_FDB_INFORMATION.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 18897 bytes Desc: RFE_EXTEND_L2POP_FDB_INFORMATION.docx URL: From yong.hu at intel.com Wed Sep 19 03:16:04 2018 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 19 Sep 2018 03:16:04 +0000 Subject: [Starlingx-discuss] Build installer instructions Message-ID: <948A3372-ED95-4929-A7EE-A9857A8C0D86@intel.com> Hi Erich, I would suggest to highlight that the following 2 files need to exist BEFORE running " $ update-pxe-network-installer" "$MY_REPO/$CENTOS_REPO/Binary/images/pxeboot/initrd.img" "$MY_REPO/$CENTOS_REPO/Binary/LiveOS/squashfs.img" - Yong On 18/09/2018, 11:51 PM, "Cordoba Malibran, Erich" wrote: Thanks for the feedback :) I updated the documentation in the wiki. I included the note that this procedure doesn't need to be done frequently.. Here is the wiki link: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Build_installer -Erich On Mon, 2018-09-17 at 16:40 +0000, Penney, Don wrote: > It's good to note that if you've already got installer images > generated (ie. on a shared system, in /import/mirror/CentOS/tis- > installer), you don't need to run "build-pkgs --installer". So > presumably, this would not be part of a general designer workflow. > > Historically, we upversioned these images whenever they were updated, > but this introduces some challenges under Starling-X. It may make > sense to drop the version number from the images as referenced in the > pxe-network-installer package build, essentially treating it as a > .latest version. Individuals or groups could then manage their own > installer version history as they see fit, ie. build images with 0.1, > 0.2, 0.3, with symlinks to the latest perhaps. If these images aren't > being hosted somewhere, if individuals/groups are generating their > own, then the versioning shouldn't be in the build files. > > > > -----Original Message----- > From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.co > m] > Sent: Monday, September 17, 2018 12:12 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Build installer instructions > > Hi, > > I would like to share/discuss the instructions to generate the > installer before are publish into the wiki. I couldn't find a > previous > version of these instructions, probably I confused with this warning > from the download_mirror.sh[0]. The update-pxe-network-installer > script > follows the steps detailed here[1]. > > Build installer > =============== > > To get your StarlingX ISO ready to use, you will need to create the > init files that will be used to boot the ISO as well to boot > additional > controllers and compute nodes. > > Once you had run `build-iso`, run: > > ``` > build-pkgs --installer > ``` > > This will build `rpm` and `anaconda` packages. Then run: > > ``` > update-pxe-network-installer > ``` > > The update-pxe-network-installer` covers the steps detailed in > `$MY_REPO/stx/stx-metal/installer/initrd/README`. This script will > create three files on `/localdisk/loadbuild///pxe- > network-installer/output` > > ``` > new-initrd.img > new-squashfs.img > new-vmlinuz > ``` > > Then, rename them to: > > ``` > initrd.img-stx-0.2 > squashfs.img-stx-0.2 > vmlinuz-stx-0.2 > ``` > > There are two ways to use these files: > > 1. Store the files in the '/import/mirror/CentOS/tis-installer/` > folder for future use. > 2. Store it in an arbitrary location and modify the > `$MY_REPO/stx/stx- > metal/installer/pxe-network-installer/centos/build_srpm.data` file to > point to these files. > > Now, the `pxe-network-installer` package needs to be recreated and > the > ISO regenerated. > > ``` > build-pkgs --clean pxe-network-installer > build-pkgs pxe-network-installer > build-iso > ``` > > Now your ISO should be able to boot. > > Updating these files is not a common tasks, it is recommended only do > it if the kernel version is upgraded or new kernel modules are added. > > > ===================== > End of documentation > > > > [0] http://git.starlingx.io/cgit/stx-tools/tree/centos-mirror-tools/d > ownload_mirror.sh#n264 > [1] http://git.starlingx.io/cgit/stx-metal/tree/installer/initrd/READ > ME > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From aragorn at intel.com Wed Sep 19 09:28:31 2018 From: aragorn at intel.com (aragorn at intel.com) Date: 19 Sep 2018 02:28:31 -0700 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#96] Missing packages - Results report Message-ID: [mirror-downloader][#96] Missing packages. Results report: - Missing: logs/K1_rpms_missing_centos.log adobe-source-code-pro-fonts-2.010.1.030-1.el7.noarch.rpm unifont-fonts-9.0.06-2.el7.noarch.rpm - Missing: logs/L1_rpms_missing_centos.log adobe-source-code-pro-fonts-2.010.1.030-1.el7.noarch.rpm unifont-fonts-9.0.06-2.el7.noarch.rpm - Missing: logs/L1_srpms_missing_centos.log lshell-0.9.16-5.el7.src.rpm From sylvain.bauza at gmail.com Wed Sep 19 07:56:15 2018 From: sylvain.bauza at gmail.com (Sylvain Bauza) Date: Wed, 19 Sep 2018 09:56:15 +0200 Subject: [Starlingx-discuss] [openstack-dev] Forum Topic Submission Period In-Reply-To: <5BA17EDB.5060701@openstack.org> References: <5B9FD2BB.3060806@openstack.org> <5b5a669d-144c-bcc2-306c-c6410ef705ef@gmail.com> <5BA17EDB.5060701@openstack.org> Message-ID: Le mer. 19 sept. 2018 à 00:41, Jimmy McArthur a écrit : > Hey Matt, > > > Matt Riedemann wrote: > > > > Just a process question. > > Good question. > > I submitted a presentation for the normal marketing blitz part of the > > summit which wasn't accepted (I'm still dealing with this emotionally, > > btw...) > Same as I do :-) Unrelated point, for the first time in all the Summits I know, I wasn't able to know the track chairs for a specific track. Ideally, I'd love to reach them in order to know what they disliked in my proposal. > If there's anything I can do... > > but when I look at the CFP link for Forum topics, my thing shows up > > there as "Received" so does that mean my non-Forum-at-all submission > > is now automatically a candidate for the Forum because that would not > > be my intended audience (only suits and big wigs please). > Forum Submissions would be considered separate and non-Forum submissions > will not be considered for the Forum. The submission process is based on > the track you submit to and, in the case of the Forum, we separate this > track out from the rest of the submission process. > > If you think there is still something funky, send me a note via > speakersupport at openstack.org or jimmy at openstack.org and I'll work > through it with you. > > I have another question, do you know why we can't propose a Forum session with multiple speakers ? Is this a bug or an expected behaviour ? In general, there is only one moderator for a Forum session, but in the past, I clearly remember we had some sessions that were having multiple moderators (for various reasons). -Sylvain Cheers, > Jimmy > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Wed Sep 19 12:08:48 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Wed, 19 Sep 2018 12:08:48 +0000 Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming In-Reply-To: References: <16E8ABC3-4BD3-4EC1-B32E-B8133A13A0CC@windriver.com> Message-ID: Hi Chenjie, Looks good. Regards, Matt From: "Xu, Chenjie" Date: Tuesday, September 18, 2018 at 10:24 PM To: "Peters, Matt" Cc: "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming Hi Matt, Thanks for your comment! The duplicate in the reference has been removed and the RFE has been checked again. Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, September 18, 2018 10:56 PM To: Xu, Chenjie Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming Hi Chenjie, I think the RFE looks good. I have no specific comments about the content, however, I think the references should be checked since there are duplicates. Everything else looks great. Regards, Matt From: "Xu, Chenjie" > Date: Monday, September 17, 2018 at 3:18 AM To: "Peters, Matt" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming Hi Matt, We analyze the patch 4ae5a58 related to l2pop. An RFE has been written(You can find it in the attachment). Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Wed Sep 19 13:13:24 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 19 Sep 2018 08:13:24 -0500 Subject: [Starlingx-discuss] [openstack-dev] Forum Topic Submission Period In-Reply-To: References: <5B9FD2BB.3060806@openstack.org> <5b5a669d-144c-bcc2-306c-c6410ef705ef@gmail.com> <5BA17EDB.5060701@openstack.org> Message-ID: <5BA24B74.8010301@openstack.org> Sylvain Bauza wrote: > > > Le mer. 19 sept. 2018 à 00:41, Jimmy McArthur > a écrit : SNIP > > > Same as I do :-) Unrelated point, for the first time in all the > Summits I know, I wasn't able to know the track chairs for a specific > track. Ideally, I'd love to reach them in order to know what they > disliked in my proposal. They were listed on an Etherpad that was listed under Presentation Selection Process in the CFP navigation. That has since been overwritten w/ Forum Selection Process, so let me try to dig that up. We publish the Track Chairs every year. > SNIP > > I have another question, do you know why we can't propose a Forum > session with multiple speakers ? Is this a bug or an expected > behaviour ? In general, there is only one moderator for a Forum > session, but in the past, I clearly remember we had some sessions that > were having multiple moderators (for various reasons). Correct. Forum sessions aren't meant to have speakers like a normal presentation. They are all set up parliamentary style w/ one or more moderators. However, the moderator can manage the room any way they'd like. If you want to promote the people that will be in the room, this can be added to the abstract. > > -Sylvain > > > Cheers, > Jimmy > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Wed Sep 19 13:15:09 2018 From: Matt.Peters at windriver.com (Peters, Matt) Date: Wed, 19 Sep 2018 13:15:09 +0000 Subject: [Starlingx-discuss] Analysis report about Network Trunk feature for StartlingX upstreaming In-Reply-To: References: <76647BD697F40748B1FA4F56DA02AA0B4D4EB222@SHSMSX104.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB577F1B@fmsmsx115.amr.corp.intel.com> <76647BD697F40748B1FA4F56DA02AA0B4D4EB495@SHSMSX104.ccr.corp.intel.com> <304C67CB-BAE4-4E42-A613-1C848535F166@windriver.com> <76647BD697F40748B1FA4F56DA02AA0B4D4EDBFE@SHSMSX104.ccr.corp.intel.com> Message-ID: <45BCE356-0DAC-4C66-9244-4EED06478182@windriver.com> Hello Huifeng, I wanted to follow-up on item #1 below (ba9d9f60a7a2665194cacb92a05e0acd2dc3de41: Add rpc notification for trunk updates). The concern is that there is a difference in behavior between the port and trunks, that may impact the user experience and not just impact the agent/server behavior. The problem is that it is not symmetric with setting admin_setup_up on a Port. If you set that attribute to False on a Port then that port is disabled in the vswitch; packets are no longer sent/received. Based on that expectation, then it would make sense that setting admin_state_up=False on a trunk would disable that trunk on the vswitch (i.e., stop processing VLAN packets arriving from that VM instance), but that is not what happens; it continues to be operational. It is our opinion that this is an incorrect behavior that is worth correcting. Based on the above behavioral difference, I think it makes sense to pursue this with the neutron team since they may want to align on this behavior as well. If the neutron team rejects this change, then we can align on the current upstream behavior. Regards, Matt From: "Peters, Matt" Date: Friday, September 7, 2018 at 11:00 AM To: "Le, Huifeng" , "Jolliffe, Ian" , "Jones, Bruce E" , Brent Rowsell Cc: "Zhao, Forrest" , "Troyer, Dean" , "starlingx-discuss at lists.starlingx.io" Subject: RE: Analysis report about Network Trunk feature for StartlingX upstreaming See inline for specific responses to the review information. Responses marked with [MP>] From: Le, Huifeng [mailto:huifeng.le at intel.com] Sent: Sunday, August 19, 2018 10:32 PM To: Jolliffe, Ian; Jones, Bruce E; Rowsell, Brent; Peters, Matt Cc: Zhao, Forrest; Troyer, Dean; starlingx-discuss at lists.starlingx.io Subject: RE: Analysis report about Network Trunk feature for StartlingX upstreaming Ian, Thanks very much for the comments. some comments below for you reference, and please help to review, thanks much! Best Regards, Le, Huifeng From: Jolliffe, Ian [mailto:Ian.Jolliffe at windriver.com] Sent: Saturday, August 18, 2018 4:16 AM To: Le, Huifeng ; Jones, Bruce E ; Rowsell, Brent ; Peters, Matt Cc: Zhao, Forrest ; Troyer, Dean ; starlingx-discuss at lists.starlingx.io Subject: Re: Analysis report about Network Trunk feature for StartlingX upstreaming Hi Huifeng; Thanks for the updates/analysis, comments below. Ian Ian/Brent/Matt, We did analysis about the Network trunk related patches for StartingX upstream, below are the suggestions for upstreaming, could you please help to review and comment? Thanks much! 1. ba9d9f60a7a2665194cacb92a05e0acd2dc3de41: Add rpc notification for trunk updates Function: sent notification to the agent when a trunk is updated Analysis: (1)Trunk’s AFTER_UPDATE event is generated for API call: PUT /v2.0/trunks/{trunk-id} The update request is only for changing fields like name, description or admin_state_up. Setting the admin_state_up to False locks the trunk in that it prevents operations such as adding/removing subports. In Neutron upstream, admin_state_up is used in server side, e.g. add_subports, remove subports, delete_trunk and not used in agent side (2)OVS trunk agent driver uses OVSDB event to handle trunk event, no need to manually trigger trunk update event (3)Linux trunk agent driver will handle trunk update event triggered by server, while it will need apply the patch only in case admin_state_up update need to be handled Suggestion: Not a bug for Neutron upstream, suggest not to upstream If this is not upstreamed, are the dependencies or changes required in the StarlingX code base? What are the implications of not upstreaming? [hle2] for STX, trunk_updated event will force the trunk’s parent-port to refresh (e.g. handle_trunks->mark_port_for_refresh(trunk['port_id']) etc.) to get the new “admin_state_up” value from server and this value will be used in handle_updated_port() to determine whether it is allowed to update port/device status in server side. “admin_state_up” is mainly used to control operation at neutron server side like add_subports, remove subports, delete_trunk etc. and all these 3 operations will force port to refresh (handle_trunks/handle_subports->mark_port_for_refresh), so suppose, the general flow will not be impacted whether to handle trunk_updated event or not. But in some wired cases, add “admin_state_up” check in agent side may cause issues (please help to review whether it is make sense), e.g for below calling flow (suppose trunk’s ‘admin_state_up’ is ‘up’): (1) add_subports (2) set “admin_state_up” to ‘down’, step(1) may fail to set device’s state at agent side in case aws agent’s handle_updated_port() (in daemon loop) executed after step (2) So to my understanding: (1) if using OVS agent in STX, no impact for not upstream (2) if using AVS agent + STX, suggest removing “admin_state_up” check in AVS agent (in function handle_updated_port () of avs/agent.py) like below. if trunk_details and trunk_details['admin_state_up']: … [MP>] Thanks for the detailed analysis. The suggested change will need to be tested to see if it full resolves the original issue. However, since the driver could be used by other agents (beyond just the AVS agent), I think it would not hurt to have the additional notification sent to complete the driver definition for the set of RPC notifications. 2. 6955351c5eca6e37061fb0140d11ea53693fe0e1: Add support to delete bound network Function: enable delete trunk if it is can_be_trunked (not bounded or driver’s can_trunk_bound_port=true) Analysis: Applied for LinuxBridge Driver and AVS bridge Driver (can_trunk_bound_port=True), no impact for OVSTrunkDriver (can_trunk_bound_port=False). workaround also available for linux bridge (e.g. unbind the port first then delete the trunk) Suggestion: it is a low priority bug for Neutron upstream (only applied for linux bridge and workround available), suggest not to upstream I think you need to propose a fix. Or this will need to be carried long term. [hle2] yes, let’s try to propose a fix for upstream. [MP>] Agree. 3. 43a684946e781a25d21a4f50b8dc67d61be42809: Enable trunk service by default Function: add “trunk” in DEFAULT_SERVICE_PLUGINS Analysis: It is a deploy configuration for downstream product Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. 4. c54d804792f10b7f505de6794274c4df4768f6f0: Include trunk presence in port details Function: add trunk_port (bool) flag in port_details to identify whether this port is a parent port for a trunk Analysis: It is a performance improvement for AVS agent by reducing RPC call from agent to server. OVS agent has different implementation with no improvement by introducing this field Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. 5. 3eed837ebd236e6b1959ea88d9ab5322c9eef6b9: Ignore trunk subports on same vlan as vlan-subnet ports Function: Ignore trunk subports on same vlan as vlan-subnet ports Analysis: It is a bug fix for AVS agent Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Sep 19 13:56:27 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 19 Sep 2018 13:56:27 +0000 Subject: [Starlingx-discuss] Notes for weekly StarlingX non-OpenStack Distro meeting - 9/19 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B34AA3E@SHSMSX104.ccr.corp.intel.com> Agenda & Notes for 9/19 meeting: 1. CentOS 7.5 upgrade testing status (Shuicheng, Elio, Numan/Nimalini) - Kernel upgraded: 862.11.6. Fixed the issue during testing cycle. GDC report is 25/25 pass; WindRiver test results no blocking issue so far. - Sanity on different type of HW (extended sanity); NOVA suites on different HW/configs. Simplex/storage/regular multi-node * different HW drivers mixes on CentOS. - Only problem is kernel signiture which is build issue (root caused and not caused by 7.5 upgrade). - will run automation as regular routine testing after merge. about 2 wks cycle, start on 9/22. So we'd better to merge it before 9/22 to catch up the WR test cycle.  2. Decision required: feature branch merge back to master (Ghada, Brent/Dean) - Bruce: let's discussion in the community call - but we are in a reasonable state.  - Jason: merge earlier and test more on mainline. - Saul: let's discussion this in community call.  3. Libvirt/qemu upgrade status (Ghada/Jim) - qemu is not going well, still have functionality issue on newer version. Will not make it for Sep code freeze. Ghada made the decision to push over to 2019.03. - libvirt and python-libvirt will be in by next Monday/Tuesday.  4. 2018.10 content review (Ghada) - VM-migration: will be merged by end of this week; - symbol issue: fixed by revert the binutil back to 2.25 due to upstream known issue. - SB 2002565: not a bug, status change.  5. Ceph upgrade status (Vivian/Dehao) - Dehao: successfully build w/ Ceph 13.2.0; 27 new packages added. by pass the dependencies of Python3. move to Cephfs2 and deprecated Cephfs1. New Ceph13.2.0 repo created to replace stx-Ceph 10.2.6.  - 4 PR generated: stx-upstream; stx-tools; stx-root; stx-integ.  - Didn't cherryPick the patches from stx-Ceph 10.2.6 - Ceph patches was not included in the master xls. Brent can help to get a list of patches for Ceph.  - upgrade: migrate the patches over from Ceph 10 to 13. After this is done, then we can ask validation team to do testing against features.  6. non-OpenStack patch analysis status (Saul/Zhipeng) - Brent & Ian: reviewed OS-distro related patches. Recent patch regarding memcached as the example to move RPM init to services in post-installation. We are making some progress.  7. Opens (Brent, Saul, Ghada) - None From Ken.Young at windriver.com Wed Sep 19 15:32:10 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Wed, 19 Sep 2018 15:32:10 +0000 Subject: [Starlingx-discuss] [Build] Follow-up on Installer Action Message-ID: Saul / Cesar, I wanted to follow up on my action from the StarlingX Build Meeting on Monday. A full recipe for building the installer is already available in the README discussed on the call: https://github.com/openstack/stx-metal/blob/master/installer/initrd/README This action is closed. Now that we have this recipe, what are the next steps? I am suggesting that: 1. Once the CentOS 7.5 merges, we create an updated installer. This needs to follow this recipe precisely. 2. We need a Wiki highlighting this to the broader community. The capability is there but it is really hidden at the moment. This should also contain the recommendation provided by Don Penney on the mailing list on how frequently this step needs to be completed (i.e., rarely). I believe this covers off the immediate issue. I am certainly open to other ideas and suggestions. Cesar, Please add this topic for the build meeting on Monday. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Sep 19 18:35:45 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 19 Sep 2018 18:35:45 +0000 Subject: [Starlingx-discuss] RFC: Updated governance doc on the wiki In-Reply-To: References: <9A85D2917C58154C960D95352B22818BAB58FEA1@fmsmsx115.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB59155F@fmsmsx115.amr.corp.intel.com> Dean, thank you for this feedback. I have made all of the changes you suggested to the Governance wiki page. Additional feedback on https://wiki.openstack.org/wiki/Starlingx/Initial_Governance is welcome! brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Monday, September 17, 2018 4:19 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] RFC: Updated governance doc on the wiki On Mon, Sep 17, 2018 at 3:54 PM, Jones, Bruce E wrote: > I have updated our draft Governance document based on feedback from the PTG. > Please review and send me any feedback you have. I made a minor formatting change to reduce the emphasis on company affiliation in the initial TSC membership and decided I wanted to do more for clarity without changing the intent. I will propose the changes here to include some rationale initially before further editing the wiki: > We are actively recruiting for additional Technical Steering Committee > members Strike this, it does not feel appropriate for a governance doucment > In September 2019, 3 of the 7 seats will be up for election by the project's Contributors. Anyone who is a Contributor to the project will be eligible to run, and anyone who is a Contributor is eligible to vote. s/will be/is/.. Should use 'is' in both places in that sentence. > In that election the TSC positions held by one each of the members from Wind River and Intel will be opened for election, to be determined randomly. In April 2020, the remaining 4 seats will be up for election. In that election, the other initial TSC members from Wind River and Intel will be opened for election. Strike the last sentence above, it is redundant, suggest replace with: At that time all initially appointed TSC terms will have been replaced by elected terms. > TSC elections will continue on this staggered cycle (3 seats and 4 seats) every six months in order to allow new leaders to rise up and ensure some consistency across the terms. TSC members will serve at least one year terms after the initial bootstrapping phase. There are no term limits, but in order to encourage diversity, no more than 2 of the 7 seats can be filled by any one organization. Suggest alternative: TSC Elections will continue on a staggered six month cycle (3 seats and 4 seats) in order to ensure consistency across terms while allowing new leaders to begin to serve. There are no limits on the number of terms an individual may serve, but no single organization may be represented by more than two seats at any given time. For clarity, here is the rewritten paragraph: In September 2019, 3 of the 7 seats will be up for election by the project's Contributors. Anyone who is a Contributor to the project will be eligible to run, and anyone who is a Contributor is eligible to vote. In that election the TSC positions held by one each of the members from Wind River and Intel will be opened for election, to be determined randomly. In April 2020, the remaining 4 seats will be up for election. At that time all initially appointed TSC terms will have been replaced by elected terms. TSC Elections will continue on a staggered six month cycle (3 seats and 4 seats) in order to ensure consistency across terms while allowing new leaders to begin to serve. There are no limits on the number of terms an individual may serve, but no single organization may be represented by more than two seats at any given time. > The Technical Steering Committee will meet regularly in an open forum with times and locations published in community channels. The Technical Steering Committee can elect a Chair at its discretion. Meetings with be hosted and facilitated by the OpenStack Foundation. The meeting facillitation and hosting doesn't seem like something to be codified in governance? > Voting within the TSC requires a quorum of 5 members present. In the initial phase when the TSC does not have 5 members, a quorum will be 4 members. TSC members should seek consensus on most technical issues but if needed they can be resolved through a simple majority vote. Voting to create a new or archive an inactive StarlingX sub-project or to change the project's formal Governance document requires a 2/3rds super-majority. How about this: A quorum for the TSC requires more than half of the members. (When the TSC membership is an even number, this means half + 1.) The TSC should seek consensus on issues and decisions however a simple majority vote shall be sufficient for most resolutions. Certain resolutions, specifically changing the project formal governance (including this document) and changes to project structure (adding or removing a sub-project) require a two-thirds majority vote. ((If there are more super-majority things we need to list them here)) dt -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Wed Sep 19 18:44:06 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 19 Sep 2018 18:44:06 +0000 Subject: [Starlingx-discuss] Weekly project team call notes Message-ID: <9A85D2917C58154C960D95352B22818BAB591597@fmsmsx115.amr.corp.intel.com> Here are the notes from today's call, which can also be found on https://etherpad.openstack.org/p/stx-status brucej Agenda and Notes for the Sep 19th call * PTG Update o Review comments on the draft Feature Dev process (Bruce) ? Ian to take the first shot at a Spec template (in the spec repo) o Review comments on the Governance draft (Bruce) ? Bruce (and team) to review Dean's comments o New Multi-OS sub-project (Bruce) ? Bruce to start up wiki page, arrange call with Ildiko. Brent, Saul, Cesar, Yong, Scott, Abraham, Victor all possible team members. o Containerized Services update (Brent) ? Brent to update the team at next week's call - needs 60 minutes o Project de-coupling update (Brent) ? Next step is to split/decouple sys inventory, break down into inventory and config mangement. Spec to come shortly. o Investing in StoryBoard development (Bruce) ? Looking for volunteers to help with the SB Web UI and add content. o Edge WG Update / slides (Greg) o Update from discussion with the OpenStack User Committee (Ian) ? How do we want to work with the broader OpenStack community? Beginning of the dialog. * Update from the OpenStack BoD meeting - Dean o No big surprises. Proposal made for how to manage strategic initiaitives and pilot projects. Focus areas and pilot projects are not strongly connected, no focus area governance model (yet). We are a pilot progress and within 18 months will be reviewed by the BoD who will decide if our project is viable/active/open. o Proposal made to add a new "Silver" Foundation membership level. * Release status (Ghada) o We reviewed status of features and bugs. Bug count is 15 for the release. Teams have queries for their bugs on each wiki page. Features are mostly on track, but we're going to delay the qemu upgrade to 3.0. o We need to help Ghada with bug triage. Ada can help. Other volunteers for the virtual team welcome! Brent to help. Another volunteer whose name I missed. * Forum session proposals (ildikov/gwaines) o https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming * CentOS 7.5 update - ready to merge? Yes - approved to merge. Dean to rebase one last time from master. * stxb tool - feedback, concerns, status... (Cesar) o To be discussed in more depth at the Cores call tomorrow. * Status from other teams / issues * Help needed? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Wed Sep 19 19:45:10 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 19 Sep 2018 14:45:10 -0500 Subject: [Starlingx-discuss] Merge f/centos75 feature branch into master Message-ID: I have proposed the 4 reviews to merge the f/centos75 feature branch into master[0]. When approved we should consider the feature branch closed. Please let me know if you see anything odd about this as it is the first re-merge of a feature branch for us... Thanks dt [0] https://review.openstack.org/#/q/topic:merge-f/centos75+(status:open+OR+status:merged) -- Dean Troyer dtroyer at gmail.com From chenjie.xu at intel.com Thu Sep 20 01:44:45 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Thu, 20 Sep 2018 01:44:45 +0000 Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming In-Reply-To: References: <16E8ABC3-4BD3-4EC1-B32E-B8133A13A0CC@windriver.com> Message-ID: Hi Matt, Thank you for your comment! Best Regard, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, September 19, 2018 8:09 PM To: Xu, Chenjie Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming Hi Chenjie, Looks good. Regards, Matt From: "Xu, Chenjie" > Date: Tuesday, September 18, 2018 at 10:24 PM To: "Peters, Matt" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: RE: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming Hi Matt, Thanks for your comment! The duplicate in the reference has been removed and the RFE has been checked again. Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Tuesday, September 18, 2018 10:56 PM To: Xu, Chenjie > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming Hi Chenjie, I think the RFE looks good. I have no specific comments about the content, however, I think the references should be checked since there are duplicates. Everything else looks great. Regards, Matt From: "Xu, Chenjie" > Date: Monday, September 17, 2018 at 3:18 AM To: "Peters, Matt" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Analysis of patch 4ae5a58 for StartlingX upstreaming Hi Matt, We analyze the patch 4ae5a58 related to l2pop. An RFE has been written(You can find it in the attachment). Could you please help to review and comment? Thanks very much! Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiaoyan.li at intel.com Thu Sep 20 02:17:29 2018 From: xiaoyan.li at intel.com (Li, Xiaoyan) Date: Thu, 20 Sep 2018 02:17:29 +0000 Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB25D46B@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB25D46B@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi, Brent The following are mechanism of Cinder volume cache. Creation of cached volume: It creates a cached volume in the backend storage when creating from an image. 1. Create_from_image: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L890 2. Return image cache entry: If not existed, it creates a new entry. https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L746 3. Create a new image-volume and cache entry for it: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L872 Use a cached volume when creating a volume: https://github.com/openstack/cinder/blob/stable/pike/cinder/volume/flows/manager/create_volume.py#L723-L735 Delete the cache volume: When capacity and number of cache entries exceed specified limit, it deletes cache entries (cached volumes). https://github.com/openstack/cinder/blob/stable/pike/cinder/image/cache.py#L164 Best wishes Lisa From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, September 6, 2018 10:02 AM To: Li, Xiaoyan ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching We would need to review this feature to ensure it provides equivalent functionality first. If it does, great, we can look at reverting and enabling this cinder functionality. Brent From: Li, Xiaoyan [mailto:xiaoyan.li at intel.com] Sent: Wednesday, September 5, 2018 9:59 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [StarlingX] Use Cinder generic image cache to replace raw caching Hi all, This email is about Raw caching function in StarlingX. This feature is to cache an image in backend storage like Ceph when we first create a volume in this backend storage. In fact, Cinder upstream has already had a similar function in Pike release. https://specs.openstack.org/openstack/cinder-specs/specs/liberty/image-volume-cache.html So I want to revert Raw caching function in StarlingX, and use Cinder generic image cache instead. The problem is that we need to update Cinder config in StarlingX. Any comments? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From dehao.shang at intel.com Thu Sep 20 03:54:39 2018 From: dehao.shang at intel.com (Shang, Dehao) Date: Thu, 20 Sep 2018 03:54:39 +0000 Subject: [Starlingx-discuss] ceph upgrading PR and summary. Message-ID: <71AECFE5078153419EB7B8DBE0644B26386413AC@shsmsx102.ccr.corp.intel.com> Hi: This is just draft PR for ceph upgrading. Please feel free to give your advices. PR 1: change cephfs1 into cephfs2 https://github.com/shangdehao1/stx-upstream/commit/d612093fab072afb4fb9d054deca924778084ad6 PR 2 : ceph13.2.0 need to download new packages : PR: https://github.com/shangdehao1/stx-tools/commit/09abdefc37ba70f452c5998390ce167c5cb2d50d PR 3: don't ignore files at compress process. ( TODO : better method to replace it) PR: https://github.com/shangdehao1/stx-root/commit/1bedca4609fbca06746f7bbfda27e7023949af37 PR4: ceph 13.2.0 commit id. https://github.com/shangdehao1/stx-integ/commit/1ab1d71591faa7ddf83b2cd7d53cef5def9dc1c0 How to create ceph13.2.0 repo 1: wget http://cbs.centos.org/kojifiles/packages/ceph/13.2.0/0.el7/src/ceph-13.2.0-0.el7.src.rpm 2: rpm2cpio ceph-13.2.0-0.el7.src.rpm | cpio -div 3: tar -xvjf ceph-13.2.0.tar.bz2 4:modify ceph.spce 1: disable python3 2: apply the patch to solve the conflict between openstack-keystone and ceph 13.2.0 3: modify ceph version: namely 0.el7%{?_tis_dist}.%{tis_patch_ver} 4: modify compress format into tar.gz 5: disbale some useless package. Ceph debug info package Ceph dashboard TODO: refer to stx-ceph, to disable more package. Next step: 1: for PR 3, at compress process, still ignore this useless files, but for ceph, need to include these files. 2: in order to speed up building, need to disable useless packages. 2: integrate stx-ceph patch into ceph13.2.0 3: testing at runtime. Thanks Dehao -------------- next part -------------- An HTML attachment was scrubbed... URL: From huifeng.le at intel.com Thu Sep 20 06:33:43 2018 From: huifeng.le at intel.com (Le, Huifeng) Date: Thu, 20 Sep 2018 06:33:43 +0000 Subject: [Starlingx-discuss] Analysis report about Network Trunk feature for StartlingX upstreaming In-Reply-To: <45BCE356-0DAC-4C66-9244-4EED06478182@windriver.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D4EB222@SHSMSX104.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB577F1B@fmsmsx115.amr.corp.intel.com> <76647BD697F40748B1FA4F56DA02AA0B4D4EB495@SHSMSX104.ccr.corp.intel.com> <304C67CB-BAE4-4E42-A613-1C848535F166@windriver.com> <76647BD697F40748B1FA4F56DA02AA0B4D4EDBFE@SHSMSX104.ccr.corp.intel.com> <45BCE356-0DAC-4C66-9244-4EED06478182@windriver.com> Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D4F835C@SHSMSX104.ccr.corp.intel.com> Matt, Thanks much for sharing the insight! and Aligned internally, we will raise the question/problem to community for discussion then flowing up, thanks much! Best Regards, Le, Huifeng From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, September 19, 2018 9:15 PM To: Le, Huifeng Cc: Zhao, Forrest ; starlingx-discuss at lists.starlingx.io Subject: Re: Analysis report about Network Trunk feature for StartlingX upstreaming Hello Huifeng, I wanted to follow-up on item #1 below (ba9d9f60a7a2665194cacb92a05e0acd2dc3de41: Add rpc notification for trunk updates). The concern is that there is a difference in behavior between the port and trunks, that may impact the user experience and not just impact the agent/server behavior. The problem is that it is not symmetric with setting admin_setup_up on a Port. If you set that attribute to False on a Port then that port is disabled in the vswitch; packets are no longer sent/received. Based on that expectation, then it would make sense that setting admin_state_up=False on a trunk would disable that trunk on the vswitch (i.e., stop processing VLAN packets arriving from that VM instance), but that is not what happens; it continues to be operational. It is our opinion that this is an incorrect behavior that is worth correcting. Based on the above behavioral difference, I think it makes sense to pursue this with the neutron team since they may want to align on this behavior as well. If the neutron team rejects this change, then we can align on the current upstream behavior. Regards, Matt From: "Peters, Matt" > Date: Friday, September 7, 2018 at 11:00 AM To: "Le, Huifeng" >, "Jolliffe, Ian" >, "Jones, Bruce E" >, Brent Rowsell > Cc: "Zhao, Forrest" >, "Troyer, Dean" >, "starlingx-discuss at lists.starlingx.io" > Subject: RE: Analysis report about Network Trunk feature for StartlingX upstreaming See inline for specific responses to the review information. Responses marked with [MP>] From: Le, Huifeng [mailto:huifeng.le at intel.com] Sent: Sunday, August 19, 2018 10:32 PM To: Jolliffe, Ian; Jones, Bruce E; Rowsell, Brent; Peters, Matt Cc: Zhao, Forrest; Troyer, Dean; starlingx-discuss at lists.starlingx.io Subject: RE: Analysis report about Network Trunk feature for StartlingX upstreaming Ian, Thanks very much for the comments. some comments below for you reference, and please help to review, thanks much! Best Regards, Le, Huifeng From: Jolliffe, Ian [mailto:Ian.Jolliffe at windriver.com] Sent: Saturday, August 18, 2018 4:16 AM To: Le, Huifeng >; Jones, Bruce E >; Rowsell, Brent >; Peters, Matt > Cc: Zhao, Forrest >; Troyer, Dean >; starlingx-discuss at lists.starlingx.io Subject: Re: Analysis report about Network Trunk feature for StartlingX upstreaming Hi Huifeng; Thanks for the updates/analysis, comments below. Ian Ian/Brent/Matt, We did analysis about the Network trunk related patches for StartingX upstream, below are the suggestions for upstreaming, could you please help to review and comment? Thanks much! 1. ba9d9f60a7a2665194cacb92a05e0acd2dc3de41: Add rpc notification for trunk updates Function: sent notification to the agent when a trunk is updated Analysis: (1)Trunk’s AFTER_UPDATE event is generated for API call: PUT /v2.0/trunks/{trunk-id} The update request is only for changing fields like name, description or admin_state_up. Setting the admin_state_up to False locks the trunk in that it prevents operations such as adding/removing subports. In Neutron upstream, admin_state_up is used in server side, e.g. add_subports, remove subports, delete_trunk and not used in agent side (2)OVS trunk agent driver uses OVSDB event to handle trunk event, no need to manually trigger trunk update event (3)Linux trunk agent driver will handle trunk update event triggered by server, while it will need apply the patch only in case admin_state_up update need to be handled Suggestion: Not a bug for Neutron upstream, suggest not to upstream If this is not upstreamed, are the dependencies or changes required in the StarlingX code base? What are the implications of not upstreaming? [hle2] for STX, trunk_updated event will force the trunk’s parent-port to refresh (e.g. handle_trunks->mark_port_for_refresh(trunk['port_id']) etc.) to get the new “admin_state_up” value from server and this value will be used in handle_updated_port() to determine whether it is allowed to update port/device status in server side. “admin_state_up” is mainly used to control operation at neutron server side like add_subports, remove subports, delete_trunk etc. and all these 3 operations will force port to refresh (handle_trunks/handle_subports->mark_port_for_refresh), so suppose, the general flow will not be impacted whether to handle trunk_updated event or not. But in some wired cases, add “admin_state_up” check in agent side may cause issues (please help to review whether it is make sense), e.g for below calling flow (suppose trunk’s ‘admin_state_up’ is ‘up’): (1) add_subports (2) set “admin_state_up” to ‘down’, step(1) may fail to set device’s state at agent side in case aws agent’s handle_updated_port() (in daemon loop) executed after step (2) So to my understanding: (1) if using OVS agent in STX, no impact for not upstream (2) if using AVS agent + STX, suggest removing “admin_state_up” check in AVS agent (in function handle_updated_port () of avs/agent.py) like below. if trunk_details and trunk_details['admin_state_up']: … [MP>] Thanks for the detailed analysis. The suggested change will need to be tested to see if it full resolves the original issue. However, since the driver could be used by other agents (beyond just the AVS agent), I think it would not hurt to have the additional notification sent to complete the driver definition for the set of RPC notifications. 2. 6955351c5eca6e37061fb0140d11ea53693fe0e1: Add support to delete bound network Function: enable delete trunk if it is can_be_trunked (not bounded or driver’s can_trunk_bound_port=true) Analysis: Applied for LinuxBridge Driver and AVS bridge Driver (can_trunk_bound_port=True), no impact for OVSTrunkDriver (can_trunk_bound_port=False). workaround also available for linux bridge (e.g. unbind the port first then delete the trunk) Suggestion: it is a low priority bug for Neutron upstream (only applied for linux bridge and workround available), suggest not to upstream I think you need to propose a fix. Or this will need to be carried long term. [hle2] yes, let’s try to propose a fix for upstream. [MP>] Agree. 3. 43a684946e781a25d21a4f50b8dc67d61be42809: Enable trunk service by default Function: add “trunk” in DEFAULT_SERVICE_PLUGINS Analysis: It is a deploy configuration for downstream product Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. 4. c54d804792f10b7f505de6794274c4df4768f6f0: Include trunk presence in port details Function: add trunk_port (bool) flag in port_details to identify whether this port is a parent port for a trunk Analysis: It is a performance improvement for AVS agent by reducing RPC call from agent to server. OVS agent has different implementation with no improvement by introducing this field Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. 5. 3eed837ebd236e6b1959ea88d9ab5322c9eef6b9: Ignore trunk subports on same vlan as vlan-subnet ports Function: Ignore trunk subports on same vlan as vlan-subnet ports Analysis: It is a bug fix for AVS agent Suggestion: Not a bug for Neutron upstream, suggest not to upstream Agree [MP>] Agree. Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Sep 20 08:30:29 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 20 Sep 2018 08:30:29 +0000 Subject: [Starlingx-discuss] Merge f/centos75 feature branch into master In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C765536B84C@SHSMSX101.ccr.corp.intel.com> Hi all, Please notice feature branch centos75 has been merged back to master. When you sync latest code, please make sure to update mirror to have CentOS7.5 package for build. Best Regards Shuicheng -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Thursday, September 20, 2018 3:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Merge f/centos75 feature branch into master I have proposed the 4 reviews to merge the f/centos75 feature branch into master[0]. When approved we should consider the feature branch closed. Please let me know if you see anything odd about this as it is the first re-merge of a feature branch for us... Thanks dt [0] https://review.openstack.org/#/q/topic:merge-f/centos75+(status:open+OR+status:merged) -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From aragorn at intel.com Thu Sep 20 09:17:38 2018 From: aragorn at intel.com (aragorn at intel.com) Date: 20 Sep 2018 02:17:38 -0700 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#97] Missing packages - Results report Message-ID: [mirror-downloader][#97] Missing packages. Results report: - Missing: logs/K1_rpms_missing_centos.log adobe-source-code-pro-fonts-2.010.1.030-1.el7.noarch.rpm libcmocka-1.1.1-0.el7.x86_64.rpm libcmocka-devel-1.1.1-0.el7.x86_64.rpm unifont-fonts-9.0.06-2.el7.noarch.rpm - Missing: logs/L1_rpms_missing_centos.log adobe-source-code-pro-fonts-2.010.1.030-1.el7.noarch.rpm libcmocka-1.1.1-0.el7.x86_64.rpm libcmocka-devel-1.1.1-0.el7.x86_64.rpm unifont-fonts-9.0.06-2.el7.noarch.rpm - Missing: logs/L1_srpms_missing_centos.log lshell-0.9.16-5.el7.src.rpm From chenjie.xu at intel.com Thu Sep 20 09:27:09 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Thu, 20 Sep 2018 09:27:09 +0000 Subject: [Starlingx-discuss] Analysis of patch 170f4be for StartlingX upstreaming Message-ID: Hi Matt, We are analyzing the patch 170f4be. This patch add an "audit" flag into fdb but I find that ovs agent don't process this flag. Wondering if this flag is processed by avs agent? Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry at openstack.org Thu Sep 20 09:41:02 2018 From: thierry at openstack.org (Thierry Carrez) Date: Thu, 20 Sep 2018 11:41:02 +0200 Subject: [Starlingx-discuss] RFC: Updated governance doc on the wiki In-Reply-To: <9A85D2917C58154C960D95352B22818BAB59155F@fmsmsx115.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB58FEA1@fmsmsx115.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB59155F@fmsmsx115.amr.corp.intel.com> Message-ID: <286a2db6-d44d-20a0-bbc2-61f47b0762d5@openstack.org> Jones, Bruce E wrote: > Dean, thank you for this feedback. I have made all of the changes you suggested to the Governance wiki page. > > Additional feedback on https://wiki.openstack.org/wiki/Starlingx/Initial_Governance is welcome! Great work there (especially on the Project Lead rewritten paragraph)! My only comment would be around the "no single organization may be represented by more than two seats at any given time" rule for TSC and how that would work in practice. At election time it's pretty simple -- if the elected person would break the rule, just skip them and take the next ranked person. It's a bit more tricky in case of job changes triggering the rule. Like some TSC member X moving to a company that already has 2 members. It would be a good idea to describe how to handle that (likely) situation so that you already know how to handle it. Options would be for that person to immediately lose their TSC seat (to be replaced by next in line in the election results ?), or to keep it until the next election round, or to keep it but not have a formal vote until the next election... The mention that "Individuals are expected to continue to support the project in the event of career changes unless they notify the project that they are resigning their position" tend to point to one of the latter options, but it's a bit unclear. In my experience, we tend to overthink those rules -- I think it would be safe to just wait until the next election to "fix" the situation. Those happen often enough anyway, and someone changing companies and continuing to work on the project is a lot more likely to wear their "project hat" rather than their "new company hat" anyway. So my suggestion would be to replace "no single organization may be represented by more than two seats at any given time" by "no single organization may be represented by more than two seats after any election round". -- Thierry Carrez (ttx) From abraham.arce.moreno at intel.com Thu Sep 20 14:47:59 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 20 Sep 2018 14:47:59 +0000 Subject: [Starlingx-discuss] StarlingX Release Sub-Projects In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA403D2D@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB575A46@fmsmsx115.amr.corp.intel.com> Message-ID: > hi, Arce, Hi Wei, I apologize for the late reply. > I checked the link and found that no content there. Is there any process > there? > > We have a PRC partner that would like to discuss with us for use case for > StarlingX. We do not have an official StarlingX working group yet so we will not see formal content in this page [0] at least for the next weeks, let our PRC partner know this mailing list is open to initiate the discussion at a high level. Another recommendation is to join the OpenStack Edge Computing Group [1] who is driving a great number of discussions. We have a weekly call on Monday 13:00 PST, for more details please refer to the Sub Group Use Cases wiki section [2], our PRC partner can be included in the agenda to present and get feedback on his particular use case. Bruce? Ghada? Please feel free to propose any other way to help PRC partner, and let me know if something needs to be done from my side. [0] https://wiki.openstack.org/wiki/StarlingX/Use_Cases [1] https://wiki.openstack.org/wiki/Edge_Computing_Group [2] https://wiki.openstack.org/wiki/Edge_Computing_Group#Use_cases From wei.w.hu at intel.com Thu Sep 20 15:04:56 2018 From: wei.w.hu at intel.com (Hu, Wei W) Date: Thu, 20 Sep 2018 15:04:56 +0000 Subject: [Starlingx-discuss] StarlingX Release Sub-Projects In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA403D2D@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB575A46@fmsmsx115.amr.corp.intel.com> Message-ID: Thanks, Arce. This is very informative and helpful. We will have meetings tomorrow with our partner. So just in time. Let's see the feedback and how we work together to help them. -----Original Message----- From: Arce Moreno, Abraham Sent: Thursday, September 20, 2018 10:48 PM To: Hu, Wei W ; Jones, Bruce E ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: StarlingX Release Sub-Projects > hi, Arce, Hi Wei, I apologize for the late reply. > I checked the link and found that no content there. Is there any > process there? > > We have a PRC partner that would like to discuss with us for use case > for StarlingX. We do not have an official StarlingX working group yet so we will not see formal content in this page [0] at least for the next weeks, let our PRC partner know this mailing list is open to initiate the discussion at a high level. Another recommendation is to join the OpenStack Edge Computing Group [1] who is driving a great number of discussions. We have a weekly call on Monday 13:00 PST, for more details please refer to the Sub Group Use Cases wiki section [2], our PRC partner can be included in the agenda to present and get feedback on his particular use case. Bruce? Ghada? Please feel free to propose any other way to help PRC partner, and let me know if something needs to be done from my side. [0] https://wiki.openstack.org/wiki/StarlingX/Use_Cases [1] https://wiki.openstack.org/wiki/Edge_Computing_Group [2] https://wiki.openstack.org/wiki/Edge_Computing_Group#Use_cases From cesar.lara at intel.com Thu Sep 20 17:27:57 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Thu, 20 Sep 2018 17:27:57 +0000 Subject: [Starlingx-discuss] [Build] [meetings] September 17 - meeting minutes Message-ID: <0B566C62EC792145B40E29EFEBF1AB471050BE8B@fmsmsx104.amr.corp.intel.com> Attendees Mario, Memo, Hayde, Erich, Jason, Scott, Bruce, Saul,Chuy Agenda -Scoping and planning for first release of sxtb tool (all) -Installer consolidation for starling X https://bugs.launchpad.net/starlingx/+bug/1790213 Installer consolidation - We are seeing differences in the packages contained in the installer for StarlingX once the ISO is being built, apparently we have two different approaches on generating the installer files, we need to consolidate and adopt a single set of instructions to generate installer files. More information on this topic for consolidation of files and instructions - Ken Stxb tool - not ready for release yet as we are missing a few scenarios to standardize on a single tool, on initial scope, stxb tool was set as a "getting started" kind of thing, not meant to go after developers use case. A lot of comments on the code and the implementation of the logic behind the toll were raised, we will still discussing around the first scope and if this meets the criteria to be released in the next few weeks. November release out of scope for stxb tool. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Sep 20 17:47:06 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 20 Sep 2018 17:47:06 +0000 Subject: [Starlingx-discuss] RFC: Updated governance doc on the wiki In-Reply-To: <286a2db6-d44d-20a0-bbc2-61f47b0762d5@openstack.org> References: <9A85D2917C58154C960D95352B22818BAB58FEA1@fmsmsx115.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB59155F@fmsmsx115.amr.corp.intel.com> <286a2db6-d44d-20a0-bbc2-61f47b0762d5@openstack.org> Message-ID: <9A85D2917C58154C960D95352B22818BAB591DE8@fmsmsx115.amr.corp.intel.com> Dean, thank you for the feedback. The current text (which we edited live at the call this week) says: "There are no limits on the number of terms an individual may serve, but no single organization may be represented by more than two seats at any given time. In the event that 3 people from one organization are elected to the TSC in one election, the person with the lowest vote count among the 3 is skipped and the next candidate is elected. Any other case of more than 2 people per company on the TSC shall be addressed at the latest at the next scheduled election." I think this addresses your concerns. brucej -----Original Message----- From: Thierry Carrez [mailto:thierry at openstack.org] Sent: Thursday, September 20, 2018 2:41 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] RFC: Updated governance doc on the wiki Jones, Bruce E wrote: > Dean, thank you for this feedback. I have made all of the changes you suggested to the Governance wiki page. > > Additional feedback on https://wiki.openstack.org/wiki/Starlingx/Initial_Governance is welcome! Great work there (especially on the Project Lead rewritten paragraph)! My only comment would be around the "no single organization may be represented by more than two seats at any given time" rule for TSC and how that would work in practice. At election time it's pretty simple -- if the elected person would break the rule, just skip them and take the next ranked person. It's a bit more tricky in case of job changes triggering the rule. Like some TSC member X moving to a company that already has 2 members. It would be a good idea to describe how to handle that (likely) situation so that you already know how to handle it. Options would be for that person to immediately lose their TSC seat (to be replaced by next in line in the election results ?), or to keep it until the next election round, or to keep it but not have a formal vote until the next election... The mention that "Individuals are expected to continue to support the project in the event of career changes unless they notify the project that they are resigning their position" tend to point to one of the latter options, but it's a bit unclear. In my experience, we tend to overthink those rules -- I think it would be safe to just wait until the next election to "fix" the situation. Those happen often enough anyway, and someone changing companies and continuing to work on the project is a lot more likely to wear their "project hat" rather than their "new company hat" anyway. So my suggestion would be to replace "no single organization may be represented by more than two seats at any given time" by "no single organization may be represented by more than two seats after any election round". -- Thierry Carrez (ttx) _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ken.Young at windriver.com Thu Sep 20 18:27:55 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Thu, 20 Sep 2018 18:27:55 +0000 Subject: [Starlingx-discuss] [Build] [meetings] September 17 - meeting minutes In-Reply-To: <0B566C62EC792145B40E29EFEBF1AB471050BE8B@fmsmsx104.amr.corp.intel.com> References: <0B566C62EC792145B40E29EFEBF1AB471050BE8B@fmsmsx104.amr.corp.intel.com> Message-ID: <56ED7B56-2DCA-4D4F-93E0-7BEFF5C12E4A@windriver.com> Cesar, Thank you for the minutes. I have closed my action below with an email to the discussion list yesterday. Let’s review that in Monday in the build meeting. /KenY From: "Lara, Cesar" Date: Thursday, September 20, 2018 at 1:29 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [Build] [meetings] September 17 - meeting minutes Attendees Mario, Memo, Hayde, Erich, Jason, Scott, Bruce, Saul,Chuy Agenda -Scoping and planning for first release of sxtb tool (all) -Installer consolidation for starling X https://bugs.launchpad.net/starlingx/+bug/1790213 Installer consolidation – We are seeing differences in the packages contained in the installer for StarlingX once the ISO is being built, apparently we have two different approaches on generating the installer files, we need to consolidate and adopt a single set of instructions to generate installer files. More information on this topic for consolidation of files and instructions – Ken Stxb tool – not ready for release yet as we are missing a few scenarios to standardize on a single tool, on initial scope, stxb tool was set as a “getting started” kind of thing, not meant to go after developers use case. A lot of comments on the code and the implementation of the logic behind the toll were raised, we will still discussing around the first scope and if this meets the criteria to be released in the next few weeks. November release out of scope for stxb tool. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Sep 20 20:10:28 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 20 Sep 2018 20:10:28 +0000 Subject: [Starlingx-discuss] Bug Handling Process >> Proposal for notgating tag Message-ID: <151EE31B9FCCA54397A757BC674650F0BA455453@ALA-MBD.corp.ad.wrs.com> Hello all, In StarlingX, we currently use labels for target releases for Features/Enhancements as well as bugs [0]: Example: stx.2018.10 (October Release), stx.2019.03 (March Release). For low priority bugs or enhancements which may not have a target release, I was thinking to use a specific tag to indicate that they do not gate any release - stx.ng or stx.notgating. This would help with the screening/prioritization process. Right now, we leave them blank (w/o a release tag), but it's harder to tell if they have been reviewed or not. I like the idea of having an explicit release better. Any thoughts or concerns? [0] https://wiki.openstack.org/wiki/StarlingX/Tags_and_Prefixes Thanks, Ghada From: Khalil, Ghada Sent: Monday, September 17, 2018 6:23 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: Bug Handling Process / Useful Launchpad Bugs / Focus on stx.2018.10 Bugs Hello all, I've documented details of the StarlingX Bug Handling process on the wiki: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process Please review and let me know if you have any feedback. All feedback is welcome. In the above wiki, I have included links to useful Launchpad bugs: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process#Key_StarlingX_Bug_Queries With the team's focus on stx.2018.10, I have created specific queries for the release. Project Leads, Please have a look at the unassigned stx.2018.10 bugs and assign to the team accordingly. Please also track all stx.2018.10 bugs to resolution as part of your regular team meetings/communication. Thanks, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273 skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Sep 20 21:05:16 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 20 Sep 2018 21:05:16 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking meeting - 9/20 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA455510@ALA-MBD.corp.ad.wrs.com> The StarlingX networking team had their first meeting on 8/30. Weekly meetings are scheduled for Thursday at 9am Eastern. Meeting Details are available on the wiki: https://wiki.openstack.org/wiki/StarlingX/Networking Meeting agenda/notes are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Sept 20/2018 * Neutron Blueprint Status / Next Steps * Provider Network Management -- Highest priority ? Merge the Segment Range Management in this spec: https://review.openstack.org/579411 ? Also include the current API (w/o the Host Management piece) ? Rename to Provider Segment Range Configuration ? Action: Ruijing to add a note to the current spec review saying we will re-work the spec based on the feedback from PTG and re-publish it. Fcst: Sept 21 ? Next Step: Ruijing to re-work the spec. Time-Line: 1-2wks to have the updated spec. Fcst: Sept 28-Oct5 * Action: Forrest to confirm the resourcing for this work * System Host Management ? neutron community did not agree to move forward with this spec. The neutron spec will not be pursued any further. ? Action: Ruijing to add a note to the gerrit review and mark the review as Abandoned. Fcst: Sept 21 ? Plan is to move this functionality to the stx-nfv project * Use the neutron APIs from stx-nfv. Need to prototype the use of admin_state_up / admin_state_down o This may drive an Enhancement Request into neutron. Neutron team was open to this. ? Next Step: Matt to write story in SB describing the requirements. * After consultation with the Technical Lead for stx-nfv, he advised us to defer this work for a while as the code is undergoing churn due to containerization support. * We will revisit this again in a few weeks - October 18 * Rescheduling of DHCP Servers and Routers ? neutron community did not agree to move forward with this spec. The neutron spec will not be pursued any further. ? Action: Ruijing to add a note to the gerrit review and mark the review as Abandoned. Fcst: Sept 21 ? Plan is to move this functionality to the stx-nfv project * Implement a plugin in the stx-nfv vim to do the re-scheduling ? Next Step: Matt to capture requirements in SB. Note: This will be included in the same story as the "System Host Management" since they are closely related * Fault Management ? Plan is to not pursue this spec with neutron. The corresponding gerrit review will be abandoned. ? Action: Ruijing to add a note to the review and mark the review as Abandoned. Fcst: Sept 21 ? For now, leave the patch in stx-neutron as is. This is broader than just neutron, same hooks exist in glance/cinder/etc. Need a larger discussion/decision. ? Put on hold for now. * ML2 Connection Auditing and Monitoring ? Plan is to review the current neutron logging capabilities to see if it is sufficient to diagnose issues * Neutron team is open to receiving Enhancement Requests if needed. ? Action: Forrest to confirm the resourcing for this work * Other Neutron Upstreaming Patches - Bugs * Not reviewed in the meeting * stx.2018.10 Status * 2 features planned and on track * 6 bugs: 2 well understood, 2 need more info, 2 need further investigation ? Kailun to follow up on https://bugs.launchpad.net/starlingx/+bug/1790252 * ovs-dpdk Enhancements - stx.2019.03 * Kailun working on OVS-DPDK Firewall Driver Enhancements. ? Facing some issues . Steve to send output from his system. Regards, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Sep 20 21:11:08 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 20 Sep 2018 21:11:08 +0000 Subject: [Starlingx-discuss] [MutliOS] New wiki page & RFC Clear Linux demo high level plan Message-ID: <9A85D2917C58154C960D95352B22818BAB592012@fmsmsx115.amr.corp.intel.com> As most of you know, the Intel team has been asked to implement a pilot/POC showing StarlingX running in a very limited fashion using Clear Linux as the Host OS. There has been some internal work and planning for this. I'm going to start taking that work out into the open through the newly created Multi-OS sub-project wiki page [0]. Saul and I did some brainstorming this afternoon on a high level plan for the Clear Linux demo. It's documented on the wiki [1]. We are looking for feedback on that high level plan, especially from the people already working on this. brucej [0] https://wiki.openstack.org/wiki/StarlingX/MultiOS [1] https://wiki.openstack.org/wiki/StarlingX/MultiOS#Clear_Linux_high_level_plan -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Sep 20 21:39:16 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 20 Sep 2018 21:39:16 +0000 Subject: [Starlingx-discuss] [Docs] Publish StarlingX governance from an access controlled git repo Message-ID: <9A85D2917C58154C960D95352B22818BAB592063@fmsmsx115.amr.corp.intel.com> I've just created a new story for this work [0]. Docs team, please review the story and tasks, and update as needed. And feel free to sign up for the tasks :). Brucej [0] https://storyboard.openstack.org/#!/story/2003821 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Sep 20 21:51:13 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 20 Sep 2018 21:51:13 +0000 Subject: [Starlingx-discuss] Bug Handling Process >> Proposal for notgating tag In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA455453@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA455453@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5920E3@fmsmsx115.amr.corp.intel.com> Maybe marking such bugs as Low priority is enough? If a new bug comes in that isn't important, mark it Low and maybe someday someone will fix it. If someone files a Low bug and then asks about it later, it must not be Low anymore so raise the priority and tag it for a release. brucej From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, September 20, 2018 1:10 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Bug Handling Process >> Proposal for notgating tag Hello all, In StarlingX, we currently use labels for target releases for Features/Enhancements as well as bugs [0]: Example: stx.2018.10 (October Release), stx.2019.03 (March Release). For low priority bugs or enhancements which may not have a target release, I was thinking to use a specific tag to indicate that they do not gate any release - stx.ng or stx.notgating. This would help with the screening/prioritization process. Right now, we leave them blank (w/o a release tag), but it's harder to tell if they have been reviewed or not. I like the idea of having an explicit release better. Any thoughts or concerns? [0] https://wiki.openstack.org/wiki/StarlingX/Tags_and_Prefixes Thanks, Ghada From: Khalil, Ghada Sent: Monday, September 17, 2018 6:23 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: Bug Handling Process / Useful Launchpad Bugs / Focus on stx.2018.10 Bugs Hello all, I've documented details of the StarlingX Bug Handling process on the wiki: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process Please review and let me know if you have any feedback. All feedback is welcome. In the above wiki, I have included links to useful Launchpad bugs: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process#Key_StarlingX_Bug_Queries With the team's focus on stx.2018.10, I have created specific queries for the release. Project Leads, Please have a look at the unassigned stx.2018.10 bugs and assign to the team accordingly. Please also track all stx.2018.10 bugs to resolution as part of your regular team meetings/communication. Thanks, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273 skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From eddie.ramirez at intel.com Thu Sep 20 21:55:29 2018 From: eddie.ramirez at intel.com (Ramirez, Eddie) Date: Thu, 20 Sep 2018 21:55:29 +0000 Subject: [Starlingx-discuss] Bug Handling Process >> Proposal for notgating tag In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5920E3@fmsmsx115.amr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA455453@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB5920E3@fmsmsx115.amr.corp.intel.com> Message-ID: Agree with Bruce, LOW priority is self-explanatory and can be deferred until more people users are affected…. From: "Jones, Bruce E" Date: Thursday, September 20, 2018 at 2:52 PM To: "'starlingx-discuss at lists.starlingx.io'" Subject: Re: [Starlingx-discuss] Bug Handling Process >> Proposal for notgating tag Maybe marking such bugs as Low priority is enough? If a new bug comes in that isn’t important, mark it Low and maybe someday someone will fix it. If someone files a Low bug and then asks about it later, it must not be Low anymore so raise the priority and tag it for a release. brucej From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, September 20, 2018 1:10 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Bug Handling Process >> Proposal for notgating tag Hello all, In StarlingX, we currently use labels for target releases for Features/Enhancements as well as bugs [0]: Example: stx.2018.10 (October Release), stx.2019.03 (March Release). For low priority bugs or enhancements which may not have a target release, I was thinking to use a specific tag to indicate that they do not gate any release – stx.ng or stx.notgating. This would help with the screening/prioritization process. Right now, we leave them blank (w/o a release tag), but it’s harder to tell if they have been reviewed or not. I like the idea of having an explicit release better. Any thoughts or concerns? [0] https://wiki.openstack.org/wiki/StarlingX/Tags_and_Prefixes Thanks, Ghada From: Khalil, Ghada Sent: Monday, September 17, 2018 6:23 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: Bug Handling Process / Useful Launchpad Bugs / Focus on stx.2018.10 Bugs Hello all, I’ve documented details of the StarlingX Bug Handling process on the wiki: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process Please review and let me know if you have any feedback. All feedback is welcome. In the above wiki, I have included links to useful Launchpad bugs: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process#Key_StarlingX_Bug_Queries With the team’s focus on stx.2018.10, I have created specific queries for the release. Project Leads, Please have a look at the unassigned stx.2018.10 bugs and assign to the team accordingly. Please also track all stx.2018.10 bugs to resolution as part of your regular team meetings/communication. Thanks, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273 skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Thu Sep 20 21:56:39 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 20 Sep 2018 21:56:39 +0000 Subject: [Starlingx-discuss] Bug Handling Process >> Proposal for notgating tag In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA455453@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA455453@ALA-MBD.corp.ad.wrs.com> Message-ID: <85F739BD-DA76-49E8-AD9A-3B5C11CDB978@windriver.com> I think you proposal makes sense Brent Sent from my iPhone On Sep 20, 2018, at 3:11 PM, Khalil, Ghada > wrote: Hello all, In StarlingX, we currently use labels for target releases for Features/Enhancements as well as bugs [0]: Example: stx.2018.10 (October Release), stx.2019.03 (March Release). For low priority bugs or enhancements which may not have a target release, I was thinking to use a specific tag to indicate that they do not gate any release – stx.ng or stx.notgating. This would help with the screening/prioritization process. Right now, we leave them blank (w/o a release tag), but it’s harder to tell if they have been reviewed or not. I like the idea of having an explicit release better. Any thoughts or concerns? [0] https://wiki.openstack.org/wiki/StarlingX/Tags_and_Prefixes Thanks, Ghada From: Khalil, Ghada Sent: Monday, September 17, 2018 6:23 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: Bug Handling Process / Useful Launchpad Bugs / Focus on stx.2018.10 Bugs Hello all, I’ve documented details of the StarlingX Bug Handling process on the wiki: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process Please review and let me know if you have any feedback. All feedback is welcome. In the above wiki, I have included links to useful Launchpad bugs: https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process#Key_StarlingX_Bug_Queries With the team’s focus on stx.2018.10, I have created specific queries for the release. Project Leads, Please have a look at the unassigned stx.2018.10 bugs and assign to the team accordingly. Please also track all stx.2018.10 bugs to resolution as part of your regular team meetings/communication. Thanks, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273 skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 _______________________________________________ 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 erich.cordoba.malibran at intel.com Thu Sep 20 23:36:03 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 20 Sep 2018 23:36:03 +0000 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#97] Missing packages - Results report In-Reply-To: References: Message-ID: <77adde8f71f2ba3f1eaecfc202f77e1d3e1a61f2.camel@intel.com> I created these two bugs related with this failure. https://bugs.launchpad.net/starlingx/+bug/1793617 https://bugs.launchpad.net/starlingx/+bug/1793615 I'm testing fix for 1793617, however the other one is more tricky. Basically lshell package cannot be downloaded because the mirror where it lives is corrupt. I think we need another mirror (can't find one yet) or talk with the administrator of that mirror. -Erich On Thu, 2018-09-20 at 02:17 -0700, aragorn at intel.com wrote: > [mirror-downloader][#97] Missing packages. Results report: > - Missing: logs/K1_rpms_missing_centos.log > adobe-source-code-pro-fonts-2.010.1.030-1.el7.noarch.rpm > libcmocka-1.1.1-0.el7.x86_64.rpm > libcmocka-devel-1.1.1-0.el7.x86_64.rpm > unifont-fonts-9.0.06-2.el7.noarch.rpm - Missing: > logs/L1_rpms_missing_centos.log > adobe-source-code-pro-fonts-2.010.1.030-1.el7.noarch.rpm > libcmocka-1.1.1-0.el7.x86_64.rpm > libcmocka-devel-1.1.1-0.el7.x86_64.rpm > unifont-fonts-9.0.06-2.el7.noarch.rpm - Missing: > logs/L1_srpms_missing_centos.log > lshell-0.9.16-5.el7.src.rpm > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From shuicheng.lin at intel.com Fri Sep 21 06:37:59 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 21 Sep 2018 06:37:59 +0000 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#97] Missing packages - Results report In-Reply-To: <77adde8f71f2ba3f1eaecfc202f77e1d3e1a61f2.camel@intel.com> References: <77adde8f71f2ba3f1eaecfc202f77e1d3e1a61f2.camel@intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765536DAB2@SHSMSX101.ccr.corp.intel.com> Hi Erich, I could find lshell in below repo and download successfully: [slin14 at a7b7e1499d7a cgcs-root]$ sudo -E yumdownloader -C --source --url lshell-0.9.16-5.el7 Loaded plugins: fastestmirror, ovl Enabling base-source repository Enabling extras-source repository Enabling epel-source repository Enabling updates-source repository http://epel.blizoo.mk/epel/7/SRPMS/l/lshell-0.9.16-5.el7.src.rpm Best Regards Shuicheng -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Friday, September 21, 2018 7:36 AM To: aragorn ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#97] Missing packages - Results report I created these two bugs related with this failure. https://bugs.launchpad.net/starlingx/+bug/1793617 https://bugs.launchpad.net/starlingx/+bug/1793615 I'm testing fix for 1793617, however the other one is more tricky. Basically lshell package cannot be downloaded because the mirror where it lives is corrupt. I think we need another mirror (can't find one yet) or talk with the administrator of that mirror. -Erich On Thu, 2018-09-20 at 02:17 -0700, aragorn at intel.com wrote: > [mirror-downloader][#97] Missing packages. Results report: > - Missing: logs/K1_rpms_missing_centos.log > adobe-source-code-pro-fonts-2.010.1.030-1.el7.noarch.rpm > libcmocka-1.1.1-0.el7.x86_64.rpm > libcmocka-devel-1.1.1-0.el7.x86_64.rpm > unifont-fonts-9.0.06-2.el7.noarch.rpm - Missing: > logs/L1_rpms_missing_centos.log > adobe-source-code-pro-fonts-2.010.1.030-1.el7.noarch.rpm > libcmocka-1.1.1-0.el7.x86_64.rpm > libcmocka-devel-1.1.1-0.el7.x86_64.rpm > unifont-fonts-9.0.06-2.el7.noarch.rpm - Missing: > logs/L1_srpms_missing_centos.log > lshell-0.9.16-5.el7.src.rpm > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Fri Sep 21 11:48:02 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 21 Sep 2018 13:48:02 +0200 Subject: [Starlingx-discuss] OSF Edge Computing Group BoF at ONS EU Message-ID: <307B9C5B-9B3F-4273-8CD7-C0E9944BC1D8@gmail.com> Hi, I would like to draw your attention to a BoF session around Edge to explore use cases and current ongoing design, development and testing activities under the OpenStack Foundation umbrella, OPNFV, ONAP, Akraino and so forth and to identify next steps. You can find more details about the session here: https://onseu18.sched.com/event/GZqk/edge-computing-group-at-ons-europe The gathering is overlapping with the Edge Computing Group weekly call and I will keep the Zoom call (https://zoom.us/j/879678938) open for the session, so those of you who’re interested but cannot join on site can dial in remotely. Please let me know if you have any questions. See you next week in Amsterdam! :) Thanks and Best Regards, Ildikó From Dariush.Eslimi at windriver.com Fri Sep 21 18:11:13 2018 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Fri, 21 Sep 2018 18:11:13 +0000 Subject: [Starlingx-discuss] StarlingX Release Notes Content In-Reply-To: References: Message-ID: I updated the etherpad for following repos: • stx-clients • stx-config • stx-distcloud • stx-distcloud-client • stx-fault • stx-gui • stx-ha • stx-metal • stx-update • stx-nfv Cheers, Dariush -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: September-17-18 11:30 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] StarlingX Release Notes Content To all StarlingX main and supporting projects leaders: In preparation to complete our documentation journey we need your help to write under this etherpad page [0] the content for your Release Notes including a Prelude and a couple of features to be added in your project repository, we are targeting this task to be completed if possible, end of this week. Please take a look at the example from Dean in the same etherpad page [0] submitted though a stx-tools gerrit review [1], we will take your information from the Etherpad and we will add it to the Release Notes commit. [0] https://etherpad.openstack.org/p/stx-docs [1] https://review.openstack.org/#/c/600198/3/releasenotes/notes/release-summary-9c35dd1bd9b020f1.yaml _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From michel.thebeau at windriver.com Fri Sep 21 20:27:20 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Fri, 21 Sep 2018 16:27:20 -0400 Subject: [Starlingx-discuss] Stories for stx-tools deployment In-Reply-To: References: <511d268b-c23c-2520-152c-fcf7e9286e09@windriver.com> Message-ID: <282f2903-db5a-e98e-b884-f9d68af14dc5@windriver.com> Hi Abraham, I created four stories: deployment/libvirt: sizing for reference configurations   https://storyboard.openstack.org/#!/story/2003835 deployment/libvirt: virtual disk placement for reference configurations   https://storyboard.openstack.org/#!/story/2003836 deployment/libvirt: tenant networking for reference configurations   https://storyboard.openstack.org/#!/story/2003837 deployment/libvirt: concurrent clusters under virtualization   https://storyboard.openstack.org/#!/story/2003838 M On 2018-09-17 09:44 PM, Arce Moreno, Abraham wrote: > Michel, > >> I've been working through the wikis under >> "https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Enviro >> nment". > We really appreciate and thank you for your support for the recent improvements > made under stx-tools to support the StarlingX installation under a virtual environment. > >> After I've finished reviewing "standard Controller Storage" and "all-in-one" >> configurations under virtualization, I'd like consider stories for stx- >> tools/deployement such as "running multiple clusters on a host" and "testing >> networking for instances". >> >> I do not see anything in storyboard: >> https://storyboard.openstack.org/#!/project/openstack/stx-tools >> >> Do you know if there are plans for those things? > From my understanding there are no more stories associated to virtualization since > pushing out the initial commit based in Ubuntu and deploying the different configurations > under a Virtual Environment were completed so please feel to create the next level of stories. > > Only pending thing based on feedback from Greg Waines is to take advantage of the existing > documentation to add the deployment under Bare Metal so this might be a missing story, I will > add it. > > Please let us know how we can help. From ildiko.vancsa at gmail.com Fri Sep 21 21:25:56 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 21 Sep 2018 23:25:56 +0200 Subject: [Starlingx-discuss] Forum session proposal period closes soon! - ACTION NEEDED Message-ID: <30B2D975-6605-461A-90F6-D03219B2A547@gmail.com> Hi, It is a friendly reminder that the session proposal period for the Forum at the Berlin OpenStack Summit is closing on the 26th of September. You can find the topics proposed for StarlingX so far on this etherpad: https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming Please check the session ideas and add your vote to the ones you would like to have up for discussion or add new ideas if you have more topics in mind. The sessions that the StarlingX community decide to propose also need a moderator, please sign up on the etherpad if you would be interested and available to moderate a session. Please let me know if you have any questions. Thanks and Best Regards, Ildikó From ada.cabrales at intel.com Fri Sep 21 23:54:03 2018 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Fri, 21 Sep 2018 23:54:03 +0000 Subject: [Starlingx-discuss] [ Test ] stx.2018.10 test plan Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E716E81DD@fmsmsx104.amr.corp.intel.com> Hello, I'm posting the test plan proposed for the October Release in the wiki [0]. We have 238 tests so far, mostly focus on the stx services. As we mentioned before, the tests will be run manually by our team for this release. The expectation is to increase the number of automated tests along time. We are considering to cover the four configurations (Simplex, Duplex, Multinode local storage, Multinode external storage) both on bare metal and virtual. However, we are experiencing setup problems with multinode bare metal and simplex. We are digging into it. We'll have more information next week. Please take a look at it and let us know what else must be included. Thanks Ada [0] https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan From scott.w.doenecke at intel.com Sat Sep 22 04:02:45 2018 From: scott.w.doenecke at intel.com (Doenecke, Scott W) Date: Sat, 22 Sep 2018 04:02:45 +0000 Subject: [Starlingx-discuss] StarlingX Brochure for Berlin - Draft for comments Message-ID: <9C2E28407FB51546B9A92BD2EB7218A0013A72A257@ORSMSX103.amr.corp.intel.com> Hello Claire et al, I’ve got a first cut at a possible StarlingX brochure for Berlin. Would you please take a look at it and see what you’d like to edit. Cheers, Scott -----Original Appointment----- From: claire at openstack.org [mailto:claire at openstack.org] Sent: Wednesday, August 22, 2018 10:08 AM To: claire at openstack.org; Doenecke, Scott W; glenn.seiler at windriver.com; Allison Price; Broughton, Travis V; Ildiko Vancsa; Jeff; starlingx-discuss at lists.starlingx.io Subject: Invitation: Bi-Weekly StarlingX Marketing/Community Content Work @ Every 2 weeks from 8am to 9am on Wednesday from Wed Sep 5 to Wed Nov 7 (PDT) (scott.w.doenecke at intel.com) When: Wednesday, September 19, 2018 10:00 AM-11:00 AM America/Chicago. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: StarlingX Handout_v1.1.pdf Type: application/pdf Size: 1176266 bytes Desc: StarlingX Handout_v1.1.pdf URL: From ildiko.vancsa at gmail.com Sat Sep 22 18:51:42 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Sat, 22 Sep 2018 20:51:42 +0200 Subject: [Starlingx-discuss] Additional StarlingX sessions at the Summit - Speakers Needed!! Message-ID: <5BB19D90-2953-4F62-92DC-323620BA961C@gmail.com> Hi, The next OpenStack Summit is approaching quickly and we are looking for speakers for a couple of additional sessions that we will be scheduling for StarlingX shortly to provide even more visibility to the project: * Project Update: a 20-minute long recorded session. The purpose of the session is to give an overview and update about the project, which I believe is a great opportunity to talk about the first release and the plans onwards beyond a brief introduction of the project. We are looking for one or at most two speakers for this session. * Project Onboarding: a 40-minute long non-recorded session. The purpose of this slot is to introduce the StarlingX project as well as the community to attract and onboard new contributors. It is important to let people know how they can get started with StarlingX and what they can start to work on/contribute to make it as easy for them to join the project as possible. We are looking for up to three speakers for this session, but having more team members in the room can help engaging with new contributors. * Breakout session (optional): a 40-minute long recorded session. We would like to offer one full conference session for the team to take. This can be either a presentation that was proposed for the CFP but wasn’t selected, or a topic that you feel important to talk about and is not covered yet through the already scheduled presentations. This opportunity is optional, but if the team decides to take it we will need a title, abstract and speaker(s) (max. 3) as soon as possible. I created an etherpad to sign up for the slots listed above: https://etherpad.openstack.org/p/StarlingXSessionsBerlin Please add your name to the ones you would like to present and suggestions for the breakout session if you have any, to choose from. We can discuss options on the project call next week and we would like to finalize the list of speakers and the breakout session details during the upcoming week or two. Please let me know if you have any questions. Thanks and Best Regards, Ildikó From ildiko.vancsa at gmail.com Sun Sep 23 12:49:39 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Sun, 23 Sep 2018 14:49:39 +0200 Subject: [Starlingx-discuss] StarlingX Release Sub-Projects In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA403D2D@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB575A46@fmsmsx115.amr.corp.intel.com> Message-ID: <6B5E3E25-8244-4D1C-9B7E-C601627B4D07@gmail.com> Hi, I would like to propose to use the Edge Computing Group as the forum to collect and discuss use cases and have that as a foundation for StarlingX as well. The Edge Computing Group is in the Edge focus area and with that it is not under the OpenStack project but rather incorporated with StarlingX in some extent on the same level. The group’s focus is on use cases, requirements and references architectures with some already ongoing activities on testing and enhancements in OpenStack services such as Keystone and Glance. As Abraham pointed out already we have a sub-group focusing on use cases with weekly calls on Mondays. Please let me know if you have any questions about the working group or the activities or the resources Abraham linked in his previous email. I would be happy to help the StarlingX team to join and leverage the activities the group has. Thanks and Best Regards, Ildikó > On 2018. Sep 20., at 17:04, Hu, Wei W wrote: > > Thanks, Arce. > > This is very informative and helpful. We will have meetings tomorrow with our partner. So just in time. Let's see the feedback and how we work together to help them. > > -----Original Message----- > From: Arce Moreno, Abraham > Sent: Thursday, September 20, 2018 10:48 PM > To: Hu, Wei W ; Jones, Bruce E ; Khalil, Ghada ; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: StarlingX Release Sub-Projects > >> hi, Arce, > > Hi Wei, I apologize for the late reply. > >> I checked the link and found that no content there. Is there any >> process there? >> >> We have a PRC partner that would like to discuss with us for use case >> for StarlingX. > > We do not have an official StarlingX working group yet so we will not see formal content in this page [0] at least for the next weeks, let our PRC partner know this mailing list is open to initiate the discussion at a high level. > > Another recommendation is to join the OpenStack Edge Computing Group [1] who is driving a great number of discussions. We have a weekly call on Monday > 13:00 PST, for more details please refer to the Sub Group Use Cases wiki section [2], our PRC partner can be included in the agenda to present and get feedback on his particular use case. > > Bruce? Ghada? > > Please feel free to propose any other way to help PRC partner, and let me know if something needs to be done from my side. > > [0] https://wiki.openstack.org/wiki/StarlingX/Use_Cases > [1] https://wiki.openstack.org/wiki/Edge_Computing_Group > [2] https://wiki.openstack.org/wiki/Edge_Computing_Group#Use_cases > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Greg.Waines at windriver.com Mon Sep 24 12:32:05 2018 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 24 Sep 2018 12:32:05 +0000 Subject: [Starlingx-discuss] Requesting suggestions for Berlin / Stein OpenStack Summit Forum topics from StarlingX Team In-Reply-To: <8F3DE5D5-0B6D-477A-92B8-47F4156FBA49@windriver.com> References: <8F3DE5D5-0B6D-477A-92B8-47F4156FBA49@windriver.com> Message-ID: Last call for any Forum Topics ... If you want to suggest any topics for consideration, you’ll need to update the etherpad by end-of-day today (Sept.24). https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming With the help of a few other StarlingX members, I’ll prioritize and submit abstracts for the top Forum topics that have been brainstormed by the StarlingX community ... required by Sept.26 . Thanks for your suggestions so far, Greg. From: Greg Waines Date: Thursday, September 6, 2018 at 10:27 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Requesting suggestions for Berlin / Stein OpenStack Summit Forum topics from StarlingX Team I am gathering potential Topics for ‘Forum’ sessions at the Berlin / Stein OpenStack Summit, from the StarlingX Team. If you are not familiar with ‘Forum’ sessions at the Summit, see end of email. I have done some initial brainstorming with the StarlingX Architecture Team to start things off. See the following etherpad: https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming Please either email me directly or update the etherpad at bottom (with your name/email) with any ‘Forum’ –type topics that you would like to see considered for the Berlin / Stein OpenStack Summit. Greg. p.s. If you're not familiar with the Forum, the quick summary is a collaboration between various teams to help identify problems, ideas, and needs for future development. It's comprised of rooms set up in fishbowl/conversational style, unlike the formal presentations of the OpenStack Summit. It's been instrumental in helping OpenStack developers set the course for the coming development cycle, and we hope it's a format that will work well for StarlingX as well. Examples of typical sessions that make for a great Forum: · Strategic, whole-of-community discussions, to think about the big picture, including beyond just one release cycle and new technologies o eg Making OpenStack One Platform for containers/VMs/Bare Metal (Strategic session) the entire community congregates to share opinions on how to make OpenStack achieve its integration engine goal · Cross-project sessions, in a similar vein to what has happened at past forums, but with increased emphasis on issues that are of relevant to all areas of the community o eg Rolling Upgrades at Scale (Cross-Project session) – the Large Deployments Team collaborates with Nova, Cinder and Keystone to tackle issues that come up with rolling upgrades when there’s a large number of machines. · Project-specific sessions, where community members most interested in a specific project can discuss their experience with the project over the last release and provide feedback, collaborate on priorities, and present or generate 'blue sky' ideas for the next release o eg Neutron Pain Points (Project-Specific session) – Co-organized by neutron developers and users. Neutron developers bring some specific questions about implementation and usage. Neutron users bring feedback from the latest release. All community members interested in Neutron discuss ideas about the future. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Mon Sep 24 14:53:12 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Mon, 24 Sep 2018 14:53:12 +0000 Subject: [Starlingx-discuss] [MutliOS] New wiki page & RFC Clear Linux demo high level plan In-Reply-To: <9A85D2917C58154C960D95352B22818BAB592012@fmsmsx115.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB592012@fmsmsx115.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB27E132@ALA-MBD.corp.ad.wrs.com> Bruce, When is the first sub-project meeting ? Brent From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, September 20, 2018 5:11 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [MutliOS] New wiki page & RFC Clear Linux demo high level plan As most of you know, the Intel team has been asked to implement a pilot/POC showing StarlingX running in a very limited fashion using Clear Linux as the Host OS. There has been some internal work and planning for this. I'm going to start taking that work out into the open through the newly created Multi-OS sub-project wiki page [0]. Saul and I did some brainstorming this afternoon on a high level plan for the Clear Linux demo. It's documented on the wiki [1]. We are looking for feedback on that high level plan, especially from the people already working on this. brucej [0] https://wiki.openstack.org/wiki/StarlingX/MultiOS [1] https://wiki.openstack.org/wiki/StarlingX/MultiOS#Clear_Linux_high_level_plan -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Mon Sep 24 15:19:59 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Mon, 24 Sep 2018 10:19:59 -0500 Subject: [Starlingx-discuss] [Forum] Forum Topic Submission Period - Time Running out! Message-ID: <5BA9009F.6000405@openstack.org> Just a reminder that there is a little more than 60 hours left to submit your forum topics. Please make haste to the Forum submission tool: https://www.openstack.org/summit/berlin-2018/call-for-presentations Cheers, Jimmy > Jimmy McArthur > September 17, 2018 at 11:13 AM > Hello Everyone! > > The Forum Topic Submission session started September 12 and will run > through September 26th. Now is the time to wrangle the topics you > gathered during your Brainstorming Phase and start pushing forum > topics through. Don't rely only on a PTL to make the agenda... step on > up and place the items you consider important front and center. > > As you may have noticed on the Forum Wiki > (https://wiki.openstack.org/wiki/Forum), we're reusing the normal CFP > tool this year. We did our best to remove Summit specific language, > but if you notice something, just know that you are submitting to the > Forum. URL is here: > > https://www.openstack.org/summit/berlin-2018/call-for-presentations > > Looking forward to seeing everyone's submissions! > > If you have questions or concerns about the process, please don't > hesitate to reach out. > > Cheers, > Jimmy > > _______________________________________________ > Openstack-track-chairs mailing list > Openstack-track-chairs at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Sep 24 17:14:11 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 24 Sep 2018 17:14:11 +0000 Subject: [Starlingx-discuss] [MutliOS] New wiki page & RFC Clear Linux demo high level plan In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB27E132@ALA-MBD.corp.ad.wrs.com> References: <9A85D2917C58154C960D95352B22818BAB592012@fmsmsx115.amr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB27E132@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5A3C1F@fmsmsx117.amr.corp.intel.com> We haven't set one yet, I'm working with Ildiko to find a time slot... brucej From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Monday, September 24, 2018 7:53 AM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [MutliOS] New wiki page & RFC Clear Linux demo high level plan Bruce, When is the first sub-project meeting ? Brent From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, September 20, 2018 5:11 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [MutliOS] New wiki page & RFC Clear Linux demo high level plan As most of you know, the Intel team has been asked to implement a pilot/POC showing StarlingX running in a very limited fashion using Clear Linux as the Host OS. There has been some internal work and planning for this. I'm going to start taking that work out into the open through the newly created Multi-OS sub-project wiki page [0]. Saul and I did some brainstorming this afternoon on a high level plan for the Clear Linux demo. It's documented on the wiki [1]. We are looking for feedback on that high level plan, especially from the people already working on this. brucej [0] https://wiki.openstack.org/wiki/StarlingX/MultiOS [1] https://wiki.openstack.org/wiki/StarlingX/MultiOS#Clear_Linux_high_level_plan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Mon Sep 24 17:46:09 2018 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 24 Sep 2018 17:46:09 +0000 Subject: [Starlingx-discuss] ABSTRACTS for Berlin / Stein OpenStack Summit Forum topics from StarlingX Team Message-ID: In parallel with waiting for any last minute Forum Topic suggestions from the StarlingX Team, I have written up ABSTRACTS for the TOP 3 picks on the etherpad ( https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming ). Please feel free to provide comments on the ABSTRACTS, Greg. From: Greg Waines Date: Monday, September 24, 2018 at 8:32 AM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Requesting suggestions for Berlin / Stein OpenStack Summit Forum topics from StarlingX Team Last call for any Forum Topics ... If you want to suggest any topics for consideration, you’ll need to update the etherpad by end-of-day today (Sept.24). https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming With the help of a few other StarlingX members, I’ll prioritize and submit abstracts for the top Forum topics that have been brainstormed by the StarlingX community ... required by Sept.26 . Thanks for your suggestions so far, Greg. From: Greg Waines Date: Thursday, September 6, 2018 at 10:27 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Requesting suggestions for Berlin / Stein OpenStack Summit Forum topics from StarlingX Team I am gathering potential Topics for ‘Forum’ sessions at the Berlin / Stein OpenStack Summit, from the StarlingX Team. If you are not familiar with ‘Forum’ sessions at the Summit, see end of email. I have done some initial brainstorming with the StarlingX Architecture Team to start things off. See the following etherpad: https://etherpad.openstack.org/p/StarlingXBerlinForumBrainstorming Please either email me directly or update the etherpad at bottom (with your name/email) with any ‘Forum’ –type topics that you would like to see considered for the Berlin / Stein OpenStack Summit. Greg. p.s. If you're not familiar with the Forum, the quick summary is a collaboration between various teams to help identify problems, ideas, and needs for future development. It's comprised of rooms set up in fishbowl/conversational style, unlike the formal presentations of the OpenStack Summit. It's been instrumental in helping OpenStack developers set the course for the coming development cycle, and we hope it's a format that will work well for StarlingX as well. Examples of typical sessions that make for a great Forum: · Strategic, whole-of-community discussions, to think about the big picture, including beyond just one release cycle and new technologies o eg Making OpenStack One Platform for containers/VMs/Bare Metal (Strategic session) the entire community congregates to share opinions on how to make OpenStack achieve its integration engine goal · Cross-project sessions, in a similar vein to what has happened at past forums, but with increased emphasis on issues that are of relevant to all areas of the community o eg Rolling Upgrades at Scale (Cross-Project session) – the Large Deployments Team collaborates with Nova, Cinder and Keystone to tackle issues that come up with rolling upgrades when there’s a large number of machines. · Project-specific sessions, where community members most interested in a specific project can discuss their experience with the project over the last release and provide feedback, collaborate on priorities, and present or generate 'blue sky' ideas for the next release o eg Neutron Pain Points (Project-Specific session) – Co-organized by neutron developers and users. Neutron developers bring some specific questions about implementation and usage. Neutron users bring feedback from the latest release. All community members interested in Neutron discuss ideas about the future. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Sep 24 21:42:59 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 24 Sep 2018 21:42:59 +0000 Subject: [Starlingx-discuss] stx.2018.10 Status Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4564B9@ALA-MBD.corp.ad.wrs.com> Hello all, The code freeze for the StarlingX October release is scheduled for Wednesday Sept 26. During the community meeting on Wednesday 10am ET, we will have a final review of the status and a go/no-go call for the code freeze. Summary: There are 15 stories in Story Board and 13 bugs in Launchpad tagged against the release. See below for more details. Logistics: All features/enhancements need to be submitted for the code freeze. Bug fixes will continue to go in until the Once the code freeze is in effect, there will be no submissions to master until the release branch is created. Once the release branch is created, all bugs tagged for stx.2018.10 need to be submitted in master first and cherry-picked to the release branch. Story Board: 2003396/2003339: [Feature] Upgrade libvirt & libvirt-python to 4.7.0 Code is ready. Working through reviews and waiting for branch merge instructions 2003715: Move StarlingX OCF scripts out of stx-openstack-ras repo In progress. Expect status update Tuesday morning 2003115: [stx-cinder / stx-python-cinderclient] Remove proprietary cinder volume backup and restore Code ready to merge, but is dependent on 2003715. 2003087: [Feature] Generalized Interface and Network Configuration Code merged. Testing in progress and issues are reported in Launchpad. Will close. 2002985: [Bug] Backup and Restore: failed to create multiple cinder backups in parallel Covered by 2003115. See status above. 2002946: [Enhancement] OVS LLDP inventory Gerrit review in progress. Some follow-up required. Expect status update tomorrow to determine if this will make it before the code freeze. 2002835: [Feature][Build] StarlingX Build Optimization Code merged. The remaining item is the wiki; not gated by the code freeze 2002813: [Doc] Create initial template for documentation Several tasks under review. Will get an update on Wednesday 2002712: [Doc] Provide StarlingX API documentation Several tasks under review. Will get an update on Wednesday 2002708: [Doc]: Define/Document the initial documentation infrastructure, style and publishing process Several tasks under review. Will get an update on Wednesday 2002707: [Doc] Document the StarlingX CI/CD environment Not gated by code freeze; content goes on the wiki 2002706: [Doc] Document the basic project planning process and tooling Not gated by code freeze; content goes on the wiki 2002738: [Doc] Define and document the feature development process Not gated by code freeze; content goes on the wiki 2002700: [Doc] STX - Getting Started Not gated by code freeze; content goes on the wiki Launchpad: Tagged for stx.2018.10: 13 https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 All are assigned with the exception of one build issue: https://bugs.launchpad.net/starlingx/+bug/1792001 (Action: Cesar to follow up) Needs Triage: 1 https://bugs.launchpad.net/starlingx/+bug/1790514 (Hayde following up with the reporter) Regards, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Mon Sep 24 22:23:30 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 24 Sep 2018 17:23:30 -0500 Subject: [Starlingx-discuss] stx.2018.10 Status In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4564B9@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA4564B9@ALA-MBD.corp.ad.wrs.com> Message-ID: On Mon, Sep 24, 2018 at 4:42 PM, Khalil, Ghada wrote: > The code freeze for the StarlingX October release is scheduled for Wednesday > Sept 26. During the community meeting on Wednesday 10am ET, we will have a > final review of the status and a go/no-go call for the code freeze. I would add that the Zuul pipelines have been running slowly the last week or so, partially due to a reduction in capacity from some of our cloud providers. We are waiting for test nodes up to 5+ hours today in the check pipeline. Things are running slower than usual so we will need to account for that in setting the actual freeze time. [...] > Once the code freeze is in effect, there will be no submissions to master > until the release branch is created. The requirement here is no merges until after the branches. We can continue to submit to Gerrit, and trust the core reviewers to not +W anything. That way the regular back-and-forth of the review process can continue. dt -- Dean Troyer dtroyer at gmail.com From david.a.cobbley at intel.com Mon Sep 24 22:34:57 2018 From: david.a.cobbley at intel.com (Cobbley, David A) Date: Mon, 24 Sep 2018 22:34:57 +0000 Subject: [Starlingx-discuss] stx.2018.10 Status In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA4564B9@ALA-MBD.corp.ad.wrs.com> Message-ID: <2D61419E-BA3A-4194-9F6F-22F17DE01CCA@intel.com> Great clarification, Dean; we do want the review process to continue orthogonal to the release, even if merges are stopped. -- David C On 9/24/18, 5:23 PM, "Dean Troyer" wrote: On Mon, Sep 24, 2018 at 4:42 PM, Khalil, Ghada wrote: > The code freeze for the StarlingX October release is scheduled for Wednesday > Sept 26. During the community meeting on Wednesday 10am ET, we will have a > final review of the status and a go/no-go call for the code freeze. I would add that the Zuul pipelines have been running slowly the last week or so, partially due to a reduction in capacity from some of our cloud providers. We are waiting for test nodes up to 5+ hours today in the check pipeline. Things are running slower than usual so we will need to account for that in setting the actual freeze time. [...] > Once the code freeze is in effect, there will be no submissions to master > until the release branch is created. The requirement here is no merges until after the branches. We can continue to submit to Gerrit, and trust the core reviewers to not +W anything. That way the regular back-and-forth of the review process can continue. dt -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From abraham.arce.moreno at intel.com Tue Sep 25 01:39:50 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 25 Sep 2018 01:39:50 +0000 Subject: [Starlingx-discuss] stx.2018.10 Status In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4564B9@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA4564B9@ALA-MBD.corp.ad.wrs.com> Message-ID: > The code freeze for the StarlingX October release is scheduled for > Wednesday Sept 26. During the community meeting on Wednesday 10am ET, > we will have a final review of the status and a go/no-go call for the code > freeze. >From Documentation side, find in [0] the today's update on the documentation [docs / releasenotes / api-ref] for our StarlingX repos. > 2002813: [Doc] Create initial template for documentation > Several tasks under review. Will get an update on Wednesday See [1] Documentation Tracking for the individual updates and links to stories and reviews. See [2] Release Tracking for the individual updates and links to stories and reviews. > 2002712: [Doc] Provide StarlingX API documentation > Several tasks under review. Will get an update on Wednesday See [3] API Reference Tracking for the individual update and links to stories and reviews. > 2002708: [Doc]: Define/Document the initial documentation infrastructure, > style and publishing process > Several tasks under review. Will get an update on Wednesday See [4] ? [0] https://ethercalc.openstack.org/sifnpbvze9lb [1] https://wiki.openstack.org/wiki/StarlingX/Documentation#Tracking [2] https://wiki.openstack.org/wiki/StarlingX/Releases/Release_Notes#Tracking [3] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide/API_Documentation#Tracking [4] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-September/001167.html From cindy.xie at intel.com Tue Sep 25 03:47:18 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 25 Sep 2018 03:47:18 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 9/26 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B37FF50@SHSMSX104.ccr.corp.intel.com> Agenda for 9/26 meeting: - Review the "Team Objective / Priorities" again due to multi-OS sub-project team created (Cindy/Brent/Saul) - Libvirt/qemu upgrade status (Ghada/Jim)  - non-OpenStack patch analysis status (Saul/Zhipeng) - Ceph upgrade status (Vivian/Dehao) - Opens (all) @ to those who has agenda items on the list, please attend; others, you're welcome to attend. Also welcome to bring any open topics to the agenda. Thx. - cindy -----Original Appointment----- From: Xie, Cindy Sent: Friday, August 24, 2018 9:38 AM To: Xie, Cindy; Khalil, Ghada; Wold, Saul; Rowsell, Brent; Sun, Austin; Wang, Yi C; Lin, Shuicheng; Chen, Yan; Somerville, Jim; 'Ildiko Vancsa'; starlingx-discuss at lists.starlingx.io Cc: Perez Rodriguez, Humberto I; Hu, Yong; Zhu, Vivian; 'Chen, Jacky'; 'Leo Xu'; 'Waines, Greg'; 'Eslimi, Dariush'; 'Komiyama, Takeo'; Martinez Monroy, Elio; Jones, Bruce E; Hernandez Gonzalez, Fernando; Hu, Wei W; Qi, Mingyuan; 'Young, Ken'; Arce Moreno, Abraham; 'Seiler, Glenn'; Gomez, Juan P; Shang, Dehao Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, September 26, 2018 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM EDT (9PM China time) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other From xiaoyan.li at intel.com Tue Sep 25 08:22:48 2018 From: xiaoyan.li at intel.com (Li, Xiaoyan) Date: Tue, 25 Sep 2018 08:22:48 +0000 Subject: [Starlingx-discuss] Ceph upgrading and rebasing Message-ID: Hi, We are going to upgrade Ceph to 13.2.0. We need to rebase the updated commits in StarlingX on Ceph 13.2.0. We have concerns about the folder wrs. Why do we have this folder? What does it do? 1. Why need to have *.service? Seems Ceph has provided such functions. 2. Ceph.conf: What is this config for? 3. Ceph_pmon_wrapper.sh: where will this script be used? 4. osd-wait-status.py: where does the script be used? And also there are lots of changes related to ceph.spec. Any change explanation/history about these changes? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Sep 25 09:24:04 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 25 Sep 2018 11:24:04 +0200 Subject: [Starlingx-discuss] PTG summary on edge discussions Message-ID: <6C68741E-E116-445A-A492-0C6A2BDE83C5@gmail.com> Hi, Hereby I would like to give you a short summary on the discussions that happened at the PTG in the area of edge. The Edge Computing Group sessions took place on Tuesday where our main activity was to draw an overall architecture diagram to capture the basic setup and requirements of edge towards a set of OpenStack services. Our main and initial focus was around Keystone and Glance, but discussion with other project teams such as Nova, Ironic and Cinder also happened later during the week. The edge architecture diagrams we drew are part of a so called Minimum Viable Product (MVP) which refers to the minimalist nature of the setup where we didn’t try to cover all aspects but rather define a minimum set of services and requirements to get to a functional system. This architecture will evolve further as we collect more use cases and requirements. To describe edge use cases on a higher level with Mobile Edge as a use case in the background we identified three main building blocks: * Main or Regional Datacenter (DC) * Edge Sites * Far Edge Sites or Cloudlets We examined the architecture diagram with the following user stories in mind: * As a deployer of OpenStack I want to minimize the number of control planes I need to manage across a large geographical region. * As a user of OpenStack I expect instance autoscale continues to function in an edge site if connectivity is lost to the main datacenter. * As a deployer of OpenStack I want disk images to be pulled to a cluster on demand, without needing to sync every disk image everywhere. * As a user of OpenStack I want to manage all of my instances in a region (from regional DC to far edge cloudlets) via a single API endpoint. We concluded to talk about service requirements in two major categories: 1. The Edge sites are fully operational in case of a connection loss between the Regional DC and the Edge site which requires control plane services running on the Edge site 2. Having full control on the Edge site is not critical in case a connection loss between the Regional DC and an Edge site which can be satisfied by having the control plane services running only in the Regional DC In the first case the orchestration of the services becomes harder and is not necessarily solved yet, while in the second case you have centralized control but losing functionality on the Edge sites in the event of a connection loss. We did not discuss things such as HA at the PTG and we did not go into details on networking during the architectural discussion either. We agreed to prefer federation for Keystone and came up with two work items to cover missing functionality: * Keystone to trust a token from an ID Provider master and when the auth method is called, perform an idempotent creation of the user, project and role assignments according to the assertions made in the token * Keystone should support the creation of users and projects with predictable UUIDs (eg.: hash of the name of the users and projects). This greatly simplifies Image federation and telemetry gathering For Glance we explored image caching and spent some time discussing the option to also cache metadata so a user can boot new instances at the edge in case of a network connection loss which would result in being disconnected from the registry: * I as a user of Glance, want to upload an image in the main datacenter and boot that image in an edge datacenter. Fetch the image to the edge datacenter with its metadata We are still in the progress of documenting the discussions and draw the architecture diagrams and flows for Keystone and Glance. In addition to the above we went through Dublin PTG wiki (https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG) capturing requirements: * we agreed to consider the list of requirements on the wiki finalized for now * agreed to move there the additional requirements listed on the Use Cases (https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases) wiki page For the details on the discussions with related OpenStack projects you can check the following etherpads for notes: * Cinder: https://etherpad.openstack.org/p/cinder-ptg-planning-denver-9-2018 * Glance: https://etherpad.openstack.org/p/glance-stein-edge-architecture * Ironic: https://etherpad.openstack.org/p/ironic-stein-ptg-edge * Keystone: https://etherpad.openstack.org/p/keystone-stein-edge-architecture * Neutron: https://etherpad.openstack.org/p/neutron-stein-ptg * Nova: https://etherpad.openstack.org/p/nova-ptg-stein Notes from the StarlingX sessions: https://etherpad.openstack.org/p/stx-PTG-agenda We are still working on the MVP architecture to clean it up and discuss comments and questions before moving it to a wiki page. Please let me know if you would like to get access to the document and I will share it with you. Please let me know if you have any questions or comments to the above captured items. Thanks and Best Regards, Ildikó (IRC: ildikov) From Ovidiu.Poncea at windriver.com Tue Sep 25 10:03:31 2018 From: Ovidiu.Poncea at windriver.com (Poncea, Ovidiu) Date: Tue, 25 Sep 2018 10:03:31 +0000 Subject: [Starlingx-discuss] Ceph upgrading and rebasing In-Reply-To: References: Message-ID: <4C60D9C5C8176C47874FFF36647AA19E9D5C6FCF@ALA-MBD.corp.ad.wrs.com> Hi Lisa, See inline. Ovidiu ________________________________ From: Li, Xiaoyan [xiaoyan.li at intel.com] Sent: Tuesday, September 25, 2018 11:22 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Ceph upgrading and rebasing Hi, We are going to upgrade Ceph to 13.2.0. We need to rebase the updated commits in StarlingX on Ceph 13.2.0. We have concerns about the folder wrs. Why do we have this folder? What does it do? [Ovi] Custom config files needed by stx used by the spec. 1. Why need to have *.service? Seems Ceph has provided such functions. [Ovi] Before systemd, titanium had init scripts which we still use. This was our wrapper to make them work with systemd. Since then ceph added its own, it may be worth to get rid of it and update to the pne in ceph. 2. Ceph.conf: What is this config for? [Ovi] To my knowledge this is the default ceph.conf file used when ceph is enabled. Other config options are appended by puppet to this default (e.g. osd's, mons etc.). 3. Ceph_pmon_wrapper.sh: where will this script be used? [Ovi] This is used by pmon (ceph is pmon mananged) to check the state of ceph services, restart them if they fail or hang. See inside ceph.conf.pmon. The ceph_pmon_wrapper.sh is also related to changes in init-ceph.in (see "WRS: Check if a ceph process is hung" section). 4. osd-wait-status.py: where does the script be used? [Ovi] It's no longer used, it should be removed (we used it in the past to wait for OSDs to shutdown before marking a host as "locked" - now mtc+pmon takes cares of it correctly). References to it should also be removed from init-ceph.in. And also there are lots of changes related to ceph.spec. Any change explanation/history about these changes? [Ovi] Ask Dean Troyer, he did the original push and should have access to the previous commits. Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ovidiu.Poncea at windriver.com Tue Sep 25 15:15:07 2018 From: Ovidiu.Poncea at windriver.com (Poncea, Ovidiu) Date: Tue, 25 Sep 2018 15:15:07 +0000 Subject: [Starlingx-discuss] Ceph upgrading and rebasing In-Reply-To: <4C60D9C5C8176C47874FFF36647AA19E9D5C6FCF@ALA-MBD.corp.ad.wrs.com> References: , <4C60D9C5C8176C47874FFF36647AA19E9D5C6FCF@ALA-MBD.corp.ad.wrs.com> Message-ID: <4C60D9C5C8176C47874FFF36647AA19E9D5C7082@ALA-MBD.corp.ad.wrs.com> Btw, for what's worth, there is also a ceph.sh in the wrs folder. This file is used by mtc to enable / disable services when a host goes availabel. It is deployed by the rpm in /etc/services.d/ (see spec). When a host is locked/going enabled mtc iterates through all the scripts in /etc/services.d/$host_type where host_type is one in [controller, compute, storage] and executes these scripts with 'start' or 'stop' parameter. This is stx specific, it has nothing to do with systemd. For ceph it also hides its status from pmon view. Regards, Ovidiu ________________________________ From: Poncea, Ovidiu [Ovidiu.Poncea at windriver.com] Sent: Tuesday, September 25, 2018 1:03 PM To: Li, Xiaoyan; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Ceph upgrading and rebasing Hi Lisa, See inline. Ovidiu ________________________________ From: Li, Xiaoyan [xiaoyan.li at intel.com] Sent: Tuesday, September 25, 2018 11:22 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Ceph upgrading and rebasing Hi, We are going to upgrade Ceph to 13.2.0. We need to rebase the updated commits in StarlingX on Ceph 13.2.0. We have concerns about the folder wrs. Why do we have this folder? What does it do? [Ovi] Custom config files needed by stx used by the spec. 1. Why need to have *.service? Seems Ceph has provided such functions. [Ovi] Before systemd, titanium had init scripts which we still use. This was our wrapper to make them work with systemd. Since then ceph added its own, it may be worth to get rid of it and update to the pne in ceph. 2. Ceph.conf: What is this config for? [Ovi] To my knowledge this is the default ceph.conf file used when ceph is enabled. Other config options are appended by puppet to this default (e.g. osd's, mons etc.). 3. Ceph_pmon_wrapper.sh: where will this script be used? [Ovi] This is used by pmon (ceph is pmon mananged) to check the state of ceph services, restart them if they fail or hang. See inside ceph.conf.pmon. The ceph_pmon_wrapper.sh is also related to changes in init-ceph.in (see "WRS: Check if a ceph process is hung" section). 4. osd-wait-status.py: where does the script be used? [Ovi] It's no longer used, it should be removed (we used it in the past to wait for OSDs to shutdown before marking a host as "locked" - now mtc+pmon takes cares of it correctly). References to it should also be removed from init-ceph.in. And also there are lots of changes related to ceph.spec. Any change explanation/history about these changes? [Ovi] Ask Dean Troyer, he did the original push and should have access to the previous commits. Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.thebeau at windriver.com Tue Sep 25 17:22:12 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Tue, 25 Sep 2018 13:22:12 -0400 Subject: [Starlingx-discuss] console/ssh login banner revert to default Message-ID: Hi, I was wondering if anyone had noticed and knew why the login banner for console and ssh had reverted to the default value for centos-release rpm.  But, from what I can tell we still have the modifications of the spec file for centos-release package which replace the default with a more wordy "WARNING WARNING... THIS IS A PRIVATE COMPUTER SYSTEM... etc".  That is, despite the meta-patches for the spec file, the built bindary rpm for centos-release package has the default text. I found that the reversion happened between 2018-09-19 and 2018-09-20, but I haven't spotted the cause.  Could that be related to CentOS7.5 rebase? I first noticed yesterday when I checked build 2018-09-23. M From aragorn at intel.com Tue Sep 25 18:08:02 2018 From: aragorn at intel.com (aragorn at intel.com) Date: 25 Sep 2018 11:08:02 -0700 Subject: [Starlingx-discuss] Automated Notification for: [mirror-downloader][#98] Missing packages - Results report Message-ID: [mirror-downloader][#98] Missing packages. Results report: - Missing: logs/L1_srpms_missing_centos.log lshell-0.9.16-5.el7.src.rpm - Missing GPG key: ./output/stx-r1/CentOS/pike/Source/libvirt-python-3.5.0-1.fc24.src.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#596bea5d) From sgw at linux.intel.com Tue Sep 25 18:41:20 2018 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 25 Sep 2018 11:41:20 -0700 Subject: [Starlingx-discuss] [build] Pending Gerrit PR that need review from Cores Message-ID: <3f124c34-dbef-2e9c-41d8-a40b5d4dfc59@linux.intel.com> Folks, There are some pending reviews in many of the repos that reviewed and possibly merged before the code freeze tomorrow. Can you all please take a few minutes to review the incoming reviews, we all probably have different views and dashboards, so I am not sure what the best dashboard URL would be. I guess folks should start with: https://review.openstack.org/#/dashboard/self Dean provided me with this more complex search: https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Fstx-clients+OR+project%3Aopenstack%2Fstx-config+OR+project%3Aopenstack%2Fstx-fault+OR+project%3Aopenstack%2Fstx-gplv2+OR+project%3Aopenstack%2Fstx-gplv3+OR+project%3Aopenstack%2Fstx-gui+OR+project%3Aopenstack%2Fstx-ha+OR+project%3Aopenstack%2Fstx-integ+OR+project%3Aopenstack%2Fstx-manifest+OR+project%3Aopenstack%2Fstx-metal+OR+project%3Aopenstack%2Fstx-nfv+OR+project%3Aopenstack%2Fstx-root+OR+project%3Aopenstack%2Fstx-tis-repo+OR+project%3Aopenstack%2Fstx-tools+OR+project%3Aopenstack%2Fstx-update+OR+project%3Aopenstack%2Fstx-upstream+OR+project%3Aopenstack%2Fstx-utils%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Czuul+NOT+reviewedby%3Aself&title=StarlingX+Review+Inbox&Needs+final+%2B2=label%3ACode-Review%3E%3D2+limit%3A50+NOT+label%3ACode-Review%3C%3D-1%2Cself&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D-1+NOT+label%3ACode-Review%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven't+voted+in+the+current+revision=NOT+label%3ACode-Review%3C%3D-1%2Cself+NOT+label%3ACode-Review%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2d Thanks Sau! From bruce.e.jones at intel.com Tue Sep 25 19:25:15 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 25 Sep 2018 19:25:15 +0000 Subject: [Starlingx-discuss] [build] Pending Gerrit PR that need review from Cores In-Reply-To: <3f124c34-dbef-2e9c-41d8-a40b5d4dfc59@linux.intel.com> References: <3f124c34-dbef-2e9c-41d8-a40b5d4dfc59@linux.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5A5E3E@fmsmsx117.amr.corp.intel.com> The big query below now has a link on the Wiki - it's in the Code section called "StarlingX Gerrit Review Dashboard by Status". There are a lot of pending reviews. It's a day before our code freeze. If any of that code needs to hit the release, it needs to be reviewed and approved asap. brucej -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, September 25, 2018 11:41 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build] Pending Gerrit PR that need review from Cores Folks, There are some pending reviews in many of the repos that reviewed and possibly merged before the code freeze tomorrow. Can you all please take a few minutes to review the incoming reviews, we all probably have different views and dashboards, so I am not sure what the best dashboard URL would be. I guess folks should start with: https://review.openstack.org/#/dashboard/self Dean provided me with this more complex search: https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Fstx-clients+OR+project%3Aopenstack%2Fstx-config+OR+project%3Aopenstack%2Fstx-fault+OR+project%3Aopenstack%2Fstx-gplv2+OR+project%3Aopenstack%2Fstx-gplv3+OR+project%3Aopenstack%2Fstx-gui+OR+project%3Aopenstack%2Fstx-ha+OR+project%3Aopenstack%2Fstx-integ+OR+project%3Aopenstack%2Fstx-manifest+OR+project%3Aopenstack%2Fstx-metal+OR+project%3Aopenstack%2Fstx-nfv+OR+project%3Aopenstack%2Fstx-root+OR+project%3Aopenstack%2Fstx-tis-repo+OR+project%3Aopenstack%2Fstx-tools+OR+project%3Aopenstack%2Fstx-update+OR+project%3Aopenstack%2Fstx-upstream+OR+project%3Aopenstack%2Fstx-utils%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Czuul+NOT+reviewedby%3Aself&title=StarlingX+Review+Inbox&Needs+final+%2B2=label%3ACode-Review%3E%3D2+limit%3A50+NOT+label%3ACode-Review%3C%3D-1%2Cself&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D-1+NOT+label%3ACode-Review%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven't+voted+in+the+current+revision=NOT+label%3ACode-Review%3C%3D-1%2Cself+NOT+label%3ACode-Review%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2d Thanks Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Tue Sep 25 19:30:11 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 25 Sep 2018 19:30:11 +0000 Subject: [Starlingx-discuss] [build] Pending Gerrit PR that need review from Cores In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5A5E3E@fmsmsx117.amr.corp.intel.com> References: <3f124c34-dbef-2e9c-41d8-a40b5d4dfc59@linux.intel.com> <9A85D2917C58154C960D95352B22818BAB5A5E3E@fmsmsx117.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA456ABA@ALA-MBD.corp.ad.wrs.com> Just to clarify, not all these reviews are required for the code freeze. Items required for the code freeze will have a story or bug with the "stx.2018.10" tag. -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, September 25, 2018 3:25 PM To: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build] Pending Gerrit PR that need review from Cores The big query below now has a link on the Wiki - it's in the Code section called "StarlingX Gerrit Review Dashboard by Status". There are a lot of pending reviews. It's a day before our code freeze. If any of that code needs to hit the release, it needs to be reviewed and approved asap. brucej -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, September 25, 2018 11:41 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build] Pending Gerrit PR that need review from Cores Folks, There are some pending reviews in many of the repos that reviewed and possibly merged before the code freeze tomorrow. Can you all please take a few minutes to review the incoming reviews, we all probably have different views and dashboards, so I am not sure what the best dashboard URL would be. I guess folks should start with: https://review.openstack.org/#/dashboard/self Dean provided me with this more complex search: https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Fstx-clients+OR+project%3Aopenstack%2Fstx-config+OR+project%3Aopenstack%2Fstx-fault+OR+project%3Aopenstack%2Fstx-gplv2+OR+project%3Aopenstack%2Fstx-gplv3+OR+project%3Aopenstack%2Fstx-gui+OR+project%3Aopenstack%2Fstx-ha+OR+project%3Aopenstack%2Fstx-integ+OR+project%3Aopenstack%2Fstx-manifest+OR+project%3Aopenstack%2Fstx-metal+OR+project%3Aopenstack%2Fstx-nfv+OR+project%3Aopenstack%2Fstx-root+OR+project%3Aopenstack%2Fstx-tis-repo+OR+project%3Aopenstack%2Fstx-tools+OR+project%3Aopenstack%2Fstx-update+OR+project%3Aopenstack%2Fstx-upstream+OR+project%3Aopenstack%2Fstx-utils%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D-1+label%3AVerified%3E%3D1%2Czuul+NOT+reviewedby%3Aself&title=StarlingX+Review+Inbox&Needs+final+%2B2=label%3ACode-Review%3E%3D2+limit%3A50+NOT+label%3ACode-Review%3C%3D-1%2Cself&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode-Review%3E%3D2+NOT+label%3ACode-Review%3C%3D-1%2Cstarlingx-core+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode-Review%3C%3D-1+NOT+label%3ACode-Review%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven't+voted+in+the+current+revision=NOT+label%3ACode-Review%3C%3D-1%2Cself+NOT+label%3ACode-Review%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2d Thanks Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Tue Sep 25 19:34:21 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 25 Sep 2018 14:34:21 -0500 Subject: [Starlingx-discuss] [build] Pending Gerrit PR that need review from Cores In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA456ABA@ALA-MBD.corp.ad.wrs.com> References: <3f124c34-dbef-2e9c-41d8-a40b5d4dfc59@linux.intel.com> <9A85D2917C58154C960D95352B22818BAB5A5E3E@fmsmsx117.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA456ABA@ALA-MBD.corp.ad.wrs.com> Message-ID: On Tue, Sep 25, 2018 at 2:30 PM, Khalil, Ghada wrote: > Just to clarify, not all these reviews are required for the code freeze. > Items required for the code freeze will have a story or bug with the "stx.2018.10" tag. One way to track these directly in Gerrit would be to set the review topic to that tag, then you can just query the tag to see the status... Also, don't forget that CI is still running with a deep backlog and at least 4 hours waiting to get test nodes in the check queue is still common; the gate queue has priority so isn't so bad. dt -- Dean Troyer dtroyer at gmail.com From Numan.Waheed at windriver.com Tue Sep 25 21:03:17 2018 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Tue, 25 Sep 2018 21:03:17 +0000 Subject: [Starlingx-discuss] [ Test ] stx.2018.10 test plan In-Reply-To: <4F6AACE4B0F173488D033B02A8BB5B7E716E81DD@fmsmsx104.amr.corp.intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E81DD@fmsmsx104.amr.corp.intel.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE481F95FD@ALA-MBD.corp.ad.wrs.com> Hi Ada, Thanks for sharing the test plan. Here are my comments: TC 14 - There is only one controller in Simplex. It cannot be swacted. I think the test cases is actually meant for Duplex system. TC 63 - will cover TC 58 and TC 59 TC 87 - I am assuming you have crypto device configured in your system TC 97, 98 - I am assuming you will test it on Direct Connect Duplex system TC 206, 207, 209, 209 - I am assuming you have BMC setup in your lab TC 231 to 236 - Suggest to pick fewer Time zone test cases to save time for other tests Suggestions: - I would suggest adding more success path scenarios instead of failure scenarios - I would suggest adding test cases for VM operations using different type of VMs - Please consider adding some CEPH related test cases - Backup and Restore for different type of configs - Heat test cases Regards, Numan. -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: September-21-18 7:54 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Test ] stx.2018.10 test plan Hello, I'm posting the test plan proposed for the October Release in the wiki [0]. We have 238 tests so far, mostly focus on the stx services. As we mentioned before, the tests will be run manually by our team for this release. The expectation is to increase the number of automated tests along time. We are considering to cover the four configurations (Simplex, Duplex, Multinode local storage, Multinode external storage) both on bare metal and virtual. However, we are experiencing setup problems with multinode bare metal and simplex. We are digging into it. We'll have more information next week. Please take a look at it and let us know what else must be included. Thanks Ada [0] https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cesar.lara at intel.com Tue Sep 25 21:15:14 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Tue, 25 Sep 2018 21:15:14 +0000 Subject: [Starlingx-discuss] [build][meetings] build meeting minutes 9/24/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB471051EA72@fmsmsx104.amr.corp.intel.com> Attendees: Saul, Hayde, Abe, Erich Ken, Marcela, Bruce, Cesar Agenda for 9/24/2018 - Installer- Ken - New proposal for mirror - general plan for next version of stxb - moved to next meeting - opens Meeting Notes - Documentation for installer completed and updated both in wiki and in the script's readme file, we are still having gaps on documentation on how often do we rebuild the installer package and what happens if we upgrade to new kernel or need to inject new drivers. AR is to take this to the community and take input about their needs - Question was raised about Aragorn emails in the mailing list about missing packages, not really sure about the actions needed when we do see an email about missing packages; the answer for this question is that Aragorn is an automated account that sends alerts of missing packages whenever we try to create a mirror from scratch, if those packages are missing we need to find new repositories or urls and update manifest files to get new sources for those packages at build time. - We are currently working with a Canadian incubator company called www.cengn.ca which seems willing to host StarlingX build artifacts and IOS images as a contribution to the project, the idea will be to host packages needed for our build and avoid hard to get packages, we should hear more about this and the next steps for us as build team. - We need to work on the next version of stxb tool, we will be working on requirements for next release. A proposal for an initial use case to be discussed with the team. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Tue Sep 25 21:16:46 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 25 Sep 2018 16:16:46 -0500 Subject: [Starlingx-discuss] Git tagging of upstream branches Message-ID: Background: Jim Somerville is working on a rebase of libvirt to 4.7.0 (we were on 3.5.0) with the stx-specific changes on top of a fresh upstream branch. Until now we have designated that the woking branch name for all activity is 'master'. For upstream forked repos this may not make sense going forward. We will have this problem with most it not all of them as we rebase on new upstream work. These repos were all newly constructed from upstream clones with the stx squash patch laid on top. With libvirt 4.7.0 Jim has done the same thing again (filtering the patches of course) but with individual patches instead of a single squash. (YAY!) What I am proposing we do is maintain multiple branches in these repos corresponding to the upstream branch as _our_ working master. Using this sort of scheme we can have multiple rebase-masters at once (in the above, pike and rocky for example), each release would correspond to only one of those, that relationship would not be encoded in the branch names, I think that is acceptable. So for the immediate libvirt situation: Upstream stable branch: v4.7.0 (this is a tag in the libvirt repo) StarlingX 'master': stx/v4.7.0 (sticking with the libvirt style for versions) Or OpenStack terms: Upstream stable branch: stable/pike StarlingX 'master' branch: stx/pike StarlingX release/stable branch: r/2018.10 Any thoughts on the approach? On the form of the branch names? FWIW, we have proposed the first iteration of this in the stx-libvirt repo [0]. dt [0] https://github.com/starlingx-staging/stx-libvirt/pull/1 -- Dean Troyer dtroyer at gmail.com From ada.cabrales at intel.com Tue Sep 25 21:22:30 2018 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 25 Sep 2018 21:22:30 +0000 Subject: [Starlingx-discuss] [ Test ] stx.2018.10 test plan In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE481F95FD@ALA-MBD.corp.ad.wrs.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E81DD@fmsmsx104.amr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE481F95FD@ALA-MBD.corp.ad.wrs.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E716F376B@FMSMSX108.amr.corp.intel.com> Thanks for taking the time for reviewing it, Numan! I'm still adding some test cases. I'll check your suggestions and adjust. Ada > -----Original Message----- > From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] > Sent: Tuesday, September 25, 2018 4:03 PM > To: Cabrales, Ada ; starlingx- > discuss at lists.starlingx.io > Subject: RE: [ Test ] stx.2018.10 test plan > > Hi Ada, > > Thanks for sharing the test plan. Here are my comments: > > TC 14 - There is only one controller in Simplex. It cannot be swacted. I think > the test cases is actually meant for Duplex system. > TC 63 - will cover TC 58 and TC 59 > TC 87 - I am assuming you have crypto device configured in your system TC > 97, 98 - I am assuming you will test it on Direct Connect Duplex system TC > 206, 207, 209, 209 - I am assuming you have BMC setup in your lab TC 231 to > 236 - Suggest to pick fewer Time zone test cases to save time for other tests > > Suggestions: > - I would suggest adding more success path scenarios instead of failure > scenarios > - I would suggest adding test cases for VM operations using different type of > VMs > - Please consider adding some CEPH related test cases > - Backup and Restore for different type of configs > - Heat test cases > > Regards, > > Numan. > > -----Original Message----- > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > Sent: September-21-18 7:54 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [ Test ] stx.2018.10 test plan > > Hello, > > I'm posting the test plan proposed for the October Release in the wiki [0]. > We have 238 tests so far, mostly focus on the stx services. As we mentioned > before, the tests will be run manually by our team for this release. The > expectation is to increase the number of automated tests along time. > > We are considering to cover the four configurations (Simplex, Duplex, > Multinode local storage, Multinode external storage) both on bare metal and > virtual. However, we are experiencing setup problems with multinode bare > metal and simplex. We are digging into it. We'll have more information next > week. > > Please take a look at it and let us know what else must be included. > > Thanks > Ada > > [0] https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Tue Sep 25 22:15:59 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 25 Sep 2018 22:15:59 +0000 Subject: [Starlingx-discuss] Git tagging of upstream branches In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BAB5A60CF@fmsmsx117.amr.corp.intel.com> This all makes sense to me. I'm assuming we did not do anything like this for the CentOS upgrades, or the in progress Ceph upgrade. Should we handle Ceph in the same way? And everything else going forward? brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Tuesday, September 25, 2018 2:17 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Git tagging of upstream branches Background: Jim Somerville is working on a rebase of libvirt to 4.7.0 (we were on 3.5.0) with the stx-specific changes on top of a fresh upstream branch. Until now we have designated that the woking branch name for all activity is 'master'. For upstream forked repos this may not make sense going forward. We will have this problem with most it not all of them as we rebase on new upstream work. These repos were all newly constructed from upstream clones with the stx squash patch laid on top. With libvirt 4.7.0 Jim has done the same thing again (filtering the patches of course) but with individual patches instead of a single squash. (YAY!) What I am proposing we do is maintain multiple branches in these repos corresponding to the upstream branch as _our_ working master. Using this sort of scheme we can have multiple rebase-masters at once (in the above, pike and rocky for example), each release would correspond to only one of those, that relationship would not be encoded in the branch names, I think that is acceptable. So for the immediate libvirt situation: Upstream stable branch: v4.7.0 (this is a tag in the libvirt repo) StarlingX 'master': stx/v4.7.0 (sticking with the libvirt style for versions) Or OpenStack terms: Upstream stable branch: stable/pike StarlingX 'master' branch: stx/pike StarlingX release/stable branch: r/2018.10 Any thoughts on the approach? On the form of the branch names? FWIW, we have proposed the first iteration of this in the stx-libvirt repo [0]. dt [0] https://github.com/starlingx-staging/stx-libvirt/pull/1 -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Tue Sep 25 22:35:36 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 25 Sep 2018 22:35:36 +0000 Subject: [Starlingx-discuss] Git tagging of upstream branches In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB283C1C@ALA-MBD.corp.ad.wrs.com> Sounds reasonable to me Brent -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Tuesday, September 25, 2018 5:17 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Git tagging of upstream branches Background: Jim Somerville is working on a rebase of libvirt to 4.7.0 (we were on 3.5.0) with the stx-specific changes on top of a fresh upstream branch. Until now we have designated that the woking branch name for all activity is 'master'. For upstream forked repos this may not make sense going forward. We will have this problem with most it not all of them as we rebase on new upstream work. These repos were all newly constructed from upstream clones with the stx squash patch laid on top. With libvirt 4.7.0 Jim has done the same thing again (filtering the patches of course) but with individual patches instead of a single squash. (YAY!) What I am proposing we do is maintain multiple branches in these repos corresponding to the upstream branch as _our_ working master. Using this sort of scheme we can have multiple rebase-masters at once (in the above, pike and rocky for example), each release would correspond to only one of those, that relationship would not be encoded in the branch names, I think that is acceptable. So for the immediate libvirt situation: Upstream stable branch: v4.7.0 (this is a tag in the libvirt repo) StarlingX 'master': stx/v4.7.0 (sticking with the libvirt style for versions) Or OpenStack terms: Upstream stable branch: stable/pike StarlingX 'master' branch: stx/pike StarlingX release/stable branch: r/2018.10 Any thoughts on the approach? On the form of the branch names? FWIW, we have proposed the first iteration of this in the stx-libvirt repo [0]. dt [0] https://github.com/starlingx-staging/stx-libvirt/pull/1 -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Tue Sep 25 22:37:29 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 25 Sep 2018 17:37:29 -0500 Subject: [Starlingx-discuss] Git tagging of upstream branches In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5A60CF@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB5A60CF@fmsmsx117.amr.corp.intel.com> Message-ID: On Tue, Sep 25, 2018 at 5:15 PM, Jones, Bruce E wrote: > This all makes sense to me. I'm assuming we did not do anything like this for the CentOS upgrades, or the in progress Ceph upgrade. Should we handle Ceph in the same way? And everything else going forward? I don't know where the Ceph upgrade work is being done, nothing has been proposed to the stx-sech repo. The CentOS upgrades are in the stx-* repos in Gerrit under the regular stuff, this is only for the staging repos that are direct forks of upstream. dt -- Dean Troyer dtroyer at gmail.com From dtroyer at gmail.com Tue Sep 25 22:38:09 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 25 Sep 2018 17:38:09 -0500 Subject: [Starlingx-discuss] Git tagging of upstream branches In-Reply-To: References: <9A85D2917C58154C960D95352B22818BAB5A60CF@fmsmsx117.amr.corp.intel.com> Message-ID: On Tue, Sep 25, 2018 at 5:37 PM, Dean Troyer wrote: > On Tue, Sep 25, 2018 at 5:15 PM, Jones, Bruce E wrote: >> This all makes sense to me. I'm assuming we did not do anything like this for the CentOS upgrades, or the in progress Ceph upgrade. Should we handle Ceph in the same way? And everything else going forward? > > I don't know where the Ceph upgrade work is being done, nothing has > been proposed to the stx-sech repo. Good grief, stx-ceph dt -- Dean Troyer dtroyer at gmail.com From Brent.Rowsell at windriver.com Tue Sep 25 23:15:36 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 25 Sep 2018 23:15:36 +0000 Subject: [Starlingx-discuss] Git tagging of upstream branches In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5A60CF@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB5A60CF@fmsmsx117.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB283E37@ALA-MBD.corp.ad.wrs.com> The same strategy should apply to the ceph upgrade. Brent -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, September 25, 2018 6:16 PM To: Dean Troyer ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Git tagging of upstream branches This all makes sense to me. I'm assuming we did not do anything like this for the CentOS upgrades, or the in progress Ceph upgrade. Should we handle Ceph in the same way? And everything else going forward? brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Tuesday, September 25, 2018 2:17 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Git tagging of upstream branches Background: Jim Somerville is working on a rebase of libvirt to 4.7.0 (we were on 3.5.0) with the stx-specific changes on top of a fresh upstream branch. Until now we have designated that the woking branch name for all activity is 'master'. For upstream forked repos this may not make sense going forward. We will have this problem with most it not all of them as we rebase on new upstream work. These repos were all newly constructed from upstream clones with the stx squash patch laid on top. With libvirt 4.7.0 Jim has done the same thing again (filtering the patches of course) but with individual patches instead of a single squash. (YAY!) What I am proposing we do is maintain multiple branches in these repos corresponding to the upstream branch as _our_ working master. Using this sort of scheme we can have multiple rebase-masters at once (in the above, pike and rocky for example), each release would correspond to only one of those, that relationship would not be encoded in the branch names, I think that is acceptable. So for the immediate libvirt situation: Upstream stable branch: v4.7.0 (this is a tag in the libvirt repo) StarlingX 'master': stx/v4.7.0 (sticking with the libvirt style for versions) Or OpenStack terms: Upstream stable branch: stable/pike StarlingX 'master' branch: stx/pike StarlingX release/stable branch: r/2018.10 Any thoughts on the approach? On the form of the branch names? FWIW, we have proposed the first iteration of this in the stx-libvirt repo [0]. dt [0] https://github.com/starlingx-staging/stx-libvirt/pull/1 -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Tue Sep 25 22:40:39 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 25 Sep 2018 22:40:39 +0000 Subject: [Starlingx-discuss] MultiOS sub-project weekly call Message-ID: <9A85D2917C58154C960D95352B22818BAB5A612D@fmsmsx117.amr.corp.intel.com> We are starting a weekly call for the Multi-OS sub-project. The call is every Monday 4PM Pacific time https://zoom.us/j/342730236. Project notes https://etherpad.openstack.org/p/stx-multios. The folks on the To: have previously volunteered to join the sub-project, but everyone is of course welcome to join the call. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Wed Sep 26 01:18:42 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 26 Sep 2018 01:18:42 +0000 Subject: [Starlingx-discuss] console/ssh login banner revert to default In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C76553829F2@SHSMSX101.ccr.corp.intel.com> Hi Michel, It is caused by centos-release src rpm upgrade. I have fixed it with below patch. Please help review it. Thanks. https://review.openstack.org/605285 Best Regards Shuicheng -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau at windriver.com] Sent: Wednesday, September 26, 2018 1:22 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] console/ssh login banner revert to default Hi, I was wondering if anyone had noticed and knew why the login banner for console and ssh had reverted to the default value for centos-release rpm.  But, from what I can tell we still have the modifications of the spec file for centos-release package which replace the default with a more wordy "WARNING WARNING... THIS IS A PRIVATE COMPUTER SYSTEM... etc".  That is, despite the meta-patches for the spec file, the built bindary rpm for centos-release package has the default text. I found that the reversion happened between 2018-09-19 and 2018-09-20, but I haven't spotted the cause.  Could that be related to CentOS7.5 rebase? I first noticed yesterday when I checked build 2018-09-23. M _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Wed Sep 26 13:11:57 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 26 Sep 2018 13:11:57 +0000 Subject: [Starlingx-discuss] console/ssh login banner revert to default In-Reply-To: <9700A18779F35F49AF027300A49E7C76553829F2@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76553829F2@SHSMSX101.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA456D26@ALA-MBD.corp.ad.wrs.com> Hi Shuicheng, Thanks for investigating. I've assigned you the Launchpad bug reporting this issue: https://bugs.launchpad.net/starlingx/+bug/1794329 Please add it to your commit message (if possible): Closes-Bug: 1794329 Regards, Ghada -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, September 25, 2018 9:19 PM To: Thebeau, Michel; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] console/ssh login banner revert to default Hi Michel, It is caused by centos-release src rpm upgrade. I have fixed it with below patch. Please help review it. Thanks. https://review.openstack.org/605285 Best Regards Shuicheng -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau at windriver.com] Sent: Wednesday, September 26, 2018 1:22 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] console/ssh login banner revert to default Hi, I was wondering if anyone had noticed and knew why the login banner for console and ssh had reverted to the default value for centos-release rpm.  But, from what I can tell we still have the modifications of the spec file for centos-release package which replace the default with a more wordy "WARNING WARNING... THIS IS A PRIVATE COMPUTER SYSTEM... etc".  That is, despite the meta-patches for the spec file, the built bindary rpm for centos-release package has the default text. I found that the reversion happened between 2018-09-19 and 2018-09-20, but I haven't spotted the cause.  Could that be related to CentOS7.5 rebase? I first noticed yesterday when I checked build 2018-09-23. M _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From shuicheng.lin at intel.com Wed Sep 26 13:21:37 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 26 Sep 2018 13:21:37 +0000 Subject: [Starlingx-discuss] console/ssh login banner revert to default In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA456D26@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C76553829F2@SHSMSX101.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA456D26@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C7655382BD2@SHSMSX101.ccr.corp.intel.com> Hi Ghada, I have updated commit message to point to the bug link. Thanks. Best Regards Shuicheng -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, September 26, 2018 9:12 PM To: Lin, Shuicheng ; Thebeau, Michel ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] console/ssh login banner revert to default Hi Shuicheng, Thanks for investigating. I've assigned you the Launchpad bug reporting this issue: https://bugs.launchpad.net/starlingx/+bug/1794329 Please add it to your commit message (if possible): Closes-Bug: 1794329 Regards, Ghada -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, September 25, 2018 9:19 PM To: Thebeau, Michel; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] console/ssh login banner revert to default Hi Michel, It is caused by centos-release src rpm upgrade. I have fixed it with below patch. Please help review it. Thanks. https://review.openstack.org/605285 Best Regards Shuicheng -----Original Message----- From: Michel Thebeau [mailto:michel.thebeau at windriver.com] Sent: Wednesday, September 26, 2018 1:22 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] console/ssh login banner revert to default Hi, I was wondering if anyone had noticed and knew why the login banner for console and ssh had reverted to the default value for centos-release rpm.  But, from what I can tell we still have the modifications of the spec file for centos-release package which replace the default with a more wordy "WARNING WARNING... THIS IS A PRIVATE COMPUTER SYSTEM... etc".  That is, despite the meta-patches for the spec file, the built bindary rpm for centos-release package has the default text. I found that the reversion happened between 2018-09-19 and 2018-09-20, but I haven't spotted the cause.  Could that be related to CentOS7.5 rebase? I first noticed yesterday when I checked build 2018-09-23. M _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Wed Sep 26 13:33:31 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 26 Sep 2018 13:33:31 +0000 Subject: [Starlingx-discuss] MInutes: Weekly StarlingX non-OpenStack Distr meeting, 9/26 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B38515A@SHSMSX104.ccr.corp.intel.com> Agenda & Notes for 9/26 meeting: - Review the "Team Objective / Priorities" again due to multi-OS sub-project team created (Cindy/Brent/Saul) team objective and priority page updated - Libvirt/qemu upgrade status (Ghada/Jim) no blocking issue, -1 blocked by workflow. 4 pending patches waiting for merge, expected to be in by end of today. Waiting for Dean to merge to stx-staging for the libvirt repo. qemu will not be in this 2018.10 release. - non-OpenStack patch analysis status (Saul/Zhipeng) 3 stories created to re-work on the sRPM: 2003768/2003770/2003803 for the patches that we marked "upstreamable", we are still analysing to see what actually can do for upstream. Need to make progress on multiple front. Saul is still reviewing the patches. Will have a new tech leader joining the team to join the effort. - Ceph upgrade status (Vivian/Dehao) scrub all the patches developed on Ceph10. In total, 36 commits in total. only 2 of them don't require rebase. Lisa dropped email to mailing list and clear about the next step. No open for rebase for now. Will update the progress after Chinese National Holiday. Feature branch needs to be created on staging as well. follow the same process as of Libvirt/qemu update. spec files only on Openstack CI. test for Ceph upgrade: once Ceph upgrade is done, will handle it to validation team. Ceph configuration needs to be added. WR can help again this time. AR for Cindy to check w/ Ada with the plan of Ceph config lab. Elio: we are working very hard to get this setup. Question: Elio, what is the difference btw Ceph config vs the controller storage config. - Opens (all) bug on CentOS 7.5 upgrade (1794329): patch uploaded: https://review.openstack.org/#/c/605285/ let's review and +2 on this patch and get it merged before code freeze. -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Tuesday, September 25, 2018 11:47 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 9/26 Agenda for 9/26 meeting: - Review the "Team Objective / Priorities" again due to multi-OS sub-project team created (Cindy/Brent/Saul) - Libvirt/qemu upgrade status (Ghada/Jim)  - non-OpenStack patch analysis status (Saul/Zhipeng) - Ceph upgrade status (Vivian/Dehao) - Opens (all) @ to those who has agenda items on the list, please attend; others, you're welcome to attend. Also welcome to bring any open topics to the agenda. Thx. - cindy -----Original Appointment----- From: Xie, Cindy Sent: Friday, August 24, 2018 9:38 AM To: Xie, Cindy; Khalil, Ghada; Wold, Saul; Rowsell, Brent; Sun, Austin; Wang, Yi C; Lin, Shuicheng; Chen, Yan; Somerville, Jim; 'Ildiko Vancsa'; starlingx-discuss at lists.starlingx.io Cc: Perez Rodriguez, Humberto I; Hu, Yong; Zhu, Vivian; 'Chen, Jacky'; 'Leo Xu'; 'Waines, Greg'; 'Eslimi, Dariush'; 'Komiyama, Takeo'; Martinez Monroy, Elio; Jones, Bruce E; Hernandez Gonzalez, Fernando; Hu, Wei W; Qi, Mingyuan; 'Young, Ken'; Arce Moreno, Abraham; 'Seiler, Glenn'; Gomez, Juan P; Shang, Dehao Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, September 26, 2018 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . Cadence and time slot: o Wednesday 9AM EDT (9PM China time) . Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ . Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Wed Sep 26 14:52:23 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 26 Sep 2018 14:52:23 +0000 Subject: [Starlingx-discuss] Notes from today's call Message-ID: <9A85D2917C58154C960D95352B22818BAB5A662D@fmsmsx117.amr.corp.intel.com> Agenda and Notes for the Sep 26th call * Code freeze! o Final deadline 12AM EST today! Complete your code reviews asap. o Build bug https://bugs.launchpad.net/starlingx/+bug/1794415 is release gating. * Containerized Services Update - Brent o Brent to set a separate call for the community * Mirror and builds for community - Ian o www.cengn.ca team will be joining the project and contributing hosted build artifacts & mirrors. Many thanks to Ian for making this happen! * If time remains: o Feedback on the Feature Dev process? Approval? ? https://wiki.openstack.org/wiki/StarlingX/Feature_Development_Process ? Please review and send feedback to the list o Release note content - include "vanilla" features e.g. simplex/duplex/multi-node? ? Base features are already covered in the introductory document ? Add links to such docs to the release notes. o Branches for rebases in the "forked" repos - Dean's email ? Dean to create branches for Ceph upgrade and document on the wiki -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Wed Sep 26 15:32:16 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 26 Sep 2018 15:32:16 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build Message-ID: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> Hi, This is the build issue mentioned in the meeting this morning https://bugs.launchpad.net/starlingx/+bug/1794415 <- full details are here. In summary what happens is that ceph cannot be build, the build.log for ceph says: BUILDSTDERR: aclocal: overwriting 'm4/ax_c_var_func.m4' with '/usr/share/aclocal/ax_c_var_func.m4' BUILDSTDERR: aclocal: overwriting 'm4/ax_check_compile_flag.m4' with '/usr/share/aclocal/ax_check_compile_flag.m4' BUILDSTDERR: aclocal: installing 'm4/ax_cxx_compile_stdcxx.m4' from '/usr/share/aclocal/ax_cxx_compile_stdcxx.m4' BUILDSTDERR: aclocal: overwriting 'm4/ax_cxx_compile_stdcxx_11.m4' with '/usr/share/aclocal/ax_cxx_compile_stdcxx_11.m4' BUILDSTDERR: aclocal: overwriting 'm4/ax_cxx_static_cast.m4' with '/usr/share/aclocal/ax_cxx_static_cast.m4' BUILDSTDERR: aclocal: overwriting 'm4/pkg.m4' with '/usr/share/aclocal/pkg.m4' BUILDSTDERR: aclocal: installing 'm4/ax_require_defined.m4' from '/usr/share/aclocal/ax_require_defined.m4' BUILDSTDERR: aclocal: error: too many loops BUILDSTDERR: aclocal: Please contact . BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) RPM build errors: Child return code was: 1 EXCEPTION: [Error()] However, I'm able to build ceph in mock and I don't see this problem there. We'll continue investigating -Erich From Ghada.Khalil at windriver.com Wed Sep 26 15:44:02 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 26 Sep 2018 15:44:02 +0000 Subject: [Starlingx-discuss] [Release] stx.2018.10 status & next steps Message-ID: <151EE31B9FCCA54397A757BC674650F0BA456F00@ALA-MBD.corp.ad.wrs.com> Hello all, This email captures the discussion related to the stx.2018.10 code freeze plan - discussed this morning at the StarlingX community meeting. The code freeze will be in effect as of today (September 26, 2018) at midnight Eastern Time / 9pm Pacific Time Gerrit reviews can continue, but we ask Core Reviewers NOT to Workflow+1 any commits after the cut-off above. Follow-up emails will be sent when merges can resume on master. Review Priorities/Workflow+1 until the code freeze: - Stories: - https://storyboard.openstack.org/#!/story/2003715 - https://storyboard.openstack.org/#!/story/2003396 - https://storyboard.openstack.org/#!/story/2003339 - https://storyboard.openstack.org/#!/story/2003115 - https://storyboard.openstack.org/#!/story/2002985 - https://storyboard.openstack.org/#!/story/2002946 (best effort) - Documentation Updates: https://review.openstack.org/#/q/status:open+branch:master+topic:documentation-baseline - Updating the release version to 18.10: https://storyboard.openstack.org/#!/story/2003085 - Key Bugs - https://bugs.launchpad.net/starlingx/+bug/1794415 (more info to be sent to mailing list) - https://bugs.launchpad.net/starlingx/+bug/1794542 (assigned to Scott) - https://bugs.launchpad.net/starlingx/+bug/1793214 (assigned to Mitch) - Other stx.2018.10 bugs - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 - Use your discretion depending on complexity, testing, churn, etc - There is no real urgency to get all these bugs into master before the code freeze as these can merge later and be cherry-picked by the developer to the release branch If you have any questions, please respond to this email. Regards, Ghada From cindy.xie at intel.com Wed Sep 26 15:49:42 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 26 Sep 2018 15:49:42 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B385482@SHSMSX104.ccr.corp.intel.com> Erich, Did you ever try serial build in your Jenkins? It takes time but if serial build can be successful, it may narrow the problem. Thx. - cindy -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Wednesday, September 26, 2018 11:32 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] build-pkgs cannot complete std build Hi, This is the build issue mentioned in the meeting this morning https://bugs.launchpad.net/starlingx/+bug/1794415 <- full details are here. In summary what happens is that ceph cannot be build, the build.log for ceph says: BUILDSTDERR: aclocal: overwriting 'm4/ax_c_var_func.m4' with '/usr/share/aclocal/ax_c_var_func.m4' BUILDSTDERR: aclocal: overwriting 'm4/ax_check_compile_flag.m4' with '/usr/share/aclocal/ax_check_compile_flag.m4' BUILDSTDERR: aclocal: installing 'm4/ax_cxx_compile_stdcxx.m4' from '/usr/share/aclocal/ax_cxx_compile_stdcxx.m4' BUILDSTDERR: aclocal: overwriting 'm4/ax_cxx_compile_stdcxx_11.m4' with '/usr/share/aclocal/ax_cxx_compile_stdcxx_11.m4' BUILDSTDERR: aclocal: overwriting 'm4/ax_cxx_static_cast.m4' with '/usr/share/aclocal/ax_cxx_static_cast.m4' BUILDSTDERR: aclocal: overwriting 'm4/pkg.m4' with '/usr/share/aclocal/pkg.m4' BUILDSTDERR: aclocal: installing 'm4/ax_require_defined.m4' from '/usr/share/aclocal/ax_require_defined.m4' BUILDSTDERR: aclocal: error: too many loops BUILDSTDERR: aclocal: Please contact . BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) RPM build errors: Child return code was: 1 EXCEPTION: [Error()] However, I'm able to build ceph in mock and I don't see this problem there. We'll continue investigating -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Wed Sep 26 16:16:43 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 26 Sep 2018 12:16:43 -0400 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> Message-ID: <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> aclocal 'too many loops' has been popping up sporadically for a week or two now.  Possibly 7.5 related. I suspect that there is a build order and/or race condition element to this.   It often goes away if you just run build-pkgs a second time. The second possible element is that build-pkgs is using flags that preserve the mock environment between packages.  The goal was to avoid reinstalling required packages that are often common across the packages we build.   It was a build time speedup that has been in use for 2-3 years now without incident. Google shows that other folks have hit 'aclocal too many loops' as well, and there are suggestions that it might be fixed in a recent update to automake.  Scanning the changelog for the latest and greatest from gnu.org doesn't show any obvious fixes addressing this issue. Scott On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: > BUILDSTDERR: aclocal: error: too many loops > BUILDSTDERR: aclocal: Please contact. > BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. > BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 > BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 > BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) > BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib > BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Wed Sep 26 16:22:00 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 26 Sep 2018 11:22:00 -0500 Subject: [Starlingx-discuss] MInutes: Weekly StarlingX non-OpenStack Distr meeting, 9/26 In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B38515A@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F2B38515A@SHSMSX104.ccr.corp.intel.com> Message-ID: On Wed, Sep 26, 2018 at 8:33 AM, Xie, Cindy wrote: > - Libvirt/qemu upgrade status (Ghada/Jim) > no blocking issue, -1 blocked by workflow. 4 pending patches waiting for merge, expected to be in by end of today. Waiting for Dean to merge to stx-staging for the libvirt repo. > qemu will not be in this 2018.10 release. This was merged this morning, https://review.openstack.org/#/c/605465/ contains the manifest change to pull the new branch stx/v4.7.0. > - Ceph upgrade status (Vivian/Dehao) > Feature branch needs to be created on staging as well. follow the same process as of Libvirt/qemu update. This is not technically a feature branch, it is the 'master' branch for the 13.2.0 rebase. stx/v13.2.0 has been created. You can create a PR against this branch with your rebased commits. Let me know when you have done this or if you need help with it. We will need a similar change to the manifest file as above to enable using the branch. dt -- Dean Troyer dtroyer at gmail.com From abraham.arce.moreno at intel.com Wed Sep 26 16:24:56 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 26 Sep 2018 16:24:56 +0000 Subject: [Starlingx-discuss] CEPH Based Testing Options Message-ID: In today's "Weekly StarlingX non-OpenStack Distro" [0] there was a requirement for our validation activities around CEPH so we need your help to learn more about the specific hardware. StarlingX allows a flexible storage options: 1. Linux Logical Volume Manager 2. CEPH 3. External SAN [ CEPH : StarlingX Dedicated Storage ] StarlingX system can be configured as Ceph-backend storage (Controller) and have available N number of Compute and Storage hosts, today we are deploying this as a "Dedicated Storage" configuration [1] : - 2 Controller Nodes - 2 Compute Nodes - 2 Storage Nodes [ CEPH : Homepage Documentation ] Looking at the Hardware Recommendations from CEPH Documentation, they list N number of components including requirements for CPU, RAM and a bunch of storage devices (Hard Disks, SSDs) [2] StarlingX provides this provisioning automatically if "Dedicated Storage" is configuration chosen. [CEPH : Specific Hardware ] Can you please guide us on what does that specific need makes it unique? Is it a hardware? Is it a configuration? Is the mix of both? 1. Is StarlingX "Dedicated Storage" configuration one of the 2 possible CEPH based testing options? 2. Do we need a separate CEPH cluster provisioned including their own OSDs and monitors? 3. Any other? We would appreciate any link to information and architecture to learn more about this request. [0] https://wiki.openstack.org/wiki/StarlingX/Distro [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Dedicated_Storage [2] http://docs.ceph.com/docs/jewel/start/hardware-recommendations/ From Ghada.Khalil at windriver.com Wed Sep 26 16:34:12 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 26 Sep 2018 16:34:12 +0000 Subject: [Starlingx-discuss] MInutes: Weekly StarlingX non-OpenStack Distr meeting, 9/26 In-Reply-To: References: <2FD5DDB5A04D264C80D42CA35194914F2B38515A@SHSMSX104.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA456FB1@ALA-MBD.corp.ad.wrs.com> A note/question below... Ghada -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Wednesday, September 26, 2018 12:22 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] MInutes: Weekly StarlingX non-OpenStack Distr meeting, 9/26 > - Ceph upgrade status (Vivian/Dehao) > Feature branch needs to be created on staging as well. follow the same process as of Libvirt/qemu update. This is not technically a feature branch, it is the 'master' branch for the 13.2.0 rebase. stx/v13.2.0 has been created. You can create a PR against this branch with your rebased commits. Let me know when you have done this or if you need help with it. We will need a similar change to the manifest file as above to enable using the branch. dt [[GK]] Based on the discussion this morning, the ceph upgrade is not ready to push to stx/v13.2.0 yet. I don't believe the work is complete and no testing has been done yet. My understanding of the proposal is that the pull request would be done only when the content is ready to be merged/used (or close to it). Is that the recommendation? I realize that it's possible to put the code in the branch at any time and not change the manifest. But, as a general practice, we want to only push changes that are tested. As a side note, the ceph upgrade is not an stx.2018.10 deliverable. -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Wed Sep 26 16:48:06 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 26 Sep 2018 11:48:06 -0500 Subject: [Starlingx-discuss] MInutes: Weekly StarlingX non-OpenStack Distr meeting, 9/26 In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA456FB1@ALA-MBD.corp.ad.wrs.com> References: <2FD5DDB5A04D264C80D42CA35194914F2B38515A@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA456FB1@ALA-MBD.corp.ad.wrs.com> Message-ID: On Wed, Sep 26, 2018 at 11:34 AM, Khalil, Ghada wrote: > [[GK]] Based on the discussion this morning, the ceph upgrade is not ready to push to stx/v13.2.0 yet. I don't believe the work is complete and no testing has been done yet. My understanding of the proposal is that the pull request would be done only when the content is ready to be merged/used (or close to it). Is that the recommendation? I realize that it's possible to put the code in the branch at any time and not change the manifest. But, as a > general practice, we want to only push changes that are tested. I disagree slightly, we only want to _merge_ changes that are tested. In an ideal world a good bit of the testing happens when pushed to Github or Gerrit...we will get to that someday. This is preparing the place to push those changes for testing, and to share them in a public place. All of the Ceph upgrade work done so far has been in a private location. We should be doing _all_ of this work in public. This is exactly one of the reasons we need to create these branches for rebase work. > As a side note, the ceph upgrade is not an stx.2018.10 deliverable. This makes no changes to the existing branch and should not impact anything in the release cycle. dt -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Wed Sep 26 20:27:01 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 26 Sep 2018 20:27:01 +0000 Subject: [Starlingx-discuss] Initial Thoughts on Cengn In-Reply-To: <4734b1f8-6da0-2a35-ff18-e14930d574d8@intel.com> References: <4734b1f8-6da0-2a35-ff18-e14930d574d8@intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5A6B32@fmsmsx117.amr.corp.intel.com> Sharing this with the mailing list... Ken is working on a Story for this, to be reviewed with the Build sub-project team. brucej -----Original Message----- From: Wold, Saul Sent: Wednesday, September 26, 2018 11:21 AM To: Jones, Bruce E ; Troyer, Dean ; Rodriguez Bahena, Victor Subject: Initial Thoughts on Cengn Just jotting some notes down, not sure where they should go yet, I want to wait for the Cengn deal to be more solid. Dean and I talked about a couple of these things: 1) Need to ensure GPL requirements are met even for Binary RPMs downloaded from REHL or Centos, they need to provide the corresponding SRPM. It would be best to just mirror all SRPMs. 2) What Mechanism to use to provide the mirror: - Yum Repo - HTTPS - rsync 3) What mechanism should a community member use - Proxy to check local source before checking Remote - ideally with yum repo, but maybe HTTPS - yumdownloader - rsync - https 4) Mirror package manamaget - when to deprecate a package - when we EOL support for a given release + 1year? 5) CI/CD - Nightly Build - Testing? 6) Whatever else I have forgotten or overlooked Sau! From scott.little at windriver.com Wed Sep 26 21:08:20 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 26 Sep 2018 17:08:20 -0400 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> Message-ID: <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> I have also been investigating another intermittent build error affecting initscripts. https://bugs.launchpad.net/starlingx/+bug/1794611 So any given package might be built by rpm-4.11.3, or by rpm-4.14.0.  It's a race with many inputs.  Ideally it shouldn't matter, but it does.  build-pkgs --serial might reduce the odds, but likely won't solve it entirely. In this case it is a new option that rpm passes to the patch command, --no-backup-if-mismatch, first introduced by rpm-4.13. This option has the effect of suppressing the creation of '.orig' files. Creation of .orig files are a consequence of applying patches that are not clean. Unclean patches are ones that require 'fuzzing', i.e. treat the patch line numbers as approximate, rather than a strict requirement, just so long as the before/after context seems to be correct. Prior to StarlingX, my policy for rebasing patches was that no fuzz is tolerated in our patches. All the work to upgrade to 7.5 has created a lot of fuzzy patches. audit-2.8.1-3.el7.tis.2 bash-4.2.46-30.el7.tis.3 dhcp-4.2.5-68.el7.centos.1.tis.8 dnsmasq-2.76-5.el7.tis.6 drbd-8.4.3-0.tis.6 facter-2.4.4-4.el7.tis.4 haproxy-1.5.18-7.el7.tis.7 initscripts-9.49.41-1.el7.tis.16 iptables-1.4.21-24.1.el7_5.tis.3 kubernetes-1.10.0-1.tis.1 libevent-2.0.21-4.el7.tis.2 lighttpd-1.4.50-1.el7.tis.6 logrotate-3.8.6-15.el7.tis.3 netpbm-10.79.00-7.el7.tis.2 net-snmp-5.7.2-33.el7_5.2.tis.10 net-tools-2.0-0.22.20131004git.el7.tis.2 nfs-utils-1.3.0-0.54.el7.tis.4 nss-pam-ldapd-0.8.13-16.el7.tis.4 ntp-4.2.6p5-28.el7.centos.tis.3 openldap-2.4.44-15.el7_5.tis.8 openssh-7.4p1-16.el7_4.tis.9 pam-1.1.8-22.el7.tis.4 puppet-4.8.2-1.el7.tis.2 puppet-ceph-2.4.1-1.el7.tis.4 puppet-horizon-11.5.0-1.el7.tis.1 python-2.7.5-69.el7_5.tis.3 python-keyring-5.7.1-1.tis.2 python-wsme-0.9.2-1.el7.tis.3 resource-agents-3.9.5-124.el7.tis.12 rsync-3.1.2-4.el7.tis.2 shadow-utils-4.1.5.1-24.el7.tis.4 sudo-1.8.19p2-14.el7_5.tis.3 watchdog-5.13-11.el7.tis.2 So any of these packages might or might not produce unwanted .orig files. The .orig files might or might not be packaged, or break packaging. So there are a number of threads to pull at here. 1) Are fuzzy patches tolerated.   I vote no.  Sooner or later a fuzzy patch will be mis-applied and cause us problems. 2) Can we force rpmbuild within mock to use a consistent policy with respect to creation of orig files? 3) Can we pre-build rpm, such that all packages build against the same rpm version? 4) Are we patching any other low level build tools that have similar issues?  Possibly explaining ceph?  TBD On 18-09-26 12:16 PM, Scott Little wrote: > aclocal 'too many loops' has been popping up sporadically for a week > or two now.  Possibly 7.5 related. > > I suspect that there is a build order and/or race condition element to > this.   It often goes away if you just run build-pkgs a second time. > > The second possible element is that build-pkgs is using flags that > preserve the mock environment between packages.  The goal was to avoid > reinstalling required packages that are often common across the > packages we build.   It was a build time speedup that has been in use > for 2-3 years now without incident. > > Google shows that other folks have hit 'aclocal too many loops' as > well, and there are suggestions that it might be fixed in a recent > update to automake.  Scanning the changelog for the latest and > greatest from gnu.org doesn't show any obvious fixes addressing this > issue. > > Scott > > > On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >> BUILDSTDERR: aclocal: error: too many loops >> BUILDSTDERR: aclocal: Please contact. >> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. >> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 >> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 >> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >> BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib >> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) > > > > > _______________________________________________ > 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 cesar.lara at intel.com Wed Sep 26 21:11:46 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 26 Sep 2018 21:11:46 +0000 Subject: [Starlingx-discuss] [meetings][build] Build team meeting Agenda for 10/1/2018 Message-ID: <0B566C62EC792145B40E29EFEBF1AB4710521086@fmsmsx104.amr.corp.intel.com> StarlingX Build team meeting Agenda for 10/1/2018 * Build issues on intel side - Findings and next steps - Mock cleanup proposal - General discussion * Proposals for hosting with cengn * Brainstorming for next release * Re-scoping of stxb tool Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Sep 26 21:58:07 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 26 Sep 2018 21:58:07 +0000 Subject: [Starlingx-discuss] [Release] stx.2018.10 status & next steps Message-ID: <151EE31B9FCCA54397A757BC674650F0BA457443@ALA-MBD.corp.ad.wrs.com> Below is an updated status as of a few minutes ago. Updates are prefixed with [[GK]] -----Original Message----- From: Khalil, Ghada Sent: Wednesday, September 26, 2018 11:44 AM To: starlingx-discuss at lists.starlingx.io Subject: [Release] stx.2018.10 status & next steps Importance: High Hello all, This email captures the discussion related to the stx.2018.10 code freeze plan - discussed this morning at the StarlingX community meeting. The code freeze will be in effect as of today (September 26, 2018) at midnight Eastern Time / 9pm Pacific Time Gerrit reviews can continue, but we ask Core Reviewers NOT to Workflow+1 any commits after the cut-off above. Follow-up emails will be sent when merges can resume on master. Review Priorities/Workflow+1 until the code freeze: - Stories: - OCF Re-location: https://storyboard.openstack.org/#!/story/2003715 [[GK]] Merged - Libvirt 4.7.0: https://storyboard.openstack.org/#!/story/2003396 - Libvirt 4.7.0: https://storyboard.openstack.org/#!/story/2003339 [[GK]] One commit still waiting for zuul: https://review.openstack.org/#/c/605465/ - Cinder B&R: https://storyboard.openstack.org/#!/story/2003115 - Cinder B&R: https://storyboard.openstack.org/#!/story/2002985 [[GK]] Merged - https://storyboard.openstack.org/#!/story/2002946 (best effort) [[GK]] Waiting on zuul, but also needs W+1 - Documentation Updates: https://review.openstack.org/#/q/status:open+branch:master+topic:documentation-baseline [[GK]] There are still 9 reviews here. Some have -1 and require re-work. I expect this may still go into tomorrow - Updating the release version to 18.10: https://storyboard.openstack.org/#!/story/2003085 [[GK]] Waiting for zuul - Key Bugs - https://bugs.launchpad.net/starlingx/+bug/1794415 (more info to be sent to mailing list) [[GK]] No resolution yet - https://bugs.launchpad.net/starlingx/+bug/1794542 (assigned to Scott) [[GK]] Waiting for Zuul - https://bugs.launchpad.net/starlingx/+bug/1793214 (assigned to Mitch) [[GK]] Merged - Other stx.2018.10 bugs - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 - Use your discretion depending on complexity, testing, churn, etc - There is no real urgency to get all these bugs into master before the code freeze as these can merge later and be cherry-picked by the developer to the release branch If you have any questions, please respond to this email. Regards, Ghada From dtroyer at gmail.com Wed Sep 26 22:17:33 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 26 Sep 2018 17:17:33 -0500 Subject: [Starlingx-discuss] [Release] stx.2018.10 status & next steps In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA457443@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA457443@ALA-MBD.corp.ad.wrs.com> Message-ID: On Wed, Sep 26, 2018 at 4:58 PM, Khalil, Ghada wrote: > Below is an updated status as of a few minutes ago. Updates are prefixed with [[GK]] I took the liberty of changing the topic on the existing open reviews in Gerrit to 'rel-2018.10' so we can use a query to track the remaining reviews. ( I did not change the doc reviews as they already have a working topic query.) There are currently 5 showing open. https://review.openstack.org/#/q/topic:rel-2018.10+status:open > - Documentation Updates: https://review.openstack.org/#/q/status:open+branch:master+topic:documentation-baseline > [[GK]] There are still 9 reviews here. Some have -1 and require re-work. I expect this may still go into tomorrow Continue to use this query to follow the doc reviews dt -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Wed Sep 26 22:33:31 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 26 Sep 2018 22:33:31 +0000 Subject: [Starlingx-discuss] [Release] stx.2018.10 status & next steps In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA457443@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5A6D4B@fmsmsx117.amr.corp.intel.com> > I took the liberty of changing the topic on the existing open reviews in Gerrit to 'rel-2018.10' so we can use a query to track the remaining reviews. ( I did not change the doc reviews as they already have a working topic query.) There are currently 5 showing open. > https://review.openstack.org/#/q/topic:rel-2018.10+status:open Thank you Dean, this is very helpful. Right now the only issues I'm concerned about are the build issues reported by Scott in his email. That is very concerning. brucej From sgw at linux.intel.com Wed Sep 26 23:44:50 2018 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 26 Sep 2018 16:44:50 -0700 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> Message-ID: <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> On 09/26/2018 02:08 PM, Scott Little wrote: > I have also been investigating another intermittent build error > affecting initscripts. > > https://bugs.launchpad.net/starlingx/+bug/1794611 > > So any given package might be built by rpm-4.11.3, or by rpm-4.14.0. > It's a race with many inputs.  Ideally it shouldn't matter, but it > does.  build-pkgs --serial might reduce the odds, but likely won't solve > it entirely. > Why is this the case in the first place, can't we ensure we only build rpm-4.14.0? > In this case it is a new option that rpm passes to the patch command, > --no-backup-if-mismatch, first introduced by rpm-4.13. > This option has the effect of suppressing the creation of '.orig' files. > > Creation of .orig files are a consequence of applying patches that are > not clean. Unclean patches are ones that require 'fuzzing', i.e. treat > the patch line numbers as approximate, rather than a strict requirement, > just so long as the before/after context seems to be correct. > > Prior to StarlingX, my policy for rebasing patches was that no fuzz is > tolerated in our patches. > > All the work to upgrade to 7.5 has created a lot of fuzzy patches. > Wow, sorry I was not aware that they were all fuzzy patches. > audit-2.8.1-3.el7.tis.2 > bash-4.2.46-30.el7.tis.3 > dhcp-4.2.5-68.el7.centos.1.tis.8 > dnsmasq-2.76-5.el7.tis.6 > drbd-8.4.3-0.tis.6 > facter-2.4.4-4.el7.tis.4 > haproxy-1.5.18-7.el7.tis.7 > initscripts-9.49.41-1.el7.tis.16 > iptables-1.4.21-24.1.el7_5.tis.3 > kubernetes-1.10.0-1.tis.1 > libevent-2.0.21-4.el7.tis.2 > lighttpd-1.4.50-1.el7.tis.6 > logrotate-3.8.6-15.el7.tis.3 > netpbm-10.79.00-7.el7.tis.2 > net-snmp-5.7.2-33.el7_5.2.tis.10 > net-tools-2.0-0.22.20131004git.el7.tis.2 > nfs-utils-1.3.0-0.54.el7.tis.4 > nss-pam-ldapd-0.8.13-16.el7.tis.4 > ntp-4.2.6p5-28.el7.centos.tis.3 > openldap-2.4.44-15.el7_5.tis.8 > openssh-7.4p1-16.el7_4.tis.9 > pam-1.1.8-22.el7.tis.4 > puppet-4.8.2-1.el7.tis.2 > puppet-ceph-2.4.1-1.el7.tis.4 > puppet-horizon-11.5.0-1.el7.tis.1 > python-2.7.5-69.el7_5.tis.3 > python-keyring-5.7.1-1.tis.2 > python-wsme-0.9.2-1.el7.tis.3 > resource-agents-3.9.5-124.el7.tis.12 > rsync-3.1.2-4.el7.tis.2 > shadow-utils-4.1.5.1-24.el7.tis.4 > sudo-1.8.19p2-14.el7_5.tis.3 > watchdog-5.13-11.el7.tis.2 > > So any of these packages might or might not produce unwanted .orig files. > The .orig files might or might not be packaged, or break packaging. > > So there are a number of threads to pull at here. > 1) Are fuzzy patches tolerated.   I vote no.  Sooner or later a fuzzy > patch will be mis-applied and cause us problems. Agreed, when updating patches should be rebased and de-fuzzed. > 2) Can we force rpmbuild within mock to use a consistent policy with > respect to creation of orig files? It would be good to investigate that. > 3) Can we pre-build rpm, such that all packages build against the same > rpm version? Yes, as mentioned above we should use a consistent version. > 4) Are we patching any other low level build tools that have similar > issues?  Possibly explaining ceph?  TBD > Yup more info is needed Sau! > > > On 18-09-26 12:16 PM, Scott Little wrote: >> aclocal 'too many loops' has been popping up sporadically for a week >> or two now.  Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition element to >> this.   It often goes away if you just run build-pkgs a second time. >> >> The second possible element is that build-pkgs is using flags that >> preserve the mock environment between packages.  The goal was to avoid >> reinstalling required packages that are often common across the >> packages we build.   It was a build time speedup that has been in use >> for 2-3 years now without incident. >> >> Google shows that other folks have hit 'aclocal too many loops' as >> well, and there are suggestions that it might be fixed in a recent >> update to automake.  Scanning the changelog for the latest and >> greatest from gnu.org doesn't show any obvious fixes addressing this >> issue. >> >> Scott >> >> >> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>> BUILDSTDERR: aclocal: error: too many loops >>> BUILDSTDERR: aclocal: Please contact. >>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. >>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 >>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 >>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >>> BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib >>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From erich.cordoba.malibran at intel.com Wed Sep 26 23:42:52 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 26 Sep 2018 23:42:52 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> Message-ID: <68a2d9646d1e2e4f46f4833a0f0c0c2c8cbfecd9.camel@intel.com> Trying to get a serial build avoiding the possible mock problems I encounter with this issue: BUILD_AVOIDANCE_URL= /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-srpms-serial --std /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-srpms-serial: line 33: /build-srpms-common.sh: No such file or directory CLEAN_FLAG=0 22:26:39 build-srpms-serial --std 22:26:39 make: all 22:26:40 ===== Build SRPM for 'remote-clients' ===== 22:26:40 PKG_BASE=/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients 22:26:40 WORK_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/stx-clients/remote-clients 22:26:40 RPMBUILD_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/stx-clients/remote-clients/rpmbuild 22:26:40 /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-srpms-serial: line 941: md5sums_from_input_vars: command not found 22:26:40 ERROR: build_dir_spec (943): md5sums_from_input_vars '' '/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients/centos/remote-clients.spec' '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SOURCES/remote-clients' Doing sed -i 's/PARALLEL/SERIAL/g' build-tools/build-srpms-serial fixes this issue. However, after the srpms are created the build-rpm-serial script is unable to find these srpms. See below ######## Wed Sep 26 22:36:34 UTC 2018: build-srpm-serial --std was successful ######## Wed Sep 26 22:36:34 UTC 2018: Launching build-rpms-serial --std /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-rpms-serial --std FORMAL_BUILD=0 modify-build-cfg /localdisk/loadbuild/jenkins-slave/starlingx/std/jenkins-slave-starlingx-tis-r5-pike-std.cfg Nothing to build in '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SRPMS' ######## Wed Sep 26 22:36:35 UTC 2018: build-rpm-serial --std was successful This is reported here: https://bugs.launchpad.net/starlingx/+bug/1790583 I tried this but it didn't work for me: https://review.openstack.org/#/c/603983/ So, for now seems that it's not possible to use serial building. On Wed, 2018-09-26 at 12:16 -0400, Scott Little wrote: > aclocal 'too many loops' has been popping up sporadically for a week > or two now. Possibly 7.5 related. > > I suspect that there is a build order and/or race condition element > to this. It often goes away if you just run build-pkgs a second > time. > > The second possible element is that build-pkgs is using flags that > preserve the mock environment between packages. The goal was to > avoid reinstalling required packages that are often common across the > packages we build. It was a build time speedup that has been in use > for 2-3 years now without incident. > > Google shows that other folks have hit 'aclocal too many loops' as > well, and there are suggestions that it might be fixed in a recent > update to automake. Scanning the changelog for the latest and > greatest from gnu.org doesn't show any obvious fixes addressing this > issue. > > Scott > > > On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: > > BUILDSTDERR: aclocal: error: too many loops > > BUILDSTDERR: aclocal: Please contact . > > BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line > > 662. > > BUILDSTDERR: Automake::Channels::msg('automake', '', 'too > > many loops') called at /usr/share/automake- > > 1.13/Automake/ChannelDefs.pm line 212 > > BUILDSTDERR: Automake::ChannelDefs::prog_error('too many > > loops') called at /usr/bin/aclocal line 1187 > > BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c > > (%build) > > BUILDSTDERR: Macro expanded in comment on line 214: %global > > _libexecdir %{_exec_prefix}/lib > > BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c > > (%build) > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Thu Sep 27 00:05:01 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 27 Sep 2018 00:05:01 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> Message-ID: <30f504ec5f5525a86bf5c357cd7362fc035205b6.camel@intel.com> On Wed, 2018-09-26 at 16:44 -0700, Saul Wold wrote: > > On 09/26/2018 02:08 PM, Scott Little wrote: > > I have also been investigating another intermittent build error > > affecting initscripts. > > > > https://bugs.launchpad.net/starlingx/+bug/1794611 > > > > So any given package might be built by rpm-4.11.3, or by rpm- > > 4.14.0. > > It's a race with many inputs. Ideally it shouldn't matter, but it > > does. build-pkgs --serial might reduce the odds, but likely won't > > solve > > it entirely. > > > > Why is this the case in the first place, can't we ensure we only > build > rpm-4.14.0? > > > In this case it is a new option that rpm passes to the patch > > command, > > --no-backup-if-mismatch, first introduced by rpm-4.13. > > This option has the effect of suppressing the creation of '.orig' > > files. > > > > Creation of .orig files are a consequence of applying patches that > > are > > not clean. Unclean patches are ones that require 'fuzzing', i.e. > > treat > > the patch line numbers as approximate, rather than a strict > > requirement, > > just so long as the before/after context seems to be correct. > > > > Prior to StarlingX, my policy for rebasing patches was that no fuzz > > is > > tolerated in our patches. > > > > All the work to upgrade to 7.5 has created a lot of fuzzy patches. > > > > Wow, sorry I was not aware that they were all fuzzy patches. > How did you got this list? There were .orig files in those folder? > > audit-2.8.1-3.el7.tis.2 > > bash-4.2.46-30.el7.tis.3 > > dhcp-4.2.5-68.el7.centos.1.tis.8 > > dnsmasq-2.76-5.el7.tis.6 > > drbd-8.4.3-0.tis.6 > > facter-2.4.4-4.el7.tis.4 > > haproxy-1.5.18-7.el7.tis.7 > > initscripts-9.49.41-1.el7.tis.16 > > iptables-1.4.21-24.1.el7_5.tis.3 > > kubernetes-1.10.0-1.tis.1 > > libevent-2.0.21-4.el7.tis.2 > > lighttpd-1.4.50-1.el7.tis.6 > > logrotate-3.8.6-15.el7.tis.3 > > netpbm-10.79.00-7.el7.tis.2 > > net-snmp-5.7.2-33.el7_5.2.tis.10 > > net-tools-2.0-0.22.20131004git.el7.tis.2 > > nfs-utils-1.3.0-0.54.el7.tis.4 > > nss-pam-ldapd-0.8.13-16.el7.tis.4 > > ntp-4.2.6p5-28.el7.centos.tis.3 > > openldap-2.4.44-15.el7_5.tis.8 > > openssh-7.4p1-16.el7_4.tis.9 > > pam-1.1.8-22.el7.tis.4 > > puppet-4.8.2-1.el7.tis.2 > > puppet-ceph-2.4.1-1.el7.tis.4 > > puppet-horizon-11.5.0-1.el7.tis.1 > > python-2.7.5-69.el7_5.tis.3 > > python-keyring-5.7.1-1.tis.2 > > python-wsme-0.9.2-1.el7.tis.3 > > resource-agents-3.9.5-124.el7.tis.12 > > rsync-3.1.2-4.el7.tis.2 > > shadow-utils-4.1.5.1-24.el7.tis.4 > > sudo-1.8.19p2-14.el7_5.tis.3 > > watchdog-5.13-11.el7.tis.2 > > > > So any of these packages might or might not produce unwanted .orig > > files. > > The .orig files might or might not be packaged, or break packaging. > > > > So there are a number of threads to pull at here. > > 1) Are fuzzy patches tolerated. I vote no. Sooner or later a > > fuzzy > > patch will be mis-applied and cause us problems. > > Agreed, when updating patches should be rebased and de-fuzzed. > > > 2) Can we force rpmbuild within mock to use a consistent policy > > with > > respect to creation of orig files? > > It would be good to investigate that. > Seems we can pass _default_patch_fuzz 0 as a variable to rpmbuild. What could be the course of action here? - Wire rpmbuild to not allow fuzzy patches. - Then iteratively try to build until all the index are correct -Erich > > 3) Can we pre-build rpm, such that all packages build against the > > same > > rpm version? > > Yes, as mentioned above we should use a consistent version. > > > 4) Are we patching any other low level build tools that have > > similar > > issues? Possibly explaining ceph? TBD > > > > Yup more info is needed > > Sau! > > > > > > > > On 18-09-26 12:16 PM, Scott Little wrote: > > > aclocal 'too many loops' has been popping up sporadically for a > > > week > > > or two now. Possibly 7.5 related. > > > > > > I suspect that there is a build order and/or race condition > > > element to > > > this. It often goes away if you just run build-pkgs a second > > > time. > > > > > > The second possible element is that build-pkgs is using flags > > > that > > > preserve the mock environment between packages. The goal was to > > > avoid > > > reinstalling required packages that are often common across the > > > packages we build. It was a build time speedup that has been in > > > use > > > for 2-3 years now without incident. > > > > > > Google shows that other folks have hit 'aclocal too many loops' > > > as > > > well, and there are suggestions that it might be fixed in a > > > recent > > > update to automake. Scanning the changelog for the latest and > > > greatest from gnu.org doesn't show any obvious fixes addressing > > > this > > > issue. > > > > > > Scott > > > > > > > > > On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: > > > > BUILDSTDERR: aclocal: error: too many loops > > > > BUILDSTDERR: aclocal: Please contact. > > > > BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm > > > > line 662. > > > > BUILDSTDERR: Automake::Channels::msg('automake', '', > > > > 'too many loops') called at /usr/share/automake- > > > > 1.13/Automake/ChannelDefs.pm line 212 > > > > BUILDSTDERR: Automake::ChannelDefs::prog_error('too > > > > many loops') called at /usr/bin/aclocal line 1187 > > > > BUILDSTDERR: error: Bad exit status from /var/tmp/rpm- > > > > tmp.Sj0E7c (%build) > > > > BUILDSTDERR: Macro expanded in comment on line 214: %global > > > > _libexecdir %{_exec_prefix}/lib > > > > BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c > > > > (%build) > > > > > > > > > > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > > uss > > > > > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Thu Sep 27 00:55:19 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 27 Sep 2018 00:55:19 +0000 Subject: [Starlingx-discuss] [Release] stx.2018.10 status & next steps In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5A6D4B@fmsmsx117.amr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA457443@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB5A6D4B@fmsmsx117.amr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3B51E4@ALA-MBD.corp.ad.wrs.com> One of these open reviews is blocked by a Zuul failure, in the new openstack-tox-docs job, which would be unrelated to the updated https://review.openstack.org/#/c/605462/ 2018-09-26 23:53:29.362172 | ubuntu-xenial | "msg": "rsync: change_dir \"/home/zuul//src/git.openstack.org/openstack/stx-integ/doc/build\" failed: No such file or directory (2)\nrsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1655) [Receiver=3.1.1]\nrsync: [Receiver] write error: Broken pipe (32) 2018-09-26 23:53:37.844954 | ubuntu-xenial | rsync: change_dir "/home/zuul//src/git.openstack.org/openstack/stx-integ/.tox/docs/log" failed: No such file or directory (2) 2018-09-26 23:53:37.845126 | ubuntu-xenial | rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1655) [Receiver=3.1.1] I don't know if a recheck will work here or not, if it's some transient failure, but it looks like we've got some Zuul jobs that have been in the queue for 7+ hours now. We may need to make these doc jobs non-voting if there can be such intermittent failures. I haven't looked at what the job is doing, though -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, September 26, 2018 6:34 PM To: Dean Troyer; Khalil, Ghada Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Release] stx.2018.10 status & next steps > I took the liberty of changing the topic on the existing open reviews in Gerrit to 'rel-2018.10' so we can use a query to track the remaining reviews. ( I did not change the doc reviews as they already have a working topic query.) There are currently 5 showing open. > https://review.openstack.org/#/q/topic:rel-2018.10+status:open Thank you Dean, this is very helpful. Right now the only issues I'm concerned about are the build issues reported by Scott in his email. That is very concerning. brucej _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Thu Sep 27 01:09:47 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 27 Sep 2018 01:09:47 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4574F2@ALA-MBD.corp.ad.wrs.com> Hi Saul, It looks like the first step is for all the 7.5 patches to be re-generated and de-fuzzed. I consider this to be gating the October release. Do you agree? I suggest that this gets addressed in master before the release branch creation. I will add a new task to the CentOS 7.5 rebase story for Cindy's team to work on. I would also like to propose that we continue to place master under code freeze/limited merge and only allow the items we consider gating for October. This would allow us to limit the churn to the next few days. Is this ok with everyone? Thanks, Ghada -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Wednesday, September 26, 2018 7:45 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build On 09/26/2018 02:08 PM, Scott Little wrote: > I have also been investigating another intermittent build error > affecting initscripts. > > https://bugs.launchpad.net/starlingx/+bug/1794611 > > So any given package might be built by rpm-4.11.3, or by rpm-4.14.0. > It's a race with many inputs.  Ideally it shouldn't matter, but it > does.  build-pkgs --serial might reduce the odds, but likely won't > solve it entirely. > Why is this the case in the first place, can't we ensure we only build rpm-4.14.0? > In this case it is a new option that rpm passes to the patch command, > --no-backup-if-mismatch, first introduced by rpm-4.13. > This option has the effect of suppressing the creation of '.orig' files. > > Creation of .orig files are a consequence of applying patches that are > not clean. Unclean patches are ones that require 'fuzzing', i.e. treat > the patch line numbers as approximate, rather than a strict > requirement, just so long as the before/after context seems to be correct. > > Prior to StarlingX, my policy for rebasing patches was that no fuzz is > tolerated in our patches. > > All the work to upgrade to 7.5 has created a lot of fuzzy patches. > Wow, sorry I was not aware that they were all fuzzy patches. > audit-2.8.1-3.el7.tis.2 > bash-4.2.46-30.el7.tis.3 > dhcp-4.2.5-68.el7.centos.1.tis.8 > dnsmasq-2.76-5.el7.tis.6 > drbd-8.4.3-0.tis.6 > facter-2.4.4-4.el7.tis.4 > haproxy-1.5.18-7.el7.tis.7 > initscripts-9.49.41-1.el7.tis.16 > iptables-1.4.21-24.1.el7_5.tis.3 > kubernetes-1.10.0-1.tis.1 > libevent-2.0.21-4.el7.tis.2 > lighttpd-1.4.50-1.el7.tis.6 > logrotate-3.8.6-15.el7.tis.3 > netpbm-10.79.00-7.el7.tis.2 > net-snmp-5.7.2-33.el7_5.2.tis.10 > net-tools-2.0-0.22.20131004git.el7.tis.2 > nfs-utils-1.3.0-0.54.el7.tis.4 > nss-pam-ldapd-0.8.13-16.el7.tis.4 > ntp-4.2.6p5-28.el7.centos.tis.3 > openldap-2.4.44-15.el7_5.tis.8 > openssh-7.4p1-16.el7_4.tis.9 > pam-1.1.8-22.el7.tis.4 > puppet-4.8.2-1.el7.tis.2 > puppet-ceph-2.4.1-1.el7.tis.4 > puppet-horizon-11.5.0-1.el7.tis.1 > python-2.7.5-69.el7_5.tis.3 > python-keyring-5.7.1-1.tis.2 > python-wsme-0.9.2-1.el7.tis.3 > resource-agents-3.9.5-124.el7.tis.12 > rsync-3.1.2-4.el7.tis.2 > shadow-utils-4.1.5.1-24.el7.tis.4 > sudo-1.8.19p2-14.el7_5.tis.3 > watchdog-5.13-11.el7.tis.2 > > So any of these packages might or might not produce unwanted .orig files. > The .orig files might or might not be packaged, or break packaging. > > So there are a number of threads to pull at here. > 1) Are fuzzy patches tolerated.   I vote no.  Sooner or later a fuzzy > patch will be mis-applied and cause us problems. Agreed, when updating patches should be rebased and de-fuzzed. > 2) Can we force rpmbuild within mock to use a consistent policy with > respect to creation of orig files? It would be good to investigate that. > 3) Can we pre-build rpm, such that all packages build against the same > rpm version? Yes, as mentioned above we should use a consistent version. > 4) Are we patching any other low level build tools that have similar > issues?  Possibly explaining ceph?  TBD > Yup more info is needed Sau! > > > On 18-09-26 12:16 PM, Scott Little wrote: >> aclocal 'too many loops' has been popping up sporadically for a week >> or two now.  Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition element >> to this.   It often goes away if you just run build-pkgs a second time. >> >> The second possible element is that build-pkgs is using flags that >> preserve the mock environment between packages.  The goal was to >> avoid reinstalling required packages that are often common across the >> packages we build.   It was a build time speedup that has been in use >> for 2-3 years now without incident. >> >> Google shows that other folks have hit 'aclocal too many loops' as >> well, and there are suggestions that it might be fixed in a recent >> update to automake.  Scanning the changelog for the latest and >> greatest from gnu.org doesn't show any obvious fixes addressing this >> issue. >> >> Scott >> >> >> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>> BUILDSTDERR: aclocal: error: too many loops >>> BUILDSTDERR: aclocal: Please contact. >>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. >>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 >>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 >>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >>> BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib >>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Thu Sep 27 01:12:11 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 27 Sep 2018 01:12:11 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA4574F2@ALA-MBD.corp.ad.wrs.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4574F2@ALA-MBD.corp.ad.wrs.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB287231@ALA-MBD.corp.ad.wrs.com> I agree. Brent -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, September 26, 2018 9:10 PM To: Saul Wold ; starlingx-discuss at lists.starlingx.io; Xie, Cindy ; Lin, Shuicheng Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build Hi Saul, It looks like the first step is for all the 7.5 patches to be re-generated and de-fuzzed. I consider this to be gating the October release. Do you agree? I suggest that this gets addressed in master before the release branch creation. I will add a new task to the CentOS 7.5 rebase story for Cindy's team to work on. I would also like to propose that we continue to place master under code freeze/limited merge and only allow the items we consider gating for October. This would allow us to limit the churn to the next few days. Is this ok with everyone? Thanks, Ghada -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Wednesday, September 26, 2018 7:45 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build On 09/26/2018 02:08 PM, Scott Little wrote: > I have also been investigating another intermittent build error > affecting initscripts. > > https://bugs.launchpad.net/starlingx/+bug/1794611 > > So any given package might be built by rpm-4.11.3, or by rpm-4.14.0. > It's a race with many inputs.  Ideally it shouldn't matter, but it > does.  build-pkgs --serial might reduce the odds, but likely won't > solve it entirely. > Why is this the case in the first place, can't we ensure we only build rpm-4.14.0? > In this case it is a new option that rpm passes to the patch command, > --no-backup-if-mismatch, first introduced by rpm-4.13. > This option has the effect of suppressing the creation of '.orig' files. > > Creation of .orig files are a consequence of applying patches that are > not clean. Unclean patches are ones that require 'fuzzing', i.e. treat > the patch line numbers as approximate, rather than a strict > requirement, just so long as the before/after context seems to be correct. > > Prior to StarlingX, my policy for rebasing patches was that no fuzz is > tolerated in our patches. > > All the work to upgrade to 7.5 has created a lot of fuzzy patches. > Wow, sorry I was not aware that they were all fuzzy patches. > audit-2.8.1-3.el7.tis.2 > bash-4.2.46-30.el7.tis.3 > dhcp-4.2.5-68.el7.centos.1.tis.8 > dnsmasq-2.76-5.el7.tis.6 > drbd-8.4.3-0.tis.6 > facter-2.4.4-4.el7.tis.4 > haproxy-1.5.18-7.el7.tis.7 > initscripts-9.49.41-1.el7.tis.16 > iptables-1.4.21-24.1.el7_5.tis.3 > kubernetes-1.10.0-1.tis.1 > libevent-2.0.21-4.el7.tis.2 > lighttpd-1.4.50-1.el7.tis.6 > logrotate-3.8.6-15.el7.tis.3 > netpbm-10.79.00-7.el7.tis.2 > net-snmp-5.7.2-33.el7_5.2.tis.10 > net-tools-2.0-0.22.20131004git.el7.tis.2 > nfs-utils-1.3.0-0.54.el7.tis.4 > nss-pam-ldapd-0.8.13-16.el7.tis.4 > ntp-4.2.6p5-28.el7.centos.tis.3 > openldap-2.4.44-15.el7_5.tis.8 > openssh-7.4p1-16.el7_4.tis.9 > pam-1.1.8-22.el7.tis.4 > puppet-4.8.2-1.el7.tis.2 > puppet-ceph-2.4.1-1.el7.tis.4 > puppet-horizon-11.5.0-1.el7.tis.1 > python-2.7.5-69.el7_5.tis.3 > python-keyring-5.7.1-1.tis.2 > python-wsme-0.9.2-1.el7.tis.3 > resource-agents-3.9.5-124.el7.tis.12 > rsync-3.1.2-4.el7.tis.2 > shadow-utils-4.1.5.1-24.el7.tis.4 > sudo-1.8.19p2-14.el7_5.tis.3 > watchdog-5.13-11.el7.tis.2 > > So any of these packages might or might not produce unwanted .orig files. > The .orig files might or might not be packaged, or break packaging. > > So there are a number of threads to pull at here. > 1) Are fuzzy patches tolerated.   I vote no.  Sooner or later a fuzzy > patch will be mis-applied and cause us problems. Agreed, when updating patches should be rebased and de-fuzzed. > 2) Can we force rpmbuild within mock to use a consistent policy with > respect to creation of orig files? It would be good to investigate that. > 3) Can we pre-build rpm, such that all packages build against the same > rpm version? Yes, as mentioned above we should use a consistent version. > 4) Are we patching any other low level build tools that have similar > issues?  Possibly explaining ceph?  TBD > Yup more info is needed Sau! > > > On 18-09-26 12:16 PM, Scott Little wrote: >> aclocal 'too many loops' has been popping up sporadically for a week >> or two now.  Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition element >> to this.   It often goes away if you just run build-pkgs a second time. >> >> The second possible element is that build-pkgs is using flags that >> preserve the mock environment between packages.  The goal was to >> avoid reinstalling required packages that are often common across the >> packages we build.   It was a build time speedup that has been in use >> for 2-3 years now without incident. >> >> Google shows that other folks have hit 'aclocal too many loops' as >> well, and there are suggestions that it might be fixed in a recent >> update to automake.  Scanning the changelog for the latest and >> greatest from gnu.org doesn't show any obvious fixes addressing this >> issue. >> >> Scott >> >> >> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>> BUILDSTDERR: aclocal: error: too many loops >>> BUILDSTDERR: aclocal: Please contact. >>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. >>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 >>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 >>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >>> BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib >>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Sep 27 01:19:32 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 27 Sep 2018 01:19:32 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB287231@ALA-MBD.corp.ad.wrs.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4574F2@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB287231@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5A6E83@fmsmsx117.amr.corp.intel.com> Cindy, do you agree? How long will it take for the patches to be corrected? Team - assuming her answer is "more than a day or two", do we want to hold the release branch creation that long? We're moving the release into day-for-day slip mode... brucej -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Wednesday, September 26, 2018 6:12 PM To: Khalil, Ghada ; Saul Wold ; starlingx-discuss at lists.starlingx.io; Xie, Cindy ; Lin, Shuicheng Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build I agree. Brent -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, September 26, 2018 9:10 PM To: Saul Wold ; starlingx-discuss at lists.starlingx.io; Xie, Cindy ; Lin, Shuicheng Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build Hi Saul, It looks like the first step is for all the 7.5 patches to be re-generated and de-fuzzed. I consider this to be gating the October release. Do you agree? I suggest that this gets addressed in master before the release branch creation. I will add a new task to the CentOS 7.5 rebase story for Cindy's team to work on. I would also like to propose that we continue to place master under code freeze/limited merge and only allow the items we consider gating for October. This would allow us to limit the churn to the next few days. Is this ok with everyone? Thanks, Ghada -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Wednesday, September 26, 2018 7:45 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build On 09/26/2018 02:08 PM, Scott Little wrote: > I have also been investigating another intermittent build error > affecting initscripts. > > https://bugs.launchpad.net/starlingx/+bug/1794611 > > So any given package might be built by rpm-4.11.3, or by rpm-4.14.0. > It's a race with many inputs.  Ideally it shouldn't matter, but it > does.  build-pkgs --serial might reduce the odds, but likely won't > solve it entirely. > Why is this the case in the first place, can't we ensure we only build rpm-4.14.0? > In this case it is a new option that rpm passes to the patch command, > --no-backup-if-mismatch, first introduced by rpm-4.13. > This option has the effect of suppressing the creation of '.orig' files. > > Creation of .orig files are a consequence of applying patches that are > not clean. Unclean patches are ones that require 'fuzzing', i.e. treat > the patch line numbers as approximate, rather than a strict > requirement, just so long as the before/after context seems to be correct. > > Prior to StarlingX, my policy for rebasing patches was that no fuzz is > tolerated in our patches. > > All the work to upgrade to 7.5 has created a lot of fuzzy patches. > Wow, sorry I was not aware that they were all fuzzy patches. > audit-2.8.1-3.el7.tis.2 > bash-4.2.46-30.el7.tis.3 > dhcp-4.2.5-68.el7.centos.1.tis.8 > dnsmasq-2.76-5.el7.tis.6 > drbd-8.4.3-0.tis.6 > facter-2.4.4-4.el7.tis.4 > haproxy-1.5.18-7.el7.tis.7 > initscripts-9.49.41-1.el7.tis.16 > iptables-1.4.21-24.1.el7_5.tis.3 > kubernetes-1.10.0-1.tis.1 > libevent-2.0.21-4.el7.tis.2 > lighttpd-1.4.50-1.el7.tis.6 > logrotate-3.8.6-15.el7.tis.3 > netpbm-10.79.00-7.el7.tis.2 > net-snmp-5.7.2-33.el7_5.2.tis.10 > net-tools-2.0-0.22.20131004git.el7.tis.2 > nfs-utils-1.3.0-0.54.el7.tis.4 > nss-pam-ldapd-0.8.13-16.el7.tis.4 > ntp-4.2.6p5-28.el7.centos.tis.3 > openldap-2.4.44-15.el7_5.tis.8 > openssh-7.4p1-16.el7_4.tis.9 > pam-1.1.8-22.el7.tis.4 > puppet-4.8.2-1.el7.tis.2 > puppet-ceph-2.4.1-1.el7.tis.4 > puppet-horizon-11.5.0-1.el7.tis.1 > python-2.7.5-69.el7_5.tis.3 > python-keyring-5.7.1-1.tis.2 > python-wsme-0.9.2-1.el7.tis.3 > resource-agents-3.9.5-124.el7.tis.12 > rsync-3.1.2-4.el7.tis.2 > shadow-utils-4.1.5.1-24.el7.tis.4 > sudo-1.8.19p2-14.el7_5.tis.3 > watchdog-5.13-11.el7.tis.2 > > So any of these packages might or might not produce unwanted .orig files. > The .orig files might or might not be packaged, or break packaging. > > So there are a number of threads to pull at here. > 1) Are fuzzy patches tolerated.   I vote no.  Sooner or later a fuzzy > patch will be mis-applied and cause us problems. Agreed, when updating patches should be rebased and de-fuzzed. > 2) Can we force rpmbuild within mock to use a consistent policy with > respect to creation of orig files? It would be good to investigate that. > 3) Can we pre-build rpm, such that all packages build against the same > rpm version? Yes, as mentioned above we should use a consistent version. > 4) Are we patching any other low level build tools that have similar > issues?  Possibly explaining ceph?  TBD > Yup more info is needed Sau! > > > On 18-09-26 12:16 PM, Scott Little wrote: >> aclocal 'too many loops' has been popping up sporadically for a week >> or two now.  Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition element >> to this.   It often goes away if you just run build-pkgs a second time. >> >> The second possible element is that build-pkgs is using flags that >> preserve the mock environment between packages.  The goal was to >> avoid reinstalling required packages that are often common across the >> packages we build.   It was a build time speedup that has been in use >> for 2-3 years now without incident. >> >> Google shows that other folks have hit 'aclocal too many loops' as >> well, and there are suggestions that it might be fixed in a recent >> update to automake.  Scanning the changelog for the latest and >> greatest from gnu.org doesn't show any obvious fixes addressing this >> issue. >> >> Scott >> >> >> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>> BUILDSTDERR: aclocal: error: too many loops >>> BUILDSTDERR: aclocal: Please contact. >>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. >>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 >>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 >>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >>> BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib >>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Thu Sep 27 01:20:24 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 26 Sep 2018 20:20:24 -0500 Subject: [Starlingx-discuss] [Release] stx.2018.10 status & next steps In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA3B51E4@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA457443@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB5A6D4B@fmsmsx117.amr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA3B51E4@ALA-MBD.corp.ad.wrs.com> Message-ID: On Wed, Sep 26, 2018 at 7:55 PM, Penney, Don wrote: > One of these open reviews is blocked by a Zuul failure, in the new openstack-tox-docs job, which would be unrelated to the updated > https://review.openstack.org/#/c/605462/ [...] > I don't know if a recheck will work here or not, if it's some transient failure, but it looks like we've got some Zuul jobs that have been in the queue for 7+ hours now. A POST_FAILURE on a job is almost always a failure in the infrastructure of some sort. Whether a recheck is going to be useful depends on what it is. This one does appear to be a job configuration failure, but the cause is not immediately obvious to me... dt -- Dean Troyer dtroyer at gmail.com From dtroyer at gmail.com Thu Sep 27 01:25:56 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 26 Sep 2018 20:25:56 -0500 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5A6E83@fmsmsx117.amr.corp.intel.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4574F2@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB287231@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB5A6E83@fmsmsx117.amr.corp.intel.com> Message-ID: On Wed, Sep 26, 2018 at 8:19 PM, Jones, Bruce E wrote: > Team - assuming her answer is "more than a day or two", do we want to hold the release branch creation that long? We're moving the release into day-for-day slip mode... The tradeoff is how much work it would be to backport that after a branch, and how much testing is invalidated after such a change is backported... If this needs to be completed for testing to begin then it is easy, I suspect that isn't the case though. If this is a build issue it may be release blocking but not branch blocking, provided a build can be expected to be available to begin testing. dt -- Dean Troyer dtroyer at gmail.com From Brent.Rowsell at windriver.com Thu Sep 27 01:30:22 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 27 Sep 2018 01:30:22 +0000 Subject: [Starlingx-discuss] CEPH Based Testing Options In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB2872BF@ALA-MBD.corp.ad.wrs.com> Arce, For a minimal ceph config you will want 5 nodes. - 2 controllers - 2 computes - 3 storage nodes • Dual socket xeon, min 16 cores • Min 64GB RAM • 4 disks preferably SSD’s. 3 for OSD’s, 1 for the root disk The CEPH monitors will run on the controllers and the 1st storage node to provide the quorum of 3. Brent -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Wednesday, September 26, 2018 12:25 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] CEPH Based Testing Options In today's "Weekly StarlingX non-OpenStack Distro" [0] there was a requirement for our validation activities around CEPH so we need your help to learn more about the specific hardware. StarlingX allows a flexible storage options: 1. Linux Logical Volume Manager 2. CEPH 3. External SAN [ CEPH : StarlingX Dedicated Storage ] StarlingX system can be configured as Ceph-backend storage (Controller) and have available N number of Compute and Storage hosts, today we are deploying this as a "Dedicated Storage" configuration [1] : - 2 Controller Nodes - 2 Compute Nodes - 2 Storage Nodes [ CEPH : Homepage Documentation ] Looking at the Hardware Recommendations from CEPH Documentation, they list N number of components including requirements for CPU, RAM and a bunch of storage devices (Hard Disks, SSDs) [2] StarlingX provides this provisioning automatically if "Dedicated Storage" is configuration chosen. [CEPH : Specific Hardware ] Can you please guide us on what does that specific need makes it unique? Is it a hardware? Is it a configuration? Is the mix of both? 1. Is StarlingX "Dedicated Storage" configuration one of the 2 possible CEPH based testing options? 2. Do we need a separate CEPH cluster provisioned including their own OSDs and monitors? 3. Any other? We would appreciate any link to information and architecture to learn more about this request. [0] https://wiki.openstack.org/wiki/StarlingX/Distro [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Dedicated_Storage [2] http://docs.ceph.com/docs/jewel/start/hardware-recommendations/ _______________________________________________ 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 cindy.xie at intel.com Thu Sep 27 01:30:38 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 27 Sep 2018 01:30:38 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4574F2@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB287231@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB5A6E83@fmsmsx117.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B385E2A@SHSMSX104.ccr.corp.intel.com> I think we agreed in yesterday's meeting the build failure is blocking the branch. Whichever issues that we are finding (including fuzzy patches), it should hold off the branching. I really would like to see a successful build from master before a branch can be created. But the impact is to hold off the follow-on feature patches from merging to master. Thx. - cindy -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Thursday, September 27, 2018 9:26 AM To: Jones, Bruce E Cc: Rowsell, Brent ; Khalil, Ghada ; Saul Wold ; starlingx-discuss at lists.starlingx.io; Xie, Cindy ; Lin, Shuicheng Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build On Wed, Sep 26, 2018 at 8:19 PM, Jones, Bruce E wrote: > Team - assuming her answer is "more than a day or two", do we want to hold the release branch creation that long? We're moving the release into day-for-day slip mode... The tradeoff is how much work it would be to backport that after a branch, and how much testing is invalidated after such a change is backported... If this needs to be completed for testing to begin then it is easy, I suspect that isn't the case though. If this is a build issue it may be release blocking but not branch blocking, provided a build can be expected to be available to begin testing. dt -- Dean Troyer dtroyer at gmail.com From shuicheng.lin at intel.com Thu Sep 27 01:23:44 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 27 Sep 2018 01:23:44 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5A6E83@fmsmsx117.amr.corp.intel.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4574F2@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB287231@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB5A6E83@fmsmsx117.amr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C7655382DBD@SHSMSX101.ccr.corp.intel.com> Hi all, I will try to finish the fuzzy correction today. Best Regards Shuicheng -----Original Message----- From: Jones, Bruce E Sent: Thursday, September 27, 2018 9:20 AM To: Rowsell, Brent ; Khalil, Ghada ; Saul Wold ; starlingx-discuss at lists.starlingx.io; Xie, Cindy ; Lin, Shuicheng Subject: RE: [Starlingx-discuss] build-pkgs cannot complete std build Cindy, do you agree? How long will it take for the patches to be corrected? Team - assuming her answer is "more than a day or two", do we want to hold the release branch creation that long? We're moving the release into day-for-day slip mode... brucej -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Wednesday, September 26, 2018 6:12 PM To: Khalil, Ghada ; Saul Wold ; starlingx-discuss at lists.starlingx.io; Xie, Cindy ; Lin, Shuicheng Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build I agree. Brent -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, September 26, 2018 9:10 PM To: Saul Wold ; starlingx-discuss at lists.starlingx.io; Xie, Cindy ; Lin, Shuicheng Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build Hi Saul, It looks like the first step is for all the 7.5 patches to be re-generated and de-fuzzed. I consider this to be gating the October release. Do you agree? I suggest that this gets addressed in master before the release branch creation. I will add a new task to the CentOS 7.5 rebase story for Cindy's team to work on. I would also like to propose that we continue to place master under code freeze/limited merge and only allow the items we consider gating for October. This would allow us to limit the churn to the next few days. Is this ok with everyone? Thanks, Ghada -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Wednesday, September 26, 2018 7:45 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build On 09/26/2018 02:08 PM, Scott Little wrote: > I have also been investigating another intermittent build error > affecting initscripts. > > https://bugs.launchpad.net/starlingx/+bug/1794611 > > So any given package might be built by rpm-4.11.3, or by rpm-4.14.0. > It's a race with many inputs.  Ideally it shouldn't matter, but it > does.  build-pkgs --serial might reduce the odds, but likely won't > solve it entirely. > Why is this the case in the first place, can't we ensure we only build rpm-4.14.0? > In this case it is a new option that rpm passes to the patch command, > --no-backup-if-mismatch, first introduced by rpm-4.13. > This option has the effect of suppressing the creation of '.orig' files. > > Creation of .orig files are a consequence of applying patches that are > not clean. Unclean patches are ones that require 'fuzzing', i.e. treat > the patch line numbers as approximate, rather than a strict > requirement, just so long as the before/after context seems to be correct. > > Prior to StarlingX, my policy for rebasing patches was that no fuzz is > tolerated in our patches. > > All the work to upgrade to 7.5 has created a lot of fuzzy patches. > Wow, sorry I was not aware that they were all fuzzy patches. > audit-2.8.1-3.el7.tis.2 > bash-4.2.46-30.el7.tis.3 > dhcp-4.2.5-68.el7.centos.1.tis.8 > dnsmasq-2.76-5.el7.tis.6 > drbd-8.4.3-0.tis.6 > facter-2.4.4-4.el7.tis.4 > haproxy-1.5.18-7.el7.tis.7 > initscripts-9.49.41-1.el7.tis.16 > iptables-1.4.21-24.1.el7_5.tis.3 > kubernetes-1.10.0-1.tis.1 > libevent-2.0.21-4.el7.tis.2 > lighttpd-1.4.50-1.el7.tis.6 > logrotate-3.8.6-15.el7.tis.3 > netpbm-10.79.00-7.el7.tis.2 > net-snmp-5.7.2-33.el7_5.2.tis.10 > net-tools-2.0-0.22.20131004git.el7.tis.2 > nfs-utils-1.3.0-0.54.el7.tis.4 > nss-pam-ldapd-0.8.13-16.el7.tis.4 > ntp-4.2.6p5-28.el7.centos.tis.3 > openldap-2.4.44-15.el7_5.tis.8 > openssh-7.4p1-16.el7_4.tis.9 > pam-1.1.8-22.el7.tis.4 > puppet-4.8.2-1.el7.tis.2 > puppet-ceph-2.4.1-1.el7.tis.4 > puppet-horizon-11.5.0-1.el7.tis.1 > python-2.7.5-69.el7_5.tis.3 > python-keyring-5.7.1-1.tis.2 > python-wsme-0.9.2-1.el7.tis.3 > resource-agents-3.9.5-124.el7.tis.12 > rsync-3.1.2-4.el7.tis.2 > shadow-utils-4.1.5.1-24.el7.tis.4 > sudo-1.8.19p2-14.el7_5.tis.3 > watchdog-5.13-11.el7.tis.2 > > So any of these packages might or might not produce unwanted .orig files. > The .orig files might or might not be packaged, or break packaging. > > So there are a number of threads to pull at here. > 1) Are fuzzy patches tolerated.   I vote no.  Sooner or later a fuzzy > patch will be mis-applied and cause us problems. Agreed, when updating patches should be rebased and de-fuzzed. > 2) Can we force rpmbuild within mock to use a consistent policy with > respect to creation of orig files? It would be good to investigate that. > 3) Can we pre-build rpm, such that all packages build against the same > rpm version? Yes, as mentioned above we should use a consistent version. > 4) Are we patching any other low level build tools that have similar > issues?  Possibly explaining ceph?  TBD > Yup more info is needed Sau! > > > On 18-09-26 12:16 PM, Scott Little wrote: >> aclocal 'too many loops' has been popping up sporadically for a week >> or two now.  Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition element >> to this.   It often goes away if you just run build-pkgs a second time. >> >> The second possible element is that build-pkgs is using flags that >> preserve the mock environment between packages.  The goal was to >> avoid reinstalling required packages that are often common across the >> packages we build.   It was a build time speedup that has been in use >> for 2-3 years now without incident. >> >> Google shows that other folks have hit 'aclocal too many loops' as >> well, and there are suggestions that it might be fixed in a recent >> update to automake.  Scanning the changelog for the latest and >> greatest from gnu.org doesn't show any obvious fixes addressing this >> issue. >> >> Scott >> >> >> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>> BUILDSTDERR: aclocal: error: too many loops >>> BUILDSTDERR: aclocal: Please contact. >>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. >>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 >>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 >>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >>> BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib >>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Thu Sep 27 01:50:42 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 27 Sep 2018 01:50:42 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds Message-ID: <151EE31B9FCCA54397A757BC674650F0BA457548@ALA-MBD.corp.ad.wrs.com> Erich, Given the failures you are seeing, I re-opened https://bugs.launchpad.net/starlingx/+bug/1790583 (it was still in a Fix Released state even though the original commit was reverted and a new one is currently in review) Austin, I see that you have an update pending for this: https://review.openstack.org/#/c/603983/ But according to Erich, it didn't address the build issue. Can you please investigate further? Thanks, Ghada -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Wednesday, September 26, 2018 7:43 PM To: Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build Trying to get a serial build avoiding the possible mock problems I encounter with this issue: BUILD_AVOIDANCE_URL= /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-srpms-serial --std /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-srpms-serial: line 33: /build-srpms-common.sh: No such file or directory CLEAN_FLAG=0 22:26:39 build-srpms-serial --std 22:26:39 make: all 22:26:40 ===== Build SRPM for 'remote-clients' ===== 22:26:40 PKG_BASE=/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients 22:26:40 WORK_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/stx-clients/remote-clients 22:26:40 RPMBUILD_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/stx-clients/remote-clients/rpmbuild 22:26:40 /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-srpms-serial: line 941: md5sums_from_input_vars: command not found 22:26:40 ERROR: build_dir_spec (943): md5sums_from_input_vars '' '/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients/centos/remote-clients.spec' '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SOURCES/remote-clients' Doing sed -i 's/PARALLEL/SERIAL/g' build-tools/build-srpms-serial fixes this issue. However, after the srpms are created the build-rpm-serial script is unable to find these srpms. See below ######## Wed Sep 26 22:36:34 UTC 2018: build-srpm-serial --std was successful ######## Wed Sep 26 22:36:34 UTC 2018: Launching build-rpms-serial --std /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-rpms-serial --std FORMAL_BUILD=0 modify-build-cfg /localdisk/loadbuild/jenkins-slave/starlingx/std/jenkins-slave-starlingx-tis-r5-pike-std.cfg Nothing to build in '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SRPMS' ######## Wed Sep 26 22:36:35 UTC 2018: build-rpm-serial --std was successful This is reported here: https://bugs.launchpad.net/starlingx/+bug/1790583 I tried this but it didn't work for me: https://review.openstack.org/#/c/603983/ So, for now seems that it's not possible to use serial building. On Wed, 2018-09-26 at 12:16 -0400, Scott Little wrote: > aclocal 'too many loops' has been popping up sporadically for a week > or two now. Possibly 7.5 related. > > I suspect that there is a build order and/or race condition element > to this. It often goes away if you just run build-pkgs a second > time. > > The second possible element is that build-pkgs is using flags that > preserve the mock environment between packages. The goal was to avoid > reinstalling required packages that are often common across the > packages we build. It was a build time speedup that has been in use > for 2-3 years now without incident. > > Google shows that other folks have hit 'aclocal too many loops' as > well, and there are suggestions that it might be fixed in a recent > update to automake. Scanning the changelog for the latest and > greatest from gnu.org doesn't show any obvious fixes addressing this > issue. > > Scott > > > On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: > > BUILDSTDERR: aclocal: error: too many loops > > BUILDSTDERR: aclocal: Please contact . > > BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line > > 662. > > BUILDSTDERR: Automake::Channels::msg('automake', '', 'too > > many loops') called at /usr/share/automake- > > 1.13/Automake/ChannelDefs.pm line 212 > > BUILDSTDERR: Automake::ChannelDefs::prog_error('too many > > loops') called at /usr/bin/aclocal line 1187 > > BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c > > (%build) > > BUILDSTDERR: Macro expanded in comment on line 214: %global > > _libexecdir %{_exec_prefix}/lib > > BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c > > (%build) > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Thu Sep 27 02:26:16 2018 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 26 Sep 2018 19:26:16 -0700 Subject: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA457548@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA457548@ALA-MBD.corp.ad.wrs.com> Message-ID: <97219db6-14e6-f718-0b0d-a27233b3e625@linux.intel.com> On 09/26/2018 06:50 PM, Khalil, Ghada wrote: > Erich, > Given the failures you are seeing, I re-opened https://bugs.launchpad.net/starlingx/+bug/1790583 > (it was still in a Fix Released state even though the original commit was reverted and a new one is currently in review) > > Austin, I see that you have an update pending for this: https://review.openstack.org/#/c/603983/ > But according to Erich, it didn't address the build issue. Can you please investigate further? > OK, I understand Austin's patch now and gave it my +2. I am going to try again with a scratch build now the libvirt bits have merged (or at least I think they have merged) Sau! > Thanks, > Ghada > > -----Original Message----- > From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] > Sent: Wednesday, September 26, 2018 7:43 PM > To: Little, Scott; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build > > Trying to get a serial build avoiding the possible mock problems I encounter with this issue: > > > BUILD_AVOIDANCE_URL= > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-srpms-serial --std > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-srpms-serial: line 33: /build-srpms-common.sh: No such file or directory > CLEAN_FLAG=0 > 22:26:39 build-srpms-serial --std > 22:26:39 make: all > 22:26:40 ===== Build SRPM for 'remote-clients' ===== > 22:26:40 PKG_BASE=/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients > 22:26:40 WORK_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/stx-clients/remote-clients > 22:26:40 RPMBUILD_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/stx-clients/remote-clients/rpmbuild > 22:26:40 /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-srpms-serial: line 941: md5sums_from_input_vars: command not found > 22:26:40 ERROR: build_dir_spec (943): md5sums_from_input_vars '' '/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients/centos/remote-clients.spec' '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SOURCES/remote-clients' > > Doing sed -i 's/PARALLEL/SERIAL/g' build-tools/build-srpms-serial fixes this issue. However, after the srpms are created the build-rpm-serial script is unable to find these srpms. See below > > > ######## Wed Sep 26 22:36:34 UTC 2018: build-srpm-serial --std was successful > > ######## Wed Sep 26 22:36:34 UTC 2018: Launching build-rpms-serial --std > > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/build-rpms-serial --std > FORMAL_BUILD=0 > modify-build-cfg /localdisk/loadbuild/jenkins-slave/starlingx/std/jenkins-slave-starlingx-tis-r5-pike-std.cfg > Nothing to build in '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SRPMS' > > ######## Wed Sep 26 22:36:35 UTC 2018: build-rpm-serial --std was successful > > This is reported here: https://bugs.launchpad.net/starlingx/+bug/1790583 > I tried this but it didn't work for me: https://review.openstack.org/#/c/603983/ > > So, for now seems that it's not possible to use serial building. > > > On Wed, 2018-09-26 at 12:16 -0400, Scott Little wrote: >> aclocal 'too many loops' has been popping up sporadically for a week >> or two now. Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition element >> to this. It often goes away if you just run build-pkgs a second >> time. >> >> The second possible element is that build-pkgs is using flags that >> preserve the mock environment between packages. The goal was to avoid >> reinstalling required packages that are often common across the >> packages we build. It was a build time speedup that has been in use >> for 2-3 years now without incident. >> >> Google shows that other folks have hit 'aclocal too many loops' as >> well, and there are suggestions that it might be fixed in a recent >> update to automake. Scanning the changelog for the latest and >> greatest from gnu.org doesn't show any obvious fixes addressing this >> issue. >> >> Scott >> >> >> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>> BUILDSTDERR: aclocal: error: too many loops >>> BUILDSTDERR: aclocal: Please contact . >>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line >>> 662. >>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too >>> many loops') called at /usr/share/automake- >>> 1.13/Automake/ChannelDefs.pm line 212 >>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many >>> loops') called at /usr/bin/aclocal line 1187 >>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>> (%build) >>> BUILDSTDERR: Macro expanded in comment on line 214: %global >>> _libexecdir %{_exec_prefix}/lib >>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>> (%build) >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Ghada.Khalil at windriver.com Thu Sep 27 03:08:13 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 27 Sep 2018 03:08:13 +0000 Subject: [Starlingx-discuss] POST_FAILURE >> RE: [Release] stx.2018.10 status & next steps Message-ID: <151EE31B9FCCA54397A757BC674650F0BA457594@ALA-MBD.corp.ad.wrs.com> There appears to be multiple examples of this zuul POST_FAILURE: https://review.openstack.org/#/c/605236/ https://review.openstack.org/#/c/605285/ Ghada -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Wednesday, September 26, 2018 9:20 PM To: Penney, Don Cc: Jones, Bruce E; Khalil, Ghada; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Release] stx.2018.10 status & next steps On Wed, Sep 26, 2018 at 7:55 PM, Penney, Don wrote: > One of these open reviews is blocked by a Zuul failure, in the new > openstack-tox-docs job, which would be unrelated to the updated > https://review.openstack.org/#/c/605462/ [...] > I don't know if a recheck will work here or not, if it's some transient failure, but it looks like we've got some Zuul jobs that have been in the queue for 7+ hours now. A POST_FAILURE on a job is almost always a failure in the infrastructure of some sort. Whether a recheck is going to be useful depends on what it is. This one does appear to be a job configuration failure, but the cause is not immediately obvious to me... dt -- Dean Troyer dtroyer at gmail.com From austin.sun at intel.com Thu Sep 27 03:10:38 2018 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 27 Sep 2018 03:10:38 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds In-Reply-To: <97219db6-14e6-f718-0b0d-a27233b3e625@linux.intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA457548@ALA-MBD.corp.ad.wrs.com> <97219db6-14e6-f718-0b0d-a27233b3e625@linux.intel.com> Message-ID: Hi Ghada and Saul: Thanks. I'm working for fuzz patch with Shuicheng now, I will check build serial issue after "fuzz" task. BR Austin Sun. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Thursday, September 27, 2018 10:26 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds On 09/26/2018 06:50 PM, Khalil, Ghada wrote: > Erich, > Given the failures you are seeing, I re-opened > https://bugs.launchpad.net/starlingx/+bug/1790583 > (it was still in a Fix Released state even though the original commit > was reverted and a new one is currently in review) > > Austin, I see that you have an update pending for this: > https://review.openstack.org/#/c/603983/ > But according to Erich, it didn't address the build issue. Can you please investigate further? > OK, I understand Austin's patch now and gave it my +2. I am going to try again with a scratch build now the libvirt bits have merged (or at least I think they have merged) Sau! > Thanks, > Ghada > > -----Original Message----- > From: Cordoba Malibran, Erich > [mailto:erich.cordoba.malibran at intel.com] > Sent: Wednesday, September 26, 2018 7:43 PM > To: Little, Scott; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build > > Trying to get a serial build avoiding the possible mock problems I encounter with this issue: > > > BUILD_AVOIDANCE_URL= > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial --std > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial: line 33: /build-srpms-common.sh: No such file or > directory > CLEAN_FLAG=0 > 22:26:39 build-srpms-serial --std > 22:26:39 make: all > 22:26:40 ===== Build SRPM for 'remote-clients' ===== > 22:26:40 > PKG_BASE=/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx > -clients/remote-clients > 22:26:40 > WORK_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/ > stx-clients/remote-clients > 22:26:40 > RPMBUILD_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/ > stx/stx-clients/remote-clients/rpmbuild > 22:26:40 > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial: line 941: md5sums_from_input_vars: command not found > 22:26:40 ERROR: build_dir_spec (943): md5sums_from_input_vars '' '/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients/centos/remote-clients.spec' '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SOURCES/remote-clients' > > Doing sed -i 's/PARALLEL/SERIAL/g' build-tools/build-srpms-serial > fixes this issue. However, after the srpms are created the > build-rpm-serial script is unable to find these srpms. See below > > > ######## Wed Sep 26 22:36:34 UTC 2018: build-srpm-serial --std was > successful > > ######## Wed Sep 26 22:36:34 UTC 2018: Launching build-rpms-serial > --std > > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-rpms-serial --std > FORMAL_BUILD=0 > modify-build-cfg > /localdisk/loadbuild/jenkins-slave/starlingx/std/jenkins-slave-starlin > gx-tis-r5-pike-std.cfg Nothing to build in > '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SRPMS' > > ######## Wed Sep 26 22:36:35 UTC 2018: build-rpm-serial --std was > successful > > This is reported here: > https://bugs.launchpad.net/starlingx/+bug/1790583 > I tried this but it didn't work for me: > https://review.openstack.org/#/c/603983/ > > So, for now seems that it's not possible to use serial building. > > > On Wed, 2018-09-26 at 12:16 -0400, Scott Little wrote: >> aclocal 'too many loops' has been popping up sporadically for a week >> or two now. Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition element >> to this. It often goes away if you just run build-pkgs a second >> time. >> >> The second possible element is that build-pkgs is using flags that >> preserve the mock environment between packages. The goal was to >> avoid reinstalling required packages that are often common across the >> packages we build. It was a build time speedup that has been in use >> for 2-3 years now without incident. >> >> Google shows that other folks have hit 'aclocal too many loops' as >> well, and there are suggestions that it might be fixed in a recent >> update to automake. Scanning the changelog for the latest and >> greatest from gnu.org doesn't show any obvious fixes addressing this >> issue. >> >> Scott >> >> >> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>> BUILDSTDERR: aclocal: error: too many loops >>> BUILDSTDERR: aclocal: Please contact . >>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line >>> 662. >>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too >>> many loops') called at /usr/share/automake- >>> 1.13/Automake/ChannelDefs.pm line 212 >>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many >>> loops') called at /usr/bin/aclocal line 1187 >>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>> (%build) >>> BUILDSTDERR: Macro expanded in comment on line 214: %global >>> _libexecdir %{_exec_prefix}/lib >>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>> (%build) >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Thu Sep 27 03:36:24 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 27 Sep 2018 03:36:24 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA457548@ALA-MBD.corp.ad.wrs.com> <97219db6-14e6-f718-0b0d-a27233b3e625@linux.intel.com> Message-ID: <19885B5A-74C1-4F38-B775-5417D2948F43@intel.com> I sent the first fix : https://review.openstack.org/#/c/605578/ This is just for the wrong variable name that was blocking the script. On 9/26/18, 10:11 PM, "Sun, Austin" wrote: Hi Ghada and Saul: Thanks. I'm working for fuzz patch with Shuicheng now, I will check build serial issue after "fuzz" task. BR Austin Sun. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Thursday, September 27, 2018 10:26 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds On 09/26/2018 06:50 PM, Khalil, Ghada wrote: > Erich, > Given the failures you are seeing, I re-opened > https://bugs.launchpad.net/starlingx/+bug/1790583 > (it was still in a Fix Released state even though the original commit > was reverted and a new one is currently in review) > > Austin, I see that you have an update pending for this: > https://review.openstack.org/#/c/603983/ > But according to Erich, it didn't address the build issue. Can you please investigate further? > OK, I understand Austin's patch now and gave it my +2. I am going to try again with a scratch build now the libvirt bits have merged (or at least I think they have merged) Sau! > Thanks, > Ghada > > -----Original Message----- > From: Cordoba Malibran, Erich > [mailto:erich.cordoba.malibran at intel.com] > Sent: Wednesday, September 26, 2018 7:43 PM > To: Little, Scott; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build > > Trying to get a serial build avoiding the possible mock problems I encounter with this issue: > > > BUILD_AVOIDANCE_URL= > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial --std > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial: line 33: /build-srpms-common.sh: No such file or > directory > CLEAN_FLAG=0 > 22:26:39 build-srpms-serial --std > 22:26:39 make: all > 22:26:40 ===== Build SRPM for 'remote-clients' ===== > 22:26:40 > PKG_BASE=/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx > -clients/remote-clients > 22:26:40 > WORK_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/ > stx-clients/remote-clients > 22:26:40 > RPMBUILD_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/ > stx/stx-clients/remote-clients/rpmbuild > 22:26:40 > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial: line 941: md5sums_from_input_vars: command not found > 22:26:40 ERROR: build_dir_spec (943): md5sums_from_input_vars '' '/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients/centos/remote-clients.spec' '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SOURCES/remote-clients' > > Doing sed -i 's/PARALLEL/SERIAL/g' build-tools/build-srpms-serial > fixes this issue. However, after the srpms are created the > build-rpm-serial script is unable to find these srpms. See below > > > ######## Wed Sep 26 22:36:34 UTC 2018: build-srpm-serial --std was > successful > > ######## Wed Sep 26 22:36:34 UTC 2018: Launching build-rpms-serial > --std > > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-rpms-serial --std > FORMAL_BUILD=0 > modify-build-cfg > /localdisk/loadbuild/jenkins-slave/starlingx/std/jenkins-slave-starlin > gx-tis-r5-pike-std.cfg Nothing to build in > '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SRPMS' > > ######## Wed Sep 26 22:36:35 UTC 2018: build-rpm-serial --std was > successful > > This is reported here: > https://bugs.launchpad.net/starlingx/+bug/1790583 > I tried this but it didn't work for me: > https://review.openstack.org/#/c/603983/ > > So, for now seems that it's not possible to use serial building. > > > On Wed, 2018-09-26 at 12:16 -0400, Scott Little wrote: >> aclocal 'too many loops' has been popping up sporadically for a week >> or two now. Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition element >> to this. It often goes away if you just run build-pkgs a second >> time. >> >> The second possible element is that build-pkgs is using flags that >> preserve the mock environment between packages. The goal was to >> avoid reinstalling required packages that are often common across the >> packages we build. It was a build time speedup that has been in use >> for 2-3 years now without incident. >> >> Google shows that other folks have hit 'aclocal too many loops' as >> well, and there are suggestions that it might be fixed in a recent >> update to automake. Scanning the changelog for the latest and >> greatest from gnu.org doesn't show any obvious fixes addressing this >> issue. >> >> Scott >> >> >> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>> BUILDSTDERR: aclocal: error: too many loops >>> BUILDSTDERR: aclocal: Please contact . >>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line >>> 662. >>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too >>> many loops') called at /usr/share/automake- >>> 1.13/Automake/ChannelDefs.pm line 212 >>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many >>> loops') called at /usr/bin/aclocal line 1187 >>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>> (%build) >>> BUILDSTDERR: Macro expanded in comment on line 214: %global >>> _libexecdir %{_exec_prefix}/lib >>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>> (%build) >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Thu Sep 27 04:27:41 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 27 Sep 2018 04:27:41 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds In-Reply-To: <19885B5A-74C1-4F38-B775-5417D2948F43@intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA457548@ALA-MBD.corp.ad.wrs.com> <97219db6-14e6-f718-0b0d-a27233b3e625@linux.intel.com> <19885B5A-74C1-4F38-B775-5417D2948F43@intel.com> Message-ID: <575736B5-CF66-4EEF-A9F6-A6A3FE5ACCBF@intel.com> Austin, This worked for me to solve the deleted srpms, just one variable was missing. diff --git a/build-tools/build-srpms-serial b/build-tools/build-srpms-serial index fbdd33c..36cf61b 100755 --- a/build-tools/build-srpms-serial +++ b/build-tools/build-srpms-serial @@ -116,6 +116,7 @@ create_output_dirs () { # create output dirs mkdir -p $MY_BUILD_DIR + mkdir -p $BUILD_ROOT/tmp mkdir -p $MY_SRC_RPM_BUILD_DIR mkdir -p $MY_SRC_RPM_BUILD_DIR/SOURCES mkdir -p $MY_SRC_RPM_BUILD_DIR/SPECS @@ -1235,6 +1236,7 @@ done if [ $ALL -eq 1 ]; then echo echo "Auditing for obsolete srpms" + AUDIT_DIR=$(mktemp -d $MY_WORKSPACE/tmp/$USER-$ME-audit-XXXXXX) PACKAGES_CONSIDERED="" for GIT_ROOT in $GIT_LIST; do for p in $(cat $GIT_ROOT/$PKG_DIRS_FILE 2>> /dev/null); do @@ -1245,7 +1247,7 @@ if [ $ALL -eq 1 ]; then for f in $(find $src_dir/${DISTRO} -name '*.spec' | sort -V); do NAME=$(spec_find_tag Name "$f" 2>> /dev/null) if [ $? -eq 0 ]; then - PACKAGES_CONSIDERED="$PACKAGES_CONSIDERED $NAME" + touch "$AUDIT_DIR/$NAME" fi done if [ -f $src_dir/$SRPM_LIST_PATH ]; then @@ -1279,7 +1281,7 @@ if [ $ALL -eq 1 ]; then if [ -f $ORIG_SRPM_PATH ]; then NAME=$(rpm -q --queryformat '%{NAME}\n' -p $ORIG_SRPM_PATH 2>> /dev/null) if [ $? -eq 0 ]; then - PACKAGES_CONSIDERED="$PACKAGES_CONSIDERED $NAME" + touch "$AUDIT_DIR/$NAME" fi fi done I hope this can helps. -Erich On 9/26/18, 10:39 PM, "Cordoba Malibran, Erich" wrote: I sent the first fix : https://review.openstack.org/#/c/605578/ This is just for the wrong variable name that was blocking the script. On 9/26/18, 10:11 PM, "Sun, Austin" wrote: Hi Ghada and Saul: Thanks. I'm working for fuzz patch with Shuicheng now, I will check build serial issue after "fuzz" task. BR Austin Sun. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Thursday, September 27, 2018 10:26 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds On 09/26/2018 06:50 PM, Khalil, Ghada wrote: > Erich, > Given the failures you are seeing, I re-opened > https://bugs.launchpad.net/starlingx/+bug/1790583 > (it was still in a Fix Released state even though the original commit > was reverted and a new one is currently in review) > > Austin, I see that you have an update pending for this: > https://review.openstack.org/#/c/603983/ > But according to Erich, it didn't address the build issue. Can you please investigate further? > OK, I understand Austin's patch now and gave it my +2. I am going to try again with a scratch build now the libvirt bits have merged (or at least I think they have merged) Sau! > Thanks, > Ghada > > -----Original Message----- > From: Cordoba Malibran, Erich > [mailto:erich.cordoba.malibran at intel.com] > Sent: Wednesday, September 26, 2018 7:43 PM > To: Little, Scott; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build > > Trying to get a serial build avoiding the possible mock problems I encounter with this issue: > > > BUILD_AVOIDANCE_URL= > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial --std > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial: line 33: /build-srpms-common.sh: No such file or > directory > CLEAN_FLAG=0 > 22:26:39 build-srpms-serial --std > 22:26:39 make: all > 22:26:40 ===== Build SRPM for 'remote-clients' ===== > 22:26:40 > PKG_BASE=/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx > -clients/remote-clients > 22:26:40 > WORK_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/ > stx-clients/remote-clients > 22:26:40 > RPMBUILD_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/ > stx/stx-clients/remote-clients/rpmbuild > 22:26:40 > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial: line 941: md5sums_from_input_vars: command not found > 22:26:40 ERROR: build_dir_spec (943): md5sums_from_input_vars '' '/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients/centos/remote-clients.spec' '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SOURCES/remote-clients' > > Doing sed -i 's/PARALLEL/SERIAL/g' build-tools/build-srpms-serial > fixes this issue. However, after the srpms are created the > build-rpm-serial script is unable to find these srpms. See below > > > ######## Wed Sep 26 22:36:34 UTC 2018: build-srpm-serial --std was > successful > > ######## Wed Sep 26 22:36:34 UTC 2018: Launching build-rpms-serial > --std > > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-rpms-serial --std > FORMAL_BUILD=0 > modify-build-cfg > /localdisk/loadbuild/jenkins-slave/starlingx/std/jenkins-slave-starlin > gx-tis-r5-pike-std.cfg Nothing to build in > '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SRPMS' > > ######## Wed Sep 26 22:36:35 UTC 2018: build-rpm-serial --std was > successful > > This is reported here: > https://bugs.launchpad.net/starlingx/+bug/1790583 > I tried this but it didn't work for me: > https://review.openstack.org/#/c/603983/ > > So, for now seems that it's not possible to use serial building. > > > On Wed, 2018-09-26 at 12:16 -0400, Scott Little wrote: >> aclocal 'too many loops' has been popping up sporadically for a week >> or two now. Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition element >> to this. It often goes away if you just run build-pkgs a second >> time. >> >> The second possible element is that build-pkgs is using flags that >> preserve the mock environment between packages. The goal was to >> avoid reinstalling required packages that are often common across the >> packages we build. It was a build time speedup that has been in use >> for 2-3 years now without incident. >> >> Google shows that other folks have hit 'aclocal too many loops' as >> well, and there are suggestions that it might be fixed in a recent >> update to automake. Scanning the changelog for the latest and >> greatest from gnu.org doesn't show any obvious fixes addressing this >> issue. >> >> Scott >> >> >> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>> BUILDSTDERR: aclocal: error: too many loops >>> BUILDSTDERR: aclocal: Please contact . >>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line >>> 662. >>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too >>> many loops') called at /usr/share/automake- >>> 1.13/Automake/ChannelDefs.pm line 212 >>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many >>> loops') called at /usr/bin/aclocal line 1187 >>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>> (%build) >>> BUILDSTDERR: Macro expanded in comment on line 214: %global >>> _libexecdir %{_exec_prefix}/lib >>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>> (%build) >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Thu Sep 27 05:11:08 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 27 Sep 2018 00:11:08 -0500 Subject: [Starlingx-discuss] POST_FAILURE >> RE: [Release] stx.2018.10 status & next steps In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA457594@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA457594@ALA-MBD.corp.ad.wrs.com> Message-ID: On Wed, Sep 26, 2018 at 10:08 PM, Khalil, Ghada wrote: > There appears to be multiple examples of this zuul POST_FAILURE: > https://review.openstack.org/#/c/605236/ > https://review.openstack.org/#/c/605285/ so the actual failure here (all three of these so far) is the tox 'docs' environment is not present in these reviews. Which is normal, what is not is why the docs job is running here when it is not present in .zuul.yaml. These are both present in master so I've rebased all three of these on master and hopefully it will clear. In the morning I'll dig in to why that job is running when it isn't called (could be due to inheriting from OpenStack default jobs)... dt -- Dean Troyer dtroyer at gmail.com From austin.sun at intel.com Thu Sep 27 13:02:34 2018 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 27 Sep 2018 13:02:34 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds In-Reply-To: <575736B5-CF66-4EEF-A9F6-A6A3FE5ACCBF@intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA457548@ALA-MBD.corp.ad.wrs.com> <97219db6-14e6-f718-0b0d-a27233b3e625@linux.intel.com> <19885B5A-74C1-4F38-B775-5417D2948F43@intel.com> <575736B5-CF66-4EEF-A9F6-A6A3FE5ACCBF@intel.com> Message-ID: Hi Erich: Sorry , which variable was missing ? are you using same patch https://review.openstack.org/#/c/603983/ ? Thanks. BR Austin Sun. -----Original Message----- From: Cordoba Malibran, Erich Sent: Thursday, September 27, 2018 12:28 PM To: Sun, Austin ; Saul Wold ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds Austin, This worked for me to solve the deleted srpms, just one variable was missing. diff --git a/build-tools/build-srpms-serial b/build-tools/build-srpms-serial index fbdd33c..36cf61b 100755 --- a/build-tools/build-srpms-serial +++ b/build-tools/build-srpms-serial @@ -116,6 +116,7 @@ create_output_dirs () { # create output dirs mkdir -p $MY_BUILD_DIR + mkdir -p $BUILD_ROOT/tmp mkdir -p $MY_SRC_RPM_BUILD_DIR mkdir -p $MY_SRC_RPM_BUILD_DIR/SOURCES mkdir -p $MY_SRC_RPM_BUILD_DIR/SPECS @@ -1235,6 +1236,7 @@ done if [ $ALL -eq 1 ]; then echo echo "Auditing for obsolete srpms" + AUDIT_DIR=$(mktemp -d $MY_WORKSPACE/tmp/$USER-$ME-audit-XXXXXX) PACKAGES_CONSIDERED="" for GIT_ROOT in $GIT_LIST; do for p in $(cat $GIT_ROOT/$PKG_DIRS_FILE 2>> /dev/null); do @@ -1245,7 +1247,7 @@ if [ $ALL -eq 1 ]; then for f in $(find $src_dir/${DISTRO} -name '*.spec' | sort -V); do NAME=$(spec_find_tag Name "$f" 2>> /dev/null) if [ $? -eq 0 ]; then - PACKAGES_CONSIDERED="$PACKAGES_CONSIDERED $NAME" + touch "$AUDIT_DIR/$NAME" fi done if [ -f $src_dir/$SRPM_LIST_PATH ]; then @@ -1279,7 +1281,7 @@ if [ $ALL -eq 1 ]; then if [ -f $ORIG_SRPM_PATH ]; then NAME=$(rpm -q --queryformat '%{NAME}\n' -p $ORIG_SRPM_PATH 2>> /dev/null) if [ $? -eq 0 ]; then - PACKAGES_CONSIDERED="$PACKAGES_CONSIDERED $NAME" + touch "$AUDIT_DIR/$NAME" fi fi done I hope this can helps. -Erich On 9/26/18, 10:39 PM, "Cordoba Malibran, Erich" wrote: I sent the first fix : https://review.openstack.org/#/c/605578/ This is just for the wrong variable name that was blocking the script. On 9/26/18, 10:11 PM, "Sun, Austin" wrote: Hi Ghada and Saul: Thanks. I'm working for fuzz patch with Shuicheng now, I will check build serial issue after "fuzz" task. BR Austin Sun. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Thursday, September 27, 2018 10:26 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds On 09/26/2018 06:50 PM, Khalil, Ghada wrote: > Erich, > Given the failures you are seeing, I re-opened > https://bugs.launchpad.net/starlingx/+bug/1790583 > (it was still in a Fix Released state even though the original commit > was reverted and a new one is currently in review) > > Austin, I see that you have an update pending for this: > https://review.openstack.org/#/c/603983/ > But according to Erich, it didn't address the build issue. Can you please investigate further? > OK, I understand Austin's patch now and gave it my +2. I am going to try again with a scratch build now the libvirt bits have merged (or at least I think they have merged) Sau! > Thanks, > Ghada > > -----Original Message----- > From: Cordoba Malibran, Erich > [mailto:erich.cordoba.malibran at intel.com] > Sent: Wednesday, September 26, 2018 7:43 PM > To: Little, Scott; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build > > Trying to get a serial build avoiding the possible mock problems I encounter with this issue: > > > BUILD_AVOIDANCE_URL= > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial --std > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial: line 33: /build-srpms-common.sh: No such file or > directory > CLEAN_FLAG=0 > 22:26:39 build-srpms-serial --std > 22:26:39 make: all > 22:26:40 ===== Build SRPM for 'remote-clients' ===== > 22:26:40 > PKG_BASE=/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx > -clients/remote-clients > 22:26:40 > WORK_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/ > stx-clients/remote-clients > 22:26:40 > RPMBUILD_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/ > stx/stx-clients/remote-clients/rpmbuild > 22:26:40 > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-srpms-serial: line 941: md5sums_from_input_vars: command not found > 22:26:40 ERROR: build_dir_spec (943): md5sums_from_input_vars '' '/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients/centos/remote-clients.spec' '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SOURCES/remote-clients' > > Doing sed -i 's/PARALLEL/SERIAL/g' build-tools/build-srpms-serial > fixes this issue. However, after the srpms are created the > build-rpm-serial script is unable to find these srpms. See below > > > ######## Wed Sep 26 22:36:34 UTC 2018: build-srpm-serial --std was > successful > > ######## Wed Sep 26 22:36:34 UTC 2018: Launching build-rpms-serial > --std > > /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil > d-rpms-serial --std > FORMAL_BUILD=0 > modify-build-cfg > /localdisk/loadbuild/jenkins-slave/starlingx/std/jenkins-slave-starlin > gx-tis-r5-pike-std.cfg Nothing to build in > '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SRPMS' > > ######## Wed Sep 26 22:36:35 UTC 2018: build-rpm-serial --std was > successful > > This is reported here: > https://bugs.launchpad.net/starlingx/+bug/1790583 > I tried this but it didn't work for me: > https://review.openstack.org/#/c/603983/ > > So, for now seems that it's not possible to use serial building. > > > On Wed, 2018-09-26 at 12:16 -0400, Scott Little wrote: >> aclocal 'too many loops' has been popping up sporadically for a week >> or two now. Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition element >> to this. It often goes away if you just run build-pkgs a second >> time. >> >> The second possible element is that build-pkgs is using flags that >> preserve the mock environment between packages. The goal was to >> avoid reinstalling required packages that are often common across the >> packages we build. It was a build time speedup that has been in use >> for 2-3 years now without incident. >> >> Google shows that other folks have hit 'aclocal too many loops' as >> well, and there are suggestions that it might be fixed in a recent >> update to automake. Scanning the changelog for the latest and >> greatest from gnu.org doesn't show any obvious fixes addressing this >> issue. >> >> Scott >> >> >> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>> BUILDSTDERR: aclocal: error: too many loops >>> BUILDSTDERR: aclocal: Please contact . >>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line >>> 662. >>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too >>> many loops') called at /usr/share/automake- >>> 1.13/Automake/ChannelDefs.pm line 212 >>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many >>> loops') called at /usr/bin/aclocal line 1187 >>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>> (%build) >>> BUILDSTDERR: Macro expanded in comment on line 214: %global >>> _libexecdir %{_exec_prefix}/lib >>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>> (%build) >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From shuicheng.lin at intel.com Thu Sep 27 14:24:50 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 27 Sep 2018 14:24:50 +0000 Subject: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm Message-ID: <9700A18779F35F49AF027300A49E7C76553830F7@SHSMSX101.ccr.corp.intel.com> Hi all, Here is the patch list to de-fuzz the patches in CentOS7.5 upgrade task. https://review.openstack.org/#/q/topic:patch_fuzz+(status:open+OR+status:merged) I notice there are some other src rpms also have the fuzzy issue. Will handle them later. Also, I find some SRC RPM itself has the fuzzy issue, such as openldap/rsync/netpbm/openssh etc. So we cannot eliminate all fuzzy issue just by rebase ourselves patches. Best Regards Shuicheng From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, September 27, 2018 5:08 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build I have also been investigating another intermittent build error affecting initscripts. https://bugs.launchpad.net/starlingx/+bug/1794611 So any given package might be built by rpm-4.11.3, or by rpm-4.14.0. It's a race with many inputs. Ideally it shouldn't matter, but it does. build-pkgs --serial might reduce the odds, but likely won't solve it entirely. In this case it is a new option that rpm passes to the patch command, --no-backup-if-mismatch, first introduced by rpm-4.13. This option has the effect of suppressing the creation of '.orig' files. Creation of .orig files are a consequence of applying patches that are not clean. Unclean patches are ones that require 'fuzzing', i.e. treat the patch line numbers as approximate, rather than a strict requirement, just so long as the before/after context seems to be correct. Prior to StarlingX, my policy for rebasing patches was that no fuzz is tolerated in our patches. All the work to upgrade to 7.5 has created a lot of fuzzy patches. audit-2.8.1-3.el7.tis.2 bash-4.2.46-30.el7.tis.3 dhcp-4.2.5-68.el7.centos.1.tis.8 dnsmasq-2.76-5.el7.tis.6 drbd-8.4.3-0.tis.6 facter-2.4.4-4.el7.tis.4 haproxy-1.5.18-7.el7.tis.7 initscripts-9.49.41-1.el7.tis.16 iptables-1.4.21-24.1.el7_5.tis.3 kubernetes-1.10.0-1.tis.1 libevent-2.0.21-4.el7.tis.2 lighttpd-1.4.50-1.el7.tis.6 logrotate-3.8.6-15.el7.tis.3 netpbm-10.79.00-7.el7.tis.2 net-snmp-5.7.2-33.el7_5.2.tis.10 net-tools-2.0-0.22.20131004git.el7.tis.2 nfs-utils-1.3.0-0.54.el7.tis.4 nss-pam-ldapd-0.8.13-16.el7.tis.4 ntp-4.2.6p5-28.el7.centos.tis.3 openldap-2.4.44-15.el7_5.tis.8 openssh-7.4p1-16.el7_4.tis.9 pam-1.1.8-22.el7.tis.4 puppet-4.8.2-1.el7.tis.2 puppet-ceph-2.4.1-1.el7.tis.4 puppet-horizon-11.5.0-1.el7.tis.1 python-2.7.5-69.el7_5.tis.3 python-keyring-5.7.1-1.tis.2 python-wsme-0.9.2-1.el7.tis.3 resource-agents-3.9.5-124.el7.tis.12 rsync-3.1.2-4.el7.tis.2 shadow-utils-4.1.5.1-24.el7.tis.4 sudo-1.8.19p2-14.el7_5.tis.3 watchdog-5.13-11.el7.tis.2 So any of these packages might or might not produce unwanted .orig files. The .orig files might or might not be packaged, or break packaging. So there are a number of threads to pull at here. 1) Are fuzzy patches tolerated. I vote no. Sooner or later a fuzzy patch will be mis-applied and cause us problems. 2) Can we force rpmbuild within mock to use a consistent policy with respect to creation of orig files? 3) Can we pre-build rpm, such that all packages build against the same rpm version? 4) Are we patching any other low level build tools that have similar issues? Possibly explaining ceph? TBD On 18-09-26 12:16 PM, Scott Little wrote: aclocal 'too many loops' has been popping up sporadically for a week or two now. Possibly 7.5 related. I suspect that there is a build order and/or race condition element to this. It often goes away if you just run build-pkgs a second time. The second possible element is that build-pkgs is using flags that preserve the mock environment between packages. The goal was to avoid reinstalling required packages that are often common across the packages we build. It was a build time speedup that has been in use for 2-3 years now without incident. Google shows that other folks have hit 'aclocal too many loops' as well, and there are suggestions that it might be fixed in a recent update to automake. Scanning the changelog for the latest and greatest from gnu.org doesn't show any obvious fixes addressing this issue. Scott On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: BUILDSTDERR: aclocal: error: too many loops BUILDSTDERR: aclocal: Please contact . BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) _______________________________________________ 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 Thu Sep 27 14:27:52 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 27 Sep 2018 10:27:52 -0400 Subject: [Starlingx-discuss] openstack-ras build failure Message-ID: Any 'repo sync' after 2018-09-26 22:00:00 UTC will likely see a build failure in openstack-ras. The fix was delivered 2018-09-27 14:20:00 UTC. Sorry for the inconvenience.  It's hard to co-ordinate multi git updates that span both openstack and github. Scott From hazzim.i.anaya.casas at intel.com Thu Sep 27 14:51:41 2018 From: hazzim.i.anaya.casas at intel.com (Anaya casas, Hazzim I) Date: Thu, 27 Sep 2018 14:51:41 +0000 Subject: [Starlingx-discuss] CEPH Based Testing Options In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB2872BF@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB2872BF@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Brent, at this moment the storage servers have less disks, but for today EOD I could try to get the disk that are missing and fulfill the requirements. On Sep 26, 2018, at 20:30, Rowsell, Brent > wrote: Arce, For a minimal ceph config you will want 5 nodes. - 2 controllers - 2 computes - 3 storage nodes * Dual socket xeon, min 16 cores * Min 64GB RAM * 4 disks preferably SSD’s. 3 for OSD’s, 1 for the root disk The CEPH monitors will run on the controllers and the 1st storage node to provide the quorum of 3. Brent -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Wednesday, September 26, 2018 12:25 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] CEPH Based Testing Options In today's "Weekly StarlingX non-OpenStack Distro" [0] there was a requirement for our validation activities around CEPH so we need your help to learn more about the specific hardware. StarlingX allows a flexible storage options: 1. Linux Logical Volume Manager 2. CEPH 3. External SAN [ CEPH : StarlingX Dedicated Storage ] StarlingX system can be configured as Ceph-backend storage (Controller) and have available N number of Compute and Storage hosts, today we are deploying this as a "Dedicated Storage" configuration [1] : - 2 Controller Nodes - 2 Compute Nodes - 2 Storage Nodes [ CEPH : Homepage Documentation ] Looking at the Hardware Recommendations from CEPH Documentation, they list N number of components including requirements for CPU, RAM and a bunch of storage devices (Hard Disks, SSDs) [2] StarlingX provides this provisioning automatically if "Dedicated Storage" is configuration chosen. [CEPH : Specific Hardware ] Can you please guide us on what does that specific need makes it unique? Is it a hardware? Is it a configuration? Is the mix of both? 1. Is StarlingX "Dedicated Storage" configuration one of the 2 possible CEPH based testing options? 2. Do we need a separate CEPH cluster provisioned including their own OSDs and monitors? 3. Any other? We would appreciate any link to information and architecture to learn more about this request. [0] https://wiki.openstack.org/wiki/StarlingX/Distro [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Dedicated_Storage [2] http://docs.ceph.com/docs/jewel/start/hardware-recommendations/ _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry at openstack.org Thu Sep 27 15:13:18 2018 From: thierry at openstack.org (Thierry Carrez) Date: Thu, 27 Sep 2018 17:13:18 +0200 Subject: [Starlingx-discuss] StarlingX Initial Governance Message-ID: <0309b193-6b70-00d3-9ac4-053eb4f28fd4@openstack.org> Hi everyone, I reread the Governance document[1] and found an inconsistency we'll likely want to address before the initial TSC formally blesses it: In "Technical Steering Committee": > It will be comprised of 7 members who will be appointed at Launch but fully elected by the Contributors within the first year then: > In April 2020, the remaining 4 seats are up for election "appointed at Launch" is a bit vague, I would use "initially appointed" (which would start the clock to when the TSC is fully formed). But more importantly, "fully elected by the Contributors within the first year" is at odds with still having appointed members around in March, 2020. The date or the period needs to be adjusted to match. We'll also likely want to clarify initial terms for the non-WR and non-Intel initial TSC members. One option is to appoint one of them with a short term, and the other two with long terms. Another option would be to randomly select the short one (like for the WR and Intel initially-appointed seats) Finally, I would suggest saying that if somone steps down from their TSC seat, their seat should automatically be up for election at the next round. So imagine someone that is initially appointed for a year, stepping down after 4 months: their seat would be up for reelection, which would make the first election determine 4 seats instead of just 3. That will facilitate keeping an active TSC with a limited number of stale members. That level of subtlety could be conveyed through a separate document that details the corner cases of the election process, if you find it too distracting for the Governance document. [1] https://wiki.openstack.org/wiki/Starlingx/Initial_Governance -- Thierry Carrez (ttx) From scott.little at windriver.com Thu Sep 27 15:16:47 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 27 Sep 2018 11:16:47 -0400 Subject: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA457548@ALA-MBD.corp.ad.wrs.com> <97219db6-14e6-f718-0b0d-a27233b3e625@linux.intel.com> Message-ID: <4c04047c-972c-8a40-5283-1fcd4f70a8df@windriver.com> Fix posted in ... https://review.openstack.org/605775 On 18-09-26 11:10 PM, Sun, Austin wrote: > Hi Ghada and Saul: > Thanks. I'm working for fuzz patch with Shuicheng now, I will check build serial issue after "fuzz" task. > > BR > Austin Sun. > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Thursday, September 27, 2018 10:26 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds > > > > On 09/26/2018 06:50 PM, Khalil, Ghada wrote: >> Erich, >> Given the failures you are seeing, I re-opened >> https://bugs.launchpad.net/starlingx/+bug/1790583 >> (it was still in a Fix Released state even though the original commit >> was reverted and a new one is currently in review) >> >> Austin, I see that you have an update pending for this: >> https://review.openstack.org/#/c/603983/ >> But according to Erich, it didn't address the build issue. Can you please investigate further? >> > OK, I understand Austin's patch now and gave it my +2. > > I am going to try again with a scratch build now the libvirt bits have merged (or at least I think they have merged) > > Sau! >> Thanks, >> Ghada >> >> -----Original Message----- >> From: Cordoba Malibran, Erich >> [mailto:erich.cordoba.malibran at intel.com] >> Sent: Wednesday, September 26, 2018 7:43 PM >> To: Little, Scott; starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build >> >> Trying to get a serial build avoiding the possible mock problems I encounter with this issue: >> >> >> BUILD_AVOIDANCE_URL= >> /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil >> d-srpms-serial --std >> /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil >> d-srpms-serial: line 33: /build-srpms-common.sh: No such file or >> directory >> CLEAN_FLAG=0 >> 22:26:39 build-srpms-serial --std >> 22:26:39 make: all >> 22:26:40 ===== Build SRPM for 'remote-clients' ===== >> 22:26:40 >> PKG_BASE=/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx >> -clients/remote-clients >> 22:26:40 >> WORK_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/ >> stx-clients/remote-clients >> 22:26:40 >> RPMBUILD_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/ >> stx/stx-clients/remote-clients/rpmbuild >> 22:26:40 >> /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil >> d-srpms-serial: line 941: md5sums_from_input_vars: command not found >> 22:26:40 ERROR: build_dir_spec (943): md5sums_from_input_vars '' '/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients/centos/remote-clients.spec' '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SOURCES/remote-clients' >> >> Doing sed -i 's/PARALLEL/SERIAL/g' build-tools/build-srpms-serial >> fixes this issue. However, after the srpms are created the >> build-rpm-serial script is unable to find these srpms. See below >> >> >> ######## Wed Sep 26 22:36:34 UTC 2018: build-srpm-serial --std was >> successful >> >> ######## Wed Sep 26 22:36:34 UTC 2018: Launching build-rpms-serial >> --std >> >> /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil >> d-rpms-serial --std >> FORMAL_BUILD=0 >> modify-build-cfg >> /localdisk/loadbuild/jenkins-slave/starlingx/std/jenkins-slave-starlin >> gx-tis-r5-pike-std.cfg Nothing to build in >> '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SRPMS' >> >> ######## Wed Sep 26 22:36:35 UTC 2018: build-rpm-serial --std was >> successful >> >> This is reported here: >> https://bugs.launchpad.net/starlingx/+bug/1790583 >> I tried this but it didn't work for me: >> https://review.openstack.org/#/c/603983/ >> >> So, for now seems that it's not possible to use serial building. >> >> >> On Wed, 2018-09-26 at 12:16 -0400, Scott Little wrote: >>> aclocal 'too many loops' has been popping up sporadically for a week >>> or two now. Possibly 7.5 related. >>> >>> I suspect that there is a build order and/or race condition element >>> to this. It often goes away if you just run build-pkgs a second >>> time. >>> >>> The second possible element is that build-pkgs is using flags that >>> preserve the mock environment between packages. The goal was to >>> avoid reinstalling required packages that are often common across the >>> packages we build. It was a build time speedup that has been in use >>> for 2-3 years now without incident. >>> >>> Google shows that other folks have hit 'aclocal too many loops' as >>> well, and there are suggestions that it might be fixed in a recent >>> update to automake. Scanning the changelog for the latest and >>> greatest from gnu.org doesn't show any obvious fixes addressing this >>> issue. >>> >>> Scott >>> >>> >>> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>>> BUILDSTDERR: aclocal: error: too many loops >>>> BUILDSTDERR: aclocal: Please contact . >>>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line >>>> 662. >>>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too >>>> many loops') called at /usr/share/automake- >>>> 1.13/Automake/ChannelDefs.pm line 212 >>>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many >>>> loops') called at /usr/bin/aclocal line 1187 >>>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>>> (%build) >>>> BUILDSTDERR: Macro expanded in comment on line 214: %global >>>> _libexecdir %{_exec_prefix}/lib >>>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>>> (%build) >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From claire at openstack.org Thu Sep 27 15:21:00 2018 From: claire at openstack.org (Claire Massey) Date: Thu, 27 Sep 2018 10:21:00 -0500 Subject: [Starlingx-discuss] StarlingX Initial Governance In-Reply-To: <0309b193-6b70-00d3-9ac4-053eb4f28fd4@openstack.org> References: <0309b193-6b70-00d3-9ac4-053eb4f28fd4@openstack.org> Message-ID: <2A0287E6-6C87-49D8-A896-D0D663ECF8C7@openstack.org> Hi all, I agree with Thierry and think that in order to encourage growth for the project, the first election period should to be adjusted. The next several months will be a critical time for StarlingX to welcome diverse engagement. From what we’ve experienced while launching other projects, like Kata Containers for example, new companies that are interested in engaging with the project for the first time are also very interested in having the opportunity to be elected to the technical leadership body within a reasonable amount of time. The opportunity to contribute to the project and possibly earn an elected seat early on in the life of the project can be very motivating for new companies that want to get involved. Based on the current StarlingX election timeline shown in the governance documentation[1], September 2019 is the soonest date when a new person would be able to be elected to the TSC. I personally think that waiting an entire year is just too long and may discourage new contributors from getting involved in the short-term. I recommend that instead of waiting a full year to hold the first election, that it's held sooner, in *May 2019*, which is eight months from now. The planned StarlingX release cadence and schedule[2] shows that the next two releases are timed to happen in March and July 2019, so hosting the first election between those two releases, in May 2019, could work well. [1] https://wiki.openstack.org/wiki/Starlingx/Initial_Governance#Technical_Steering_Committee [2] https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Cadence_and_Schedule Thanks, Claire > On Sep 27, 2018, at 10:13 AM, Thierry Carrez wrote: > > Hi everyone, > > I reread the Governance document[1] and found an inconsistency we'll likely want to address before the initial TSC formally blesses it: > > In "Technical Steering Committee": >> It will be comprised of 7 members who will be appointed at Launch but fully elected by the Contributors within the first year > > then: >> In April 2020, the remaining 4 seats are up for election > > "appointed at Launch" is a bit vague, I would use "initially appointed" (which would start the clock to when the TSC is fully formed). But more importantly, "fully elected by the Contributors within the first year" is at odds with still having appointed members around in March, 2020. The date or the period needs to be adjusted to match. > > We'll also likely want to clarify initial terms for the non-WR and non-Intel initial TSC members. One option is to appoint one of them with a short term, and the other two with long terms. Another option would be to randomly select the short one (like for the WR and Intel initially-appointed seats) > > Finally, I would suggest saying that if somone steps down from their TSC seat, their seat should automatically be up for election at the next round. So imagine someone that is initially appointed for a year, stepping down after 4 months: their seat would be up for reelection, which would make the first election determine 4 seats instead of just 3. That will facilitate keeping an active TSC with a limited number of stale members. > > That level of subtlety could be conveyed through a separate document that details the corner cases of the election process, if you find it too distracting for the Governance document. > > [1] https://wiki.openstack.org/wiki/Starlingx/Initial_Governance > > -- > Thierry Carrez (ttx) > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Thu Sep 27 15:20:21 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 27 Sep 2018 11:20:21 -0400 Subject: [Starlingx-discuss] build-pkgs cannot complete std build >> serial builds In-Reply-To: <4c04047c-972c-8a40-5283-1fcd4f70a8df@windriver.com> References: <151EE31B9FCCA54397A757BC674650F0BA457548@ALA-MBD.corp.ad.wrs.com> <97219db6-14e6-f718-0b0d-a27233b3e625@linux.intel.com> <4c04047c-972c-8a40-5283-1fcd4f70a8df@windriver.com> Message-ID: <88e380b7-debd-7037-220a-eb508bbefdac@windriver.com> Abandoned.  Erich beat me to it. Scott On 18-09-27 11:16 AM, Scott Little wrote: > Fix posted in ... > > https://review.openstack.org/605775 > > > > On 18-09-26 11:10 PM, Sun, Austin wrote: >> Hi Ghada and Saul: >>      Thanks.  I'm working for fuzz patch with Shuicheng now,  I will >> check build serial issue after "fuzz" task. >> >> BR >> Austin Sun. >> >> -----Original Message----- >> From: Saul Wold [mailto:sgw at linux.intel.com] >> Sent: Thursday, September 27, 2018 10:26 AM >> To: starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build >> >> serial builds >> >> >> >> On 09/26/2018 06:50 PM, Khalil, Ghada wrote: >>> Erich, >>> Given the failures you are seeing, I re-opened >>> https://bugs.launchpad.net/starlingx/+bug/1790583 >>> (it was still in a Fix Released state even though the original commit >>> was reverted and a new one is currently in review) >>> >>> Austin, I see that you have an update pending for this: >>> https://review.openstack.org/#/c/603983/ >>> But according to Erich, it didn't address the build issue. Can you >>> please investigate further? >>> >> OK, I understand Austin's patch now and gave it my +2. >> >> I am going to try again with a scratch build now the libvirt bits >> have merged (or at least I think they have merged) >> >> Sau! >>> Thanks, >>> Ghada >>> >>> -----Original Message----- >>> From: Cordoba Malibran, Erich >>> [mailto:erich.cordoba.malibran at intel.com] >>> Sent: Wednesday, September 26, 2018 7:43 PM >>> To: Little, Scott; starlingx-discuss at lists.starlingx.io >>> Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build >>> >>> Trying to get a serial build avoiding the possible mock problems I >>> encounter with this issue: >>> >>> >>> BUILD_AVOIDANCE_URL= >>> /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil >>> d-srpms-serial --std >>> /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil >>> d-srpms-serial: line 33: /build-srpms-common.sh: No such file or >>> directory >>> CLEAN_FLAG=0 >>> 22:26:39 build-srpms-serial --std >>> 22:26:39 make: all >>> 22:26:40 ===== Build SRPM for 'remote-clients' ===== >>> 22:26:40 >>> PKG_BASE=/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx >>> -clients/remote-clients >>> 22:26:40 >>> WORK_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/stx/ >>> stx-clients/remote-clients >>> 22:26:40 >>> RPMBUILD_BASE=/localdisk/loadbuild/jenkins-slave/starlingx/std/inputs/ >>> stx/stx-clients/remote-clients/rpmbuild >>> 22:26:40 >>> /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil >>> d-srpms-serial: line 941: md5sums_from_input_vars: command not found >>> 22:26:40 ERROR: build_dir_spec (943): md5sums_from_input_vars '' >>> '/localdisk/designer/jenkins-slave/starlingx/cgcs-root/stx/stx-clients/remote-clients/centos/remote-clients.spec' >>> '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SOURCES/remote-clients' >>> >>> >>> Doing sed -i 's/PARALLEL/SERIAL/g' build-tools/build-srpms-serial >>> fixes this issue. However, after the srpms are created the >>> build-rpm-serial script is unable to find these srpms. See below >>> >>> >>> ######## Wed Sep 26 22:36:34 UTC 2018: build-srpm-serial --std was >>> successful >>> ######## Wed Sep 26 22:36:34 UTC 2018: Launching build-rpms-serial >>> --std >>> /localdisk/designer/jenkins-slave/starlingx/cgcs-root/build-tools/buil >>> d-rpms-serial --std >>> FORMAL_BUILD=0 >>> modify-build-cfg >>> /localdisk/loadbuild/jenkins-slave/starlingx/std/jenkins-slave-starlin >>> gx-tis-r5-pike-std.cfg Nothing to build in >>> '/localdisk/loadbuild/jenkins-slave/starlingx/std/rpmbuild/SRPMS' >>> ######## Wed Sep 26 22:36:35 UTC 2018: build-rpm-serial --std was >>> successful >>> >>> This is reported here: >>> https://bugs.launchpad.net/starlingx/+bug/1790583 >>> I tried this but it didn't work for me: >>> https://review.openstack.org/#/c/603983/ >>> >>> So, for now seems that it's not possible to use serial building. >>> >>> >>> On Wed, 2018-09-26 at 12:16 -0400, Scott Little wrote: >>>> aclocal 'too many loops' has been popping up sporadically for a week >>>> or two now.  Possibly 7.5 related. >>>> >>>> I suspect that there is a build order and/or race condition element >>>> to this.   It often goes away if you just run build-pkgs a second >>>> time. >>>> >>>> The second possible element is that build-pkgs is using flags that >>>> preserve the mock environment between packages.  The goal was to >>>> avoid reinstalling required packages that are often common across the >>>> packages we build.   It was a build time speedup that has been in use >>>> for 2-3 years now without incident. >>>> >>>> Google shows that other folks have hit 'aclocal too many loops' as >>>> well, and there are suggestions that it might be fixed in a recent >>>> update to automake.  Scanning the changelog for the latest and >>>> greatest from gnu.org doesn't show any obvious fixes addressing this >>>> issue. >>>> >>>> Scott >>>> >>>> >>>> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>>>> BUILDSTDERR: aclocal: error: too many loops >>>>> BUILDSTDERR: aclocal: Please contact . >>>>> BUILDSTDERR:  at /usr/share/automake-1.13/Automake/Channels.pm line >>>>> 662. >>>>> BUILDSTDERR:     Automake::Channels::msg('automake', '', 'too >>>>> many loops') called at /usr/share/automake- >>>>> 1.13/Automake/ChannelDefs.pm line 212 >>>>> BUILDSTDERR:     Automake::ChannelDefs::prog_error('too many >>>>> loops') called at /usr/bin/aclocal line 1187 >>>>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>>>> (%build) >>>>> BUILDSTDERR:     Macro expanded in comment on line 214: %global >>>>> _libexecdir %{_exec_prefix}/lib >>>>> BUILDSTDERR:     Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>>>> (%build) >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Thu Sep 27 15:23:35 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 27 Sep 2018 15:23:35 +0000 Subject: [Starlingx-discuss] stx.2018.10 code freeze status Message-ID: <151EE31B9FCCA54397A757BC674650F0BA457853@ALA-MBD.corp.ad.wrs.com> Hello all, The starlingx master branch is under a "limited" merge window. This is a reminder to core reviewers NOT to workflow + 1 any commits that don't fall under the following categories: - CentOS 7.5 patch de-fuzzing: https://review.openstack.org/#/q/topic:patch_fuzz+(status:open+OR+status:merged) - Documentation updates required https://review.openstack.org/#/q/status:open+branch:master+topic:documentation-baseline Build-Related Bugs - build-srpms-serial is broken: https://bugs.launchpad.net/starlingx/+bug/1790583 Looking for Austin, Erich & Saul to summarize the status. There are two proposed commits: one from Austin & one from Erich. - build-pkgs cannot complete std build: https://bugs.launchpad.net/starlingx/+bug/1791127 Needs re-test after the CentOS 7.5 patch de-fuzzing. Any other updates on this one? - Corrupt mirror causes missing lshell src rpm: https://bugs.launchpad.net/starlingx/+bug/1793615 This one just got re-opened by Erich. I will let him comment on it further Is anyone else aware of any other serious issues that should gate the branch creation for the October release? Regards, Ghada From scott.little at windriver.com Thu Sep 27 15:24:17 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 27 Sep 2018 11:24:17 -0400 Subject: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm In-Reply-To: <9700A18779F35F49AF027300A49E7C76553830F7@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76553830F7@SHSMSX101.ccr.corp.intel.com> Message-ID: <33b41902-d812-709a-c77a-dc902b5715d7@windriver.com> Yes, I've seen some upstream packages that ship from CentOS or EL7 with fuzzy patches.  Can't do much about that. My list might include packages where the only fuzzy patches are those coming from CentOS.  We'll have to sort through them by hand I think. Scott On 18-09-27 10:24 AM, Lin, Shuicheng wrote: > > Hi all, > > Here is the patch list to de-fuzz the patches in CentOS7.5 upgrade task. > > https://review.openstack.org/#/q/topic:patch_fuzz+(status:open+OR+status:merged) > > > I notice there are some other src rpms also have the fuzzy issue. Will > handle them later. > > Also, I find some SRC RPM itself has the fuzzy issue, such as > openldap/rsync/netpbm/openssh etc. > > So we cannot eliminate all fuzzy issue just by rebase ourselves patches. > > Best Regards > > Shuicheng > > *From:*Scott Little [mailto:scott.little at windriver.com] > *Sent:* Thursday, September 27, 2018 5:08 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] build-pkgs cannot complete std build > > I have also been investigating another intermittent build error > affecting initscripts. > > https://bugs.launchpad.net/starlingx/+bug/1794611 > > So any given package might be built by rpm-4.11.3, or by rpm-4.14.0.  > It's a race with many inputs.  Ideally it shouldn't matter, but it > does.  build-pkgs --serial might reduce the odds, but likely won't > solve it entirely. > > In this case it is a new option that rpm passes to the patch command, > --no-backup-if-mismatch, first introduced by rpm-4.13. > This option has the effect of suppressing the creation of '.orig' files. > > Creation of .orig files are a consequence of applying patches that are > not clean. Unclean patches are ones that require 'fuzzing', i.e. treat > the patch line numbers as approximate, rather than a strict > requirement, just so long as the before/after context seems to be correct. > > Prior to StarlingX, my policy for rebasing patches was that no fuzz is > tolerated in our patches. > > All the work to upgrade to 7.5 has created a lot of fuzzy patches. > > audit-2.8.1-3.el7.tis.2 > bash-4.2.46-30.el7.tis.3 > dhcp-4.2.5-68.el7.centos.1.tis.8 > dnsmasq-2.76-5.el7.tis.6 > drbd-8.4.3-0.tis.6 > facter-2.4.4-4.el7.tis.4 > haproxy-1.5.18-7.el7.tis.7 > initscripts-9.49.41-1.el7.tis.16 > iptables-1.4.21-24.1.el7_5.tis.3 > kubernetes-1.10.0-1.tis.1 > libevent-2.0.21-4.el7.tis.2 > lighttpd-1.4.50-1.el7.tis.6 > logrotate-3.8.6-15.el7.tis.3 > netpbm-10.79.00-7.el7.tis.2 > net-snmp-5.7.2-33.el7_5.2.tis.10 > net-tools-2.0-0.22.20131004git.el7.tis.2 > nfs-utils-1.3.0-0.54.el7.tis.4 > nss-pam-ldapd-0.8.13-16.el7.tis.4 > ntp-4.2.6p5-28.el7.centos.tis.3 > openldap-2.4.44-15.el7_5.tis.8 > openssh-7.4p1-16.el7_4.tis.9 > pam-1.1.8-22.el7.tis.4 > puppet-4.8.2-1.el7.tis.2 > puppet-ceph-2.4.1-1.el7.tis.4 > puppet-horizon-11.5.0-1.el7.tis.1 > python-2.7.5-69.el7_5.tis.3 > python-keyring-5.7.1-1.tis.2 > python-wsme-0.9.2-1.el7.tis.3 > resource-agents-3.9.5-124.el7.tis.12 > rsync-3.1.2-4.el7.tis.2 > shadow-utils-4.1.5.1-24.el7.tis.4 > sudo-1.8.19p2-14.el7_5.tis.3 > watchdog-5.13-11.el7.tis.2 > > So any of these packages might or might not produce unwanted .orig files. > The .orig files might or might not be packaged, or break packaging. > > So there are a number of threads to pull at here. > 1) Are fuzzy patches tolerated.   I vote no.  Sooner or later a fuzzy > patch will be mis-applied and cause us problems. > 2) Can we force rpmbuild within mock to use a consistent policy with > respect to creation of orig files? > 3) Can we pre-build rpm, such that all packages build against the same > rpm version? > 4) Are we patching any other low level build tools that have similar > issues?  Possibly explaining ceph?  TBD > > > > On 18-09-26 12:16 PM, Scott Little wrote: > > aclocal 'too many loops' has been popping up sporadically for a > week or two now.  Possibly 7.5 related. > > I suspect that there is a build order and/or race condition > element to this.   It often goes away if you just run build-pkgs a > second time. > > The second possible element is that build-pkgs is using flags that > preserve the mock environment between packages.  The goal was to > avoid reinstalling required packages that are often common across > the packages we build.   It was a build time speedup that has been > in use for 2-3 years now without incident. > > Google shows that other folks have hit 'aclocal too many loops' as > well, and there are suggestions that it might be fixed in a recent > update to automake.  Scanning the changelog for the latest and > greatest from gnu.org doesn't show any obvious fixes addressing > this issue. > > Scott > > > On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: > > BUILDSTDERR: aclocal: error: too many loops > > BUILDSTDERR: aclocal: Please contact . > > BUILDSTDERR:  at /usr/share/automake-1.13/Automake/Channels.pm line 662. > > BUILDSTDERR:    Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 > > BUILDSTDERR:    Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 > > BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) > > BUILDSTDERR:     Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib > > BUILDSTDERR:     Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) > > > > > _______________________________________________ > > 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 Thu Sep 27 16:10:59 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 27 Sep 2018 12:10:59 -0400 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <30f504ec5f5525a86bf5c357cd7362fc035205b6.camel@intel.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> <30f504ec5f5525a86bf5c357cd7362fc035205b6.camel@intel.com> Message-ID: On 18-09-26 08:05 PM, Cordoba Malibran, Erich wrote: > On Wed, 2018-09-26 at 16:44 -0700, Saul Wold wrote: >> On 09/26/2018 02:08 PM, Scott Little wrote: >>> I have also been investigating another intermittent build error >>> affecting initscripts. >>> >>> https://bugs.launchpad.net/starlingx/+bug/1794611 >>> >>> So any given package might be built by rpm-4.11.3, or by rpm- >>> 4.14.0. >>> It's a race with many inputs. Ideally it shouldn't matter, but it >>> does. build-pkgs --serial might reduce the odds, but likely won't >>> solve >>> it entirely. >>> >> Why is this the case in the first place, can't we ensure we only >> build >> rpm-4.14.0? >> >>> In this case it is a new option that rpm passes to the patch >>> command, >>> --no-backup-if-mismatch, first introduced by rpm-4.13. >>> This option has the effect of suppressing the creation of '.orig' >>> files. >>> >>> Creation of .orig files are a consequence of applying patches that >>> are >>> not clean. Unclean patches are ones that require 'fuzzing', i.e. >>> treat >>> the patch line numbers as approximate, rather than a strict >>> requirement, >>> just so long as the before/after context seems to be correct. >>> >>> Prior to StarlingX, my policy for rebasing patches was that no fuzz >>> is >>> tolerated in our patches. >>> >>> All the work to upgrade to 7.5 has created a lot of fuzzy patches. >>> >> Wow, sorry I was not aware that they were all fuzzy patches. >> > How did you got this list? There were .orig files in those folder? My query was ... for f in $(grep -l 'Hunk' $MY_WORKSPACE/std/results/*/*/build.log); do basename $(dirname $f); done As noted in another thread, we might get false positives in the form of CentOS/EL7 patches that are fuzzy, not our own. > >>> audit-2.8.1-3.el7.tis.2 >>> bash-4.2.46-30.el7.tis.3 >>> dhcp-4.2.5-68.el7.centos.1.tis.8 >>> dnsmasq-2.76-5.el7.tis.6 >>> drbd-8.4.3-0.tis.6 >>> facter-2.4.4-4.el7.tis.4 >>> haproxy-1.5.18-7.el7.tis.7 >>> initscripts-9.49.41-1.el7.tis.16 >>> iptables-1.4.21-24.1.el7_5.tis.3 >>> kubernetes-1.10.0-1.tis.1 >>> libevent-2.0.21-4.el7.tis.2 >>> lighttpd-1.4.50-1.el7.tis.6 >>> logrotate-3.8.6-15.el7.tis.3 >>> netpbm-10.79.00-7.el7.tis.2 >>> net-snmp-5.7.2-33.el7_5.2.tis.10 >>> net-tools-2.0-0.22.20131004git.el7.tis.2 >>> nfs-utils-1.3.0-0.54.el7.tis.4 >>> nss-pam-ldapd-0.8.13-16.el7.tis.4 >>> ntp-4.2.6p5-28.el7.centos.tis.3 >>> openldap-2.4.44-15.el7_5.tis.8 >>> openssh-7.4p1-16.el7_4.tis.9 >>> pam-1.1.8-22.el7.tis.4 >>> puppet-4.8.2-1.el7.tis.2 >>> puppet-ceph-2.4.1-1.el7.tis.4 >>> puppet-horizon-11.5.0-1.el7.tis.1 >>> python-2.7.5-69.el7_5.tis.3 >>> python-keyring-5.7.1-1.tis.2 >>> python-wsme-0.9.2-1.el7.tis.3 >>> resource-agents-3.9.5-124.el7.tis.12 >>> rsync-3.1.2-4.el7.tis.2 >>> shadow-utils-4.1.5.1-24.el7.tis.4 >>> sudo-1.8.19p2-14.el7_5.tis.3 >>> watchdog-5.13-11.el7.tis.2 >>> >>> So any of these packages might or might not produce unwanted .orig >>> files. >>> The .orig files might or might not be packaged, or break packaging. >>> >>> So there are a number of threads to pull at here. >>> 1) Are fuzzy patches tolerated. I vote no. Sooner or later a >>> fuzzy >>> patch will be mis-applied and cause us problems. >> Agreed, when updating patches should be rebased and de-fuzzed. >> >>> 2) Can we force rpmbuild within mock to use a consistent policy >>> with >>> respect to creation of orig files? >> It would be good to investigate that. >> > Seems we can pass _default_patch_fuzz 0 as a variable to rpmbuild. > > What could be the course of action here? > - Wire rpmbuild to not allow fuzzy patches. > - Then iteratively try to build until all the index are correct > > > -Erich I usually start by using a combination of 'build-pkgs --edit', 'git format-patch', and meld (a graphical diff/merge tool). e.g. # If 'build-pkgs --edit' works, it's rather fragile as it's more or less parsing spec files, it produces # two gits, on for working on the tarball content, and a second for the spec file and other files outside the tarball. # Patches are seen as commits, applied with fuzz allowed.  STX patches will get a WRS prefix  (sorry, I'll make that STX in future) build-pkgs --edit --clean initscripts build-pkgs --edit initscripts ...   11:36:45 b7: ===== 'initscripts' has been extracted for editing. =====   11:36:45 b7: ===== Metadata can be found at: /localdisk/loadbuild/slittle1/starlingx-4/std/srpm_work/initscripts/rpmbuild   11:36:45 b7: ===== Source code can be found at: /localdisk/loadbuild/slittle1/starlingx-4/std/srpm_work/initscripts/gits/initscripts.spec/initscripts-9.49.41 cd /localdisk/loadbuild/slittle1/starlingx-4/std/srpm_work/initscripts/gits/initscripts.spec/initscripts-9.49.41 git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%ci) %C(bold blue)<%an>%Creset' --abbrev-commit   * 3aaf0ca - (HEAD, initscripts-9.49.41-1.el7) WRS: Patch15: run-dhclient-as-daemon-for-ipv6.patch (2018-09-27 11:36:45 -0400)   * 126e810 - WRS: Patch14: ifup-eth-stop-waiting-if-link-is-up.patch (2018-09-27 11:36:44 -0400)   * df98ada - WRS: Patch13: ipv6-static-route-support.patch (2018-09-27 11:36:44 -0400)   * cc391dd - WRS: Patch12: sysconfig-unsafe-usage-of-linkdelay-variable.patch (2018-09-27 11:36:44 -0400)   * 398cdf6 - WRS: Patch11: sysconfig-affirmative-check-for-link-carrier.patch (2018-09-27 11:36:43 -0400)   * a3ebe9e - WRS: Patch10: run-ifdown-on-all-interfaces.patch (2018-09-27 11:36:43 -0400)   * 0a6e1fc - WRS: Patch9: 0001-force-delay-check-link-down.patch (2018-09-27 11:36:43 -0400)   * 45075af - WRS: Patch8: 0001-dhclient-remove-1-arg.patch (2018-09-27 11:36:42 -0400)   * 02f8215 - WRS: Patch7: support-interface-promisc.patch (2018-09-27 11:36:42 -0400)   * c5b8eab - WRS: Patch6: dhclient-restrict-interfaces-to-those-on-c.patch (2018-09-27 11:36:41 -0400)   * 6d8bcb5 - WRS: Patch5: relocate-dhclient-leases-to-var-run.patch (2018-09-27 11:36:41 -0400)   * 480e9a5 - WRS: Patch4: support-interface-scriptlets.patch (2018-09-27 11:36:41 -0400)   * 487fdfa - (tag: pre_wrs_initscripts-9.49.41-1.el7) ORIGINAL: extracted archive (2018-09-27 11:36:39 -0400)   * 7ca8368 - (master) ORIGINAL: initial commit (2018-09-27 11:36:39 -0400) # Create new patches without fuzz.  Note: patch comment text is often discarded # git format-patch git format-patch $(git tag | grep pre_wrs_) # use meld or other diff/merge tool to transfer the revised line numbers.  A bit of coding magic is required to translate patch names. cd $MY_REPO/stx/stx-integ/base/initscripts/centos/patches/ for src in $(ls -1 /localdisk/loadbuild/slittle1/starlingx-4/std/srpm_work/initscripts/gits/initscripts.spec/initscripts-9.49.41/00*patch); do dest=$(ls -1 $(basename $src | cut -d '-' -f 4- | sed 's#.patch$#*#')); meld $src $dest; done cd /localdisk/loadbuild/slittle1/starlingx-4/std/srpm_work/initscripts/rpmbuild git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%ci) %C(bold blue)<%an>%Creset' --abbrev-commit   * 4ecfd77 - (HEAD, initscripts-9.49.41-1.el7) WRS: spec-run-dhclient-as-daemon-for-ipv6.patch (2018-09-27 11:36:40 -0400)   * 69d0bb4 - WRS: spec-ifup-eth-stop-waiting-if-link-is-up.patch (2018-09-27 11:36:40 -0400)   * e2942ca - WRS: ipv6-static-route-support.patch (2018-09-27 11:36:40 -0400)   * 4e0368a - WRS: fix-build-failures-due-to-unwanted-sgid.patch (2018-09-27 11:36:40 -0400)   * bc43676 - WRS: spec-sysconfig-unsafe-usage-of-linkdelay-variable.patch (2018-09-27 11:36:40 -0400)   * 6a38a1d - WRS: spec-sysconfig-affirmative-check-for-link-carrier.patch (2018-09-27 11:36:40 -0400)   * 730fe3c - WRS: 0001-Update-package-versioning-for-TIS-format.patch (2018-09-27 11:36:39 -0400)   * a083a54 - WRS: run-ifdown-on-all-interfaces.patch (2018-09-27 11:36:39 -0400)   * 7f02bc2 - WRS: force-delay-check-link-down.patch (2018-09-27 11:36:39 -0400)   * dbdb232 - WRS: 0001-Fix-Interfaces-intermittenly-do-not-come-up-on-boot.patch (2018-09-27 11:36:39 -0400)   * c51c427 - WRS: spec-add-mountnfs-init-script.patch (2018-09-27 11:36:39 -0400)   * 0a5a833 - WRS: 0001-Support-PROMISC-for-interfaces-config.patch (2018-09-27 11:36:39 -0400)   * e0bbac3 - WRS: 0001-Disable-zeroconf-route.patch (2018-09-27 11:36:39 -0400)   * 6485d13 - WRS: stop-creating-shared-dirs.patch (2018-09-27 11:36:39 -0400)   * 7223930 - WRS: spec-include-TiS-changes.patch (2018-09-27 11:36:39 -0400)   * b63eb3d - (tag: wrs_post_copy_list_initscripts-9.49.41-1.el7) WRS: COPY_LIST content (2018-09-27 11:36:39 -0400)   * 8e1e97a - (tag: pre_wrs_initscripts-9.49.41-1.el7) ORIGINAL: srpm extract (2018-09-27 11:36:38 -0400)   * a6928fd - (master) ORIGINAL: initial commit (2018-09-27 11:36:38 -0400) # Create new meta-patches without fuzz.  Note: patch comment text is often discarded # git format-patch git format-patch $(git tag | grep wrs_post_copy) # use meld or other diff/merge tool to transfer the revised line numbers.  A bit of coding magic is required to translate patch names. cd $MY_REPO/stx/stx-integ/base/initscripts/centos/meta_patches/ for src in $(ls -1 /localdisk/loadbuild/slittle1/starlingx-4/std/srpm_work/initscripts/rpmbuild/00*patch); do dest=$(ls -1 $(basename $src | cut -d '-' -f 3- | sed 's#.patch$#*#')); meld $src $dest; done > >>> 3) Can we pre-build rpm, such that all packages build against the >>> same >>> rpm version? >> Yes, as mentioned above we should use a consistent version. >> >>> 4) Are we patching any other low level build tools that have >>> similar >>> issues? Possibly explaining ceph? TBD >>> >> Yup more info is needed >> >> Sau! >> >> >>> >>> On 18-09-26 12:16 PM, Scott Little wrote: >>>> aclocal 'too many loops' has been popping up sporadically for a >>>> week >>>> or two now. Possibly 7.5 related. >>>> >>>> I suspect that there is a build order and/or race condition >>>> element to >>>> this. It often goes away if you just run build-pkgs a second >>>> time. >>>> >>>> The second possible element is that build-pkgs is using flags >>>> that >>>> preserve the mock environment between packages. The goal was to >>>> avoid >>>> reinstalling required packages that are often common across the >>>> packages we build. It was a build time speedup that has been in >>>> use >>>> for 2-3 years now without incident. >>>> >>>> Google shows that other folks have hit 'aclocal too many loops' >>>> as >>>> well, and there are suggestions that it might be fixed in a >>>> recent >>>> update to automake. Scanning the changelog for the latest and >>>> greatest from gnu.org doesn't show any obvious fixes addressing >>>> this >>>> issue. >>>> >>>> Scott >>>> >>>> >>>> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>>>> BUILDSTDERR: aclocal: error: too many loops >>>>> BUILDSTDERR: aclocal: Please contact. >>>>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm >>>>> line 662. >>>>> BUILDSTDERR: Automake::Channels::msg('automake', '', >>>>> 'too many loops') called at /usr/share/automake- >>>>> 1.13/Automake/ChannelDefs.pm line 212 >>>>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too >>>>> many loops') called at /usr/bin/aclocal line 1187 >>>>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm- >>>>> tmp.Sj0E7c (%build) >>>>> BUILDSTDERR: Macro expanded in comment on line 214: %global >>>>> _libexecdir %{_exec_prefix}/lib >>>>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>>>> (%build) >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc >>>> uss >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>> s >>> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Sep 27 16:14:37 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 27 Sep 2018 16:14:37 +0000 Subject: [Starlingx-discuss] StarlingX Initial Governance In-Reply-To: <2A0287E6-6C87-49D8-A896-D0D663ECF8C7@openstack.org> References: <0309b193-6b70-00d3-9ac4-053eb4f28fd4@openstack.org> <2A0287E6-6C87-49D8-A896-D0D663ECF8C7@openstack.org> Message-ID: <9A85D2917C58154C960D95352B22818BAB5A725A@fmsmsx117.amr.corp.intel.com> Thank you for the feedback. We appreciate it. The way I'd like to suggest that we handle this is to get the governance document into source control. At the Documentation team meeting this week we agreed to create a stx-governance repo and place the document there. Then I will post changes to gerrit to address this feedback that can be reviewed and approved. Makes sense? @Ildiko, please let me know when the repo goes live. I'll be working on converting the current draft from wiki to .rst this week. brucej -----Original Message----- From: Claire Massey [mailto:claire at openstack.org] Sent: Thursday, September 27, 2018 8:21 AM To: Thierry Carrez Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX Initial Governance Hi all, I agree with Thierry and think that in order to encourage growth for the project, the first election period should to be adjusted. The next several months will be a critical time for StarlingX to welcome diverse engagement. From what we’ve experienced while launching other projects, like Kata Containers for example, new companies that are interested in engaging with the project for the first time are also very interested in having the opportunity to be elected to the technical leadership body within a reasonable amount of time. The opportunity to contribute to the project and possibly earn an elected seat early on in the life of the project can be very motivating for new companies that want to get involved. Based on the current StarlingX election timeline shown in the governance documentation[1], September 2019 is the soonest date when a new person would be able to be elected to the TSC. I personally think that waiting an entire year is just too long and may discourage new contributors from getting involved in the short-term. I recommend that instead of waiting a full year to hold the first election, that it's held sooner, in *May 2019*, which is eight months from now. The planned StarlingX release cadence and schedule[2] shows that the next two releases are timed to happen in March and July 2019, so hosting the first election between those two releases, in May 2019, could work well. [1] https://wiki.openstack.org/wiki/Starlingx/Initial_Governance#Technical_Steering_Committee [2] https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Cadence_and_Schedule Thanks, Claire > On Sep 27, 2018, at 10:13 AM, Thierry Carrez wrote: > > Hi everyone, > > I reread the Governance document[1] and found an inconsistency we'll likely want to address before the initial TSC formally blesses it: > > In "Technical Steering Committee": >> It will be comprised of 7 members who will be appointed at Launch but fully elected by the Contributors within the first year > > then: >> In April 2020, the remaining 4 seats are up for election > > "appointed at Launch" is a bit vague, I would use "initially appointed" (which would start the clock to when the TSC is fully formed). But more importantly, "fully elected by the Contributors within the first year" is at odds with still having appointed members around in March, 2020. The date or the period needs to be adjusted to match. > > We'll also likely want to clarify initial terms for the non-WR and non-Intel initial TSC members. One option is to appoint one of them with a short term, and the other two with long terms. Another option would be to randomly select the short one (like for the WR and Intel initially-appointed seats) > > Finally, I would suggest saying that if somone steps down from their TSC seat, their seat should automatically be up for election at the next round. So imagine someone that is initially appointed for a year, stepping down after 4 months: their seat would be up for reelection, which would make the first election determine 4 seats instead of just 3. That will facilitate keeping an active TSC with a limited number of stale members. > > That level of subtlety could be conveyed through a separate document that details the corner cases of the election process, if you find it too distracting for the Governance document. > > [1] https://wiki.openstack.org/wiki/Starlingx/Initial_Governance > > -- > Thierry Carrez (ttx) > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Sep 27 16:24:36 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 27 Sep 2018 16:24:36 +0000 Subject: [Starlingx-discuss] TSC call minutes Sep 27 2018 Message-ID: <9A85D2917C58154C960D95352B22818BAB5A7305@fmsmsx117.amr.corp.intel.com> 9/27/18: * Rename this call the TSC call. Bruce will continue to facilitate * Upstreaming o Team is dividing up the patches into openstack, qemu/libvirt, and distro. Brief review of Abandoned distro patches, most no longer needed due to the update to CentOS 7.2 * TL / PL for the multi-os * PL: Candidates: Bruce, Cindy, Dariush. Ian to check with Dariush. Bruce & Cindy will be active regardless * TL: Candidates: Brent, Saul. Saul & Brent both will also be active in this * No decision. Ian to check with Dariush. Try to finalize next week. * Release update * De-fuzzying patches are in the Zuul queue, waiting for Zuul resources * Can be reviewed now and should be +1 W once they get 2 +2 * Release branch is gated on resolving these * There are also some build patches pending that we might want to cherry pick into the branch * We talked briefly about how to decide what changes should be backported to the release branch - need to review case by case for impact, testing impact, etc... -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Sep 27 16:22:38 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 27 Sep 2018 12:22:38 -0400 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <30f504ec5f5525a86bf5c357cd7362fc035205b6.camel@intel.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <89de6304-650e-0030-f057-fb42c4f2ee85@windriver.com> <7294a543-fd4d-258f-a684-2e880fecfc11@linux.intel.com> <30f504ec5f5525a86bf5c357cd7362fc035205b6.camel@intel.com> Message-ID: On 18-09-26 08:05 PM, Cordoba Malibran, Erich wrote: > Seems we can pass _default_patch_fuzz 0 as a variable to rpmbuild. > > What could be the course of action here? > - Wire rpmbuild to not allow fuzzy patches. > - Then iteratively try to build until all the index are correct > > > -Erich I don't think that would work.  Some of the CentOS/EL7 src.rpm's ship with embedded fuzzy patches.  We can't fix those. From sgw at linux.intel.com Thu Sep 27 17:41:35 2018 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 27 Sep 2018 10:41:35 -0700 Subject: [Starlingx-discuss] May have to consider an lshell replacement Message-ID: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> Folks, As I was looking at the upstream patches, I looked into the status of lshell and noticed there was an existing open issue[0] which referenced 2 CVEs: - CVE-2016-6902 - remote authenticated users can break out of a limited shell and execute arbitrary commands. - CVE-2016-6903 - lshell 0.9.16 allows remote authenticated users to break out of a limited shell and execute arbitrary commands. These are related, and there is a potential fix, but issue 150 [3] seems to indicate the patch is not complete. The maintainer has expressed that he not able to do anything about this as of May this year. Additionally lshell is python2 based and would need to be converted to python3. I went so far as proposing a very simple change to their README.md to fix a bad link and it stalled in their travis tox check. Sau! [0] https://github.com/ghantoos/lshell/issues/188 [1] https://nvd.nist.gov/vuln/detail/CVE-2016-6902 [2] https://nvd.nist.gov/vuln/detail/CVE-2016-6903 [0] https://github.com/ghantoos/lshell/issues/150 From bruce.e.jones at intel.com Thu Sep 27 17:45:23 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 27 Sep 2018 17:45:23 +0000 Subject: [Starlingx-discuss] May have to consider an lshell replacement In-Reply-To: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> References: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5A73B1@fmsmsx117.amr.corp.intel.com> What alternatives do we have for this functionality? brucej -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Thursday, September 27, 2018 10:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] May have to consider an lshell replacement Folks, As I was looking at the upstream patches, I looked into the status of lshell and noticed there was an existing open issue[0] which referenced 2 CVEs: - CVE-2016-6902 - remote authenticated users can break out of a limited shell and execute arbitrary commands. - CVE-2016-6903 - lshell 0.9.16 allows remote authenticated users to break out of a limited shell and execute arbitrary commands. These are related, and there is a potential fix, but issue 150 [3] seems to indicate the patch is not complete. The maintainer has expressed that he not able to do anything about this as of May this year. Additionally lshell is python2 based and would need to be converted to python3. I went so far as proposing a very simple change to their README.md to fix a bad link and it stalled in their travis tox check. Sau! [0] https://github.com/ghantoos/lshell/issues/188 [1] https://nvd.nist.gov/vuln/detail/CVE-2016-6902 [2] https://nvd.nist.gov/vuln/detail/CVE-2016-6903 [0] https://github.com/ghantoos/lshell/issues/150 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Thu Sep 27 17:48:21 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 27 Sep 2018 17:48:21 +0000 Subject: [Starlingx-discuss] May have to consider an lshell replacement In-Reply-To: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> References: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> Message-ID: <7e05fa4afe1d86ecff404a80508b5312eef384cf.camel@intel.com> Same thing can apply for ibsh, seems to be dead since 2005. http://ibsh.sourceforge.net/ -Erich On Thu, 2018-09-27 at 10:41 -0700, Saul Wold wrote: > Folks, > > As I was looking at the upstream patches, I looked into the status > of > lshell and noticed there was an existing open issue[0] which > referenced > 2 CVEs: > > - CVE-2016-6902 - remote authenticated users can break out of a > limited shell and execute arbitrary commands. > - CVE-2016-6903 - lshell 0.9.16 allows remote authenticated users > to > break out of a limited shell and execute arbitrary commands. > > These are related, and there is a potential fix, but issue 150 [3] > seems > to indicate the patch is not complete. The maintainer has expressed > that > he not able to do anything about this as of May this year. > Additionally > lshell is python2 based and would need to be converted to python3. > > I went so far as proposing a very simple change to their README.md > to > fix a bad link and it stalled in their travis tox check. > > Sau! > > [0] https://github.com/ghantoos/lshell/issues/188 > [1] https://nvd.nist.gov/vuln/detail/CVE-2016-6902 > [2] https://nvd.nist.gov/vuln/detail/CVE-2016-6903 > [0] https://github.com/ghantoos/lshell/issues/150 > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From michel.thebeau at windriver.com Thu Sep 27 18:05:00 2018 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Thu, 27 Sep 2018 14:05:00 -0400 Subject: [Starlingx-discuss] Simplex configuration per wiki Message-ID: <3b76d581-72d6-cd85-41ef-c294c8c4ff66@windriver.com> Hi Abraham, list, I had a chance to boot simplex configuration per the "simplex" wiki: https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex It runs based off the xml for duplex, and appears to run as expected. M From scott.little at windriver.com Thu Sep 27 18:02:43 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 27 Sep 2018 14:02:43 -0400 Subject: [Starlingx-discuss] [meetings][build] Build team meeting Agenda for 10/1/2018 In-Reply-To: <0B566C62EC792145B40E29EFEBF1AB4710521086@fmsmsx104.amr.corp.intel.com> References: <0B566C62EC792145B40E29EFEBF1AB4710521086@fmsmsx104.amr.corp.intel.com> Message-ID: Don't suppose we could find another time slot? This meeting keeps colliding with my wifes eye doc appointments ... detached retina, macular tear, cataract... a long saga. Mondays are a problem. Scott On 18-09-26 05:11 PM, Lara, Cesar wrote: > > StarlingX Build team meeting > > Agenda for 10/1/2018 > > ·Build issues on intel side > > -Findings and next steps > > -Mock cleanup proposal > > -General discussion > > ·Proposals for hosting with cengn > > ·Brainstorming  for next release > > ·Re-scoping of stxb tool > > Regards > > *//* > > */Cesar Lara/* > > Software Engineering Manager > > OpenSource Technology Center > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From saul.wold at intel.com Thu Sep 27 17:48:13 2018 From: saul.wold at intel.com (Saul Wold) Date: Thu, 27 Sep 2018 10:48:13 -0700 Subject: [Starlingx-discuss] Origin of systemd millisecond patch Message-ID: <06495b7d-32ec-cbd8-589f-afd8c3e90a58@intel.com> Brent, This systemd patch seems to originate from Red Hat's systemd team, I need to get more information about this before proposing this to systemd community. I tried to search the systemd archives to see if Red Hat had attempted to upstream this patch and did not find anything. Does anyone have any contacts at Red Hat that might be able to help so that we can move forward with upstreaming this. As systemd is a pretty core tool, I would rather use an upstream than building our own. Thanks Sau! -------------- next part -------------- A non-text attachment was scrubbed... Name: 0501-inject-millisec-in-syslog-date.patch Type: text/x-patch Size: 2795 bytes Desc: not available URL: From sgw at linux.intel.com Thu Sep 27 18:16:10 2018 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 27 Sep 2018 11:16:10 -0700 Subject: [Starlingx-discuss] Origin of systemd millisecond patch Message-ID: <82c9011a-6f9b-47fd-9b30-d6909d6ee4fd@linux.intel.com> Brent, This systemd patch seems to originate from Red Hat's systemd team, I need to get more information about this before proposing this to systemd community. I tried to search the systemd archives to see if Red Hat had attempted to upstream this patch and did not find anything. Does anyone have any contacts at Red Hat that might be able to help so that we can move forward with upstreaming this. As systemd is a pretty core tool, I would rather use an upstream than building our own. Thanks Sau! -------------- next part -------------- A non-text attachment was scrubbed... Name: 0501-inject-millisec-in-syslog-date.patch Type: text/x-patch Size: 2796 bytes Desc: not available URL: From sgw at linux.intel.com Thu Sep 27 18:21:46 2018 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 27 Sep 2018 11:21:46 -0700 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> Message-ID: <9fcf603c-11a8-cc75-9683-61eb802997ef@linux.intel.com> On 09/26/2018 09:16 AM, Scott Little wrote: > aclocal 'too many loops' has been popping up sporadically for a week or > two now.  Possibly 7.5 related. > > I suspect that there is a build order and/or race condition element to > this.   It often goes away if you just run build-pkgs a second time. > I am seeing this failure also, but it does not go away after a second rebuild. I have the lastest stx-root (build-tools) with the recent patches. Is this directly related to the fuzz issue or is there something else we need to address in CEPH itself. This is blocking my local build. Sau! > The second possible element is that build-pkgs is using flags that > preserve the mock environment between packages.  The goal was to avoid > reinstalling required packages that are often common across the packages > we build.   It was a build time speedup that has been in use for 2-3 > years now without incident. > > Google shows that other folks have hit 'aclocal too many loops' as well, > and there are suggestions that it might be fixed in a recent update to > automake.  Scanning the changelog for the latest and greatest from > gnu.org doesn't show any obvious fixes addressing this issue. > > Scott > > > On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >> BUILDSTDERR: aclocal: error: too many loops >> BUILDSTDERR: aclocal: Please contact. >> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. >> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 >> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 >> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >> BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib >> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From dtroyer at gmail.com Thu Sep 27 19:07:08 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 27 Sep 2018 14:07:08 -0500 Subject: [Starlingx-discuss] May have to consider an lshell replacement In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5A73B1@fmsmsx117.amr.corp.intel.com> References: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> <9A85D2917C58154C960D95352B22818BAB5A73B1@fmsmsx117.amr.corp.intel.com> Message-ID: On Thu, Sep 27, 2018 at 12:45 PM, Jones, Bruce E wrote: > What alternatives do we have for this functionality? Alternatives in increasing levels of commitment to lshell: * replace it * fork the project and fix the CVEs and continue * adopt the project and take over maintenance as a stand0-alone project should the existing maintainer be interested in doing so[0] I am specifically not listing 'do nothing' as active CVEs must be addressed... dt [0] OpenStack has done this on occasion when a dependency goes dormant and the maintainer has no interest in continuing and the cost of converting outweighs the perceived cost of maintenance and ownership. -- Dean Troyer dtroyer at gmail.com From Ken.Young at windriver.com Thu Sep 27 19:28:28 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Thu, 27 Sep 2018 19:28:28 +0000 Subject: [Starlingx-discuss] FW: May have to consider an lshell replacement In-Reply-To: References: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> <9A85D2917C58154C960D95352B22818BAB5A73B1@fmsmsx117.amr.corp.intel.com> Message-ID: <425223BD-6F57-486D-B774-01AD7B2DCFB0@windriver.com> Dean / Saul, We agree that the all security issues are initially embargoed. Therefore, this topic should not be discussed on the mailing list until it has been vetted by the security team. The security team has published a method to raise these issues. You will find it here: https://wiki.openstack.org/wiki/StarlingX/Security#How_to_report_security_issues_to_Starling_X I would suggest that we open a Security launchpad and we can continue the discussion there. Thank you in advance. Regards, Ken Y On 2018-09-27, 3:07 PM, "Dean Troyer" wrote: On Thu, Sep 27, 2018 at 12:45 PM, Jones, Bruce E wrote: > What alternatives do we have for this functionality? Alternatives in increasing levels of commitment to lshell: * replace it * fork the project and fix the CVEs and continue * adopt the project and take over maintenance as a stand0-alone project should the existing maintainer be interested in doing so[0] I am specifically not listing 'do nothing' as active CVEs must be addressed... dt [0] OpenStack has done this on occasion when a dependency goes dormant and the maintainer has no interest in continuing and the cost of converting outweighs the perceived cost of maintenance and ownership. -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Sep 27 19:42:21 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 27 Sep 2018 19:42:21 +0000 Subject: [Starlingx-discuss] FW: May have to consider an lshell replacement In-Reply-To: <425223BD-6F57-486D-B774-01AD7B2DCFB0@windriver.com> References: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> <9A85D2917C58154C960D95352B22818BAB5A73B1@fmsmsx117.amr.corp.intel.com> <425223BD-6F57-486D-B774-01AD7B2DCFB0@windriver.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5A7535@fmsmsx117.amr.corp.intel.com> Bug https://bugs.launchpad.net/starlingx/+bug/1794868 filed. Saul and Dean added to it. brucej -----Original Message----- From: Young, Ken [mailto:Ken.Young at windriver.com] Sent: Thursday, September 27, 2018 12:28 PM To: Dean Troyer ; Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] FW: May have to consider an lshell replacement Dean / Saul, We agree that the all security issues are initially embargoed. Therefore, this topic should not be discussed on the mailing list until it has been vetted by the security team. The security team has published a method to raise these issues. You will find it here: https://wiki.openstack.org/wiki/StarlingX/Security#How_to_report_security_issues_to_Starling_X I would suggest that we open a Security launchpad and we can continue the discussion there. Thank you in advance. Regards, Ken Y On 2018-09-27, 3:07 PM, "Dean Troyer" wrote: On Thu, Sep 27, 2018 at 12:45 PM, Jones, Bruce E wrote: > What alternatives do we have for this functionality? Alternatives in increasing levels of commitment to lshell: * replace it * fork the project and fix the CVEs and continue * adopt the project and take over maintenance as a stand0-alone project should the existing maintainer be interested in doing so[0] I am specifically not listing 'do nothing' as active CVEs must be addressed... dt [0] OpenStack has done this on occasion when a dependency goes dormant and the maintainer has no interest in continuing and the cost of converting outweighs the perceived cost of maintenance and ownership. -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Thu Sep 27 19:49:08 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 27 Sep 2018 19:49:08 +0000 Subject: [Starlingx-discuss] stx.2018.10 code freeze status In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA457853@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA457853@ALA-MBD.corp.ad.wrs.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA458CF3@ALA-MBD.corp.ad.wrs.com> Updates as of a few minutes ago are inline (prefixed with [[GK]]). Info requested inline from Saul, Abraham. -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, September 27, 2018 11:24 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx.2018.10 code freeze status Hello all, The starlingx master branch is under a "limited" merge window. This is a reminder to core reviewers NOT to workflow + 1 any commits that don't fall under the following categories: - CentOS 7.5 patch de-fuzzing: https://review.openstack.org/#/q/topic:patch_fuzz+(status:open+OR+status:merged) [[GK]] There are 5 commits still not merged. 2 require W+1. Saul, can you please look at those. - Documentation updates required https://review.openstack.org/#/q/status:open+branch:master+topic:documentation-baseline [[GK]] There are 3 commits still not merged. They just seem to need W+1 to merge. Abraham, are these the only ones left to finish off the doc updates? Build-Related Bugs - build-srpms-serial is broken: https://bugs.launchpad.net/starlingx/+bug/1790583 Looking for Austin, Erich & Saul to summarize the status. There are two proposed commits: one from Austin & one from Erich. [[GK]] The Launchpad is now marked as Fix Released, so I'll assume this is no longer an issue. - build-pkgs cannot complete std build: https://bugs.launchpad.net/starlingx/+bug/1791127 Needs re-test after the CentOS 7.5 patch de-fuzzing. Any other updates on this one? [[GK]] The only report I've seen is related to ceph failures from Saul. Any more info? A WR STX build passed this afternoon. - Corrupt mirror causes missing lshell src rpm: https://bugs.launchpad.net/starlingx/+bug/1793615 This one just got re-opened by Erich. I will let him comment on it further [[GK]] Any updates on this? The thread discussing the replacement of lshell is beyond the scope of the October release. Is anyone else aware of any other serious issues that should gate the branch creation for the October release? Regards, Ghada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Thu Sep 27 19:53:14 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 27 Sep 2018 15:53:14 -0400 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <9fcf603c-11a8-cc75-9683-61eb802997ef@linux.intel.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <9fcf603c-11a8-cc75-9683-61eb802997ef@linux.intel.com> Message-ID: <7270e771-bf71-5622-1249-30faa1156e35@windriver.com> Our latest build, based on code synced at 2018-09-27T15:28:00  UTC, built successfully. It took three attempts to get ceph built.  The first two passes aborted quickly due to missing packages.  The final pass did not exhibit the 'aclocal: too many loops'**issue. The only build I have that exhibited the too many loops error was a snapshot on 2018-09-20T15:50:40 UTC I do have a designer with an older snapshot that seems to hit it regularly, so I'll work with him and see if we can learn more. I think we need more data from the community - Who's build is failing on ceph with *aclocal: too many loops?* - Who is building successfully ? - Who can build only intermittently? Info to collect for failed builds: - build command used? - Was it a new workspace, a cleaned workspace, or a previously used workspace? - $MY_WORKSPACE/build-std.log - $MY_WORKSPACE/std/results/*/ceph-*/*.log For successful builds, same info. Rather than full build logs, I can settle for: - grep '\(Success building\|iteration\|building ceph\)' $MY_WORKSPACE/build-std.log - grep compute_resources: build-std.log On 18-09-27 02:21 PM, Saul Wold wrote: > On 09/26/2018 09:16 AM, Scott Little wrote: >> aclocal 'too many loops' has been popping up sporadically for a week >> or two now. Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition element >> to this.   It often goes away if you just run build-pkgs a second time. >> > I am seeing this failure also, but it does not go away after a second > rebuild.  I have the lastest stx-root (build-tools) with the recent > patches. > > Is this directly related to the fuzz issue or is there something else > we need to address in CEPH itself. > > This is blocking my local build. > > Sau! -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Sep 27 19:56:37 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 27 Sep 2018 15:56:37 -0400 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <7270e771-bf71-5622-1249-30faa1156e35@windriver.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <9fcf603c-11a8-cc75-9683-61eb802997ef@linux.intel.com> <7270e771-bf71-5622-1249-30faa1156e35@windriver.com> Message-ID: <2a14c931-9bd8-9a1d-3c81-d92d3503fde4@windriver.com> On 18-09-27 03:53 PM, Scott Little wrote: > Our latest build, based on code synced at 2018-09-27T15:28:00  UTC, > built successfully. > > It took three attempts to get ceph built.  The first two passes > aborted quickly due to missing packages.  The final pass did not > exhibit the 'aclocal: too many loops'**issue. > > The only build I have that exhibited the too many loops error was a > snapshot on 2018-09-20T15:50:40 UTC > > I do have a designer with an older snapshot that seems to hit it > regularly, so I'll work with him and see if we can learn more. > > I think we need more data from the community > - Who's build is failing on ceph with *aclocal: too many loops?* > - Who is building successfully ? > - Who can build only intermittently? > > > > Info to collect for failed builds: - repo sync timestamp > - build command used? > - Was it a new workspace, a cleaned workspace, or a previously used > workspace? - $MY_WORKSPACE/CONTEXT > - $MY_WORKSPACE/build-std.log > - $MY_WORKSPACE/std/results/*/ceph-*/*.log > > For successful builds, same info. Rather than full build logs, I can > settle for: > - grep '\(Success building\|iteration\|building ceph\)' > $MY_WORKSPACE/build-std.log > - grep compute_resources: build-std.log > > > > > > On 18-09-27 02:21 PM, Saul Wold wrote: >> On 09/26/2018 09:16 AM, Scott Little wrote: >>> aclocal 'too many loops' has been popping up sporadically for a week >>> or two now.  Possibly 7.5 related. >>> >>> I suspect that there is a build order and/or race condition element >>> to this.   It often goes away if you just run build-pkgs a second time. >>> >> I am seeing this failure also, but it does not go away after a second >> rebuild.  I have the lastest stx-root (build-tools) with the recent >> patches. >> >> Is this directly related to the fuzz issue or is there something else >> we need to address in CEPH itself. >> >> This is blocking my local build. >> >> Sau! > > > > > _______________________________________________ > 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 abraham.arce.moreno at intel.com Thu Sep 27 20:05:40 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 27 Sep 2018 20:05:40 +0000 Subject: [Starlingx-discuss] stx.2018.10 code freeze status In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA458CF3@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA457853@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA458CF3@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks everyone involved in reviewing and merging Documentation patches. > Updates as of a few minutes ago are inline (prefixed with [[GK]]). > Info requested inline from Saul, Abraham. > > - Documentation updates required > https://review.openstack.org/#/q/status:open+branch:master+topic:docum > entation-baseline > [[GK]] There are 3 commits still not merged. They just seem to need W+1 to > merge. Abraham, are these the only ones left to finish off the doc updates? These are the missing patches in process to be merged: [Doc] OpenStack API Reference Guide https://review.openstack.org/#/c/599466 stx-config: API ref doc content added. https://review.openstack.org/#/c/605254/ stx-fault: API ref doc content added. https://review.openstack.org/#/c/605259/ stx-ha: API ref doc content added. https://review.openstack.org/#/c/605272/ stx-metal: API ref doc content added. https://review.openstack.org/#/c/605275/ From abraham.arce.moreno at intel.com Thu Sep 27 20:25:17 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 27 Sep 2018 20:25:17 +0000 Subject: [Starlingx-discuss] StarlingX Release Notes Content In-Reply-To: References: Message-ID: Thanks Eslimi, > I updated the etherpad for following repos: > > • stx-clients > • stx-config > • stx-distcloud > • stx-distcloud-client > • stx-fault > • stx-gui > • stx-ha > • stx-metal > • stx-update > • stx-nfv > > [0] https://etherpad.openstack.org/p/stx-docs > [1] https://review.openstack.org/#/c/600198/3/releasenotes/notes/release- > summary-9c35dd1bd9b020f1.yaml All repos have now Reno as their release notes manager so let us know what else is needed and when it is needed for the official release notes in each individual repository. From Ken.Young at windriver.com Thu Sep 27 20:38:25 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Thu, 27 Sep 2018 20:38:25 +0000 Subject: [Starlingx-discuss] FW: May have to consider an lshell replacement In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5A7535@fmsmsx117.amr.corp.intel.com> References: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> <9A85D2917C58154C960D95352B22818BAB5A73B1@fmsmsx117.amr.corp.intel.com> <425223BD-6F57-486D-B774-01AD7B2DCFB0@windriver.com> <9A85D2917C58154C960D95352B22818BAB5A7535@fmsmsx117.amr.corp.intel.com> Message-ID: Bruce, Can you add the VMT team to the bug please? I cannot open this. Thanks! /KenY On 2018-09-27, 3:42 PM, "Jones, Bruce E" wrote: Bug https://bugs.launchpad.net/starlingx/+bug/1794868 filed. Saul and Dean added to it. brucej -----Original Message----- From: Young, Ken [mailto:Ken.Young at windriver.com] Sent: Thursday, September 27, 2018 12:28 PM To: Dean Troyer ; Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] FW: May have to consider an lshell replacement Dean / Saul, We agree that the all security issues are initially embargoed. Therefore, this topic should not be discussed on the mailing list until it has been vetted by the security team. The security team has published a method to raise these issues. You will find it here: https://wiki.openstack.org/wiki/StarlingX/Security#How_to_report_security_issues_to_Starling_X I would suggest that we open a Security launchpad and we can continue the discussion there. Thank you in advance. Regards, Ken Y On 2018-09-27, 3:07 PM, "Dean Troyer" wrote: On Thu, Sep 27, 2018 at 12:45 PM, Jones, Bruce E wrote: > What alternatives do we have for this functionality? Alternatives in increasing levels of commitment to lshell: * replace it * fork the project and fix the CVEs and continue * adopt the project and take over maintenance as a stand0-alone project should the existing maintainer be interested in doing so[0] I am specifically not listing 'do nothing' as active CVEs must be addressed... dt [0] OpenStack has done this on occasion when a dependency goes dormant and the maintainer has no interest in continuing and the cost of converting outweighs the perceived cost of maintenance and ownership. -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Thu Sep 27 21:07:15 2018 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 27 Sep 2018 14:07:15 -0700 Subject: [Starlingx-discuss] stx.2018.10 code freeze status In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA458CF3@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA457853@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA458CF3@ALA-MBD.corp.ad.wrs.com> Message-ID: <7eb3574f-7251-53d7-62e2-aea39a64e225@linux.intel.com> On 09/27/2018 12:49 PM, Khalil, Ghada wrote: > Updates as of a few minutes ago are inline (prefixed with [[GK]]). > Info requested inline from Saul, Abraham. > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Thursday, September 27, 2018 11:24 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] stx.2018.10 code freeze status > > Hello all, > The starlingx master branch is under a "limited" merge window. > This is a reminder to core reviewers NOT to workflow + 1 any commits that don't fall under the following categories: > > - CentOS 7.5 patch de-fuzzing: > https://review.openstack.org/#/q/topic:patch_fuzz+(status:open+OR+status:merged) > [[GK]] There are 5 commits still not merged. 2 require W+1. Saul, can you please look at those. > I believe we are down to 1 pending due to comments about changes in the body of the patch beyond de-fuzzing, I will let Scott and/or Don comment on that. There are 2 others marked +W pending merge. > - Documentation updates required > https://review.openstack.org/#/q/status:open+branch:master+topic:documentation-baseline > [[GK]] There are 3 commits still not merged. They just seem to need W+1 to merge. Abraham, are these the only ones left to finish off the doc updates? > I added my +2 where appropriate > Build-Related Bugs > - build-srpms-serial is broken: https://bugs.launchpad.net/starlingx/+bug/1790583 > Looking for Austin, Erich & Saul to summarize the status. There are two proposed commits: one from Austin & one from Erich. > [[GK]] The Launchpad is now marked as Fix Released, so I'll assume this is no longer an issue. > > - build-pkgs cannot complete std build: https://bugs.launchpad.net/starlingx/+bug/1791127 > Needs re-test after the CentOS 7.5 patch de-fuzzing. Any other updates on this one? > [[GK]] The only report I've seen is related to ceph failures from Saul. Any more info? A WR STX build passed this afternoon. > No more information, it built when I ran it a 3rd time, we need to get a better root cause of this as it will be bad user interaction. I am not sure it's a blocker for the branching. > - Corrupt mirror causes missing lshell src rpm: https://bugs.launchpad.net/starlingx/+bug/1793615 > This one just got re-opened by Erich. I will let him comment on it further > [[GK]] Any updates on this? The thread discussing the replacement of lshell is beyond the scope of the October release. > Correct, lshell stays for 2018.10 Sau! > Is anyone else aware of any other serious issues that should gate the branch creation for the October release? > > Regards, > Ghada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Don.Penney at windriver.com Thu Sep 27 21:17:14 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 27 Sep 2018 21:17:14 +0000 Subject: [Starlingx-discuss] stx.2018.10 code freeze status In-Reply-To: <7eb3574f-7251-53d7-62e2-aea39a64e225@linux.intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA457853@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA458CF3@ALA-MBD.corp.ad.wrs.com> <7eb3574f-7251-53d7-62e2-aea39a64e225@linux.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA3B5DE7@ALA-MBD.corp.ad.wrs.com> I had comments on the following two reviews, one of which has been W+1'd already by Scott: https://review.openstack.org/#/c/605687/ https://review.openstack.org/#/c/605686/ My comments were providing the original author of the patches that were being revised, since a name was being added to a couple of patches where there was none before. I didn't -1 for this, but also didn't +2. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Thursday, September 27, 2018 5:07 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.2018.10 code freeze status On 09/27/2018 12:49 PM, Khalil, Ghada wrote: > Updates as of a few minutes ago are inline (prefixed with [[GK]]). > Info requested inline from Saul, Abraham. > > -----Original Message----- > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] > Sent: Thursday, September 27, 2018 11:24 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] stx.2018.10 code freeze status > > Hello all, > The starlingx master branch is under a "limited" merge window. > This is a reminder to core reviewers NOT to workflow + 1 any commits that don't fall under the following categories: > > - CentOS 7.5 patch de-fuzzing: > https://review.openstack.org/#/q/topic:patch_fuzz+(status:open+OR+status:merged) > [[GK]] There are 5 commits still not merged. 2 require W+1. Saul, can you please look at those. > I believe we are down to 1 pending due to comments about changes in the body of the patch beyond de-fuzzing, I will let Scott and/or Don comment on that. There are 2 others marked +W pending merge. > - Documentation updates required > https://review.openstack.org/#/q/status:open+branch:master+topic:documentation-baseline > [[GK]] There are 3 commits still not merged. They just seem to need W+1 to merge. Abraham, are these the only ones left to finish off the doc updates? > I added my +2 where appropriate > Build-Related Bugs > - build-srpms-serial is broken: https://bugs.launchpad.net/starlingx/+bug/1790583 > Looking for Austin, Erich & Saul to summarize the status. There are two proposed commits: one from Austin & one from Erich. > [[GK]] The Launchpad is now marked as Fix Released, so I'll assume this is no longer an issue. > > - build-pkgs cannot complete std build: https://bugs.launchpad.net/starlingx/+bug/1791127 > Needs re-test after the CentOS 7.5 patch de-fuzzing. Any other updates on this one? > [[GK]] The only report I've seen is related to ceph failures from Saul. Any more info? A WR STX build passed this afternoon. > No more information, it built when I ran it a 3rd time, we need to get a better root cause of this as it will be bad user interaction. I am not sure it's a blocker for the branching. > - Corrupt mirror causes missing lshell src rpm: https://bugs.launchpad.net/starlingx/+bug/1793615 > This one just got re-opened by Erich. I will let him comment on it further > [[GK]] Any updates on this? The thread discussing the replacement of lshell is beyond the scope of the October release. > Correct, lshell stays for 2018.10 Sau! > Is anyone else aware of any other serious issues that should gate the branch creation for the October release? > > Regards, > Ghada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Sep 27 21:36:55 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 27 Sep 2018 21:36:55 +0000 Subject: [Starlingx-discuss] FW: May have to consider an lshell replacement In-Reply-To: References: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> <9A85D2917C58154C960D95352B22818BAB5A73B1@fmsmsx117.amr.corp.intel.com> <425223BD-6F57-486D-B774-01AD7B2DCFB0@windriver.com> <9A85D2917C58154C960D95352B22818BAB5A7535@fmsmsx117.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5A76B7@fmsmsx117.amr.corp.intel.com> My bad, fixed now. brucej -----Original Message----- From: Young, Ken [mailto:Ken.Young at windriver.com] Sent: Thursday, September 27, 2018 1:38 PM To: Jones, Bruce E ; Dean Troyer ; Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] FW: May have to consider an lshell replacement Bruce, Can you add the VMT team to the bug please? I cannot open this. Thanks! /KenY On 2018-09-27, 3:42 PM, "Jones, Bruce E" wrote: Bug https://bugs.launchpad.net/starlingx/+bug/1794868 filed. Saul and Dean added to it. brucej -----Original Message----- From: Young, Ken [mailto:Ken.Young at windriver.com] Sent: Thursday, September 27, 2018 12:28 PM To: Dean Troyer ; Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] FW: May have to consider an lshell replacement Dean / Saul, We agree that the all security issues are initially embargoed. Therefore, this topic should not be discussed on the mailing list until it has been vetted by the security team. The security team has published a method to raise these issues. You will find it here: https://wiki.openstack.org/wiki/StarlingX/Security#How_to_report_security_issues_to_Starling_X I would suggest that we open a Security launchpad and we can continue the discussion there. Thank you in advance. Regards, Ken Y On 2018-09-27, 3:07 PM, "Dean Troyer" wrote: On Thu, Sep 27, 2018 at 12:45 PM, Jones, Bruce E wrote: > What alternatives do we have for this functionality? Alternatives in increasing levels of commitment to lshell: * replace it * fork the project and fix the CVEs and continue * adopt the project and take over maintenance as a stand0-alone project should the existing maintainer be interested in doing so[0] I am specifically not listing 'do nothing' as active CVEs must be addressed... dt [0] OpenStack has done this on occasion when a dependency goes dormant and the maintainer has no interest in continuing and the cost of converting outweighs the perceived cost of maintenance and ownership. -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Thu Sep 27 21:48:09 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 27 Sep 2018 21:48:09 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <9fcf603c-11a8-cc75-9683-61eb802997ef@linux.intel.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <9fcf603c-11a8-cc75-9683-61eb802997ef@linux.intel.com> Message-ID: Hi, I did this experiment: I cherry pick all the defuzzed patches and try to build. The result was that the build failing packages now are: libvirt-python-4.7.0-1.tis.1.src.rpm vm-topology-1.0- 1.tis.src.rpm libvirt-4.7.0-1.tis.22.src.rpm which basically is just libvirt, the other ones are just depending on libvirt. Checking the build.log for libvirt: Making all in src make[2]: Entering directory `/builddir/build/BUILD/libvirt-4.7.0/src' BUILDSTDERR: make[2]: *** No rule to make target `keycodemapdb/data/keymaps.csv', needed by `util/virkeycodetable_linux.h'. Stop. make[2]: Leaving directory `/builddir/build/BUILD/libvirt-4.7.0/src' BUILDSTDERR: make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/builddir/build/BUILD/libvirt-4.7.0' BUILDSTDERR: make: *** [all] Error 2 RPM build errors: BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Chutrp (%build) BUILDSTDERR: Macro expanded in comment on line 2067: %{_datadir}/systemtap/tapset/libvirt_probes*.stp BUILDSTDERR: Macro expanded in comment on line 2068: %{_datadir}/systemtap/tapset/libvirt_qemu_probes*.stp BUILDSTDERR: Macro expanded in comment on line 2069: %{_datadir}/systemtap/tapset/libvirt_functions.stp BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Chutrp (%build) Child return code was: 1 So, this is a new failure, but the problem stuck in ceph wasn't present in this execution. Should be noticed that only one attempt of build- pkgs was needed to get here. -Erich On Thu, 2018-09-27 at 11:21 -0700, Saul Wold wrote: > > On 09/26/2018 09:16 AM, Scott Little wrote: > > aclocal 'too many loops' has been popping up sporadically for a > > week or > > two now. Possibly 7.5 related. > > > > I suspect that there is a build order and/or race condition element > > to > > this. It often goes away if you just run build-pkgs a second > > time. > > > > I am seeing this failure also, but it does not go away after a > second > rebuild. I have the lastest stx-root (build-tools) with the recent > patches. > > Is this directly related to the fuzz issue or is there something else > we > need to address in CEPH itself. > > This is blocking my local build. > > Sau! > > > The second possible element is that build-pkgs is using flags that > > preserve the mock environment between packages. The goal was to > > avoid > > reinstalling required packages that are often common across the > > packages > > we build. It was a build time speedup that has been in use for 2- > > 3 > > years now without incident. > > > > Google shows that other folks have hit 'aclocal too many loops' as > > well, > > and there are suggestions that it might be fixed in a recent update > > to > > automake. Scanning the changelog for the latest and greatest from > > gnu.org doesn't show any obvious fixes addressing this issue. > > > > Scott > > > > > > On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: > > > BUILDSTDERR: aclocal: error: too many loops > > > BUILDSTDERR: aclocal: Please contact. > > > BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm > > > line 662. > > > BUILDSTDERR: Automake::Channels::msg('automake', '', 'too > > > many loops') called at /usr/share/automake- > > > 1.13/Automake/ChannelDefs.pm line 212 > > > BUILDSTDERR: Automake::ChannelDefs::prog_error('too many > > > loops') called at /usr/bin/aclocal line 1187 > > > BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c > > > (%build) > > > BUILDSTDERR: Macro expanded in comment on line 214: %global > > > _libexecdir %{_exec_prefix}/lib > > > BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c > > > (%build) > > > > > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Thu Sep 27 21:57:00 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 27 Sep 2018 16:57:00 -0500 Subject: [Starlingx-discuss] StarlingX Release Notes Content In-Reply-To: References: Message-ID: On Thu, Sep 27, 2018 at 3:25 PM, Arce Moreno, Abraham wrote: >> [0] https://etherpad.openstack.org/p/stx-docs >> [1] https://review.openstack.org/#/c/600198/3/releasenotes/notes/release- >> summary-9c35dd1bd9b020f1.yaml > > All repos have now Reno as their release notes manager so let us know > what else is needed and when it is needed for the official release notes > in each individual repository. I've updated the etherpad to have the correct RST format without using etherpad tabs and bullets since we're short on time to get these in... I haven't seen any reviews for this yet, if anyone is working on them please double-check the formatting locally to make sure it looks as expected. I would like to have these in before branch, it simplifies the sections down the road...who is planning to create the notes? dt -- Dean Troyer dtroyer at gmail.com From abraham.arce.moreno at intel.com Thu Sep 27 22:03:52 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 27 Sep 2018 22:03:52 +0000 Subject: [Starlingx-discuss] StarlingX Release Notes Content In-Reply-To: References: Message-ID: > On Thu, Sep 27, 2018 at 3:25 PM, Arce Moreno, Abraham > wrote: > >> [0] https://etherpad.openstack.org/p/stx-docs > >> [1] > https://review.openstack.org/#/c/600198/3/releasenotes/notes/release- > >> summary-9c35dd1bd9b020f1.yaml > > > > All repos have now Reno as their release notes manager so let us know > > what else is needed and when it is needed for the official release notes > > in each individual repository. > > I've updated the etherpad to have the correct RST format without using > etherpad tabs and bullets since we're short on time to get these in... > > I haven't seen any reviews for this yet, if anyone is working on them > please double-check the formatting locally to make sure it looks as > expected. > > I would like to have these in before branch, it simplifies the > sections down the road...who is planning to create the notes? My bad, I assumed this was intended after we pass our validation. I am working on them now. From abraham.arce.moreno at intel.com Thu Sep 27 22:13:34 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 27 Sep 2018 22:13:34 +0000 Subject: [Starlingx-discuss] StarlingX Release Notes Content In-Reply-To: References: Message-ID: > > > All repos have now Reno as their release notes manager so let us > > > know what else is needed and when it is needed for the official > > > release notes in each individual repository. > > > > I've updated the etherpad to have the correct RST format without using > > etherpad tabs and bullets since we're short on time to get these in... > > > > I haven't seen any reviews for this yet, if anyone is working on them > > please double-check the formatting locally to make sure it looks as > > expected. > > > > I would like to have these in before branch, it simplifies the > > sections down the road...who is planning to create the notes? > > My bad, I assumed this was intended after we pass our validation. > I am working on them now. Here you have the first, let me know if this is ok so I can work with the rest of the projects. https://review.openstack.org/#/c/605872 From jim.somerville at windriver.com Thu Sep 27 22:27:36 2018 From: jim.somerville at windriver.com (Jim Somerville) Date: Thu, 27 Sep 2018 18:27:36 -0400 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <9fcf603c-11a8-cc75-9683-61eb802997ef@linux.intel.com> Message-ID: <5beeffc5-66e6-0fd8-f48a-8183d0243c19@windriver.com> On 2018-09-27 05:48 PM, Cordoba Malibran, Erich wrote: > Hi, > > I did this experiment: > > I cherry pick all the defuzzed patches and try to build. The result was > that the build failing packages now are: > > libvirt-python-4.7.0-1.tis.1.src.rpm vm-topology-1.0- > 1.tis.src.rpm libvirt-4.7.0-1.tis.22.src.rpm > > which basically is just libvirt, the other ones are just depending on > libvirt. Checking the build.log for libvirt: > > > Making all in src > make[2]: Entering directory `/builddir/build/BUILD/libvirt-4.7.0/src' > BUILDSTDERR: make[2]: *** No rule to make target `keycodemapdb/data/keymaps.csv', needed by `util/virkeycodetable_linux.h'. Stop. Hi Erich, Check your stx/downloads directory, what version of keycodemapdb do you have in there? You need keycodemapdb-16e5b07.tar.gz which you should have received via the change to stx-tools/centos-mirror-tools/tarball-dl.lst -Jim > make[2]: Leaving directory `/builddir/build/BUILD/libvirt-4.7.0/src' > BUILDSTDERR: make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/builddir/build/BUILD/libvirt-4.7.0' > BUILDSTDERR: make: *** [all] Error 2 > RPM build errors: > BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Chutrp (%build) > BUILDSTDERR: Macro expanded in comment on line 2067: %{_datadir}/systemtap/tapset/libvirt_probes*.stp > BUILDSTDERR: Macro expanded in comment on line 2068: %{_datadir}/systemtap/tapset/libvirt_qemu_probes*.stp > BUILDSTDERR: Macro expanded in comment on line 2069: %{_datadir}/systemtap/tapset/libvirt_functions.stp > BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Chutrp (%build) > Child return code was: 1 > > So, this is a new failure, but the problem stuck in ceph wasn't present > in this execution. Should be noticed that only one attempt of build- > pkgs was needed to get here. > > -Erich > > > On Thu, 2018-09-27 at 11:21 -0700, Saul Wold wrote: >> >> On 09/26/2018 09:16 AM, Scott Little wrote: >>> aclocal 'too many loops' has been popping up sporadically for a >>> week or >>> two now. Possibly 7.5 related. >>> >>> I suspect that there is a build order and/or race condition element >>> to >>> this. It often goes away if you just run build-pkgs a second >>> time. >>> >> >> I am seeing this failure also, but it does not go away after a >> second >> rebuild. I have the lastest stx-root (build-tools) with the recent >> patches. >> >> Is this directly related to the fuzz issue or is there something else >> we >> need to address in CEPH itself. >> >> This is blocking my local build. >> >> Sau! >> >>> The second possible element is that build-pkgs is using flags that >>> preserve the mock environment between packages. The goal was to >>> avoid >>> reinstalling required packages that are often common across the >>> packages >>> we build. It was a build time speedup that has been in use for 2- >>> 3 >>> years now without incident. >>> >>> Google shows that other folks have hit 'aclocal too many loops' as >>> well, >>> and there are suggestions that it might be fixed in a recent update >>> to >>> automake. Scanning the changelog for the latest and greatest from >>> gnu.org doesn't show any obvious fixes addressing this issue. >>> >>> Scott >>> >>> >>> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >>>> BUILDSTDERR: aclocal: error: too many loops >>>> BUILDSTDERR: aclocal: Please contact. >>>> BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm >>>> line 662. >>>> BUILDSTDERR: Automake::Channels::msg('automake', '', 'too >>>> many loops') called at /usr/share/automake- >>>> 1.13/Automake/ChannelDefs.pm line 212 >>>> BUILDSTDERR: Automake::ChannelDefs::prog_error('too many >>>> loops') called at /usr/bin/aclocal line 1187 >>>> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>>> (%build) >>>> BUILDSTDERR: Macro expanded in comment on line 214: %global >>>> _libexecdir %{_exec_prefix}/lib >>>> BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c >>>> (%build) >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>> s >>> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From cesar.lara at intel.com Thu Sep 27 23:24:45 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Thu, 27 Sep 2018 23:24:45 +0000 Subject: [Starlingx-discuss] [meetings][build] Build team meeting Agenda for 10/1/2018 In-Reply-To: References: <0B566C62EC792145B40E29EFEBF1AB4710521086@fmsmsx104.amr.corp.intel.com> Message-ID: <0B566C62EC792145B40E29EFEBF1AB4710522916@fmsmsx104.amr.corp.intel.com> Sorry to hear that Scott, I'll ask around to check on time slot availability and get back so we can pick a more convenient one. The participation from all of you is important and greatly appreciated Regards Cesar Lara From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, September 27, 2018 1:03 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [meetings][build] Build team meeting Agenda for 10/1/2018 Don't suppose we could find another time slot? This meeting keeps colliding with my wifes eye doc appointments ... detached retina, macular tear, cataract... a long saga. Mondays are a problem. Scott On 18-09-26 05:11 PM, Lara, Cesar wrote: StarlingX Build team meeting Agenda for 10/1/2018 * Build issues on intel side - Findings and next steps - Mock cleanup proposal - General discussion * Proposals for hosting with cengn * Brainstorming for next release * Re-scoping of stxb tool Regards Cesar Lara Software Engineering Manager OpenSource Technology Center _______________________________________________ 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 ran1.an at intel.com Fri Sep 28 00:59:31 2018 From: ran1.an at intel.com (An, Ran1) Date: Fri, 28 Sep 2018 00:59:31 +0000 Subject: [Starlingx-discuss] [Container] Please help review code Message-ID: <9BAB5B7CAF57C3459E4636391F1071CECC7273@shsmsx102.ccr.corp.intel.com> Hi Could anyone can help and review this commit? https://review.openstack.org/#/c/605319/ Thanks Ran From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Thursday, September 13, 2018 9:16 PM To: An, Ran1 ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [Container] Story of Initial Kubernetes Integration Ran: That's for your offer to assist. You can take the 24909 task to add unit tests. Please add Al Bailey and Bart Wensley as reviewers when you are ready. But let's leave the 24910 task unassigned for the moment as we think this may not be required. I have an action to discuss this one with the technical leads. Frank Miller Containers Project Lead From: An, Ran1 [mailto:ran1.an at intel.com] Sent: Thursday, September 13, 2018 3:31 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Container] Story of Initial Kubernetes Integration Hi I am going to take task 24909 and 24910 under story initial kubernetes integration , anyone has concerns? Details: story: https://storyboard.openstack.org/#!/story/2002843 , Task 24909- Add unit tests for nfv kubernetes api Task 24910- Use SSL/TLS in nfv kubernetes client Thanks Ran -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Fri Sep 28 01:02:25 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Fri, 28 Sep 2018 01:02:25 +0000 Subject: [Starlingx-discuss] May have to consider an lshell replacement In-Reply-To: References: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> <9A85D2917C58154C960D95352B22818BAB5A73B1@fmsmsx117.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B389BAC@SHSMSX104.ccr.corp.intel.com> Is LShell and ibsh specific to CentOS or it applicable for other OS? Say for example, can we look for alternatives that Ubuntu or ClearLinux is using for the similar functionality? Thanks. - cindy -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Friday, September 28, 2018 3:07 AM To: Jones, Bruce E Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] May have to consider an lshell replacement On Thu, Sep 27, 2018 at 12:45 PM, Jones, Bruce E wrote: > What alternatives do we have for this functionality? Alternatives in increasing levels of commitment to lshell: * replace it * fork the project and fix the CVEs and continue * adopt the project and take over maintenance as a stand0-alone project should the existing maintainer be interested in doing so[0] I am specifically not listing 'do nothing' as active CVEs must be addressed... dt [0] OpenStack has done this on occasion when a dependency goes dormant and the maintainer has no interest in continuing and the cost of converting outweighs the perceived cost of maintenance and ownership. -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From shuicheng.lin at intel.com Fri Sep 28 06:27:15 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 28 Sep 2018 06:27:15 +0000 Subject: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm In-Reply-To: <33b41902-d812-709a-c77a-dc902b5715d7@windriver.com> References: <9700A18779F35F49AF027300A49E7C76553830F7@SHSMSX101.ccr.corp.intel.com> <33b41902-d812-709a-c77a-dc902b5715d7@windriver.com> Message-ID: <9700A18779F35F49AF027300A49E7C76553834D4@SHSMSX101.ccr.corp.intel.com> Hi Scott, What do you think about upgrade rpm in mirror lst to 4.14 version? So we could get rid of the fuzz issue. To do this upgrade, rpm will be moved from centos repo lst to tarball lst. Here is the release notes of rpm-4.13 to fix this fuzz issue: Enable –no-backup-if-mismatch by default in %patch macro (RhBug:884755) Best Regards Shuicheng From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, September 27, 2018 11:24 PM To: Lin, Shuicheng ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm Yes, I've seen some upstream packages that ship from CentOS or EL7 with fuzzy patches. Can't do much about that. My list might include packages where the only fuzzy patches are those coming from CentOS. We'll have to sort through them by hand I think. Scott On 18-09-27 10:24 AM, Lin, Shuicheng wrote: Hi all, Here is the patch list to de-fuzz the patches in CentOS7.5 upgrade task. https://review.openstack.org/#/q/topic:patch_fuzz+(status:open+OR+status:merged) I notice there are some other src rpms also have the fuzzy issue. Will handle them later. Also, I find some SRC RPM itself has the fuzzy issue, such as openldap/rsync/netpbm/openssh etc. So we cannot eliminate all fuzzy issue just by rebase ourselves patches. Best Regards Shuicheng From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, September 27, 2018 5:08 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build I have also been investigating another intermittent build error affecting initscripts. https://bugs.launchpad.net/starlingx/+bug/1794611 So any given package might be built by rpm-4.11.3, or by rpm-4.14.0. It's a race with many inputs. Ideally it shouldn't matter, but it does. build-pkgs --serial might reduce the odds, but likely won't solve it entirely. In this case it is a new option that rpm passes to the patch command, --no-backup-if-mismatch, first introduced by rpm-4.13. This option has the effect of suppressing the creation of '.orig' files. Creation of .orig files are a consequence of applying patches that are not clean. Unclean patches are ones that require 'fuzzing', i.e. treat the patch line numbers as approximate, rather than a strict requirement, just so long as the before/after context seems to be correct. Prior to StarlingX, my policy for rebasing patches was that no fuzz is tolerated in our patches. All the work to upgrade to 7.5 has created a lot of fuzzy patches. audit-2.8.1-3.el7.tis.2 bash-4.2.46-30.el7.tis.3 dhcp-4.2.5-68.el7.centos.1.tis.8 dnsmasq-2.76-5.el7.tis.6 drbd-8.4.3-0.tis.6 facter-2.4.4-4.el7.tis.4 haproxy-1.5.18-7.el7.tis.7 initscripts-9.49.41-1.el7.tis.16 iptables-1.4.21-24.1.el7_5.tis.3 kubernetes-1.10.0-1.tis.1 libevent-2.0.21-4.el7.tis.2 lighttpd-1.4.50-1.el7.tis.6 logrotate-3.8.6-15.el7.tis.3 netpbm-10.79.00-7.el7.tis.2 net-snmp-5.7.2-33.el7_5.2.tis.10 net-tools-2.0-0.22.20131004git.el7.tis.2 nfs-utils-1.3.0-0.54.el7.tis.4 nss-pam-ldapd-0.8.13-16.el7.tis.4 ntp-4.2.6p5-28.el7.centos.tis.3 openldap-2.4.44-15.el7_5.tis.8 openssh-7.4p1-16.el7_4.tis.9 pam-1.1.8-22.el7.tis.4 puppet-4.8.2-1.el7.tis.2 puppet-ceph-2.4.1-1.el7.tis.4 puppet-horizon-11.5.0-1.el7.tis.1 python-2.7.5-69.el7_5.tis.3 python-keyring-5.7.1-1.tis.2 python-wsme-0.9.2-1.el7.tis.3 resource-agents-3.9.5-124.el7.tis.12 rsync-3.1.2-4.el7.tis.2 shadow-utils-4.1.5.1-24.el7.tis.4 sudo-1.8.19p2-14.el7_5.tis.3 watchdog-5.13-11.el7.tis.2 So any of these packages might or might not produce unwanted .orig files. The .orig files might or might not be packaged, or break packaging. So there are a number of threads to pull at here. 1) Are fuzzy patches tolerated. I vote no. Sooner or later a fuzzy patch will be mis-applied and cause us problems. 2) Can we force rpmbuild within mock to use a consistent policy with respect to creation of orig files? 3) Can we pre-build rpm, such that all packages build against the same rpm version? 4) Are we patching any other low level build tools that have similar issues? Possibly explaining ceph? TBD On 18-09-26 12:16 PM, Scott Little wrote: aclocal 'too many loops' has been popping up sporadically for a week or two now. Possibly 7.5 related. I suspect that there is a build order and/or race condition element to this. It often goes away if you just run build-pkgs a second time. The second possible element is that build-pkgs is using flags that preserve the mock environment between packages. The goal was to avoid reinstalling required packages that are often common across the packages we build. It was a build time speedup that has been in use for 2-3 years now without incident. Google shows that other folks have hit 'aclocal too many loops' as well, and there are suggestions that it might be fixed in a recent update to automake. Scanning the changelog for the latest and greatest from gnu.org doesn't show any obvious fixes addressing this issue. Scott On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: BUILDSTDERR: aclocal: error: too many loops BUILDSTDERR: aclocal: Please contact . BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) _______________________________________________ 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 cindy.xie at intel.com Fri Sep 28 08:11:54 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Fri, 28 Sep 2018 08:11:54 +0000 Subject: [Starlingx-discuss] No StarlingX non-OpenStack Distro meeting on Oct 3rd Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B38A219@SHSMSX104.ccr.corp.intel.com> China team on National Holiday. The meeting for Oct 3 will be skipped. Thx. - cindy -----Original Appointment----- From: Xie, Cindy Sent: Friday, August 24, 2018 9:38 AM To: Xie, Cindy; Khalil, Ghada; Wold, Saul; Rowsell, Brent; Sun, Austin; Wang, Yi C; Lin, Shuicheng; Chen, Yan; Somerville, Jim; 'Ildiko Vancsa'; starlingx-discuss at lists.starlingx.io Cc: Perez Rodriguez, Humberto I; Hu, Yong; Zhu, Vivian; 'Chen, Jacky'; 'Leo Xu'; 'Waines, Greg'; 'Eslimi, Dariush'; 'Komiyama, Takeo'; Martinez Monroy, Elio; Jones, Bruce E; Hernandez Gonzalez, Fernando; Hu, Wei W; Qi, Mingyuan; 'Young, Ken'; Arce Moreno, Abraham; 'Seiler, Glenn'; Gomez, Juan P; Shang, Dehao Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, October 3, 2018 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 * Cadence and time slot: o Wednesday 9AM EDT (9PM China time) * Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other -------------- next part -------------- An HTML attachment was scrubbed... URL: From li.kai at 99cloud.net Fri Sep 28 02:42:30 2018 From: li.kai at 99cloud.net (kai) Date: Fri, 28 Sep 2018 10:42:30 +0800 Subject: [Starlingx-discuss] =?utf-8?b?562U5aSNOiAgWyBUZXN0IF0gc3R4LjIw?= =?utf-8?q?18=2E10_test_plan?= In-Reply-To: <4F6AACE4B0F173488D033B02A8BB5B7E716E81DD@fmsmsx104.amr.corp.intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E716E81DD@fmsmsx104.amr.corp.intel.com> Message-ID: Hi, Ada, where can we find the detail test steps for each test case? -----邮件原件----- 发件人: Cabrales, Ada 发送时间: 2018年9月22日 7:54 收件人: starlingx-discuss at lists.starlingx.io 主题: [Starlingx-discuss] [ Test ] stx.2018.10 test plan Hello, I'm posting the test plan proposed for the October Release in the wiki [0]. We have 238 tests so far, mostly focus on the stx services. As we mentioned before, the tests will be run manually by our team for this release. The expectation is to increase the number of automated tests along time. We are considering to cover the four configurations (Simplex, Duplex, Multinode local storage, Multinode external storage) both on bare metal and virtual. However, we are experiencing setup problems with multinode bare metal and simplex. We are digging into it. We'll have more information next week. Please take a look at it and let us know what else must be included. Thanks Ada [0] https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Fri Sep 28 08:12:09 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Fri, 28 Sep 2018 08:12:09 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX non-OpenStack Distro meeting Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B38A244@SHSMSX104.ccr.corp.intel.com> * Cadence and time slot: o Wednesday 9AM EDT (9PM China time) * Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5104 bytes Desc: not available URL: From jimmy at openstack.org Fri Sep 28 13:24:34 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Fri, 28 Sep 2018 08:24:34 -0500 Subject: [Starlingx-discuss] OpenStack Summit Forum Submission Process Extended Message-ID: <5BAE2B92.4030409@openstack.org> Hello Everyone We are extended the Forum Submission process through September 30, 11:59pm Pacific (6:59am GMT). We've already gotten a ton of great submissions, but we want to leave the door open through the weekend in case we have any stragglers. Please submit your topics here: https://www.openstack.org/summit/berlin-2018/call-for-presentations If you'd like to review the submissions to date, you can go to https://www.openstack.org/summit/berlin-2018/vote-for-speakers. There is no voting period, this is just so Forum attendees can review the submissions to date. Thank you! Jimmy From Ken.Young at windriver.com Fri Sep 28 13:54:08 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Fri, 28 Sep 2018 13:54:08 +0000 Subject: [Starlingx-discuss] May have to consider an lshell replacement In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B389BAC@SHSMSX104.ccr.corp.intel.com> References: <1fd79d0c-6ec7-4e11-0640-f2d0b45e3254@linux.intel.com> <9A85D2917C58154C960D95352B22818BAB5A73B1@fmsmsx117.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B389BAC@SHSMSX104.ccr.corp.intel.com> Message-ID: <87EB7586-00DA-42C2-A626-95FBDCEEE927@windriver.com> Cindy, I will copy these questions to the launchpad. Team,. Please keep all discussion of this issue within the launchpad. Regards, Ken Y On 2018-09-27, 9:02 PM, "Xie, Cindy" wrote: Is LShell and ibsh specific to CentOS or it applicable for other OS? Say for example, can we look for alternatives that Ubuntu or ClearLinux is using for the similar functionality? Thanks. - cindy -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Friday, September 28, 2018 3:07 AM To: Jones, Bruce E Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] May have to consider an lshell replacement On Thu, Sep 27, 2018 at 12:45 PM, Jones, Bruce E wrote: > What alternatives do we have for this functionality? Alternatives in increasing levels of commitment to lshell: * replace it * fork the project and fix the CVEs and continue * adopt the project and take over maintenance as a stand0-alone project should the existing maintainer be interested in doing so[0] I am specifically not listing 'do nothing' as active CVEs must be addressed... dt [0] OpenStack has done this on occasion when a dependency goes dormant and the maintainer has no interest in continuing and the cost of converting outweighs the perceived cost of maintenance and ownership. -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Fri Sep 28 13:54:25 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 28 Sep 2018 09:54:25 -0400 Subject: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm In-Reply-To: <9700A18779F35F49AF027300A49E7C76553834D4@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76553830F7@SHSMSX101.ccr.corp.intel.com> <33b41902-d812-709a-c77a-dc902b5715d7@windriver.com> <9700A18779F35F49AF027300A49E7C76553834D4@SHSMSX101.ccr.corp.intel.com> Message-ID: <9c43419b-b546-a797-b2ab-8ffc349b5da6@windriver.com> Certainly that will prevent creation of .orig files, so the risk of build failures in the packaging phase will be eliminated. However I have strong distrust of fuzzy patches.  It suggests to me that folks are upgrading packages without doing the due diligence to make sure the patches are still needed, and are being applied correctly. Also I have seen twice in my career, a fuzzy patch get improperly applied to a neighboring bit of code that happened to look similar to the proper target.  It's rare, but it can occur. On the plus side, moving to 4.14 would give us a consistent version of rpm throughout the build.  That I like. I'm thinking we should do it, but we need a no fuzzy patches policy, and perhaps we create an audit that looks for fuzzy patches. Scott On 18-09-28 02:27 AM, Lin, Shuicheng wrote: > > Hi Scott, > > What do you think about upgrade rpm in mirror lst to 4.14 version? So > we could get rid of the fuzz issue. > > To do this upgrade, rpm will be moved from centos repo lst to tarball lst. > > Here is the release notes of rpm-4.13 to fix this fuzz issue: > > Enable –no-backup-if-mismatch by default in %patch macro (RhBug:884755 > ) > > Best Regards > > Shuicheng > > *From:*Scott Little [mailto:scott.little at windriver.com] > *Sent:* Thursday, September 27, 2018 11:24 PM > *To:* Lin, Shuicheng ; > starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm > > Yes, I've seen some upstream packages that ship from CentOS or EL7 > with fuzzy patches.  Can't do much about that. > > My list might include packages where the only fuzzy patches are those > coming from CentOS.  We'll have to sort through them by hand I think. > > Scott > > > > On 18-09-27 10:24 AM, Lin, Shuicheng wrote: > > Hi all, > > Here is the patch list to de-fuzz the patches in CentOS7.5 upgrade > task. > > https://review.openstack.org/#/q/topic:patch_fuzz+(status:open+OR+status:merged) > > > I notice there are some other src rpms also have the fuzzy issue. > Will handle them later. > > Also, I find some SRC RPM itself has the fuzzy issue, such as > openldap/rsync/netpbm/openssh etc. > > So we cannot eliminate all fuzzy issue just by rebase ourselves > patches. > > Best Regards > > Shuicheng > > *From:*Scott Little [mailto:scott.little at windriver.com] > *Sent:* Thursday, September 27, 2018 5:08 AM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] build-pkgs cannot complete std > build > > I have also been investigating another intermittent build error > affecting initscripts. > > https://bugs.launchpad.net/starlingx/+bug/1794611 > > So any given package might be built by rpm-4.11.3, or by > rpm-4.14.0.  It's a race with many inputs.  Ideally it shouldn't > matter, but it does.  build-pkgs --serial might reduce the odds, > but likely won't solve it entirely. > > In this case it is a new option that rpm passes to the patch > command, --no-backup-if-mismatch, first introduced by rpm-4.13. > This option has the effect of suppressing the creation of '.orig' > files. > > Creation of .orig files are a consequence of applying patches that > are not clean. Unclean patches are ones that require 'fuzzing', > i.e. treat the patch line numbers as approximate, rather than a > strict requirement, just so long as the before/after context seems > to be correct. > > Prior to StarlingX, my policy for rebasing patches was that no > fuzz is tolerated in our patches. > > All the work to upgrade to 7.5 has created a lot of fuzzy patches. > > audit-2.8.1-3.el7.tis.2 > bash-4.2.46-30.el7.tis.3 > dhcp-4.2.5-68.el7.centos.1.tis.8 > dnsmasq-2.76-5.el7.tis.6 > drbd-8.4.3-0.tis.6 > facter-2.4.4-4.el7.tis.4 > haproxy-1.5.18-7.el7.tis.7 > initscripts-9.49.41-1.el7.tis.16 > iptables-1.4.21-24.1.el7_5.tis.3 > kubernetes-1.10.0-1.tis.1 > libevent-2.0.21-4.el7.tis.2 > lighttpd-1.4.50-1.el7.tis.6 > logrotate-3.8.6-15.el7.tis.3 > netpbm-10.79.00-7.el7.tis.2 > net-snmp-5.7.2-33.el7_5.2.tis.10 > net-tools-2.0-0.22.20131004git.el7.tis.2 > nfs-utils-1.3.0-0.54.el7.tis.4 > nss-pam-ldapd-0.8.13-16.el7.tis.4 > ntp-4.2.6p5-28.el7.centos.tis.3 > openldap-2.4.44-15.el7_5.tis.8 > openssh-7.4p1-16.el7_4.tis.9 > pam-1.1.8-22.el7.tis.4 > puppet-4.8.2-1.el7.tis.2 > puppet-ceph-2.4.1-1.el7.tis.4 > puppet-horizon-11.5.0-1.el7.tis.1 > python-2.7.5-69.el7_5.tis.3 > python-keyring-5.7.1-1.tis.2 > python-wsme-0.9.2-1.el7.tis.3 > resource-agents-3.9.5-124.el7.tis.12 > rsync-3.1.2-4.el7.tis.2 > shadow-utils-4.1.5.1-24.el7.tis.4 > sudo-1.8.19p2-14.el7_5.tis.3 > watchdog-5.13-11.el7.tis.2 > > So any of these packages might or might not produce unwanted .orig > files. > The .orig files might or might not be packaged, or break packaging. > > So there are a number of threads to pull at here. > 1) Are fuzzy patches tolerated.   I vote no.  Sooner or later a > fuzzy patch will be mis-applied and cause us problems. > 2) Can we force rpmbuild within mock to use a consistent policy > with respect to creation of orig files? > 3) Can we pre-build rpm, such that all packages build against the > same rpm version? > 4) Are we patching any other low level build tools that have > similar issues?  Possibly explaining ceph?  TBD > > > > On 18-09-26 12:16 PM, Scott Little wrote: > > aclocal 'too many loops' has been popping up sporadically for > a week or two now.  Possibly 7.5 related. > > I suspect that there is a build order and/or race condition > element to this.   It often goes away if you just run > build-pkgs a second time. > > The second possible element is that build-pkgs is using flags > that preserve the mock environment between packages.  The goal > was to avoid reinstalling required packages that are often > common across the packages we build.   It was a build time > speedup that has been in use for 2-3 years now without incident. > > Google shows that other folks have hit 'aclocal too many > loops' as well, and there are suggestions that it might be > fixed in a recent update to automake.  Scanning the changelog > for the latest and greatest from gnu.org doesn't show any > obvious fixes addressing this issue. > > Scott > > > On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: > > BUILDSTDERR: aclocal: error: too many loops > > BUILDSTDERR: aclocal: Please contact . > > BUILDSTDERR:  at /usr/share/automake-1.13/Automake/Channels.pm line 662. > > BUILDSTDERR:    Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 > > BUILDSTDERR:    Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 > > BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) > > BUILDSTDERR:     Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib > > BUILDSTDERR:     Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) > > > > > > _______________________________________________ > > 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 sgw at linux.intel.com Fri Sep 28 14:08:33 2018 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 28 Sep 2018 07:08:33 -0700 Subject: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm In-Reply-To: <9c43419b-b546-a797-b2ab-8ffc349b5da6@windriver.com> References: <9700A18779F35F49AF027300A49E7C76553830F7@SHSMSX101.ccr.corp.intel.com> <33b41902-d812-709a-c77a-dc902b5715d7@windriver.com> <9700A18779F35F49AF027300A49E7C76553834D4@SHSMSX101.ccr.corp.intel.com> <9c43419b-b546-a797-b2ab-8ffc349b5da6@windriver.com> Message-ID: <684da4a8-8b8e-69b0-796a-ac89f85713b1@linux.intel.com> On 09/28/2018 06:54 AM, Scott Little wrote: > Certainly that will prevent creation of .orig files, so the risk of > build failures in the packaging phase will be eliminated. > However I have strong distrust of fuzzy patches.  It suggests to me that > folks are upgrading packages without doing the > due diligence to make sure the patches are still needed, and are being > applied correctly. > > Also I have seen twice in my career, a fuzzy patch get improperly > applied to a neighboring bit of code that happened to > look similar to the proper target.  It's rare, but it can occur. > I agree with this, I have also been "bitten" by a mis-applied fuzz patch. > On the plus side, moving to 4.14 would give us a consistent version of > rpm throughout the build.  That I like. > > I'm thinking we should do it, but we need a no fuzzy patches policy, and > perhaps we create an audit that looks for fuzzy patches. > This sounds like a good plan for post-October release Sau! > Scott > > > > On 18-09-28 02:27 AM, Lin, Shuicheng wrote: >> >> Hi Scott, >> >> What do you think about upgrade rpm in mirror lst to 4.14 version? So >> we could get rid of the fuzz issue. >> >> To do this upgrade, rpm will be moved from centos repo lst to tarball lst. >> >> Here is the release notes of rpm-4.13 to fix this fuzz issue: >> >> Enable –no-backup-if-mismatch by default in %patch macro (RhBug:884755 >> ) >> >> Best Regards >> >> Shuicheng >> >> *From:*Scott Little [mailto:scott.little at windriver.com] >> *Sent:* Thursday, September 27, 2018 11:24 PM >> *To:* Lin, Shuicheng ; >> starlingx-discuss at lists.starlingx.io >> *Subject:* Re: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm >> >> Yes, I've seen some upstream packages that ship from CentOS or EL7 >> with fuzzy patches.  Can't do much about that. >> >> My list might include packages where the only fuzzy patches are those >> coming from CentOS.  We'll have to sort through them by hand I think. >> >> Scott >> >> >> >> On 18-09-27 10:24 AM, Lin, Shuicheng wrote: >> >> Hi all, >> >> Here is the patch list to de-fuzz the patches in CentOS7.5 upgrade >> task. >> >> https://review.openstack.org/#/q/topic:patch_fuzz+(status:open+OR+status:merged) >> >> >> I notice there are some other src rpms also have the fuzzy issue. >> Will handle them later. >> >> Also, I find some SRC RPM itself has the fuzzy issue, such as >> openldap/rsync/netpbm/openssh etc. >> >> So we cannot eliminate all fuzzy issue just by rebase ourselves >> patches. >> >> Best Regards >> >> Shuicheng >> >> *From:*Scott Little [mailto:scott.little at windriver.com] >> *Sent:* Thursday, September 27, 2018 5:08 AM >> *To:* starlingx-discuss at lists.starlingx.io >> >> *Subject:* Re: [Starlingx-discuss] build-pkgs cannot complete std >> build >> >> I have also been investigating another intermittent build error >> affecting initscripts. >> >> https://bugs.launchpad.net/starlingx/+bug/1794611 >> >> So any given package might be built by rpm-4.11.3, or by >> rpm-4.14.0.  It's a race with many inputs.  Ideally it shouldn't >> matter, but it does.  build-pkgs --serial might reduce the odds, >> but likely won't solve it entirely. >> >> In this case it is a new option that rpm passes to the patch >> command, --no-backup-if-mismatch, first introduced by rpm-4.13. >> This option has the effect of suppressing the creation of '.orig' >> files. >> >> Creation of .orig files are a consequence of applying patches that >> are not clean. Unclean patches are ones that require 'fuzzing', >> i.e. treat the patch line numbers as approximate, rather than a >> strict requirement, just so long as the before/after context seems >> to be correct. >> >> Prior to StarlingX, my policy for rebasing patches was that no >> fuzz is tolerated in our patches. >> >> All the work to upgrade to 7.5 has created a lot of fuzzy patches. >> >> audit-2.8.1-3.el7.tis.2 >> bash-4.2.46-30.el7.tis.3 >> dhcp-4.2.5-68.el7.centos.1.tis.8 >> dnsmasq-2.76-5.el7.tis.6 >> drbd-8.4.3-0.tis.6 >> facter-2.4.4-4.el7.tis.4 >> haproxy-1.5.18-7.el7.tis.7 >> initscripts-9.49.41-1.el7.tis.16 >> iptables-1.4.21-24.1.el7_5.tis.3 >> kubernetes-1.10.0-1.tis.1 >> libevent-2.0.21-4.el7.tis.2 >> lighttpd-1.4.50-1.el7.tis.6 >> logrotate-3.8.6-15.el7.tis.3 >> netpbm-10.79.00-7.el7.tis.2 >> net-snmp-5.7.2-33.el7_5.2.tis.10 >> net-tools-2.0-0.22.20131004git.el7.tis.2 >> nfs-utils-1.3.0-0.54.el7.tis.4 >> nss-pam-ldapd-0.8.13-16.el7.tis.4 >> ntp-4.2.6p5-28.el7.centos.tis.3 >> openldap-2.4.44-15.el7_5.tis.8 >> openssh-7.4p1-16.el7_4.tis.9 >> pam-1.1.8-22.el7.tis.4 >> puppet-4.8.2-1.el7.tis.2 >> puppet-ceph-2.4.1-1.el7.tis.4 >> puppet-horizon-11.5.0-1.el7.tis.1 >> python-2.7.5-69.el7_5.tis.3 >> python-keyring-5.7.1-1.tis.2 >> python-wsme-0.9.2-1.el7.tis.3 >> resource-agents-3.9.5-124.el7.tis.12 >> rsync-3.1.2-4.el7.tis.2 >> shadow-utils-4.1.5.1-24.el7.tis.4 >> sudo-1.8.19p2-14.el7_5.tis.3 >> watchdog-5.13-11.el7.tis.2 >> >> So any of these packages might or might not produce unwanted .orig >> files. >> The .orig files might or might not be packaged, or break packaging. >> >> So there are a number of threads to pull at here. >> 1) Are fuzzy patches tolerated.   I vote no.  Sooner or later a >> fuzzy patch will be mis-applied and cause us problems. >> 2) Can we force rpmbuild within mock to use a consistent policy >> with respect to creation of orig files? >> 3) Can we pre-build rpm, such that all packages build against the >> same rpm version? >> 4) Are we patching any other low level build tools that have >> similar issues?  Possibly explaining ceph?  TBD >> >> >> >> On 18-09-26 12:16 PM, Scott Little wrote: >> >> aclocal 'too many loops' has been popping up sporadically for >> a week or two now.  Possibly 7.5 related. >> >> I suspect that there is a build order and/or race condition >> element to this.   It often goes away if you just run >> build-pkgs a second time. >> >> The second possible element is that build-pkgs is using flags >> that preserve the mock environment between packages.  The goal >> was to avoid reinstalling required packages that are often >> common across the packages we build.   It was a build time >> speedup that has been in use for 2-3 years now without incident. >> >> Google shows that other folks have hit 'aclocal too many >> loops' as well, and there are suggestions that it might be >> fixed in a recent update to automake.  Scanning the changelog >> for the latest and greatest from gnu.org doesn't show any >> obvious fixes addressing this issue. >> >> Scott >> >> >> On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: >> >> BUILDSTDERR: aclocal: error: too many loops >> >> BUILDSTDERR: aclocal: Please contact . >> >> BUILDSTDERR:  at /usr/share/automake-1.13/Automake/Channels.pm line 662. >> >> BUILDSTDERR:    Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 >> >> BUILDSTDERR:    Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 >> >> BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >> >> BUILDSTDERR:     Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib >> >> BUILDSTDERR:     Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) >> >> >> >> >> >> _______________________________________________ >> >> Starlingx-discuss mailing list >> >> Starlingx-discuss at lists.starlingx.io >> >> >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Ghada.Khalil at windriver.com Fri Sep 28 17:18:36 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 28 Sep 2018 17:18:36 +0000 Subject: [Starlingx-discuss] stx.2018.10 code freeze status -- Branch creation in progress Message-ID: <151EE31B9FCCA54397A757BC674650F0BA45921C@ALA-MBD.corp.ad.wrs.com> Hello all, Dean is in the process of starting the branch creation for the stx.2018.10 release. Please do not W+1 any commits to master until the branches are created. Dean will send an email once merges can resume on master. Note: There are a few documentation updates which did not make it. Those will need to be cherry-picked to the release branches by their respective authors. Once the release branches are created, any commits tagged for stx.2018.10 need to be merged in master first and then cherry-picked to the release branch by the developer. All other commits (tagged for stx.2019.03 or untagged) should be merged in master only. Launch pads tagged for stx.2018.10: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 Stories tagged for stx.2018.10: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.2018.10 * only the doc story is expected to have additional commits that require cherrypicking. Thank you everyone for working extra hard to get in the required content for the branch creation. Regards, Ghada From bruce.e.jones at intel.com Fri Sep 28 17:43:05 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 28 Sep 2018 17:43:05 +0000 Subject: [Starlingx-discuss] stx.2018.10 code freeze status -- Branch creation in progress In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA45921C@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA45921C@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5A8459@fmsmsx117.amr.corp.intel.com> One more thing. Once we get the green light from Dean, we need builds created from the branch so testing can begin. We'll need a reference build from within both Intel and Wind River to support the test teams there. Resolving build issues on the branch and Critical/test blocking bugs found in testing should be everyone's highest priority. brucej -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Friday, September 28, 2018 10:19 AM To: Khalil, Ghada ; starlingx-discuss at lists.starlingx.io; Dean Troyer Subject: [Starlingx-discuss] stx.2018.10 code freeze status -- Branch creation in progress Hello all, Dean is in the process of starting the branch creation for the stx.2018.10 release. Please do not W+1 any commits to master until the branches are created. Dean will send an email once merges can resume on master. Note: There are a few documentation updates which did not make it. Those will need to be cherry-picked to the release branches by their respective authors. Once the release branches are created, any commits tagged for stx.2018.10 need to be merged in master first and then cherry-picked to the release branch by the developer. All other commits (tagged for stx.2019.03 or untagged) should be merged in master only. Launch pads tagged for stx.2018.10: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2018.10 Stories tagged for stx.2018.10: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.2018.10 * only the doc story is expected to have additional commits that require cherrypicking. Thank you everyone for working extra hard to get in the required content for the branch creation. Regards, Ghada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Fri Sep 28 19:32:45 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 28 Sep 2018 14:32:45 -0500 Subject: [Starlingx-discuss] [r/2018.10] StarlingX Release 2018.10 RC1 branch is complete Message-ID: I have completed branching all 44 repos for release 2018.10. This is tagged as 2018.10.rc1 for release candidate 1. We have not defined a formal release candidate process but I used the name for the branch tag as most people will know what that means: this branch will become the release when final. The final release tag will be 2018.10.0. Release branch: r/2018.10 Current tag: 2018.10.rc1 The usual list of .gitreview updates are the first reviews on the release branch in Gerrit and should be the first things approved on the branch. This list also includes an update for the manifest file. https://review.openstack.org/#/q/topic:create-r/2018.10+status:open All master branches are again open for merging ongoing work. Remember that any fixes to the release branch first get merged to master and then backported. Currently there are two reviews that were not merged before the branching (https://review.openstack.org/#/c/605254 did merge in time). They have topic set to release-backport: https://review.openstack.org/#/q/status:open+branch:master+topic:release-backport There are currently two reviews on that list (https://review.openstack.org/606123 and https://review.openstack.org/605275), they are stacked and will merge in that order once approved. Thank you for your patience and please let me or anyone on the release team know if you find any problems. dt -- Dean Troyer dtroyer at gmail.com From scott.little at windriver.com Fri Sep 28 20:39:11 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 28 Sep 2018 16:39:11 -0400 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <0471463b-7533-f743-2a79-44eebc36ae5e@linux.intel.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <9fcf603c-11a8-cc75-9683-61eb802997ef@linux.intel.com> <7270e771-bf71-5622-1249-30faa1156e35@windriver.com> <2a14c931-9bd8-9a1d-3c81-d92d3503fde4@windriver.com> <0471463b-7533-f743-2a79-44eebc36ae5e@linux.intel.com> Message-ID: <47976b76-ce32-6722-e187-c573f496fd74@windriver.com> Ok, we've seen 3 ceph failures in our last 6 builds. The common factor:  tpm2-tools builds on 'b0' before ceph builds. Our theory.  The buildRequires of tpm2-tools causes autoconf-archive to be installed... which installs a bunch of .m4 files in /usr/share/aclocal ... which causes ceph grief when it calls aclocal. I don't really know automake or aclocal all that well.  I'm assuming /usr/share/aclocal is acting something like a cache, but it's a cache whos contents are incompatible with ceph. Do we have any autotools / aclocal / m4 experts in the house? Possible fixes: - ceph: can we tell it to not use the aclocal cache... explicitly (a flag to aclocal?)  ... or implicitly (update ceph's m4 files so they look 'newer' than the cache)? - tpm2-tools: Can we remove the dependence on autoconf-archive? No other package we build seems to need it. Scott On 18-09-27 04:45 PM, Saul Wold wrote: > > And of course it worked the third time! > > So, I lost the good logs. > > Sau! > > > On 09/27/2018 12:56 PM, Scott Little wrote: >> On 18-09-27 03:53 PM, Scott Little wrote: >>> Our latest build, based on code synced at 2018-09-27T15:28:00  UTC, >>> built successfully. >>> >>> It took three attempts to get ceph built.  The first two passes >>> aborted quickly due to missing packages.  The final pass did not >>> exhibit the 'aclocal: too many loops'**issue. >>> >>> The only build I have that exhibited the too many loops error was a >>> snapshot on 2018-09-20T15:50:40 UTC >>> >>> I do have a designer with an older snapshot that seems to hit it >>> regularly, so I'll work with him and see if we can learn more. >>> >>> I think we need more data from the community >>> - Who's build is failing on ceph with *aclocal: too many loops?* >>> - Who is building successfully ? >>> - Who can build only intermittently? >>> >>> >>> >>> Info to collect for failed builds: >> - repo sync timestamp >>> - build command used? >>> - Was it a new workspace, a cleaned workspace, or a previously used >>> workspace? >> - $MY_WORKSPACE/CONTEXT >>> - $MY_WORKSPACE/build-std.log >>> - $MY_WORKSPACE/std/results/*/ceph-*/*.log >>> >>> For successful builds, same info. Rather than full build logs, I can >>> settle for: >>> - grep '\(Success building\|iteration\|building ceph\)' >>> $MY_WORKSPACE/build-std.log >>> - grep compute_resources: build-std.log >>> >>> >>> >>> >>> >>> On 18-09-27 02:21 PM, Saul Wold wrote: >>>> On 09/26/2018 09:16 AM, Scott Little wrote: >>>>> aclocal 'too many loops' has been popping up sporadically for a >>>>> week or two now.  Possibly 7.5 related. >>>>> >>>>> I suspect that there is a build order and/or race condition >>>>> element to this.   It often goes away if you just run build-pkgs a >>>>> second time. >>>>> >>>> I am seeing this failure also, but it does not go away after a >>>> second rebuild.  I have the lastest stx-root (build-tools) with the >>>> recent patches. >>>> >>>> Is this directly related to the fuzz issue or is there something >>>> else we need to address in CEPH itself. >>>> >>>> This is blocking my local build. >>>> >>>> Sau! >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> From Ghada.Khalil at windriver.com Fri Sep 28 22:15:25 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 28 Sep 2018 22:15:25 +0000 Subject: [Starlingx-discuss] Launchpad / Gerrit integration for multiple commits Message-ID: <151EE31B9FCCA54397A757BC674650F0BA459495@ALA-MBD.corp.ad.wrs.com> Hello all, I have noticed that Launchpad bugs are automatically marked as "Fix Released" even when there are multiple commits specified and not all of them are merged. In those cases, the commit message for each commit uses the "Closes-Bug". I went back to the openstack documentation for reference and found the following: https://wiki.openstack.org/wiki/GitCommitMessages * Closes-Bug: #1234567 -- use 'Closes-Bug' if the commit is intended to fully fix and close the bug being referenced. * Partial-Bug: #1234567 -- use 'Partial-Bug' if the commit is only a partial fix and more work is needed. * Related-Bug: #1234567 -- use 'Related-Bug' if the commit is merely related to the referenced bug. So if a fix requires multiple commits, I suggest you use "Partial-Bug" with only the final commit using "Closes-Bug". I have updated the StarlingX Code Submission Guidelines wiki accordingly: https://wiki.openstack.org/wiki/StarlingX/CodeSubmissionGuidelines Regards, Ghada From erich.cordoba.malibran at intel.com Fri Sep 28 22:18:00 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Fri, 28 Sep 2018 22:18:00 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <47976b76-ce32-6722-e187-c573f496fd74@windriver.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <9fcf603c-11a8-cc75-9683-61eb802997ef@linux.intel.com> <7270e771-bf71-5622-1249-30faa1156e35@windriver.com> <2a14c931-9bd8-9a1d-3c81-d92d3503fde4@windriver.com> <0471463b-7533-f743-2a79-44eebc36ae5e@linux.intel.com> <47976b76-ce32-6722-e187-c573f496fd74@windriver.com> Message-ID: Not sure if it's a valid fix but changing the two aclocal commands from aclocal -I m4 --install to aclocal -I m4 avoid to copy the macros installed by autoconf-archive into the ceph environment. -Erich On Fri, 2018-09-28 at 16:39 -0400, Scott Little wrote: > Ok, we've seen 3 ceph failures in our last 6 builds. > > The common factor: tpm2-tools builds on 'b0' before ceph builds. > > Our theory. The buildRequires of tpm2-tools causes autoconf-archive > to > be installed... which installs a bunch of .m4 files in > /usr/share/aclocal ... which causes ceph grief when it calls aclocal. > > I don't really know automake or aclocal all that well. I'm assuming > /usr/share/aclocal is acting something like a cache, but it's a > cache > whos contents are incompatible with ceph. > > Do we have any autotools / aclocal / m4 experts in the house? > > Possible fixes: > - ceph: can we tell it to not use the aclocal cache... explicitly (a > flag to aclocal?) ... or implicitly (update ceph's m4 files so they > look 'newer' than the cache)? > - tpm2-tools: Can we remove the dependence on autoconf-archive? No > other > package we build seems to need it. > > Scott > > > > On 18-09-27 04:45 PM, Saul Wold wrote: > > > > And of course it worked the third time! > > > > So, I lost the good logs. > > > > Sau! > > > > > > On 09/27/2018 12:56 PM, Scott Little wrote: > > > On 18-09-27 03:53 PM, Scott Little wrote: > > > > Our latest build, based on code synced at 2018-09-27T15:28:00 > > > > UTC, > > > > built successfully. > > > > > > > > It took three attempts to get ceph built. The first two > > > > passes > > > > aborted quickly due to missing packages. The final pass did > > > > not > > > > exhibit the 'aclocal: too many loops'**issue. > > > > > > > > The only build I have that exhibited the too many loops error > > > > was a > > > > snapshot on 2018-09-20T15:50:40 UTC > > > > > > > > I do have a designer with an older snapshot that seems to hit > > > > it > > > > regularly, so I'll work with him and see if we can learn more. > > > > > > > > I think we need more data from the community > > > > - Who's build is failing on ceph with *aclocal: too many > > > > loops?* > > > > - Who is building successfully ? > > > > - Who can build only intermittently? > > > > > > > > > > > > > > > > Info to collect for failed builds: > > > > > > - repo sync timestamp > > > > - build command used? > > > > - Was it a new workspace, a cleaned workspace, or a previously > > > > used > > > > workspace? > > > > > > - $MY_WORKSPACE/CONTEXT > > > > - $MY_WORKSPACE/build-std.log > > > > - $MY_WORKSPACE/std/results/*/ceph-*/*.log > > > > > > > > For successful builds, same info. Rather than full build logs, > > > > I can > > > > settle for: > > > > - grep '\(Success building\|iteration\|building ceph\)' > > > > $MY_WORKSPACE/build-std.log > > > > - grep compute_resources: build-std.log > > > > > > > > > > > > > > > > > > > > > > > > On 18-09-27 02:21 PM, Saul Wold wrote: > > > > > On 09/26/2018 09:16 AM, Scott Little wrote: > > > > > > aclocal 'too many loops' has been popping up sporadically > > > > > > for a > > > > > > week or two now. Possibly 7.5 related. > > > > > > > > > > > > I suspect that there is a build order and/or race > > > > > > condition > > > > > > element to this. It often goes away if you just run > > > > > > build-pkgs a > > > > > > second time. > > > > > > > > > > > > > > > > I am seeing this failure also, but it does not go away after > > > > > a > > > > > second rebuild. I have the lastest stx-root (build-tools) > > > > > with the > > > > > recent patches. > > > > > > > > > > Is this directly related to the fuzz issue or is there > > > > > something > > > > > else we need to address in CEPH itself. > > > > > > > > > > This is blocking my local build. > > > > > > > > > > Sau! > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-di > > > > scuss > > > > > > > > > > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > > uss > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Fri Sep 28 23:39:01 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 28 Sep 2018 23:39:01 +0000 Subject: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm In-Reply-To: <9c43419b-b546-a797-b2ab-8ffc349b5da6@windriver.com> References: <9700A18779F35F49AF027300A49E7C76553830F7@SHSMSX101.ccr.corp.intel.com> <33b41902-d812-709a-c77a-dc902b5715d7@windriver.com> <9700A18779F35F49AF027300A49E7C76553834D4@SHSMSX101.ccr.corp.intel.com> <9c43419b-b546-a797-b2ab-8ffc349b5da6@windriver.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB28C91F@ALA-MBD.corp.ad.wrs.com> Agree with Scott Brent From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, September 28, 2018 9:54 AM To: Lin, Shuicheng ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm Certainly that will prevent creation of .orig files, so the risk of build failures in the packaging phase will be eliminated. However I have strong distrust of fuzzy patches. It suggests to me that folks are upgrading packages without doing the due diligence to make sure the patches are still needed, and are being applied correctly. Also I have seen twice in my career, a fuzzy patch get improperly applied to a neighboring bit of code that happened to look similar to the proper target. It's rare, but it can occur. On the plus side, moving to 4.14 would give us a consistent version of rpm throughout the build. That I like. I'm thinking we should do it, but we need a no fuzzy patches policy, and perhaps we create an audit that looks for fuzzy patches. Scott On 18-09-28 02:27 AM, Lin, Shuicheng wrote: Hi Scott, What do you think about upgrade rpm in mirror lst to 4.14 version? So we could get rid of the fuzz issue. To do this upgrade, rpm will be moved from centos repo lst to tarball lst. Here is the release notes of rpm-4.13 to fix this fuzz issue: Enable –no-backup-if-mismatch by default in %patch macro (RhBug:884755) Best Regards Shuicheng From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, September 27, 2018 11:24 PM To: Lin, Shuicheng ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm Yes, I've seen some upstream packages that ship from CentOS or EL7 with fuzzy patches. Can't do much about that. My list might include packages where the only fuzzy patches are those coming from CentOS. We'll have to sort through them by hand I think. Scott On 18-09-27 10:24 AM, Lin, Shuicheng wrote: Hi all, Here is the patch list to de-fuzz the patches in CentOS7.5 upgrade task. https://review.openstack.org/#/q/topic:patch_fuzz+(status:open+OR+status:merged) I notice there are some other src rpms also have the fuzzy issue. Will handle them later. Also, I find some SRC RPM itself has the fuzzy issue, such as openldap/rsync/netpbm/openssh etc. So we cannot eliminate all fuzzy issue just by rebase ourselves patches. Best Regards Shuicheng From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, September 27, 2018 5:08 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build I have also been investigating another intermittent build error affecting initscripts. https://bugs.launchpad.net/starlingx/+bug/1794611 So any given package might be built by rpm-4.11.3, or by rpm-4.14.0. It's a race with many inputs. Ideally it shouldn't matter, but it does. build-pkgs --serial might reduce the odds, but likely won't solve it entirely. In this case it is a new option that rpm passes to the patch command, --no-backup-if-mismatch, first introduced by rpm-4.13. This option has the effect of suppressing the creation of '.orig' files. Creation of .orig files are a consequence of applying patches that are not clean. Unclean patches are ones that require 'fuzzing', i.e. treat the patch line numbers as approximate, rather than a strict requirement, just so long as the before/after context seems to be correct. Prior to StarlingX, my policy for rebasing patches was that no fuzz is tolerated in our patches. All the work to upgrade to 7.5 has created a lot of fuzzy patches. audit-2.8.1-3.el7.tis.2 bash-4.2.46-30.el7.tis.3 dhcp-4.2.5-68.el7.centos.1.tis.8 dnsmasq-2.76-5.el7.tis.6 drbd-8.4.3-0.tis.6 facter-2.4.4-4.el7.tis.4 haproxy-1.5.18-7.el7.tis.7 initscripts-9.49.41-1.el7.tis.16 iptables-1.4.21-24.1.el7_5.tis.3 kubernetes-1.10.0-1.tis.1 libevent-2.0.21-4.el7.tis.2 lighttpd-1.4.50-1.el7.tis.6 logrotate-3.8.6-15.el7.tis.3 netpbm-10.79.00-7.el7.tis.2 net-snmp-5.7.2-33.el7_5.2.tis.10 net-tools-2.0-0.22.20131004git.el7.tis.2 nfs-utils-1.3.0-0.54.el7.tis.4 nss-pam-ldapd-0.8.13-16.el7.tis.4 ntp-4.2.6p5-28.el7.centos.tis.3 openldap-2.4.44-15.el7_5.tis.8 openssh-7.4p1-16.el7_4.tis.9 pam-1.1.8-22.el7.tis.4 puppet-4.8.2-1.el7.tis.2 puppet-ceph-2.4.1-1.el7.tis.4 puppet-horizon-11.5.0-1.el7.tis.1 python-2.7.5-69.el7_5.tis.3 python-keyring-5.7.1-1.tis.2 python-wsme-0.9.2-1.el7.tis.3 resource-agents-3.9.5-124.el7.tis.12 rsync-3.1.2-4.el7.tis.2 shadow-utils-4.1.5.1-24.el7.tis.4 sudo-1.8.19p2-14.el7_5.tis.3 watchdog-5.13-11.el7.tis.2 So any of these packages might or might not produce unwanted .orig files. The .orig files might or might not be packaged, or break packaging. So there are a number of threads to pull at here. 1) Are fuzzy patches tolerated. I vote no. Sooner or later a fuzzy patch will be mis-applied and cause us problems. 2) Can we force rpmbuild within mock to use a consistent policy with respect to creation of orig files? 3) Can we pre-build rpm, such that all packages build against the same rpm version? 4) Are we patching any other low level build tools that have similar issues? Possibly explaining ceph? TBD On 18-09-26 12:16 PM, Scott Little wrote: aclocal 'too many loops' has been popping up sporadically for a week or two now. Possibly 7.5 related. I suspect that there is a build order and/or race condition element to this. It often goes away if you just run build-pkgs a second time. The second possible element is that build-pkgs is using flags that preserve the mock environment between packages. The goal was to avoid reinstalling required packages that are often common across the packages we build. It was a build time speedup that has been in use for 2-3 years now without incident. Google shows that other folks have hit 'aclocal too many loops' as well, and there are suggestions that it might be fixed in a recent update to automake. Scanning the changelog for the latest and greatest from gnu.org doesn't show any obvious fixes addressing this issue. Scott On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: BUILDSTDERR: aclocal: error: too many loops BUILDSTDERR: aclocal: Please contact . BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) _______________________________________________ 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 sgw at linux.intel.com Sat Sep 29 00:20:24 2018 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 28 Sep 2018 17:20:24 -0700 Subject: [Starlingx-discuss] build-pkgs cannot complete std build In-Reply-To: <47976b76-ce32-6722-e187-c573f496fd74@windriver.com> References: <668d78e1a36768a23f247a0a4f92b79920db33a6.camel@intel.com> <2ca0a806-58fa-34c7-0176-ac2d74a83e2d@windriver.com> <9fcf603c-11a8-cc75-9683-61eb802997ef@linux.intel.com> <7270e771-bf71-5622-1249-30faa1156e35@windriver.com> <2a14c931-9bd8-9a1d-3c81-d92d3503fde4@windriver.com> <0471463b-7533-f743-2a79-44eebc36ae5e@linux.intel.com> <47976b76-ce32-6722-e187-c573f496fd74@windriver.com> Message-ID: On 09/28/2018 01:39 PM, Scott Little wrote: > Ok, we've seen 3 ceph failures in our last 6 builds. > > The common factor:  tpm2-tools builds on 'b0' before ceph builds. > > Our theory.  The buildRequires of tpm2-tools causes autoconf-archive to > be installed... which installs a bunch of .m4 files in > /usr/share/aclocal ... which causes ceph grief when it calls aclocal. > > I don't really know automake or aclocal all that well.  I'm assuming > /usr/share/aclocal is acting something like a cache, but it's a cache > whos contents are incompatible with ceph. > > Do we have any autotools / aclocal / m4 experts in the house? > > Possible fixes: > - ceph: can we tell it to not use the aclocal cache... explicitly (a > flag to aclocal?)  ... or implicitly (update ceph's m4 files so they > look 'newer' than the cache)? Not sure about that, I would have to dig deeper into aclocal, it's been a while since I dug into that. > - tpm2-tools: Can we remove the dependence on autoconf-archive? No other > package we build seems to need it. > A quick scan show that the autoconf-archive was put in there for travis support, and goes away this past March upstream when they coverted to using a container for travis. If we could use a newer version of tpm2 that might solve this. Maybe Erich's solution can work Sau! > Scott > > > > On 18-09-27 04:45 PM, Saul Wold wrote: >> >> And of course it worked the third time! >> >> So, I lost the good logs. >> >> Sau! >> >> >> On 09/27/2018 12:56 PM, Scott Little wrote: >>> On 18-09-27 03:53 PM, Scott Little wrote: >>>> Our latest build, based on code synced at 2018-09-27T15:28:00  UTC, >>>> built successfully. >>>> >>>> It took three attempts to get ceph built.  The first two passes >>>> aborted quickly due to missing packages.  The final pass did not >>>> exhibit the 'aclocal: too many loops'**issue. >>>> >>>> The only build I have that exhibited the too many loops error was a >>>> snapshot on 2018-09-20T15:50:40 UTC >>>> >>>> I do have a designer with an older snapshot that seems to hit it >>>> regularly, so I'll work with him and see if we can learn more. >>>> >>>> I think we need more data from the community >>>> - Who's build is failing on ceph with *aclocal: too many loops?* >>>> - Who is building successfully ? >>>> - Who can build only intermittently? >>>> >>>> >>>> >>>> Info to collect for failed builds: >>> - repo sync timestamp >>>> - build command used? >>>> - Was it a new workspace, a cleaned workspace, or a previously used >>>> workspace? >>> - $MY_WORKSPACE/CONTEXT >>>> - $MY_WORKSPACE/build-std.log >>>> - $MY_WORKSPACE/std/results/*/ceph-*/*.log >>>> >>>> For successful builds, same info. Rather than full build logs, I can >>>> settle for: >>>> - grep '\(Success building\|iteration\|building ceph\)' >>>> $MY_WORKSPACE/build-std.log >>>> - grep compute_resources: build-std.log >>>> >>>> >>>> >>>> >>>> >>>> On 18-09-27 02:21 PM, Saul Wold wrote: >>>>> On 09/26/2018 09:16 AM, Scott Little wrote: >>>>>> aclocal 'too many loops' has been popping up sporadically for a >>>>>> week or two now.  Possibly 7.5 related. >>>>>> >>>>>> I suspect that there is a build order and/or race condition >>>>>> element to this.   It often goes away if you just run build-pkgs a >>>>>> second time. >>>>>> >>>>> I am seeing this failure also, but it does not go away after a >>>>> second rebuild.  I have the lastest stx-root (build-tools) with the >>>>> recent patches. >>>>> >>>>> Is this directly related to the fuzz issue or is there something >>>>> else we need to address in CEPH itself. >>>>> >>>>> This is blocking my local build. >>>>> >>>>> Sau! >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> > From yong.hu at intel.com Sat Sep 29 00:24:02 2018 From: yong.hu at intel.com (Hu, Yong) Date: Sat, 29 Sep 2018 00:24:02 +0000 Subject: [Starlingx-discuss] [multi-os] replace "/etc" in config files by a variable "sysconfdir" Message-ID: As a part of initiatives, I would like to suggest to replace “/etc”, which is hardcoded in some StarlingX config files, by a variable something like “sysconfdir”, which would be “instantiated” a bit later upon the OS type (CentOS, ClearLinux or Ubuntu). Taking “stx-nfv/nfv/nfv-vim/nfv_vim/config.ini” as an example, “/etc” is coded in this “config.ini” directly to refer other config files: config_file=/etc/nfv/nfv_plugins/alarm_handlers/config.ini config_file=/etc/nfv/nfv_plugins/nfvi_plugins/config.ini My recommendation is to use a variable “sysconfdir” as instead, and to “define” this variable on later stage, like in “nfv.spec” for CentOS, in which “sysconfdir” is “/etc”. The benefit I see here is in other OSs, such as Clear Linux in which we can set different value, for example, “/usr/local/etc” for this variable “sysconfdir”. Should you have any questions or feedback, please let me know. If I don’t see objections with this kind of changes, I will make some patches accordingly afterward. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Fri Sep 28 23:41:47 2018 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Fri, 28 Sep 2018 23:41:47 +0000 Subject: [Starlingx-discuss] [ Test ] stx.2018.10 test plan In-Reply-To: References: <4F6AACE4B0F173488D033B02A8BB5B7E716E81DD@fmsmsx104.amr.corp.intel.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E716F8D3B@FMSMSX108.amr.corp.intel.com> Hi Kai I'm still finishing with the details. I will upload the document early next week. Regards Ada > -----Original Message----- > From: kai [mailto:li.kai at 99cloud.net] > Sent: Thursday, September 27, 2018 9:43 PM > To: Cabrales, Ada ; starlingx- > discuss at lists.starlingx.io > Cc: Hu, Wei W ; Sun, Xianghui > ; wuyx36 at chinaunicom.cn; Xie, Cindy > ; Wang, Shane ; Ding, Jian- > feng ; Zeng, Hongli ; > Jin, Yuntong ; 'lvhz7' ; > Zhao, Forrest ; 'yanky5' > ; '陈丹' ; '王友祥' > ; huang.shuquan at 99cloud.net; Liang, > Maggie ; 'jeffrey.zhang' > ; '龚永生' ; > 'jing.liuqing' ; '99cloud' > > Subject: 答复: [Starlingx-discuss] [ Test ] stx.2018.10 test plan > > Hi, Ada, where can we find the detail test steps for each test case? > > -----邮件原件----- > 发件人: Cabrales, Ada > 发送时间: 2018年9月22日 7:54 > 收件人: starlingx-discuss at lists.starlingx.io > 主题: [Starlingx-discuss] [ Test ] stx.2018.10 test plan > > Hello, > > I'm posting the test plan proposed for the October Release in the wiki [0]. > We have 238 tests so far, mostly focus on the stx services. As we mentioned > before, the tests will be run manually by our team for this release. The > expectation is to increase the number of automated tests along time. > > We are considering to cover the four configurations (Simplex, Duplex, > Multinode local storage, Multinode external storage) both on bare metal and > virtual. However, we are experiencing setup problems with multinode bare > metal and simplex. We are digging into it. We'll have more information next > week. > > Please take a look at it and let us know what else must be included. > > Thanks > Ada > > [0] https://wiki.openstack.org/wiki/StarlingX/stx.2018.10_Testplan > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From juan.carlos.alonso at intel.com Sat Sep 29 02:17:25 2018 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Sat, 29 Sep 2018 02:17:25 +0000 Subject: [Starlingx-discuss] There are not network interfaces in controller-1 Message-ID: <8557B550001AFB46A43A0CCC314BF85144243ABB@FMSMSX108.amr.corp.intel.com> Hi, Was there a change on how to create or provision network interfaces for controllers? When Controller-1 was installed and try to provision it, there is not output for "system host-if-list -a controller-1", for controller-0 there is. So, if controller-1 is not full provisioned it cannot 'unlock' and cannot be used. I followed steps in Wiki for Virtual multinode controller storage. https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Controller_Storage Execute against ISO: stx-2018-09-28-148.iso Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Sat Sep 29 02:26:27 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Sat, 29 Sep 2018 02:26:27 +0000 Subject: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB28C91F@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C76553830F7@SHSMSX101.ccr.corp.intel.com> <33b41902-d812-709a-c77a-dc902b5715d7@windriver.com> <9700A18779F35F49AF027300A49E7C76553834D4@SHSMSX101.ccr.corp.intel.com> <9c43419b-b546-a797-b2ab-8ffc349b5da6@windriver.com> <2588653EBDFFA34B982FAF00F1B4844EBB28C91F@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C7655383752@SHSMSX101.ccr.corp.intel.com> Hi all, Two story are created to track rpm upgrade and fuzzy patch elimination. [Feature] Upgrade rpm to 4.14.0 version [Enhancement] De-fuzz fuzzy patch Best Regards Shuicheng From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Saturday, September 29, 2018 7:39 AM To: Little, Scott ; Lin, Shuicheng ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm Agree with Scott Brent From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, September 28, 2018 9:54 AM To: Lin, Shuicheng >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm Certainly that will prevent creation of .orig files, so the risk of build failures in the packaging phase will be eliminated. However I have strong distrust of fuzzy patches. It suggests to me that folks are upgrading packages without doing the due diligence to make sure the patches are still needed, and are being applied correctly. Also I have seen twice in my career, a fuzzy patch get improperly applied to a neighboring bit of code that happened to look similar to the proper target. It's rare, but it can occur. On the plus side, moving to 4.14 would give us a consistent version of rpm throughout the build. That I like. I'm thinking we should do it, but we need a no fuzzy patches policy, and perhaps we create an audit that looks for fuzzy patches. Scott On 18-09-28 02:27 AM, Lin, Shuicheng wrote: Hi Scott, What do you think about upgrade rpm in mirror lst to 4.14 version? So we could get rid of the fuzz issue. To do this upgrade, rpm will be moved from centos repo lst to tarball lst. Here is the release notes of rpm-4.13 to fix this fuzz issue: Enable –no-backup-if-mismatch by default in %patch macro (RhBug:884755) Best Regards Shuicheng From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, September 27, 2018 11:24 PM To: Lin, Shuicheng ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] de-fuzz centos7.5 upgraded src rpm Yes, I've seen some upstream packages that ship from CentOS or EL7 with fuzzy patches. Can't do much about that. My list might include packages where the only fuzzy patches are those coming from CentOS. We'll have to sort through them by hand I think. Scott On 18-09-27 10:24 AM, Lin, Shuicheng wrote: Hi all, Here is the patch list to de-fuzz the patches in CentOS7.5 upgrade task. https://review.openstack.org/#/q/topic:patch_fuzz+(status:open+OR+status:merged) I notice there are some other src rpms also have the fuzzy issue. Will handle them later. Also, I find some SRC RPM itself has the fuzzy issue, such as openldap/rsync/netpbm/openssh etc. So we cannot eliminate all fuzzy issue just by rebase ourselves patches. Best Regards Shuicheng From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, September 27, 2018 5:08 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build I have also been investigating another intermittent build error affecting initscripts. https://bugs.launchpad.net/starlingx/+bug/1794611 So any given package might be built by rpm-4.11.3, or by rpm-4.14.0. It's a race with many inputs. Ideally it shouldn't matter, but it does. build-pkgs --serial might reduce the odds, but likely won't solve it entirely. In this case it is a new option that rpm passes to the patch command, --no-backup-if-mismatch, first introduced by rpm-4.13. This option has the effect of suppressing the creation of '.orig' files. Creation of .orig files are a consequence of applying patches that are not clean. Unclean patches are ones that require 'fuzzing', i.e. treat the patch line numbers as approximate, rather than a strict requirement, just so long as the before/after context seems to be correct. Prior to StarlingX, my policy for rebasing patches was that no fuzz is tolerated in our patches. All the work to upgrade to 7.5 has created a lot of fuzzy patches. audit-2.8.1-3.el7.tis.2 bash-4.2.46-30.el7.tis.3 dhcp-4.2.5-68.el7.centos.1.tis.8 dnsmasq-2.76-5.el7.tis.6 drbd-8.4.3-0.tis.6 facter-2.4.4-4.el7.tis.4 haproxy-1.5.18-7.el7.tis.7 initscripts-9.49.41-1.el7.tis.16 iptables-1.4.21-24.1.el7_5.tis.3 kubernetes-1.10.0-1.tis.1 libevent-2.0.21-4.el7.tis.2 lighttpd-1.4.50-1.el7.tis.6 logrotate-3.8.6-15.el7.tis.3 netpbm-10.79.00-7.el7.tis.2 net-snmp-5.7.2-33.el7_5.2.tis.10 net-tools-2.0-0.22.20131004git.el7.tis.2 nfs-utils-1.3.0-0.54.el7.tis.4 nss-pam-ldapd-0.8.13-16.el7.tis.4 ntp-4.2.6p5-28.el7.centos.tis.3 openldap-2.4.44-15.el7_5.tis.8 openssh-7.4p1-16.el7_4.tis.9 pam-1.1.8-22.el7.tis.4 puppet-4.8.2-1.el7.tis.2 puppet-ceph-2.4.1-1.el7.tis.4 puppet-horizon-11.5.0-1.el7.tis.1 python-2.7.5-69.el7_5.tis.3 python-keyring-5.7.1-1.tis.2 python-wsme-0.9.2-1.el7.tis.3 resource-agents-3.9.5-124.el7.tis.12 rsync-3.1.2-4.el7.tis.2 shadow-utils-4.1.5.1-24.el7.tis.4 sudo-1.8.19p2-14.el7_5.tis.3 watchdog-5.13-11.el7.tis.2 So any of these packages might or might not produce unwanted .orig files. The .orig files might or might not be packaged, or break packaging. So there are a number of threads to pull at here. 1) Are fuzzy patches tolerated. I vote no. Sooner or later a fuzzy patch will be mis-applied and cause us problems. 2) Can we force rpmbuild within mock to use a consistent policy with respect to creation of orig files? 3) Can we pre-build rpm, such that all packages build against the same rpm version? 4) Are we patching any other low level build tools that have similar issues? Possibly explaining ceph? TBD On 18-09-26 12:16 PM, Scott Little wrote: aclocal 'too many loops' has been popping up sporadically for a week or two now. Possibly 7.5 related. I suspect that there is a build order and/or race condition element to this. It often goes away if you just run build-pkgs a second time. The second possible element is that build-pkgs is using flags that preserve the mock environment between packages. The goal was to avoid reinstalling required packages that are often common across the packages we build. It was a build time speedup that has been in use for 2-3 years now without incident. Google shows that other folks have hit 'aclocal too many loops' as well, and there are suggestions that it might be fixed in a recent update to automake. Scanning the changelog for the latest and greatest from gnu.org doesn't show any obvious fixes addressing this issue. Scott On 18-09-26 11:32 AM, Cordoba Malibran, Erich wrote: BUILDSTDERR: aclocal: error: too many loops BUILDSTDERR: aclocal: Please contact . BUILDSTDERR: at /usr/share/automake-1.13/Automake/Channels.pm line 662. BUILDSTDERR: Automake::Channels::msg('automake', '', 'too many loops') called at /usr/share/automake-1.13/Automake/ChannelDefs.pm line 212 BUILDSTDERR: Automake::ChannelDefs::prog_error('too many loops') called at /usr/bin/aclocal line 1187 BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) BUILDSTDERR: Macro expanded in comment on line 214: %global _libexecdir %{_exec_prefix}/lib BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.Sj0E7c (%build) _______________________________________________ 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 austin.sun at intel.com Sat Sep 29 08:41:16 2018 From: austin.sun at intel.com (Sun, Austin) Date: Sat, 29 Sep 2018 08:41:16 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build----aclocal: too many loops Message-ID: Hi Saul , Scott and Erich: I met same issue in my local env, I did some study aclocal script and some test. According your analysis , autoconf-archive-2017.03.21-1.el7.noarch.rpm was added , which included a lot of system m4 files used by aclocal, according [0] and [1], '--install' option will cp system macros (.m4) to local m4 folder , From error log: BUILDSTDERR: aclocal: installing /usr/share/aclocal/ax_require_defined.m4 to m4/ax_require_defined.m4 BUILDSTDERR: aclocal: installing 'm4/ax_require_defined.m4' from '/usr/share/aclocal/ax_require_defined.m4' BUILDSTDERR: aclocal: running: cp /usr/share/aclocal/ax_require_defined.m4 m4/ax_require_defined.m4 BUILDSTDERR: aclocal: running aclocal anew, because some files were installed locally BUILDSTDERR: aclocal: error: too many loops ax_require_defined.m4 cause this issue, If copied ax_require_defined.m4 to code base stx/git/ceph/m4/, ceph can be built successfully . since cannot upload change to starlingx-staging , please use [3] ax_require_defined.m4 file which is same as file in autoconf-archive-2017.03.21-1.el7.noarch.rpm package - About why ax_require_defined.m4 is a must for ceph build: ax_cxx_compile_stdcxx_11.m4 is upgraded from local serial 4 to system serial 18 including in autoconf-archive rpm , which is using AX_REQUIRE_DEFINED defined in ax_require_defined.m4 have tried force upgrade local m4/ax_cxx_compile_stdcxx_11.m4 to serial 19 , it can solve this issue too. -[0] https://www.gnu.org/software/automake/manual/html_node/Serials.html#Serials -[1] https://www.gnu.org/software/automake/manual/html_node/aclocal-Invocation.html#aclocal-Invocation -[2] http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=blob_plain;f=m4/ax_require_defined.m4 Thanks. BR Austin Sun. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Saturday, September 29, 2018 8:20 AM To: Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build On 09/28/2018 01:39 PM, Scott Little wrote: > Ok, we've seen 3 ceph failures in our last 6 builds. > > The common factor:  tpm2-tools builds on 'b0' before ceph builds. > > Our theory.  The buildRequires of tpm2-tools causes autoconf-archive > to be installed... which installs a bunch of .m4 files in > /usr/share/aclocal ... which causes ceph grief when it calls aclocal. > > I don't really know automake or aclocal all that well.  I'm assuming > /usr/share/aclocal is acting something like a cache, but it's a cache > whos contents are incompatible with ceph. > > Do we have any autotools / aclocal / m4 experts in the house? > > Possible fixes: > - ceph: can we tell it to not use the aclocal cache... explicitly (a > flag to aclocal?)  ... or implicitly (update ceph's m4 files so they > look 'newer' than the cache)? Not sure about that, I would have to dig deeper into aclocal, it's been a while since I dug into that. > - tpm2-tools: Can we remove the dependence on autoconf-archive? No > other package we build seems to need it. > A quick scan show that the autoconf-archive was put in there for travis support, and goes away this past March upstream when they coverted to using a container for travis. If we could use a newer version of tpm2 that might solve this. Maybe Erich's solution can work Sau! > Scott > > > > On 18-09-27 04:45 PM, Saul Wold wrote: >> >> And of course it worked the third time! >> >> So, I lost the good logs. >> >> Sau! >> >> >> On 09/27/2018 12:56 PM, Scott Little wrote: >>> On 18-09-27 03:53 PM, Scott Little wrote: >>>> Our latest build, based on code synced at 2018-09-27T15:28:00  UTC, >>>> built successfully. >>>> >>>> It took three attempts to get ceph built.  The first two passes >>>> aborted quickly due to missing packages.  The final pass did not >>>> exhibit the 'aclocal: too many loops'**issue. >>>> >>>> The only build I have that exhibited the too many loops error was a >>>> snapshot on 2018-09-20T15:50:40 UTC >>>> >>>> I do have a designer with an older snapshot that seems to hit it >>>> regularly, so I'll work with him and see if we can learn more. >>>> >>>> I think we need more data from the community >>>> - Who's build is failing on ceph with *aclocal: too many loops?* >>>> - Who is building successfully ? >>>> - Who can build only intermittently? >>>> >>>> >>>> >>>> Info to collect for failed builds: >>> - repo sync timestamp >>>> - build command used? >>>> - Was it a new workspace, a cleaned workspace, or a previously used >>>> workspace? >>> - $MY_WORKSPACE/CONTEXT >>>> - $MY_WORKSPACE/build-std.log >>>> - $MY_WORKSPACE/std/results/*/ceph-*/*.log >>>> >>>> For successful builds, same info. Rather than full build logs, I >>>> can settle for: >>>> - grep '\(Success building\|iteration\|building ceph\)' >>>> $MY_WORKSPACE/build-std.log >>>> - grep compute_resources: build-std.log >>>> >>>> >>>> >>>> >>>> >>>> On 18-09-27 02:21 PM, Saul Wold wrote: >>>>> On 09/26/2018 09:16 AM, Scott Little wrote: >>>>>> aclocal 'too many loops' has been popping up sporadically for a >>>>>> week or two now.  Possibly 7.5 related. >>>>>> >>>>>> I suspect that there is a build order and/or race condition >>>>>> element to this.   It often goes away if you just run build-pkgs >>>>>> a second time. >>>>>> >>>>> I am seeing this failure also, but it does not go away after a >>>>> second rebuild.  I have the lastest stx-root (build-tools) with >>>>> the recent patches. >>>>> >>>>> Is this directly related to the fuzz issue or is there something >>>>> else we need to address in CEPH itself. >>>>> >>>>> This is blocking my local build. >>>>> >>>>> Sau! >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>>> s >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Sat Sep 29 10:02:54 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Sat, 29 Sep 2018 10:02:54 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build----aclocal: too many loops In-Reply-To: References: Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B38B7FE@SHSMSX104.ccr.corp.intel.com> Austin, Thanks for the finding - can we generate pull-requests for ax_require_define.m4 against StarlingX-staging? Thx. - cindy -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Saturday, September 29, 2018 4:41 PM To: Saul Wold ; Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build----aclocal: too many loops Hi Saul , Scott and Erich: I met same issue in my local env, I did some study aclocal script and some test. According your analysis , autoconf-archive-2017.03.21-1.el7.noarch.rpm was added , which included a lot of system m4 files used by aclocal, according [0] and [1], '--install' option will cp system macros (.m4) to local m4 folder , From error log: BUILDSTDERR: aclocal: installing /usr/share/aclocal/ax_require_defined.m4 to m4/ax_require_defined.m4 BUILDSTDERR: aclocal: installing 'm4/ax_require_defined.m4' from '/usr/share/aclocal/ax_require_defined.m4' BUILDSTDERR: aclocal: running: cp /usr/share/aclocal/ax_require_defined.m4 m4/ax_require_defined.m4 BUILDSTDERR: aclocal: running aclocal anew, because some files were installed locally BUILDSTDERR: aclocal: error: too many loops ax_require_defined.m4 cause this issue, If copied ax_require_defined.m4 to code base stx/git/ceph/m4/, ceph can be built successfully . since cannot upload change to starlingx-staging , please use [3] ax_require_defined.m4 file which is same as file in autoconf-archive-2017.03.21-1.el7.noarch.rpm package - About why ax_require_defined.m4 is a must for ceph build: ax_cxx_compile_stdcxx_11.m4 is upgraded from local serial 4 to system serial 18 including in autoconf-archive rpm , which is using AX_REQUIRE_DEFINED defined in ax_require_defined.m4 have tried force upgrade local m4/ax_cxx_compile_stdcxx_11.m4 to serial 19 , it can solve this issue too. -[0] https://www.gnu.org/software/automake/manual/html_node/Serials.html#Serials -[1] https://www.gnu.org/software/automake/manual/html_node/aclocal-Invocation.html#aclocal-Invocation -[2] http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=blob_plain;f=m4/ax_require_defined.m4 Thanks. BR Austin Sun. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Saturday, September 29, 2018 8:20 AM To: Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build On 09/28/2018 01:39 PM, Scott Little wrote: > Ok, we've seen 3 ceph failures in our last 6 builds. > > The common factor:  tpm2-tools builds on 'b0' before ceph builds. > > Our theory.  The buildRequires of tpm2-tools causes autoconf-archive > to be installed... which installs a bunch of .m4 files in > /usr/share/aclocal ... which causes ceph grief when it calls aclocal. > > I don't really know automake or aclocal all that well.  I'm assuming > /usr/share/aclocal is acting something like a cache, but it's a cache > whos contents are incompatible with ceph. > > Do we have any autotools / aclocal / m4 experts in the house? > > Possible fixes: > - ceph: can we tell it to not use the aclocal cache... explicitly (a > flag to aclocal?)  ... or implicitly (update ceph's m4 files so they > look 'newer' than the cache)? Not sure about that, I would have to dig deeper into aclocal, it's been a while since I dug into that. > - tpm2-tools: Can we remove the dependence on autoconf-archive? No > other package we build seems to need it. > A quick scan show that the autoconf-archive was put in there for travis support, and goes away this past March upstream when they coverted to using a container for travis. If we could use a newer version of tpm2 that might solve this. Maybe Erich's solution can work Sau! > Scott > > > > On 18-09-27 04:45 PM, Saul Wold wrote: >> >> And of course it worked the third time! >> >> So, I lost the good logs. >> >> Sau! >> >> >> On 09/27/2018 12:56 PM, Scott Little wrote: >>> On 18-09-27 03:53 PM, Scott Little wrote: >>>> Our latest build, based on code synced at 2018-09-27T15:28:00  UTC, >>>> built successfully. >>>> >>>> It took three attempts to get ceph built.  The first two passes >>>> aborted quickly due to missing packages.  The final pass did not >>>> exhibit the 'aclocal: too many loops'**issue. >>>> >>>> The only build I have that exhibited the too many loops error was a >>>> snapshot on 2018-09-20T15:50:40 UTC >>>> >>>> I do have a designer with an older snapshot that seems to hit it >>>> regularly, so I'll work with him and see if we can learn more. >>>> >>>> I think we need more data from the community >>>> - Who's build is failing on ceph with *aclocal: too many loops?* >>>> - Who is building successfully ? >>>> - Who can build only intermittently? >>>> >>>> >>>> >>>> Info to collect for failed builds: >>> - repo sync timestamp >>>> - build command used? >>>> - Was it a new workspace, a cleaned workspace, or a previously used >>>> workspace? >>> - $MY_WORKSPACE/CONTEXT >>>> - $MY_WORKSPACE/build-std.log >>>> - $MY_WORKSPACE/std/results/*/ceph-*/*.log >>>> >>>> For successful builds, same info. Rather than full build logs, I >>>> can settle for: >>>> - grep '\(Success building\|iteration\|building ceph\)' >>>> $MY_WORKSPACE/build-std.log >>>> - grep compute_resources: build-std.log >>>> >>>> >>>> >>>> >>>> >>>> On 18-09-27 02:21 PM, Saul Wold wrote: >>>>> On 09/26/2018 09:16 AM, Scott Little wrote: >>>>>> aclocal 'too many loops' has been popping up sporadically for a >>>>>> week or two now.  Possibly 7.5 related. >>>>>> >>>>>> I suspect that there is a build order and/or race condition >>>>>> element to this.   It often goes away if you just run build-pkgs >>>>>> a second time. >>>>>> >>>>> I am seeing this failure also, but it does not go away after a >>>>> second rebuild.  I have the lastest stx-root (build-tools) with >>>>> the recent patches. >>>>> >>>>> Is this directly related to the fuzz issue or is there something >>>>> else we need to address in CEPH itself. >>>>> >>>>> This is blocking my local build. >>>>> >>>>> Sau! >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>>> s >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Sat Sep 29 13:47:29 2018 From: austin.sun at intel.com (Sun, Austin) Date: Sat, 29 Sep 2018 13:47:29 +0000 Subject: [Starlingx-discuss] build-pkgs cannot complete std build----aclocal: too many loops In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B38B7FE@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F2B38B7FE@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Cindy and All: I have generated two PR, one is for master and another is for r/2018.10. please help check if the PR process is correct . -[0] https://github.com/starlingx-staging/stx-ceph/pull/2 -[1] https://github.com/starlingx-staging/stx-ceph/pull/3 Thanks. BR Austin Sun. -----Original Message----- From: Xie, Cindy Sent: Saturday, September 29, 2018 6:03 PM To: Sun, Austin ; Saul Wold ; Scott Little ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] build-pkgs cannot complete std build----aclocal: too many loops Austin, Thanks for the finding - can we generate pull-requests for ax_require_define.m4 against StarlingX-staging? Thx. - cindy -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Saturday, September 29, 2018 4:41 PM To: Saul Wold ; Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build----aclocal: too many loops Hi Saul , Scott and Erich: I met same issue in my local env, I did some study aclocal script and some test. According your analysis , autoconf-archive-2017.03.21-1.el7.noarch.rpm was added , which included a lot of system m4 files used by aclocal, according [0] and [1], '--install' option will cp system macros (.m4) to local m4 folder , From error log: BUILDSTDERR: aclocal: installing /usr/share/aclocal/ax_require_defined.m4 to m4/ax_require_defined.m4 BUILDSTDERR: aclocal: installing 'm4/ax_require_defined.m4' from '/usr/share/aclocal/ax_require_defined.m4' BUILDSTDERR: aclocal: running: cp /usr/share/aclocal/ax_require_defined.m4 m4/ax_require_defined.m4 BUILDSTDERR: aclocal: running aclocal anew, because some files were installed locally BUILDSTDERR: aclocal: error: too many loops ax_require_defined.m4 cause this issue, If copied ax_require_defined.m4 to code base stx/git/ceph/m4/, ceph can be built successfully . since cannot upload change to starlingx-staging , please use [3] ax_require_defined.m4 file which is same as file in autoconf-archive-2017.03.21-1.el7.noarch.rpm package - About why ax_require_defined.m4 is a must for ceph build: ax_cxx_compile_stdcxx_11.m4 is upgraded from local serial 4 to system serial 18 including in autoconf-archive rpm , which is using AX_REQUIRE_DEFINED defined in ax_require_defined.m4 have tried force upgrade local m4/ax_cxx_compile_stdcxx_11.m4 to serial 19 , it can solve this issue too. -[0] https://www.gnu.org/software/automake/manual/html_node/Serials.html#Serials -[1] https://www.gnu.org/software/automake/manual/html_node/aclocal-Invocation.html#aclocal-Invocation -[2] http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=blob_plain;f=m4/ax_require_defined.m4 Thanks. BR Austin Sun. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Saturday, September 29, 2018 8:20 AM To: Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs cannot complete std build On 09/28/2018 01:39 PM, Scott Little wrote: > Ok, we've seen 3 ceph failures in our last 6 builds. > > The common factor:  tpm2-tools builds on 'b0' before ceph builds. > > Our theory.  The buildRequires of tpm2-tools causes autoconf-archive > to be installed... which installs a bunch of .m4 files in > /usr/share/aclocal ... which causes ceph grief when it calls aclocal. > > I don't really know automake or aclocal all that well.  I'm assuming > /usr/share/aclocal is acting something like a cache, but it's a cache > whos contents are incompatible with ceph. > > Do we have any autotools / aclocal / m4 experts in the house? > > Possible fixes: > - ceph: can we tell it to not use the aclocal cache... explicitly (a > flag to aclocal?)  ... or implicitly (update ceph's m4 files so they > look 'newer' than the cache)? Not sure about that, I would have to dig deeper into aclocal, it's been a while since I dug into that. > - tpm2-tools: Can we remove the dependence on autoconf-archive? No > other package we build seems to need it. > A quick scan show that the autoconf-archive was put in there for travis support, and goes away this past March upstream when they coverted to using a container for travis. If we could use a newer version of tpm2 that might solve this. Maybe Erich's solution can work Sau! > Scott > > > > On 18-09-27 04:45 PM, Saul Wold wrote: >> >> And of course it worked the third time! >> >> So, I lost the good logs. >> >> Sau! >> >> >> On 09/27/2018 12:56 PM, Scott Little wrote: >>> On 18-09-27 03:53 PM, Scott Little wrote: >>>> Our latest build, based on code synced at 2018-09-27T15:28:00  UTC, >>>> built successfully. >>>> >>>> It took three attempts to get ceph built.  The first two passes >>>> aborted quickly due to missing packages.  The final pass did not >>>> exhibit the 'aclocal: too many loops'**issue. >>>> >>>> The only build I have that exhibited the too many loops error was a >>>> snapshot on 2018-09-20T15:50:40 UTC >>>> >>>> I do have a designer with an older snapshot that seems to hit it >>>> regularly, so I'll work with him and see if we can learn more. >>>> >>>> I think we need more data from the community >>>> - Who's build is failing on ceph with *aclocal: too many loops?* >>>> - Who is building successfully ? >>>> - Who can build only intermittently? >>>> >>>> >>>> >>>> Info to collect for failed builds: >>> - repo sync timestamp >>>> - build command used? >>>> - Was it a new workspace, a cleaned workspace, or a previously used >>>> workspace? >>> - $MY_WORKSPACE/CONTEXT >>>> - $MY_WORKSPACE/build-std.log >>>> - $MY_WORKSPACE/std/results/*/ceph-*/*.log >>>> >>>> For successful builds, same info. Rather than full build logs, I >>>> can settle for: >>>> - grep '\(Success building\|iteration\|building ceph\)' >>>> $MY_WORKSPACE/build-std.log >>>> - grep compute_resources: build-std.log >>>> >>>> >>>> >>>> >>>> >>>> On 18-09-27 02:21 PM, Saul Wold wrote: >>>>> On 09/26/2018 09:16 AM, Scott Little wrote: >>>>>> aclocal 'too many loops' has been popping up sporadically for a >>>>>> week or two now.  Possibly 7.5 related. >>>>>> >>>>>> I suspect that there is a build order and/or race condition >>>>>> element to this.   It often goes away if you just run build-pkgs >>>>>> a second time. >>>>>> >>>>> I am seeing this failure also, but it does not go away after a >>>>> second rebuild.  I have the lastest stx-root (build-tools) with >>>>> the recent patches. >>>>> >>>>> Is this directly related to the fuzz issue or is there something >>>>> else we need to address in CEPH itself. >>>>> >>>>> This is blocking my local build. >>>>> >>>>> Sau! >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>>> s >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Sat Sep 29 14:38:00 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Sat, 29 Sep 2018 14:38:00 +0000 Subject: [Starlingx-discuss] Containerizing the StarlingX Infrastructure Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB28D2DE@ALA-MBD.corp.ad.wrs.com> Folks, Setting up this call to give the community an overview of the StarlingX infrastructure containerization initiative. Hope you can join. Thanks, Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1712 bytes Desc: not available URL: From Brent.Rowsell at windriver.com Sat Sep 29 14:40:23 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Sat, 29 Sep 2018 14:40:23 +0000 Subject: [Starlingx-discuss] There are not network interfaces in controller-1 In-Reply-To: <8557B550001AFB46A43A0CCC314BF85144243ABB@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85144243ABB@FMSMSX108.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB28D30B@ALA-MBD.corp.ad.wrs.com> Did controller-1 go online ? Brent From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Friday, September 28, 2018 10:17 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] There are not network interfaces in controller-1 Hi, Was there a change on how to create or provision network interfaces for controllers? When Controller-1 was installed and try to provision it, there is not output for "system host-if-list -a controller-1", for controller-0 there is. So, if controller-1 is not full provisioned it cannot 'unlock' and cannot be used. I followed steps in Wiki for Virtual multinode controller storage. https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Controller_Storage Execute against ISO: stx-2018-09-28-148.iso Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Sun Sep 30 15:06:42 2018 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Sun, 30 Sep 2018 15:06:42 +0000 Subject: [Starlingx-discuss] Analysis of patch e547a7e & ebd41fd for StartlingX upstreaming References: Message-ID: Hi Matt, For patches e547a7e and ebd41fd, I think it's a bug in Neutron upstream and will submit the patch to fix it in the next step. This bug is caused by passing the wrong parameter after create or update router. You can find the analysis report within attached file. Could you please help review and comment! Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Analysis Report for e547a7e&ebd41fd .docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 417196 bytes Desc: Analysis Report for e547a7e&ebd41fd .docx URL: