Customer Case testing for database issues (#16566)

* Customer Case testing for database issues

* Change test name

Co-authored-by: vsedmik <46570670+vsedmik@users.noreply.github.com>

---------

Co-authored-by: vsedmik <46570670+vsedmik@users.noreply.github.com>
(cherry picked from commit 3c57c25)

tests/foreman/api/test_contentview.py

@@ -1080,6 +1080,28 @@ def test_cv_audit_scenarios(self, module_product, target_sat):
         assert not self.yumcv.read().needs_publish
 
 
+@pytest.mark.tier2
+def test_repository_rpms_id_type(target_sat):
+    """Katello_repository_rpms_id_seq needs to have the type bigint to allow
+    repeated publishing of Content Views by customers.
+
+    :id: a506782f-1edd-4568-99bb-d289212156ba
+
+    :steps:
+        1. Login to the Satellite cli and access the foreman posgres shell
+        2. Search for katello_repository_rpms_id_seq
+
+    :expectedresults: katello_repository_rpms_id_seq should have the type bigint, and not the type integer
+
+    :CaseImportance: Medium
+    """
+    db_out = target_sat.execute(
+        'sudo -u postgres psql -d foreman -c "select * from pg_sequences where sequencename=\'katello_repository_rpms_id_seq\';"'
+    )
+    assert 'bigint' in db_out.stdout
+    assert 'integer' not in db_out.stdout
+
+
 @pytest.mark.tier2
 def test_negative_readonly_user_actions(
     target_sat, function_role, content_view, module_org, module_lce