<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hello Matthias, Regarding the software versions: [root@honeybee plans]# /usr/local/lib/pulp/bin/pip list Package Version ------------------------------------------------------- pulp-2to3-migration 0.11.0 pulpcore 3.12.0 pulp-cli 0.7.0 Looks like I could do some upgrading. I tried to upgrade the pulp.pulp_installer, but that bombed (see separate email). Regarding the cached api-spec, I ran pulp status. There is no mention of any api being outdated or refreshing (see attached output 20210505_pulp_status.txt I have also re-run the migration plan create with -vvv . The output is attached as 20210505_pulp_migration_create_vvv.txt . I hope it means more to you than it does to me. Ben Stanley. <div class="moz-cite-prefix">On 4/5/21 6:58 pm, Matthias Dellweg wrote: </div> <blockquote type="cite" cite="mid:CAG+ryNzgSG_DK2-nt2uSNbM0+S1x+gHb3nqeeogGoT9u0rtMZQ@mail.gmail.com"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <div dir="ltr"> <div>Hello again.</div> <div>The pulp cli is using requests to talk to your server. I seems like pointing the environment variable <code>REQUESTS_CA_BUNDLE</code> to the full path of a copy of the file you may find as '/etc/pulp/certs/root.crt' or '/etc/pulp/certs/ca.crt' tells requests to use the provided root certificate. </div> </div> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Tue, May 4, 2021 at 10:28 AM Matthias Dellweg <<a href="mailto:mdellweg@redhat.com" moz-do-not-send="true">mdellweg@redhat.com</a>> wrote: </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div dir="ltr"> <div>Hello Stan,</div> <div>thank you for reporting this. First of all, you are right about the `--plan`. Are you willing to send a PR for that mistake?</div> <div>Let me first ask you the typical support questions: Which version of the migration plugin and the CLI is this?</div> <div>The error looks to me like the CLI get's an unexpected answer from the server, and that can have multiple reasons.</div> <div>1. the cached api-spec of the CLI is outdated. Please run `pulp <...> status` and look for "Notice: Cached api is outdated. Refreshing...". After that, try again. </div> <div>2. the server does not reply in the way, it's api-spec promises</div> <div>3. something in the reverse proxy garbles the result</div> <div>Can you please try to rerun your command with `pulp -vvv --no-verify-ssl --username USERNAME ...` to add some debugging output. It will show you the requests sent to the server as well as the responses. I hope this can give some insight. </div> </div> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Tue, May 4, 2021 at 2:18 AM Ben Stanley <<a href="mailto:ben.stanley@gmail.com" target="_blank" moz-do-not-send="true">ben.stanley@gmail.com</a>> wrote: </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div> Hello pulp-list, I am attempting to migrate my pulp2 to pulp3. I seem to be facing difficulties at every step. After overcoming the initial difficulties of installation, I am now up to trying to migrate the data. Looking at the migration documentation: <a href="https://pulp-2to3-migration.readthedocs.io/en/latest/workflows.html" target="_blank" moz-do-not-send="true">https://pulp-2to3-migration.readthedocs.io/en/latest/workflows.html</a> I note that the command in the documentation is incorrect: [root@honeybee plans]# pulp --no-verify-ssl --username USERNAME --password PASSWORD migration plan create plan='{"plugins": [{"type": "iso"}]}' Usage: pulp migration plan create [OPTIONS] Try 'pulp migration plan create --help' for help. Error: Missing option '--plan'. [root@honeybee plans]# The documentation should be corrected to use --plan=<stuff> instead of plan=<stuff> . Even after I corrected the command to use --plan=<stuff>, I got a huge error message. root@honeybee plans]# pulp --no-verify-ssl --username USERNAME --password PASSWORD migration plan create --plan='{"plugins": [{"type": "iso"}]}' Traceback (most recent call last): File "/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/cli/common/openapi.py", line 219, in parse_response response_spec = method_spec["responses"][str(response.status_code)] KeyError: '200' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/bin/pulp", line 8, in <module> sys.exit(main()) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/click/core.py", line 829, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/click/core.py", line 782, in main rv = self.invoke(ctx) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/click/core.py", line 1259, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/click/core.py", line 1259, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/click/core.py", line 1259, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/click/core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/click/core.py", line 610, in invoke return callback(*args, **kwargs) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/click/decorators.py", line 73, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/click/core.py", line 610, in invoke return callback(*args, **kwargs) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/click/decorators.py", line 73, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/click/core.py", line 610, in invoke return callback(*args, **kwargs) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/cli/common/generic.py", line 287, in callback result = entity_ctx.create(body=body) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/cli/common/context.py", line 364, in create self.CREATE_ID, parameters=_parameters, body=body, non_blocking=non_blocking File "/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/cli/common/context.py", line 129, in call result = self.api.call(operation_id, *args, **kwargs) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/cli/common/openapi.py", line 284, in call return self.parse_response(method_spec, response) File "/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/cli/common/openapi.py", line 222, in parse_response response_spec = method_spec["responses"][str(100 * int(response.status_code / 100))] KeyError: '200' [root@honeybee plans]# What do I need to fix to proceed with my migration? And I'd also like to know how I can get it to work without having to specify --no-verify-ssl . Note that I have a self-signed certificate. I don't mind pointing the pulp command to the self-signed certificate file so that it will accept it, but I don't know how to do that. Thanks, Ben Stanley. </div> _______________________________________________ Pulp-list mailing list <a href="mailto:Pulp-list@redhat.com" target="_blank" moz-do-not-send="true">Pulp-list@redhat.com</a> <a href="https://listman.redhat.com/mailman/listinfo/pulp-list" rel="noreferrer" target="_blank" moz-do-not-send="true">https://listman.redhat.com/mailman/listinfo/pulp-list</a></blockquote> </div> </blockquote> </div> </blockquote> </body> </html>