Re: [Pulp-list] Pulp-list Digest, Vol 126, Issue 47

[Bin Li (BLOOMBERG/ 120 PARK)]

/backends/base/schema.py\",
> line 447, in add_field", " self.execute(sql, params)", " File
> 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
> line 137, in execute", " cursor.execute(sql, params)", " File
> 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 67, in execute", " return self._execute_with_wrappers(sql, params,
> many=False, executor=self._execute)", " File
> 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 76, in _execute_with_wrappers", " return executor(sql, params, many,
> context)", " File
> 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 84, in _execute", " return self.cursor.execute(sql, params)", " File
> 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\",
> line 89, in __exit__", " raise dj_exc_value.with_traceback(traceback) from
> exc_value", " File
> 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 84, in _execute", " return self.cursor.execute(sql, params)",
> "django.db.utils.IntegrityError: column \"last_sync_revision_number\"
> contains null values"], "stdout": "Operations to perform:\n Apply all
> migrations: admin, auth, contenttypes, core, file, rpm, sessions\nRunning
> migrations:\n Applying rpm.0005_optimize_sync...", "stdout_lines":
> ["Operations to perform:", " Apply all migrations: admin, auth,
> contenttypes, core, file, rpm, sessions", "Running migrations:", " Applying
> rpm.0005_optimize_sync..."]}
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://www.redhat.com/archives/pulp-list/attachments/20200528/b72a1bd7/atta
chment.html>

--

Message: 2
Date: Fri, 29 May 2020 03:26:21 -
From: "Bin Li (BLOOMBERG/ 120 PARK)" 
To: dkli...@redhat.com
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3 migration error
Message-ID: <5ED080DD013F001C003900BF_0_6156@msllnjpmsgsv06>
Content-Type: text/plain; charset="utf-8"

Yes, we are trying to upgrade to 3.3.2.

From: dkli...@redhat.com At: 05/28/20 17:13:05To:  Bin Li (BLOOMBERG/ 120 PARK 
) 
Cc:  pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3 migration error

Are you upgrading to pulp-rpm 3.3.2? 

On Thu, May 28, 2020 at 5:08 PM Bin Li (BLOOMBERG/ 120 PARK) 
 wrote:

Hi All,Getting a new error when migrate from 3.2 to 3.3. Please advise if this 
can be fixed manually.

TASK [pulp_database : Run database migrations] 


fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd": 
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"], 
"delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg": 
"non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333", 
"stderr": "Traceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backen
ds/utils.py\", line 84, in _execute\nreturn self.cursor.execute(sql, 
params)\npsycopg2.errors.NotNullViolation: column \"last_sync_revision_number\" 
contains null values\n\n\nThe above exception was the direct cause of the 
following exception:\n\nTraceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in \n
sys.exit(execute_from_command_line())\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/mana
gement/__init__.py\", line 381, in execute_from_command_line\n
utility.execute()\n  File \"/opt/utils
 
/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py
\", line 375, in execute\n
self.fetch_command(subcommand).run_from_argv(self.argv)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/mana
gement/base.py\", line 323, in run_from_argv\nself.execute(*args, 
**cmd_options)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/mana
gement/base.py\", line 364, in execute\noutput = self.handle(*args, 
**optio

[Pulp-list] pulp 3.3 content server not able to retrieve pkg.

[Bin Li (BLOOMBERG/ 120 PARK)]

We did a fresh install of 3.3. After sysing repos from remote, got 404 error 
when try to retrieve the packages from repo.

# wget 
http://localhost:24816/pulp/content/system3rdparty/7.3/admin-python-36-3.6.5-2.el7.x86_64.rpm
--2020-05-28 23:31:05--  
http://localhost:24816/pulp/content/system3rdparty/7.3/admin-python-36-3.6.5-2.el7.x86_64.rpm
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:24816... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-05-28 23:31:06 ERROR 404: Not Found.


We are able to see the rpm though api but not able to wget
Here are the info of the distribution, publication, and repo.

{'base_path': 'system3rdparty/7.3',
 'base_url': 
'http://ip-1-76-158-244.drr1.bcpc.bloomberg.com/pulp/content/system3rdparty/7.3',
 'content_guard': None,
 'name': 'systems_third_party_rhel7.3',
 'publication': 
'/pulp/api/v3/publications/rpm/rpm/78ed2012-feb1-452c-bf0f-20c877afc3a0/',
 'pulp_created': datetime.datetime(2020, 5, 9, 5, 11, 47, 639184, 
tzinfo=tzutc()),
 'pulp_href': 
'/pulp/api/v3/distributions/rpm/rpm/7134856d-de97-4ef1-a425-241a9f425c63/'}
{'metadata_checksum_type': 'sha256',
 'package_checksum_type': 'sha256',
 'pulp_created': datetime.datetime(2020, 5, 28, 20, 33, 36, 140455, 
tzinfo=tzutc()),
 'pulp_href': 
'/pulp/api/v3/publications/rpm/rpm/78ed2012-feb1-452c-bf0f-20c877afc3a0/',
 'repository': 
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/',
 'repository_version': 
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/versions/7/'}
{'description': 'system  party 7.3',
 'latest_version_href': 
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/versions/7/',
 'metadata_signing_service': None,
 'name': 'systems_third_party_rhel7.3',
 'pulp_created': datetime.datetime(2020, 5, 9, 5, 6, 8, 781604, tzinfo=tzutc()),
 'pulp_href': 
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/',
 'versions_href': 
'/pulp/api/v3/repositories/rpm/rpm/bda99ecf-90da-4a18-ae84-baf86c3ba1da/versions/'}


# ./sget status
{
"versions": [
{
"component": "pulpcore",
"version": "3.3.1"
},
{
"component": "pulp_rpm",
"version": "3.3.2"
},
{
"component": "pulp_file",
"version": "0.3.0"
}
],
"online_workers": [
{
"pulp_href": 
"/pulp/api/v3/workers/86605b78-6d6b-4ad4-bb8f-cf9885c5f90d/",
"pulp_created": "2020-05-09T05:05:55.272910Z",
"name": "resource-manager",
"last_heartbeat": "2020-05-29T03:35:29.913501Z"
},
{
"pulp_href": 
"/pulp/api/v3/workers/b373a038-e8bc-4207-aba3-eefc816cadb3/",
"pulp_created": "2020-05-29T02:58:28.912571Z",
"name": "116...@ip-1-76-158-244.drr1.bcpc.bloomberg.com",
"last_heartbeat": "2020-05-29T03:35:32.817973Z"
},
{
"pulp_href": 
"/pulp/api/v3/workers/e9b7b7c2-c86d-4d2d-b887-17b48d16dc41/",
"pulp_created": "2020-05-29T02:58:29.248424Z",
"name": "116...@ip-1-76-158-244.drr1.bcpc.bloomberg.com",
"last_heartbeat": "2020-05-29T03:35:33.419618Z"
}
],
"online_content_apps": [
{
"name": "116...@ip-1-76-158-244.drr1.bcpc.bloomberg.com",
"last_heartbeat": "2020-05-29T03:35:28.815660Z"
},
{
"name": "116...@ip-1-76-158-244.drr1.bcpc.bloomberg.com",
"last_heartbeat": "2020-05-29T03:35:28.818255Z"
}
],
"database_connection": {
"connected": true
},
"redis_connection": {
"connected": true
},
"storage": {
"total": 21463281664,
"used": 18353487872,
"free": 3109793792
}
}

We never had issues with this in all previous pulp 3 release. Please help.___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] pulp 3.3 migration error

[Bin Li (BLOOMBERG/ 120 PARK)]

Yes, we are trying to upgrade to 3.3.2.

From: dkli...@redhat.com At: 05/28/20 17:13:05To:  Bin Li (BLOOMBERG/ 120 PARK 
) 
Cc:  pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3 migration error

Are you upgrading to pulp-rpm 3.3.2? 

On Thu, May 28, 2020 at 5:08 PM Bin Li (BLOOMBERG/ 120 PARK) 
 wrote:

Hi All,Getting a new error when migrate from 3.2 to 3.3. Please advise if this 
can be fixed manually.

TASK [pulp_database : Run database migrations] 

fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd": 
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"], 
"delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg": 
"non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333", 
"stderr": "Traceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, 
params)\npsycopg2.errors.NotNullViolation: column \"last_sync_revision_number\" 
contains null values\n\n\nThe above exception was the direct cause of the 
following exception:\n\nTraceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in \n
sys.exit(execute_from_command_line())\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
 line 381, in execute_from_command_line\nutility.execute()\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
 line 375, in execute\n
self.fetch_command(subcommand).run_from_argv(self.argv)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 323, in run_from_argv\nself.execute(*args, **cmd_options)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 364, in execute\noutput = self.handle(*args, **options)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 83, in wrapped\nres = handle_func(*args, **kwargs)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
 line 234, in handle\nfake_initial=fake_initial,\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 117, in migrate\nstate = self._migrate_all_forwards(state, plan, 
full_plan, fake=fake, fake_initial=fake_initial)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 147, in _migrate_all_forwards\nstate = self.apply_migration(state, 
migration, fake=fake, fake_initial=fake_initial)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 245, in apply_migration\nstate = migration.apply(state, 
schema_editor)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
 line 124, in apply\noperation.database_forwards(self.app_label, 
schema_editor, old_state, project_state)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
 line 112, in database_forwards\nfield,\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
 line 447, in add_field\nself.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
 line 137, in execute\ncursor.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 67, in execute\nreturn self._execute_with_wrappers(sql, params, 
many=False, executor=self._execute)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 76, in _execute_with_wrappers\nreturn executor(sql, params, many, 
context)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\",
 line 89, in __exit__\nraise dj_exc_value.with_traceback(traceback) from 
exc_value\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, 
params)\ndjango.db.utils.IntegrityError: column \"last_sync_revision_number\" 
contains null values", "stderr_lines": ["Traceback (most recent call last):", " 
 File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute", "return self.cursor.execute(sql, params)", 
"psycopg

Re: [Pulp-list] pulp 3.3 migration error

[Dennis Kliban]

Are you upgrading to pulp-rpm 3.3.2?

On Thu, May 28, 2020 at 5:08 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:

> Hi All,
> Getting a new error when migrate from 3.2 to 3.3. Please advise if this
> can be fixed manually.
>
> TASK [pulp_database : Run database migrations]
> 
> fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd":
> ["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"],
> "delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg":
> "non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333",
> "stderr": "Traceback (most recent call last):\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 84, in _execute\n return self.cursor.execute(sql,
> params)\npsycopg2.errors.NotNullViolation: column
> \"last_sync_revision_number\" contains null values\n\n\nThe above exception
> was the direct cause of the following exception:\n\nTraceback (most recent
> call last):\n File \"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8,
> in \n sys.exit(execute_from_command_line())\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
> line 381, in execute_from_command_line\n utility.execute()\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
> line 375, in execute\n
> self.fetch_command(subcommand).run_from_argv(self.argv)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
> line 323, in run_from_argv\n self.execute(*args, **cmd_options)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
> line 364, in execute\n output = self.handle(*args, **options)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
> line 83, in wrapped\n res = handle_func(*args, **kwargs)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
> line 234, in handle\n fake_initial=fake_initial,\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
> line 117, in migrate\n state = self._migrate_all_forwards(state, plan,
> full_plan, fake=fake, fake_initial=fake_initial)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
> line 147, in _migrate_all_forwards\n state = self.apply_migration(state,
> migration, fake=fake, fake_initial=fake_initial)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
> line 245, in apply_migration\n state = migration.apply(state,
> schema_editor)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
> line 124, in apply\n operation.database_forwards(self.app_label,
> schema_editor, old_state, project_state)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
> line 112, in database_forwards\n field,\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
> line 447, in add_field\n self.execute(sql, params)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
> line 137, in execute\n cursor.execute(sql, params)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 67, in execute\n return self._execute_with_wrappers(sql, params,
> many=False, executor=self._execute)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 76, in _execute_with_wrappers\n return executor(sql, params, many,
> context)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 84, in _execute\n return self.cursor.execute(sql, params)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\",
> line 89, in __exit__\n raise dj_exc_value.with_traceback(traceback) from
> exc_value\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 84, in _execute\n return self.cursor.execute(sql,
> params)\ndjango.db.utils.IntegrityError: column
> \"last_sync_revision_number\" contains null values", "stderr_lines":
> ["Traceback (most recent call last):", " File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 84, in _execute", " return self.cursor.execute(sql, params)",
> "psycopg2.errors.NotNullViolation: column \"last_sync_revision_number\"
> contains null values", "", "", "The above exception was the direct cause of
> the following exception:", "", "Traceback (most

[Pulp-list] pulp 3.3 migration error

[Bin Li (BLOOMBERG/ 120 PARK)]

Hi All,Getting a new error when migrate from 3.2 to 3.3. Please advise if this 
can be fixed manually.

TASK [pulp_database : Run database migrations] 

fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd": 
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"], 
"delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg": 
"non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333", 
"stderr": "Traceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, 
params)\npsycopg2.errors.NotNullViolation: column \"last_sync_revision_number\" 
contains null values\n\n\nThe above exception was the direct cause of the 
following exception:\n\nTraceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in \n
sys.exit(execute_from_command_line())\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
 line 381, in execute_from_command_line\nutility.execute()\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
 line 375, in execute\n
self.fetch_command(subcommand).run_from_argv(self.argv)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 323, in run_from_argv\nself.execute(*args, **cmd_options)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 364, in execute\noutput = self.handle(*args, **options)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 83, in wrapped\nres = handle_func(*args, **kwargs)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
 line 234, in handle\nfake_initial=fake_initial,\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 117, in migrate\nstate = self._migrate_all_forwards(state, plan, 
full_plan, fake=fake, fake_initial=fake_initial)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 147, in _migrate_all_forwards\nstate = self.apply_migration(state, 
migration, fake=fake, fake_initial=fake_initial)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 245, in apply_migration\nstate = migration.apply(state, 
schema_editor)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
 line 124, in apply\noperation.database_forwards(self.app_label, 
schema_editor, old_state, project_state)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
 line 112, in database_forwards\nfield,\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
 line 447, in add_field\nself.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
 line 137, in execute\ncursor.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 67, in execute\nreturn self._execute_with_wrappers(sql, params, 
many=False, executor=self._execute)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 76, in _execute_with_wrappers\nreturn executor(sql, params, many, 
context)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\",
 line 89, in __exit__\nraise dj_exc_value.with_traceback(traceback) from 
exc_value\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, 
params)\ndjango.db.utils.IntegrityError: column \"last_sync_revision_number\" 
contains null values", "stderr_lines": ["Traceback (most recent call last):", " 
 File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute", "return self.cursor.execute(sql, params)", 
"psycopg2.errors.NotNullViolation: column \"last_sync_revision_number\" 
contains null values", "", "", "The above exception was the direct cause of the 
following exception:", "", "Traceback (most recent call last):", "  File 
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in ", "
sys.exit(execute_from_

Re: [Pulp-list] Syncing Red hat Repos entitlement issue

[Gravel Bone]

Also, I shut the service down and ensured it wasn't running and while the
entitlement file in /etc/pki/entitltements didn't change the syncs still
failed with the issue...so while yes, it rhsmcertd can be the culprit,
there's something else on Red Hat side maybe?

On Thu, May 28, 2020 at 12:24 PM Myers, Mike  wrote:

> It’s 100% the rhsmcertd process that’s doing it.  From the man page:
>
>
>
>rhsmcertd - Periodically scans and updates the entitlement
> certificates on a registered system.
>
>
>
> What I’m unclear on is why the certs get changed by Red Hat so often when
> our entitlements certainly haven’t.  And more importantly, what, if
> anything, we can do to integrate that process more closely with Pulp.
>
>
>
> And to be clear, I’m not trying to call this out as a Pulp project problem
> or issue, just wondering if others who use the project have insights or
> solutions they’re willing to share.
>
>
>
> Cheers,
>
> *Mike Myers*
>
>
>
>
>
> *From: *Brian Bouterse 
> *Date: *Thursday, May 28, 2020 at 8:52 AM
> *To: *Gravel Bone 
> *Cc: *Mike Myers , "pulp-list@redhat.com" <
> pulp-list@redhat.com>
> *Subject: *Re: [Pulp-list]  Syncing Red hat Repos entitlement
> issue
>
>
>
> One idea to track down which process is editing those certs/files would be
> to use auditd or systemtap https://unix.stackexchange.com/a/99091
> 
> Just a thought I wanted to share.
>
>
>
> On Thu, May 28, 2020 at 9:18 AM Gravel Bone  wrote:
>
> In this case the entitlement certs themselves aren't expired from a date
> perspective, they just no longer work connecting to Red Hat.It's more
> like they've been revoked because the server they are on got new
> entitlement certs which is happening automatically, I just have not figured
> out how to prevent that.   I've tried turning of rhsmcertd, disabled
> subscription management, and combinations in between.
>
>
>
> On Wed, May 27, 2020 at 2:23 PM Brian Bouterse 
> wrote:
>
> If the certs are short-lived, then there isn't much to do except ask the
> issuer to give you longer ones. You could inspect the certs more closely I
> believe using the `rct cat-crt` command. Pulp-certguard has some docs
> showing an example with that tool
> https://pulp-certguard.readthedocs.io/en/latest/debugging.html#checking-authorized-urls-in-rhsm-certificates
> 
>
>
>
> On Wed, May 27, 2020 at 11:20 AM Myers, Mike  wrote:
>
> We’ve faced that too.  I’ve love some deeper insight, but what I’ve found
> so far is that “rhsmcertd” process does some sort of check/update on those
> certs.  We’ve just set a process to pull those from /etc/pki/entitlement
> into Pulp when such a failure occurs.  It would be nice if there were a
> Pulp native way to address this (short of running the whole Satellite suite)
>
>
>
> Cheers,
>
> *Mike Myers*
>
>
>
> *From: * on behalf of Gravel Bone <
> gravelb...@gmail.com>
> *Date: *Wednesday, May 27, 2020 at 5:48 AM
> *To: *"pulp-list@redhat.com" 
> *Subject: *[Pulp-list] Syncing Red hat Repos entitlement issue
>
>
>
> This is probably something straight forward, but my searches have found
> nothing...
>
>
>
> I pull an entitlement files from our server (well three for three
> different subscriptions) and create repos using them to sync the
> corresponding Red Hat repository.The problem is, the entitlements seem
> to expire about every month.   I'm sure it's something I'm missing that
> stupid obvious, but google has not been my friend nor has the
> documentation...help would be appreciated...
>
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
> 
>
>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Syncing Red hat Repos entitlement issue

[Myers, Mike]

It’s 100% the rhsmcertd process that’s doing it.  From the man page:

   rhsmcertd - Periodically scans and updates the entitlement certificates 
on a registered system.

What I’m unclear on is why the certs get changed by Red Hat so often when our 
entitlements certainly haven’t.  And more importantly, what, if anything, we 
can do to integrate that process more closely with Pulp.

And to be clear, I’m not trying to call this out as a Pulp project problem or 
issue, just wondering if others who use the project have insights or solutions 
they’re willing to share.

Cheers,
Mike Myers


From: Brian Bouterse 
Date: Thursday, May 28, 2020 at 8:52 AM
To: Gravel Bone 
Cc: Mike Myers , "pulp-list@redhat.com" 

Subject: Re: [Pulp-list]  Syncing Red hat Repos entitlement issue

One idea to track down which process is editing those certs/files would be to 
use auditd or systemtap 
https://unix.stackexchange.com/a/99091
  Just a thought I wanted to share.

On Thu, May 28, 2020 at 9:18 AM Gravel Bone 
mailto:gravelb...@gmail.com>> wrote:
In this case the entitlement certs themselves aren't expired from a date 
perspective, they just no longer work connecting to Red Hat.It's more like 
they've been revoked because the server they are on got new entitlement certs 
which is happening automatically, I just have not figured out how to prevent 
that.   I've tried turning of rhsmcertd, disabled subscription management, and 
combinations in between.

On Wed, May 27, 2020 at 2:23 PM Brian Bouterse 
mailto:bmbou...@redhat.com>> wrote:
If the certs are short-lived, then there isn't much to do except ask the issuer 
to give you longer ones. You could inspect the certs more closely I believe 
using the `rct cat-crt` command. Pulp-certguard has some docs showing an 
example with that tool 
https://pulp-certguard.readthedocs.io/en/latest/debugging.html#checking-authorized-urls-in-rhsm-certificates

On Wed, May 27, 2020 at 11:20 AM Myers, Mike 
mailto:mike.my...@nike.com>> wrote:
We’ve faced that too.  I’ve love some deeper insight, but what I’ve found so 
far is that “rhsmcertd” process does some sort of check/update on those certs.  
We’ve just set a process to pull those from /etc/pki/entitlement into Pulp when 
such a failure occurs.  It would be nice if there were a Pulp native way to 
address this (short of running the whole Satellite suite)

Cheers,
Mike Myers

From: mailto:pulp-list-boun...@redhat.com>> on 
behalf of Gravel Bone mailto:gravelb...@gmail.com>>
Date: Wednesday, May 27, 2020 at 5:48 AM
To: "pulp-list@redhat.com" 
mailto:pulp-list@redhat.com>>
Subject: [Pulp-list] Syncing Red hat Repos entitlement issue

This is probably something straight forward, but my searches have found 
nothing...

I pull an entitlement files from our server (well three for three different 
subscriptions) and create repos using them to sync the corresponding Red Hat 
repository.The problem is, the entitlements seem to expire about every 
month.   I'm sure it's something I'm missing that stupid obvious, but google 
has not been my friend nor has the documentation...help would be appreciated...
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp-list Digest, Vol 126, Issue 44

[Bin Li (BLOOMBERG/ 120 PARK)]

I figured it out the issue.  The 3.3 installer works after I pin plugins.

pulp_install_plugins:
  pulp-file:
#upgrade: true
version: '0.3.0'
  pulp-rpm:
#upgrade: true
version: '3.3.2'


From: pulp-list@redhat.com At: 05/28/20 12:02:36To:  pulp-list@redhat.com
Subject: Pulp-list Digest, Vol 126, Issue 44

Send Pulp-list mailing list submissions to
   pulp-list@redhat.com

To subscribe or unsubscribe via the World Wide Web, visit
 https://www.redhat.com/mailman/listinfo/pulp-list
or, via email, send a message with subject or body 'help' to
 pulp-list-requ...@redhat.com

You can reach the person managing the list at
 pulp-list-ow...@redhat.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Pulp-list digest..."


Today's Topics:

   1. Pin pulp 3.3.1 (Bin Li (BLOOMBERG/ 120 PARK))


--

Message: 1
Date: Thu, 28 May 2020 15:52:04 -
From: "Bin Li (BLOOMBERG/ 120 PARK)" 
To: pulp-list@redhat.com
Subject: [Pulp-list] Pin pulp 3.3.1
Message-ID: <5ECFDE2400FF035A00390603_0_54956@msllnjpmsgsv06>
Content-Type: text/plain; charset="utf-8"

We got an error when rerun pulp_installer 3.3 after 3.4 is released.
" pulpcore==3.3.1 (from -r requirements.in (line 1))", "  pulpcore<3.4,>=3.3 
(from pulp-rpm==3.3.2)", "  pulpcore<3.5,>=3.4 (from pulp-file==1.0.0)"

How do we pin the pulpcore to 3.3 for now since we haven't test 3.4 yet in our 
dev environment?

Thanks
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://www.redhat.com/archives/pulp-list/attachments/20200528/a2d4d334/atta
chment.html>

--

___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

End of Pulp-list Digest, Vol 126, Issue 44
**


___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pin pulp 3.3.1

[Bin Li (BLOOMBERG/ 120 PARK)]

We got an error when rerun pulp_installer 3.3 after 3.4 is released.
" pulpcore==3.3.1 (from -r requirements.in (line 1))", "  pulpcore<3.4,>=3.3 
(from pulp-rpm==3.3.2)", "  pulpcore<3.5,>=3.4 (from pulp-file==1.0.0)"

How do we pin the pulpcore to 3.3 for now since we haven't test 3.4 yet in our 
dev environment?

Thanks

___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Syncing Red hat Repos entitlement issue

[Brian Bouterse]

One idea to track down which process is editing those certs/files would be
to use auditd or systemtap https://unix.stackexchange.com/a/99091  Just a
thought I wanted to share.

On Thu, May 28, 2020 at 9:18 AM Gravel Bone  wrote:

> In this case the entitlement certs themselves aren't expired from a date
> perspective, they just no longer work connecting to Red Hat.It's more
> like they've been revoked because the server they are on got new
> entitlement certs which is happening automatically, I just have not figured
> out how to prevent that.   I've tried turning of rhsmcertd, disabled
> subscription management, and combinations in between.
>
> On Wed, May 27, 2020 at 2:23 PM Brian Bouterse 
> wrote:
>
>> If the certs are short-lived, then there isn't much to do except ask the
>> issuer to give you longer ones. You could inspect the certs more closely I
>> believe using the `rct cat-crt` command. Pulp-certguard has some docs
>> showing an example with that tool
>> https://pulp-certguard.readthedocs.io/en/latest/debugging.html#checking-authorized-urls-in-rhsm-certificates
>>
>> On Wed, May 27, 2020 at 11:20 AM Myers, Mike  wrote:
>>
>>> We’ve faced that too.  I’ve love some deeper insight, but what I’ve
>>> found so far is that “rhsmcertd” process does some sort of check/update on
>>> those certs.  We’ve just set a process to pull those from
>>> /etc/pki/entitlement into Pulp when such a failure occurs.  It would be
>>> nice if there were a Pulp native way to address this (short of running the
>>> whole Satellite suite)
>>>
>>>
>>>
>>> Cheers,
>>>
>>> *Mike Myers*
>>>
>>>
>>>
>>> *From: * on behalf of Gravel Bone <
>>> gravelb...@gmail.com>
>>> *Date: *Wednesday, May 27, 2020 at 5:48 AM
>>> *To: *"pulp-list@redhat.com" 
>>> *Subject: *[Pulp-list] Syncing Red hat Repos entitlement issue
>>>
>>>
>>>
>>> This is probably something straight forward, but my searches have found
>>> nothing...
>>>
>>>
>>>
>>> I pull an entitlement files from our server (well three for three
>>> different subscriptions) and create repos using them to sync the
>>> corresponding Red Hat repository.The problem is, the entitlements seem
>>> to expire about every month.   I'm sure it's something I'm missing that
>>> stupid obvious, but google has not been my friend nor has the
>>> documentation...help would be appreciated...
>>> ___
>>> Pulp-list mailing list
>>> Pulp-list@redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-list
>>
>>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] CLI Authentication question

[Matthias Dellweg]

No, it has been like that with starting 3.0.0-dev-alpha1 (or what it
was called back then)

On Thu, May 28, 2020 at 3:06 PM Heide, Todd  wrote:
>
> Huh, ok, I had thought the Ansible would have installed it like before.  OK, 
> thanks, I will get it installed. Was this a recent change with 3.3.1?
>
> -Original Message-
> From: Matthias Dellweg 
> Sent: Thursday, May 28, 2020 7:52 AM
> To: Heide, Todd 
> Cc: Daniel Alley ; Pulp-list@redhat.com
> Subject: Re: [Pulp-list] CLI Authentication question
>
> [EXTERNAL] This message originated outside of the organization. Use caution 
> when opening files or following links in this email!
>
> You have only pulp_rpm installed (see the versions part of status).
> ISO/file support has moved into the pulp_file plugin.
>
> On Thu, May 28, 2020 at 2:45 PM Heide, Todd  
> wrote:
> >
> > Yes, you are correct, some other items are missing now that it can 
> > authenticate, base.sh works now, but other scripts are still not 
> > functioning correctly.  PUT and POST are not allowed.
> >
> > HTTP 200 OK
> > Allow: GET, HEAD, OPTIONS
> > Content-Type: application/json
> > Vary: Accept
> >
> > {
> > "versions": [
> > {
> > "component": "pulpcore",
> > "version": "3.3.1"
> > },
> > {
> > "component": "pulp_rpm",
> > "version": "3.3.2"
> > }
> > ],
> > "online_workers": [
> > {
> > "pulp_href": 
> > "/pulp/api/v3/workers/b46d78d1-7f2a-494c-9055-2e0c29d1e05b/",
> > "pulp_created": "2020-05-21T17:50:01.035050Z",
> > "name": "1...@aecdas-pulp3test.example.com",
> > "last_heartbeat": "2020-05-28T12:42:18.330629Z"
> > },
> > {
> > "pulp_href": 
> > "/pulp/api/v3/workers/97e5731f-1405-4e53-8824-39fed702c2d9/",
> > "pulp_created": "2020-05-21T17:50:02.840377Z",
> > "name": "1...@aecdas-pulp3test.example.com",
> > "last_heartbeat": "2020-05-28T12:42:20.535613Z"
> > },
> > {
> > "pulp_href": 
> > "/pulp/api/v3/workers/fef5826d-62df-4a79-8145-2e4b3495f495/",
> > "pulp_created": "2020-05-21T17:49:41.225878Z",
> > "name": "resource-manager",
> > "last_heartbeat": "2020-05-28T12:42:21.137314Z"
> > }
> > ],
> > "online_content_apps": [
> > {
> > "name": "2...@aecdas-pulp3test.example.com",
> > "last_heartbeat": "2020-05-28T12:42:23.731799Z"
> > },
> > {
> > "name": "2...@aecdas-pulp3test.example.com ",
> > "last_heartbeat": "2020-05-28T12:42:30.153881Z"
> > }
> > ],
> > "database_connection": {
> > "connected": true
> > },
> > "redis_connection": {
> > "connected": true
> > },
> > "storage": {
> > "total": 536859357184,
> > "used": 2708668416,
> > "free": 534150688768
> > }
> > }
> >
> > -Original Message-
> > From: Matthias Dellweg 
> > Sent: Thursday, May 28, 2020 4:47 AM
> > To: Daniel Alley 
> > Cc: Heide, Todd ; Pulp-list@redhat.com
> > Subject: Re: [Pulp-list] CLI Authentication question
> >
> > [EXTERNAL] This message originated outside of the organization. Use caution 
> > when opening files or following links in this email!
> >
> > It returns 404, which does not sound like missing credentials. Are you 
> > sure, the pulp_file plugin is installed? Can you access and may be post 
> > here http://localhost:24817/pulp/api/v3/status/ ?
> >
> > On Thu, May 28, 2020 at 4:32 AM Daniel Alley  wrote:
> > >
> > > Hello Todd,
> > >
> > > I believe the file you're looking for is ~/.netrc  --
> > > https://ec.haxx.se/usingcurl/usingcurl-netrc
> > >
> > > I hope that helps!
> > >
> > >
> > > On Wed, May 27, 2020 at 11:21 AM Heide, Todd  
> > > wrote:
> > >>
> > >> This is my third attempt at a working Pulp 3 server. I finally got
> > >> the REST Framework working, but, for the life of me, cannot
> > >> remember the hidden file that is used under the CLI user to
> > >> authenticate against the system.  I lost my links recently to docs,
> > >> and cannot remember what the file was called, and I didn't think to
> > >> back it up when I tore the server down.  Good news is, the UI
> > >> appears to be working, and I can log in as admin, but I am not
> > >> seeing where I can post, put, etc.  Trying to set up a repo via CLI
> > >> I get
> > >>
> > >> http POST
> > >> http://localhost:24817/pulp/api/v3/repositories/file/file/
> > >> name=foo
> > >> HTTP/1.1 404 Not Found
> > >> Connection: close
> > >> Content-Length: 77
> > >> Content-Type: text/html
> > >> Date: Wed, 27 May 2020 14:43:01 GMT
> > >> Server: gunicorn/20.0.4
> > >> X-Frame-Options: SAMEORIGIN
> > >>
> > >> Not FoundThe requested resource was not found on this
> > >> server.
> > >>
> > >> I'm thinking that the file I am referring to is the key, but I can't 
> > >> find what I am looking for.
> >

Re: [Pulp-list] Syncing Red hat Repos entitlement issue

[Gravel Bone]

In this case the entitlement certs themselves aren't expired from a date
perspective, they just no longer work connecting to Red Hat.It's more
like they've been revoked because the server they are on got new
entitlement certs which is happening automatically, I just have not figured
out how to prevent that.   I've tried turning of rhsmcertd, disabled
subscription management, and combinations in between.

On Wed, May 27, 2020 at 2:23 PM Brian Bouterse  wrote:

> If the certs are short-lived, then there isn't much to do except ask the
> issuer to give you longer ones. You could inspect the certs more closely I
> believe using the `rct cat-crt` command. Pulp-certguard has some docs
> showing an example with that tool
> https://pulp-certguard.readthedocs.io/en/latest/debugging.html#checking-authorized-urls-in-rhsm-certificates
>
> On Wed, May 27, 2020 at 11:20 AM Myers, Mike  wrote:
>
>> We’ve faced that too.  I’ve love some deeper insight, but what I’ve found
>> so far is that “rhsmcertd” process does some sort of check/update on those
>> certs.  We’ve just set a process to pull those from /etc/pki/entitlement
>> into Pulp when such a failure occurs.  It would be nice if there were a
>> Pulp native way to address this (short of running the whole Satellite suite)
>>
>>
>>
>> Cheers,
>>
>> *Mike Myers*
>>
>>
>>
>> *From: * on behalf of Gravel Bone <
>> gravelb...@gmail.com>
>> *Date: *Wednesday, May 27, 2020 at 5:48 AM
>> *To: *"pulp-list@redhat.com" 
>> *Subject: *[Pulp-list] Syncing Red hat Repos entitlement issue
>>
>>
>>
>> This is probably something straight forward, but my searches have found
>> nothing...
>>
>>
>>
>> I pull an entitlement files from our server (well three for three
>> different subscriptions) and create repos using them to sync the
>> corresponding Red Hat repository.The problem is, the entitlements seem
>> to expire about every month.   I'm sure it's something I'm missing that
>> stupid obvious, but google has not been my friend nor has the
>> documentation...help would be appreciated...
>> ___
>> Pulp-list mailing list
>> Pulp-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-list
>
>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] CLI Authentication question

[Heide, Todd]

Huh, ok, I had thought the Ansible would have installed it like before.  OK, 
thanks, I will get it installed. Was this a recent change with 3.3.1?

-Original Message-
From: Matthias Dellweg  
Sent: Thursday, May 28, 2020 7:52 AM
To: Heide, Todd 
Cc: Daniel Alley ; Pulp-list@redhat.com
Subject: Re: [Pulp-list] CLI Authentication question

[EXTERNAL] This message originated outside of the organization. Use caution 
when opening files or following links in this email!

You have only pulp_rpm installed (see the versions part of status).
ISO/file support has moved into the pulp_file plugin.

On Thu, May 28, 2020 at 2:45 PM Heide, Todd  wrote:
>
> Yes, you are correct, some other items are missing now that it can 
> authenticate, base.sh works now, but other scripts are still not functioning 
> correctly.  PUT and POST are not allowed.
>
> HTTP 200 OK
> Allow: GET, HEAD, OPTIONS
> Content-Type: application/json
> Vary: Accept
>
> {
> "versions": [
> {
> "component": "pulpcore",
> "version": "3.3.1"
> },
> {
> "component": "pulp_rpm",
> "version": "3.3.2"
> }
> ],
> "online_workers": [
> {
> "pulp_href": 
> "/pulp/api/v3/workers/b46d78d1-7f2a-494c-9055-2e0c29d1e05b/",
> "pulp_created": "2020-05-21T17:50:01.035050Z",
> "name": "1...@aecdas-pulp3test.example.com",
> "last_heartbeat": "2020-05-28T12:42:18.330629Z"
> },
> {
> "pulp_href": 
> "/pulp/api/v3/workers/97e5731f-1405-4e53-8824-39fed702c2d9/",
> "pulp_created": "2020-05-21T17:50:02.840377Z",
> "name": "1...@aecdas-pulp3test.example.com",
> "last_heartbeat": "2020-05-28T12:42:20.535613Z"
> },
> {
> "pulp_href": 
> "/pulp/api/v3/workers/fef5826d-62df-4a79-8145-2e4b3495f495/",
> "pulp_created": "2020-05-21T17:49:41.225878Z",
> "name": "resource-manager",
> "last_heartbeat": "2020-05-28T12:42:21.137314Z"
> }
> ],
> "online_content_apps": [
> {
> "name": "2...@aecdas-pulp3test.example.com",
> "last_heartbeat": "2020-05-28T12:42:23.731799Z"
> },
> {
> "name": "2...@aecdas-pulp3test.example.com ",
> "last_heartbeat": "2020-05-28T12:42:30.153881Z"
> }
> ],
> "database_connection": {
> "connected": true
> },
> "redis_connection": {
> "connected": true
> },
> "storage": {
> "total": 536859357184,
> "used": 2708668416,
> "free": 534150688768
> }
> }
>
> -Original Message-
> From: Matthias Dellweg 
> Sent: Thursday, May 28, 2020 4:47 AM
> To: Daniel Alley 
> Cc: Heide, Todd ; Pulp-list@redhat.com
> Subject: Re: [Pulp-list] CLI Authentication question
>
> [EXTERNAL] This message originated outside of the organization. Use caution 
> when opening files or following links in this email!
>
> It returns 404, which does not sound like missing credentials. Are you sure, 
> the pulp_file plugin is installed? Can you access and may be post here 
> http://localhost:24817/pulp/api/v3/status/ ?
>
> On Thu, May 28, 2020 at 4:32 AM Daniel Alley  wrote:
> >
> > Hello Todd,
> >
> > I believe the file you're looking for is ~/.netrc  -- 
> > https://ec.haxx.se/usingcurl/usingcurl-netrc
> >
> > I hope that helps!
> >
> >
> > On Wed, May 27, 2020 at 11:21 AM Heide, Todd  
> > wrote:
> >>
> >> This is my third attempt at a working Pulp 3 server. I finally got 
> >> the REST Framework working, but, for the life of me, cannot 
> >> remember the hidden file that is used under the CLI user to 
> >> authenticate against the system.  I lost my links recently to docs, 
> >> and cannot remember what the file was called, and I didn't think to 
> >> back it up when I tore the server down.  Good news is, the UI 
> >> appears to be working, and I can log in as admin, but I am not 
> >> seeing where I can post, put, etc.  Trying to set up a repo via CLI 
> >> I get
> >>
> >> http POST 
> >> http://localhost:24817/pulp/api/v3/repositories/file/file/
> >> name=foo
> >> HTTP/1.1 404 Not Found
> >> Connection: close
> >> Content-Length: 77
> >> Content-Type: text/html
> >> Date: Wed, 27 May 2020 14:43:01 GMT
> >> Server: gunicorn/20.0.4
> >> X-Frame-Options: SAMEORIGIN
> >>
> >> Not FoundThe requested resource was not found on this 
> >> server.
> >>
> >> I'm thinking that the file I am referring to is the key, but I can't find 
> >> what I am looking for.
> >>
> >>
> >> ___
> >> Pulp-list mailing list
> >> Pulp-list@redhat.com
> >> https://www.redhat.com/mailman/listinfo/pulp-list
> >>
> > ___
> > Pulp-list mailing list
> > Pulp-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/pulp-list
>


___
Pulp-list mailing list

[Pulp-list] pulpcore 3.4.0 and pulp_file 1.0.0 are Generally Available

[Dennis Kliban]

Pulpcore 3.4.0[0] and pulp_file 1.0.0 [1] have been released. For a list of
changes, please check the changelogs for pulpcore[2] and pulp_file[3].

It should be noted that this release removes SecretCharFields and therefore
until Role-Based Access Control is added to Pulp, REST API is not safe for
multi-user use. Sensitive credentials can be read by any user, e.g.
Remote.password, Remote.client_key.

Here are some of the other highlights:

* Implemented incremental-exporting for PulpExport. #6136
* Added support for S3 and other non-filesystem storage options to pulp
import/export functionality. #6456
* Optimized imports by having repository versions processed using child
tasks. #6484
* Added repository type check during Pulp imports. #6532
* Added version checking to import process. #6558
* Taught PulpExport to export by RepositoryVersions if specified. #6566
* Task groups now have an ‘all_tasks_dispatched’ field which denotes that
no more tasks will spawn as part of this group. #6591
* Taught export how to split export-file into chunk_size bytes. #6736

The only backwards incompatible change is the one mentioned in the notice
above:

* Content of ssl certificates and keys changed to be return their full
value instead of sha256 through REST API. #6691

# Installation and Upgrade

Users should use the 3.4.0 release of pulp_installer (previously known as
ansible-pulp) [5] to install or upgrade their installations. This version
of the installer will check compatibility of all installed plugins with
pulpcore 3.4. The installer will abort if any plugin is incompatible.

# Plugin API

Plugin writers can see the plugin API changes here[4]. Some highlights:

* Added new NoArtifactContentUploadSerializer and
NoArtifactContentUploadViewSet to enable plugin writers to upload content
without storing an Artifact #6281
* Added view_name_pattern to DetailRelatedField and DetailIdentityField to
properly identify wrong resource types. #6521
* Added support for Distributions to provide non-Artifact content via a
content_handler. #6570
* Added constants to the plugin API at pulpcore.plugin.constants. #6579
* TaskGroups now have an ‘all_tasks_dispatched’ field that can be used to
notify systems that no further tasks will be dispatched for a TaskGroup.
Plugin writers should call “.finish()” on all TaskGroups created once they
are done using them to set this field. #6591

And in keeping with the recommended strategy to pin plugins to a 3.y
version of pulpcore, plugins should release compatibility releases with 3.4
as soon as they can. We recommend using "pulpcore>=3.4,<3.5".

[0] https://pypi.org/project/pulpcore/3.4.0/
[1] https://pypi.org/project/pulp-file/1.0.0/
[2] https://docs.pulpproject.org/en/3.4/changes.html#id1
[3] https://pulp-file.readthedocs.io/en/latest/changes.html#id1
[4] https://docs.pulpproject.org/en/3.4/changes.html#plugin-api
[5] https://github.com/pulp/pulp_installer/releases/tag/3.4.0
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] CLI Authentication question

[Matthias Dellweg]

You have only pulp_rpm installed (see the versions part of status).
ISO/file support has moved into the pulp_file plugin.

On Thu, May 28, 2020 at 2:45 PM Heide, Todd  wrote:
>
> Yes, you are correct, some other items are missing now that it can 
> authenticate, base.sh works now, but other scripts are still not functioning 
> correctly.  PUT and POST are not allowed.
>
> HTTP 200 OK
> Allow: GET, HEAD, OPTIONS
> Content-Type: application/json
> Vary: Accept
>
> {
> "versions": [
> {
> "component": "pulpcore",
> "version": "3.3.1"
> },
> {
> "component": "pulp_rpm",
> "version": "3.3.2"
> }
> ],
> "online_workers": [
> {
> "pulp_href": 
> "/pulp/api/v3/workers/b46d78d1-7f2a-494c-9055-2e0c29d1e05b/",
> "pulp_created": "2020-05-21T17:50:01.035050Z",
> "name": "1...@aecdas-pulp3test.example.com",
> "last_heartbeat": "2020-05-28T12:42:18.330629Z"
> },
> {
> "pulp_href": 
> "/pulp/api/v3/workers/97e5731f-1405-4e53-8824-39fed702c2d9/",
> "pulp_created": "2020-05-21T17:50:02.840377Z",
> "name": "1...@aecdas-pulp3test.example.com",
> "last_heartbeat": "2020-05-28T12:42:20.535613Z"
> },
> {
> "pulp_href": 
> "/pulp/api/v3/workers/fef5826d-62df-4a79-8145-2e4b3495f495/",
> "pulp_created": "2020-05-21T17:49:41.225878Z",
> "name": "resource-manager",
> "last_heartbeat": "2020-05-28T12:42:21.137314Z"
> }
> ],
> "online_content_apps": [
> {
> "name": "2...@aecdas-pulp3test.example.com",
> "last_heartbeat": "2020-05-28T12:42:23.731799Z"
> },
> {
> "name": "2...@aecdas-pulp3test.example.com ",
> "last_heartbeat": "2020-05-28T12:42:30.153881Z"
> }
> ],
> "database_connection": {
> "connected": true
> },
> "redis_connection": {
> "connected": true
> },
> "storage": {
> "total": 536859357184,
> "used": 2708668416,
> "free": 534150688768
> }
> }
>
> -Original Message-
> From: Matthias Dellweg 
> Sent: Thursday, May 28, 2020 4:47 AM
> To: Daniel Alley 
> Cc: Heide, Todd ; Pulp-list@redhat.com
> Subject: Re: [Pulp-list] CLI Authentication question
>
> [EXTERNAL] This message originated outside of the organization. Use caution 
> when opening files or following links in this email!
>
> It returns 404, which does not sound like missing credentials. Are you sure, 
> the pulp_file plugin is installed? Can you access and may be post here 
> http://localhost:24817/pulp/api/v3/status/ ?
>
> On Thu, May 28, 2020 at 4:32 AM Daniel Alley  wrote:
> >
> > Hello Todd,
> >
> > I believe the file you're looking for is ~/.netrc  --
> > https://ec.haxx.se/usingcurl/usingcurl-netrc
> >
> > I hope that helps!
> >
> >
> > On Wed, May 27, 2020 at 11:21 AM Heide, Todd  
> > wrote:
> >>
> >> This is my third attempt at a working Pulp 3 server. I finally got
> >> the REST Framework working, but, for the life of me, cannot remember
> >> the hidden file that is used under the CLI user to authenticate
> >> against the system.  I lost my links recently to docs, and cannot
> >> remember what the file was called, and I didn't think to back it up
> >> when I tore the server down.  Good news is, the UI appears to be
> >> working, and I can log in as admin, but I am not seeing where I can
> >> post, put, etc.  Trying to set up a repo via CLI I get
> >>
> >> http POST http://localhost:24817/pulp/api/v3/repositories/file/file/
> >> name=foo
> >> HTTP/1.1 404 Not Found
> >> Connection: close
> >> Content-Length: 77
> >> Content-Type: text/html
> >> Date: Wed, 27 May 2020 14:43:01 GMT
> >> Server: gunicorn/20.0.4
> >> X-Frame-Options: SAMEORIGIN
> >>
> >> Not FoundThe requested resource was not found on this
> >> server.
> >>
> >> I'm thinking that the file I am referring to is the key, but I can't find 
> >> what I am looking for.
> >>
> >>
> >> ___
> >> Pulp-list mailing list
> >> Pulp-list@redhat.com
> >> https://www.redhat.com/mailman/listinfo/pulp-list
> >>
> > ___
> > Pulp-list mailing list
> > Pulp-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/pulp-list
>

___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] CLI Authentication question

[Heide, Todd]

Yes, you are correct, some other items are missing now that it can 
authenticate, base.sh works now, but other scripts are still not functioning 
correctly.  PUT and POST are not allowed. 

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
"versions": [
{
"component": "pulpcore",
"version": "3.3.1"
},
{
"component": "pulp_rpm",
"version": "3.3.2"
}
],
"online_workers": [
{
"pulp_href": 
"/pulp/api/v3/workers/b46d78d1-7f2a-494c-9055-2e0c29d1e05b/",
"pulp_created": "2020-05-21T17:50:01.035050Z",
"name": "1...@aecdas-pulp3test.example.com",
"last_heartbeat": "2020-05-28T12:42:18.330629Z"
},
{
"pulp_href": 
"/pulp/api/v3/workers/97e5731f-1405-4e53-8824-39fed702c2d9/",
"pulp_created": "2020-05-21T17:50:02.840377Z",
"name": "1...@aecdas-pulp3test.example.com",
"last_heartbeat": "2020-05-28T12:42:20.535613Z"
},
{
"pulp_href": 
"/pulp/api/v3/workers/fef5826d-62df-4a79-8145-2e4b3495f495/",
"pulp_created": "2020-05-21T17:49:41.225878Z",
"name": "resource-manager",
"last_heartbeat": "2020-05-28T12:42:21.137314Z"
}
],
"online_content_apps": [
{
"name": "2...@aecdas-pulp3test.example.com",
"last_heartbeat": "2020-05-28T12:42:23.731799Z"
},
{
"name": "2...@aecdas-pulp3test.example.com ",
"last_heartbeat": "2020-05-28T12:42:30.153881Z"
}
],
"database_connection": {
"connected": true
},
"redis_connection": {
"connected": true
},
"storage": {
"total": 536859357184,
"used": 2708668416,
"free": 534150688768
}
}

-Original Message-
From: Matthias Dellweg  
Sent: Thursday, May 28, 2020 4:47 AM
To: Daniel Alley 
Cc: Heide, Todd ; Pulp-list@redhat.com
Subject: Re: [Pulp-list] CLI Authentication question

[EXTERNAL] This message originated outside of the organization. Use caution 
when opening files or following links in this email!

It returns 404, which does not sound like missing credentials. Are you sure, 
the pulp_file plugin is installed? Can you access and may be post here 
http://localhost:24817/pulp/api/v3/status/ ?

On Thu, May 28, 2020 at 4:32 AM Daniel Alley  wrote:
>
> Hello Todd,
>
> I believe the file you're looking for is ~/.netrc  -- 
> https://ec.haxx.se/usingcurl/usingcurl-netrc
>
> I hope that helps!
>
>
> On Wed, May 27, 2020 at 11:21 AM Heide, Todd  
> wrote:
>>
>> This is my third attempt at a working Pulp 3 server. I finally got 
>> the REST Framework working, but, for the life of me, cannot remember 
>> the hidden file that is used under the CLI user to authenticate 
>> against the system.  I lost my links recently to docs, and cannot 
>> remember what the file was called, and I didn't think to back it up 
>> when I tore the server down.  Good news is, the UI appears to be 
>> working, and I can log in as admin, but I am not seeing where I can 
>> post, put, etc.  Trying to set up a repo via CLI I get
>>
>> http POST http://localhost:24817/pulp/api/v3/repositories/file/file/ 
>> name=foo
>> HTTP/1.1 404 Not Found
>> Connection: close
>> Content-Length: 77
>> Content-Type: text/html
>> Date: Wed, 27 May 2020 14:43:01 GMT
>> Server: gunicorn/20.0.4
>> X-Frame-Options: SAMEORIGIN
>>
>> Not FoundThe requested resource was not found on this 
>> server.
>>
>> I'm thinking that the file I am referring to is the key, but I can't find 
>> what I am looking for.
>>
>>
>> ___
>> Pulp-list mailing list
>> Pulp-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-list
>>
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list


___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] CLI Authentication question

[Matthias Dellweg]

It returns 404, which does not sound like missing credentials. Are you
sure, the pulp_file plugin is installed? Can you access and may be
post here http://localhost:24817/pulp/api/v3/status/ ?

On Thu, May 28, 2020 at 4:32 AM Daniel Alley  wrote:
>
> Hello Todd,
>
> I believe the file you're looking for is ~/.netrc  -- 
> https://ec.haxx.se/usingcurl/usingcurl-netrc
>
> I hope that helps!
>
>
> On Wed, May 27, 2020 at 11:21 AM Heide, Todd  
> wrote:
>>
>> This is my third attempt at a working Pulp 3 server. I finally got the REST 
>> Framework working, but, for the life of me, cannot remember the hidden file 
>> that is used under the CLI user to authenticate against the system.  I lost 
>> my links recently to docs, and cannot remember what the file was called, and 
>> I didn't think to back it up when I tore the server down.  Good news is, the 
>> UI appears to be working, and I can log in as admin, but I am not seeing 
>> where I can post, put, etc.  Trying to set up a repo via CLI I get
>>
>> http POST http://localhost:24817/pulp/api/v3/repositories/file/file/ name=foo
>> HTTP/1.1 404 Not Found
>> Connection: close
>> Content-Length: 77
>> Content-Type: text/html
>> Date: Wed, 27 May 2020 14:43:01 GMT
>> Server: gunicorn/20.0.4
>> X-Frame-Options: SAMEORIGIN
>>
>> Not FoundThe requested resource was not found on this server.
>>
>> I'm thinking that the file I am referring to is the key, but I can't find 
>> what I am looking for.
>>
>>
>> ___
>> Pulp-list mailing list
>> Pulp-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-list
>>
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list


___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list