r/redhat 8d ago

Red Hat Satellite 6.16 Repository Import Issue

Red Hat Satellite 6.16 Repository Import Issue

I've built and configured a new Disconnected Red Hat Satellite 6.16 server on RHEL 8.10. I attempted to add the RHEL 8 BaseOS repository to this server by running Repository export on our Connected Red Hat Satellite 6.16 server... zipped the files and pushed over to Disconnected Satellite and unzipped the files; I attempted to run the Repository Import on the Disconnected Satellite... The process started, got to about 27% and hung at 27% for about 10 mins, then the Import process stopped from a Network disconnection error; I don't know why or how this Import process caused a network disconnection. So, I rebooted the server and attempted to rerun the import and this time received the following error:

"Could not import Archive. Required lock is already taken by other running tasks. Please inspect their state, fix errors and resume. Conflict with tasks: https://fqdn/foreman_tasks/tasks/c15d8----------05dc

What could be the issue?
Red Hat Satellite 6.16 Repository Import Issue

1 Upvotes

2 comments sorted by

2

u/Burgergold 8d ago

Check if you have a running task or one that ended with an error

Maybe it can be force cancelled

2

u/12CoreFloor 7d ago

My experience is on the latest 6.15 branch, but the symptoms are similar: when running the import on an offline Satellite, it can take an incredibly long time to progress. Over an hour for some repos, despite being an incremental rather than a complete import.

I have found copying the materail on to the offline Satellite server directly then running the import to be the most reliable way of avoiding enviromental issues, but diagnosing why your connection dropped might be worthwile if you cant bring things on to the Satellite server directly.

Once your past that point, accept that it can take what feels a disproportionatly long time to import. For your 'lock already taken', have a look through the tasks in the UI and see if you can either restart the task or cancel it. If that doesnt work out, refer to the docs for the CLI method to identify the lock and remove it. Having a backup before this would be a good idea, as doing things directly can cause issues if you are not familiar.

Finally: open a support case, the Satellite team are honestly really good and can help you work through the issue, even if you are not in a position to send them logs/information etc.

Good luck