Red Hat Satellite 5.7 Documentation Released
Hi folks,
We've released the documentation set for Satellite 5.7. There have been a number of documentation changes since Satellite 5.6 that I want to highlight.
Firstly, there is new content for a bunch of new features. I've included a high-level list in the Release Notes for 5.7.
We've also restructured some of the documentation to help clarify certain processes.
I'm also looking to improve our Satellite 5.7 documentation suite over time so please feel free to let me know if you've got any suggestions for improvements or if you hit any roadblocks while following certain procedures.
Sincerely,
Dan Macpherson
Responses
Can the install be configured to get PostgreSQL 9.2 storing it's data back in /var/lib/pgsql/data?
I'm downloading all the ISO & channels right now, but have a heavily scripted kickstart to build our 5.4 -> 5.6^H7 migration system. If I can't point PostgreSQL 9.2 back at /var/lib/pgsql, I'll need to revisit the partition table in the kickstart and figure out which part of /opt/rh/postgresql92/root/var/lib/pgsql/data I should create as the new partition before the software has been installed.
We are indeed, although I didn't think of the contexts initially. Now you point it out, I think it's best not to take chances where SELinux is concerned.
I just find it a bit odd that I've now moved my database location 3 times in 3 upgrades; from the Embedded Oracle directory to /var/lib/pgsql to /opt/rh/postgresql92/root/var/lib/pgsql/data. Especially since the last migration was still effectively using the same database software (different version of pgsql notwithstanding).
I'll just change the mount point again. Would have been nice to have allowed the data to stay in the same place when upgrading from 5.6 to 5.7. I can't see my system running any other version of pgsql, so it's not as if there's going to be anything else going into /var/lib/pgsql now.
Got to say that it looks like Satellite 5.7 was released too early. My issues might only affect Embedded database installations, but so far I've found:
1) database space check still checks the /var/lib/pgsql/data directory rather than the new location
2) PostgreSQL92 not happy creating a database if /opt/rh/postgresql92/root/var/lib/pgsql/data is mounted as a partition (as detailed in the Install Guide).
Think I've got past those with 2 workarounds at the moment. Yes - RH Support are aware and both issues raised as internal bugzillas I think. Hopefully I'm in for a smooth ride from here on in!
Update: The workarounds, in case it helps others, are:
1) Use the --skip-db-diskspace-check flag on the install.pl command
2) Create /postgresql92/root/var/lib/pgsql as the mount point, then create the data subfolder manually
Now stumped with the inability to run Embedded PostgreSQL unless SELinux is DISABLED. Not permissive - disabled.
Looking good once all that's done, but I'm not in the habit of running production systems with so many workarounds. So it's there for the Admins to have a poke around with for now.
Liking what we see so far...
Deleted this comment & moved the satellite 6 comment I had made here to this existing discussion...
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
