[Pulp-list] pulp-2to3-migration tool problem 301 Moved Permanently

Wed Apr 28 19:10:16 UTC 2021

Hey Ben,

We also have docs on how to setup and run the migration should that help
you or make it easier for you rather than following the video.
Also docs are getting regularly updated with the recent changes, fixes ,etc
https://pulp-2to3-migration.readthedocs.io/en/latest/workflows.html

--------
Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."

On Wed, Apr 28, 2021 at 2:46 PM David Davis <daviddavis at redhat.com> wrote:

> Hi Ben,
>
> You're missing a slash.
>
>     http POST :/pulp/api/v3/migration-plans/ <MyPlan.json
>
> The 301 response is trying to redirect you to
> https://localhost/pulp/api/v3/migration-plans/.
>
> Also, we've since added support for the pulp-2to3-migration to our CLI
> which may be a bit easier to use than httpie.
>
> https://github.com/pulp/pulp-cli
>
> David
>
>
> On Wed, Apr 28, 2021 at 4:32 AM Ben Stanley <ben.stanley at gmail.com> wrote:
>
>> Hello Pulp People,
>>
>> I think I've finally got my pulp3 + plugins installed. I can access
>> http://localhost/pulp/api/v3/ and see the schema.
>>
>> Now I'm up to trying to migrate the content from my pulp2 server. I have
>> installed the pulp-2to3-migration plugin (note that the ansible
>> installation instructions didn't describe how to do it. I manually added
>> pulp-2to3-migration to the pulp_install.yml file).
>>
>> I'm following the instructions provided by Tanya Tereshchenko in the
>> video "Don't get stuck on Pulp 2!". I have created a simple plan for the
>> pulp-file plugin to import my ISO repos. I was confused where Tanya
>> starts using the http command. After quite a bit of searching I found
>> out that it is provided by the httpie package.
>>
>> So I tried the command
>>
>> http POST :/pulp/api/v3/migration-plans <MyPlan.json
>>
>> Tanya's video shows the response:
>>
>> ====================================
>> HTTP/1.1 201 Created
>> Access-Control-Expose-Headers: Correlation-ID
>> Allow: GET, POST, HEAD, OPTIONS
>> Connection: Keep-Alive
>> Content-Length: 705
>> Content-Type: application/json
>> Correlation-ID: 166793e08cee499eb20573cfcf7befb5
>> Date: Wed, 20 Jan 2021 13:22:32 GMT
>> Keep-Alive: timeout=5, max=10000
>> Location:
>> /pulp/api/v3/migration-plans/76aea09f-04a8-4ace-9188-1e5e579f76e0/
>> Server: gunicorn/20.0.4
>> Vary: Accept, Cookie
>> X-Frame-Options: SAMEORIGIN
>> ==========================================
>>
>> Unfortunately my response looks very different:
>>
>> =========================================
>> HTTP://1.1301 Moved Permanently
>> Connection: keep-alive
>> Content-Lenght: 169
>> Content-Type: text/html
>> Date: Wed, 28 Apr 2021 08:15:00 GMT
>> Location: https://localhost/pulp/api/v3/migration-plans/
>> Server: nginx/1.16.1
>>
>> <html>
>> <head><title>301 Moved Permanently</title></head>
>> <body>
>>
>> <center><h1>301 Moved Permanently</h1></center>
>> <hr><center>nginx/1.16.1</center>
>> </body>
>> </html>
>> ==========================================
>>
>> What have I done wrong?
>>
>> I can see that Tanya's system is running gunicorn web server, whereas in
>> my system the response is provided by nginx directly. Do I need to set
>> up another web server? At the moment I'm just running whatever ansible
>> set up for me.
>>
>> Ben.
>>
>>
>> _______________________________________________
>> Pulp-list mailing list
>> Pulp-list at redhat.com
>> https://listman.redhat.com/mailman/listinfo/pulp-list
>>
>> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20210428/3ee62b0b/attachment.htm>