date:20160914

[foreman-users] Could not find kernel image: linux

2016-09-14 Thread Tom McKay

Admittedly I am a far cry from a knowledgeable foreman provisioner, but
with the assistance of others I mostly muddle along... but I need help.

I am running foreman/katello from git and have set up a network named
"provisioning" for my katello install. I'm running libvirt compute resource.

At the moment, I get an error of "Could not find kernel image: linux" at
the start of provisioning. After poking around the templates, I see that
word in the "Kickstart default PXELinux" template, "DEFAULT linux". At this
point I'm dropped to the boot: prompt. Some googling later (and lots of
failures) I entered "kickstart_cmdline" at that prompt. Magic! The install
finished and the VM rebooted... and back to the boot: prompt with same
error message.

And now I'm just stuck in a loop if I enter kickstart_cmdline again. It
just reinstalls everything and reboots, landing me back at the boot: prompt.

I'm sure this is user error but I'm not sure where or what to look for.

-- 
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] Puppet Server Stop After OS Update

2016-09-14 Thread Marcio Costa

Hello. Im using Centos 7.2 and after an update, the puppet servers stop 
loading.  I have this error:

Sep 14 14:13:15 java: Exception in thread "main" 
*java.lang.IllegalArgumentException: 
service 
:puppetlabs.trapperkeeper.services.status.status-service/status-service 
does not appear in configuration*
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_endpoint_and_server_from_config.invoke(webrouting_service_core.clj:55)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_route.invoke(webrouting_service_core.clj:99)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.services.webrouting.webrouting_service$reify__25542$service_fnk__5223__auto___positional$reify__25550.get_route(webrouting_service.clj:37)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval25272$fn__25436$G__25256__25442.invoke(webrouting_service.clj:10)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval25272$fn__25436$G__25255__25449.invoke(webrouting_service.clj:10)
Sep 14 14:13:15 java: at clojure.core$partial$fn__4527.invoke(core.clj:2493)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.services.status.status_service$reify__36201$service_fnk__5223__auto___positional$reify__36208.start(status_service.clj:31)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.services$eval5025$fn__5039$G__5015__5042.invoke(services.clj:8)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.services$eval5025$fn__5039$G__5014__5046.invoke(services.clj:8)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.internal$eval13757$run_lifecycle_fn_BANG___13764$fn__13765.invoke(internal.clj:200)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.internal$eval13757$run_lifecycle_fn_BANG___13764.invoke(internal.clj:183)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.internal$eval13786$run_lifecycle_fns__13791$fn__13792.invoke(internal.clj:234)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.internal$eval13786$run_lifecycle_fns__13791.invoke(internal.clj:211)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.internal$eval14257$build_app_STAR___14266$fn$reify__14276.start(internal.clj:587)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.internal$eval14303$boot_services_for_app_STAR__STAR___14310$fn__14311$fn__14313.invoke(internal.clj:613)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.internal$eval14303$boot_services_for_app_STAR__STAR___14310$fn__14311.invoke(internal.clj:611)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.internal$eval14303$boot_services_for_app_STAR__STAR___14310.invoke(internal.clj:605)
Sep 14 14:13:15 java: at clojure.core$partial$fn__4529.invoke(core.clj:2499)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.internal$eval13825$initialize_lifecycle_worker__13836$fn__13837$fn__13924$state_machine__11796__auto13925$fn__13927.invoke(internal.clj:251)
Sep 14 14:13:15 java: at 
puppetlabs.trapperkeeper.internal$eval13825$initialize_lifecycle_worker__13836$fn__13837$fn__13924$state_machine__11796__auto13925.invoke(internal.clj:251)
Sep 14 14:13:15 java: at 
clojure.core.async.impl.ioc_macros$run_state_machine.invoke(ioc_macros.clj:1011)
Sep 14 14:13:15 java: at 
clojure.core.async.impl.ioc_macros$run_state_machine_wrapped.invoke(ioc_macros.clj:1015)
Sep 14 14:13:15 java: at 
clojure.core.async$ioc_alts_BANG_$fn__11964.invoke(async.clj:378)
Sep 14 14:13:15 java: at 
clojure.core.async$do_alts$fn__11910$fn__11913.invoke(async.clj:247)
Sep 14 14:13:15 java: at 
clojure.core.async.impl.channels.ManyToManyChannel$fn__6731$fn__6732.invoke(channels.clj:95)
Sep 14 14:13:15 java: at clojure.lang.AFn.run(AFn.java:22)
Sep 14 14:13:15 java: at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
Sep 14 14:13:15 java: at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
Sep 14 14:13:15 java: at java.lang.Thread.run(Thread.java:745)
Sep 14 14:13:15 systemd: puppetserver.service: main process exited, 
code=exited, status=1/FAILURE
Sep 14 14:13:15 systemd: puppetserver.service: control process exited, 
code=exited status=1
Sep 14 14:13:15 systemd: Failed to start puppetserver Service.
Sep 14 14:13:15 systemd: Unit puppetserver.service entered failed state.
Sep 14 14:13:15 systemd: puppetserver.service failed.
Sep 14 14:13:15 systemd: puppetserver.service holdoff time over, scheduling 
restart.
Sep 14 14:13:15 systemd: Starting puppetserver Service...

I have modified the file *web-routes.conf.erb* and added the text: 
(https://github.com/theforeman/puppet-puppet/blob/master/templates/server/puppetserver/conf.d/web-routes.conf.erb#L17-L21)
<%- if scope.function_versioncmp([@server_puppetserver_version, '2.6']) >= 0 
-%> 

# This controls the mount point for the status API 
"puppetlabs.trapperkeeper.services.status.status-service/status-service": 
"/status" 
<%- end -%>

Still not working.   I

Re: [foreman-users] 500 Internal Server Error when subscribing hosts

2016-09-14 Thread Justin Sherrill


On 09/14/2016 10:17 AM, James Evans wrote:
I ran foreman-rake katello:reimport as that seems to be the 
replacement for the functionality of katello:reindex, restarted all 
katello services, and tried again. It's still failing. I've attached 
the requested log file.


I recognize an error:


Error opening CA Certificate /etc/pki/pulp/ca.crt
140466849802144:error:02001002:system library:fopen:No such file or 
directory:bss_file.c:398:fopen('/etc/pki/pulp/ca.crt','r')
 140466849802144:error:20074002:BIO routines:FILE_CTRL:system 
lib:bss_file.c:400:

 unable to load certificate
 unable to write 'random state'

 can you try running:

pulp-gen-ca-certificate
katello-service restart


-Justin



Thanks,

james

On Tuesday, September 13, 2016 at 4:46:24 PM UTC-5, John Mitsch wrote:

James,

Try a couple things first:

foreman-rake katello:reindex
systemctl restart tomcat

then
 'tail -f -n 0 /var/log/candlepin/* /var/log/messages/
/var/log/foreman/production.log' on your machine and retry the
activation key.
Share that output with us (if its still erroring). It will be best
to pipe this to a file and attach it as it makes it easier to parse.

Let me know if you have any questions.

Thanks,

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

On Tue, Sep 13, 2016 at 4:54 PM, James Evans
 wrote:

I've been prototyping Foreman for a while now, and everything
has been working perfectly in testing. Now I've built out our
production deployment and imported content, and started trying
to move hosts to the Foreman and Katello server. When ever I
run subscription-manager register, from any host, I get 500
Internal Server Error, and the task hangs. I have to go into
the dynaflow console and skip the broken step, and resume the
task to clear locks.

I've never had this happen in any of my tests where I've built
a number of test servers to test out processes and
configurations. All the test systems were able to register
clients with no issues at all. The server and client are both
fully updated RHEL 7.2 boxes, the server is
running foreman-1.12.2-1.el7.noarch
and katello-3.1.0-5.el7.noarch.

The only other difference between the production and test is
that I never imported RHEL content into the test systems.

I've spent a week building out the products, repositories,
content views, etc. and would really like to recover this
without having to start over, but this is obviously a major
problem!

I've googled the errors, with out finding any thing. Can
anyone help me?

On the client I run:

# subscription-manager register --org="myOrg"
--activationkey="rhel-72-x86_64-production"
Task 1ac48d97-a570-4a43-9a09-b5cb0be7cf29:
RestClient::InternalServerError: 500 Internal Server Error

And the production.log contains (abbreviated):

2016-09-13 15:39:15 [app] [I] Started GET "/rhsm/" for
XX.XX.XX.XX at 2016-09-13 15:39:15 -0500
2016-09-13 15:39:15 [app] [I] Processing by
Katello::Api::V2::RootController#rhsm_resource_list as JSON
2016-09-13 15:39:15 [app] [I]   Parameters: {"root"=>{}}
2016-09-13 15:39:15 [app] [I]   Rendered

/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.1.0.1/app/views/katello/api/v2/root/resource_list.json.rabl
within katello/api/v2/layouts/collection (2.4ms)
2016-09-13 15:39:15 [app] [I] Completed 200 OK in 21ms (Views:
3.8ms | ActiveRecord: 0.0ms)
2016-09-13 15:39:15 [app] [I] Started GET "/rhsm/status" for
XX.XX.XX.XX at 2016-09-13 15:39:15 -0500
2016-09-13 15:39:15 [app] [I] Processing by
Katello::Api::Rhsm::CandlepinProxiesController#server_status
as JSON
2016-09-13 15:39:15 [app] [I] Completed 200 OK in 308ms
(Views: 0.9ms | ActiveRecord: 0.0ms)
2016-09-13 15:39:16 [app] [I] Started POST
"/rhsm/consumers?owner=myOrg_keys=rhel-72-x86_64-production"
for XX.XX.XX.XX at 2016-09-13 15:39:16 -0500
2016-09-13 15:39:16 [app] [I] Processing by
Katello::Api::Rhsm::CandlepinProxiesController#consumer_activate
as JSON
2016-09-13 15:39:16 [app] [I]   Parameters:
{"facts"=>"[FILTERED]",
"installedProducts"=>[{"productName"=>"Red Hat Enterprise
Linux Server", "arch"=>"x86_64", "version"=>"7.2",
"productId"=>"69"}], "type"=>"system", "name"=>"client.com
", "contentTags"=>["rhel-7",
"rhel-7-server"], "owner"=>"myOrg",
"activation_keys"=>"rhel-72-x86_64-production"}
2016-09-13 15:39:18 [app] [I] Import facts for
'client.example.com ' completed.
Added: 0, Updated: 1,

Re: [foreman-users] Re: "No root file system is defined" error using preseed atomic partitioning scheme

2016-09-14 Thread Hauke Behrens



On 09/14/2016 03:04 PM, Akash Kaveti wrote:
> Hello Again,
> 
> It is working now, I have check the syslog, the device I am trying to
> install is not there it seems,
> so I gave /dev/sdb, it is working now.

Glad I could help. :-)


> It is working for the current host, but what about the other hosts, Why
> cant I use "/d-i partman/early_command string debconf-set
> partman-auto/disk "$(list-devices disk | head -n1)/"

It's always hard to guess what device is getting used.
If you have a usb-stick plugged-in with the e.g. a formean-boot-iso,
that might be /dev/sda and your "real" hard-disk might be /dev/sdb/.

In that case "head -n2" will do the trick.
When using raid-devices this might be different too.

Also check out this thread:

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

Hauke

-- 
bytemine GmbH, Im Technologiepark 4, 26129 Oldenburg
Support: 0441-309197-42 --- Vertrieb: 0441-309197-69
GF: Felix Kronlage -- AG in Oldenburg -- HRB 203 940
https://www.bytemine.net --- VAT-Number: DE267286778

-- 
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] 500 Internal Server Error when subscribing hosts

2016-09-14 Thread James Evans

I ran foreman-rake katello:reimport as that seems to be the replacement for 
the functionality of katello:reindex, restarted all katello services, and 
tried again. It's still failing. I've attached the requested log file.

Thanks,

james

On Tuesday, September 13, 2016 at 4:46:24 PM UTC-5, John Mitsch wrote:
>
> James,
>
> Try a couple things first:
>
> foreman-rake katello:reindex
> systemctl restart tomcat
>
> then
>  'tail -f -n 0 /var/log/candlepin/* /var/log/messages/ 
> /var/log/foreman/production.log' on your machine and retry the activation 
> key.
> Share that output with us (if its still erroring). It will be best to pipe 
> this to a file and attach it as it makes it easier to parse.
>
> Let me know if you have any questions.
>
> Thanks,
>
> John Mitsch
> Red Hat Engineering
> (860)-967-7285
> irc: jomitsch
>
> On Tue, Sep 13, 2016 at 4:54 PM, James Evans  > wrote:
>
>> I've been prototyping Foreman for a while now, and everything has been 
>> working perfectly in testing. Now I've built out our production deployment 
>> and imported content, and started trying to move hosts to the Foreman and 
>> Katello server. When ever I run subscription-manager register, from any 
>> host, I get 500 Internal Server Error, and the task hangs. I have to go 
>> into the dynaflow console and skip the broken step, and resume the task to 
>> clear locks.
>>
>> I've never had this happen in any of my tests where I've built a number 
>> of test servers to test out processes and configurations. All the test 
>> systems were able to register clients with no issues at all. The server and 
>> client are both fully updated RHEL 7.2 boxes, the server is 
>> running foreman-1.12.2-1.el7.noarch and katello-3.1.0-5.el7.noarch.
>>
>> The only other difference between the production and test is that I never 
>> imported RHEL content into the test systems.
>>
>> I've spent a week building out the products, repositories, content views, 
>> etc. and would really like to recover this without having to start over, 
>> but this is obviously a major problem!
>>
>> I've googled the errors, with out finding any thing. Can anyone help me?
>>
>> On the client I run:
>>
>> # subscription-manager register --org="myOrg" 
>> --activationkey="rhel-72-x86_64-production"
>> Task 1ac48d97-a570-4a43-9a09-b5cb0be7cf29: 
>> RestClient::InternalServerError: 500 Internal Server Error
>>
>> And the production.log contains (abbreviated):
>>
>> 2016-09-13 15:39:15 [app] [I] Started GET "/rhsm/" for XX.XX.XX.XX at 
>> 2016-09-13 15:39:15 -0500
>> 2016-09-13 15:39:15 [app] [I] Processing by 
>> Katello::Api::V2::RootController#rhsm_resource_list as JSON
>> 2016-09-13 15:39:15 [app] [I]   Parameters: {"root"=>{}}
>> 2016-09-13 15:39:15 [app] [I]   Rendered 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.1.0.1/app/views/katello/api/v2/root/resource_list.json.rabl
>>  
>> within katello/api/v2/layouts/collection (2.4ms)
>> 2016-09-13 15:39:15 [app] [I] Completed 200 OK in 21ms (Views: 3.8ms | 
>> ActiveRecord: 0.0ms)
>> 2016-09-13 15:39:15 [app] [I] Started GET "/rhsm/status" for XX.XX.XX.XX 
>> at 2016-09-13 15:39:15 -0500
>> 2016-09-13 15:39:15 [app] [I] Processing by 
>> Katello::Api::Rhsm::CandlepinProxiesController#server_status as JSON
>> 2016-09-13 15:39:15 [app] [I] Completed 200 OK in 308ms (Views: 0.9ms | 
>> ActiveRecord: 0.0ms)
>> 2016-09-13 15:39:16 [app] [I] Started POST 
>> "/rhsm/consumers?owner=myOrg_keys=rhel-72-x86_64-production" for 
>> XX.XX.XX.XX at 2016-09-13 15:39:16 -0500
>> 2016-09-13 15:39:16 [app] [I] Processing by 
>> Katello::Api::Rhsm::CandlepinProxiesController#consumer_activate as JSON
>> 2016-09-13 15:39:16 [app] [I]   Parameters: {"facts"=>"[FILTERED]", 
>> "installedProducts"=>[{"productName"=>"Red Hat Enterprise Linux Server", 
>> "arch"=>"x86_64", "version"=>"7.2", "productId"=>"69"}], "type"=>"system", 
>> "name"=>"client.com", "contentTags"=>["rhel-7", "rhel-7-server"], 
>> "owner"=>"myOrg", "activation_keys"=>"rhel-72-x86_64-production"}
>> 2016-09-13 15:39:18 [app] [I] Import facts for 'client.example.com' 
>> completed. Added: 0, Updated: 1, Deleted 21 facts
>> 2016-09-13 15:39:21 [katello/pulp_rest] [E] RestClient.post "
>> https://foreman.example.com/pulp/api/v2/consumers/;, 
>> "{\"id\":\"1c796228-efa5-4190-b5de-a0f7605e3074\",\"display_name\":\"
>> client.example.com\"}", "Accept"=>"*/*; q=0.5, application/xml", 
>> "Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"100", 
>> "accept"=>"application/json", "content_type"=>"application/json"
>>  | \n# => 500 InternalServerError | application/json 2551 bytes
>>  | 
>> 2016-09-13 15:39:21 [foreman-tasks/action] [E] 500 Internal Server Error 
>> (RestClient::InternalServerError)
>>  | 
>> /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.7.2/lib/runcible/base.rb:79:in
>>  
>> `block in

Re: [foreman-users] Metadata not found when syncing RHEL repositories

2016-09-14 Thread John Mitsch

Dylan,

Good to hear! Glad it was sorted out.

John

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

On Wed, Sep 14, 2016 at 1:00 AM, Dylan Baars  wrote:

> Hi John,
>
> that looks to have sorted it - in Katello, Content > Redhat Subscriptions
> > Manage Manifest. Clicked "Refresh manifest"
>
> Then Content > Sync Status
> Selected one of the RH repos > Synchronise now, and it completed
> successfully. Doing the others and they are all grabbing new files
> successfully - thanks!
>
> Dylan
>
> On Wednesday, September 14, 2016 at 10:02:05 AM UTC+12, John Mitsch wrote:
>>
>> Dylan,
>>
>> Looks like you are running into a known issue of pulp saying "not found"
>> when it means "forbidden"
>>
>> Can you try refreshing your manifest?
>>
>> Thanks,
>>
>> John Mitsch
>> Red Hat Engineering
>> (860)-967-7285
>> irc: jomitsch
>>
>> --
> 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] Metadata not found when syncing RHEL repositories

2016-09-14 Thread John Mitsch

Issue is fixed upstream in pulp already, here is the BZ
https://bugzilla.redhat.com/show_bug.cgi?id=1373662

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

On Tue, Sep 13, 2016 at 6:16 PM, Bryan Kearney 
wrote:

> On 09/13/2016 06:02 PM, John Mitsch wrote:
>
>> Dylan,
>>
>> Looks like you are running into a known issue of pulp saying "not found"
>> when it means "forbidden"
>>
>> Can you try refreshing your manifest?
>>
>
> issue number?
>
> -- bk
>
>
>> Thanks,
>>
>> John Mitsch
>> Red Hat Engineering
>> (860)-967-7285
>> irc: jomitsch
>>
>> On Mon, Sep 12, 2016 at 10:38 PM, Dylan Baars > > wrote:
>>
>> Hi all,
>>
>> we have been syncing RHEL repos from cdn.redhat.com
>>  without issue for a while, but now when I
>> attempt to sync any I get
>>
>> RPM1004: Error retrieving metadata: Not found
>>
>> in the GUI. If I try a sync and monitor /var/log/messages I see
>>
>> Sep 13 14:30:58 wellkatello.niwa.local pulp:
>> kombu.transport.qpid:INFO: Connected to qpid with SASL mechanism
>> ANONYMOUS
>> Sep 13 14:31:00 wellkatello.niwa.local pulp:
>> celery.worker.strategy:INFO: Received task:
>> pulp.server.async.tasks._queue_reserved_task[f284f6e7-215a-
>> 493e-9bc6-bf3d1a433ec8]
>> Sep 13 14:31:00 wellkatello.niwa.local pulp:
>> celery.worker.strategy:INFO: Received task:
>> pulp.server.managers.repo.sync.sync[981a01c6-fd95-42d4-8d6f-
>> e60470bf0fe9]
>> Sep 13 14:31:00 wellkatello.niwa.local pulp:
>> celery.worker.strategy:INFO: Received task:
>> pulp.server.async.tasks._release_resource[9dd3b103-26d7-
>> 4c8f-9ced-9dc785ca8f03]
>> Sep 13 14:31:00 wellkatello.niwa.local pulp: celery.worker.job:INFO:
>> Task
>> pulp.server.async.tasks._queue_reserved_task[f284f6e7-215a-
>> 493e-9bc6-bf3d1a433ec8]
>> succeeded in 0.125369669s: None
>> Sep 13 14:31:01 wellkatello.niwa.local pulp:
>> pulp_rpm.plugins.importers.yum.sync:INFO: Downloading metadata from
>> https://cdn.redhat.com/content/fastrack/rhel/server/7/x86_
>> 64/optional/os/
>> > 64/optional/os/>.
>> Sep 13 14:31:01 wellkatello.niwa.local pulp:
>> requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS
>> connection (1): cdn.redhat.com 
>> Sep 13 14:31:03 wellkatello.niwa.local pulp:
>> requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS
>> connection (1): cdn.redhat.com 
>>
>> Sep 13 14:31:03 wellkatello.niwa.local pulp:
>> pulp.server.async.tasks:INFO: Task failed :
>> [981a01c6-fd95-42d4-8d6f-e60470bf0fe9] : Error retrieving metadata:
>> Not found
>> Sep 13 14:31:04 wellkatello.niwa.local pulp: celery.worker.job:INFO:
>> Task
>> pulp.server.managers.repo.sync.sync[981a01c6-fd95-42d4-8d6f-
>> e60470bf0fe9]
>> raised expected: PulpCodedException()
>> Sep 13 14:31:04 wellkatello.niwa.local pulp: celery.worker.job:INFO:
>> Task
>> pulp.server.async.tasks._release_resource[9dd3b103-26d7-
>> 4c8f-9ced-9dc785ca8f03]
>> succeeded in 0.0117141319997s: None
>>
>> in /var/log/foreman/production.log I see
>>
>> 2016-09-13 14:37:12 [app] [I] Processing by
>> Katello::SyncManagementController#sync as JS
>> 2016-09-13 14:37:12 [app] [I]   Parameters: {"utf8"=>"✓",
>> "sync_status_url"=>"", "repoids"=>["69"], "commit"=>"Synchronize Now"}
>> 2016-09-13 14:37:15 [app] [I] Completed 200 OK in 2797ms (Views:
>> 0.8ms | ActiveRecord: 1701.8ms)
>> 2016-09-13 14:37:16 [app] [I] Started GET
>> "/katello/sync_management/sync_status?repoids%5B%5D=69&_=
>> 1473732915912"
>> for 192.168.222.132 at 2016-09-13 14:37:16 +1200
>> 2016-09-13 14:37:16 [app] [I] Processing by
>> Katello::SyncManagementController#sync_status as JSON
>> 2016-09-13 14:37:16 [app] [I]   Parameters: {"repoids"=>["69"],
>> "_"=>"1473732915912"}
>> 2016-09-13 14:37:16 [app] [I] Completed 200 OK in 94ms (Views: 0.7ms
>> | ActiveRecord: 12.9ms)
>> 2016-09-13 14:37:17 [app] [I] Started GET
>> "/katello/sync_management/sync_status?repoids%5B%5D=69&_=
>> 1473732915913"
>> for 192.168.222.132 at 2016-09-13 14:37:17 +1200
>> 2016-09-13 14:37:17 [app] [I] Processing by
>> Katello::SyncManagementController#sync_status as JSON
>> 2016-09-13 14:37:17 [app] [I]   Parameters: {"repoids"=>["69"],
>> "_"=>"1473732915913"}
>> 2016-09-13 14:37:18 [app] [I] Completed 200 OK in 102ms (Views:
>> 0.4ms | ActiveRecord: 12.0ms)
>> 2016-09-13 14:37:19 [app] [I] Started GET
>> "/katello/sync_management/sync_status?repoids%5B%5D=69&_=
>> 1473732915914"
>> for 192.168.222.132 at 2016-09-13 14:37:19 +1200
>> 2016-09-13 14:37:19 [foreman-tasks/action] [E] RPM1004: Error
>> retrieving metadata: Not found

Re: [foreman-users] Re: "No root file system is defined" error using preseed atomic partitioning scheme

2016-09-14 Thread Akash Kaveti

Hello Again,

It is working now, I have check the syslog, the device I am trying to 
install is not there it seems,
so I gave /dev/sdb, it is working now.

I am trying to install ubuntu by unattended installation on a hardware box.
I am using the default the partition template, I am not using LVM.
 
It is working for the current host, but what about the other hosts, Why 
cant I use "*d-i partman/early_command string debconf-set partman-auto/disk 
"$(list-devices disk | head -n1)*"

Thank you for the help, i have been struggling with this error from 
yesterday.

On Wednesday, September 14, 2016 at 1:52:33 PM UTC+2, Hauke Behrens wrote:
>
> Hi, 
>
> what kind of system are you trying to install to ? 
> KVM/Libvirt, a hardware box, something else ? 
> Are you maybe using LVM to provide the virtual disk ? 
>
> Please provide some more information on what you are trying to install 
> to. Maybe that will help to find the error. 
>
> I've also seen that error before, and in my cases it always was: 
> "trying to install to a wrong disk or "trying to install to non- 
> existant device". 
>
> One thing you can try is to switch to a different console 
> (ctrl+alt+f1,f2 etc.) during the install and checking syslog, to see 
> what commands are issued. 
> Check if the device really exists on the system or try another recipe. 
>
> Hauke 
>
>
>
>

-- 
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] 500 Internal Server Error when subscribing hosts

2016-09-14 Thread James Evans

Thank you for the response. I've seen several references to 
katello:reindex, but I don't seem to have that task on my production 
machine:

# foreman-rake katello:reindex
rake aborted!
Don't know how to build task 'katello:reindex'

(See full trace by running task with --trace)

Interestingly enough, I do seem to have the task on my test server. This is 
pretty confusing as I scripted out the install on both machines, so they 
*should* be identical. 
A quick look at rpm -qVa doesn't so anything obvious, what package provides 
this task?

james

On Tuesday, September 13, 2016 at 4:46:24 PM UTC-5, John Mitsch wrote:
>
> James,
>
> Try a couple things first:
>
> foreman-rake katello:reindex
> systemctl restart tomcat
>
> then
>  'tail -f -n 0 /var/log/candlepin/* /var/log/messages/ 
> /var/log/foreman/production.log' on your machine and retry the activation 
> key.
> Share that output with us (if its still erroring). It will be best to pipe 
> this to a file and attach it as it makes it easier to parse.
>
> Let me know if you have any questions.
>
> Thanks,
>
> John Mitsch
> Red Hat Engineering
> (860)-967-7285
> irc: jomitsch
>
> On Tue, Sep 13, 2016 at 4:54 PM, James Evans  > wrote:
>
>> I've been prototyping Foreman for a while now, and everything has been 
>> working perfectly in testing. Now I've built out our production deployment 
>> and imported content, and started trying to move hosts to the Foreman and 
>> Katello server. When ever I run subscription-manager register, from any 
>> host, I get 500 Internal Server Error, and the task hangs. I have to go 
>> into the dynaflow console and skip the broken step, and resume the task to 
>> clear locks.
>>
>> I've never had this happen in any of my tests where I've built a number 
>> of test servers to test out processes and configurations. All the test 
>> systems were able to register clients with no issues at all. The server and 
>> client are both fully updated RHEL 7.2 boxes, the server is 
>> running foreman-1.12.2-1.el7.noarch and katello-3.1.0-5.el7.noarch.
>>
>> The only other difference between the production and test is that I never 
>> imported RHEL content into the test systems.
>>
>> I've spent a week building out the products, repositories, content views, 
>> etc. and would really like to recover this without having to start over, 
>> but this is obviously a major problem!
>>
>> I've googled the errors, with out finding any thing. Can anyone help me?
>>
>> On the client I run:
>>
>> # subscription-manager register --org="myOrg" 
>> --activationkey="rhel-72-x86_64-production"
>> Task 1ac48d97-a570-4a43-9a09-b5cb0be7cf29: 
>> RestClient::InternalServerError: 500 Internal Server Error
>>
>> And the production.log contains (abbreviated):
>>
>> 2016-09-13 15:39:15 [app] [I] Started GET "/rhsm/" for XX.XX.XX.XX at 
>> 2016-09-13 15:39:15 -0500
>> 2016-09-13 15:39:15 [app] [I] Processing by 
>> Katello::Api::V2::RootController#rhsm_resource_list as JSON
>> 2016-09-13 15:39:15 [app] [I]   Parameters: {"root"=>{}}
>> 2016-09-13 15:39:15 [app] [I]   Rendered 
>> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.1.0.1/app/views/katello/api/v2/root/resource_list.json.rabl
>>  
>> within katello/api/v2/layouts/collection (2.4ms)
>> 2016-09-13 15:39:15 [app] [I] Completed 200 OK in 21ms (Views: 3.8ms | 
>> ActiveRecord: 0.0ms)
>> 2016-09-13 15:39:15 [app] [I] Started GET "/rhsm/status" for XX.XX.XX.XX 
>> at 2016-09-13 15:39:15 -0500
>> 2016-09-13 15:39:15 [app] [I] Processing by 
>> Katello::Api::Rhsm::CandlepinProxiesController#server_status as JSON
>> 2016-09-13 15:39:15 [app] [I] Completed 200 OK in 308ms (Views: 0.9ms | 
>> ActiveRecord: 0.0ms)
>> 2016-09-13 15:39:16 [app] [I] Started POST 
>> "/rhsm/consumers?owner=myOrg_keys=rhel-72-x86_64-production" for 
>> XX.XX.XX.XX at 2016-09-13 15:39:16 -0500
>> 2016-09-13 15:39:16 [app] [I] Processing by 
>> Katello::Api::Rhsm::CandlepinProxiesController#consumer_activate as JSON
>> 2016-09-13 15:39:16 [app] [I]   Parameters: {"facts"=>"[FILTERED]", 
>> "installedProducts"=>[{"productName"=>"Red Hat Enterprise Linux Server", 
>> "arch"=>"x86_64", "version"=>"7.2", "productId"=>"69"}], "type"=>"system", 
>> "name"=>"client.com", "contentTags"=>["rhel-7", "rhel-7-server"], 
>> "owner"=>"myOrg", "activation_keys"=>"rhel-72-x86_64-production"}
>> 2016-09-13 15:39:18 [app] [I] Import facts for 'client.example.com' 
>> completed. Added: 0, Updated: 1, Deleted 21 facts
>> 2016-09-13 15:39:21 [katello/pulp_rest] [E] RestClient.post "
>> https://foreman.example.com/pulp/api/v2/consumers/;, 
>> "{\"id\":\"1c796228-efa5-4190-b5de-a0f7605e3074\",\"display_name\":\"
>> client.example.com\"}", "Accept"=>"*/*; q=0.5, application/xml", 
>> "Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"100", 
>> "accept"=>"application/json", "content_type"=>"application/json"
>>  | \n# => 500 InternalServerError | application/json 2551 bytes
>>  | 
>> 2016-09-13 15:39:21 [foreman-tasks/action] [E]

Re: [foreman-users] Re: "No root file system is defined" error using preseed atomic partitioning scheme

2016-09-14 Thread Hauke Behrens

Hi,

what kind of system are you trying to install to ?
KVM/Libvirt, a hardware box, something else ?
Are you maybe using LVM to provide the virtual disk ?

Please provide some more information on what you are trying to install
to. Maybe that will help to find the error.

I've also seen that error before, and in my cases it always was:
"trying to install to a wrong disk or "trying to install to non-
existant device".

One thing you can try is to switch to a different console
(ctrl+alt+f1,f2 etc.) during the install and checking syslog, to see
what commands are issued.
Check if the device really exists on the system or try another recipe.

Hauke



-- 
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: "No root file system is defined" error using preseed atomic partitioning scheme

2016-09-14 Thread Akash Kaveti

Hi,

Thanks for the response, I have tried to install on different server as 
well, but got the same error,
Below I am pasting my partition template,

# Use the first detected hard disk as default installation disk
#d-i partman/early_command string debconf-set partman-auto/disk 
"$(list-devices disk | head -n1)"
d-i partman-auto/disk string dev/sda

### Partitioning
# The presently available methods are: "regular", "lvm" and "crypto"
d-i partman-auto/method string crypto

# If one of the disks that are going to be automatically partitioned
# contains an old LVM configuration, the user will normally receive a
# warning. This can be preseeded away...
d-i partman-lvm/device_remove_lvm boolean true
# The same applies to pre-existing software RAID array:
d-i partman-md/device_remove_md boolean true
# And the same goes for the confirmation to write the lvm partitions.
d-i partman-lvm/confirm boolean true
d-i partman-lvm/confirm_nooverwrite boolean true

# You can choose one of the three predefined partitioning recipes:
# - atomic: all files in one partition
# - home:   separate /home partition
# - multi:  separate /home, /var, and /tmp partitions (/usr was removed in 
jessie)
d-i partman-auto/choose_recipe select atomic

# If you just want to change the default filesystem to something
# else, you can do that without providing a full recipe.

# This makes partman automatically partition without confirmation, provided
# that you told it what to do using one of the methods above.
d-i partman/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true

Thank you.

On Tuesday, September 13, 2016 at 4:49:42 PM UTC+2, Akash Kaveti wrote:
>
> I am using preseed default as partitioning template, but when a host is 
> launched using that I got this error "No root file system is defined"
>

-- 
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: Foreman with vmware template

2016-09-14 Thread Anirudh T

Thank you very much guys, i created Userdata template as mentioned and it 
worked. Initially i tried with finish scripts + SSH but it use to hang.  
But now i am using userdata template without ssh and its working. 

On Wednesday, August 31, 2016 at 5:21:17 PM UTC+5:30, mso wrote:
>
> You need to configure
>
> In VMWARE
>
> - the template, i assume you have it
>
> in the template you need to have 
>
> - open-vm-tools install
> - ssh host keys cleaned out 
> - keys and certs for puppet clean out
>
> in foreman you need to have
>
> - the compute resource
> - the image
> - the compute profile 
> - the subnet
> - the provisioinng profile
>
> a provisioning template must include something like this 
>
> 
> identity:
>   LinuxPrep:
> domain: <%= @host.domain %>
> hostName: <%= @host.shortname %>
> hwClockUTC: true
> timeZone: Europe/Berlin
>
> globalIPSettings:
>   dnsSuffixList: 
> - <%= @host.domain %>
>   dnsServerList:
> - <%= @host.subnet.dns_primary %>
>   
> nicSettingMap:
> <% @host.interfaces.each do |interface| %>
>   - adapter:
>   dnsDomain: <%= interface.domain %>
>   dnsServerList: 
> - <%= interface.subnet.dns_primary %>
>   ip: <%= interface.ip %>
>   subnetMask: <%= interface.subnet.mask %>
>   gateway: 
> - <%= interface.subnet.gateway %>
>
> fqdn: <%= @host %>
> manage_etc_hosts: true
>
> 
>
> then  the foreman provides the IP address to VMWare and using the 
> open-vm-tools, the IP is injected into the machine similar to cloud-init 
> behaviour
>
> We have that running with CentOS and Ubuntu - but not with Debian ( look 
> at my post "Debian GNU/Linux 8 missing")
>
>
> Cheers
> Soeren
>
>
>
>

-- 
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] Should I upgrade regularly on Centos7?

2016-09-14 Thread Lukas Zapletal

> I notice that katello is up to 3.1 and 3.0.2 and Foreman is up to 1.12.2  
> (we have 1.11.4)
> 
> Is it worth upgrading regularly enough to get those fixes?
>  (also, how can I subscribe to this group?)

You need to understand how software packages are being upgraded. In
Foreman, we do major and minor releases. Usually you want to stay on
particular version as long as possible and only upgrade minor versions
(e.g. 1.11.X). You do this by regular update (yum upgrade).

These updates includes security issues and important regressions. So you
absolutely want these.

We only support two major releases, so when 1.13 comes out in few weeks,
1.11 will become unsupported, so I'd suggest you to upgrade. Follow our
instructions at:

https://theforeman.org/manuals/1.3/index.html#3.6Upgrade

When using katello use:

http://www.katello.org/docs/3.0/upgrade/index.html

to make the upgrade.

Remember to BACKUP your instance before upgrading, I highly recommend to
do this also for minor updates.

It brings interesting question - since Katello now uses
foreman-installer, shall we move the install/upgrade instructions to
theforeman.org? Do we also have upgrade procedure to the first version
which uses the new approach?

-- 
Later,
 Lukas #lzap Zapletal

-- 
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] search host very slow in foreman

2016-09-14 Thread Lukas Zapletal

> what was the search query that you used?

And do you experience this when loading "intelligent completion" or when
doing actual query?

Are you able to enable slow queries logging in your postgres and send us
the output?

https://wiki.postgresql.org/wiki/Logging_Difficult_Queries

Easiest is to set log_min_duration_statement to reasonable value (1
second).

-- 
Later,
 Lukas #lzap Zapletal

-- 
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] Validation failed: Description has already been taken, Title has already been taken

2016-09-14 Thread Tomer Brisker

Hi David,

Glad to hear this fixed the issue.

When a host reports facts that don't match its current settings, such as a
different OS, that host will be updated with the new values.
This is expected behaviour -
https://theforeman.org/manuals/1.13/index.html#creating-hosts-in-foreman-with-facts
The 7.2 OS was most likely created by the incorrect fact parsing ignoring
the second part of the minor version.

Thanks for your help!
Tomer


On Wed, Sep 14, 2016 at 5:01 AM, David LeVene 
wrote:

> Hi Tomer,
>
> Thanks, It works as expected - but what I did notice is that with this
> change when I've got the Operating systems defined as noted in a previous
> post, a host was moved from CentOS 7.2 -> CentOS 7.2.1511. What happens
> when users Patch a host and it goes to the next CentOS version of 7.3.?
> I presume it will create a new host with that major/minor version.
>
> If users have something similar configured, this patch may move hosts to a
> different OS without their knowledge - This host was the original foreman
> host, so I suspect it checked in and configured its self before I manually
> created the other OS's, hence it was working and not reporting errors
>
>
> Results of same host after updating the code:
>
> 2016-09-14 11:13:34 [app] [I] Processing by Api::V2::HostsController#facts
> as JSON
> 2016-09-14 11:13:34 [app] [I]   Parameters: {"facts"=>"[FILTERED]",
> "name"=>"testing-dlevene", "certname"=>"testing-dlevene", "apiv"=>"v2",
> :host=>{"name"=>"testing-dlevene",
>  "certname"=>"testing-dlevene"}}
> 2016-09-14 11:13:34 [app] [I] Import facts for 'testing-dlevene'
> completed. Added: 0, Updated: 6, Deleted 0 facts
> 2016-09-14 11:13:34 [app] [I] Completed 201 Created in 434ms (Views: 5.5ms
> | ActiveRecord: 109.2ms)
>
> Let me know if there is any further testing you require on my end.
>
> Regards
> David
>
>
> On 13 September 2016 at 18:32, Tomer Brisker  wrote:
>
>> Hi David,
>>
>> The fix is ready for testing in https://github.com/theforem
>> an/foreman/pull/3836
>>
>> Thanks
>> Tomer
>>
>> On Tue, Sep 13, 2016 at 3:11 AM, David LeVene 
>> wrote:
>>
>>> Hi Tomer,
>>>
>>> Great that you've been able to reproduce it.
>>>
>>> Yep - let me know when I can test it.
>>>
>>> Regards
>>> David
>>>
>>> On 12 September 2016 at 05:07, Tomer Brisker 
>>> wrote:
>>>
 Thank you for the information David!

 I have managed to reproduce the issue locally and will work to resolve
 it.
 It would seem that indeed the cause lies with the OS that has a
 non-numeric minor version (2.1511).
 I will let you know once I have a pull request ready to fix the issue
 so you may test it.

 Have a nice week,
 Tomer

 On Fri, Sep 9, 2016 at 5:39 AM, David LeVene 
 wrote:

> Hi Tomer,
>
> I've just reverted to a database backup which has the issue - and here
> is the information you requested
>
> foreman=# select * from operatingsystems;
>  id | major |  name  | minor  | nameindicator |
> created_at | updated_at | release_name |  type
> |  description  | hosts_count | hostgroups_count | password_hash
> | title
> +---+++---+-
> ---++--+
> +---+-+-
> -+---+---
>   3 | 7 | CentOS | 2  |   | 2016-01-13
> 02:34:09.557672 | 2016-01-13 02:34:09.557672 |  | Redhat
> |   |   1 |0 | SHA256|
> CentOS 7.2
>   1 | 7 | CentOS | 1  |   | 2015-12-07
> 03:23:39.087921 | 2015-12-16 06:38:11.025759 |  | Redhat |
> CentOS Linux 7.1.1503 |   0 |0 | SHA256|
> CentOS Linux 7.1.1503
>   2 | 7 | CentOS | 2.1511 |   | 2015-12-16
> 07:40:19.21053  | 2016-01-13 02:21:43.201217 |  | Redhat |
> CentOS Linux 7.2.1511 |   6 |0 | SHA256|
> CentOS Linux 7.2.1511
> (3 rows)
>
>
> {"name"=>"CentOS", "family"=>"RedHat", "release"=>{"major"=>"7",
> "minor"=>"2", "full"=>"7.2.1511"}, "lsb"=>{"distcodename"=>"Core",
> "distid"=>"CentOS", "distdescription"=>"CentOS Linux release 7.2.1511
> (Core) ", "release"=>":core-4.1-amd64:core-4.1-noarch",
> "distrelease"=>"7.2.1511", "majdistrelease"=>"7", 
> "minordistrelease"=>"2"}}
>
> 2016-09-09 12:05:52 [app] [I] Import facts for 'testing completed.
> Added: 0, Updated: 9, Deleted 0 facts
> 2016-09-09 12:05:53 [app] [W] Action failed
>  | ActiveRecord::RecordInvalid: Validation failed: Description has
> already been taken, Title has already been taken
>

[foreman-users] Should I upgrade regularly on Centos7?

2016-09-14 Thread Lachlan Musicman

We have an otherwise up to date Centos 7 vm running 
Katello/Foreman/"satellite 6". From the about page


   - foreman-installer-katello-3.0.2-1.el7.noarch
   - katello-3.0.0-9.el7.noarch
   - katello-agent-2.5.0-3.el7.noarch


I notice that katello is up to 3.1 and 3.0.2 and Foreman is up to 1.12.2  
(we have 1.11.4)

Is it worth upgrading regularly enough to get those fixes?
 (also, how can I subscribe to this group?)

cheers
L.

-- 
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] Could not find kernel image: linux

[foreman-users] Puppet Server Stop After OS Update

Re: [foreman-users] 500 Internal Server Error when subscribing hosts

Re: [foreman-users] Re: "No root file system is defined" error using preseed atomic partitioning scheme

Re: [foreman-users] 500 Internal Server Error when subscribing hosts

Re: [foreman-users] Metadata not found when syncing RHEL repositories

Re: [foreman-users] Metadata not found when syncing RHEL repositories

Re: [foreman-users] Re: "No root file system is defined" error using preseed atomic partitioning scheme

Re: [foreman-users] 500 Internal Server Error when subscribing hosts

Re: [foreman-users] Re: "No root file system is defined" error using preseed atomic partitioning scheme

[foreman-users] Re: "No root file system is defined" error using preseed atomic partitioning scheme

[foreman-users] Re: Foreman with vmware template

Re: [foreman-users] Should I upgrade regularly on Centos7?

Re: [foreman-users] search host very slow in foreman

Re: [foreman-users] Validation failed: Description has already been taken, Title has already been taken

[foreman-users] Should I upgrade regularly on Centos7?

16 matches

Site Navigation

Mail list logo

Footer information