[foreman-users]
With both http://yum.theforeman.org/releases/1.15/el7/x86_64/ and http://yum.theforeman.org/releases/latest/el7/x86_64/ I'm getting the error: RPM1015: Malformed repository: metadata is missing for some packages in filelists.xml and in other.xml There are a lot of pulp bugs reported to this end, but none with a working fix. Any ideas on how to get past this? Cheers L. -- "Mission Statement: To provide hope and inspiration for collective action, to build collective power, to achieve collective transformation, rooted in grief and rage but pointed towards vision and dreams." - Patrisse Cullors, *Black Lives Matter founder* -- 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: How can I automate Install puppet agent on host after provisioning
We working mainly with Windows environments, but i think its not designed that the puppet agent is automatically installed on a new host with the right environment parameters (and also the user wich run the puppet agent service). While we creating a new host on a VMware infrastructure with a foreman (user data) provisioning template, we define the agent installation over powershell in each provisioning template with the needed installation arguments for agent installation (masterserver, environment, user, ...). -- 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 1.15.2 bug fix release
tl;dr: if you installed tfm-rubygem-safemode 1.3.2, either update your templates to not use "&:" in Ruby blocks, or downgrade to 1.3.1. In case you've recently upgraded, the 1.3.2 version of Safemode (rubygem-safemode) was put on the 1.15 repos a few days ago. This version includes a security patch to make the jail more secure. (https://github.com/svenfuchs/safemode/pull/23/files) However - our templates supplied by default, contain some code incompatible with this change, namely line 53 here: https://github.com/theforeman/community-templates/blob/d2b82a88fdf8ccdf2dc278161df1e80f406de6ee/provisioning_templates/provision/kickstart_default.erb#L53 If you are using "&:", please start using other options such as .each, .map, etc... to ensure compatibility with 1.15.3, which will ship with 1.3.2 safemode and the security patch. I have removed safemode 1.3.2 from our 1.15 repos, so new installs or upgrades will not be affected. Shoutouts to afisher for warning about this on #theforeman IRC today. On 07/13, Daniel Lobato Garcia wrote: > Foreman 1.15.2 is now available with bug fixes for fifteen issues, > notably problems when the fix_db_cache setting was set, Foreman has > been unable to boot in some cases. > > Please see the release notes for the full list of changes: > https://theforeman.org/manuals/1.15/#Releasenotesfor1.15.2 > > It is likely that a 1.15.3 will follow suit in two weeks or less, to > harden the release. Please report any bugs using our tracker (see the > Bug reporting section of this email). > > Information > === > For installation or upgrade instructions, see: > > Installation quick start: > https://theforeman.org/manuals/1.15/quickstart_guide.html > > Upgrade instructions: > https://theforeman.org/manuals/1.15/index.html#3.6Upgrade > > Release notes: > https://theforeman.org/manuals/1.15/index.html#Releasenotesfor1.15 > > Do take note of the upgrade warnings and deprecations in this release: > https://theforeman.org/manuals/1.15/index.html#Upgradewarnings > > > Downloads > = > Packages may be found in the 1.15 directories on both deb.foreman.org > and yum.theforeman.org, and tarballs are on downloads.theforeman.org. > > The GPG key used for RPMs and tarballs has the following fingerprint: > 6610 7FC8 658F F702 E849 9AC4 17A3 FD24 9A8D AAD5 > (https://theforeman.org/security.html#GPGkeys) > > > Bug reporting > = > If you come across a bug, please file it and note the version of > Foreman > that you're using in the report. > > Foreman: http://projects.theforeman.org/projects/foreman/issues/new > Proxy: > http://projects.theforeman.org/projects/smart-proxy/issues/new > Installer: > http://projects.theforeman.org/projects/puppet-foreman/issues/new > > > Best, > > -- > Daniel Lobato Garcia > > @dLobatog > blog.daniellobato.me > daniellobato.me > > GPG: http://keys.gnupg.net/pks/lookup?op=get=0x7A92D6DD38D6DE30 > Keybase: https://keybase.io/elobato -- 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. signature.asc Description: PGP signature
Re: [foreman-users] Re: [event] Deep Dive: Running the Foreman Stack in Containers - Mon 10th July, 2pm (UK)
On Mon, Jul 10, 2017 at 10:43 PM, Alejandro Cortina < alejandro.corti...@gmail.com> wrote: > Ey, > > thank you for the video! really good stuff. > > Since one of the strong points of k8s is to make rapid development I think > it would be good to make a P2 video showing that. Ex.: how can you > code/update/ mix and mach new services and deploy and/or rollback if broken. > I'll put this on the list for when we get to this in general. I've mostly spent time just trying to get the stack to come up and not on advanced workflows yet. This is definitely in the pipeline of things to look at though. And I think it would be helpful to get info from users as to how they see themselves wanting to use and deploy the stack on a platform like this given what it can provide. For example, in my current way of tackling it I am imaging users pulling pre-built images and running them. That is, not pushing the requirement to build the images on to the users. This comes with its own benefits and potential downsides for flexibility. > > I think also it would be good to add Kubernetes to the title to make it > more reachable in youtube. > Greg - is that possible to add keywords or adjust the title for Kubernetes / Openshift? > > Cheers, > > Alex > > On Thursday, June 29, 2017 at 11:15:45 PM UTC+9, Greg Sutcliffe wrote: >> >> Hi all, >> >> Running Foreman in a container is a question that comes up from time to >> time in the Foreman community. Eric Helms has been experimenting with >> running the whole Foreman stack (core, proxies, plugins) inside >> Kubernetes, and wants to show you how it looks. We'll be holding a deep >> dive into this on Monday 10th July, at 2pm (GMT +1). You can tune in >> here: >> >> https://www.youtube.com/watch?v=mPjUvNAYp1c >> >> As always, we welcome your contributions to the video - do join us live >> on YouTube Live chat or in our IRC channel to put your questions to >> Eric! >> >> Cheers, >> Greg >> -- >> IRC / Twitter: @gwmngilfen >> Diaspora: gwmng...@joindiaspora.com >> > -- > 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. > -- Eric D. Helms Red Hat Engineering -- 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 Birthday Meetup Brno, Czech Republic
Hi, We are celebrating Foreman's 8th birthday and we would like to invite you to a Foreman meetup that is intended for wide open-source community around the project in Brno, Czech Republic area. If you are using Foreman, developing it, maintaining a plugin, or just curious about what it can do and you want to learn more, feel free to come and see the other people with the similar interests. There will be two talks: 1. From zero to hero: what Foreman can do and how to get there using the available tooling 2. The story of Satellite 6 QE: the road of the upstream code to the Satellite customers Besides those, there will be chance to ask questions and get answers and networking. Please register/RSVP for us to know the right amount of food to order. https://www.eventbrite.com/e/the-foreman-8th-birthday-community-meetup-brno-tickets-36142628575 Time: Thursday 2017-07-20 19:00 Place: Red Hat, Purkyňova 99, Tower room at 5th floor See you there -- Ivan -- 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] How can I automate Install puppet agent on host after provisioning
Hi, If i'm not mistaken, puppet agent must been install after provisioning a new host. I don't know why but I haven't puppet agent on my host after it. (and katello agent too) When I create new host I chose appropriate "puppet enviroment" and "puppet master" options. -- 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 plugin on rubyline windows
HI everyone , I want to run a foreman plugin on windows (alone ) ??? can i do it if not i want to know how to do it with any ide on linux the same machine where i install my foreman server -- 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: [event] Deep Dive: Running the Foreman Stack in Containers - Mon 10th July, 2pm (UK)
Ey, thank you for the video! really good stuff. Since one of the strong points of k8s is to make rapid development I think it would be good to make a P2 video showing that. Ex.: how can you code/update/ mix and mach new services and deploy and/or rollback if broken. I think also it would be good to add Kubernetes to the title to make it more reachable in youtube. Cheers, Alex On Thursday, June 29, 2017 at 11:15:45 PM UTC+9, Greg Sutcliffe wrote: > > Hi all, > > Running Foreman in a container is a question that comes up from time to > time in the Foreman community. Eric Helms has been experimenting with > running the whole Foreman stack (core, proxies, plugins) inside > Kubernetes, and wants to show you how it looks. We'll be holding a deep > dive into this on Monday 10th July, at 2pm (GMT +1). You can tune in > here: > > https://www.youtube.com/watch?v=mPjUvNAYp1c > > As always, we welcome your contributions to the video - do join us live > on YouTube Live chat or in our IRC channel to put your questions to > Eric! > > Cheers, > Greg > -- > IRC / Twitter: @gwmngilfen > Diaspora: gwmng...@joindiaspora.com > -- 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: OpenSCAP Upload failed: 500
More output information. https://pastebin.com/eJrCD6tB On Wednesday, 12 July 2017 11:32:14 UTC+2, Phillip Smith wrote: > > Hi > > Please can someone assist. > > [root@foreman foreman]# /usr/bin/foreman_scap_client 1 > DEBUG: running: oscap xccdf eval --profile > xccdf_org.ssgproject.content_profile_standard --results-arf > /tmp/d20170712-3398-r7bvwl/results.xml > /var/lib/openscap/content/3e1654fd14a5352d65294db555710bfda5cad1a942209e2d787ea7940035616e.xml > WARNING: Skipping > http://www.redhat.com/security/data/oval/Red_Hat_Enterprise_Linux_7.xml > file which is referenced from XCCDF content > DEBUG: running: /usr/bin/bzip2 /tmp/d20170712-3398-r7bvwl/results.xml > Uploading results to https://foreman.qualica.com:9090/compliance/arf/1 > > Upload failed: 500 "Internal Server Error " > > > [root@foreman foreman]# rpm -qa | grep scap > openscap-scanner-1.2.10-3.el7_3.x86_64 > tfm-rubygem-foreman_openscap-0.7.4-1.fm1_15.el7.noarch > rubygem-foreman_scap_client-0.3.0-1.el7.noarch > perl-Pod-Escapes-1.04-291.el7.noarch > rubygem-smart_proxy_openscap-0.6.4-1.el7.noarch > rubygem-openscap-0.4.7-1.el7.noarch > openscap-1.2.10-3.el7_3.x86_64 > scap-security-guide-0.1.30-5.el7.centos.noarch > > [root@foreman foreman]# cat /etc/foreman_scap_client/config.yaml > # DO NOT EDIT THIS FILE MANUALLY > # IT IS MANAGED BY PUPPET > > # Foreman proxy to which reports should be uploaded > :server: 'foreman.qualica.com' > :port: 9090 > > ## SSL specific options ## > # Client CA file. > # It could be Puppet CA certificate (e.g., > '/var/lib/puppet/ssl/certs/ca.pem') > # Or (recommended for client reporting to Katello) subscription manager CA > file, (e.g., '/etc/rhsm/ca/katello-server-ca.pem') > :ca_file: '/etc/foreman/proxy_ca.pem' > # Client host certificate. > # It could be Puppet agent host certificate (e.g., > '/var/lib/puppet/ssl/certs/myhost.example.com.pem') > # Or (recommended for client reporting to Katello) consumer certificate > (e.g., '/etc/pki/consumer/cert.pem') > :host_certificate: '/etc/foreman/client_cert.pem' > # Client private key > # It could be Puppet agent private key (e.g., > '/var/lib/puppet/ssl/private_keys/myhost.example.com.pem') > # Or (recommended for client reporting to Katello) consumer private key > (e.g., '/etc/pki/consumer/key.pem') > :host_private_key: '/etc/foreman/client_key.pem' > > # policy (key is id as in Foreman) > > 1: > :profile: 'xccdf_org.ssgproject.content_profile_standard' > :content_path: > '/var/lib/openscap/content/3e1654fd14a5352d65294db555710bfda5cad1a942209e2d787ea7940035616e.xml' > # Download path > # A path to download SCAP content from proxy > :download_path: > '/compliance/policies/1/content/3e1654fd14a5352d65294db555710bfda5cad1a942209e2d787ea7940035616e' > :tailoring_path: '' > :tailoring_download_path: '' > > > Kind Regards > Phillip Smith > -- 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.
