[Starlingx-discuss] About EB verification for openstack train upgrade
Xie, Cindy
cindy.xie at intel.com
Wed Oct 30 14:48:52 UTC 2019
+ mailing list in case anybody can help on debug the issue.
From: Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras at intel.com>
Sent: Wednesday, October 30, 2019 7:45 PM
To: Liu, ZhipengS <zhipengs.liu at intel.com>; 朱博祥 <zhu.boxiang at 99cloud.net>
Cc: Alonso, Juan Carlos <juan.carlos.alonso at intel.com>; Hu, Yong <yong.hu at intel.com>; Cabrales, Ada <ada.cabrales at intel.com>; Xie, Cindy <cindy.xie at intel.com>; Jones, Bruce E <bruce.e.jones at intel.com>; Martinez Monroy, Elio <elio.martinez.monroy at intel.com>
Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade
Hi Zhipeng,
The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED.
For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad.
Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/
Please, let us know if you need additional details.
Thanks & Regards,
Cristopher Lemus
From: "Liu, ZhipengS" <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>
Date: Tuesday, October 29, 2019 at 7:23 PM
To: "Lemus Contreras, Cristopher J" <cristopher.j.lemus.contreras at intel.com<mailto:cristopher.j.lemus.contreras at intel.com>>, 朱博祥 <zhu.boxiang at 99cloud.net<mailto:zhu.boxiang at 99cloud.net>>
Cc: "Alonso, Juan Carlos" <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>, "Hu, Yong" <yong.hu at intel.com<mailto:yong.hu at intel.com>>, "Cabrales, Ada" <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>, "Xie, Cindy" <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>, "Jones, Bruce E" <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>, "Martinez Monroy, Elio" <elio.martinez.monroy at intel.com<mailto:elio.martinez.monroy at intel.com>>
Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
Hi Cristopher Lemus,
Yes, exactly! Do we have a test result with my latest EB now?
Thank Boxiang for clarification!
I have included related change in latest EB 308.
Thanks!
Zhipeng
From: Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras at intel.com<mailto:cristopher.j.lemus.contreras at intel.com>>
Sent: 2019年10月30日 4:16
To: 朱博祥 <zhu.boxiang at 99cloud.net<mailto:zhu.boxiang at 99cloud.net>>; Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>
Cc: Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>; Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>; Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Martinez Monroy, Elio <elio.martinez.monroy at intel.com<mailto:elio.martinez.monroy at intel.com>>
Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade
Hi All,
I think that we are facing the exact same issue that Boxiang mentions, it’s a failure for Standard external storage (2+2+2).
We are not able to launch instances on Standard with External Storage, here’s a sample output: http://paste.openstack.org/show/785641/, the error matches the bug: https://bugs.launchpad.net/starlingx/+bug/1837241, which was reverted on the review that Boxiang listed.
The rest of the configurations are not affected, this is specific to external storage.
Thanks ,
Cristopher Lemus
From: 朱博祥 <zhu.boxiang at 99cloud.net<mailto:zhu.boxiang at 99cloud.net>>
Date: Tuesday, October 29, 2019 at 6:15 AM
To: "Liu, ZhipengS" <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>
Cc: "Alonso, Juan Carlos" <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>, "Hu, Yong" <yong.hu at intel.com<mailto:yong.hu at intel.com>>, "Cabrales, Ada" <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>, "Xie, Cindy" <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>, "Jones, Bruce E" <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>, "Lemus Contreras, Cristopher J" <cristopher.j.lemus.contreras at intel.com<mailto:cristopher.j.lemus.contreras at intel.com>>, "Martinez Monroy, Elio" <elio.martinez.monroy at intel.com<mailto:elio.martinez.monroy at intel.com>>
Subject: Re:RE: [Starlingx-discuss] About EB verification for openstack train upgrade
Hi Zhipeng,
Yeah, now when we use the openstack train, we should set force_raw_images to True when we use rbd as images_types in nova.conf. Otherwise the nova-compute service will fail to start.
The patch[0] was meant to do that before but it caused the sanity test failure and we didn't find the root cause.
[0] https://review.opendev.org/#/c/661512/
Thanks,
Boxiang
From: "Liu, ZhipengS" <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>
Date: 2019-10-29 10:54:13
To: "Alonso, Juan Carlos" <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>,"Hu, Yong" <yong.hu at intel.com<mailto:yong.hu at intel.com>>,"Cabrales, Ada" <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>,"朱博祥" <zhu.boxiang at 99cloud.net<mailto:zhu.boxiang at 99cloud.net>>
Cc: "Xie, Cindy" <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>,"Jones, Bruce E" <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>,"Lemus Contreras, Cristopher J" <cristopher.j.lemus.contreras at intel.com<mailto:cristopher.j.lemus.contreras at intel.com>>,"Martinez Monroy, Elio" <elio.martinez.monroy at intel.com<mailto:elio.martinez.monroy at intel.com>>
Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>+baoxiang
>
>Hi JC,
>
>Thanks for your quick update!
>I have found the root cause from your logs.
>
>{"log":"2019-10-25 15:36:06.371 235059 ERROR oslo_service.service [-] Error starting thread.: InvalidConfiguration: '[DEFAULT]/force_raw_images = False' is not allowed with '[libvirt]/images_type = rbd'. Please check the two configs and if you really do want to use rbd as images_type, set force_raw_images to True.\n","stream":"stdout","time":"2019-10-25T15:36:06.372419534Z"}
>
>This is related to an old LP
>https://bugs.launchpad.net/starlingx/+bug/1837241
>Last time, I revert the patch provided by Boxiang due to we were using staging nova version with some of Starlingx patches.
>https://review.opendev.org/#/c/661512/
>Now, we used upstream Nova, we need set force_raw_images = True again.
>https://review.opendev.org/#/c/672287/
>
>@Boxiang, any comment or additional change needed?
>@JC, I will provide EB to you later for this issue.
>
>Thanks!
>Zhipeng
>-----Original Message-----
>From: Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>
>Sent: 2019年10月29日 5:33
>To: Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>; Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras at intel.com<mailto:cristopher.j.lemus.contreras at intel.com>>; Martinez Monroy, Elio <elio.martinez.monroy at intel.com<mailto:elio.martinez.monroy at intel.com>>
>Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>Standard External Storage failed again, same issue.
>Logs available here: http://10.219.115.222/ISOS/ALL_NODES_20191028.125727.tar
>See the log attached too.
>
>Regards.
>Juan Carlos Alonso
>
>
>-----Original Message-----
>From: Alonso, Juan Carlos
>Sent: Monday, October 28, 2019 9:45 AM
>To: Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>; Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Lemus Contreras, Cristopher J <Cristopher.J.Lemus.Contreras at intel.com<mailto:Cristopher.J.Lemus.Contreras at intel.com>>; Martinez Monroy, Elio <elio.martinez.monroy at intel.com<mailto:elio.martinez.monroy at intel.com>>
>Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>Hello,
>
>Deployment and sanity execution was launched last Friday.
>AIO-SX, AIO-DX and Standard Local Storage deployed successfully and sanity passed.
>Cristopher found that for Standard External Storage there was a failure with nova-compute pods, this is causing system application-apply stuck at 54%.
>Cristopher also put the logs from collect here: http://10.219.115.222/ISOS/ALL_NODES_20191025.153624.tar
>
>Today only Standard External Storage was launched in BareMetal and virtual environments to assure this is a real issue. Will let you know.
>
>Regards.
>Juan Carlos Alonso
>
>-----Original Message-----
>From: Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>
>Sent: Friday, October 25, 2019 12:22 AM
>To: Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>; Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras at intel.com<mailto:cristopher.j.lemus.contreras at intel.com>>
>Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>Hi JC,
>
>Please use below EB, which based on 1024 daily build
>
>Thanks!
>Zhipeng
>
>-----Original Message-----
>From: Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>
>Sent: 2019年10月25日 3:24
>To: Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>; Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras at intel.com<mailto:cristopher.j.lemus.contreras at intel.com>>
>Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>Hello ZhipengS,
>
>Based on last StarlingX release meeting, we need a new EB with the fix merged since we have to execute sanity in both standard configurations.
>Please can you generate a new EB to star testing?
>
>Regards.
>Juan Carlos Alonso
>
>-----Original Message-----
>From: Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>
>Sent: Wednesday, October 23, 2019 8:47 PM
>To: Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>; Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras at intel.com<mailto:cristopher.j.lemus.contreras at intel.com>>
>Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>Hi JC,
>
>Thanks for your update!
>According to your test result, it seems just some known issues caused by other changes seen in your test.
>Standards setup failure should be introduced in recent code merge.
>Since you passed this case when you used my first EB that based on earlier daily build.
>BTW, I also passed simplex test in bare metal environment yesterday with EB03
>
>@all,
>Based on current status, I think we can claim sanity test is good enough and can push related patches to be merged now.
>
>For images, as this is just for internal verification, they are private images pushed by me. So, you could not get them in your private registry and only get them from dock.io. That's not the problem!
>
>Thanks!
>Zhipeng
>
>-----Original Message-----
>From: Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>
>Sent: 2019年10月24日 3:41
>To: Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>; Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras at intel.com<mailto:cristopher.j.lemus.contreras at intel.com>>
>Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>Last update, on Virtual environment we have the same issue: AIO-SX and AIO-DX success. Both standards failed.
>
>Regards.
>Juan Carlos Alonso
>
>-----Original Message-----
>From: Alonso, Juan Carlos
>Sent: Wednesday, October 23, 2019 10:44 AM
>To: Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>; Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>; Lemus Contreras, Cristopher J <Cristopher.J.Lemus.Contreras at intel.com<mailto:Cristopher.J.Lemus.Contreras at intel.com>>
>Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>Hello ZhipengS,
>
>On Baremetal, deployment and Sanity on Simplex and Duplex success, but failed in both standards.
>Your EB is based on master branch, right? Has been an issue last days and the fix has been submitted and merged: https://review.opendev.org/#/c/689438/
>So, deployment on standards should work and if you generate a new EB should work too.
>
>On virtual environment, all deployments for all configs success.
>
>During the apply of stx-openstack, it failed due to the lack of some images, we are using a private registry and images could not found there.
>Images were downloaded manually and stx-openstack re applied.
>Do you have the updated list of the images you download? I CC to Cristopher who helped me with deployment and figure out this issue.
>
>Regards.
>Juan Carlos Alonso
>
>-----Original Message-----
>From: Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>
>Sent: Wednesday, October 23, 2019 3:33 AM
>To: Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>
>Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>I have tested EB 303 in our simplex bare metal environment Deployment and basic VM test pass!
>
>Zhipeng
>
>-----Original Message-----
>From: Liu, ZhipengS
>Sent: 2019年10月23日 10:27
>To: Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>
>Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>Hi JC,
>
>I saw the fixed provided by Bob already in my EB 303.
>Have you tested this one, any update?
>
>Thanks!
>Zhipeng
>
>-----Original Message-----
>From: Liu, ZhipengS
>Sent: 2019年10月23日 9:30
>To: Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>
>Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>Hi JC,
>
>I saw that sanity test of daily build also has the same issue as you have.
>I will trigger a new EB with the fixed provide by Bob.
>https://review.opendev.org/#/c/689643/ Ensure minimal replicas for platform-integ-apps managed apply
>
>Thanks!
>Zhipeng
>
>-----Original Message-----
>From: Liu, ZhipengS
>Sent: 2019年10月22日 22:27
>To: Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>; Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>
>Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>Yes
>
>But the failure place JC met is not the same as I saw.
>I met one failure on applying openstack, but JC saw the failure on applying platform app, which should not be related to train upgrade.
>For my failure case, it should disable nova schedule node probe as we did before, I add this fix in my new EB based on latest Daily build 1021.
>
>@JC, I triggered EB-303, it may be available in 2 hours, you can check the status below http://dcp-dev.intel.com/jenkins/blue/organizations/jenkins/StarlingX%2Fstx-eng-build/activity
>When it is ready, you can fetch EB from here and retest in BM setup.
>http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/303/outputs/
>
>Thanks!
>Zhipeng
>
>-----Original Message-----
>From: Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>
>Sent: 2019年10月22日 22:07
>To: Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>; Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>; Cabrales, Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>Cc: Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>
>Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade
>
>Thanks Zhipeng, I suppose RC means Root Cause. :-)
>
>On 2019/10/22 9:37 PM, Liu, ZhipengS wrote:
>> Hi JC,
>>
>> I should find the RC, will send you a new EB in 1 hour.
>>
>> Thanks!
>>
>> Zhipeng
>>
>> *From:*Liu, ZhipengS <zhipengs.liu at intel.com<mailto:zhipengs.liu at intel.com>>
>> *Sent:* 2019年10月22日9:27
>> *To:* Alonso, Juan Carlos <juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>; Cabrales,
>> Ada <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
>> *Cc:* Xie, Cindy <cindy.xie at intel.com<mailto:cindy.xie at intel.com>>; Hu, Yong <yong.hu at intel.com<mailto:yong.hu at intel.com>>;
>> Jones, Bruce E <bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com>>
>> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack
>> train upgrade
>>
>> Hi JC,
>>
>> Thanks for your quick update!
>>
>> Could you help share your logs?
>>
>> Anyway, I will also try it in BM environment.
>>
>> Thanks!
>>
>> Zhipeng
>>
>> ----------------------------------------------------------------------
>> --
>>
>> *From:*Alonso, Juan Carlos
>> *Sent:* Tuesday, October 22, 2019 1:13 AM
>> *To:* Liu, ZhipengS; Cabrales, Ada
>> *Cc:* Xie, Cindy; Hu, Yong; Jones, Bruce E
>> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack
>> train upgrade
>>
>> Hello ZhipengS,
>>
>> A Sanity execution was launched last Friday on Virtual and BareMetal
>> environment.
>>
>> In virtual environment there was not issues during installation,
>> provisioning nor sanity.
>>
>> In BareMetal environment it could be installed but failed during
>> provisioning in 4 configurations:
>>
>> ======================================================================
>> ========
>>
>> Provision :: Tests for provisioning and unlocking controllers,
>> computes and
>>
>> ======================================================================
>> ========
>>
>> Provisioning Standard Storage System :: Validates provisioning of ...
>> | FAIL |
>>
>> Maximum limit of started keywords exceeded.
>>
>> The issue was during system application-apply:
>>
>> [sysadmin at controller-0 ~(keystone_admin)]$ system application-list
>>
>> +---------------------+---------+-------------------------------+---------------+---------------+------------------------------------------+
>>
>> | application | version | manifest name |
>> manifest file | status | progress
>> |
>>
>> +---------------------+---------+-------------------------------+---------------+---------------+------------------------------------------+
>>
>> | platform-integ-apps | 1.0-8 | platform-integration-manifest |
>> manifest.yaml | remove-failed | operation aborted, check logs for
>> detail |
>>
>> +---------------------+---------+-------------------------------+---------------+---------------+------------------------------------------+
>>
>> Regards.
>>
>> Juan Carlos Alonso
>>
>> *From:*Liu, ZhipengS <zhipengs.liu at intel.com
>> <mailto:zhipengs.liu at intel.com>>
>> *Sent:* Sunday, October 20, 2019 8:35 PM
>> *To:* Cabrales, Ada <ada.cabrales at intel.com
>> <mailto:ada.cabrales at intel.com>>
>> *Cc:* Xie, Cindy <cindy.xie at intel.com <mailto:cindy.xie at intel.com<mailto:cindy.xie at intel.com%20%3cmailto:cindy.xie at intel.com>>>;
>> Hu, Yong <yong.hu at intel.com <mailto:yong.hu at intel.com<mailto:yong.hu at intel.com%20%3cmailto:yong.hu at intel.com>>>; Jones, Bruce
>> E <bruce.e.jones at intel.com <mailto:bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com%20%3cmailto:bruce.e.jones at intel.com>>>; Alonso,
>> Juan Carlos <juan.carlos.alonso at intel.com
>> <mailto:juan.carlos.alonso at intel.com>>
>> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack
>> train upgrade
>>
>> Hi Ada,
>>
>> Do we have test result now?
>>
>> Thanks!
>>
>> Zhipeng
>>
>> *From:*Cabrales, Ada <ada.cabrales at intel.com
>> <mailto:ada.cabrales at intel.com>>
>> *Sent:* 2019年10月14日22:20
>> *To:* Liu, ZhipengS <zhipengs.liu at intel.com
>> <mailto:zhipengs.liu at intel.com>>
>> *Cc:* Xie, Cindy <cindy.xie at intel.com <mailto:cindy.xie at intel.com<mailto:cindy.xie at intel.com%20%3cmailto:cindy.xie at intel.com>>>;
>> Hu, Yong <yong.hu at intel.com <mailto:yong.hu at intel.com<mailto:yong.hu at intel.com%20%3cmailto:yong.hu at intel.com>>>; Jones, Bruce
>> E <bruce.e.jones at intel.com <mailto:bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com%20%3cmailto:bruce.e.jones at intel.com>>>; Alonso,
>> Juan Carlos <juan.carlos.alonso at intel.com
>> <mailto:juan.carlos.alonso at intel.com>>
>> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack
>> train upgrade
>>
>> Sure, let us try with this one.
>>
>> Thanks!
>>
>> Ada
>>
>> *From:*Liu, ZhipengS <zhipengs.liu at intel.com
>> <mailto:zhipengs.liu at intel.com>>
>> *Sent:* Sunday, October 13, 2019 6:44 AM
>> *To:* Cabrales, Ada <ada.cabrales at intel.com
>> <mailto:ada.cabrales at intel.com>>
>> *Cc:* Xie, Cindy <cindy.xie at intel.com <mailto:cindy.xie at intel.com<mailto:cindy.xie at intel.com%20%3cmailto:cindy.xie at intel.com>>>;
>> Hu, Yong <yong.hu at intel.com <mailto:yong.hu at intel.com<mailto:yong.hu at intel.com%20%3cmailto:yong.hu at intel.com>>>; Jones, Bruce
>> E <bruce.e.jones at intel.com <mailto:bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com%20%3cmailto:bruce.e.jones at intel.com>>>
>> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack
>> train upgrade
>>
>> Hi Ada,
>>
>> Could you please use below new EB?
>>
>> One horizon issue was fixed, found during my duplex test.
>>
>> http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/294/outputs/
>>
>> Thanks!
>>
>> Zhipeng
>>
>> *From:*Liu, ZhipengS <zhipengs.liu at intel.com
>> <mailto:zhipengs.liu at intel.com>>
>> *Sent:* 2019年10月11日20:43
>> *To:* Cabrales, Ada <ada.cabrales at intel.com
>> <mailto:ada.cabrales at intel.com>>; Jones, Bruce E
>> <bruce.e.jones at intel.com <mailto:bruce.e.jones at intel.com<mailto:bruce.e.jones at intel.com%20%3cmailto:bruce.e.jones at intel.com>>>
>> *Cc:* starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
>> <mailto:starlingx-discuss at lists.starlingx.io>
>> *Subject:* [Starlingx-discuss] About EB verification for openstack
>> train upgrade
>>
>> Hi Ada and Bruce,
>>
>> So far, I have finished openstack train upgrade and
>> openstack-helm/helm-infra upgrade.
>>
>> Story: https://storyboard.openstack.org/#!/story/2006544
>>
>> Basic deployment and VM creation/remove test pass in AIO setup!
>>
>> @Ada <mailto:ada.cabrales at intel.com>, Could you help to arrange sanity
>> test with below EB, thanks!
>>
>> http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/290/outputs/
>>
>> Current status summarized as below.
>>
>> 1)Openstack upgrade
>>
>> Finished 13 services upgrade, including nova, neutron, keystone,
>> cinder, glance, placement, aodh, ironic, panko, barbican, ceilometer, heat, horizon.
>>
>> 2)Openstack-helm/helm-infra upgrade
>>
>> Upgrade openstack-helm to below version. 13 patches removed
>>
>> commit 82c72367c85ca94270f702661c7b984899c1ae38
>> <https://review.opendev.org/#/q/82c72367c85ca94270f702661c7b984899c1ae38> //Date:
>> Sat Sep 14 06:40:03 2019 +0000
>>
>> Upgrade openstack-helm-infra to below version. 1 patch removed
>>
>> commit c9d6676bf9a5aceb311dc31dadd07cba6a3d6392
>> <https://review.opendev.org/#/q/c9d6676bf9a5aceb311dc31dadd07cba6a3d6392> //Date:
>> Mon Sep 16 17:15:12 2019 +0000
>>
>> 6 patches submitted for review, your comments are appreciated, thanks!
>>
>> https://review.opendev.org/#/c/683886/
>>
>> https://review.opendev.org/#/c/683910/
>>
>> https://review.opendev.org/#/c/684166/
>>
>> https://review.opendev.org/#/c/687441/
>>
>> https://review.opendev.org/#/c/687197/
>>
>> https://review.opendev.org/#/c/688105/
>>
>> Thanks!
>>
>> zhipeng
>>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20191030/95200164/attachment-0001.html>
More information about the Starlingx-discuss
mailing list