Bug 69574
Summary: | up2date --nox -p fails with traceback | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Fred New <fred.new2911> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED RAWHIDE | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | limbo | CC: | gafton, mihai.ibanescu, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-07-24 06:39:18 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: | |||
Bug Depends On: | |||
Bug Blocks: | 67217 |
Description
Fred New
2002-07-23 12:16:21 UTC
Looking at the code of rpcServer.py a little closer, I see that enableProxyAuth should be "No" if I'm not going to specify a proxyUser or a proxyPassword. In fact, I tried changing enableProxyAuth everything ran fine with the original rpcServer.py. I believe enableProxyAuth was already "Yes" when I first ran --configure, but I wouldn't rely on changing the initial value to fix this problem. I belive misa fixed in this about version 2.9.21 or so. Fix confirmed with up2date-3.0.2-2. |