View Full Version : No Longer Symlink: "/etc/products.d/baseproduct"

21-Apr-2017, 16:08

I have a OpenSUSE 42.1 system that is registered with my SUSE Manager server and subscribed to 42.1 channels. To try and upgrade to 42.2, I did the following:

Subscribed the system to 42.2 base & child channels for updates and patches.
Ran `zypper dist-upgrade --no-recommends` to upgrade to the 42.2 level.
Verified that '/etc/os-release' now reports it's at 42.2.
Rebooted the system.
After rebooting, anytime I'd try to use `zypper` for anything, it would try to refresh the spacewalk service as usual, but would throw the following exception and bomb out:

Traceback (most recent call last):
File "/usr/lib/zypp/plugins/urlresolver/spacewalk", line 48, in RESOLVEURL self.doRESOLVEURL(headers, body)
File "/usr/lib/zypp/plugins/urlresolver/spacewalk", line 96, in doRESOLVEURL login_info = up2dateAuth.getLoginInfo(timeout=timeout)
File "/usr/share/rhn/up2date_client/up2dateAuth.py", line 246, in getLoginInfo login(timeout=timeout)
File "/usr/share/rhn/up2date_client/up2dateAuth.py", line 211, in login maybeUpdateVersion()
File "/usr/share/rhn/up2date_client/up2dateAuth.py", line 55, in maybeUpdateVersion systemVer = up2dateUtils.getVersion()
File "/usr/share/rhn/up2date_client/up2dateUtils.py", line 87, in getVersion os_release, version, release = _getOSVersionAndRelease()
File "/usr/share/rhn/up2date_client/up2dateUtils.py", line 54, in _getOSVersionAndRelease bp = os.path.abspath(os.path.join(os.path.dirname(basep roduct), os.readlink(baseproduct))) OSError: [Errno 22] Invalid argument: '/etc/products.d/baseproduct'

The problem is that somehow '/etc/products.d/baseproduct' is no longer a symlink to '/etc/products.d/openSUSE.prod', but a stand-alone file. This causes the 'os.readlink' in '/usr/share/rhn/up2date_client/up2dateUtils.py' (provided by 'rhn-client-tools' package) to throw an exception.

If you manually create the link, everything appears to start working with zypper.

That file was a symlink before the dist-upgrade, what I'm trying to find out is why it would become a stand-alone file, rather than a simple symlink to the 'openSUSE.prod' product file?

Any advice would be much appreciated. Please let me know if any further information can be provided to assist. I'll keep digging in the meantime.

Automatic Reply
26-Apr-2017, 05:30

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
- Open a service request: https://www.suse.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.suse.com)

Be sure to read the forum FAQ about what to expect in the way of responses:

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot..

Good luck!

Your SUSE Forums Team

27-Apr-2017, 07:24
I don't think this has anything to do with SUSE Manager except for providing the channels.