#7971 Staging database for kerneltest
Closed: Fixed a year ago by kevin. Opened a year ago by jcline.

I'm working on getting a kerneltest stage environment set up in OpenShift. As far as I can tell it does not currently have a database in staging so I'd like a user and database set up for it.


You just need the db created and username/password added to private to access it?

Do you have an initial schema, or would you prefer to set that up yourself?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

a year ago

I've attached a pg_dump from an empty database: kerneltest.sql

It turns out there is a database there. You should be able to access it with private vars: kerneltest_db_user and kerneltest_db_pass connecting to kerneltest_db_host.

Can you see if that works for you, if not I can wipe it and make a new db/user.

That's the staging database? Those variables are in use by the current kerneltest role so I assumed that was the production database.

If that is indeed the staging database, can you wipe it? There's not a migration path from the old database schema to the new one since it didn't seem worth the effort to save very old test results for kernels we'll never look at again.

Yeah, stg and prod were using the same variables/passwords. Sigh.

So, I made all new stg versions of those.

There is currently a kerneltest01.stg.phx2.fedoraproject.org vm thats holding the database open. Would you like me to nuke it entirely, just stop httpd on it so I can wipe the db, or something else?

I replied via IRC, but just for the permanent record nuking the staging kerneltest is fine.

ok. I have:

  • nuked the kerneltest01.stg.phx2.fedoraproject.org instance
  • dropped the old db
  • set the kerneltestuser password to the one in private 'kerneltest_stg_db_pass'
  • created the db owned by that user
  • loaded the schema you had attached here.

It came up with some errors on loading:

ERROR: syntax error at or near "AS"
LINE 2: AS integer

I'm happy to wipe it and reload or you can adjust it from the user.

Let us know if you need anything else.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.