On a default CentOS 7 install with the right repo's enables, EPEL and SCLO
I get the following, according to search on a package using yum the
package-names in the installer are wrong.
Any idea how to fix this ?
On Fedora this went fine.
Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman_memcache'
returned 1: Error: No matching Packages to list
/Stage[main]/Foreman::Plugin::Memcache/Foreman::Plugin[memcache]/Package[rubygem-foreman_memcache]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y list rubygem-foreman_memcache' returned 1: Error: No matching Packages
to list
Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman-tasks'
returned 1: Error: No matching Packages to list
/Stage[main]/Foreman::Plugin::Tasks/Foreman::Plugin[tasks]/Package[rubygem-foreman-tasks]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y list rubygem-foreman-tasks' returned 1: Error: No matching Packages to
list
Execution of '/usr/bin/yum -d 0 -e 0 -y list
rubygem-foreman_default_hostgroup' returned 1: Error: No matching Packages
to list
/Stage[main]/Foreman::Plugin::Default_hostgroup/Foreman::Plugin[default_hostgroup]/Package[rubygem-foreman_default_hostgroup]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y list rubygem-foreman_default_hostgroup' returned 1: Error: No matching
Packages to list
Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman_bootdisk'
returned 1: Error: No matching Packages to list
/Stage[main]/Foreman::Plugin::Bootdisk/Foreman::Plugin[bootdisk]/Package[rubygem-foreman_bootdisk]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y list rubygem-foreman_bootdisk' returned 1: Error: No matching Packages
to list
Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-puppetdb_foreman'
returned 1: Error: No matching Packages to list
/Stage[main]/Foreman::Plugin::Puppetdb/Foreman::Plugin[puppetdb]/Package[rubygem-puppetdb_foreman]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y list rubygem-puppetdb_foreman' returned 1: Error: No matching Packages
to list
Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman_cockpit'
returned 1: Error: No matching Packages to list
/Stage[main]/Foreman::Plugin::Cockpit/Foreman::Plugin[cockpit]/Package[rubygem-foreman_cockpit]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y list rubygem-foreman_cockpit' returned 1: Error: No matching Packages to
list
Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman_setup'
returned 1: Error: No matching Packages to list
/Stage[main]/Foreman::Plugin::Setup/Foreman::Plugin[setup]/Package[rubygem-foreman_setup]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y list rubygem-foreman_setup' returned 1: Error: No matching Packages to
list
Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman_discovery'
returned 1: Error: No matching Packages to list
/Stage[main]/Foreman::Plugin::Discovery/Foreman::Plugin[discovery]/Package[rubygem-foreman_discovery]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y list rubygem-foreman_discovery' returned 1: Error: No matching Packages
to list
Execution of '/usr/bin/yum -d 0 -e 0 -y list
rubygem-foreman_remote_execution' returned 1: Error: No matching Packages
to list
/Stage[main]/Foreman::Plugin::Remote_execution/Foreman::Plugin[remote_execution]/Package[rubygem-foreman_remote_execution]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y list rubygem-foreman_remote_execution' returned 1: Error: No matching
Packages to list
Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman_dhcp_browser'
returned 1: Error: No matching Packages to list
/Stage[main]/Foreman::Plugin::Dhcp_browser/Foreman::Plugin[dhcp_browser]/Package[rubygem-foreman_dhcp_browser]/ensure:
change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
-y list rubygem-foreman_dhcp_browser' returned 1: Error: No matching
Packages to list
Installing Done
[100%] […]
Something went wrong! Check the log for ERROR-level output
Foreman is running at https://foreman-01…
Initial credentials are admin / …
I seem to have managed this by adding tfm- in front of the plugin prefix
and 2 packagenames in the answersfile.
Please fix.
···
Op vrijdag 7 oktober 2016 02:38:34 UTC+2 schreef yamaka...@gmail.com:
>
> On a default CentOS 7 install with the right repo's enables, EPEL and SCLO
> I get the following, according to search on a package using yum the
> package-names in the installer are wrong.
>
> Any idea how to fix this ?
>
> On Fedora this went fine.
>
> Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman_memcache'
> returned 1: Error: No matching Packages to list
> /Stage[main]/Foreman::Plugin::Memcache/Foreman::Plugin[memcache]/Package[rubygem-foreman_memcache]/ensure:
> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
> -y list rubygem-foreman_memcache' returned 1: Error: No matching Packages
> to list
> Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman-tasks'
> returned 1: Error: No matching Packages to list
> /Stage[main]/Foreman::Plugin::Tasks/Foreman::Plugin[tasks]/Package[rubygem-foreman-tasks]/ensure:
> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
> -y list rubygem-foreman-tasks' returned 1: Error: No matching Packages to
> list
> Execution of '/usr/bin/yum -d 0 -e 0 -y list
> rubygem-foreman_default_hostgroup' returned 1: Error: No matching Packages
> to list
> /Stage[main]/Foreman::Plugin::Default_hostgroup/Foreman::Plugin[default_hostgroup]/Package[rubygem-foreman_default_hostgroup]/ensure:
> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
> -y list rubygem-foreman_default_hostgroup' returned 1: Error: No matching
> Packages to list
> Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman_bootdisk'
> returned 1: Error: No matching Packages to list
> /Stage[main]/Foreman::Plugin::Bootdisk/Foreman::Plugin[bootdisk]/Package[rubygem-foreman_bootdisk]/ensure:
> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
> -y list rubygem-foreman_bootdisk' returned 1: Error: No matching Packages
> to list
> Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-puppetdb_foreman'
> returned 1: Error: No matching Packages to list
> /Stage[main]/Foreman::Plugin::Puppetdb/Foreman::Plugin[puppetdb]/Package[rubygem-puppetdb_foreman]/ensure:
> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
> -y list rubygem-puppetdb_foreman' returned 1: Error: No matching Packages
> to list
> Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman_cockpit'
> returned 1: Error: No matching Packages to list
> /Stage[main]/Foreman::Plugin::Cockpit/Foreman::Plugin[cockpit]/Package[rubygem-foreman_cockpit]/ensure:
> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
> -y list rubygem-foreman_cockpit' returned 1: Error: No matching Packages to
> list
> Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman_setup'
> returned 1: Error: No matching Packages to list
> /Stage[main]/Foreman::Plugin::Setup/Foreman::Plugin[setup]/Package[rubygem-foreman_setup]/ensure:
> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
> -y list rubygem-foreman_setup' returned 1: Error: No matching Packages to
> list
> Execution of '/usr/bin/yum -d 0 -e 0 -y list rubygem-foreman_discovery'
> returned 1: Error: No matching Packages to list
> /Stage[main]/Foreman::Plugin::Discovery/Foreman::Plugin[discovery]/Package[rubygem-foreman_discovery]/ensure:
> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
> -y list rubygem-foreman_discovery' returned 1: Error: No matching Packages
> to list
> Execution of '/usr/bin/yum -d 0 -e 0 -y list
> rubygem-foreman_remote_execution' returned 1: Error: No matching Packages
> to list
> /Stage[main]/Foreman::Plugin::Remote_execution/Foreman::Plugin[remote_execution]/Package[rubygem-foreman_remote_execution]/ensure:
> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
> -y list rubygem-foreman_remote_execution' returned 1: Error: No matching
> Packages to list
> Execution of '/usr/bin/yum -d 0 -e 0 -y list
> rubygem-foreman_dhcp_browser' returned 1: Error: No matching Packages to
> list
> /Stage[main]/Foreman::Plugin::Dhcp_browser/Foreman::Plugin[dhcp_browser]/Package[rubygem-foreman_dhcp_browser]/ensure:
> change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0
> -y list rubygem-foreman_dhcp_browser' returned 1: Error: No matching
> Packages to list
> Installing Done
> [100%] [.....................................................]
> Something went wrong! Check the log for ERROR-level output
> * Foreman is running at https://foreman-01.....
> Initial credentials are admin / ............
> * Foreman Proxy is running at https://foreman-01........:8443
> * Puppetmaster is running at port 8140
> The full log is at /var/log/foreman-installer/foreman.log
> [root@foreman-01 ~]# yum clean all
> Loaded plugins: fastestmirror
> Cleaning repos: base centos-sclo-rh centos-sclo-sclo epel extras foreman
> foreman-plugins updates
> Cleaning up everything
> Cleaning up list of fastest mirrors
> [root@foreman-01 ~]# yum search foreman dhcp
> Loaded plugins: fastestmirror
> base
> > 3.6 kB 00:00:00
> centos-sclo-rh
> > 2.9 kB 00:00:00
> centos-sclo-sclo
> > 2.9 kB 00:00:00
> epel/x86_64/metalink
> > 15 kB 00:00:00
> epel
> > 4.3 kB 00:00:00
> extras
> > 3.4 kB 00:00:00
> foreman
> > 2.9 kB 00:00:00
> foreman-plugins
> > 2.9 kB 00:00:00
> updates
> > 3.4 kB 00:00:00
> (1/11):
> base/7/x86_64/group_gz
> > 155 kB 00:00:00
> (2/11):
> epel/x86_64/group_gz
> > 170 kB 00:00:00
> (3/11):
> centos-sclo-sclo/x86_64/primary_db
> > 117 kB 00:00:00
> (4/11):
> base/7/x86_64/primary_db
> > 5.3 MB 00:00:01
> (5/11):
> centos-sclo-rh/x86_64/primary_db
> > 1.8 MB 00:00:01
> (6/11):
> extras/7/x86_64/primary_db
> > 165 kB 00:00:00
> (7/11):
> updates/7/x86_64/primary_db
> > 7.8 MB 00:00:00
> (8/11):
> foreman-plugins/x86_64/primary_db
> > 78 kB 00:00:00
> (9/11):
> foreman/x86_64/primary_db
> > 144 kB 00:00:00
> (10/11):
> epel/x86_64/updateinfo
> > 623 kB 00:00:01
> (11/11):
> epel/x86_64/primary_db
> > 4.2 MB 00:00:02
> Determining fastest mirrors
> * base: mirror.i3d.net
> * epel: ftp.nluug.nl
> * extras: ftp.nluug.nl
> * updates: mirror.nl.leaseweb.net
> ====================================================== N/S matched:
> foreman, dhcp ======================================================
> foreman-proxy.noarch : Restful Proxy for DNS, DHCP, TFTP, PuppetCA and
> Puppet
> rubygem-smart_proxy_dhcp_infoblox.noarch : Infoblox DHCP provider plugin
> for Foreman's smart proxy
> tfm-rubygem-foreman_dhcp_browser.noarch : DHCP browser plugin for Foreman
> tfm-rubygem-foreman_dhcp_browser-doc.noarch : Documentation for
> rubygem-foreman_dhcp_browser
>
> Full name and summary matches only, use "search all" for everything.
> [root@foreman-01 ~]#
>
>
If you've copied the installer answers file from Fedora or another OS,
these types of errors are to be expected. The answers file is only
applicable to the same OS that it was originally generated on.
···
On 07/10/16 01:38, yamakasi.014@gmail.com wrote:
> On a default CentOS 7 install with the right repo's enables, EPEL and
> SCLO I get the following, according to search on a package using yum the
> package-names in the installer are wrong.
>
> Any idea how to fix this ?
>
> On Fedora this went fine.
You are right it's copied, but it also didn't change when I edited it.
What about the puppet 4.0 paths, are they honored ? so it uses
/etc/puppetlabs/puppet instead of /etc/puppet ?
Thanks!
···
Op vrijdag 7 oktober 2016 09:09:15 UTC+2 schreef Dominic Cleal:
>
> On 07/10/16 01:38, yamaka...@gmail.com wrote:
> > On a default CentOS 7 install with the right repo's enables, EPEL and
> > SCLO I get the following, according to search on a package using yum the
> > package-names in the installer are wrong.
> >
> > Any idea how to fix this ?
> >
> > On Fedora this went fine.
>
> If you've copied the installer answers file from Fedora or another OS,
> these types of errors are to be expected. The answers file is only
> applicable to the same OS that it was originally generated on.
>
> --
> Dominic Cleal
> dom...@cleal.org
>
If the original answers file was using the Fedora non-AIO version of
Puppet then no, the paths will be incorrect when you copy the file to an
AIO installation. The same applies, the answers file is OS-specific.
Don't copy it from one OS to another.
···
On 07/10/16 08:35, yamakasi.014@gmail.com wrote:
> You are right it's copied, but it also didn't change when I edited it.
>
> What about the puppet 4.0 paths, are they honored ? so it uses
> /etc/puppetlabs/puppet instead of /etc/puppet ?
What I mean is, when you install the 4.0 repo and run the foreman-installer
from scratch, does it understand that it needs to use /etc/puppetlabs
instead if /etc/puppet ?
···
Op vrijdag 7 oktober 2016 09:42:16 UTC+2 schreef Dominic Cleal:
>
> On 07/10/16 08:35, yamaka...@gmail.com wrote:
> > You are right it's copied, but it also didn't change when I edited it.
> >
> > What about the puppet 4.0 paths, are they honored ? so it uses
> > /etc/puppetlabs/puppet instead of /etc/puppet ?
>
> If the original answers file was using the Fedora non-AIO version of
> Puppet then no, the paths will be incorrect when you copy the file to an
> AIO installation. The same applies, the answers file is OS-specific.
> Don't copy it from one OS to another.
>
> --
> Dominic Cleal
> dom...@cleal.org
>
Yes, AIO Puppet installations with these paths are supported from 1.12.0.
···
On 07/10/16 08:44, yamakasi.014@gmail.com wrote:
> What I mean is, when you install the 4.0 repo and run the
> foreman-installer from scratch, does it understand that it needs to use
> /etc/puppetlabs instead if /etc/puppet ?
OK great, I will go back to my snapshot and let you know!
···
Op vrijdag 7 oktober 2016 09:45:29 UTC+2 schreef Dominic Cleal:
>
> On 07/10/16 08:44, yamaka...@gmail.com wrote:
> > What I mean is, when you install the 4.0 repo and run the
> > foreman-installer from scratch, does it understand that it needs to use
> > /etc/puppetlabs instead if /etc/puppet ?
>
> Yes, AIO Puppet installations with these paths are supported from 1.12.0.
>
> --
> Dominic Cleal
> dom...@cleal.org
>
