Bug 2185587 - S3-related errors during Glance initialization
Summary: S3-related errors during Glance initialization
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-glance
Version: 17.1 (Wallaby)
Hardware: All
OS: All
medium
medium
Target Milestone: z2
: 17.1
Assignee: Cyril Roelandt
QA Contact: msava
Andy Stillman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-10 12:13 UTC by Alex Stupnikov
Modified: 2023-08-03 16:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-25 15:48:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 2007924 0 None None None 2023-04-10 13:59:19 UTC
Red Hat Issue Tracker OSP-24073 0 None None None 2023-04-10 12:13:46 UTC
Red Hat Knowledge Base (Solution) 7006942 0 None None None 2023-04-10 15:08:42 UTC

Comment 1 Takashi Kajinami 2023-04-10 13:59:20 UTC 
I think this is the problem I discussed with Abhishek a while ago and at that time we concluded the error is "cosmetic" because glance_store ignores the error.
We later fixed it by https://review.opendev.org/c/openstack/glance_store/+/874534 but I'm not too sure whether it's worth fixing in OSP17
by paying effort to backport this to multiple branches.
Comment 3 Alex Stupnikov 2023-04-10 15:02:40 UTC 
Error:

2023-03-30 13:35:50.098 2 ERROR stevedore.extension [-] Could not load 'glance.store.s3.Store': No module named 'boto3': ModuleNotFoundError: No module named 'boto3'
2023-03-30 13:35:50.110 2 ERROR stevedore.extension [-] Could not load 's3': No module named 'boto3': ModuleNotFoundError: No module named 'boto3'
Comment 6 Cyril Roelandt 2023-04-25 13:21:05 UTC 
This is indeed fixed with 7dc94f7a85e976a9c66f997f944c6ede06d7984a . This will end up in RHOSP at some point, but it is not worth a specific downstream backport.
Comment 9 Cyril Roelandt 2023-07-25 15:48:16 UTC 
These errors look scary, but they do not cause any crash/bug, so I think it's not worth backporting. I'll close this bug, feel free to reopen if you think otherwise.
Note You need to log in before you can comment on or make changes to this bug.