This works mostly, but is failing on packages that look pretty important, like:
copy 'dbus-1-python-1.2.0-4.194.x86_64'
copy 'libcurl4-7.37.0-28.1.x86_64'
...
copy 'python-ipaddress-1.0.14-1.1.noarch'
Spawning worker 0 with 22 pkgs
Spawning worker 1 with 22 pkgs
Workers Finished
Saving Primary metadata
Saving file lists metadata
Saving other metadata
ERROR: package 'hwdata' not found
ERROR: package 'libnewt0_52' not found
...
ERROR: package 'salt' not found
ERROR: package 'salt-minion' not found
I’ve checked the reposync file for this pool and it looks like it’s definitely got the working ones, but is missing the ones I’m encountering ERRORS with (no big surprise, but a good check).
Just want to add that I have encountered the same exact situation. I built a system last week, encountered the problem and tried to figure it out, with no luck, then thought maybe a missed something in the install/config, so I completely blew away the VM, and started from scratch yesterday, followed instructions exactly, only to arrive at the same place again. Same missing packages you noted, about 26 in total, including a number of python packages and a few spacewalk packages.
Child Channel SLE-Manager-Tools12-Updates x86_64 SP2 (202 pkgs and 25
patches)
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.38-50-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Child Channel SLE-Manager-Tools12-Updates x86_64 SP2 (202 pkgs and 25
patches)
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.38-50-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]
Thanks for the quick response Malcolm. I’ve interpreted your instructions as:
Login to SUMA as an admin user
Switch to the “Channels” tab
Select “All Channels”
Use the filter “SLE-Manager” to search for the likes of “SLE-Manager-Tools12-*”
Sadly, in my case that comes up empty with “No Channels found” out of all of the channels that your organization has access to.
I guess I try and find out how to associate the SUMA trial license/rego for my organization instead of my scc login?
[QUOTE=drax;37095]Thanks for the quick response Malcolm. I’ve interpreted your instructions as:
Login to SUMA as an admin user
Switch to the “Channels” tab
Select “All Channels”
Use the filter “SLE-Manager” to search for the likes of “SLE-Manager-Tools12-*”
Sadly, in my case that comes up empty with “No Channels found” out of all of the channels that your organization has access to.
I guess I try and find out how to associate the SUMA trial license/rego for my organization instead of my scc login?[/QUOTE]
So I thought I’d check my organization has the SUMA Trial license associated with it:
Confirm your organization name is appearing in the top bar, well to the right of the “SUSE Customer Center” text
Under Management Tools, select Manually activate subscriptions
Select Activate a single subscription
Enter the registraton code you were given when you started the SUMA evaluation
Read and accept the terms and conditions
Hit the Manually Activate Subscription button
In my case the message "Subscription with registration code ‘xxxxxxxxxxx’ is already activated. So I’m set there…or not I guess lol.
I’ll try my luck with the local support team and see if I they can check to make sure the SUMA Evaluation Trial actually grants access to the following channels:
Ok, it looks as though my predecessors have created multiple Organizations with a variety of names and associated systems and licenses in past years with SCC.
As a result it looks like my SUMA Evaluation license is on one, and the credentials I used to register SUMA post-installation are on another.
Hopefully it doesn’t take too long to run through the cleanup/consolidation of these accounts into a single one. This seems a worthwhile time to do so as there’s an appetite for SUMA, but less so for cleanup (surprise). I daresay it will make life in future with SUSE an order of magnitude easier.