On martes, 16 de junio de 2020 16:19:01 (CEST) Thomas Weis wrote:
Am 16.06.2020 um 15:31 schrieb Julio González Gil <jgonzalez@suse.com>:
There are still two errors when creating the bootstrap repo for OES2018-SP2:
ERROR: package 'python2-uyuni-common-libs' not found ERROR: package 'python-singledispatch' not found
What client tools are you using for OES2018-SP2?
At the moment I cannot use client tools for OES2018-SP2. 2020.05 for reasons that cannot be explained to me, it does not allow me to add an existing repository to an existing channel. I choose the channel and add / remove a checkmark in an existing repo but even after "update repositories" it is not saved. Why this is so? no idea but before with 4.02 that was still possible. But I can report so much that since adding the client tools for SLE1X I only get the two errors mentioned. Previously, when if I tried to created the bootstrap repo for OES2018-SP3, many error messages related to phyton2-* appeared, these are now gone and only these two for the python2-uyuni-common-libs and python-singledispatch are left.
I see python2-uyuni-commons-libs at https://download.opensuse.org/ <https://download.opensuse.org/> repositories/systemsmanagement:/Uyuni:/Stable:/SLE12-Uyuni-Client-Tools/ SLE_12/x86_64/
see before, I´m not able to add a Repo to the existing OES2018-SP2 Channel
Please open a GitHub Issue and share a screenshot with the channel tree for OES2018-SP2 and a screenshot for the channel details for the channel where you can't add a repository. Also share the complete log of your call to mgr-create-bootstrap-repo (maybe you can also include `-d` for debug. Having something from the logs at /var/log/rhn/* could also help.
As for python-singledispatch, I will add it as well, not needed anymore as IIRC it's only for salt 3000 on python3 systems (and not ready yet), but doesn't hurt having it.
but here I'm not sure to what extent the current situation Suse / Microfocus plays a role
Regards Thomas
Am 16.06.2020 um 12:00 schrieb Julio González Gil <jgonzalez@suse.com>:
This seems to be a legitimate bug.
python-gudev is not part of the Uyuni client tools for SLE12, and on SLE12 this package is not distributed to customers, so that explains why it is failing for you.
This package was added so cloud instances can work as well, as it seems it was missing, but never added to the Uyuni client tools.
I am adding it now, and will go with the release of Uyuni 2020.06, hopefully today.
This is the only error you are getting, right?
On martes, 16 de junio de 2020 10:07:38 (CEST) Thomas Weis wrote:
I have no plan (yet) on how to create a channel overview other than a print screen. However, I have now added the SLE15 client tools manually and now I can create the bootstrap repo without errors using mgr-create-bootstrap-repo --flush For SLES12 SP5, however, this is not quite possible, I still get an error here: ERROR: package 'python-gudev' not found I added the SLES12 client tools but obviously something is still missing. Can anyone come across the right repo for this?
Thanks for the support to everyone!
Regards Thomas
Am 15.06.2020 um 20:18 schrieb Julio González Gil <jgonzalez@suse.com>:
Can you share the structure of your channels for SLE15SP1?
The Uyuni client tools should be a child of SLE15SP1 pool channel, as defined at https://github.com/uyuni-project/uyuni/blob/master/utils/spacewalk-com mo n -channels.ini#L1003 <https://github.com/uyuni-project/uyuni/blob/master/utils/spacewalk-co mm o <https://github.com/uyuni-project/uyuni/blob/master/utils/spacewalk-co m <https://github.com/uyuni-project/uyuni/blob/master/utils/spacewalk-c om> mo> n-channels.ini#L1003>
Is it your case?
How did you add the client tools to SLE15SP1? You can add them manually with the URL pointed by Christian as a child channel of SLE15SP1, or you can use `spacewalk-common-channels`. Then using `--with-custom-channels` will do the trick.
Reviewing the doc seems that it could be more clear, yes. For Uyuni users it should instruct them to use `spacewalk-common-channels` to add the client tools for all the supported operating systems. But as far I can see it doesn't really tell you that at https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/re gi <https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/ regi> s <https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/r e <https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/ re> gis> tration-overview.html <https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/r eg <https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/ reg> i <https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/r e <https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/ re> gi> stration-overview.html> and at https://www.uyuni-project.org/ <https://www.uyuni-project.org/> <https://www.uyuni-project.org/ <https://www.uyuni-project.org/>> <https://www.uyuni-project.org/ <https://www.uyuni-project.org/>> uyuni-docs/uyuni/client-configuration/bootstrap-repository.html (which is linked) talks about the Setup Wizard, that you need to use to sync SLE15SP1, but the client tools must come from `spacewalk-common-channels`.
Looks to me we need a bug for the doc.
On lunes, 15 de junio de 2020 19:23:57 (CEST) Thomas Weis wrote: > Julio, > > thank´s for Your Answer! > > I first installed OS Leap 15.1 and all updates. Then 2020.05 exactly > according to the documentation from uyuni-project.org > <http://uyuni-project.org/>. As a bloody newcomer > with 2020.05, we only had a working 4.02 before. The update to > 2020.01 > hadn't worked, probably my fault ... and that's why we installed > 2020.05 > from scratch. After the initial synchronization of our whole Suse > Subscriptions, we had the entries in the "Error generating bootstrap > repo" > message center First for OES2018 SP2, then for SLE-15-SP1. > > The command with which we wanted to create the bootstrap repository, > followed by the selection menu: > > # mgr-create-bootstrap-repo --with-custom-channels > > 1. OES2018-SP2-x86_64 > 2. SLE-12-SP5-x86_64 > 3. SLE-15-SP1-x86_64 > 4. centos-7-x86_64-uyuni > 5. centos-8-x86_64-uyuni > 6. openSUSE-Leap-15.1-x86_64 > 7. openSUSE-Leap-15.1-x86_64-uyuni > > Enter a number of a product label: > > I choose 3, then followed by: > > …... > Pool started (with 5 workers) > Pool finished > ERROR: package 'hwdata' not found > ERROR: package 'python3-hwdata' not found > ERROR: package 'python3-rhnlib' not found > ERROR: package 'spacewalk-check' not found > ERROR: package 'spacewalk-client-setup' not found > ERROR: package 'spacewalk-client-tools' not found > ERROR: package 'python3-spacewalk-check' not found > ERROR: package 'python3-spacewalk-client-setup' not found > ERROR: package 'python3-spacewalk-client-tools' not found > ERROR: package 'python3-uyuni-common-libs' not found > ERROR: none of 'mgr-daemon', 'spacewalksd' found > ERROR: package 'suseRegisterInfo' not found > ERROR: package 'python3-suseRegisterInfo' not found > ERROR: package 'zypp-plugin-spacewalk' not found > ERROR: package 'python3-zypp-plugin-spacewalk' not found > > Suggestions: > mgr-create-bootstrap-repo uses the locally synchronized versions of > files > from the Tools repository, and uses the locally synchronized pool > channel > for dependency resolution. > Both should be fully synced before running the > mgr-create-bootstrap-repo > script. > > > Also the same from: > > # mgr-create-bootstrap-repo --with-custom-channels > > 1. OES2018-SP2-x86_64 > 2. SLE-12-SP5-x86_64 > 3. SLE-15-SP1-x86_64 > 4. centos-7-x86_64-uyuni > 5. centos-8-x86_64-uyuni > 6. openSUSE-Leap-15.1-x86_64 > 7. openSUSE-Leap-15.1-x86_64-uyuni > > Enter a number of a product label: > > choose 1 (OES2018 SP2) > > > …... > Directory walk started > Directory walk done - 83 packages > Temporary output repo path: > /srv/www/htdocs/pub/repositories/sle/12/5/bootstrap.tmp/.repodata/ > Preparing sqlite DBs > Pool started (with 5 workers) > Pool finished > ERROR: package 'python2-uyuni-common-libs' not found > ERROR: package 'python-singledispatch' not found > > Suggestions: > mgr-create-bootstrap-repo uses the locally synchronized versions of > files > from the Tools repository, and uses the locally synchronized pool > channel > for dependency resolution. > Both should be fully synced before running the > mgr-create-bootstrap-repo > script. > > > > Sorry for my ignorance but I have no plan how to proceed outside of > the > documentation .. > > Thank you for your support! > > Regards > Thomas > >> Am 15.06.2020 um 17:04 schrieb Julio González Gil >> <jgonzalez@suse.com <mailto:jgonzalez@suse.com>>: >> >> If you are trying to use SLE15SP1, use the SLE15 repository as >> pointed >> by >> Christian. >> >> Also please share the command you are using to create the bootstrap >> repository, and maybe your channel structure for SLE15SP1. >> >> I'd say the problem is that either you don't have the repository >> (and >> channel) as a child of the SLE15SP1 channels, either you are not >> calling >> the bootstrap creator script with `--with-custom-channels`. >> >> On lunes, 15 de junio de 2020 16:20:33 (CEST) Thomas Weis wrote: >>> Hello Christian, >>> >>> Thank you for your answer >>> >>> local repo is available, but created with this URL: >>> >>> https://download.opensuse.org/repositories/systemsmanagement:/Uyuni >>> :/ >>> <https://download.opensuse.org/repositories/systemsmanagement:/Uyu >>> ni:/> St >>> ab >>> le: /openSUSE_Leap_15-Uyuni-Client-Tools/openSUSE_Leap_15.0/ >>> >>> @Pau >>> yes, SLES15 SP1 was fully synchronized >>> >>> >>> Regards >>> Thomas >>> >>>> Am 15.06.2020 um 15:31 schrieb Pau Garcia Quiles >>>> <pau.garcia@suse.com <mailto:pau.garcia@suse.com>>: >>>> >>>> Hello >>>> >>>> Has the SLE 15 SP1 product sync fully finished? >>>> >>>> >>>> From: Cristian Gherman >>>> Sent: Monday, June 15, 2020 10:37 AM >>>> To: Uyunii list >>>> Subject: Re: [uyuni-users] Fresh Install uyuni 2020.05 Error >>>> generating >>>> bootstrap repo >>>> >>>> Hello, >>>> >>>> You have a local repo of >>>> https://download.opensuse.org/repositories/systemsmanagement:/Uyun >>>> i: >>>> <https://download.opensuse.org/repositories/systemsmanagement:/Uy >>>> uni:> /S >>>> ta >>>> bl >>>> e:/SLE15-Uyuni-Client-Tools/ >>>> <https://download.opensuse.org/repositories/systemsmanagement:/Uyu >>>> ni >>>> <https://download.opensuse.org/repositories/systemsmanagement:/Uy >>>> uni>>>>>>>>>> >>>> :/ >>>> >>>> St >>>> a >>>> <https://download.opensuse.org/repositories/systemsmanagement:/Uyu >>>> ni >>>> <https://download.opensuse.org/repositories/systemsmanagement:/Uy >>>> uni>>>>>>>>>> >>>> :/ >>>> >>>> <https://download.opensuse.org/repositories/systemsmanagement:/Uyu >>>> n >>>> <https://download.opensuse.org/repositories/systemsmanagement:/Uy >>>> un> i:/> S >>>> <https://download.opensuse.org/repositories/systemsmanagement:/Uyu >>>> ni >>>> <https://download.opensuse.org/repositories/systemsmanagement:/Uy >>>> uni> >>>> >>>> <https://download.opensuse.org/repositories/systemsmanagement:/Uyu >>>> n >>>> <https://download.opensuse.org/repositories/systemsmanagement:/Uy >>>> un> i:> /S> ta> ble:/SLE15-Uyuni-Client-Tools/> ? >>>> >>>> >>>> Cristian Gherman >>>> Support / PHP developer >>>> >>>> >>>> cristian.gherman@reea.net <mailto:cristian.gherman@reea.net> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net>> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net>>> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net>> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net>>>> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net>> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net>>> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net>> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net> >>>> <mailto:cristian.gherman@reea.net >>>> <mailto:cristian.gherman@reea.net>>>>> | www.reea.net >>>> <http://www.reea.net/> <http://www.reea.net/ >>>> <http://www.reea.net/>> <http://www.reea.net/ >>>> <http://www.reea.net/> <http://www.reea.net/ >>>> <http://www.reea.net/>>> <http://www.reea.net/ >>>> <http://www.reea.net/> <http://www.reea.net/> >>>> <http://www.reea.net/ >>>> <http://www.reea.net/>>> <http://www.reea.net/ >>>> <http://www.reea.net/> <http://www.reea.net/>>>>>>>>> >>>> >>>> | +4 0365410942>>>> >>>> >>>> On 6/14/20 10:32 PM, Thomas Weis wrote: >>>>> Hello everyone >>>>> >>>>> we are configuring a fresh installation of Uyuni 2020.05 >>>>> After a successful reposync of SUSE Linux Enterprise Server 15 >>>>> SP1 >>>>> x86_64 we get an error message: >>>>> >>>>> Type: Creating Bootstrap Repository failed >>>>> Summary: Error generating bootstrap repo for: SLE-15-SP1-x86_64 >>>>> >>>>> show details said: >>>>> ERROR: package 'hwdata' not found ERROR: package 'python3-hwdata' >>>>> not >>>>> found ERROR: package 'python3-rhnlib' not found ERROR: package >>>>> 'spacewalk-check' not found ERROR: package >>>>> 'spacewalk-client-setup' >>>>> not >>>>> found ERROR: package 'spacewalk-client-tools' not found ERROR: >>>>> package >>>>> 'python3-spacewalk-check' not found ERROR: package >>>>> 'python3-spacewalk-client-setup' not found ERROR: package >>>>> 'python3-spacewalk-client-tools' not found ERROR: package >>>>> 'python3-uyuni-common-libs' not found ERROR: none of >>>>> 'mgr-daemon', >>>>> 'spacewalksd' found ERROR: package 'suseRegisterInfo' not found >>>>> ERROR: >>>>> package 'python3-suseRegisterInfo' not found ERROR: package >>>>> 'zypp-plugin-spacewalk' not found ERROR: package >>>>> 'python3-zypp-plugin-spacewalk' not found >>>>> >>>>> The installation was error-free, we proceeded exactly according >>>>> to >>>>> the >>>>> documentation. What is our mistake? >>>>> >>>>> thanks for suggestions >>>>> >>>>> Regards >>>>> Thomas-- >>>>> To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com