[Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches.
Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*.
Yong, Has someone run the VIM automated testing against the new load? See attached email for details. Bart -----Original Message----- From: Yong Hu [mailto:yong.hu@intel.com] Sent: November 5, 2019 9:47 AM To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Bart, It's a fair requirement, and I would suggest to run this test on the build image from Cengn after these patches merged, because: 1). we don't upgrade Openstack clients at this time as agreed previously. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. regards, Yong On 2019/11/5 11:11 PM, Wensley, Barton wrote:
Yong,
Has someone run the VIM automated testing against the new load? See attached email for details.
Bart
-----Original Message----- From: Yong Hu [mailto:yong.hu@intel.com] Sent: November 5, 2019 9:47 AM To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches.
Hi Core reviewers in Stx.distro.openstack:
The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher).
So to unblock stx.3.0 MS-3, please review the following patches in time:
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/
In addition, some background info related to this upgrade:
1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header.
2). these patches have to be merged *in one batch* due to the inter-dependencies.
3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Yong, To reply to your comments: 1). we don't upgrade Openstack clients at this time as agreed previously. The VIM doesn't use the OpenStack clients - it uses the OpenStack REST APIs directly. Often we find that when OpenStack is upversioned there can be things deprecated in the OpenStack REST APIs that break the VIM's use of these APIs. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. The fixes would be in StarlingX - not upstream. We would need to update the VIM to use the modified REST APIs. I prefer that we do this testing ahead of time instead of waiting for things to break and fixing the problems after the fact. Bart -----Original Message----- From: Yong Hu [mailto:yong.hu@intel.com] Sent: November 5, 2019 10:25 PM To: Wensley, Barton; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Bart, It's a fair requirement, and I would suggest to run this test on the build image from Cengn after these patches merged, because: 1). we don't upgrade Openstack clients at this time as agreed previously. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. regards, Yong On 2019/11/5 11:11 PM, Wensley, Barton wrote:
Yong,
Has someone run the VIM automated testing against the new load? See attached email for details.
Bart
-----Original Message----- From: Yong Hu [mailto:yong.hu@intel.com] Sent: November 5, 2019 9:47 AM To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches.
Hi Core reviewers in Stx.distro.openstack:
The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher).
So to unblock stx.3.0 MS-3, please review the following patches in time:
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/
In addition, some background info related to this upgrade:
1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header.
2). these patches have to be merged *in one batch* due to the inter-dependencies.
3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Barton, I have tested it with train engineering build today and pass! 2019-11-07 02:33:46.114 Test Instance-Pause ........................................ [OKAY] (2019-11-07 02:34:03.143 Δ=0:00:15.705) 2019-11-07 02:34:22.461 Test Instance-Unpause ...................................... [OKAY] (2019-11-07 02:34:29.069 Δ=0:00:05.879) 2019-11-07 02:34:43.772 Test Instance-Suspend ...................................... [OKAY] (2019-11-07 02:34:50.718 Δ=0:00:05.979) 2019-11-07 02:35:05.504 Test Instance-Resume ....................................... [OKAY] (2019-11-07 02:35:13.117 Δ=0:00:06.686) 2019-11-07 02:35:27.728 Test Instance-Reboot (soft) ................................ [OKAY] (2019-11-07 02:37:38.259 Δ=0:02:09.730) 2019-11-07 02:37:56.491 Test Instance-Reboot (hard) ................................ [OKAY] (2019-11-07 02:38:10.572 Δ=0:00:13.240) 2019-11-07 02:38:30.390 Test Instance-Stop ......................................... [OKAY] (2019-11-07 02:39:44.231 Δ=0:01:12.920) 2019-11-07 02:40:02.574 Test Instance-Start ........................................ [OKAY] (2019-11-07 02:40:09.293 Δ=0:00:05.941) 2019-11-07 02:40:24.714 Test Instance-Live-Migrate ................................. [OKAY] (2019-11-07 02:40:51.549 Δ=0:00:26.019) 2019-11-07 02:41:10.837 Test Instance-Cold-Migrate ................................. [OKAY] (2019-11-07 02:42:39.383 Δ=0:01:27.523) 2019-11-07 02:42:57.811 Test Instance-Cold-Migrate-Confirm ......................... [OKAY] (2019-11-07 02:43:04.873 Δ=0:00:06.199) 2019-11-07 02:43:20.031 Test Instance-Cold-Migrate-Revert .......................... [OKAY] (2019-11-07 02:45:06.808 Δ=0:00:25.094) 2019-11-07 02:45:26.019 Test Instance-Resize ....................................... [OKAY] (2019-11-07 02:46:54.315 Δ=0:01:26.712) 2019-11-07 02:47:13.467 Test Instance-Resize-Confirm ............................... [OKAY] (2019-11-07 02:47:20.348 Δ=0:00:06.114) 2019-11-07 02:47:35.183 Test Instance-Resize-Revert ................................ [OKAY] (2019-11-07 02:49:23.016 Δ=0:00:25.547) 2019-11-07 02:49:41.797 Test Instance-Rebuild ...................................... [OKAY] (2019-11-07 02:50:55.560 Δ=0:01:13.040) Total-Tests: 16 Execution-Time: 0:17:27.933 Thanks! Zhipeng -----Original Message----- From: Wensley, Barton <Barton.Wensley@windriver.com> Sent: 2019年11月6日 20:47 To: Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Yong, To reply to your comments: 1). we don't upgrade Openstack clients at this time as agreed previously. The VIM doesn't use the OpenStack clients - it uses the OpenStack REST APIs directly. Often we find that when OpenStack is upversioned there can be things deprecated in the OpenStack REST APIs that break the VIM's use of these APIs. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. The fixes would be in StarlingX - not upstream. We would need to update the VIM to use the modified REST APIs. I prefer that we do this testing ahead of time instead of waiting for things to break and fixing the problems after the fact. Bart -----Original Message----- From: Yong Hu [mailto:yong.hu@intel.com] Sent: November 5, 2019 10:25 PM To: Wensley, Barton; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Bart, It's a fair requirement, and I would suggest to run this test on the build image from Cengn after these patches merged, because: 1). we don't upgrade Openstack clients at this time as agreed previously. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. regards, Yong On 2019/11/5 11:11 PM, Wensley, Barton wrote:
Yong,
Has someone run the VIM automated testing against the new load? See attached email for details.
Bart
-----Original Message----- From: Yong Hu [mailto:yong.hu@intel.com] Sent: November 5, 2019 9:47 AM To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches.
Hi Core reviewers in Stx.distro.openstack:
The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher).
So to unblock stx.3.0 MS-3, please review the following patches in time:
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/
In addition, some background info related to this upgrade:
1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header.
2). these patches have to be merged *in one batch* due to the inter-dependencies.
3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Thanks Zhipeng - that is great news. Bart -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: November 7, 2019 3:54 AM To: Wensley, Barton; Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Barton, I have tested it with train engineering build today and pass! 2019-11-07 02:33:46.114 Test Instance-Pause ........................................ [OKAY] (2019-11-07 02:34:03.143 Δ=0:00:15.705) 2019-11-07 02:34:22.461 Test Instance-Unpause ...................................... [OKAY] (2019-11-07 02:34:29.069 Δ=0:00:05.879) 2019-11-07 02:34:43.772 Test Instance-Suspend ...................................... [OKAY] (2019-11-07 02:34:50.718 Δ=0:00:05.979) 2019-11-07 02:35:05.504 Test Instance-Resume ....................................... [OKAY] (2019-11-07 02:35:13.117 Δ=0:00:06.686) 2019-11-07 02:35:27.728 Test Instance-Reboot (soft) ................................ [OKAY] (2019-11-07 02:37:38.259 Δ=0:02:09.730) 2019-11-07 02:37:56.491 Test Instance-Reboot (hard) ................................ [OKAY] (2019-11-07 02:38:10.572 Δ=0:00:13.240) 2019-11-07 02:38:30.390 Test Instance-Stop ......................................... [OKAY] (2019-11-07 02:39:44.231 Δ=0:01:12.920) 2019-11-07 02:40:02.574 Test Instance-Start ........................................ [OKAY] (2019-11-07 02:40:09.293 Δ=0:00:05.941) 2019-11-07 02:40:24.714 Test Instance-Live-Migrate ................................. [OKAY] (2019-11-07 02:40:51.549 Δ=0:00:26.019) 2019-11-07 02:41:10.837 Test Instance-Cold-Migrate ................................. [OKAY] (2019-11-07 02:42:39.383 Δ=0:01:27.523) 2019-11-07 02:42:57.811 Test Instance-Cold-Migrate-Confirm ......................... [OKAY] (2019-11-07 02:43:04.873 Δ=0:00:06.199) 2019-11-07 02:43:20.031 Test Instance-Cold-Migrate-Revert .......................... [OKAY] (2019-11-07 02:45:06.808 Δ=0:00:25.094) 2019-11-07 02:45:26.019 Test Instance-Resize ....................................... [OKAY] (2019-11-07 02:46:54.315 Δ=0:01:26.712) 2019-11-07 02:47:13.467 Test Instance-Resize-Confirm ............................... [OKAY] (2019-11-07 02:47:20.348 Δ=0:00:06.114) 2019-11-07 02:47:35.183 Test Instance-Resize-Revert ................................ [OKAY] (2019-11-07 02:49:23.016 Δ=0:00:25.547) 2019-11-07 02:49:41.797 Test Instance-Rebuild ...................................... [OKAY] (2019-11-07 02:50:55.560 Δ=0:01:13.040) Total-Tests: 16 Execution-Time: 0:17:27.933 Thanks! Zhipeng -----Original Message----- From: Wensley, Barton <Barton.Wensley@windriver.com> Sent: 2019年11月6日 20:47 To: Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Yong, To reply to your comments: 1). we don't upgrade Openstack clients at this time as agreed previously. The VIM doesn't use the OpenStack clients - it uses the OpenStack REST APIs directly. Often we find that when OpenStack is upversioned there can be things deprecated in the OpenStack REST APIs that break the VIM's use of these APIs. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. The fixes would be in StarlingX - not upstream. We would need to update the VIM to use the modified REST APIs. I prefer that we do this testing ahead of time instead of waiting for things to break and fixing the problems after the fact. Bart -----Original Message----- From: Yong Hu [mailto:yong.hu@intel.com] Sent: November 5, 2019 10:25 PM To: Wensley, Barton; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Bart, It's a fair requirement, and I would suggest to run this test on the build image from Cengn after these patches merged, because: 1). we don't upgrade Openstack clients at this time as agreed previously. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. regards, Yong On 2019/11/5 11:11 PM, Wensley, Barton wrote:
Yong,
Has someone run the VIM automated testing against the new load? See attached email for details.
Bart
-----Original Message----- From: Yong Hu [mailto:yong.hu@intel.com] Sent: November 5, 2019 9:47 AM To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches.
Hi Core reviewers in Stx.distro.openstack:
The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher).
So to unblock stx.3.0 MS-3, please review the following patches in time:
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/
In addition, some background info related to this upgrade:
1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header.
2). these patches have to be merged *in one batch* due to the inter-dependencies.
3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*.
Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 5:54 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don <Don.Penney@windriver.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 5:54 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don <Don.Penney@windriver.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 5:54 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Don, See my inline comment. Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 11:49 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? Zhipeng: Yes, I updated this patch VERY later with my comment, as I saw some incompatible error though they do not impact pod start/stop and sanity test. 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. Zhipeng: Yes, we thought it will be OK with a clean build without workaround. We found the root cause but not used a right Method, we should have consult you earlier. Sorry for that! -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don <Don.Penney@windriver.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 5:54 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I updated my review with a couple more python modules, and the wheels and images are now building fine for me: https://review.opendev.org/693949 -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 10:49 PM To: 'Liu, ZhipengS'; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don <Don.Penney@windriver.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 5:54 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Don, I have submitted another patch for the issue of communication between horizon and cinderclient. This is a known issue during my upgrade work(In my test image, it was downgraded to 4.3.0). However, upstream still not fix it by now. https://review.opendev.org/#/c/694193/ Fix bug of communication between Horizon and cinderclient. We have to downgrade python-cinderclient from 5.0.0(specified inupper-constraints) to 4.3.0. Otherwise, we will meet some error during operating in horizon gui. Related upstream bug and patch list as below. FYI. https://review.opendev.org/#/c/643405/ https://bugs.launchpad.net/horizon/+bug/1815635 https://review.opendev.org/#/c/675891/ BTW, Austin fixed another build issue that we have not met before during building image. Attached his email for detail. We still not sure why it can pass build before? Any idea? Have you met this issue during your own build for horizon? Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 12:30 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. I updated my review with a couple more python modules, and the wheels and images are now building fine for me: https://review.opendev.org/693949 -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 10:49 PM To: 'Liu, ZhipengS'; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don <Don.Penney@windriver.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 5:54 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Thanks Zhipeng. Once your update is merged, along with Austin's, I'll kick off a new build. The image build failed yesterday because of new dependencies that were added to a module less than an hour before I kicked off the build, unfortunately. Bad timing! -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Wednesday, November 13, 2019 10:44 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, I have submitted another patch for the issue of communication between horizon and cinderclient. This is a known issue during my upgrade work(In my test image, it was downgraded to 4.3.0). However, upstream still not fix it by now. https://review.opendev.org/#/c/694193/ Fix bug of communication between Horizon and cinderclient. We have to downgrade python-cinderclient from 5.0.0(specified inupper-constraints) to 4.3.0. Otherwise, we will meet some error during operating in horizon gui. Related upstream bug and patch list as below. FYI. https://review.opendev.org/#/c/643405/ https://bugs.launchpad.net/horizon/+bug/1815635 https://review.opendev.org/#/c/675891/ BTW, Austin fixed another build issue that we have not met before during building image. Attached his email for detail. We still not sure why it can pass build before? Any idea? Have you met this issue during your own build for horizon? Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 12:30 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. I updated my review with a couple more python modules, and the wheels and images are now building fine for me: https://review.opendev.org/693949 -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 10:49 PM To: 'Liu, ZhipengS'; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don <Don.Penney@windriver.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 5:54 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I hit a few additional issues trying to build stx-horizon and have posted reviews. Once these additional updates merge, I can kick off a build: https://review.opendev.org/#/q/projects:starlingx+branch:master+topic:fix-st... -----Original Message----- From: Penney, Don [mailto:Don.Penney@windriver.com] Sent: Thursday, November 14, 2019 9:59 AM To: Liu, ZhipengS; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Thanks Zhipeng. Once your update is merged, along with Austin's, I'll kick off a new build. The image build failed yesterday because of new dependencies that were added to a module less than an hour before I kicked off the build, unfortunately. Bad timing! -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Wednesday, November 13, 2019 10:44 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, I have submitted another patch for the issue of communication between horizon and cinderclient. This is a known issue during my upgrade work(In my test image, it was downgraded to 4.3.0). However, upstream still not fix it by now. https://review.opendev.org/#/c/694193/ Fix bug of communication between Horizon and cinderclient. We have to downgrade python-cinderclient from 5.0.0(specified inupper-constraints) to 4.3.0. Otherwise, we will meet some error during operating in horizon gui. Related upstream bug and patch list as below. FYI. https://review.opendev.org/#/c/643405/ https://bugs.launchpad.net/horizon/+bug/1815635 https://review.opendev.org/#/c/675891/ BTW, Austin fixed another build issue that we have not met before during building image. Attached his email for detail. We still not sure why it can pass build before? Any idea? Have you met this issue during your own build for horizon? Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 12:30 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. I updated my review with a couple more python modules, and the wheels and images are now building fine for me: https://review.opendev.org/693949 -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 10:49 PM To: 'Liu, ZhipengS'; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don <Don.Penney@windriver.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 5:54 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
The updates have all merged, so I've launched a new build with images. -----Original Message----- From: Penney, Don Sent: Thursday, November 14, 2019 11:06 AM To: Penney, Don; Liu, ZhipengS; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. I hit a few additional issues trying to build stx-horizon and have posted reviews. Once these additional updates merge, I can kick off a build: https://review.opendev.org/#/q/projects:starlingx+branch:master+topic:fix-st... -----Original Message----- From: Penney, Don [mailto:Don.Penney@windriver.com] Sent: Thursday, November 14, 2019 9:59 AM To: Liu, ZhipengS; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Thanks Zhipeng. Once your update is merged, along with Austin's, I'll kick off a new build. The image build failed yesterday because of new dependencies that were added to a module less than an hour before I kicked off the build, unfortunately. Bad timing! -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Wednesday, November 13, 2019 10:44 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, I have submitted another patch for the issue of communication between horizon and cinderclient. This is a known issue during my upgrade work(In my test image, it was downgraded to 4.3.0). However, upstream still not fix it by now. https://review.opendev.org/#/c/694193/ Fix bug of communication between Horizon and cinderclient. We have to downgrade python-cinderclient from 5.0.0(specified inupper-constraints) to 4.3.0. Otherwise, we will meet some error during operating in horizon gui. Related upstream bug and patch list as below. FYI. https://review.opendev.org/#/c/643405/ https://bugs.launchpad.net/horizon/+bug/1815635 https://review.opendev.org/#/c/675891/ BTW, Austin fixed another build issue that we have not met before during building image. Attached his email for detail. We still not sure why it can pass build before? Any idea? Have you met this issue during your own build for horizon? Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 12:30 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. I updated my review with a couple more python modules, and the wheels and images are now building fine for me: https://review.opendev.org/693949 -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 10:49 PM To: 'Liu, ZhipengS'; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss@lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don <Don.Penney@windriver.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don <Don.Penney@windriver.com> Sent: 2019年11月13日 5:54 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I've posted an update to align the wheels.cfg with the train upper-constraints and to address this build failure: https://review.opendev.org/693949 I've set W-1 while I test building all the images, in case there are other issues to be uncovered. Cheers, Don. -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 4:54 PM To: 'Liu, ZhipengS'; Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong <yong.hu@intel.com> Sent: 2019年11月5日 22:47 To: starlingx-discuss@lists.starlingx.io; Alonso, Juan Carlos <juan.carlos.alonso@intel.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Lemus Contreras, Cristopher J <cristopher.j.lemus.contreras@intel.com> Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: 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/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (4)
-
Liu, ZhipengS
-
Penney, Don
-
Wensley, Barton
-
Yong Hu