Re: [foreman-users] katello 3.3
This did the trick. # foreman-rake foreman_tasks:cleanup TASK_SEARCH='label="Actions::Katello::Host::Erratum::ApplicableErrataInstall"' STATES="paused" Thanks for the insight. On Monday, 30 October 2017 14:13:24 UTC-6, pascalp wrote: > > You could try to either stop the tasks by label - example: > > sudo foreman-rake foreman_tasks:cleanup > TASK_SEARCH='label="Actions::Katello::Repository::Sync"' STATES="running" > NOOP=true > > or by id - example: > > sudo foreman-rake foreman_tasks:cleanup > TASK_SEARCH='id="aa929825-4fc6-4138-9b12-d3d4d00426cc"' STATES="running" > NOOP=true > > You might have to modify the "STATES" parameter (running/paused). Running > the commands with "NOOP=true" does not actually do anything but shows you > how many tasks would be removed were you to remove said parameter. > > Hope this helps. > Pascal > > On Monday, October 30, 2017 at 8:04:09 PM UTC+1, Edward Clay wrote: >> >> Looking at this futher, it looks like the katello-tracer-uploader is >> available for COS7 but I'm not finding it for CentOS 6.x. >> >> On Wednesday, 25 October 2017 15:25:47 UTC-6, Lachlan Musicman wrote: >>> >>> On 26 October 2017 at 04:39, Edward Clay <edwar...@uk2group.com> wrote: >>> >>>> I have some host that I attempted to apply applicable erratas to in a >>>> large group of host. During that task some host failed and others >>>> completed. I can't remember why they failed but I was able to manually >>>> update the systems once I fixed the issues with these host. Now I have >>>> several paused "apply applicable erratas" task for these host and I can't >>>> get them to resume nor cancel. I'm not sure how to clean this up since >>>> It's preventing me from updating to katello 3.4. >>>>> >>>>> >>>>>> >>>>>> errors in paused task: >>>>>> >>>>>> 404 Resource Not Found >>>>>> >>>>>> and >>>>>> >>>>>> host did not respond within 20 seconds. The task has been canceled. >>>>>> Is katello-agent installed and goferd running on the Host? >>>>>> >>>>>> the katello agent is installed on all managed host and the goferd >>>>>> agent is running. I've even tried to restart the goferd agent without >>>>>> success. >>>>>> >>>>> >>>>> I am not an expert on Katello by any stretch, but I have seen this >>>>> before and these are two methods I've used: >>>>> - try running katello-tracer-upload from the affected hosts. If that >>>>> doesn't work, >>>>> - rebooting the Foreman server does. You probably don't need to go >>>>> that far. Maybe just "systemctl restart foreman-tasks" >>>>> >>>>> >>>>> Looking at one of my servers I'm not finding a katello-tracer-upload. >>>> I do see a katell-package-uploader and katello-rhsm-cunsumer. "yum >>>> provides */katello-tracer-upload" reruns no results. >>>> >>>> After rebooting the foreman server i still get a fail on the upgrade >>>> check stating that 15 active task. The only thing I can find are these >>>> same failed apply erratas task. >>>> >>>> >>>> >>> >>> My search shows that katello-tracer-upload comes from >>> katello-agent-3.0.0-2 or katello-host-tools-3.0.2-1 (caveat: I am using the >>> katello 3.4 repo) - look for those packages? >>> >>> cheers >>> L. >>> >>> >>> -- >>> "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic >>> civics is the insistence that we cannot ignore the truth, nor should we >>> panic about it. It is a shared consciousness that our institutions have >>> failed and our ecosystem is collapsing, yet we are still here — and we are >>> creative agents who can shape our destinies. Apocalyptic civics is the >>> conviction that the only way out is through, and the only way through is >>> together. " >>> >>> *Greg Bloom* @greggish >>> https://twitter.com/greggish/status/873177525903609857 >>> >> -- 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] katello 3.3
Does anyone know of a katello-tracer-upload equivalent command for centos 6.x? I've tried katello-package-upload -f but it doesn't seem to have the same affect as katello-trace-upload. Also it seems odd that the 3.4 agent/client would be so different between OS versions. On Monday, 30 October 2017 13:04:09 UTC-6, Edward Clay wrote: > > Looking at this futher, it looks like the katello-tracer-uploader is > available for COS7 but I'm not finding it for CentOS 6.x. > > On Wednesday, 25 October 2017 15:25:47 UTC-6, Lachlan Musicman wrote: >> >> On 26 October 2017 at 04:39, Edward Clay <edwar...@uk2group.com> wrote: >> >>> I have some host that I attempted to apply applicable erratas to in a >>> large group of host. During that task some host failed and others >>> completed. I can't remember why they failed but I was able to manually >>> update the systems once I fixed the issues with these host. Now I have >>> several paused "apply applicable erratas" task for these host and I can't >>> get them to resume nor cancel. I'm not sure how to clean this up since >>> It's preventing me from updating to katello 3.4. >>>> >>>> >>>>> >>>>> errors in paused task: >>>>> >>>>> 404 Resource Not Found >>>>> >>>>> and >>>>> >>>>> host did not respond within 20 seconds. The task has been canceled. >>>>> Is katello-agent installed and goferd running on the Host? >>>>> >>>>> the katello agent is installed on all managed host and the goferd >>>>> agent is running. I've even tried to restart the goferd agent without >>>>> success. >>>>> >>>> >>>> I am not an expert on Katello by any stretch, but I have seen this >>>> before and these are two methods I've used: >>>> - try running katello-tracer-upload from the affected hosts. If that >>>> doesn't work, >>>> - rebooting the Foreman server does. You probably don't need to go >>>> that far. Maybe just "systemctl restart foreman-tasks" >>>> >>>> >>>> Looking at one of my servers I'm not finding a katello-tracer-upload. >>> I do see a katell-package-uploader and katello-rhsm-cunsumer. "yum >>> provides */katello-tracer-upload" reruns no results. >>> >>> After rebooting the foreman server i still get a fail on the upgrade >>> check stating that 15 active task. The only thing I can find are these >>> same failed apply erratas task. >>> >>> >>> >> >> My search shows that katello-tracer-upload comes from >> katello-agent-3.0.0-2 or katello-host-tools-3.0.2-1 (caveat: I am using the >> katello 3.4 repo) - look for those packages? >> >> cheers >> L. >> >> >> -- >> "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic >> civics is the insistence that we cannot ignore the truth, nor should we >> panic about it. It is a shared consciousness that our institutions have >> failed and our ecosystem is collapsing, yet we are still here — and we are >> creative agents who can shape our destinies. Apocalyptic civics is the >> conviction that the only way out is through, and the only way through is >> together. " >> >> *Greg Bloom* @greggish >> https://twitter.com/greggish/status/873177525903609857 >> > -- 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] katello 3.3
Looking at this futher, it looks like the katello-tracer-uploader is available for COS7 but I'm not finding it for CentOS 6.x. On Wednesday, 25 October 2017 15:25:47 UTC-6, Lachlan Musicman wrote: > > On 26 October 2017 at 04:39, Edward Clay <edwar...@uk2group.com > > wrote: > >> I have some host that I attempted to apply applicable erratas to in a >> large group of host. During that task some host failed and others >> completed. I can't remember why they failed but I was able to manually >> update the systems once I fixed the issues with these host. Now I have >> several paused "apply applicable erratas" task for these host and I can't >> get them to resume nor cancel. I'm not sure how to clean this up since >> It's preventing me from updating to katello 3.4. >>> >>> >>>> >>>> errors in paused task: >>>> >>>> 404 Resource Not Found >>>> >>>> and >>>> >>>> host did not respond within 20 seconds. The task has been canceled. >>>> Is katello-agent installed and goferd running on the Host? >>>> >>>> the katello agent is installed on all managed host and the goferd agent >>>> is running. I've even tried to restart the goferd agent without success. >>>> >>> >>> I am not an expert on Katello by any stretch, but I have seen this >>> before and these are two methods I've used: >>> - try running katello-tracer-upload from the affected hosts. If that >>> doesn't work, >>> - rebooting the Foreman server does. You probably don't need to go that >>> far. Maybe just "systemctl restart foreman-tasks" >>> >>> >>> Looking at one of my servers I'm not finding a katello-tracer-upload. I >> do see a katell-package-uploader and katello-rhsm-cunsumer. "yum provides >> */katello-tracer-upload" reruns no results. >> >> After rebooting the foreman server i still get a fail on the upgrade >> check stating that 15 active task. The only thing I can find are these >> same failed apply erratas task. >> >> >> > > My search shows that katello-tracer-upload comes from > katello-agent-3.0.0-2 or katello-host-tools-3.0.2-1 (caveat: I am using the > katello 3.4 repo) - look for those packages? > > cheers > L. > > > -- > "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic > civics is the insistence that we cannot ignore the truth, nor should we > panic about it. It is a shared consciousness that our institutions have > failed and our ecosystem is collapsing, yet we are still here — and we are > creative agents who can shape our destinies. Apocalyptic civics is the > conviction that the only way out is through, and the only way through is > together. " > > *Greg Bloom* @greggish > https://twitter.com/greggish/status/873177525903609857 > -- 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] katello 3.3
On Tuesday, 17 October 2017 16:48:37 UTC-6, Lachlan Musicman wrote: > > On 18 October 2017 at 09:20, Edward Clay <edwar...@uk2group.com > > wrote: > >> I have some host that I attempted to apply applicable erratas to in a >> large group of host. During that task some host failed and others >> completed. I can't remember why they failed but I was able to manually >> update the systems once I fixed the issues with these host. Now I have >> several paused "apply applicable erratas" task for these host and I can't >> get them to resume nor cancel. I'm not sure how to clean this up since >> It's preventing me from updating to katello 3.4. >> >> >> errors in paused task: >> >> 404 Resource Not Found >> >> and >> >> host did not respond within 20 seconds. The task has been canceled. Is >> katello-agent installed and goferd running on the Host? >> >> the katello agent is installed on all managed host and the goferd agent >> is running. I've even tried to restart the goferd agent without success. >> > > I am not an expert on Katello by any stretch, but I have seen this before > and these are two methods I've used: > - try running katello-tracer-upload from the affected hosts. If that > doesn't work, > - rebooting the Foreman server does. You probably don't need to go that > far. Maybe just "systemctl restart foreman-tasks" > > Cheers > L. > > > Thanks for your reply. Looking at one of my servers I'm not finding a katello-tracer-upload. I do see a katell-package-uploader and katello-rhsm-cunsumer. "yum provides */katello-tracer-upload" reruns no results. After rebooting the foreman server i still get a fail on the upgrade check stating that 15 active task. The only thing I can find are these same failed apply erratas task. -- 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] katello 3.3
I have some host that I attempted to apply applicable erratas to in a large group of host. During that task some host failed and others completed. I can't remember why they failed but I was able to manually update the systems once I fixed the issues with these host. Now I have several paused "apply applicable erratas" task for these host and I can't get them to resume nor cancel. I'm not sure how to clean this up since It's preventing me from updating to katello 3.4. errors in paused task: 404 Resource Not Found and host did not respond within 20 seconds. The task has been canceled. Is katello-agent installed and goferd running on the Host? the katello agent is installed on all managed host and the goferd agent is running. I've even tried to restart the goferd agent without success. -- 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 host complain after stopping puppet agent
That setting is already set to "No". I've edited a host and removed Puppet Environment, Puppet Master and Puppet CA to contain no puppet host. I've also stopped/disabled the puppet agent and the host shows out of sync and the status is orange. Not sure what I'm missing here. On Wednesday, 26 July 2017 03:05:01 UTC-6, Daniel Lobato wrote: > > On 07/25, Edward Clay wrote: > > Hello, > > > > I'm trying to figure out how to get foreman to stop complaining on the > all > > hosts page that a host hasn't checked in via the puppet agent. If I > setup > > create a new host then build it and don't install the puppet agent and > run > > it then this host won't report that it's never or hasn't checked in in > the > > past 35 minutes. The only option I can think of is to remove/delete the > > host from foreman and recreate it once the puppet agent is no longer. > > Not sure what you mean about complaining, but if you mean the little 'red' > status, it's possible to disable the configuration status by going to: > > Administer > Settings > Puppet tab > "Always show configuration status" > - set to no > > If you create hosts without Puppet smart proxies and this option is set > to no, the status will not take into account Puppet. > > > > > -- > > 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-user...@googlegroups.com . > > To post to this group, send email to forema...@googlegroups.com > . > > Visit this group at https://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/d/optout. > > > -- > Daniel Lobato Garcia > > @dLobatog > blog.daniellobato.me > daniellobato.me > > GPG: http://keys.gnupg.net/pks/lookup?op=get=0x7A92D6DD38D6DE30 > Keybase: https://keybase.io/elobato > -- 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 host complain after stopping puppet agent
Hello, I'm trying to figure out how to get foreman to stop complaining on the all hosts page that a host hasn't checked in via the puppet agent. If I setup create a new host then build it and don't install the puppet agent and run it then this host won't report that it's never or hasn't checked in in the past 35 minutes. The only option I can think of is to remove/delete the host from foreman and recreate it once the puppet agent is no longer. -- 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] provisioning a system with two NIC
I would like to apologize for my mistake here. Looks like I had setup
the public network/subnet as dhcp instead of static. Once I did all
was better. I can now provision a server and the public interface is
configured using the static IP while the internal one is configured
using dhcp.
Thanks for the help.
On Wed, 2017-05-24 at 08:39 +0200, Lukas Zapletal wrote:
> So the output artifact is rhcfg network configuration file, that's
> clear. You probably struggle with our ERB templating engine, it's
> actually ERB (google that) bug in SafeMode which means only selected
> variables and functions are available. In Foreman 1.14+ there is a
> Help tab in the Template editor which shows you the list.
>
> LZ
>
> On Tue, May 23, 2017 at 8:52 PM, Edward Clay <edward.c...@uk2group.co
> m> wrote:
> > Lukas, Thanks for this information. I gues what I need to do is
> > figure
> > out how to create my own snippet since most of this info isn't
> > clear to
> > me. Where would be the best place to start learning how to do
> > this?
> >
> > On Tue, 2017-05-23 at 09:05 +0200, Lukas Zapletal wrote:
> > > Hello,
> > >
> > > in this case you want to leave default kickstart template
> > > "network"
> > > configuration as is and only change post configuration for
> > > network:
> > >
> > > https://github.com/theforeman/community-templates/blob/develop/pr
> > > ovis
> > > ioning_templates/snippet/kickstart_networking_setup.erb
> > >
> > > This is a snippet that is inserted into default kickstart:
> > >
> > > <%= snippet 'kickstart_networking_setup' %>
> > >
> > > You perhaps want to create new snippet and configure your cards
> > > to
> > > your needs. That's the easiest method.
> > >
> > > You an also provide some flag (host parameter) that will override
> > > the
> > > default behavior and configure NIC as static, then you can add
> > > this
> > > parameter to hostgroup or something. You can do pretty much
> > > anything
> > > you want.
> > >
> > > But if you want to start with PXE and then "switch" to static at
> > > some
> > > point, Foreman itself does not support that. You can use Bootdisk
> > > instead of PXE which will work with static IP allocations tho.
> > >
> > > LZ
> > >
> > > On Tue, May 23, 2017 at 12:29 AM, Edward Clay <Edward.Clay@uk2gro
> > > up.c
> > > om> wrote:
> > > > Hello, I am trying to figure out how to best configure my
> > > > katello/foreman
> > > > provisioning kickstart template to configure a system with 2
> > > > NIC's. One nic
> > > > is configured for private communication via a non routable ip
> > > > range. We can
> > > > assign these IPs via dhcpd which we then use for doing the
> > > > provisioning
> > > > process via a local OS repo hosted on the katello/foreman
> > > > server. The
> > > > second NIC is publicly accessible and is assigned
> > > > statically. What
> > > > I'm not
> > > > sure how to do is pxe booting via the private interface
> > > > (currently
> > > > done by
> > > > assigning via dhcpd) and configuring both NIC via static
> > > > assignment
> > > > after
> > > > the provisioning process is complete. It seems like I had this
> > > > working but
> > > > it's been a long time since I tinkered with this so my memory
> > > > could
> > > > be
> > > > wrong. I believe this line was working in the past.
> > > >
> > > > network --bootproto <%= dhcp ? 'dhcp --nodefroute' : "static
> > > > --ip=#{@host.ip} --netmask=#{subnet.mask} --
> > > > gateway=#{subnet.gateway}
> > > > --nameserver=#{[subnet.dns_primary,
> > > > subnet.dns_secondary].select(&:present?).join(',')}" %> --
> > > > hostname
> > > > <%= @host
> > > > %><%= os_major >= 6 ? " --device=#{@host.mac}" : '' -%>
> > > >
> > > > I've configured the private NIC as Managed and Provision while
> > > > the
> > > > Public
> > > > NIC is configured as Primary.
> > > >
> > > > Are there any working solutions out there for this scenario?
> > > >
> > > > --
> > > > You received this
Re: [foreman-users] provisioning a system with two NIC
Thanks for directing me towards help. Looking at the
kickstart_networking_sertup it seems to mention that it's going to
setup the primary interface. When I look at the template details using
the spoof thing with the Host IP it only seems to show details about
the non primary interface.
This is what I see in the kickstart when I view it.
# enp6s0 interface
real=`ip -o link | grep 00:25:90:09:57:e4 | awk '{print $2;}' | sed
s/:$//`
# ifcfg files are ignored by NM if their name contains colons so we
convert colons to underscore
sanitized_real=$real
cat << EOF > /etc/sysconfig/network-scripts/ifcfg-$sanitized_real
BOOTPROTO="dhcp"
DEVICE=$real
HWADDR="00:25:90:09:57:e4"
ONBOOT=yes
PEERDNS=no
PEERROUTES=no
DEFROUTE=no
EOF
This isn't the primary interface. The interface configured as primary
in foreman is one where the MAC address ends in 57:e5. The
kickstart_default template is calling the kickstart_networking_setup
which says the following.
<%#
kind: snippet
name: kickstart_networking_setup
description: this will configure your host networking, it configures
your primary interface as well
as other configures NICs. It supports physical, VLAN and Alias
interfaces. It's intended to be
called from %post in your kickstart template. Note that this
snippet can be used with Foreman 1.7
and later
%>
This makes me think that this script should be doing what I am
expecting, configure the network interfaces based on the host
configuration in foreman.
On Wed, 2017-05-24 at 08:39 +0200, Lukas Zapletal wrote:
> So the output artifact is rhcfg network configuration file, that's
> clear. You probably struggle with our ERB templating engine, it's
> actually ERB (google that) bug in SafeMode which means only selected
> variables and functions are available. In Foreman 1.14+ there is a
> Help tab in the Template editor which shows you the list.
>
> LZ
>
> On Tue, May 23, 2017 at 8:52 PM, Edward Clay <edward.c...@uk2group.co
> m> wrote:
> > Lukas, Thanks for this information. I gues what I need to do is
> > figure
> > out how to create my own snippet since most of this info isn't
> > clear to
> > me. Where would be the best place to start learning how to do
> > this?
> >
> > On Tue, 2017-05-23 at 09:05 +0200, Lukas Zapletal wrote:
> > > Hello,
> > >
> > > in this case you want to leave default kickstart template
> > > "network"
> > > configuration as is and only change post configuration for
> > > network:
> > >
> > > https://github.com/theforeman/community-templates/blob/develop/pr
> > > ovis
> > > ioning_templates/snippet/kickstart_networking_setup.erb
> > >
> > > This is a snippet that is inserted into default kickstart:
> > >
> > > <%= snippet 'kickstart_networking_setup' %>
> > >
> > > You perhaps want to create new snippet and configure your cards
> > > to
> > > your needs. That's the easiest method.
> > >
> > > You an also provide some flag (host parameter) that will override
> > > the
> > > default behavior and configure NIC as static, then you can add
> > > this
> > > parameter to hostgroup or something. You can do pretty much
> > > anything
> > > you want.
> > >
> > > But if you want to start with PXE and then "switch" to static at
> > > some
> > > point, Foreman itself does not support that. You can use Bootdisk
> > > instead of PXE which will work with static IP allocations tho.
> > >
> > > LZ
> > >
> > > On Tue, May 23, 2017 at 12:29 AM, Edward Clay <Edward.Clay@uk2gro
> > > up.c
> > > om> wrote:
> > > > Hello, I am trying to figure out how to best configure my
> > > > katello/foreman
> > > > provisioning kickstart template to configure a system with 2
> > > > NIC's. One nic
> > > > is configured for private communication via a non routable ip
> > > > range. We can
> > > > assign these IPs via dhcpd which we then use for doing the
> > > > provisioning
> > > > process via a local OS repo hosted on the katello/foreman
> > > > server. The
> > > > second NIC is publicly accessible and is assigned
> > > > statically. What
> > > > I'm not
> > > > sure how to do is pxe booting via the private interface
> > > > (currently
> > > > done by
> > > > assigning via dhcpd) and configuring both NIC via static
> > > > assignment
> > > > after
> > > > the provisioning proces
[foreman-users] foreman 1.14.3-1 ansible RHEL/CentOS errata
Hello, I'm wondering if it's possible to replace or reproduce the features in forman/puppet to check the errata status in foreman and also apply install the updates from the web gui. We have the ansible plugin installed and functioning but it seems like I can only get this functionality from host I initially setup using puppet. Any thoughts ideas of how this can be done would be appreciated. -- 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: repo not showig all packages synced locally
Should of included that I'm I'm running katello 3.3.1-1 with foreman 1.14.3-1. On Tuesday, 9 May 2017 15:05:59 UTC-6, Edward Clay wrote: > > Hello, > > I'm experiencing a strange issue where I've created a product with one > repo that points syncs content from the following url. > > http://repo.r1soft.com/yum/stable/x86_64/ > > and it seems to successfully sync data locally from this remote repo but > when I look at the repo's url on my system I don't see all rpms that should > be available. What I mean by this the repo shows 23 packages available but > I only see the following browsing to the repos publish at url. > > Parent Directory > <http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/> > >- repodata/ > > <http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/repodata/> >- r1soft-docstore-6.2.2-78.x86_64.rpm > > <http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/r1soft-docstore-6.2.2-78.x86_64.rpm> >- r1soft-getmodule-1.0.0-51.x86_64.rpm > > <http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/r1soft-getmodule-1.0.0-51.x86_64.rpm> >- serverbackup-agent-6.2.2.x86_64.rpm > > <http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/serverbackup-agent-6.2.2.x86_64.rpm> >- serverbackup-async-agent-2-6-6.2.2.x86_64.rpm > > <http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/serverbackup-async-agent-2-6-6.2.2.x86_64.rpm> >- serverbackup-enterprise-6.2.2.x86_64.rpm > > <http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/serverbackup-enterprise-6.2.2.x86_64.rpm> >- serverbackup-enterprise-agent-6.2.2.x86_64.rpm > > <http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/serverbackup-enterprise-agent-6.2.2.x86_64.rpm> >- serverbackup-setup-6.2.2.x86_64.rpm > > <http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/serverbackup-setup-6.2.2.x86_64.rpm> > > > When I attempt to do a yum upgrade using this repo the server fails to > download the needed, supossadly available, packages with the following > error. > > Error Downloading Packages: > serverbackup-manager-6.2.2-78.x86_64: failure: > serverbackup-manager-6.2.2.x86_64.rpm from UK2_Group_r1soft_cdp_server_cdp: > [Errno 256] No more mirrors to try. > > There are not any filtered content views involved here the product > activation key we use is configured to use the default organization view. > > I'm not sure of what else I should check or how to troubleshoot this 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: Katello 3.2 > 3.3 upgrade with custom signed ssl certs breaks pulp
I ended up restoring from backup to the previous version 3.2 and things are working. I would like very much to figure out how to revert back to self signed ssl certs and do away with using the 3rd party signed ones. Since I ran foreman-installer with some options to use the 3rd party signed ssl certs you would think this would be a simple task. -- 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] Katello 3.2 > 3.3 upgrade with custom signed ssl certs breaks pulp
Hello, I've run into an issue where after upgrading a working katello 3.2 system to 3.3 I get the following error when attempting to publish a content view. There was an issue with the backend service pulp: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed When the system was running katello 3.2 I rand the following to get the custom signed ssl certs to work. foreman-installer --scenario katello --certs-server-cert /etc/pki/tls/certs/il-foreman1_slc_westdc_net.crt --certs-server-cert-req /etc/pki/tls/private/il-foreman1.slc.westdc.net.csr --certs-server-key /etc/pki/tls/private/il-foreman1.slc.westdc.net.key --certs-server-ca-cert /etc/pki/tls/certs/comodo-ca-bundle.crt --certs-server-ca-name comodo-ca --certs-update-server --certs-update-server-ca To fix problems with candlepin I did the following found via http://projects.theforeman.org/issues/16620 Copy /root/ssl-build/katello-default-ca.crt to /etc/pki/ca-trust/source/anchors/ and rebuild the openssl ca certs with update-ca-trust. Due to chicken-and-egg issue, this may prevent a clean install using custom certs. After performing these steps, re-run the installer. It should complete correctly the second time through. I've attempted both of theses steps along with the second fix on the above url for issue 16620 without any success. I see the following details in the /etc/foreman/plugins/katello.yaml ### File managed with puppet ### ## Module: puppet-katello :katello: :rest_client_timeout: 3600 :post_sync_url: https://il-foreman1.domain.net/katello/api/v2/repositories/sync_complete?token=gQ7efFZPwo8oWXg9abmdG3v8gkY29fcs :candlepin: :url: https://il-foreman1.domain.net:8443/candlepin :oauth_key: katello :oauth_secret: qXZyiEhe8WqoCeTtPJqhpUGCPV65GmeL :ca_cert_file: /etc/pki/katello/certs/katello-default-ca.crt :pulp: :url: https://il-foreman1.domain.net/pulp/api/v2/ :oauth_key: katello :oauth_secret: qXZyiEhe8WqoCeTtPJqhpUGCPV65GmeL :ca_cert_file: /etc/pki/katello/certs/katello-default-ca.crt :qpid: :url: amqp:ssl:localhost:5671 :subscriptions_queue_address: katello_event_queue I'm not sure what additional information to provide to help identify the problem here. Any ideas what to try/do next? Thanks -- 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] Content view with filtered errata still showing alert on host
Hello, I've run into an interesting problem. I have some servers that run cPanel and since they get some rpms/software from non redhat locations/repos we have a conflict where foreman thinks that an errata for exim is required on a cpanel server but it's not installable because cPanel provides a patched version via there repo. So to try and get rid of the red alert for this server I created a content view and included all of the needed products/repos and then filtered the errata in question. Next I created a new activation key for this content view and registered the host using this activation key. After doing all of this the host still shows a red alert that a security errata is applicable to this host. When I look at the erratas it shows no installable host available. This makes me think that the exclusion is working but somehow the display of the status of this host in the foreman web app still thinks the errata should be applied. Is this normally how foreman works when excluding an errata? How can I get this host to show happy green status in foreman? -- 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.
