For the build-iso failure, it should be due to dependency check. There should be another file “deps-detail.txt” under the same folder as deps.txt. (/localdisk/loadbuild/dehao/starlingx/export/deps.txt) You could get more info from this file. Best Regards Shuicheng From: Hu, Yong [mailto:yong.hu@intel.com] Sent: Wednesday, September 5, 2018 10:02 PM To: Zhu, Vivian <vivian.zhu@intel.com>; starlingx-discuss@lists.starlingx.io Cc: Shang, Dehao <dehao.shang@intel.com> Subject: Re: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Quick question: Before switching to newer version (ceph 13.2.0), have you ever built out the packages and ISO? From: "Zhu, Vivian" <vivian.zhu@intel.com<mailto:vivian.zhu@intel.com>> Date: Wednesday, 5 September 2018 at 9:54 PM To: "starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>" <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Cc: "Shang, Dehao" <dehao.shang@intel.com<mailto:dehao.shang@intel.com>> Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Hi Anyone who is familiar with stx-tools or build flow, Our storage team (Dehao etc.) have worked on Ceph upgrading on starlingX project and we are still staggering to resolve issues one-by-one, now we fail to build ISO, the log points to “These RPMS had problems (likely version conflicts) “. Here is our build steps and according action we did. We are looking for help to solve it, if anyone who can give some hints to narrow down/address issue or point out the wrong step here. That’s really helpful to unblock Ceph upgrade to catch up Sep.26 code freeze. Build flow step 1: download_mirror ---> container 1 | step 2: manually check *_miss_*.txt and *_fails_*.txt file, then download miss and fails package | step 3: to ensure that all package listed by rpms_from_3rd_parties.list and rpms_from_centos_repo.lst are downloaded | step 4: create work space : mkdir -p $HOME/starlingx/mirror/Centos | step 5: copy mirror to workspace which can be used by container 2 | step 6: edit Dockerfile, create image, then run container, and so on. | step 7 : clone all source using "repo sync" → container 2 | step 8: at git folder, using ceph 13.2.0 to replace ceph 10.2.6 | step 9: using ceph tools "make-srpm.sh" to create 13.2.0 ceph.spec file. | step 10 : modify new ceph.spec file according to stx-ceph's ceph.spec file | step 11: copy stx-ceph's wrs folder to ceph 13.2.0 | step 12: build-pkgs --serial | step 13: build_iso <-----------------------------fails ！！！ | step 14 : success building What we had done 1：can build starlingx image 2：ceph 13.2.0’s ceph.spec file can works. 3： build-pkgs can build all package What part we are gating when building ISO, deps can’t be resolved. we tried steps but failed. Stalingx log give one error conclusion as following: 22:14:55 Debug: Packages still unresolved: 22:14:55 22:14:56 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 22:14:56 These RPMS had problems (likely version conflicts) 22:14:56 librados.so.2()(64bit) 22:14:56 Could not install dependencies What’s the next step 1: Talked with Qi mingyuan, plan to compare every ceph 13.2.0 depes package with mirror’s package. 2: Deploy one starlingx cluster, check package and env. Help needed If we can get stx-tools design, implement overview or building flow, it can help us speed up the debug/upgrading. Thanks! - Vivian SSG OTC NST Storage Tel: (8621)61167437

Hi, yong: We have successfully built starlingx image. Now, then just replace old version ceph with ceph 13.2.0 version. So, I can think that current all error are caused by new version ceph. Thanks Dehao From: Hu, Yong Sent: Wednesday, September 5, 2018 10:02 PM To: Zhu, Vivian <vivian.zhu@intel.com>; starlingx-discuss@lists.starlingx.io Cc: Shang, Dehao <dehao.shang@intel.com> Subject: Re: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Quick question: Before switching to newer version (ceph 13.2.0), have you ever built out the packages and ISO? From: "Zhu, Vivian" <vivian.zhu@intel.com<mailto:vivian.zhu@intel.com>> Date: Wednesday, 5 September 2018 at 9:54 PM To: "starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>" <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Cc: "Shang, Dehao" <dehao.shang@intel.com<mailto:dehao.shang@intel.com>> Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Hi Anyone who is familiar with stx-tools or build flow, Our storage team (Dehao etc.) have worked on Ceph upgrading on starlingX project and we are still staggering to resolve issues one-by-one, now we fail to build ISO, the log points to “These RPMS had problems (likely version conflicts) “. Here is our build steps and according action we did. We are looking for help to solve it, if anyone who can give some hints to narrow down/address issue or point out the wrong step here. That’s really helpful to unblock Ceph upgrade to catch up Sep.26 code freeze. Build flow step 1: download_mirror ---> container 1 | step 2: manually check *_miss_*.txt and *_fails_*.txt file, then download miss and fails package | step 3: to ensure that all package listed by rpms_from_3rd_parties.list and rpms_from_centos_repo.lst are downloaded | step 4: create work space : mkdir -p $HOME/starlingx/mirror/Centos | step 5: copy mirror to workspace which can be used by container 2 | step 6: edit Dockerfile, create image, then run container, and so on. | step 7 : clone all source using "repo sync" → container 2 | step 8: at git folder, using ceph 13.2.0 to replace ceph 10.2.6 | step 9: using ceph tools "make-srpm.sh" to create 13.2.0 ceph.spec file. | step 10 : modify new ceph.spec file according to stx-ceph's ceph.spec file | step 11: copy stx-ceph's wrs folder to ceph 13.2.0 | step 12: build-pkgs --serial | step 13: build_iso <-----------------------------fails ！！！ | step 14 : success building What we had done 1：can build starlingx image 2：ceph 13.2.0’s ceph.spec file can works. 3： build-pkgs can build all package What part we are gating when building ISO, deps can’t be resolved. we tried steps but failed. Stalingx log give one error conclusion as following: 22:14:55 Debug: Packages still unresolved: 22:14:55 22:14:56 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 22:14:56 These RPMS had problems (likely version conflicts) 22:14:56 librados.so.2()(64bit) 22:14:56 Could not install dependencies What’s the next step 1: Talked with Qi mingyuan, plan to compare every ceph 13.2.0 depes package with mirror’s package. 2: Deploy one starlingx cluster, check package and env. Help needed If we can get stx-tools design, implement overview or building flow, it can help us speed up the debug/upgrading. Thanks! - Vivian SSG OTC NST Storage Tel: (8621)61167437

From this file: https://github.com/ceph/ceph/blob/mimic/ceph.spec.in We can see “%package -n librados2” and “%package -n librados-devel” still existing, so technically related RPMs will be built out together with Ceph RPMs. Then next step is to figure out anything, which librados2 depends on, is missing. From: "McKenna, Jason" <Jason.McKenna@windriver.com> Date: Wednesday, 5 September 2018 at 10:22 PM To: "Zhu, Vivian" <vivian.zhu@intel.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Cc: "Shang, Dehao" <dehao.shang@intel.com> Subject: Re: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status , Hi Vivian, librados.so.2()(64bit) should be provided by the librados2 package which is built as part of ceph 10.x.x. I suspect this package did not get built in your environment (which is why build-iso fails to find it) because the updated version of ceph does not build the package. There are a few possibilities here: * Maybe librados2 is an optional output of the ceph package. You’d have to “turn on” this functionality * Maybe librados2 has been renamed or upversioned. You’d have to update the spec file for whatever is requiring librados.so.2()(64bit) to use the new name/version of the library * Maybe librados2 is no longer required. You’d have to update the spec file for whatever is requiring librados.so.2()(64bit) to remove the requirement You can check what package has the “librados.so.2()(64bit)” requirement by looking at the $MY_WORKSPACE/export/deps_detail.txt file Hope this helps! -Jason From: Zhu, Vivian <vivian.zhu@intel.com> Sent: September 5, 2018 9:53 AM To: starlingx-discuss@lists.starlingx.io Cc: Shang, Dehao <dehao.shang@intel.com> Subject: [Starlingx-discuss] [StarlingX] Ceph upgrade from 10.x.x to 13.2.0 status Hi Anyone who is familiar with stx-tools or build flow, Our storage team (Dehao etc.) have worked on Ceph upgrading on starlingX project and we are still staggering to resolve issues one-by-one, now we fail to build ISO, the log points to “These RPMS had problems (likely version conflicts) “. Here is our build steps and according action we did. We are looking for help to solve it, if anyone who can give some hints to narrow down/address issue or point out the wrong step here. That’s really helpful to unblock Ceph upgrade to catch up Sep.26 code freeze. Build flow step 1: download_mirror ---> container 1 | step 2: manually check *_miss_*.txt and *_fails_*.txt file, then download miss and fails package | step 3: to ensure that all package listed by rpms_from_3rd_parties.list and rpms_from_centos_repo.lst are downloaded | step 4: create work space : mkdir -p $HOME/starlingx/mirror/Centos | step 5: copy mirror to workspace which can be used by container 2 | step 6: edit Dockerfile, create image, then run container, and so on. | step 7 : clone all source using "repo sync" → container 2 | step 8: at git folder, using ceph 13.2.0 to replace ceph 10.2.6 | step 9: using ceph tools "make-srpm.sh" to create 13.2.0 ceph.spec file. | step 10 : modify new ceph.spec file according to stx-ceph's ceph.spec file | step 11: copy stx-ceph's wrs folder to ceph 13.2.0 | step 12: build-pkgs --serial | step 13: build_iso <-----------------------------fails ！！！ | step 14 : success building What we had done 1：can build starlingx image 2：ceph 13.2.0’s ceph.spec file can works. 3： build-pkgs can build all package What part we are gating when building ISO, deps can’t be resolved. we tried steps but failed. Stalingx log give one error conclusion as following: 22:14:55 Debug: Packages still unresolved: 22:14:55 22:14:56 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 22:14:56 These RPMS had problems (likely version conflicts) 22:14:56 librados.so.2()(64bit) 22:14:56 Could not install dependencies What’s the next step 1: Talked with Qi mingyuan, plan to compare every ceph 13.2.0 depes package with mirror’s package. 2: Deploy one starlingx cluster, check package and env. Help needed If we can get stx-tools design, implement overview or building flow, it can help us speed up the debug/upgrading. Thanks! - Vivian SSG OTC NST Storage Tel: (8621)61167437