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

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.

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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:

[foreman-users] Puppet Server Stop After OS Update

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

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

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

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

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

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

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

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

> 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

[foreman-users] Re: Foreman with vmware template

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

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

> 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