Yes,  both “python3-ipaddr” and “python3-ipaddr” do not exist and removed.

Now I think  we have to face  the issue caused by “python2” to “python3”:

 

07:48:56 TMPDIR=/localdisk/loadbuild/hbai/c81nststx/tmp dnf repoquery -c /localdisk/loadbuild/hbai/c81nststx/export/yum.conf --repoid=local-rt --arch=x86_64,noarch  platform-python  --qf='%{name} %{name}-%{version}-%{release}.%{arch}.rpm %{relativepath}'

07:48:56 local-rt                                        3.0 MB/s | 3.0 kB     00:00

07:48:56 TMPDIR=/localdisk/loadbuild/hbai/c81nststx/tmp dnf repoquery -c /localdisk/loadbuild/hbai/c81nststx/export/yum.conf --repoid=local-installer --arch=x86_64,noarch  platform-python  --qf='%{name} %{name}-%{version}-%{release}.%{arch}.rpm %{relativepath}'

07:48:57 local-installer                                 2.9 MB/s | 3.0 kB     00:00

07:48:57 TMPDIR=/localdisk/loadbuild/hbai/c81nststx/tmp dnf repoquery -c /localdisk/loadbuild/hbai/c81nststx/export/yum.conf --repoid=StxCentos8Distro --arch=x86_64,noarch  platform-python  --qf='%{name} %{name}-%{version}-%{release}.%{arch}.rpm %{relativepath}'

07:48:57 Last metadata expiration check: 0:01:43 ago on Thu 03 Dec 2020 07:47:14 AM UTC.

07:48:57 STR=platform-python platform-python-3.6.8-15.1.el8.x86_64.rpm x86_64/platform-python-3.6.8-15.1.el8.x86_64.rpm

07:48:57 Installing PKG=platform-python PKG_FILE=platform-python-3.6.8-15.1.el8.x86_64.rpm PKG_REL_PATH=x86_64/platform-python-3.6.8-15.1.el8.x86_64.rpm PKG_PATH=/localdisk/designer/hbai/c81nststx/cgcs-root/cgcs-centos-repo/Binary/x86_64/platform-python-3.6.8-15.1.el8.x86_64.rpm from repo StxCentos8Distro

07:48:57 Debug: Packages still unresolved:

07:48:57

07:48:59 Warning: Infinite loop detected in dependency resolution.  See /localdisk/loadbuild/hbai/c81nststx/export/deps.txt for details -- exiting

07:48:59 These RPMS had problems (likely version conflicts)

07:48:59        python(abi)

07:48:59        PyYAML

07:48:59 Could not install dependencies

 

It seems this means that at least not all “python2 runtime dependency” have been addressed on current stx.

 

From: fuyong <fuyong@neusoft.com>
Sent: Tuesday, December 1, 2020 2:54 PM
To: Bai, Haiqing <Haiqing.Bai@windriver.com>; starlingx-discuss@lists.starlingx.io
Cc: Wold, Saul <Saul.Wold@windriver.com>
Subject: Re: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue

 

[Please note this e-mail is from an EXTERNAL e-mail address]

Hi Haiqing Bai

Maybe you can run the following command

"dnf repo-pkgs -c $MY_WORKSPACE/std/yum.conf local-std list"

Make sure the rpm you listed is included in the local-std repo

config/sysinv Requires: python3-ipaddr. But python3-ipaddr package does not exist in centos8
utilites/python-cephclient Requires: python3-ipaddress. But python3-ipaddress package does not exist in centos8

Please confirm in sysinv and python-cephclient, and compile  after commenting.

B,R

Yong Fu

On 2020/12/1 上午11:58, Bai, Haiqing wrote:

Yes,  libvirt can be compiled ok and each sub packages are created, for example:

 

-rw-r--r-- 1 hbai 751     7784 11 30 22:41 libvirt-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751  1921432 11 30 22:41 libvirt-docs-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751     8740 11 30 22:41 libvirt-daemon-config-network-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751   700736 11 30 22:41 libvirt-daemon-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    12728 11 30 22:41 libvirt-daemon-config-nwfilter-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751   243360 11 30 22:41 libvirt-daemon-driver-network-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    74268 11 30 22:41 libvirt-daemon-driver-nwfilter-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    48976 11 30 22:41 libvirt-daemon-driver-nodedev-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    49204 11 30 22:41 libvirt-daemon-driver-interface-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    37812 11 30 22:41 libvirt-daemon-driver-secret-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751   269600 11 30 22:41 libvirt-daemon-driver-storage-core-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    40708 11 30 22:41 libvirt-daemon-driver-storage-logical-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    39512 11 30 22:41 libvirt-daemon-driver-storage-disk-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    36836 11 30 22:41 libvirt-daemon-driver-storage-scsi-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    36780 11 30 22:41 libvirt-daemon-driver-storage-iscsi-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    38952 11 30 22:41 libvirt-daemon-driver-storage-iscsi-direct-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    35020 11 30 22:41 libvirt-daemon-driver-storage-mpath-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    48772 11 30 22:41 libvirt-daemon-driver-storage-gluster-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    43076 11 30 22:41 libvirt-daemon-driver-storage-rbd-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751     6756 11 30 22:41 libvirt-daemon-driver-storage-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751   612932 11 30 22:41 libvirt-daemon-driver-qemu-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751     6540 11 30 22:41 libvirt-daemon-lxc-4.7.0-1.tis.101.x86_64.rpm

……

 

But “build-iso”  complains:

10:19:34 Could not resolve packages:  libvirt libvirt-client libvirt-daemon libvirt-daemon-config-network

 

It seems version conflicts with “libvirt.so”  and some “python2” upgrading to “python3” runtime dependency issues have not been resolved yet.

 

From: fuyong <fuyong@neusoft.com>
Sent: Tuesday, December 1, 2020 9:12 AM
To: Bai, Haiqing <Haiqing.Bai@windriver.com>; starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue

 

[Please note this e-mail is from an EXTERNAL e-mail address]

Hi Haiqing Bai

Has libvirt compiled successfully in your integ directory?
python3-ipaddr has no el8 version.

At present, you need to comment out the place where python3-ipaddr is dependent

B,R

Yong 

On 2020/11/30 上午10:26, Bai, Haiqing wrote:

Build-iso on f/centos8 branch has below runtime dependency list:

==============================================================

Warning: Infinite loop detected in dependency resolution.  See /localdisk/loadbuild/hbai/c81nststx/export/deps.txt for details -- exiting

These RPMS had problems (likely version conflicts)

        libvirt-daemon

        libvirt-daemon-driver-network

        libvirt.so.0()(64bit)

        libvirt.so.0(LIBVIRT_0.0.3)(64bit)

        libvirt.so.0(LIBVIRT_0.1.0)(64bit)

        libvirt.so.0(LIBVIRT_0.6.1)(64bit)

        libvirt.so.0(LIBVIRT_0.9.0)(64bit)

        libvirt.so.0(LIBVIRT_0.9.3)(64bit)

        libvirt.so.0(LIBVIRT_1.0.2)(64bit)

        libvirt.so.0(LIBVIRT_1.0.6)(64bit)

        libvirt.so.0(LIBVIRT_4.5.0)(64bit)

        libvirt.so.0(LIBVIRT_PRIVATE_4.7.0)(64bit)

        python3-ipaddr

        python3-ipaddress

        python-kubernetes

        python-pint

        PyYAML

        qemu-kvm-ev

 

I remembered the python3-ipaddr issue had been mentioned before by some guys,  anyone knows the latest status of that issue?  thanks

 

B,R

Haiqing Bai 




_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)
is intended only for the use of the intended recipient and may be confidential and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication
is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this communication in error,please
immediately notify the sender by return e-mail, and delete the original message and all copies from
your system. Thank you.
---------------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)
is intended only for the use of the intended recipient and may be confidential and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication
is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this communication in error,please
immediately notify the sender by return e-mail, and delete the original message and all copies from
your system. Thank you.
---------------------------------------------------------------------------------------------------