Re: [foreman-users] Foreman installation issues Centos 7

['Jason Nance' via Foreman users]

Hi Wim,

You have included an option that requires an argument without including the 
argument, so the installer is using the next option as the argument and it is 
throwing off all of your options/arguments.

Check your options against the --help output. A common mistake is to leave out 
a "true" or "false" to the boolean options.

Regards,

J


> On Mar 28, 2017, at 2:44 AM, Wim Van den Borre  
> wrote:
> 
> Hey Everyone,
> 
> I'm trying to install foreman but when i run the installer i get a bunch of 
> these messages, does anyone know what the problem coulde be?
> 
> foreman-installer
> Parameter foreman-foreman-url invalid: ::foreman::params::foreman_url must 
> match one of (?-mix:^https?:\/\/)
> Parameter foreman-puppetrun invalid: "::foreman::params::puppetrun" is not a 
> valid boolean, "::foreman::params::puppetrun" is not a valid boolean
> Parameter foreman-unattended invalid: "::foreman::params::unattended" is not 
> a valid boolean
> Parameter foreman-authentication invalid: "::foreman::params::authentication" 
> is not a valid boolean
> Parameter foreman-passenger invalid: "::foreman::params::passenger" is not a 
> valid boolean, "::foreman::params::passenger" is not a valid boolean
> Parameter foreman-use-vhost invalid: "::foreman::params::use_vhost" is not a 
> valid boolean
> Parameter foreman-ssl invalid: "::foreman::params::ssl" is not a valid boolean
> Parameter foreman-configure-epel-repo invalid: 
> "::foreman::params::configure_epel_repo" is not a valid boolean
> Parameter foreman-configure-scl-repo invalid: 
> "::foreman::params::configure_scl_repo" is not a valid boolean
> Parameter foreman-selinux invalid: "::foreman::params::selinux" is not a 
> valid boolean
> Parameter foreman-gpgcheck invalid: "::foreman::params::gpgcheck" is not a 
> valid boolean
> 
> Kind regards
> -- 
> 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] Re: Sync is stuck in pending

['Jason Nance' via Foreman users]

Are you sure your /etc/httpd/conf.d/pulp.conf isn't empty? This sounds a lot 
like the failed upgrade symptoms when pulp.conf was getting blown away (or 
created without an httpd restart).

J


> On Feb 27, 2017, at 6:39 PM, Lachlan Musicman  wrote:
> 
> While I know it's deprecated, I've started looking at pulp-admin: 
> https://www.mankier.com/1/pulp-admin#Tasks
> 
> The task - in the GUI, the id, which I think is the Foreman task id, is 
> dcbef693-85c3-4418-a189-6ebdb262d99f
> 
> This returns 
> 
> [root@vmpr-res-utils ~]# pulp-admin -u admin tasks details --task-id 
> dcbef693-85c3-4418-a189-6ebdb262d99f
> Enter password: 
> +--+
>   Task Details
> +--+
> 
> The following resource(s) could not be found:
> 
>   dcbef693-85c3-4418-a189-6ebdb262d99f (resource_id)
> 
> 
> So this is the wrong id. I go looking in the dynaflow and see this in the 
> "suspended" task
> 
> pulp_task_group:
>   group_id: 9a8074c1-60ad-460d-80ad-9c6148d739ca
> 
> [root@vmpr-res-utils ~]# pulp-admin -u admin tasks details --task-id 
> 9a8074c1-60ad-460d-80ad-9c6148d739ca
> +--+
>   Task Details
> +--+
> 
> The following resource(s) could not be found:
> 
>   9a8074c1-60ad-460d-80ad-9c6148d739ca (resource_id)
> 
> Hmm. That's not ideal. Maybe I'm wrong - it does say "pulp_task_group" not 
> "pulp_task":
> 
> [root@vmpr-res-utils ~]# pulp-admin -u admin tasks list
> +--+
>  Tasks
> +--+
> 
> No tasks found
> 
> Hooh boy. 
> 
> Ok. So I've started seeing hints about a "force unlock" in some of the 
> pulp/katello docs and bug reports, but can't find anything definitive.
> 
> In desperation, I did, as per https://access.redhat.com/solutions/1381053 :
> 
> foreman-rake console
> ForemanTasks::Task.where(:state => :running).where(:label => 
> "Actions::Pulp::Repository::RegenerateApplicability").destroy_all
> 
> And the sync status page in the GUI is returning 404.
> 
> 
> And now sync is failing on failed subtasks: RuntimeError: A sub task failed.
> 
> pulp-admin returns
> 
> Traceback (most recent call last):
>   File "/usr/bin/pulp-admin", line 9, in 
> load_entry_point('pulp-client-admin==2.9.3', 'console_scripts', 
> 'pulp-admin')()
>   File "/usr/lib/python2.7/site-packages/pulp/client/admin/__init__.py", line 
> 9, in main
> exit_code = launcher.main(read_config(), 
> exception_handler_class=AdminExceptionHandler)
>   File "/usr/lib/python2.7/site-packages/pulp/client/launcher.py", line 115, 
> in main
> code = cli.run(args)
>   File "/usr/lib/python2.7/site-packages/pulp/client/extensions/core.py", 
> line 477, in run
> code = self.context.exception_handler.handle_exception(e)
>   File 
> "/usr/lib/python2.7/site-packages/pulp/client/extensions/exceptions.py", line 
> 98, in handle_exception
> exit_code = handle_func(e)
>   File 
> "/usr/lib/python2.7/site-packages/pulp_rpm/extensions/admin/rpm_admin_consumer/bind.py",
>  line 64, in handle_not_found
> ExceptionHandler.handle_not_found(self, e)
>   File 
> "/usr/lib/python2.7/site-packages/pulp/client/extensions/exceptions.py", line 
> 163, in handle_not_found
> for resource_type, resource_id in e.extra_data['resources'].items():
> KeyError: 'resources'
> 
> foreman-rake returns
> 
> [root@vmpr-res-utils ~]# foreman-rake katello:delete_orphaned_content --trace
> ** Invoke katello:delete_orphaned_content (first_time)
> ** Invoke environment (first_time)
> ** Execute environment
> ** Execute katello:delete_orphaned_content
> rake aborted!
> RestClient::ResourceNotFound: 404 Resource Not Found
> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/abstract_response.rb:74:in
>  `return!'
> /opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.9.0/lib/runcible/base.rb:79:in
>  `block in get_response'
> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:493:in
>  `call'
> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:493:in
>  `process_result'
> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:421:in
>  `block in transmit'
> /opt/rh/rh-ruby22/root/usr/share/ruby/net/http.rb:853:in `start'
> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:413:in
>  `transmit'
> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:176:in
>  `execute'
> /opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:41:in
> 

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

['Jason Nance' via Foreman users]

It probably would have helped had I said --upgrade. :-/



> On Feb 9, 2017, at 10:20 PM, Lachlan Musicman <data...@gmail.com> 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 <data...@gmail.com> 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 <data...@gmail.com> 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"

['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.

Re: [foreman-users] /var/lib/pulp/content not avialable

['Jason Nance' via Foreman users]

Hi Jurgen,

The default sync type is now "on demand", so the symlinks will be broken until 
a client requests the packages (which will first be retrieved by Squid from 
upstream) and the Squid cache is processed (which I believe happens daily). The 
package is still available to other clients during this time from the Squid 
cache.

You can change the sync type both for an individual repository and the default 
for new repositories (in Settings -> Content).

Regards,

J


> On Jan 20, 2017, at 2:03 PM, Jurgen Ponds  wrote:
> 
> 
> Hello
> 
> After a clean install of katello-3.x and content sync, the 
> /var/lib/pulp/content is not created. 
> The content sync appears to work, but the source content is not stored, only 
> the link in published.
> 
> With katello-2.x I had no issues with this. It started with katello-3.x
> Currently I have katello-3.3 installed.
> 
> lrwxrwxrwx. 1 apache apache 139 Jan 19 22:36 
> /var/lib/pulp/published/yum/master/yum_distributor/JPP-CentOS7_Extra_Repositories-CentOS7-bacula-x86_64/1484861805.49/bacula-console-bat-7.0.5-7.el7.x86_64.rpm
>  -> /var/lib/pulp/content/units/r
> pm/24/ba60c8a5afe14a90cea8987f20ad69275fe4bebb66b3e000b2d42f90d53089/bacula-console-bat-7.0.5-7.el7.x86_64.rpm
> 
> # yum install -y katello \ 
>  ipa-admintools \ 
>  foreman-libvirt \ 
>  tfm-rubygem-foreman_dhcp_browser
> 
> # foreman-installer --scenario katello \ 
>--foreman-admin-password=* \ 
>--foreman-email-smtp-address=seaking.jpp.nl \ 
>--foreman-email-smtp-domain=jpp.nl \ 
>--enable-foreman-plugin-remote-execution 
> 
> -- 
> 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.