-
Notifications
You must be signed in to change notification settings - Fork 24
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 1939: pulp domain integration #331
Conversation
bbb92b7
to
6bfa1b0
Compare
81cc49f
to
ee02487
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.
The domain is still created and no actual functionality is disrupted, but I'm consistently getting Error creating domain error="500 Internal Server Error" body="\n<!doctype html>\n<html lang=\"en\">\n<head>\n <title>Server Error (500)...
when using bulk create with a new orgID.
It seems like you handled the "creation at the same time" edge case. Are you still seeing this 500 error?
Note, i had an error in my example config .yaml changes for minio, thats now corrected. |
working to rebase |
e582d27
to
c05b407
Compare
this removes domain creation on create requests, as its not fully needed. Originally i thought this would make sense as the domain could be created before the snapshot task got underway. In reality its so fast that the race condition happens regardless
Hello with the default ephemeral user jdoe I created some repos with snapshots:
Notice in the above , the string ' I created a new user and bumped the org id and acc number by 1:
In the above: |
If you check the admin UI In this json,
2d18751c is the domain |
Summary
NOTE: Before merging, we need to set
DOMAIN_ENABLED: "true"
in the pulp deployment for ephemeral, within our app-inteface deploy.yaml:just add below IMAGE_TAG:
Testing steps
Use a bulk create with a different org:
List the snapshots for the repo and see that the new 'RepositoryPath' shows a domain (we still store the distribution path in the db, but thats not relevant to the user)
Also, do a bunch of bulk creates on a new org, verify that there are no errors.
Ephemeral testing:
reserve a namespace and deploy:
bonfire deploy content-sources --frontends=true
Once its up do a
namespace describe
to get the info and curl to create a repo (replacing with the correct info):Monitor the admin tasks, and verify that the task is created. You can curl the snapshots api to confirm the path:
for example, my output shows a repository_path of:
that first char set
bf7f7fae
is the domain name.you might also try bulk creation here
testing with local minion: