-
Notifications
You must be signed in to change notification settings - Fork 77
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
Fixes endpoint discovery for RGW application under test #1217
Fixes endpoint discovery for RGW application under test #1217
Conversation
The zaza test used the default endpoint as exposed by the unit to perform object IO, however, SSL is configured for PUBLIC,INTERNAL, and ADMIN bindings. Signed-off-by: Utkarsh Bhatt <[email protected]>
3bcd3ff
to
21b51a4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This feels like there exists a bug in zaza_model.get_unit_public_address()
Seeing as there have been numerous issues with this method in the past I wonder if there has been a regression.
This method also has two different implementations, with a feature flag switching between them. I wonder if setting this feature flag helps?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FTR. after talking about this some more: This is not about getting the public address from the POV of juju but an address from the space named "public" -- this lgtm
@UtkarshBhatthere Please could you add some description into the PR about why this patch is needed; i.e does it fix a bug? Is it a regression being resolved? A workaround? i.e. we need something to explain why this should be included right up in the description of the PR. Thank. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hold until there is a description of the PR available.
@ajkavanagh Thanks for the reminder, I have added a description for the change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM; thanks for updating the description.
Charm-Ceph-RGW configures Apache for Admin/Public bindings. The original test queries the charm for the default public address (i.e. address on the "" binding) to perform object IO (S3) which fails because the endpoint is not correct. For IO test, we need to fetch the address bound to the
PUBLIC
juju space, this PR fetches the same withnetwork-get
and uses that to perform object IO instead.