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

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

Re: [foreman-users] Foreman Web-UI

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: > > >

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

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

Re: [foreman-users] CV publishing errors

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

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,

Re: [foreman-users] CV publishing errors

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

[foreman-users] can not download the RHEL repos

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

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

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

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

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,

[foreman-users] upgrading puppet

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

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

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 >

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

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

[foreman-users] Re: upgrading puppet

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: >

Re: [foreman-users] CV publishing errors

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

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

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

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

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-users] Re-establishing communication with Satellite server after revoking all Capsule certificates

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

Re: [foreman-users] Web interface SSL Cert

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

Re: [foreman-users] Web interface SSL Cert

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

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

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

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

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

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

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

[foreman-users] Foreman Web-UI

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