Issue #1928
closed
Publish should be operational if override config values were specified
Description
Let's say that you create a Pulp repository with a feed and sync it. You should then be able to make the repository content available in at least the following ways:
- Publish the repository contents to a directory.
- Publish the repository contents so they're accessible via HTTP.
If you take the following series of steps, you'll succeed:
1. Create a distributor.
2. Publish the repository to one kind of location (e.g. a directory) with that distributor.
3. Create a second distributor.
4. Publish the repository to the other kind of location (e.g. via HTTP) with the second distributor.
If you take the following series of steps, you'll fail:
1. Create a distributor.
2. Publish the repository to one kind of location (e.g. a directory) with that distributor.
3. Publish the repository to the other kind of location (e.g. via HTTP) with the same distributor.
Pulp doesn't complain at all when the second publish occurs, and no errors appear in the logs. Instead, the second publication just doesn't happen. This doesn't make sense. One of the following should occur:
- Pulp should return an HTTP 3XX response when the second publication request is received.
- Pulp should successfully complete the second publish.
This bug has been reproduced on Pulp 2.8.3 and master (2.9.0). This bug has been reproduced with RPM repositories, and it's unclear whether this same issue applies to other content types.
Issue consists in the fact that second publish does not occur as it is considered as no-op.
No-op logic should be changed and added the case when in override_config something was specified.
.
Publish should be operational if override config values were specified
closes #1928 https://pulp.plan.io/issues/1928