Re: [foreman-users] Content View with status "Deletion from Library"

2017-02-09 Thread Lachlan Musicman 
Ok - that completed successfully, but the CV remains. Hm.

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

- Grace Hopper

On 10 February 2017 at 15:25, 'Jason Nance' via Foreman users <
foreman-users@googlegroups.com> wrote:

> It probably would have helped had I said --upgrade. :-/
>
>
>
> On Feb 9, 2017, at 10:20 PM, Lachlan Musicman  wrote:
>
> oooh. Big new world. Sorry, I mostly use the Katello/Foreman web gui. I'm
> just slowly coming to grips with the whole system. That's the command that
> I ran a couple of weeks ago when I updated.
>
> I'll run it 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 15:16, Lachlan Musicman  wrote:
>
>> Great - one question, what is ?
>>
>>
>> --
>> The most dangerous phrase in the language is, "We've always done it this
>> way."
>>
>> - Grace Hopper
>>
>> On 10 February 2017 at 15:11, 'Jason Nance' via Foreman users <
>> foreman-users@googlegroups.com> wrote:
>>
>>> Running the reindex rake may help. Running foreman-installer >> flag> upgrade fixes weirdness for me sometimes as well.
>>>
>>> These are just shots in the dark. I haven't seen this particular issue.
>>>
>>> J
>>>
>>>
>>> On Feb 9, 2017, at 10:04 PM, Lachlan Musicman  wrote:
>>>
>>> Foreman 1.13, Katello 3.2, Centos 7.3
>>>
>>> I tried to delete a CV, but it didn't want to delete. I tried numerous
>>> times.
>>>
>>> It finally seemed to work - but it remains in the list of CVs and when I
>>> select it, I can see it's status says Deletion from Library (2017-02-10
>>> 13:39:50 +1100) (which is 1.5 hrs ago).
>>>
>>> I get pulp timeouts on other actions, have restarted qpidd and all
>>> pulp-* are running.
>>>
>>> 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 foreman-users+unsubscr...@googlegroups.com.
>>> To post to this group, send email to foreman-users@googlegroups.com.
>>> 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 foreman-users+unsubscr...@googlegroups.com.
>>> To post to this group, send email to foreman-users@googlegroups.com.
>>> 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 foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> 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 foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> 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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Content View with status "Deletion from Library"

2017-02-09 Thread 'Jason Nance' via Foreman users 
It probably would have helped had I said --upgrade. :-/



> On Feb 9, 2017, at 10:20 PM, Lachlan Musicman  wrote:
> 
> oooh. Big new world. Sorry, I mostly use the Katello/Foreman web gui. I'm 
> just slowly coming to grips with the whole system. That's the command that I 
> ran a couple of weeks ago when I updated.
> 
> I'll run it 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 15:16, Lachlan Musicman  wrote:
>> Great - one question, what is ?
>> 
>> 
>> --
>> The most dangerous phrase in the language is, "We've always done it this 
>> way."
>> 
>> - Grace Hopper
>> 
>>> On 10 February 2017 at 15:11, 'Jason Nance' via Foreman users 
>>>  wrote:
>>> Running the reindex rake may help. Running foreman-installer >> flag> upgrade fixes weirdness for me sometimes as well.
>>> 
>>> These are just shots in the dark. I haven't seen this particular issue.
>>> 
>>> J
>>> 
>>> 
 On Feb 9, 2017, at 10:04 PM, Lachlan Musicman  wrote:
 
 Foreman 1.13, Katello 3.2, Centos 7.3
 
 I tried to delete a CV, but it didn't want to delete. I tried numerous 
 times.
 
 It finally seemed to work - but it remains in the list of CVs and when I 
 select it, I can see it's status says Deletion from Library (2017-02-10 
 13:39:50 +1100) (which is 1.5 hrs ago).
 
 I get pulp timeouts on other actions, have restarted qpidd and all pulp-* 
 are running.
 
 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 foreman-users+unsubscr...@googlegroups.com.
 To post to this group, send email to foreman-users@googlegroups.com.
 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 foreman-users+unsubscr...@googlegroups.com.
>>> To post to this group, send email to foreman-users@googlegroups.com.
>>> 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 foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> 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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Content View with status "Deletion from Library"

2017-02-09 Thread Lachlan Musicman 
oooh. Big new world. Sorry, I mostly use the Katello/Foreman web gui. I'm
just slowly coming to grips with the whole system. That's the command that
I ran a couple of weeks ago when I updated.

I'll run it 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 15:16, Lachlan Musicman  wrote:

> Great - one question, what is ?
>
>
> --
> The most dangerous phrase in the language is, "We've always done it this
> way."
>
> - Grace Hopper
>
> On 10 February 2017 at 15:11, 'Jason Nance' via Foreman users <
> foreman-users@googlegroups.com> wrote:
>
>> Running the reindex rake may help. Running foreman-installer > flag> upgrade fixes weirdness for me sometimes as well.
>>
>> These are just shots in the dark. I haven't seen this particular issue.
>>
>> J
>>
>>
>> On Feb 9, 2017, at 10:04 PM, Lachlan Musicman  wrote:
>>
>> Foreman 1.13, Katello 3.2, Centos 7.3
>>
>> I tried to delete a CV, but it didn't want to delete. I tried numerous
>> times.
>>
>> It finally seemed to work - but it remains in the list of CVs and when I
>> select it, I can see it's status says Deletion from Library (2017-02-10
>> 13:39:50 +1100) (which is 1.5 hrs ago).
>>
>> I get pulp timeouts on other actions, have restarted qpidd and all pulp-*
>> are running.
>>
>> 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 foreman-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> 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 foreman-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> 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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Content View with status "Deletion from Library"

2017-02-09 Thread Lachlan Musicman 
Great - one question, what is ?


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

- Grace Hopper

On 10 February 2017 at 15:11, 'Jason Nance' via Foreman users <
foreman-users@googlegroups.com> wrote:

> Running the reindex rake may help. Running foreman-installer  flag> upgrade fixes weirdness for me sometimes as well.
>
> These are just shots in the dark. I haven't seen this particular issue.
>
> J
>
>
> On Feb 9, 2017, at 10:04 PM, Lachlan Musicman  wrote:
>
> Foreman 1.13, Katello 3.2, Centos 7.3
>
> I tried to delete a CV, but it didn't want to delete. I tried numerous
> times.
>
> It finally seemed to work - but it remains in the list of CVs and when I
> select it, I can see it's status says Deletion from Library (2017-02-10
> 13:39:50 +1100) (which is 1.5 hrs ago).
>
> I get pulp timeouts on other actions, have restarted qpidd and all pulp-*
> are running.
>
> 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 foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> 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 foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> 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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Content View with status "Deletion from Library"

2017-02-09 Thread 'Jason Nance' via Foreman users 
Running the reindex rake may help. Running foreman-installer  
upgrade fixes weirdness for me sometimes as well.

These are just shots in the dark. I haven't seen this particular issue.

J


> On Feb 9, 2017, at 10:04 PM, Lachlan Musicman  wrote:
> 
> Foreman 1.13, Katello 3.2, Centos 7.3
> 
> I tried to delete a CV, but it didn't want to delete. I tried numerous times.
> 
> It finally seemed to work - but it remains in the list of CVs and when I 
> select it, I can see it's status says Deletion from Library (2017-02-10 
> 13:39:50 +1100) (which is 1.5 hrs ago).
> 
> I get pulp timeouts on other actions, have restarted qpidd and all pulp-* are 
> running.
> 
> 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 foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> 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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: can not download the RHEL repos

2017-02-09 Thread sinux shen 
The product I was trying to sync was "Red Hat Enterprise Linux 6 Server 
RPMs x86_64 6Server" which is one of the repos from RHEL6 product, it 
always ended up with "No New Packages", but when I was syncing another repo 
"Red Hat Enterprise Linux 6 Server - Optional RPMs x86_64 6Server", I can 
sync all the contents though.

On Friday, February 10, 2017 at 11:26:28 AM UTC+8, sinux shen wrote:
>
> Hey there,
>
> I have exported and uploaded the RHEL subscriptions to foreman and make it 
> as an 3rd party SAM, now I can see all the RHEL products, I have done this 
> before by using our previous RHEL subscriptions and can download RHEL 
> 6server repos successfully, after our subscription expire, (I would say, I 
> didn't refresh the subscriptions in Katello/foreman), I deleted these RHEL 
> 6server repos by unchecking them from "RedHat repositories" menu, and now, 
> after I refreshed our subscription, I want to enable these repos again, but 
> after I enabled them, I cannot sync/download them, it returned with "no new 
> packages", is there anything wrong with the settings? Where I can check the 
> log?
>
> Any help is appreciated.
>
> Thanks
> -Sinux
>

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] can not download the RHEL repos

2017-02-09 Thread sinux shen 
Hey there,

I have exported and uploaded the RHEL subscriptions to foreman and make it 
as an 3rd party SAM, now I can see all the RHEL products, I have done this 
before by using our previous RHEL subscriptions and can download RHEL 
6server repos successfully, after our subscription expire, (I would say, I 
didn't refresh the subscriptions in Katello/foreman), I deleted these RHEL 
6server repos by unchecking them from "RedHat repositories" menu, and now, 
after I refreshed our subscription, I want to enable these repos again, but 
after I enabled them, I cannot sync/download them, it returned with "no new 
packages", is there anything wrong with the settings? Where I can check the 
log?

Any help is appreciated.

Thanks
-Sinux

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: upgrading puppet

2017-02-09 Thread Lachlan Musicman 
Ignore - I found the repo. The product it belonged to was added to the CV,
but tt was not added to the CV.

cheers
L.

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

- Grace Hopper

On 10 February 2017 at 13:56, Lachlan Musicman  wrote:

> Foreman 1.13, katello 3.2
>
> We are self hosted.
>
> Following the instructions here:
>
> https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html
>
> When I did this it told me I didn't have the puppet 4 repos in place.
>
> I look at the repos, and I can't see puppet 4 anywhere.
>
> Here http://yum.puppetlabs.com/el/7/products/x86_64/
>
> I can see puppet up to 3.8.7
>
> http://yum.puppetlabs.com/el/7/PC1/x86_64
>
> doesn't have a package in it call puppet?
>
> Is there a package called puppet 4 or does the long list of changes listed
> here
> https://docs.puppet.com/puppet/4.0/release_notes.html
> have a hidden line that says "we have moved from calling it puppet 4 to
> puppet-x?
>
> 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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] upgrading puppet

2017-02-09 Thread Lachlan Musicman 
Foreman 1.13, katello 3.2

We are self hosted.

Following the instructions here:

https://www.theforeman.org/plugins/katello/3.2/upgrade/puppet.html

When I did this it told me I didn't have the puppet 4 repos in place.

I look at the repos, and I can't see puppet 4 anywhere.

Here http://yum.puppetlabs.com/el/7/products/x86_64/

I can see puppet up to 3.8.7

http://yum.puppetlabs.com/el/7/PC1/x86_64

doesn't have a package in it call puppet?

Is there a package called puppet 4 or does the long list of changes listed
here
https://docs.puppet.com/puppet/4.0/release_notes.html
have a hidden line that says "we have moved from calling it puppet 4 to
puppet-x?

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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] CV publishing errors

2017-02-09 Thread Lachlan Musicman 
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 <
foreman-users@googlegroups.com> wrote:

> That's set automagically during foreman-installer. :)
>
> J
>
>
> On Feb 9, 2017, at 6:02 PM, Lachlan Musicman  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 <
> foreman-users@googlegroups.com> wrote:
>
>> Are you using the user/pass from the "default_login" and
>> "default_password" in /etc/pulp/server.conf?
>>
>> j
>>
>>
>>
>> --
>> *From: *"Lachlan Musicman" 
>> *To: *"Foreman Users" 
>> *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  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  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 
 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\nR = retval = fun(*args, **kwargs)\n  File
> \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line
> 484, in __call__\nreturn super(Task, self).__call__(*args, **kwargs)\n
>  File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\",
> line 103, in __call__\nreturn super(PulpTask, self).__call__(*args,
> **kwargs)\n  File 
> \"/usr/lib/python2.7/site-packages/celery/app/trace.py\",
> line 437, in __protected_call__\nreturn 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\nunits=transfer_units)\n  File
> \"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/importer.py\",
> line 58, in import_units\nreturn 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\nassociated_units = 
> set([_associate_unit(dest_repo,
> unit) for unit in units])\n

Re: [foreman-users] CV publishing errors

2017-02-09 Thread 'Jason B. Nance' via Foreman users 
Are you using the user/pass from the "default_login" and "default_password" in 
/etc/pulp/server.conf? 

j 




From: "Lachlan Musicman"  
To: "Foreman Users"  
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 < [ mailto:data...@gmail.com | 
data...@gmail.com ] > 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 < [ mailto:thomasmc...@redhat.com | 
thomasmc...@redhat.com ] > wrote: 

BQ_BEGIN

Try including the -u admin -p admin on all the pulp-admin commands 

On Thu, Feb 9, 2017 at 5:30 PM, Lachlan Musicman < [ mailto:data...@gmail.com | 
data...@gmail.com ] > wrote: 

BQ_BEGIN

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_repository_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-bc593d4ca46d/", 
"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-packages/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-packages/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"=> 
"reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au.dq", 
"state"=>"error", 
"worker_name"=> 
" [ mailto:reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au | 
reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au ] ", 
"result"=>nil, 
"error"=> 
{"code"=>"PLP", 
"data"=>{}, 
"description"=>"Pulp exception occurred: PulpExecutionException",

Re: [foreman-users] "Planning" taking forever

2017-02-09 Thread 'Jason B. Nance' via Foreman users 
I only have 1 version of each of my CVs as it is. :-\ 




From: "Lachlan Musicman"  
To: "Foreman Users"  
Sent: Thursday, February 9, 2017 5:02:36 PM 
Subject: Re: [foreman-users] "Planning" taking forever 

I found that reducing the number of versions of CVs helped - clearing out old 
versions that weren't used any more. 

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:56, 'Jason B. Nance' via Foreman users < [ 
mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] > 
wrote: 


In the past week or two I've noticed that when I go to publish a new version of 
a CV or promote it the "Planning" phase is taking 30-60 minutes or even more. 
Mongodb is hogging all of the resources. This is on Katello 3.2.2, Foreman 
1.13.4, CentOS 7.3+. 

Anyone else experiencing this or found a solution? 

j 

-- 
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 [ mailto:foreman-users%2bunsubscr...@googlegroups.com | 
foreman-users+unsubscr...@googlegroups.com ] . 
To post to this group, send email to [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] . 
Visit this group at [ https://groups.google.com/group/foreman-users | 
https://groups.google.com/group/foreman-users ] . 
For more options, visit [ https://groups.google.com/d/optout | 
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 [ mailto:foreman-users+unsubscr...@googlegroups.com | 
foreman-users+unsubscr...@googlegroups.com ] . 
To post to this group, send email to [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] . 
Visit this group at [ https://groups.google.com/group/foreman-users | 
https://groups.google.com/group/foreman-users ] . 
For more options, visit [ https://groups.google.com/d/optout | 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] CV publishing errors

2017-02-09 Thread Lachlan Musicman 
/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  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  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 
>> 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_re
>>> pository_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-bc593d4ca46d/",
>>> "task_id"=>"39286b9b-7684-4b1c-b092-bc593d4ca46d",
>>> "tags"=>
>>>  ["pulp:repository:Peter_MacCallum_Cancer_Centre-Gaffa-dev-G
>>> AFFA-_sssd-Copr_repository_for_sssd_1_15",
>>>   "pulp:repository:Peter_MacCallum_Cancer_Centre-GAFFA-2_0-_ss
>>> sd-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\nR = retval = fun(*args, **kwargs)\n  File
>>> \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line
>>> 484, in __call__\nreturn super(Task, self).__call__(*args, **kwargs)\n
>>>  File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\",
>>> line 103, in __call__\nreturn super(PulpTask, self).__call__(*args,
>>> **kwargs)\n  File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\",
>>> line 437, in __protected_call__\nreturn 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\nunits=transfer_units)\n  File
>>> \"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/importer.py\",
>>> line 58, in import_units\nreturn 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\nassociated_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\nreturn 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\nself.import_content(path, location)\n
>>>  File \"/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py\",
>>> line 879, in import_content\nstorage.put(self, path, location)\n  File
>>> \"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\",
>>> line 123, in put\nmkdir(os.path.dirname(destination))\n  File
>>> \"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\",
>>> line 20, in mkdir\nos.makedirs(path)\n  File
>>> \"/usr/lib64/python2.7/os.py\", line 157, in makedirs\nmkdir(name,
>>> mode)\nPulpExecutionException: Pulp exception occurred:
>>> PulpExecutionException\n",
>>> "spawned_tasks"=>[],
>>> "progress_report"=>{},
>>> "queue"=>
>>>  "reserved_resource_worke...@vmpr-res-utils.unix.petermac.or
>>> g.au.dq",
>>> "state"=>"error",
>>> "worker_name"=>
>>>  "reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au",
>>> "result"=>nil,
>>> "error"=>
>>>  {"code"=>"PLP",
>>>   "data"=>{},
>>>   "description"=>"Pulp exception occurred: PulpExecutionException",
>>>   "sub_errors"=>[]},
>>>

Re: [foreman-users] CV publishing errors

2017-02-09 Thread Lachlan Musicman 
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  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 
> 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-bc593d4ca46d/",
>> "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\nR = retval = fun(*args, **kwargs)\n  File
>> \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line
>> 484, in __call__\nreturn super(Task, self).__call__(*args, **kwargs)\n
>>  File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\",
>> line 103, in __call__\nreturn super(PulpTask, self).__call__(*args,
>> **kwargs)\n  File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\",
>> line 437, in __protected_call__\nreturn 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\nunits=transfer_units)\n  File
>> \"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/importer.py\",
>> line 58, in import_units\nreturn 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\nassociated_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\nreturn 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\nself.import_content(path, location)\n
>>  File \"/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py\",
>> line 879, in import_content\nstorage.put(self, path, location)\n  File
>> \"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\",
>> line 123, in put\nmkdir(os.path.dirname(destination))\n  File
>> \"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\",
>> line 20, in mkdir\nos.makedirs(path)\n  File
>> \"/usr/lib64/python2.7/os.py\", line 157, in makedirs\nmkdir(name,
>> mode)\nPulpExecutionException: Pulp exception occurred:
>> PulpExecutionException\n",
>> "spawned_tasks"=>[],
>> "progress_report"=>{},
>> "queue"=>
>>  "reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au.dq",
>> "state"=>"error",
>> "worker_name"=>
>>  "reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au",
>> "result"=>nil,
>> "error"=>
>>  {"code"=>"PLP",
>>   "data"=>{},
>>   "description"=>"Pulp exception occurred: PulpExecutionException",
>>   "sub_errors"=>[]},
>> "_id"=>{"$oid"=>"589cdf577fc653305c394bd2"},
>> "id"=>"589cdf577fc653305c394bd2"}]}
>>
>>
>>
>> Katello::Errors::PulpError: PLP: 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,

Re: [foreman-users] Foreman install on large environment

2017-02-09 Thread Dor Azoulay 
Thank you very much, you helped a lot.

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] [Event] Next Foreman Community Demo - Thu 16 Feb 3pm [GMT]

2017-02-09 Thread greg . sutcliffe 
Hi all

It's time for the next Foreman Community Demo! Join us at 3pm on Thu 16 Feb for 
a
roundup of the recent conferences, and the usual review of new & interesting
developments from around our community. As ever, more information is available
on the event page [1] and the show agenda is being compiled at the Foreman wiki 
[2].

If you have anything new, cool tips, etc, that you'd like to share with the
community, please do let me know and I can arrange for you to be on the demo,
or (if you can't make it) I can demo for you.

As ever, we encourage live participation via the YouTube live chat, or in IRC
(#theforeman on Freenode). For those that can't attend, the video will be
posted to YouTube afterwards.

If you'd like to know when other Foreman events are happening, do check out our
Events page on the Foreman website [3].

[1] https://www.youtube.com/watch?v=Zz0Bgt87wPE
[2] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information
[3] http://theforeman.org/events

Cheers!
--
Greg
IRC: gwmngilfen

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] no new entries to /etc/salt/autosign.conf during provisioning

2017-02-09 Thread Tom K. 
Hi,

when I install new hosts via Foreman, everything works fine. Just the fact 
that no salt autosign will work. I have to
do it manually with salt-key -A
After accepting manually the salt run from foreman works perfect.

I find now helpful entry in the foreman logs to fix this.

Does anyone have the same problem or a solution?


-- Tom

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Web interface SSL Cert

2017-02-09 Thread Mimmus 
Hi Michael,
I'm facing a similar problem, *probably *after adding our internal AD CA to:
 /etc/pki/ca-trust/source/
anchors/
and run:
 update-ca-trust
(to use LDAPS as authentication source for Web GUI).

Now, from the Capsule server, command:
 /etc/puppet/node.rb myclient.mydomain.com
doesn't work anymore:
 Error retrieving node myclient.mydomain.com: Net::HTTPPreconditionFailed
(with obvious consequencies on all clients)

I'm not sure if the real cause is that. Any help?

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Web interface SSL Cert

2017-02-09 Thread Mimmus 
Hi Michael,
I'm facing a similar problem, *probably *after adding our internal AD CA to:
 /etc/pki/ca-trust/source/anchors/
and run:
 update-ca-trust
(to use LDAPS as authentication source for Web GUI).

Now, from the Capsule server, command:
 /etc/puppet/node.rb myclient.mydomain.com
doesn't work anymore:
 Error retrieving node myclient.mydomain.com: Net::HTTPPreconditionFailed
(with obvious consequencies on all clients)

I'm not sure if the real cause is that but I'm seeing now that, after 
stopping httpd on Satellite server, node.rb is working again :-D

Any help?

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re-establishing communication with Satellite server after revoking all Capsule certificates

2017-02-09 Thread Mimmus 
Hi,
I revoked by mistake all certificates on Capsule server (also Puppet 
CA/Puppet master).
I followed this procedure:

 # puppet cert clean --all
 # service puppet stop ; service httpd stop
 # rm -rf /var/lib/puppet/ssl/*
 # puppet cert list --all
 # puppet master --no-daemonize --verbose
(https://access.redhat.com/solutions/2168191)
to restore main certificates but now Capsule server cannot communicate with 
Satellite:
 # /etc/puppet/node.rb myclient.mydomain.com
 Error retrieving node myclient.mydomain.com: Net::HTTPPreconditionFailed

I suppose that Satellite server is no more able to authenticate Capsule but I 
don't know how can I solve the issue.

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Import Salt States fails with ERF12-4701 and ERF-12-7301

2017-02-09 Thread fbo 
Sorry, my fault. Seems we really need to create a saltuser, and the 
disable_ssl option was not a good idea.

Works fine now

Le mercredi 8 février 2017 16:57:52 UTC+1, fbo a écrit :
>
> Hi,
>
> I recently installed The Foreman on a server, and moved our Salt Master 
> also on it ( previous master was on a RedHat 6.6 ). I'm trying to get the 
> salt reports on foreman and having issues with configuration.
>
> Here are the config files : 
>
> - /etc/salt/master :
> external_auth:
>   pam:
> root:
>   - '@runner'
>
> rest_cherrypy:
>   port: 9191
>   host: 10.0.244.110
>   disable_ssl: true
>   ssl_key: /etc/puppetlabs/puppet/ssl/private_keys/testserver.pem
>   ssl_crt: /etc/puppetlabs/puppet/ssl/certs/testserver.pem
>   webhook_disable_auth: True
>
> - /etc/foreman-proxy/settings.d/salt.yml :
> :enabled: https
> :autosign_file: /etc/salt/autosign.conf
> :salt_command_user: root
> # Some features require using the Salt API - such as listing environments 
> and retrieving state info
> :use_api: true
> :api_url: https://testserver:9191
> :api_auth: pam
> :api_username: root
> :api_password: 
>
> The important lines in proxy log file /var/log/foreman-proxy/proxy.log :
>
> W, [2017-02-08T16:10:55.438461 ]  WARN -- : TCPServer Error: Address 
> already in use - bind(2)
> ...
> E, [2017-02-08T16:31:53.172904 ] ERROR -- : Failed to list environments: 
> SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown 
> protocol
> D, [2017-02-08T16:31:53.173046 ] DEBUG -- : Failed to list environments: 
> SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown 
> protocol
>
> They don't seem to communicate, probably for authentification reasons. I 
> tried to replace the saltuser with root user, and to disable security to 
> see if it works, but still got this error.
> I tried to look for different values for api_auth also but couldn't find 
> any doc
>
> Any idea why ? Or a simple procedure to configure this ? Both run on the 
> same server, no particular need for a specific Salt user.
>
> Thanks for your help
>

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Foreman Web-UI

2017-02-09 Thread Dominic Cleal 
On 09/02/17 09:45, Vadim Bulst wrote:
> Hi there,
> 
> I updated to from 13.x to 14.1 and there is something wrong with the UI
> - see screenshot:
> 
> 
> 
> 
> I'm using Apache on Centos 7
> 
> Did somebody already submitted a bug report ?

Yes, see comment #3 at http://projects.theforeman.org/issues/18371 for
details on correcting the Apache configuration, or re-run foreman-installer.

-- 
Dominic Cleal
domi...@cleal.org

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Foreman Web-UI

2017-02-09 Thread Vadim Bulst 
Hi there,

I updated to from 13.x to 14.1 and there is something wrong with the UI - 
see screenshot:




I'm using Apache on Centos 7 

Did somebody already submitted a bug report ?

Cheers,

Vadim

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.