Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ecc2b6e7 kills module rhn_register in CentOS 6.4 #4069

Closed
mpontes opened this issue Sep 9, 2013 · 1 comment
Closed

ecc2b6e7 kills module rhn_register in CentOS 6.4 #4069

mpontes opened this issue Sep 9, 2013 · 1 comment
Labels
bug This issue/PR relates to a bug.

Comments

@mpontes
Copy link

mpontes commented Sep 9, 2013

Commit ecc2b6e kills module rhn_register in my system (CentOS 6.4). Just initialising the module throws Python into a 100% CPU loop. It seems that the issue here is that the class in question is inheriting from another one called Config that is present in /usr/share/rhn/up2date_client/config.py in my system, which contains both has_keyand __getitem__ implementations. Using the in syntax makes it use the __getitem__ implementation, which throws it into a loop.

  File "rhn_register", line 175, in get_option_default
    if 'key' in self:
  File "/usr/share/rhn/up2date_client/config.py", line 258, in __getitem__
    if self.stored.has_key(name):
  File "/usr/share/rhn/up2date_client/config.py", line 178, in has_key
    return self.dict.has_key(name)

The RHN client that installs this file is this RPM, in case you need the source to check what's going on.
@jimi-c jimi-c closed this as completed in b3c0e3e Sep 9, 2013
@jimi-c
Copy link
Member

jimi-c commented Sep 9, 2013

Went ahead and reverted this as it was a minor change, thanks for reporting it!

jimi-c pushed a commit that referenced this issue Dec 6, 2016
@ryansb @alikins
Stop sorting of termination_policies in ec2_asg (#4883)
2e1e356 
The AWS API requires that any termination policy list that includes
`Default` must end with Default. The attribute sorting caused any list
of attributes to be lexically sorted, so a list like
`["OldestLaunchConfiguration", "Default"]` would be changed to
`["Default", "OldestLaunchConfiguration"]` because default is earlier
alphabetically. This caused calls to fail with BotoServerError per #4069

This commit also adds proper tracebacks to all botoservererror fail_json
calls.

Closes #4069
@ansibot ansibot added bug This issue/PR relates to a bug. and removed bug_report labels Mar 6, 2018
@ansible ansible locked and limited conversation to collaborators Apr 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug This issue/PR relates to a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jimi-c @mpontes @ansibot