Re: [Pulp-list] Pulp 2.10.1 ROLLED BACK

2016-11-02 Thread Sean Myers
On 11/01/2016 04:08 PM, Sean Myers wrote:
> On 11/01/2016 11:06 AM, Sean Myers wrote:
>> We're executing a plan for 2.10.2 that will fix the upgrade process.
>> As usual, I'll update here as we make progress.
> 
> I'm building a 2.10.2 beta hotfix release now.

This took longer than I'd hoped but is now available for testing.

If I haven't mentioned it before here, the problem with 2.10.1 was that
some 2.11 commits had snuck in to 2.10, including a failing migration.
That migration still exists in 2.11.0 Beta 1, so upgrading to that version
is likely to fail the same way. We've since fixed that migration (tracked
in https://pulp.plan.io/issues/2377), and I'm now testing 2.11.0 Beta 2.
I expect to have that release out later tonight or early tomorrow unless
something else pops up in testing that needs to be dealt with.

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


[Pulp-list] Child node sync status check?

2016-11-02 Thread Mcnabb, Dustin
Is it possible to do a node sync status check? Doesn't seem to be an option. 
Nor does cancelling a node sync. Am I just missing it in the documentation and 
the online help of the pulp-admin command? I see you can check the status of 
tasks, but that seems to be separate from node syncs. I kicked off a node sync 
before realizing that most of my repos are set to mirror rather than additive 
since they were created before the default was changed. I want to modify the 
sync type to be additive  for all repos, but I need to know whether the sync is 
done, and if not whether I can cancel it?

Thanks

Dustin McNabb

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

[Pulp-list] Pulp 2.10.2 Hotfix Beta 1 now available!

2016-11-02 Thread Sean Myers
Pulp 2.10.2 Hotfix Beta 1 is now available in the beta repositories:

  https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.10/

This is a critical hotfix addressing an issue that resulted in 2.10.1 being
rolled back. This release also includes all of the bug fixes to Pulp Platform,
the RPM Plugin, and the OSTree plugin originally released with 2.10.1.


Upgrading
=

The 2.10 beta repositories are included in the pulp repo files:
https://repos.fedorapeople.org/repos/pulp/pulp/fedora-pulp.repo for fedora 23 & 
24
https://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo for RHEL 6 & 7

After enabling the pulp-2.10-beta repository, you'll want to follow the standard
upgrade path with migrations:

> $ sudo systemctl stop httpd pulp_workers pulp_resource_manager pulp_celerybeat
> $ sudo yum upgrade
> $ sudo -u apache pulp-manage-db
> $ sudo systemctl start httpd pulp_workers pulp_resource_manager 
> pulp_celerybeat


Hotfix Issue


This hotfix release addresses errors caused by a merge issue introduced prior to
the release of 2.10.1, tracked in Redmine here:

https://pulp.plan.io/issues/2378


Issues Addressed


In addition to the 2.10.2 hotfix, these issues were fixed in Pulp 2.10.1:

  OSTree Support
2237Published repositories are copied instead of linked
2213Proxy URL for remotes not properly constructed.

  Pulp
   2344 Streamer PulpHTTPAdapter does not configure the proxy pool 
manger with certificates resulting in 503s.
2328Repository syncs show all units updated even when there are no 
changes
2287Cannot get docker v2 repo tags list
2278Remove checksum_type from the srpm and drpm collections
2277Content published using move (instead of copy) causes 404 due 
to selinux denial.
2221rsync distributor doesn't remove files from remote when 
rsyncing empty repository with --delete
2049Django RemovedInDjango110Warning in logs for missing TEMPLATES 
setting
1766Pulp API is incompatible with Django 1.10
1392Misleading nodes quickstart howto

  RPM Support
2326Publishes fail
2257unit test failure: "AppRegistryNotReady: Apps aren't loaded 
yet."
2242Package signature ID checking is broken when syncing in packages
2227Only first pkglist is synced for erratum even if multiple are 
present
2190Unit is associated with the repo before it is copied to the 
final location

View this list in Redmine:
http://bit.ly/2eqCCZe


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


Re: [Pulp-list] Omitting RPMs in backups

2016-11-02 Thread Nicolas FOURNIALS
Hi,

>> > Questions aside, this is theoretically doable. You'll need to be setup for
>> > pulp's deferred content download feature, which includes deploying squid or
>> > an equivalent proxy.
>> > 
>> > http://docs.pulpproject.org/user-guide/deferred-download.html
>> > 
>> > You would first restore your database, and then create a repo in pulp for
>> > each of these backup repos. For each one:
>> > 
>> > - set the download policy to "on_demand"
>> > - sync. This should discover that each content unit is already in the
>> > database, associate it to the repo, and populate the on_demand catalog with
>> > knowledge of its location in this giant feed
>> > - run the download_repo task with the "verify_all_units" option set to
>> > True. This will go through each file of each unit, discover it's missing,
>> > and then download it from the link that was cataloged above.
>> > ---
>> > http://docs.pulpproject.org/dev-guide/integration/rest-api/repo/sync.html#download-a-repository
>> > - delete your "backup" repos from pulp
>> > 
>> > This is only possible for yum repos currently, until support for deferred
>> > download is added to other plugins.
>> > 
>> > If you do go through with this as a plan, let us know how testing goes, and
>> > what tips you would have for the next person who tries it.
> Great, that was the kind of idea I was looking for, thanks a lot!
> I guess it will need using for the temporary repo a different feed
> URL from that of the saved repo.
> OK, I will try it and give some feedback.

I was about to answer that I was unsuccessful but in the end I tried
with the default immediate download policy and it worked!
So, the method is simply:
* recreate another repo with the same feed (change the relative_url),
using default download_policy
* sync
* delete the new repo
That's it, RPMs have been restored in /var/lib/pulp/content/units/rpm/

Thanks a lot,

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