[foreman-users] Migrate from Foreman to Foreman+Katello
Hello, It looks like it is not possible to add Katello to an existing Foreman installation. http://projects.theforeman.org/issues/7605 Are there any recommended methods of migrating from an existing Foreman only install, to a fresh Foreman+Katello installation? The puppet modules and existing puppet certificates should be easy enough to copy over, but what about my templates/hosts/host groups etc? Any way I can dump this data and import it into the new host? Thanks, Steve -- 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 centos-base repo not syncing
I have successfully synced other repos ie 'epel' without any difficulty. I've created a product 'centos-base' with a repo called 'centos-base' and attempted to sync the repo but no packages will sync. Same problem with centos-updates. Not sure where to start troubleshooting this, the foreman production.log doesn't have any obvious errors. The content host does display the repo including package count: # yum repolist ... repo id repo name status *!Default_Organization_CentOS-Base_CentOS-Base CentOS-Base9,007* !Default_Organization_CentOS-Gluster-3_7_CentOS-Gluster-3_7 CentOS-Gluster-3.714 !Default_Organization_CentOS-Updates_CentOS-Updates CentOS-Updates 2,548 !Default_Organization_epel_epel epel 11,215 !Default_Organization_filebeat_filebeat filebeat 44 !Default_Organization_glusterfs-nagios-epel_glusterfs-nagios-epel glusterfs-nagios-epel 10 !Default_Organization_katello-agent_katello-agent katello-agent 15 !Default_Organization_pcic_internal_pcic_internal pcic_internal 13 base/7/x86_64 CentOS-7 - Base*9,007* epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_6410,751 extras/7/x86_64 CentOS-7 - Extras393 updates/7/x86_64 CentOS-7 - Updates 2,548 repolist: 45,565 Katello version 3.1 Foreman 1.12.3 Foreman OS CentOS 7.2 pulp journal: Oct 23 11:45:03 foreman.my.domain.name pulp[12865]: kombu.transport.qpid:INFO: Connected to qpid with SASL mechanism ANONYMOUS Oct 23 11:45:04 foreman.my.domain.name pulp[299]: celery.worker.strategy:INFO: Received task: pulp.server.async.tasks._queue_reserved_task[060c2ae6-44a4-483f-ad90-be54e872ffec] Oct 23 11:45:04 foreman.my.domain.name pulp[322]: celery.worker.strategy:INFO: Received task: pulp.server.managers.repo.sync.sync[a3070bfa-6723-40c4-971e-2781746212c5] Oct 23 11:45:04 foreman.my.domain.name pulp[322]: celery.worker.strategy:INFO: Received task: pulp.server.async.tasks._release_resource[1f2bfee7-af00-4b0c-adb5-6dae94460415] Oct 23 11:45:04 foreman.my.domain.name pulp[648]: pulp_rpm.plugins.importers.yum.sync:INFO: Downloading metadata from http://mirror.it.ubc.ca/centos/7.2.1511/os/x86_64/. Oct 23 11:45:04 foreman.my.domain.name pulp[299]: celery.worker.job:INFO: Task pulp.server.async.tasks._queue_reserved_task[060c2ae6-44a4-483f-ad90-be54e872ffec] succeeded in 0.0428758189082s: None Oct 23 11:45:04 foreman.my.domain.name pulp[648]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1): mirror.it.ubc.ca Oct 23 11:45:05 foreman.my.domain.name pulp[648]: pulp_rpm.plugins.importers.yum.sync:INFO: Parsing metadata. Oct 23 11:45:05 foreman.my.domain.name pulp[648]: pulp_rpm.plugins.importers.yum.sync:INFO: Downloading metadata from http://mirror.it.ubc.ca/centos/7.2.1511/os/x86_64/. Oct 23 11:45:05 foreman.my.domain.name pulp[648]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1): mirror.it.ubc.ca Oct 23 11:45:06 foreman.my.domain.name pulp[648]: pulp_rpm.plugins.importers.yum.sync:INFO: Parsing metadata. Oct 23 11:45:06 foreman.my.domain.name pulp[648]: pulp_rpm.plugins.importers.yum.sync:INFO: Downloading metadata from http://mirror.it.ubc.ca/centos/7.2.1511/os/x86_64/. Oct 23 11:45:06 foreman.my.domain.name pulp[648]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1): mirror.it.ubc.ca Oct 23 11:45:07 foreman.my.domain.name pulp[648]: pulp_rpm.plugins.importers.yum.sync:INFO: Parsing metadata. Oct 23 11:45:07 foreman.my.domain.name pulp[648]: pulp_rpm.plugins.importers.yum.sync:INFO: upstream repo metadata has not changed. Skipping steps. Oct 23 11:45:07 foreman.my.domain.name pulp[648]: pulp_rpm.plugins.importers.yum.sync:INFO: Downloading additional units. Oct 23 11:45:07 foreman.my.domain.name pulp[648]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1): mirror.it.ubc.ca Oct 23 11:45:09 foreman.my.domain.name pulp[648]:
Re: [foreman-users] AWS EC2 with Foreman
I was seeing this on 1.15.4 and upgraded to 1.15.6 with the same results. For some reason image based deployments that have userdata enabled also require a finish template associated. This leads to 1 of 2 outcomes: 1. as Ivan stated, the host creation UI throws this error and a cannot proceed 2. as a workaround, a finish template is associated, but if VM is being deployed with a non-root user (ie 'centos' for Centos instances) the provisioning cannot be completed via SSH as the wrong user is trying to login to run the finish script. This happens even if the image is configured with user 'centos': logs: 2017-10-25 15:31:45 1c049de5 [sql] [I] About to start post launch script on test28.ipadomain.com 2017-10-25 15:31:45 1c049de5 [sql] [I] generating template to upload to test28.ipadomain.com 2017-10-25 15:32:25 1c049de5 [sql] [I] Remove puppet certificate for test28.ipadomain.com 2017-10-25 15:32:27 1c049de5 [sql] [I] Adding autosign entry for test28.ipadomain.com 2017-10-25 15:32:37 1c049de5 [app] [W] Failed to launch script on test28.ipadomain.com: Please login as the user "centos" rather than the user " root". 2017-10-25 15:32:37 1c049de5 [sql] [W] Rolling back due to a problem: [#", architecture_id: 1, operatingsystem_id: 3, environment_id: 4, ptable_id: nil, medium_id: nil, build: true, comment: "", disk: "" , installed_at: nil, model_id: nil, hostgroup_id: 4, owner_id: 5, owner_type: "User", enabled: true, puppet_ca_proxy_id: 1, managed: true, u se_image: nil, image_file: nil, uuid: "i-06d131076cfee4de4", compute_resource_id: 2, puppet_proxy_id: 1, certname: nil, image_id: 2, organiz ation_id: 1, location_id: 3, type: "Host::Managed", otp: "0Jk(/vE83}OY%cib>,+a.k", realm_id: 1, compute_profile_id: 6, provision_method: "im age", grub_pass: "", content_view_id: nil, lifecycle_environment_id: nil, global_status : 0, lookup_value_matcher: "fqdn=test28.ipadomain.com", pxe_loader: "", discovery_rule_id: nil>, :setSSHProvision], @timestamp=2017-10-25 22:32: 37 UTC>] 2017-10-25 15:32:37 1c049de5 [sql] [I] Remove puppet certificate for test28.ipadomain.com 2017-10-25 15:32:39 1c049de5 [sql] [I] Delete the autosign entry for test28.ipadomain.com 2017-10-25 15:32:39 1c049de5 [sql] [E] Task Prepare post installation script for test28.ipadomain.com *rollbacked* 2017-10-25 15:32:39 1c049de5 [sql] [E] Task Wait for test28.ipadomain.com to come online *rollbacked* 2017-10-25 15:32:39 1c049de5 [sql] [E] Task Enable certificate generation for test28.ipadomain.com *rollbacked* 2017-10-25 15:32:39 1c049de5 [sql] [E] Task Configure instance test28.ipadomain.com via SSH *failed* On Saturday, 7 October 2017 07:38:52 UTC-7, Ivan Adji-Krstev wrote: > > Hi Greg, > > I'm using Version 1.15.4. The newest one. > > On Thursday, October 5, 2017 at 12:24:46 PM UTC+2, Greg Sutcliffe wrote: >> >> On Thu, 2017-09-28 at 07:08 -0700, Ivan Adji-Krstev wrote: >> > Hi Greg, >> > and when i press resolve i got this message >> > Also when i try to press submit i get the same error. >> > >> > There is no finish template anywhere as options on the way. I have >> > try to lock the template but again same results. >> >> What version of Foreman are you on? There was a bug with the Resolve >> Templates button in recent Foreman versions (1.14 & 1.15, I think), but >> that was fixed in 1.15.4. >> >> Greg >> > -- 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] Re: "No templates were configured" for image builds?
Mike did you get anywhere with this issue? I'm having a similar problem on 1.15.4 provisioning EC2 instances. I notice if I toggle between 'bare metal' and my ec2 'deploy on' type during host creation I can resolve the userdata template only on 'bare metal' type. Steve On Friday, 15 September 2017 09:11:20 UTC-7, Mike Wilson wrote: > > > > On Friday, September 15, 2017 at 2:03:35 AM UTC-5, Ivan Necas wrote: >> >> One possibility is going to >> >> https://github.com/fog/fog-vsphere/blob/master/lib/fog/vsphere/requests/compute/cloudinit_to_customspec.rb#L7-L39 >> >> to see, what are the keys one can pass there. Perhaps it will be >> helpful as well. >> >> -- Ivan >> > > Thanks. > > Right now since I have no experience with this at all I'm just trying to > get a very basic setup working. I can't seem to find even a default config > within foreman that will work. I also can't figure out why when enabling > cloud-init it wont take the yaml template for it ... and no matter what I > do when I click "resolve" to verify templates it always says "no templates > configured". > > I think at this point I need to find someone that's done a walk through so > I can see what I'm doing wrong. I suspect I have some misunderstandings how > some of this is suppose to work and other bits that are required that I'm > just not aware of. The foreman docs cover some of this but I've not had any > luck combining it all together. > > > -- 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] Re: "No templates were configured" for image builds?
Actually it seems to be related more to the Operating System tab -> Provisioning Method type. Image won't resolve the template, Network Based will. I guess this just re-enforces that this is an image related issue. On Wednesday, 25 October 2017 13:25:41 UTC-7, steved0ca wrote: > > Mike did you get anywhere with this issue? > > I'm having a similar problem on 1.15.4 provisioning EC2 instances. I > notice if I toggle between 'bare metal' and my ec2 'deploy on' type during > host creation I can resolve the userdata template only on 'bare metal' type. > > Steve > > On Friday, 15 September 2017 09:11:20 UTC-7, Mike Wilson wrote: >> >> >> >> On Friday, September 15, 2017 at 2:03:35 AM UTC-5, Ivan Necas wrote: >>> >>> One possibility is going to >>> >>> https://github.com/fog/fog-vsphere/blob/master/lib/fog/vsphere/requests/compute/cloudinit_to_customspec.rb#L7-L39 >>> >>> to see, what are the keys one can pass there. Perhaps it will be >>> helpful as well. >>> >>> -- Ivan >>> >> >> Thanks. >> >> Right now since I have no experience with this at all I'm just trying to >> get a very basic setup working. I can't seem to find even a default config >> within foreman that will work. I also can't figure out why when enabling >> cloud-init it wont take the yaml template for it ... and no matter what I >> do when I click "resolve" to verify templates it always says "no templates >> configured". >> >> I think at this point I need to find someone that's done a walk through >> so I can see what I'm doing wrong. I suspect I have some misunderstandings >> how some of this is suppose to work and other bits that are required that >> I'm just not aware of. The foreman docs cover some of this but I've not had >> any luck combining it all together. >> >> >> -- 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.
