[Pulp-list] pulp-2to3-migration tool problem 301 Moved Permanently
ben.stanley at gmail.com
Thu Apr 29 08:26:36 UTC 2021
Thanks to those who wrote back explaining to add the trailing slash
(including those who replied off-list).
Unfortunately, I get the same response with and without the trailing slash.
It seems I've managed to stuff it up somehow. Any other ideas on things
I have also installed pulp-cli, but I haven't got that to work yet
either (see separate email).
On 28/4/21 10:41 pm, David Davis 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
> 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 <https://github.com/pulp/pulp-cli>
> On Wed, Apr 28, 2021 at 4:32 AM Ben Stanley <ben.stanley at gmail.com
> <mailto: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/ <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
> 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
> Server: gunicorn/20.0.4
> Vary: Accept, Cookie
> X-Frame-Options: SAMEORIGIN
> Unfortunately my response looks very different:
> HTTP://1.1301 <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
> <head><title>301 Moved Permanently</title></head>
> <center><h1>301 Moved Permanently</h1></center>
> 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
> up another web server? At the moment I'm just running whatever
> set up for me.
> Pulp-list mailing list
> Pulp-list at redhat.com <mailto:Pulp-list at redhat.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-list