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.

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

Boto3 SSM describe_instance_patches #3642

Closed
sirpentagon opened this issue Mar 28, 2023 · 2 comments
Closed

Boto3 SSM describe_instance_patches #3642

sirpentagon opened this issue Mar 28, 2023 · 2 comments
Assignees
Labels
closed-for-staleness ec2 p3 This is a minor priority issue response-requested Waiting on additional information or feedback. ssm

Comments

@sirpentagon
Copy link

Describe the bug

describe_instance_patches api stopped working on boto3 version 1.26.100

RuntimeError: Unable to calculate correct timezone offset for "-62135596800.0"

Expected Behavior

Give list of patches installed

Current Behavior

Time error

Reproduction Steps

ssm_client = boto3.client("ssm")
resp = ssm_client.describe_instance_patches(InstanceId="i-123456789")
print(resp)

Possible Solution

No response

Additional Information/Context

No response

SDK version used

1.26.100

Environment details (OS name and version, etc.)

Amazon EC2

@sirpentagon sirpentagon added bug This issue is a confirmed bug. needs-triage This issue or PR still needs to be triaged. labels Mar 28, 2023
@aBurmeseDev aBurmeseDev self-assigned this Mar 29, 2023
@aBurmeseDev aBurmeseDev added investigating This issue is being investigated and/or work is in progress to resolve the issue. and removed needs-triage This issue or PR still needs to be triaged. labels Mar 29, 2023
@aBurmeseDev
Copy link
Contributor

Hi @sirpentagon - thanks for reaching out.
I attempted to reproduce this on the same version 1.26.100 but wasn't able to. Since you mentioned it stopped working on this version, was it working in previous version and when did you last update the version? Just from looking at the error, I'm not sure if that's entirely related to boto3 but we'd be happy to look more into it if you could provide your debug logs. You can retrieve the logs by adding boto3.set_stream_logger('') to your code.

@aBurmeseDev aBurmeseDev added response-requested Waiting on additional information or feedback. ec2 ssm p3 This is a minor priority issue and removed bug This issue is a confirmed bug. investigating This issue is being investigated and/or work is in progress to resolve the issue. labels Mar 29, 2023
@github-actions
Copy link

github-actions bot commented Apr 3, 2023

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Apr 3, 2023
@github-actions github-actions bot closed this as completed Apr 5, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-for-staleness ec2 p3 This is a minor priority issue response-requested Waiting on additional information or feedback. ssm
Projects
None yet
Development

No branches or pull requests

2 participants