Bug 49927

Summary: Powerchute plus on non-local server malfunctioning
Product: [Retired] Red Hat Linux Reporter: Wendy Hung <wendyh>
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED NOTABUG QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: rlandry
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-07-25 14:04:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Wendy Hung 2001-07-25 14:04:00 UTC
Description of Problem:
Powerchute plus 4.5.2 and 4.5.3 program only finds server on first try and is very slow. 
Once the server (local server) is found, it prompts for a password. 
It will not accept the correct password and displays  "Invalid password" message. 
If you cancel and shutdown the powerchute user interface, you must  reboot in order to find the server again.

How Reproducible:
Every time.

Steps to Reproduce:
1. Install RH 7.1
2. Apply kernel errata 2.4.3-12smp
3. Install powerchuteplus-4.5.2-1.i386.rpm and pc.452_glibc.tar.
4. encrypted password from the /etc/shadow file was copied to the /etc/password as instructed in:
http://sturgeon.apcc.com/kbasewb2.nsf/For+External/28D83623D5DA67DE85256774005B2E68?OpenDocument

Actual Results:
To work around issues, TCP/IP networking  is turned off; limiting Powerchute plus to local servers. 

Expected Results:
Powerchute can be configured to work with non-local servers and password entry is successful.

Additional Information:
This has been reproduced on Red Hat Linux 6.2, 7.0, and 7.1 with Powerchute 4.5.2 and 4.5.3.

Same bug with PowerChute Plus 4.5.3 for RH 7.0 that is available on: http://www.apcc.com/tools/download.
There is no mention of RH 7.1 on APC's website.

Comment 1 Jeff Johnson 2001-07-25 19:54:29 UTC
I have no idea why this bug is filed against rpm. Please reopen and change
the component to something meaningful.