Ah!

Thankfully, that worked for helping fix the issue that pulp-admin wouldn't
work.

Also, it meant that I could execute the instructions in the last post of
this thread to solver the "can't kill a promotion" problem:

https://groups.google.com/forum/#!topic/foreman-users/4p26hO1RDOU

Having said all that, I'm still having trouble deploying. Have deleted key,
LCE and CV. Will start again.

cheers
L.

------
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 10 February 2017 at 12:28, 'Jason Nance' via Foreman users <
[email protected]> wrote:

> That's set automagically during foreman-installer. :)
>
> J
>
>
> On Feb 9, 2017, at 6:02 PM, Lachlan Musicman <[email protected]> wrote:
>
> AH! No, I wasn't. Thank you - I don't remember setting that, but now I
> know.
>
> cheers
> L.
>
> ------
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 10 February 2017 at 10:08, 'Jason B. Nance' via Foreman users <
> [email protected]> wrote:
>
>> Are you using the user/pass from the "default_login" and
>> "default_password" in /etc/pulp/server.conf?
>>
>> j
>>
>>
>>
>> ------------------------------
>> *From: *"Lachlan Musicman" <[email protected]>
>> *To: *"Foreman Users" <[email protected]>
>> *Sent: *Thursday, February 9, 2017 4:58:03 PM
>> *Subject: *Re: [foreman-users] CV publishing errors
>>
>> /var/log/messages shows
>>
>> pulp.server.webservices.middleware.exception:INFO: Authentication with
>> username admin failed: invalid username or password
>>
>> cheers
>> L.
>>
>> ------
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 10 February 2017 at 09:42, Lachlan Musicman <[email protected]> wrote:
>>
>>> That didn't work either :/ same error.
>>>
>>>
>>> [root@vmpr-res-utils ~]# pulp-admin login -u admin -p admin
>>> The specified user does not have permission to execute the given command
>>>
>>>
>>> cheers
>>> L.
>>>
>>> ------
>>> The most dangerous phrase in the language is, "We've always done it this
>>> way."
>>>
>>> - Grace Hopper
>>>
>>> On 10 February 2017 at 09:39, Tom McKay <[email protected]> wrote:
>>>
>>>> Try including the -u admin -p admin on all the pulp-admin commands
>>>>
>>>> On Thu, Feb 9, 2017 at 5:30 PM, Lachlan Musicman <[email protected]>
>>>> wrote:
>>>>
>>>>> CentOS 7.3.1611, foreman 1.13.4, katello 3.2.2, pulp* 2.9.3,
>>>>>
>>>>> When I try to publish a CV, I get this error
>>>>>
>>>>>
>>>>> Actions::Pulp::Repository::CopyYumMetadataFile
>>>>>
>>>>>
>>>>> {"source_pulp_id"=>
>>>>>   "Peter_MacCallum_Cancer_Centre-GAFFA-2_0-_sssd-Copr_reposito
>>>>> ry_for_sssd_1_15",
>>>>>  "target_pulp_id"=>
>>>>>   "Peter_MacCallum_Cancer_Centre-Gaffa-dev-GAFFA-_sssd-Copr_
>>>>> repository_for_sssd_1_15",
>>>>>  "clauses"=>nil,
>>>>>  "remote_user"=>"admin",
>>>>>  "remote_cp_user"=>"admin"}
>>>>>
>>>>> {"pulp_tasks"=>
>>>>>   [{"exception"=>nil,
>>>>>     "task_type"=>
>>>>>      "pulp.server.managers.repo.unit_association.associate_from_repo",
>>>>>     "_href"=>"/pulp/api/v2/tasks/39286b9b-7684-4b1c-b092-bc593d4
>>>>> ca46d/",
>>>>>     "task_id"=>"39286b9b-7684-4b1c-b092-bc593d4ca46d",
>>>>>     "tags"=>
>>>>>      ["pulp:repository:Peter_MacCallum_Cancer_Centre-Gaffa-dev-
>>>>> GAFFA-_sssd-Copr_repository_for_sssd_1_15",
>>>>>       "pulp:repository:Peter_MacCallum_Cancer_Centre-GAFFA-2_0-_
>>>>> sssd-Copr_repository_for_sssd_1_15",
>>>>>       "pulp:action:associate"],
>>>>>     "finish_time"=>"2017-02-09T21:29:59Z",
>>>>>     "_ns"=>"task_status",
>>>>>     "start_time"=>"2017-02-09T21:29:59Z",
>>>>>     "traceback"=>
>>>>>      "Traceback (most recent call last):\n  File
>>>>> \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 240,
>>>>> in trace_task\n    R = retval = fun(*args, **kwargs)\n  File
>>>>> \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line
>>>>> 484, in __call__\n    return super(Task, self).__call__(*args, **kwargs)\n
>>>>>  File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\",
>>>>> line 103, in __call__\n    return super(PulpTask, self).__call__(*args,
>>>>> **kwargs)\n  File 
>>>>> \"/usr/lib/python2.7/site-packages/celery/app/trace.py\",
>>>>> line 437, in __protected_call__\n    return self.run(*args, **kwargs)\n
>>>>>  File 
>>>>> \"/usr/lib/python2.7/site-packages/pulp/server/managers/repo/unit_association.py\",
>>>>> line 273, in associate_from_repo\n    units=transfer_units)\n  File
>>>>> \"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/importer.py\",
>>>>> line 58, in import_units\n    return associate.associate(source_repo,
>>>>> dest_repo, import_conduit, config, units)\n  File
>>>>> \"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/associate.py\",
>>>>> line 53, in associate\n    associated_units = 
>>>>> set([_associate_unit(dest_repo,
>>>>> unit) for unit in units])\n  File \"/usr/lib/python2.7/site-pack
>>>>> ages/pulp_rpm/plugins/importers/yum/associate.py\", line 339, in
>>>>> _associate_unit\n    return associate_copy_for_repo(unit, dest_repo,
>>>>> True)\n  File \"/usr/lib/python2.7/site-pack
>>>>> ages/pulp_rpm/plugins/importers/yum/associate.py\", line 379, in
>>>>> associate_copy_for_repo\n    
>>>>> new_unit.safe_import_content(unit._storage_path)\n
>>>>>  File 
>>>>> \"/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py\",
>>>>> line 905, in safe_import_content\n    self.import_content(path, 
>>>>> location)\n
>>>>>  File 
>>>>> \"/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py\",
>>>>> line 879, in import_content\n    storage.put(self, path, location)\n  File
>>>>> \"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\",
>>>>> line 123, in put\n    mkdir(os.path.dirname(destination))\n  File
>>>>> \"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\",
>>>>> line 20, in mkdir\n    os.makedirs(path)\n  File
>>>>> \"/usr/lib64/python2.7/os.py\", line 157, in makedirs\n
>>>>>  mkdir(name, mode)\nPulpExecutionException: Pulp exception occurred:
>>>>> PulpExecutionException\n",
>>>>>     "spawned_tasks"=>[],
>>>>>     "progress_report"=>{},
>>>>>     "queue"=>
>>>>>      "[email protected]
>>>>> g.au.dq",
>>>>>     "state"=>"error",
>>>>>     "worker_name"=>
>>>>>      "[email protected]",
>>>>>     "result"=>nil,
>>>>>     "error"=>
>>>>>      {"code"=>"PLP0000",
>>>>>       "data"=>{},
>>>>>       "description"=>"Pulp exception occurred: PulpExecutionException",
>>>>>       "sub_errors"=>[]},
>>>>>     "_id"=>{"$oid"=>"589cdf577fc653305c394bd2"},
>>>>>     "id"=>"589cdf577fc653305c394bd2"}]}
>>>>>
>>>>>
>>>>>
>>>>> Katello::Errors::PulpError: PLP0000: Pulp exception occurred:
>>>>> PulpExecutionException
>>>>>
>>>>>
>>>>> When I searched I found this:
>>>>>
>>>>> http://projects.theforeman.org/issues/16236
>>>>>
>>>>> When I tried the advised
>>>>>
>>>>> pulp-admin rpm repo content metafile --repo-id PULP_ID
>>>>>
>>>>> I got this error:
>>>>>
>>>>> The specified user does not have permission to execute the given
>>>>> command
>>>>>
>>>>> Which I googled, and found the suggestion:
>>>>>
>>>>> pulp-admin login -u admin -p password
>>>>>
>>>>> But I get the same error:
>>>>>
>>>>> The specified user does not have permission to execute the given
>>>>> command
>>>>>
>>>>>
>>>>> This same solution was also suggested here:
>>>>>
>>>>> https://groups.google.com/forum/#!topic/foreman-users/4p26hO1RDOU
>>>>>
>>>>> but since I can't get pulp-admin working.....
>>>>>
>>>>> What do I do next?
>>>>>
>>>>>
>>>>> Also - and this might be one for the wish list - I can't cancel the
>>>>> action and publish a new version of the CV with a different repo - it just
>>>>> says "promoting to a new environment" with the % bar and no cancel button?
>>>>>
>>>>> cheers
>>>>>
>>>>> L.
>>>>>
>>>>> ------
>>>>> The most dangerous phrase in the language is, "We've always done it
>>>>> this way."
>>>>>
>>>>> - Grace Hopper
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Foreman users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to [email protected].
>>>>> To post to this group, send email to [email protected].
>>>>> Visit this group at https://groups.google.com/group/foreman-users.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Foreman users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To post to this group, send email to [email protected].
>>>> Visit this group at https://groups.google.com/group/foreman-users.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to