Correction ..."accordingly reads the nodeinit.conf.node_type file".
---
** [tickets:#281] OSAF: RPM upgrade creates wrong nodeinit.conf on payloads**
**Status:** fixed
**Created:** Mon May 20, 2013 02:54 PM UTC by Anders Widell
**Last Updated:** Thu Jun 27, 2013 08:26 AM UTC
**Owner:** nobody
The symbolic link nodeinit.conf is created by the postinistall scripts to point
to the correct file (either nodeinit.conf.controller or nodeinit.conf.payload).
An RPM installation will create the link, and an RPM uninstallation will remove
the link. An RPM upgrade does not toch the link.
The problem is that the symbolic link nodeinit.conf is also listed in the
%files section of the opensaf RPM. This means that when the RPM is upgraded,
the nodeinit.conf created by the postinstall script will be overwritten to
always point to nodeinit.conf.controller, on both controller and payload nodes.
The solution is to remove the symbolic link from the %files section.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
