Bug 6675

Summary:	up2date can't be launched again if entered password field
Product:	[Retired] Red Hat Linux	Reporter:	terrychen
Component:	up2date	Assignee:	Preston Brown <pbrown>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.1
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-11-03 20:12:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description terrychen 1999-11-03 11:53:36 UTC

After upgrade to 1.0.5-1,(update package obtained from
ftp://priority.redhat.com/6.1/noarch/up2date-1.0.5-1.noarch.rpm),
if entered password field under Configure | User
Information, then up2date can't be launched again, although
all the operation during the first time seems ok.

The way to get around is don't input anything in the
password field (even the correct one, like I have), if it
can't be launched already, delete /etc/up2date.conf and
start all over again, better than re-install it.

Comment 1 Preston Brown 1999-11-03 14:36:59 UTC

We can't duplicate this in the lab.

Be aware that the user id and password field in the update agent
configuration have NOTHING to do with your username and password for
your system.  They are the userid and password from Red Hat's
registration system.

Also, the password you type when you start the update agent is the
ROOT password, not the password you entered into the configuration.

Comment 2 terrychen 1999-11-03 19:50:59 UTC

The things you mentioned I am already aware. These two user id and
password are two differnet sets, one for my system and one for RH's
registration system. And no matter I login as root or normal user, the
situations are the same.

I dig a little deep, it happened that my password for RH's
registration system are all numeric numbers (0 to 9) combination. If
there is at least one English alphabet within the password, then it
works just fine. But if all the character within password are numbers,
then it will produce the bug that I described.

Please try enter '111111' into the password field, and compare it with
'111x111', you should see the difference.

Comment 3 Preston Brown 1999-11-03 20:12:59 UTC

You are completely correct, I'm sorry I drew the wrong conclusion from
the initial report.

For now, the registration information isn't even being used; you can
use the update agent without entering it.  Simply erase your password.

We will issue an another version of the Update Agent ASAP that
corrects this problem (before it becomes an issue).

Comment 4 openshift-github-bot 2016-01-16 00:37:03 UTC

Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/097d34053dddad42283fbf8f1f5e82ec2cbdbc6c
Merge pull request #6679 from rhcarvalho/issue6675-dockerfile-in-bc

Merged by openshift-bot