date:20170814

Re: [foreman-users] Katello 3.4.4 Released

2017-08-14 Thread Louis Bohm

So I continued on with a yum clean all and a yum -y update.  They went fine.  
So then I tried foreman-installer —scenario katello —upgrade and that failed on 
mongoldb and then postgresql.

[root@fm ~]# foreman-installer --scenario katello --upgrade
Upgrading, to monitor the progress on all related services, please do:
  foreman-tail | tee upgrade-$(date +%Y-%m-%d-%H%M).log
Upgrade Step: stop_services...
/usr/sbin/service-wait goferd stop
Redirecting to /bin/systemctl stop  goferd.service

/usr/sbin/service-wait foreman-tasks stop
Redirecting to /bin/systemctl stop  foreman-tasks.service

/usr/sbin/service-wait httpd stop
Redirecting to /bin/systemctl stop  httpd.service

/usr/sbin/service-wait pulp_celerybeat stop
Redirecting to /bin/systemctl stop  pulp_celerybeat.service

/usr/sbin/service-wait foreman-proxy stop
Redirecting to /bin/systemctl stop  foreman-proxy.service

/usr/sbin/service-wait pulp_streamer stop
Redirecting to /bin/systemctl stop  pulp_streamer.service

/usr/sbin/service-wait pulp_resource_manager stop
Redirecting to /bin/systemctl stop  pulp_resource_manager.service

/usr/sbin/service-wait pulp_workers stop
Redirecting to /bin/systemctl stop  pulp_workers.service

/usr/sbin/service-wait tomcat stop
Redirecting to /bin/systemctl stop  tomcat.service

/usr/sbin/service-wait squid stop
Redirecting to /bin/systemctl stop  squid.service

/usr/sbin/service-wait qdrouterd stop
Redirecting to /bin/systemctl stop  qdrouterd.service

/usr/sbin/service-wait qpidd stop
Redirecting to /bin/systemctl stop  qpidd.service

Success!
katello-service stop --exclude mongod,postgresql finished successfully!
Upgrade Step: start_databases...
/usr/sbin/service-wait mongod start
Redirecting to /bin/systemctl start  mongod.service
Job for mongod.service failed because the control process exited with error 
code. See "systemctl status mongod.service" and "journalctl -xe" for details.

/usr/sbin/service-wait postgresql start
Redirecting to /bin/systemctl start  postgresql.service
Job for postgresql.service failed because the control process exited with error 
code. See "systemctl status postgresql.service" and "journalctl -xe" for 
details.
touch: cannot touch ‘/var/lock/subsys/postgresql’: No such file or directory
head: cannot open ‘/var/lib/pgsql/data/postmaster.pid’ for reading: No such 
file or directory

Some services failed to start: mongod
katello-service start --only mongod,postgresql failed! Check the output for 
error!
Upgrade step start_databases failed. Check logs for more information.

And here is the mongodb errors:
[root@fm ~]# systemctl status mongod.service -l
● mongod.service - High-performance, schema-free document-oriented database
   Loaded: loaded (/usr/lib/systemd/system/mongod.service; enabled; vendor 
preset: disabled)
   Active: failed (Result: exit-code) since Mon 2017-08-14 17:41:50 EDT; 3min 
15s ago
  Process: 13607 ExecStart=/usr/bin/mongod $OPTIONS run (code=exited, 
status=1/FAILURE)

Aug 14 17:41:50 fm.tdsops.com systemd[1]: Starting High-performance, 
schema-free document-oriented database...
Aug 14 17:41:50 fm.tdsops.com mongod[13607]: about to fork child process, 
waiting until server is ready for connections.
Aug 14 17:41:50 fm.tdsops.com mongod[13607]: forked process: 13609
Aug 14 17:41:50 fm.tdsops.com mongod[13607]: ERROR: child process failed, 
exited with error number 1
Aug 14 17:41:50 fm.tdsops.com systemd[1]: mongod.service: control process 
exited, code=exited status=1
Aug 14 17:41:50 fm.tdsops.com systemd[1]: Failed to start High-performance, 
schema-free document-oriented database.
Aug 14 17:41:50 fm.tdsops.com systemd[1]: Unit mongod.service entered failed 
state.
Aug 14 17:41:50 fm.tdsops.com systemd[1]: mongod.service failed.
and the postgresql errors:
[root@fm ~]# systemctl status postgresql.service -l
● postgresql.service - PostgreSQL database server
   Loaded: loaded (/etc/systemd/system/postgresql.service; enabled; vendor 
preset: disabled)
   Active: failed (Result: exit-code) since Mon 2017-08-14 17:41:58 EDT; 4min 
10s ago
  Process: 13644 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p 
${PGPORT} -w -t 300 (code=exited, status=1/FAILURE)
  Process: 13637 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA} 
(code=exited, status=0/SUCCESS)

Aug 14 17:41:57 fm.tdsops.com systemd[1]: Starting PostgreSQL database server...
Aug 14 17:41:57 fm.tdsops.com pg_ctl[13644]: 2017-08-14 17:41:57 EDT LOG:  
could not bind IPv6 socket: Cannot assign requested address
Aug 14 17:41:57 fm.tdsops.com pg_ctl[13644]: 2017-08-14 17:41:57 EDT HINT:  Is 
another postmaster already running on port 5432? If not, wait a few seconds and 
retry.
Aug 14 17:41:57 fm.tdsops.com pg_ctl[13644]: 2017-08-14 17:41:57 EDT FATAL:  
could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock": No such 
file or directory
Aug 14 17:41:58 fm.tdsops.com pg_ctl[13644]: pg_ctl: could not start server
Aug 14 17:41:58 fm.tdsops.com pg_ctl[13644]: Examine the log output.
Aug 14

Re: [foreman-users] Katello 3.4.4 Released

2017-08-14 Thread Louis Bohm

So this time when I did yum update  
http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm it 
worked.  However, the next step  yum update -y foreman-release-scll found 
nothing to update.
[root@fm ~]#  yum update -y foreman-release-scl
Loaded plugins: fastestmirror, package_upload, product-id, 
search-disabled-repos, subscription-
  : manager, tracer_upload
Loading mirror speeds from cached hostfile
 * base: mirrors.lga7.us.voxel.net
 * epel: mirrors.mit.edu
 * extras: mirrors.tripadvisor.com
 * updates: mirror.trouble-free.net
No packages marked for update

Shouldn’t there be updates in this step?

Louis
> On Aug 14, 2017, at 5:29 PM, Louis Bohm  wrote:
> 
> Thank you.  
> 
> This time I tried something different.  Before doing anything I removed 
> foreman-plugin.  Then I started the upgrade.  I will let you know how it goes.
> 
> Louis
>> On Aug 14, 2017, at 4:36 PM, Eric D Helms > > wrote:
>> 
>> I would recommend removing foreman-plugin and then doing the upgrade. That's 
>> not a package that is typically installed or required on a system.
>> 
>> On Mon, Aug 14, 2017 at 3:47 PM, Louis Bohm > > wrote:
>> I love having infinite history...  Here is the ouput of the command:
>> [root@fm yum.repos.d]# yum update  
>> http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm 
>> 
>> Loaded plugins: fastestmirror, package_upload, product-id, 
>> search-disabled-repos, subscription-
>>   : manager, tracer_upload
>> foreman-release.rpm |  
>> 16 kB  00:00:00
>> Examining /var/tmp/yum-root-qoYoPs/foreman-release.rpm: 
>> foreman-release-1.15.3-1.el7.noarch
>> Marking /var/tmp/yum-root-qoYoPs/foreman-release.rpm as an update to 
>> foreman-release-1.14.3-1.el7.noarch
>> Resolving Dependencies
>> --> Running transaction check
>> ---> Package foreman-release.noarch 0:1.14.3-1.el7 will be updated
>> --> Processing Dependency: foreman-release = 1.14.3-1.el7 for package: 
>> foreman-plugin-1.14.3-1.el7.noarch
>> Loading mirror speeds from cached hostfile
>>  * base: ftpmirror.your.org 
>>  * epel: mirror.metrocast.net 
>>  * extras: mirrors.centos.webair.com 
>>  * updates: mirrors.lga7.us.voxel.net 
>> ---> Package foreman-release.noarch 0:1.15.3-1.el7 will be an update
>> --> Finished Dependency Resolution
>> Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman)
>>Requires: foreman-release = 1.14.3-1.el7
>>Removing: foreman-release-1.14.3-1.el7.noarch (@foreman)
>>foreman-release = 1.14.3-1.el7
>>Updated By: foreman-release-1.15.3-1.el7.noarch (/foreman-release)
>>foreman-release = 1.15.3-1.el7
>>Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman)
>>foreman-release = 1.14.0-0.1.RC1.el7
>>Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman)
>>foreman-release = 1.14.0-0.1.RC2.el7
>>Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman)
>>foreman-release = 1.14.0-0.1.RC3.el7
>>Available: foreman-release-1.14.0-1.el7.noarch (foreman)
>>foreman-release = 1.14.0-1.el7
>>Available: foreman-release-1.14.1-1.el7.noarch (foreman)
>>foreman-release = 1.14.1-1.el7
>>Available: foreman-release-1.14.2-1.el7.noarch (foreman)
>>foreman-release = 1.14.2-1.el7
>> **
>> yum can be configured to try to resolve such errors by temporarily enabling
>> disabled repos and searching for missing dependencies.
>> To enable this functionality please set 'notify_only=0' in 
>> /etc/yum/pluginconf.d/search-disabled-repos.conf
>> **
>> 
>> Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman)
>>Requires: foreman-release = 1.14.3-1.el7
>>Removing: foreman-release-1.14.3-1.el7.noarch (@foreman)
>>foreman-release = 1.14.3-1.el7
>>Updated By: foreman-release-1.15.3-1.el7.noarch (/foreman-release)
>>foreman-release = 1.15.3-1.el7
>>Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman)
>>foreman-release = 1.14.0-0.1.RC1.el7
>>Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman)
>>foreman-release = 1.14.0-0.1.RC2.el7
>>Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman)
>>foreman-release = 1.14.0-0.1.RC3.el7
>>Available:

Re: [foreman-users] Katello 3.4.4 Released

2017-08-14 Thread Louis Bohm

Thank you.  

This time I tried something different.  Before doing anything I removed 
foreman-plugin.  Then I started the upgrade.  I will let you know how it goes.

Louis
> On Aug 14, 2017, at 4:36 PM, Eric D Helms  wrote:
> 
> I would recommend removing foreman-plugin and then doing the upgrade. That's 
> not a package that is typically installed or required on a system.
> 
> On Mon, Aug 14, 2017 at 3:47 PM, Louis Bohm  > wrote:
> I love having infinite history...  Here is the ouput of the command:
> [root@fm yum.repos.d]# yum update  
> http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm 
> 
> Loaded plugins: fastestmirror, package_upload, product-id, 
> search-disabled-repos, subscription-
>   : manager, tracer_upload
> foreman-release.rpm |  16 
> kB  00:00:00
> Examining /var/tmp/yum-root-qoYoPs/foreman-release.rpm: 
> foreman-release-1.15.3-1.el7.noarch
> Marking /var/tmp/yum-root-qoYoPs/foreman-release.rpm as an update to 
> foreman-release-1.14.3-1.el7.noarch
> Resolving Dependencies
> --> Running transaction check
> ---> Package foreman-release.noarch 0:1.14.3-1.el7 will be updated
> --> Processing Dependency: foreman-release = 1.14.3-1.el7 for package: 
> foreman-plugin-1.14.3-1.el7.noarch
> Loading mirror speeds from cached hostfile
>  * base: ftpmirror.your.org 
>  * epel: mirror.metrocast.net 
>  * extras: mirrors.centos.webair.com 
>  * updates: mirrors.lga7.us.voxel.net 
> ---> Package foreman-release.noarch 0:1.15.3-1.el7 will be an update
> --> Finished Dependency Resolution
> Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman)
>Requires: foreman-release = 1.14.3-1.el7
>Removing: foreman-release-1.14.3-1.el7.noarch (@foreman)
>foreman-release = 1.14.3-1.el7
>Updated By: foreman-release-1.15.3-1.el7.noarch (/foreman-release)
>foreman-release = 1.15.3-1.el7
>Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC1.el7
>Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC2.el7
>Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC3.el7
>Available: foreman-release-1.14.0-1.el7.noarch (foreman)
>foreman-release = 1.14.0-1.el7
>Available: foreman-release-1.14.1-1.el7.noarch (foreman)
>foreman-release = 1.14.1-1.el7
>Available: foreman-release-1.14.2-1.el7.noarch (foreman)
>foreman-release = 1.14.2-1.el7
> **
> yum can be configured to try to resolve such errors by temporarily enabling
> disabled repos and searching for missing dependencies.
> To enable this functionality please set 'notify_only=0' in 
> /etc/yum/pluginconf.d/search-disabled-repos.conf
> **
> 
> Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman)
>Requires: foreman-release = 1.14.3-1.el7
>Removing: foreman-release-1.14.3-1.el7.noarch (@foreman)
>foreman-release = 1.14.3-1.el7
>Updated By: foreman-release-1.15.3-1.el7.noarch (/foreman-release)
>foreman-release = 1.15.3-1.el7
>Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC1.el7
>Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC2.el7
>Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC3.el7
>Available: foreman-release-1.14.0-1.el7.noarch (foreman)
>foreman-release = 1.14.0-1.el7
>Available: foreman-release-1.14.1-1.el7.noarch (foreman)
>foreman-release = 1.14.1-1.el7
>Available: foreman-release-1.14.2-1.el7.noarch (foreman)
>foreman-release = 1.14.2-1.el7
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
> 
> Louis
> 
> On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:
> We are happy to announce the GA of Katello 3.4.4. This release contains a 
> large number of bug fixes for both small UI issues, user issues found while 
> using 3.4.4 and developer found issues that we felt would bring more 
> stability to users.
> 
> The highlights are too numerous to outline here, so

Re: [foreman-users] Re: Katello 3.4.4 Released

2017-08-14 Thread Eric D Helms

I would recommend removing foreman-plugin and then doing the upgrade.
That's not a package that is typically installed or required on a system.

On Mon, Aug 14, 2017 at 3:47 PM, Louis Bohm  wrote:

> I love having infinite history...  Here is the ouput of the command:
> [root@fm yum.repos.d]# yum update  http://yum.theforeman.org/
> releases/1.15/el7/x86_64/foreman-release.rpm
> Loaded plugins: fastestmirror, package_upload, product-id,
> search-disabled-repos, subscription-
>   : manager, tracer_upload
> foreman-release.rpm |
>  16 kB  00:00:00
> Examining /var/tmp/yum-root-qoYoPs/foreman-release.rpm:
> foreman-release-1.15.3-1.el7.noarch
> Marking /var/tmp/yum-root-qoYoPs/foreman-release.rpm as an update to
> foreman-release-1.14.3-1.el7.noarch
> Resolving Dependencies
> --> Running transaction check
> ---> Package foreman-release.noarch 0:1.14.3-1.el7 will be updated
> --> Processing Dependency: foreman-release = 1.14.3-1.el7 for package:
> foreman-plugin-1.14.3-1.el7.noarch
> Loading mirror speeds from cached hostfile
>  * base: ftpmirror.your.org
>  * epel: mirror.metrocast.net
>  * extras: mirrors.centos.webair.com
>  * updates: mirrors.lga7.us.voxel.net
> ---> Package foreman-release.noarch 0:1.15.3-1.el7 will be an update
> --> Finished Dependency Resolution
> Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman)
>Requires: foreman-release = 1.14.3-1.el7
>Removing: foreman-release-1.14.3-1.el7.noarch (@foreman)
>foreman-release = 1.14.3-1.el7
>Updated By: foreman-release-1.15.3-1.el7.noarch
> (/foreman-release)
>foreman-release = 1.15.3-1.el7
>Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC1.el7
>Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC2.el7
>Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC3.el7
>Available: foreman-release-1.14.0-1.el7.noarch (foreman)
>foreman-release = 1.14.0-1.el7
>Available: foreman-release-1.14.1-1.el7.noarch (foreman)
>foreman-release = 1.14.1-1.el7
>Available: foreman-release-1.14.2-1.el7.noarch (foreman)
>foreman-release = 1.14.2-1.el7
> **
> yum can be configured to try to resolve such errors by temporarily enabling
> disabled repos and searching for missing dependencies.
> To enable this functionality please set 'notify_only=0' in
> /etc/yum/pluginconf.d/search-disabled-repos.conf
> **
>
> Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman)
>Requires: foreman-release = 1.14.3-1.el7
>Removing: foreman-release-1.14.3-1.el7.noarch (@foreman)
>foreman-release = 1.14.3-1.el7
>Updated By: foreman-release-1.15.3-1.el7.noarch
> (/foreman-release)
>foreman-release = 1.15.3-1.el7
>Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC1.el7
>Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC2.el7
>Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman)
>foreman-release = 1.14.0-0.1.RC3.el7
>Available: foreman-release-1.14.0-1.el7.noarch (foreman)
>foreman-release = 1.14.0-1.el7
>Available: foreman-release-1.14.1-1.el7.noarch (foreman)
>foreman-release = 1.14.1-1.el7
>Available: foreman-release-1.14.2-1.el7.noarch (foreman)
>foreman-release = 1.14.2-1.el7
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
>
> Louis
>
> On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:
>
>> We are happy to announce the GA of Katello 3.4.4. This release contains
>> a large number of bug fixes for both small UI issues, user issues found
>> while using 3.4.4 and developer found issues that we felt would bring more
>> stability to users.
>>
>> The highlights are too numerous to outline here, so I would recommend to
>> please look at the changelog for a full list of changes:
>>
>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>>
>> Installation:
>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>
>> Upgrade:
>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>
>>
>> Bug reporting
>> =
>> If you come across a bug in your testing, please file it and note the
>> version of Katello or Foreman that you're using in the

[foreman-users] Re: Foreman migration - is CentOS upgrade possible?

2017-08-14 Thread rglaue

Here is what one needs to do to upgrade CentOS 6 to CentOS 7 for the 
foreman server.


   1. Install a new CentOS 7 server with the same version of The Foreman 
   that is installed on the CentOS 6 server, including all plugins
   2. Discover the version of PostgreSQL that is installed on the CentOS 7 
   server, and used by The Foreman (rpm -qa | grep postgres)
   3. Download this version of the tar and zipped binary distribution of 
   the PostgreSQL server onto the CentOS 6 server
  - https://www.postgresql.org/download/linux/   (clicking on " 
  download a *tag.gz archive* of the binaries, ..." is a link to the 
  following URL)
  - https://www.enterprisedb.com/download-postgresql-binaries
  4. Shutdown services (not PostgreSQL) on the CentOS 6 server
   5. On the CentOS 6 server, extract this tar and zipped PostgreSQL 
   distribution into a directory named '/usr/local/src/pgsql/'
   6. Backup the CentOS 6 Foreman server as described in the foreman 
   documentation, except for PostgreSQL
   7. Next, backup The Foreman's PostgreSQL database on the CentOS 6 server 
   with the following command series (Postgres calls `-Fc` a "custom dump")
   - 
  - su postgres
  - /usr/local/src/pgsql/bin/pg_dump -Fc foreman > 
  /tmp/pg_centos6server_foremanFc-20170814.dump
   8. restore the postgres dump to centos 7 postgres server (Restoring the 
   dump file wants to create the database, but it doesn't, so we create it and 
   endure the resulting error message during the restore operation as shown 
   here)
   - su - postgres
  - dropdb foreman
  - createdb foreman
  - g_restore -C -d foreman 
  /tmp/pg_centos6server_foremanFc-20170814.dump
 - 
 - You will see the following output, but the restore will still 
 complete:
 - could not change directory to "/root"
 - pg_restore: [archiver (db)] Error while PROCESSING TOC:
 - pg_restore: [archiver (db)] Error from TOC entry 2897; 1262 
 16385 DATABASE foreman foreman
 - pg_restore: [archiver (db)] could not execute query: ERROR: 
  database "foreman" already exists
 - Command was: CREATE DATABASE foreman WITH TEMPLATE = 
 template0 ENCODING = 'SQL_ASCII' LC_COLLATE = 'C' LC_CTYPE = 'C';
 - WARNING: errors ignored on restore: 1
  9. Your Foreman server is now migrated from CentOS 6 to CentOS 7.


If this is your puppet master and/or certificate authority, you may want to 
perform these additional steps

   1. copy over the host configuration from centos 6 to 7 server, if you do 
   not want them to be rebuilt
  - rsync -av /var/lib/puppet/yaml/ 
  root@yourcentos7server:/var/lib/puppet/yaml/
  2. On the Puppet Master, if necessary, create a new SSL Certificate 
   for the centos 7 server with DNS Alt Name
  1. https://docs.puppet.com/pe/latest/regenerate_certs_master.html
  2. puppet cert clean yourcentos7server
  3. puppet cert generate yourcentos7server 
  --dns_alt_names=puppet,puppet.example.com,foreman.example.com
  4. restart services
   3. On Puppet Slaves, if necessary, create a new SSL Certificate with DNS 
   Alt Name
  1. add dns_alt_names to [main] section in /etc/puppet/puppet.conf
  2. change the puppet master server to the yourcentos7server in 
  /etc/puppet/puppet.conf
  3. puppet agent -t  (generates new cert)
 1. sign this cert on the master, if not autosigned
  4. restart services
   4. On CentOS 7 server, ensure the httpd, foreman, and foreman-proxy 
   services are enabled; also ensure firewalld settings are correct

-RG


On Monday, February 8, 2016 at 10:09:50 AM UTC-6, Gato Pardo wrote:
>
>
> Hello!
>
> We have been using Foreman for quite a while and we're very happy with it 
> This may be the first time we try to do something that is not already 
> documented.
>
> We're currently using Foreman 1.10.1 in a CentOS 6 machine, but now time 
> comes to upgrade to CentOS 7 since we're standardizing all machines in the 
> new OS.
>
> I tried to migrate the server, with the backup - restore process as shown 
> in the documentation (0). The result is not 100% correct, although I would 
> say it mostly works since our installation is pretty simple (we use Foreman 
> for the ENC and report visualization mostly).
>
> I've got a bunch of database errors when importing the backup like:
>
> pg_restore: [archiver (db)] could not execute query: ERROR:  constraint 
> "user_roles_role_id_fk" for relation "user_roles" already exists
> Command was: ALTER TABLE ONLY user_roles
> ADD CONSTRAINT user_roles_role_id_fk FOREIGN KEY (role_id) REFERENCES 
> roles(id);
>
> I wasn't able to find any documentation or experiences, so would anyone 
> have some experience with that kind of upgrade? May I had been imp

Re: [foreman-users] Re: Katello 3.4.4 Released

2017-08-14 Thread Eric D Helms

On Mon, Aug 14, 2017 at 12:14 PM, Louis Bohm  wrote:

>
> Having major issues upgrading from Katello 3.3 to 3.4 on CentOS 7.3.1611.
>
> For starters running: yum update -y http://fedorapeople.org/
> groups/katello/releases/yum/3.4/katello/el7/x86_64/katello-
> repos-latest.rpm fails because http-parser and http-parser-devel are not
> found.  I found them and had to manually install them.
>

This one is strange, as it appears they pulled these packages from EPEL :/
We'll have to investigate this further.


>
> Then yum update -y http://yum.theforeman.org/releases/1.15/el7/x86_64/
> foreman-release.rpm fails because I have foreman-plugin-1.14.3-1.el7.noarch.
> Cannot update the plugins because foreman-release has not been upgraded.  I
> am running this on a VM so I tried to remove foreman-plugin and go that
> way.  But that failed miserably.  I have tried just manually changing the
> version numbers in the foreman repos from 1.14 to 1.15 but still same
> errors.
>
>
Can you give more information regarding your first statement? Why does that
first statement fail? Got yum output?


> Whats the fix for this???  I have to say going from Katello 3.2 to 3.3 was
> no where nearly as difficult as this.
>
> Louis
> On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:
>>
>> We are happy to announce the GA of Katello 3.4.4. This release contains
>> a large number of bug fixes for both small UI issues, user issues found
>> while using 3.4.4 and developer found issues that we felt would bring more
>> stability to users.
>>
>> The highlights are too numerous to outline here, so I would recommend to
>> please look at the changelog for a full list of changes:
>>
>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md
>>
>> Installation:
>> https://theforeman.org/plugins/katello/3.4/installation/index.html
>>
>> Upgrade:
>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>>
>>
>> Bug reporting
>> =
>> If you come across a bug in your testing, please file it and note the
>> version of Katello or Foreman that you're using in the report.
>>
>> http://projects.theforeman.org/projects/katello/issues/new
>>
>> --
>> 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.
>



-- 
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] Re: Katello 3.4.4 Released

2017-08-14 Thread Louis Bohm

Having major issues upgrading from Katello 3.3 to 3.4 on CentOS 7.3.1611.

For starters running: yum update -y 
http://fedorapeople.org/groups/katello/releases/yum/3.4/katello/el7/x86_64/katello-repos-latest.rpm

fails because http-parser and http-parser-devel are not found.  I found 
them and had to manually install them.

Then yum update -y 
http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm 
fails because I have foreman-plugin-1.14.3-1.el7.noarch.  Cannot update the 
plugins because foreman-release has not been upgraded.  I am running this 
on a VM so I tried to remove foreman-plugin and go that way.  But that 
failed miserably.  I have tried just manually changing the version numbers 
in the foreman repos from 1.14 to 1.15 but still same errors.

Whats the fix for this???  I have to say going from Katello 3.2 to 3.3 was 
no where nearly as difficult as this.

Louis
On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:
>
> We are happy to announce the GA of Katello 3.4.4. This release contains a 
> large number of bug fixes for both small UI issues, user issues found while 
> using 3.4.4 and developer found issues that we felt would bring more 
> stability to users.
>
> The highlights are too numerous to outline here, so I would recommend to 
> please look at the changelog for a full list of changes:
>
> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md  
>
> Installation:
> https://theforeman.org/plugins/katello/3.4/installation/index.html
>
> Upgrade:
> https://theforeman.org/plugins/katello/3.4/upgrade/index.html
>
>
> Bug reporting
> =
> If you come across a bug in your testing, please file it and note the
> version of Katello or Foreman that you're using in the report.
>
> http://projects.theforeman.org/projects/katello/issues/new
>
> -- 
> 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.

Re: [foreman-users] Katello 3.4.4 Released

Re: [foreman-users] Katello 3.4.4 Released

Re: [foreman-users] Katello 3.4.4 Released

Re: [foreman-users] Re: Katello 3.4.4 Released

[foreman-users] Re: Foreman migration - is CentOS upgrade possible?

Re: [foreman-users] Re: Katello 3.4.4 Released

[foreman-users] Re: Katello 3.4.4 Released

7 matches

Site Navigation

Mail list logo

Footer information