February 10, 2010
The issues included in this document were identified in Novell® ZENworks® 7.3 Linux Management with Interim Release 1 (IR1).
For installation instructions, see the Novell ZENworks 7.3 Linux Management Installation Guide.
For administration concepts and tasks, see the Novell ZENworks 7.3 Linux Management Administration Guide.
This product contains undocumented utilities that Novell Support might use to diagnose or correct problems.
The following table contains information on the documentation content changes that were made in this Readme after the initial release of ZENworks 7.3 Linux Management with IR1:
Table 1 Readme Updates
|
Date |
Readme Item Added or Updated |
|---|---|
|
January 22, 2010 |
Added the following known issue: ZENworks 7.3 Linux Management installation might fail on a device that has a default installation of SLES 10 SP3 (64-bit). |
|
February 10, 2010 |
Added the following knkown issue: Unable to manually upgrade from ZENworks 7.3 Linux Management or ZENworks 7.3 Linux Management with Hot Patch 1 to ZENworks 7.3 Linux Management with IR1 |
Some of the issues identified in the initial version of ZENworks Linux Management 7.3 have been resolved with this release. For a list of the resolved issues, see TID 7003346 in the Novell Support Knowledgebase.
This section contains information about the issues that might occur when you install and use ZENworks 7.3 Linux Management with IR1:
This section contains information about the issues that might occur when you install ZENworks 7.3 Linux Management with IR1.
The following incorrect error message is displayed on a SUSE® Linux Enterprise Server (SLES) 11 device while configuring the ZENworks Server:
Failed to activate service https://srm-test-srv.labs.blr.novell.com: []
Workaround: Ignore the message. However, you can confirm the ZENworks Service status of the device by using the rug sl command.
The ZENworks 7.3 Linux Management server or agent installation might fail on a device that has a default installation of SLES 10 SP3 64-bit because of unresolved dependencies.
Workaround: Before installing ZENworks 7.3 Linux Management with IR1 on a default installation of SLES 10 SP3 x86_64, manually install the libstdc++33-32-bit package on the device from the SLES 10 SP3 64-bit installation media.
Workaround 1: Download and install the gpg2 2.0.9-25.25.1or later package and the gpg2-lang 2.0.9-25.25.1or later package from Novell Update, then run the ZENworks 7.3 Linux Management installation.
Workaround 2: Install the ZENworks 7.3 Linux Management in one of the following ways. This might close any applications that are open.
Log in to the device in the init 3 mode by using the following command, then run the ZENworks Linux Management installation:
/sbin/init 3
Remotely log in to the device by using either RSH or SSH and run the ZENworks Linux Management installation.
This section contains information about the issues that might occur when you upgrade to ZENworks 7.3 Linux Management with IR1 from a previous release:
An online upgrade from SLES 10 to SLES 11 or from SUSE Linux Enterprise Desktop (SLED) 10 to SLED 11 is currently not supported by SUSE Linux Enterprise. Therefore, upgrading SLES 10 or SLED 10 by using ZENworks Linux Management to SLES 11 or SLED 11 is also not supported. To upgrade SLES 10 or SLED 10 that has ZENworks Linux Management installed to SLES 11 or SLED 11, see the TID 7002790 at Novell Support.
Workaround: Before upgrading to ZENworks 7.3 Linux Management, change the system language to either English, Spanish, or Portugal. For more information on how to upgrade to ZENworks 7.3 Linux Management, see Upgrading to ZENworks 7.3 Linux Management
in the Novell ZENworks 7.3 Linux Management Installation Guide.
When you try to manually upgrade a ZENworks 7.3 Linux Management or ZENworks 7.3 Linux Management with Hot Patch 1 server to ZENworks 7.3 Linux Management with IR1, the upgrade fails with the following error message if the server was originally upgraded from ZENworks 7.2 Linux Management:
IOError: [Errno 2] No such file or directory: '/etc/nds.conf'
The failure occurs because the default path of the eDirectory (8.8) configuration file, nds.conf, is changed from /etc to /etc/opt/novell/eDirectory/conf when you upgrade from ZENworks 7.2 Linux Management to ZENworks 7.3 Linux Management.
Workaround: Do the following on the ZENworks 7.3 Linux Management server:
Run the following content as a bash script:
/etc/init.d/ndsd stop
mv /etc/opt/novell/eDirectory/conf/nds.conf /etc
sed -i "s~/etc/opt/novell/eDirectory/conf~/etc~g" /etc/opt/novell/eDirectory/conf/.edir/instances.0
/etc/init.d/ndsd start
Run the ./zlm-upgrade command to manually upgrade to ZENworks 7.3 Linux Management with IR1.
The Event based schedule is not supported in ZENworks 7.3 Linux Management.
Workaround: After upgrading to ZENworks 7.3 Linux Management, manually change the schedule to or . For more information on how to edit the schedule, see Editing Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide.
This section contains information about the issues that might occur when you use the Package Management features of ZENworks Linux Management:
The use of wildcard characters using the bundle-list (bl) command to list bundles is not currently supported.
A few pattern, patch, and product rug commands are not supported on SLES 9, RHEL, and Novell Linux Desktop.
This might occur because the bundle is assigned to a device group and not directly to the device.
Workaround: None.
This section contains information about the issues that might occur when you use the Policy Management features of ZENworks Linux Management:
If you configure the SUSE Linux Enterprise Desktop policy for a SLED 10 managed device, you might encounter the following issues:
The option does not work.
If you try to remove an option that is selected in the drop-down list of the main menu file area, the main menu fails to appear. Also, if you try to unassign the policy from the managed device, the main menu still fails to appear.
Workaround: If the main menu fails to appear on unassigning the policy:
Ensure that the policy is removed from the device by refreshing the managed device and logging in to the device again.
On the managed device, right-click the panel, click , select from the list, then click .
On a SLED 10 managed device, if you unenforce the SLED policy in which the background image filename is configured, the previous background settings of the device are not restored.
Workaround: Log in to the managed device again.
If you enforce the SLED policy that is configured to remove the system menus from the system area, the system area on the SLED 10 SP1 managed device disappears.
Workaround: Remove the settings from the SLED policy and reassign the policy to the SLED 10 SP1 managed device.
This section contains information about the issues that might occur when you use the Imaging features of ZENworks Linux Management:
If you take an image of a server just after installing ZENworks Linux Management (that is, before zislnx-start has a chance to run again at boot), the image is restored with an incorrect network configuration and hostname.
Workaround: After completing the server installation, execute /etc/init.d/novell-zislnx start.
This issue does not affect installation of the ZENworks Agent on a managed device.
The Imaging engine does not support double-byte characters in image filenames. The ZENworks Control Center allows you to enter a double-byte character, but the Imaging Server does not recognize it. Therefore, do not use double-byte characters in the names of image files.
On Red Hat* Enterprise Linux 3 (RHEL 3) devices, using the /etc/init.d/novell-zislnx stop command fails to shut the service down. At some later time, the device then fails to respond to a soft reboot, and must be cold-booted.
The error message displayed when running /etc/init.d/novell-zislnx stop is incorrect, because RHEL 3 does not follow LSB standards.
Workaround: Do not use the /etc/init.d/novell-zislnx stop command. Normally, you would not run this command, because when /etc/init.d/novell-zislnx is run from either a bash prompt or at boot-up, it runs once then stops itself.
The use of a symbolic link is not supported in add-on images if the link’s location does not exist on the device where the add-on image is extracted.
The Dell utility partition relies on its version of the MBR (master boot record) to function correctly. Grub also uses the MBR for its boot loader. If you install the Dell utility partition, then install the Linux* operating system, the Dell version of the MBR is overwritten by the grub version. Instructions to remedy this problem are found in Creating Dell Configuration Bundles
in the Novell ZENworks 7.3 Linux Management Administration Guide.
However, the instructions do not work for Dell PE700 devices. For Dell PE700 devices, there is no workaround.
If you try boot a VMware* server from the CD or DVD, or a ZENworks partition, the preboot services fail with the following message:
Can't find ZEN install channel, invoking manual install
Workaround: Use a USB device to boot a VMware server.
This section contains information about the issues that might occur when you use the Inventory features of ZENworks Linux Management:
A hardware inventory currently does not report some items, such as power supply, for any type of device. For Red Hat machines, items such as floppy and monitor are not recognized.
On SLES 9, Novell Linux Desktop, and Open Enterprise Server managed devices, the hardware probe using the hwinfo utility might unload the lp module and consequently remove the printer device.
Workaround: Download and install the updates for the hwinfo utility. For detailed information on how to obtain the updates, see the Novell Support Web site.
The hardware Inventory Scanner fails to capture the network adapter information for managed devices on S390X hardware.
Workaround: None
If you create a CPU-based registration rule to filter Intel* Pentium* processors for registering the managed device to the server, the Inventory Scanner utility (hwinfo) captures the CPU model name as "Pentium(R) 4 processor 2800 MHz" instead of "Intel(R) Pentium(R) 4 CPU 2.80GHz" for some machines; the prefix Intel is omitted. Consequently, the registration of the device to the server might fail.
Workaround: None.
Workaround: None: The VMware system BIOS stores incorrect information about the processor family, which is retrieved by the hwinfo utility used in the ZENworks Linux Management hardware inventory.
This section contains information about the issues that might occur when you use the Remote Management features of ZENworks Linux Management:
When you start the Remote Login operation on a managed device, the launched session shows only a grey screen with an X cursor because XDMCP is not enabled on the managed device.
Workaround: On the managed device, do the following:
Manually enable XDMCP by executing the novell-rm-fixrl.sh script from a console session as mentioned below:
On SLES 10 and SLED 10: Execute /usr/bin/novell-rm-fixrl.sh -dm xdm -cf /etc/opt/gnome/xdm/xdm.conf enable.
On SLES 9 and Novell Linux Desktop: Execute /opt/novell/zenworks/bin/novell-rm-fixrl.sh -dm xdm -cf /etc/opt/gnome/xdm/xdm.conf enable.
On RHEL: Execute /opt/novell/zenworks/bin/novell-rm-fixrl.sh -dm gdm -cf /etc/X11/gdm/gdm.conf enable.
Start the Remote Login operation.
When starting a remote management session, the Remote Management -VNC applet randomly hangs.
Workaround: Stop and restart all running browser sessions, then retry the remote management session.
This section contains information about the issues that might occur when you use zen-installer, zen-remover, or zen-updater in ZENworks 7.3 Linux Management.
If you start zen-installer, zen-remover, and zen-updater from the command line on a RHEL5 64-bit managed device, it throws a traceback error with a mono-lib exception.
Workaround: On a RHEL5 64-bit managed device, do the following:
Edit /etc/selinux/config to set the value of SELINUX to disabled.
Reboot the device.
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
A trademark symbol (®, TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to http://www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2010 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.novell.com/company/legal/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.