Failed to synchronize cache for repo 'AppStream', ignoring this repo.

Latest response

When upgrade from 7.9 to8, the following error occurs.

Message: Unable to install RHEL 8 userspace packages.
Summary:
Details: Command ['systemd-nspawn', '--register=no', '--quiet', '-D', '/var/lib/leapp/scratch/mounts/root_/system_overlay',
'--bind=/etc/hosts:/etc/hosts', '--setenv=LEAPP_NO_RHSM=1', '--setenv=LEAPP_EXPERIMENTAL=0',
'--setenv=LEAPP_COMMON_TOOLS=:/etc/leapp/repos.d/system_upgrade/el7toel8/tools',
'--setenv=LEAPP_COMMON_FILES=:/etc/leapp/repos.d/system_upgrade/el7toel8/files', '--setenv=LEAPP_ENABLE_REPOS=BaseOS,AppStream',
'--setenv=LEAPP_UNSUPPORTED=0', '--setenv=LEAPP_EXECUTION_ID=ffb16833-e6c3-494c-bbb5-72e566ed8952', '--setenv=LEAPP_HOSTNAME=BSV10850', 'dnf', 'install',
'-y', '--nogpgcheck', '--setopt=module_platform_id=platform:el8', '--setopt=keepcache=1',
'--releasever', u'8.4', '--installroot', '/el8target', '--disablerepo', '*', '--enablerepo', u'AppStream',
'--enablerepo', u'BaseOS', 'dnf', '--disableplugin', 'subscription-manager'] failed with exit code 1.
Stderr: Host and machine ids are equal (3d353a2a140642d9bd30cb6ae9fb9ef2): refusing to link journals
Failed to synchronize cache for repo 'AppStream', ignoring this repo.
Failed to synchronize cache for repo 'BaseOS', ignoring this repo.
Error: Unable to find a match: dnf

I using leapp and writing .repo file in "basefile=file:///".
Is this causing the error?

If this is the cause, could you please tell me how to solve it offline?

Responses

Hi Shoji Kuboyama (翔士 窪山),

The basefile=file:/// line should be:

baseurl=file:///

That explains the two ignore this repo messages.

The journal message, you want to take a look at this solution in progress

If the latter does not help, please open a support case

翔士 窪山, I fixed the type error in the hidden link

Success,

Jan Gerrit Kootstra

Thank you for pointing out the typographical error and commenting.

solution in progress didn't work. support case URL is 404 error.

See remark in the post above, I fixed the link to the support site.

I am sorry the Solution in Progress did not help you.