Re: [Pulp-list] RHEL6 packages missing?

[Sean Myers]

On 03/29/2017 07:07 AM, Roth, Sandro wrote:
> Hi all
> 
> Trying to install the pulp-agent on RHEL6 machines and there seem to be some 
> packages missing from the yum repository at
> 
> https://repos.fedorapeople.org/repos/pulp/pulp/stable/2/6Server/x86_64/
> 
> Specifically I'm missing the following
> 
> pulp-rpm-yumplugins
> pulp-rpm-consumer-extensions
> pulp-rpm-handlers
> 
> Which are to be installed according to the docs
> 
> http://docs.pulpproject.org/user-guide/installation/f23-.html#consumer-client-and-agent

This is related to the dropping of support for el6 in 2.12.
It looks like the build system should be including these packages
but isn't; I'll take a look, see what's missing, and put together
a task to fix current and future releases.




signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.12.2 Beta 1 now available for testing

[Sean Myers]

Pulp 2.12.2 Beta 1 is now Available in the beta repositories:

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

This release includes a small number bug fixes for the Pulp Platform,
the RPM Plugin, and the OSTree plugin.

The current status of this release can be tracked in the Redmine Wiki:
https://pulp.plan.io/projects/pulp/wiki/2122_Release_Status


Upgrading
=

The Pulp 2.12 beta repository is included in the pulp repo files:
https://repos.fedorapeople.org/repos/pulp/pulp/fedora-pulp.repo for fedora
24 & 25
https://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo for RHEL 7

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

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

The pulp_streamer and goferd services should be omitted if those services
are not installed.


Issues Addressed


  Pulp

723 RPMs with large number of files can exceed mongo document size 
limit
2527Ensure Pulp 2.y works with both python-celery 3.1.z and 4.0.z
2551Pulp task error messages should be more informative
2584Mongo cursor times out during task 
pulp.server.managers.content.orphan.delete_all_orphans
2585Bugs fixed in version link is not correct for plugins
2524Vagrant systemd and upstart scripts are not symlinked to source

  RPM Support

2559Empty pkglist for the erratum may be generated which may cause 
yum not to find applicable packages
2620All RPM repo searches are broken
2622Sync fails when non-ASCII characters are present in primary.xml
2623Errata publish performace degradation
2274Uploading duplicate content results in ambiguous error message
2560Non-unique collection names in erratum pkglists causes yum not 
to show all packages
1414pulp rpm profiler INFO-level logging is very verbose
1903RPM import traceback (non-utf-8 metadata slipping through)
2505Getting an incorrect exception when trying to sync a local repo 
with bad permissions
2599Deprecation warning in the logs during errata migration

  OSTree Support

2544copy always matches every unit in the repo
2552updating ostree rpm gives error on sync: LibError: 
GLib.Error('No such file or directory', 'g-io-error-quark', 1)

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


el6 Support Reminder


As mentioned in the release notes, Pulp no longer supports el6 starting
with 2.12.0.

Pulp users running on RHEL or CentOS 6 are recommended to upgrade their
Pulp server to the current major version of that OS, RHEL or CentOS 7.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp 2.12.0 Now Generally Available!

[Sean Myers]

On 02/01/2017 03:52 PM, Sean Myers wrote:
> End of EL6 Support
> ==
> 
> As mentioned in the release notes, Pulp no longer supports el6 starting with 
> 2.12.
> 
> Pulp users running on RHEL or CentOS 6 are recommended to upgrade their Pulp 
> server to
> the current major version of that OS, RHEL or CentOS 7.

I erroneously built and released unsupported packages for el6. I've pushed out 
a new
2.12.0 build (2.12.0-2) only the supported bits for el6, which include the Pulp 
Agent
and Pulp Consumer Client. No other distributions will be changed.

Actually implementing our support policy in our build system has proven 
difficult,
but in the time since this release I believe we've found and corrected the 
issues
that led to this.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.12.0 Now Generally Available!

[Sean Myers]

Pulp 2.12.0 is now Generally Available, and can be downloaded from
the 2.12 stable repositories:

https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.12/

New features for Pulp 2.12 include new features added to the Pulp platform, as 
well
as the Puppet, RPM, and Docker plugins. Many bug fixes are also included in
the 2.12.0 release.

More information about these new features can be found in the features list 
below,
as well as in the 2.12 release notes:

http://docs.pulpproject.org/en/2.12/user-guide/release-notes/2.12.x.html

Try out the new features, and let us know how they work for you!

Since the release of Release Candidate 2, we've decided to pull the pulp_python
upgrade to version 2.0 from this release, due to usability and documentation
issues that we feel still need to be worked out before that pluginis ready for
release. We'll be including it in a future release. Users currently testing a
pre-release of 2.12.0 (a Beta or Release Candidate) may need to downgrade the
installed versions of the pulp-python packages to 1.1.3-1 as a result.

These are the current stable packages for the pulp_python plugin as of Pulp
2.12.0:

- pulp-python-admin-extensions-1.1.3-1
- pulp-python-plugins-1.1.3-1
- python-pulp-python-common-1.1.3-1

Upgrading
=

The Pulp 2 stable repositories are included in the pulp repo files:

https://repos.fedorapeople.org/repos/pulp/pulp/fedora-pulp.repo for fedora 24 & 
25
https://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo for RHEL 7

After enabling the pulp-stable or pulp-2-stable repository, you'll want to 
follow the standard
upgrade path with migrations:

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

The pulp_streamer and goferd services should be omitted if those services are 
not installed.


New Features


Here are the specific stories done for 2.12:

  Pulp
2525Failover events should be explicitly logged as such when they 
occur
2509Pulp process failure detection and any failover should occur 
within 30 seconds
2186As a user, pulp-manage-db refuses to run if other pulp 
processes are running locally
1939As a user, I would like to be able to profile Pulp tasks
1268As a user, orphan content delete reports how many units were 
deleted
  RPM Support
1976As user, I can have packages sorted in "Packages/$x" 
directories when published
  Docker Support
2189As a user, I can update docker_tag units without using sync


View this list in redmine:
http://bit.ly/2iMdYpK


Issues Addressed


Here are the bug fixes specific to 2.12:

  Pulp
2545pulp-manage-db wait time calculation can end up with many hours 
of wait time
2264better error reporting during import/association
1488Deprecate nodes
1321Commit message requirements for Pulp contributions are out of 
date and could be better
103 Document the commit message keywords that will interact with 
Redmine
  RPM Support
1823RPMs partially downloaded

All bug fixes from Pulp 2.11.1 and earlier are also included in Pulp 2.12.

View this list in redmine:
http://bit.ly/2iMgzjJ


End of EL6 Support
==

As mentioned in the release notes, Pulp no longer supports el6 starting with 
2.12.

Pulp users running on RHEL or CentOS 6 are recommended to upgrade their Pulp 
server to
the current major version of that OS, RHEL or CentOS 7.




signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.11.2 Now Generally Available!

[Sean Myers]

Pulp 2.11.2 is now Generally Available in the stable repositories:

  https://repos.fedorapeople.org/repos/pulp/pulp/stables/2.11

This release includes a small number bug fixes for the Pulp Platform, and the 
RPM Plugin,
and is the final release for the Pulp 2.11 line since the 2.12.0 release is 
currently in
progress.

2.12.0 is expected to be generally available very soon (likely tomorrow); this 
release is
only useful to users explicitly choosing to stay on pulp 2.11 for some time 
after the release
of 2.12.


Upgrading
=

Due to the imminent release of 2.12.0, the Pulp 2.11 stable repository *will 
not* be included
in the normal pulp repo files. They will point to Pulp 2.12 upon the release of 
that version.
The appropriate repository for your distribution will need to be manually 
installed in order
to stay on Pulp 2.11.

After adding the appropriate Pulp 2.11 stable repository, you'll want to follow 
the standard
upgrade path with migrations:

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

The pulp_streamer and goferd services should be omitted if those services are 
not installed.


Issues Addressed


  Pulp

1847last_unit_added is not added in mongo repo collection records
2520credentials in feed URL are not url-unquoted

  RPM Support

1086pulp_distribution.xml sync should ignore repodata/*

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


el6 Support Reminder


As mentioned in the 2.11.0 release notes, we are no longer supported el6 
distributions
after Pulp 2.11. See the release notes for more information:

http://docs.pulpproject.org/en/2.11/user-guide/release-notes/2.11.x.html#el6-support-changes



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.12.0 Release Candidate 2 Now Available!

[Sean Myers]

On 01/24/17 16:02, Sean Myers wrote:
> Pulp 2.12.0 Release Canidate 1 is now available, and can be downloaded from
> the 2.12 beta repositories:
> 
> https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.12/

Pulp 2.12.0 Release Candidate 2 is now available. No plugins have changed since 
RC 1,
the bugfix (linked below) required a change to only the Pulp platform.

Details:

While testing out 2.12.0, my good man elyezer discovered an annoying timezone 
issue
that would most likely cause pulp-manage-db to wait a very long time before 
starting.

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

After identifying the issue, he also filed the pull request that fixed it, which
I've just built and published as RC 2.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.11.2 Beta 1 Now Available!

[Sean Myers]

Pulp 2.11.2 Beta 1 is now Available in the beta repositories:

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

This release includes a small number bug fixes for the Pulp Platform, and the 
RPM Plugin,
and is most likely the final release for the Pulp 2.11 line since the 2.12.0 
release is
currently underway.

The current status of this release can be tracked in the Redmine Wiki:
https://pulp.plan.io/projects/pulp/wiki/2120_Release_Status


Upgrading
=

The Pulp 2.11 beta repository is 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.11-beta repository, you'll want to follow the standard
upgrade path with migrations:

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

The pulp_streamer and goferd services should be omitted if those services are 
not installed.


Issues Addressed


  Pulp

1847last_unit_added is not added in mongo repo collection records
2520credentials in feed URL are not url-unquoted

  RPM Support

1086pulp_distribution.xml sync should ignore repodata/*

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


el6 Support Reminder


As mentioned in the 2.11.0 release notes, we are no longer supported el6 
distributions
after Pulp 2.11. See the release notes for more information:

http://docs.pulpproject.org/en/2.11/user-guide/release-notes/2.11.x.html#el6-support-changes



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.12.0 Beta 1 Now Available!

[Sean Myers]

Pulp 2.12.0 Beta 1 is now available, and can be downloaded from
the 2.12 beta repositories:

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

New features for Pulp 2.12 include new features added to the Pulp platform, as 
well
as the Puppet, RPM, Python, and Docker plugins. Many bug fixes are also 
included in
the 2.12.0 release.

More information about these new features can be found in the features list 
below,
as well as in the 2.12 release notes:
http://docs.pulpproject.org/en/2.12/testing/user-guide/release-notes/2.12.x.html

Try out the new features, and let us know how they work for you!


Upgrading
=

The Pulp 2.12 beta repository is 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.11-beta repository, you'll want to follow the standard
upgrade path with migrations:

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

The pulp_streamer and goferd services should be omitted if those services are 
not installed.


New Features


Here are the specific stories done for 2.12:

  Pulp
2525Failover events should be explicitly logged as such when they 
occur
2509Pulp process failure detection and any failover should occur 
within 30 seconds
2186As a user, pulp-manage-db refuses to run if other pulp 
processes are running locally
1939As a user, I would like to be able to profile Pulp tasks
1268As a user, orphan content delete reports how many units were 
deleted
  Python Support
1882Rebuild model to support all package types
140 As a user, I can sync Python packages from another Pulp server
136 As a user, I can upload wheel packages to Pulp
135 As a user, I can synchronize wheels from PyPI
  RPM Support
1976As user, I can have packages sorted in "Packages/$x" 
directories when published
  Docker Support
2189As a user, I can update docker_tag units without using sync


View this list in redmine:
http://bit.ly/2iMdYpK


Issues Addressed


Here are the bug fixes specific to 2.12:

  Pulp
2264better error reporting during import/association
1488Deprecate nodes
1321Commit message requirements for Pulp contributions are out of 
date and could be better
103 Document the commit message keywords that will interact with 
Redmine
  RPM Support
1823RPMs partially downloaded

All bug fixes from Pulp 2.11.1 and earlier are also included in Pulp 2.12.

View this list in redmine:
http://bit.ly/2iMgzjJ


End of EL6 Support
==

As mentioned in earlier release notes, Pulp no longer supports el6 starting 
with 2.12.

Pulp users running on RHEL or CentOS 6 are recommended to upgrade their Pulp 
server to
the current major version of that OS.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.11.1 Now Generally Available!

[Sean Myers]

Pulp 2.11.1 is now Generally Available in the stable repositories:

  https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.11/

This release includes bug fixes for the Pulp Platform, the Puppet plugin, and 
the RPM Plugin.

No blocking issues were reported during the 2.11.1 beta, so this release is 
unchanged from the
2.11.1 Beta 1 release.


Upgrading
=

The Pulp 2 stable repository is 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-stable repository, you'll want to follow the standard
upgrade path with migrations:

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

The pulp_streamer and goferd services should be omitted if those services are 
not installed.


Issues Addressed


  Pulp
2439No data available in publish step (OSError: [Errno 61] No data 
available)
2483pulp_rpm migration 0031 fails: cursor not found
2491When stopping pulp_workers, pulp_celerybeat, and 
pulp_resource_manager gracefully, the status API still shows them as running
2464pulp-admin broken in vagrant environment on 2.y
1287Repo sync failing with KeyError
2006iso importer fails without useful error message
2136publish step error handling incorrectly assumes open file
2476pulp publish fail when selinux is disabled
2510django logs warning when responding with 404

  Puppet Support
2500ValueError exception is raised when uploading module with 
invalid name
1981unnecessary pulp error on puppet repo sync
1853pulp-puppet-module-builder should not overwrite existing module 
files

  RPM Support
2514Creating a group no longer updates the existing group
2365rpm upload fails to populate "files" field on model
2457When syncing do not associate units that are already associated 
to the repo
2096Additional updateinfo.xml after second publish
2466Remove unnecessary `deepcopy` calls for sync 

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


el6 Support Reminder


As mentioned in the 2.11.0 release notes, we are no longer supported el6 
distributions
after Pulp 2.11. See the release notes for more information:

http://docs.pulpproject.org/en/2.11/user-guide/release-notes/2.11.x.html#el6-support-changes



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.11.1 Beta 1 Now Available!

[Sean Myers]

Pulp 2.11.1 Beta 1 is now Available in the beta repositories:

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

This release includes bug fixes for the Pulp Platform, the Puppet plugin, and 
the RPM Plugin.


Upgrading
=

The Pulp 2.11 beta repository is 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.11-beta repository, you'll want to follow the standard
upgrade path with migrations:

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

The pulp_streamer and goferd services should be omitted if those services are 
not installed.


Issues Addressed


  Pulp
2439No data available in publish step (OSError: [Errno 61] No data 
available)
2483pulp_rpm migration 0031 fails: cursor not found
2491When stopping pulp_workers, pulp_celerybeat, and 
pulp_resource_manager gracefully, the status API still shows them as running
2464pulp-admin broken in vagrant environment on 2.y
1287Repo sync failing with KeyError
2006iso importer fails without useful error message
2136publish step error handling incorrectly assumes open file
2476pulp publish fail when selinux is disabled
2510django logs warning when responding with 404

  Puppet Support
2500ValueError exception is raised when uploading module with 
invalid name
1981unnecessary pulp error on puppet repo sync
1853pulp-puppet-module-builder should not overwrite existing module 
files

  RPM Support
2514Creating a group no longer updates the existing group
2365rpm upload fails to populate "files" field on model
2457When syncing do not associate units that are already associated 
to the repo
2096Additional updateinfo.xml after second publish
2466Remove unnecessary `deepcopy` calls for sync 

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


el6 Support Reminder


As mentioned in the 2.11.0 release notes, we are no longer supported el6 
distributions
after Pulp 2.11. See the release notes for more information:

http://docs.pulpproject.org/en/2.11/user-guide/release-notes/2.11.x.html#el6-support-changes



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Managing repos/schedules/etc with Puppet

[Sean Myers]

On 12/08/2016 02:31 PM, Kodiak Firesmith wrote:
> Just speaking for myself here, but when Red Hat converged on Puppet
> (~2011?), we went all-in on that so we're a Puppet shop.  We didn't expect
> Red Hat to go flipmode on us and buy Ansible 3 years later.  So I'm only
> interested in Puppet right now :)

https://docs.ansible.com/ansible/puppet_module.html :D

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

[Pulp-list] Pulp 2.11.0 Beta 3 Approved as Release Candidate

[Sean Myers]

On 11/23/2016 04:36 PM, Sean Myers wrote:
> Pulp 2.11.0 Beta 3 is now available, and can be downloaded from
> the 2.11 beta repositories:
> 
> https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.11/

This beta release has been accepted as a Release Candidate by our testing team,
and upgrade testing from earlier releases of Pulp has begun.

Given a minimum of one week in the Release Candidate stage to allow for upgrade
testing, the earliest possible date for 2.11.0 to become generally available is
Monday, December 12.

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

[Pulp-list] Pulp 2.10.3 Generally Available!

[Sean Myers]

Pulp 2.10.3 is now Generally Available in the stable repositories:

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

This release includes bug fixes for the Pulp Platform, and the RPM Plugin.


Upgrading
=

The Pulp 2 stable repository is 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-stable 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


Issues Addressed


  Pulp
2436pulp-selinux RPM fails to run restorecon statements post install
2195can't sync unit that was previously uploaded
2424restorecon runs unecessarily for all 2.10+ upgrades
  RPM Support
2354Incorrect URL on lazy catalog entries created for existing RPM 
content units
2372updating importer ssl_client_cert to null fails with error
2362applicability calculation wastes time scanning a list
2374Can't skip distribution content during sync

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


el6 Known Issue Update
==

In the beta announcement, I mentioned that the el6 test suite was indicating 
that
this release might be unstable for that platform.

The el6 release has since been verified as working and cleared for release, as 
reported here:
https://pulp.plan.io/projects/pulp/wiki/Pulp_2_10_3_Test_Result_Summary

Thanks to everyone involved in this investigation.

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

Re: [Pulp-list] Pulp 2.10.3 Beta 1 now available!

[Sean Myers]

On 11/21/2016 04:53 PM, Sean Myers wrote:
> Potential Known Issue
> =
> 
> Our el6 test suite was indicating that this release might be unstable for 
> that platform.
> We're investigating this now, and I'll update here once we know more.

dkliban determined that this was indeed broken. We've fixed the problem 
affecting el6
builds, and I've pushed the update up to the beta repositories.

Here's the issue, for reference:
https://pulp.plan.io/issues/2436

This issue will be included in the normal issue list for future release 
announcements
regarding 2.10.3.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.11.0 Beta 3 Now Available

[Sean Myers]

Pulp 2.11.0 Beta 3 is now available, and can be downloaded from
the 2.11 beta repositories:

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

A failing migration was discovered, preventing some users from upgrading from 
previous
versions of Pulp, and was fixed in Beta 2:

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

Additionally, fixes included in the 2.10.2 hotfix release and 2.10.3 have been 
brought
forward to 2.11 Beta 3.

New features for Pulp 2.11 include more improvements to RPM syncing, the 
ability to pull older
trees with OSTree, incremental publish with Docker and RPM, and the ability to 
upload DRPMS.
Several bugs were also fixed; all the details can be found later in this 
announcement.

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.11/testing/user-guide/release-notes/2.11.x.html
http://docs.pulpproject.org/en/2.11/testing/plugins/pulp_rpm/user-guide/release-notes/2.11.x.html
Docker 2.2 and OSTree 1.2 release notes coming soon.

Try out the new features, and let us know how they work for you!


Upgrading
=

The 2.11 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.11-beta repository, you'll want to follow the standard
upgrade path, with migrations, to get to 2.11:

> $ 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


New Features


Here are the specific stories done for 2.11:

  Docker Support
2114As a user, I can perform incremental publish with Docker rsync 
distributor

  OSTree Support
2205As a user, I want to pull older versions of trees available to 
atomic hosts.

  Pulp
1983As a user, an importer config change or content removal will 
cause the next sync to be full
2172Memory Improvements with Process Recycling
2186As a user, pulp-manage-db refuses to run if other pulp 
processes are running locally

  RPM Support
1806As a user, I can use pulp-admin to upload drpms
2113As a user, I can perform an incremental publish using ISO rsync 
distributor
2132As a consumer of Pulp content I want ISO & ISO_rsync 
distributor to support relative_url for consistency with yum
2211As a user, I can sync a distribution unit with the existing 
yum_importer without requiring yum metadata
2212As a user I can see in the task report of copy operation list 
of units which did not pass signature filter 

View this list in redmine:
http://bit.ly/2eQz5Ui


Issues Addressed


Here are the bug fixes specific to 2.11:

  Pulp
23770025_importer_schema_change hits issue with last_sync being None
1977basic auth in URL fails when using authenticated proxy
1069extra Task ID in docs example to bind a repo
2133Permissions docs should include some info on /v2/
752 Suggestion to add -v remains even if you use -v

  RPM Support
2224Cannot sync from mirrorlists
2321Pulp can't handle mirrorlists with invalid entries
2363Pulp acts like all is well when a sync completely fails
2071Creating yum distributor without https, http keys in config 
crashes

All bug fixes from Pulp 2.10.3 and earlier are included in Pulp 2.11.

View this list in redmine:
http://bit.ly/2dHG8ws



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Sometimes 'purge_duplicates' takes an abnormal amount of time

[Sean Myers]

On 11/21/2016 05:52 PM, Eric Helms wrote:
> On Mon, Nov 21, 2016 at 4:03 PM, Sean Myers  wrote:
> 
>> On 11/21/2016 03:29 PM, Eric Helms wrote:
>>> Hi,
>>>
>>> I've noticed that at times, during a sync, the 'purge_duplicates' step
>>> seems to take what I would consider an abnormal amount of time. A sync
>> that
>>> usually takes 5 or so minutes can suddenly take an hour and it seems to
>>> just sit at this particular step. Since Pulp progress reports do not
>>> contain timing data [1] I cannot give hard numbers on this. Is there
>>> anything that might explain this behavior? Is this a valid or known bug?
>> I
>>> am happy to provide as much data and information as I can because.
>>
>> I don't know of issues where this step just pauses.
>>
>> What version(s) of pulp/mongodb is this running on? What distribution(s)?
>>
> 
> 2.8.7 on mongodb 2.6.11
> 
>>
>> Is there a particular feed that reliably causes this?
>>
> 
> I wish. This does not happen all of the time which makes it hard to zero on
> the problem. We experience high IO time at some points, and I have noticed
> that during these times when we do large queries to Pulp and thus mongodb
> we run into all things slowing down. I am working to get some better hard
> evidence by adding cProfiles.

cProfile stuff would be gravy, but I suspect that a pulp developer with a
fresh take on this would be able to take my work from the original effort
to speed up the purging of duplicate nevra and find some obvious things to
optimization. This is a new Redmine issue that should be filed in Pulp's
Redmine.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.10.3 Beta 1 now available!

[Sean Myers]

Pulp 2.10.3 Beta 1 is now available in the beta repositories:

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

This release includes bug fixes for the Pulp Platform, and the RPM Plugin.


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


Issues Addressed


  Pulp
2424restorecon runs unecessarily for all 2.10+ upgrades
2195can't sync unit that was previously uploaded
  RPM Support
2374Can't skip distribution content during sync
2372updating importer ssl_client_cert to null fails with error
2362applicability calculation wastes time scanning a list
2354Incorrect URL on lazy catalog entries created for existing RPM 
content units

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


Potential Known Issue
=

Our el6 test suite was indicating that this release might be unstable for that 
platform.
We're investigating this now, and I'll update here once we know more.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Sometimes 'purge_duplicates' takes an abnormal amount of time

[Sean Myers]

On 11/21/2016 03:29 PM, Eric Helms wrote:
> Hi,
> 
> I've noticed that at times, during a sync, the 'purge_duplicates' step
> seems to take what I would consider an abnormal amount of time. A sync that
> usually takes 5 or so minutes can suddenly take an hour and it seems to
> just sit at this particular step. Since Pulp progress reports do not
> contain timing data [1] I cannot give hard numbers on this. Is there
> anything that might explain this behavior? Is this a valid or known bug? I
> am happy to provide as much data and information as I can because.

I don't know of issues where this step just pauses.

What version(s) of pulp/mongodb is this running on? What distribution(s)?

Is there a particular feed that reliably causes this?



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.10.2 Hotfix now generally available!

[Sean Myers]

Pulp 2.10.2 Hotfix is now generally available in the stable repositories:

  https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.10/
  https://repos.fedorapeople.org/repos/pulp/pulp/stable/2/

This is a critical hotfix addressing a issues 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.

All hotfix issues (listed below) are tested and verified as fixed.


Upgrading
=

The Pulp 2 stable repository is 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-stable 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 Issues
=

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

While that fix was being verified, it was discovered that publishing fails on 
el6,
tracked in Redmine here:

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


Known Issues


- Upgrading on EL 7.3 can take longer than on other platforms. pulp-selinux 
package unnecessarily
  runs restorecon on /var/lib/pulp. The duration of upgrade depends on the 
amount of content in
  that directory.

- As part of fixing the above issue, it was also discovered that upgrading from 
2.10.0 can take
  longer than from 2.9.1 and earlier versions. The fix for this issue will be 
released with 2.10.3.


Issues Addressed


In addition to the 2.10.2 hotfix issues, 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] Pulp 2.10.2 Hotfix Beta 3 now available!

[Sean Myers]

On 11/15/2016 01:43 PM, Sean Myers wrote:
> The fix for hotfix issue #2387 was found to be incomplete, requiring another 
> build.
> 
> That build is now available as 2.10.2 Hotfix Beta 3. My release announcement 
> for
> Hotfix Beta 2 (quoted below) is otherwise unchanged and also applies to 
> Hotfix Beta 3.


As of 2.10.2 Hotfix Beta 3, all hotfix issues have been verified. Upgrade 
testing has
also completed successfully.

This hotfix release should become a Generally Available release tomorrow. (woot)

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

Re: [Pulp-list] Try Pulp 3.0

[Sean Myers]

On 11/16/2016 02:23 PM, Thomas Mueller wrote:
> hi
> 
> After reading http://pulpproject.org/2016/10/31/pulp-3.0-mvp/  I'm eager
> to try this MVP.
> 
>  http://docs.pulpproject.org/en/3.0/nightly/contributing/build_guide.html
> is a bit short of text or maybe i just failed to find the right spot. :-)
> 
> Is it already in a state to play or is too early?

Right now it's too early; we actually just got those docs published yesterday
in hopes of talking about what we plan to do with them in tomorrow's sprint 
demo.

The developer setup[0] is similarly barren, but I'm working on a story for this
sprint to make the developer setup experience much more reliable, which (in my
opinion) includes documentation on how the developer setup should actually work.

I think in a few weeks you'll have something to play with, even if the only
thing Pulp knows how to do at that point is create a repository.

[0]: http://docs.pulpproject.org/en/3.0/nightly/contributing/dev-setup.html

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

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

[Sean Myers]

The fix for hotfix issue #2387 was found to be incomplete, requiring another 
build.

That build is now available as 2.10.2 Hotfix Beta 3. My release announcement for
Hotfix Beta 2 (quoted below) is otherwise unchanged and also applies to Hotfix 
Beta 3.

On 11/14/2016 02:13 PM, Sean Myers wrote:
> Pulp 2.10.2 Hotfix Beta 2 is now available in the beta repositories:
> 
>   https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.10/
> 
> This is a critical hotfix addressing a issues 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.
> 
> Assuming all hotfix issues (listed below) are tested and verified as fixed,
> we'll make this release generally available.
> 
> 
> 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
> 
> While that fix was being verified, it was discovered that publishing fails on 
> el6,
> tracked in Redmine here:
> 
>   https://pulp.plan.io/issues/2387
> 
> Both of these issues should be fixed in 2.10.2 Hotfix Beta 2.
> 
> 
> Issues Addressed
> 
> 
> In addition to the 2.10.2 hotfix issues, 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

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

[Sean Myers]

Pulp 2.10.2 Hotfix Beta 2 is now available in the beta repositories:

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

This is a critical hotfix addressing a issues 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.

Assuming all hotfix issues (listed below) are tested and verified as fixed,
we'll make this release generally available.


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

While that fix was being verified, it was discovered that publishing fails on 
el6,
tracked in Redmine here:

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

Both of these issues should be fixed in 2.10.2 Hotfix Beta 2.


Issues Addressed


In addition to the 2.10.2 hotfix issues, 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

[Pulp-list] Pulp 2.11.0 Beta 2 Now Available

[Sean Myers]

Pulp 2.11.0 Beta 2 is now available, and can be downloaded from
the 2.11 beta repositories:

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

A failing migration was discovered, preventing some users from upgrading from 
previous
versions of Pulp, and has been fixed in Beta 2:

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

New features for Pulp 2.11 include more improvements to RPM syncing, the 
ability to pull older
trees with OSTree, incremental publish with Docker and RPM, and the ability to 
upload DRPMS.
Several bugs were also fixed; all the details can be found later in this 
announcement.

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.11/testing/user-guide/release-notes/2.11.x.html
http://docs.pulpproject.org/en/2.11/testing/plugins/pulp_rpm/user-guide/release-notes/2.11.x.html
Docker 2.2 and OSTree 1.2 release notes coming soon.

Try out the new features, and let us know how they work for you!


Upgrading
=

The 2.11 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.11-beta repository, you'll want to follow the standard
upgrade path, with migrations, to get to 2.11:

> $ 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


New Features


Here are the specific stories done for 2.11:

  Docker Support
2114As a user, I can perform incremental publish with Docker rsync 
distributor

  OSTree Support
2205As a user, I want to pull older versions of trees available to 
atomic hosts.

  Pulp
1983As a user, an importer config change or content removal will 
cause the next sync to be full
2172Memory Improvements with Process Recycling
2186As a user, pulp-manage-db refuses to run if other pulp 
processes are running locally

  RPM Support
1806As a user, I can use pulp-admin to upload drpms
2113As a user, I can perform an incremental publish using ISO rsync 
distributor
2132As a consumer of Pulp content I want ISO & ISO_rsync 
distributor to support relative_url for consistency with yum
2211As a user, I can sync a distribution unit with the existing 
yum_importer without requiring yum metadata
2212As a user I can see in the task report of copy operation list 
of units which did not pass signature filter 

View this list in redmine:
http://bit.ly/2eQz5Ui


Issues Addressed


Here are the bug fixes specific to 2.11:

  Pulp
23770025_importer_schema_change hits issue with last_sync being None
752 Suggestion to add -v remains even if you use -v
1069extra Task ID in docs example to bind a repo
1977basic auth in URL fails when using authenticated proxy
2133Permissions docs should include some info on /v2/

  Python Support
1961Package twine for Fedora and RHEL

  RPM Support
2071Creating yum distributor without https, http keys in config 
crashes
2224Cannot sync from mirrorlists
2321Pulp can't handle mirrorlists with invalid entries
2363Pulp acts like all is well when a sync completely fails

All bug fixes from Pulp 2.10.1 and earlier are included in Pulp 2.11.

View this list in redmine:
http://bit.ly/2dHG8ws


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

Re: [Pulp-list] Pulp 2.10.1 ROLLED BACK

[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] Pulp 2.10.2 Hotfix Beta 1 now available!

[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] Pulp 2.10.1 ROLLED BACK

[Sean Myers]

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.

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

Re: [Pulp-list] Pulp 2.10.1 ROLLED BACK

[Sean Myers]

On 10/31/2016 07:23 PM, Sean Myers wrote:
> A potential workaround has been discovered; we'll update here and in
> Redmine once we've got something to get folks that are currently
> stuck on 2.10.1 *un*stuck.

A workaround exists that is ready for testing:
https://pulp.plan.io/issues/2377#note-4

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.

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

[Pulp-list] Pulp 2.10.1 ROLLED BACK

[Sean Myers]

On 10/31/2016 04:20 PM, Sean Myers wrote:
> Pulp 2.10.1 is now Generally Available in the stable repositories

2.10.1 has been rolled back, 2.10.0 is the available version.

2.10.1 has a migration failure blocking most, if not all, users
attempting to upgrade. I've rolled back the 2.10.1 release so that
users that have not yet attempted to upgrade should not be affected,
and we'll be releasing 2.10.2 shortly with fixed migrations.

The migration failure has been reported here:
https://pulp.plan.io/issues/2377

The 2.10.2 hotfix effort is being tracked in Redmine here:
https://pulp.plan.io/issues/2378

A potential workaround has been discovered; we'll update here and in
Redmine once we've got something to get folks that are currently
stuck on 2.10.1 *un*stuck.

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

[Pulp-list] Pulp 2.10.1 Generally Available!

[Sean Myers]

Pulp 2.10.1 is now Generally Available in the stable repositories:

* pulp-2-stable: https://repos.fedorapeople.org/pulp/pulp/stable/2/
* pulp-stable: https://repos.fedorapeople.org/pulp/pulp/stable/latest/

This release includes bug fixes to Pulp Platform, the RPM Plugin,
and the OSTree plugin.

Pulp 2.10.1 includes a variety of bug fixes to the Pulp Platform, as well
as the OSTree and RPM plugins, outlined below.


Upgrading
=

The Pulp stable 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-stable or pulp-2-stable 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


Issues Addressed


These issues are fixed in Pulp 2.10.1:

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

  Pulp
2344Streamer 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] Pulp 2.11.0 Beta 1 Now Available

[Sean Myers]

On 10/26/2016 12:23 AM, Sean Myers wrote:
> More information about these new features can be found in the release notes:
> http://docs.pulpproject.org/en/2.11/testing/user-guide/release-notes/2.11.x.html
> http://docs.pulpproject.org/en/2.11/testing/plugins/pulp_rpm/user-guide/release-notes/2.11.x.html
> Docker 2.2 and OSTree 1.2 release notes coming soon.

Docker and OSTree release notes are now available:
https://docs.pulpproject.org/en/2.11/testing/plugins/pulp_docker/user-guide/release-notes/2.2.x.html
https://docs.pulpproject.org/en/2.11/testing/plugins/pulp_ostree/user-guide/release-notes/1.2.x.html




signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.11.0 Beta 1 Now Available

[Sean Myers]

Pulp 2.11.0 Beta 1 is now available, and can be downloaded from
the 2.11 beta repositories:

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

New features for Pulp 2.11 include more improvements to RPM syncing, the 
ability to pull older
trees with OSTree, incremental publish with Docker and RPM, and the ability to 
upload DRPMS.
Several bugs were also fixed; all the details can be found later in this 
announcement.

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.11/testing/user-guide/release-notes/2.11.x.html
http://docs.pulpproject.org/en/2.11/testing/plugins/pulp_rpm/user-guide/release-notes/2.11.x.html
Docker 2.2 and OSTree 1.2 release notes coming soon.

Try out the new features, and let us know how they work for you!


Upgrading
=

The 2.11 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.11-beta repository, you'll want to follow the standard
upgrade path, with migrations, to get to 2.11:

> $ 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


New Features


Here are the specific stories done for 2.11:

  Docker Support
2114As a user, I can perform incremental publish with Docker rsync 
distributor

  OSTree Support
2205As a user, I want to pull older versions of trees available to 
atomic hosts.

  Pulp
2186As a user, pulp-manage-db refuses to run if other pulp 
processes are running locally

  RPM Support
2212As a user I can see in the task report of copy operation list 
of units which did not pass signature filter
2211As a user, I can sync a distribution unit with the existing 
yum_importer without requiring yum metadata
2132As a consumer of Pulp content I want ISO & ISO_rsync 
distributor to support relative_url for consistency with yum
2113As a user, I can perform an incremental publish using ISO rsync 
distributor
1983As a user, an importer config change or content removal will 
cause the next sync to be full
1806As a user, I can use pulp-admin to upload drpms

View this list in redmine:
http://bit.ly/2eQz5Ui


Issues Addressed


Here are the bug fixes specific to 2.11:

  Pulp
2172Investigate memory usage and optimization
2133Permissions docs should include some info on /v2/
1977basic auth in URL fails when using authenticated proxy
1069extra Task ID in docs example to bind a repo
752 Suggestion to add -v remains even if you use -v

  Python Support
1961Package twine for Fedora and RHEL

  RPM Support
2363Pulp acts like all is well when a sync completely fails
2321Pulp can't handle mirrorlists with invalid entries
2224Cannot sync from mirrorlists
2071Creating yum distributor without https, http keys in config 
crashes

All bug fixes from Pulp 2.10.1 and earlier are included in Pulp 2.11.

View this list in redmine:
http://bit.ly/2dHG8ws



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.10.1 Beta 2 now available!

[Sean Myers]

Pulp 2.10.1 Beta 2 is now available in the beta repositories:

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

This release includes bug fixes to Pulp Platform, the RPM Plugin,
and the OSTree plugin.

Beta 2 includes a small number of minor improvements to Beta 1, including
tweaks to the SELinux policy and some spec file fixes that fix issues with these
releases and the "downstream" releases of pulp in Fedora 24 not playing nice 
with
each other (they do now). We also picked up a nice lazy streamer fix in #2344.

Only the Pulp Platform packages are different in Beta 2 (RPM and OSTree are
unchanged).

Upgrade testing to 2.10.1 is still ongoing; we'll be releasing 2.10.1 as either
generally available (GA) or a new beta depending on those test results. :)


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


Issues Addressed


These issues are 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



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.10.1 Beta 1 now available!

[Sean Myers]

Pulp 2.10.1 Beta 1 is now available in the beta repositories:

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

This release includes bug fixes to Pulp Platform, the RPM Plugin,
and the OSTree plugin.

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


Issues Addressed


These issues are fixed in Pulp 2.10.1:

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

  Pulp
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



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Sept 23 Triage delayed

[Sean Myers]

Due to a conflict with another meeting, tomorrow's triage session (or today's, 
depending on where you are) is going to happen a little bit later in the day.

Triage is normally scheduled for 10:30 AM, Eastern Time. The conflicting 
meeting ends at 11, so we'll give folks time to get settled after the meeting 
and most likely start triage an hour later, at 11:30 AM in the usual place 
(#pulp-dev on freenode). Apologies for any inconvenience. If that time doesn't
work out, I'll update here with the details.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9.3 Generally Available

[Sean Myers]

Pulp 2.9.3 is now Generally Available in the stable repositories:

  https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.9/

This release includes bug fixes to Pulp Platform, the RPM Plugin,
and the Docker plugin.

No changes have taken place between 2.9.3 Beta 2 and this release.

View this announcement on pulproject.org:
http://pulpproject.org/2016/09/19/pulp-2-9-3-generally-available/


Upgrading
=

The 2.9 stable repositories are not included in the pulp repo files, and must be
installed manually with the following repository baseurls.

Fedora 23: 
https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.9/fedora-$releasever/$basearch/
RHEL/Centos 6 & 7: 
https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.9/$releasever/$basearch/

After enabling the pulp 2.9 repository for your distribution, 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


Issues Addressed


These issues are fixed in Pulp 2.9.3:

  Docker Support
2198Timestamp not updated for changed docker_tag
2142Units created with 0-byte files when sync runs out of disk space
  Pulp
2121Requires: selinux-policy is broken in spec files
2112Status API does not log Qpid errors
2047directory creation race condition during publish
  RPM Support
2236Upgrading to pulp 2.9 causes sync of repos with DRPM' with a 
"relativepath" field to fail.
2234Upgrading to pulp 2.9 causes sync of repos with SRPM's with a 
filelist field to fail.
2197Error report for file size verification is not generated 
correctly
2134Updating a repo without specifying checksum_type causes KeyError
1926package without epoch in the erratum pkglist is not handled 
correctly during publish
1881pulp-admin fails to display the erratum if not all metadata is 
present
236 Don't re-download rpms if they exist on disk

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


Fedora Support
==

Fedora 22 packages are incidentally included in this release, but are not
supported due to Fedora 22 reaching its end-of-life.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp 2.10.0 Now Generally Available

[Sean Myers]

On 09/15/2016 03:36 PM, Sean Myers wrote:
> 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, to get to 2.10:
> 
>> $ 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

The 2.10 *stable* repositories are also included in the pulp repo files, but
the repository you'll need to enable is either pulp-2-stable or pulp-stable.

My apologies for the delicious copypasta. :)



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.10.0 Now Generally Available

[Sean Myers]

Pulp 2.10.0 is now  available, and can be downloaded from the Pulp 2.10 stable 
repositories:

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

New features for Pulp 2.10 include the new rsync distributor, new 
high-availability
features for resource managers, as well as some improvements to RPM publishing 
and
package validation. Several bugs were also fixed; all the details can be found 
later
in this announcement.

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.10/testing/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_rpm/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_docker/user-guide/release-notes/2.1.x.html

Try out the new features, and let us know how they work for you!

These two issues were listed as blockers for release candidate 1, and fixed in 
release
candidate 2. Upgrade testing to 2.10.0 from earlier versions of pulp is 
complete and has
verified that these issues do not affect 2.10.0: 

2234Upgrading to pulp 2.9 causes sync of repos with SRPM's with a 
filelist field to fail.
  https://pulp.plan.io/issues/2234

2236Upgrading to pulp 2.9 causes sync of repos with DRPM' with a 
"relativepath" field to fail.
  https://pulp.plan.io/issues/2236

No other blocking issues have been identified, which clears 2.10.0 to become 
generally
available a little earlier than I indicated in my previous announcement for 
this release.


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, to get to 2.10:

> $ 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


New Features


Here are the specific stories done for 2.10:

  Docker Support
1887As a user, I can use the rsync predistributor with docker web 
distributor
1291As a user, I can sync feeds that require username/password 
authentication
  Pulp
1990Rsync distributor
1963As a user, I can use rsync distributor to publish iso 
repositories
1759As a user, I can use rsync distributor to publish RPM 
repositores
898 As a user I can run multiple pulp_resource_managers 
concurrently with all of them actively participating
  RPM Support
1991As a user, uploaded units which don't pass the signature check 
are not imported
1982As a user, I can force a full sync
1878Support for choosing the checksum type in updateinfo
1156As a user, I can have an "signature" attribute stored for RPMs, 
SRPMs, and DRPMs

View this list in redmine:
http://bit.ly/2axDGKA


Issues Addressed


Here are the bug fixes specific to 2.10:

  Pulp
2082Cannot add importer to the repository
1948Upgrading RPMs on EL6 sometimes fails during pre script
2187rsync as predistributor logic is wrong
2202predistributor logic in platform does not account for 
force_full and updated distributor configs
2030importer config is not validated during the update
2039Not full importer config is validated in the update call
2118Reduce runtime of file path migration
1606API call to install consumers raises 500 if body contains wrong 
data type
2106Pin to flake8 2.6.2
  RPM Support
2188Make GPG signature checking is called "filtering"
2042updateinfo.xml is missing checksums
2199The RPM rsync distributor breaks when SELinux is enabled
2115The 'skip_fast_forward' in RPM rsync config should be renamed 
to 'force_full'

All bug fixes from Pulp 2.9.2 and earlier are included in Pulp 2.10, as well as 
the fixes
for the two blockers mentioned above.

View this list in redmine:
http://bit.ly/2awB1h4


Fedora Support
==

Fedora 22 has reached its end-of-life. As a result Pulp 2.10 is being built for 
(and tested on)
Fedoras 23 and 24.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.10 Release Candidate 2 Now Available

[Sean Myers]

Pulp 2.10 Release Candidate 2 is now available, and can be downloaded from
the 2.10 beta repositories:

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

Two blocking issues have been discovered since the release of RC 1. They were 
addressed
in Pulp 2.9, and since they affect upgrading from earlier versions of Pulp they 
were
labeled as blockers for 2.10 as well. Since Release Candidate 1, only the fixes 
for these
two issues have been added:

2234Upgrading to pulp 2.9 causes sync of repos with SRPM's with a 
filelist field to fail.
  https://pulp.plan.io/issues/2234

2236Upgrading to pulp 2.9 causes sync of repos with DRPM' with a 
"relativepath" field to fail.
  https://pulp.plan.io/issues/2236

RC 2 should become Generally Available in one week (9/20), but may be pushed 
back if:

- new blocker issues are discovered
- upgrade testing takes longer than expected
- upgrade testing fails

New features for Pulp 2.10 include the new rsync distributor, new 
high-availability
features for resource managers, as well as some improvements to RPM publishing 
and
package validation. Several bugs were also fixed; all the details can be found 
later
in this announcement.

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.10/testing/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_rpm/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_docker/user-guide/release-notes/2.1.x.html

Try out the new features, and let us know how they work for you!


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, to get to 2.10:

> $ 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


New Features


Here are the specific stories done for 2.10:

  Docker Support
1887As a user, I can use the rsync predistributor with docker web 
distributor
1291As a user, I can sync feeds that require username/password 
authentication
  Pulp
1990Rsync distributor
1963As a user, I can use rsync distributor to publish iso 
repositories
1759As a user, I can use rsync distributor to publish RPM 
repositores
898 As a user I can run multiple pulp_resource_managers 
concurrently with all of them actively participating
  RPM Support
1991As a user, uploaded units which don't pass the signature check 
are not imported
1982As a user, I can force a full sync
1878Support for choosing the checksum type in updateinfo
1156As a user, I can have an "signature" attribute stored for RPMs, 
SRPMs, and DRPMs

View this list in redmine:
http://bit.ly/2axDGKA


Issues Addressed


Here are the bug fixes specific to 2.10:

  Pulp
2082Cannot add importer to the repository
1948Upgrading RPMs on EL6 sometimes fails during pre script
2187rsync as predistributor logic is wrong
2202predistributor logic in platform does not account for 
force_full and updated distributor configs
2030importer config is not validated during the update
2039Not full importer config is validated in the update call
2118Reduce runtime of file path migration
1606API call to install consumers raises 500 if body contains wrong 
data type
2106Pin to flake8 2.6.2
  RPM Support
2188Make GPG signature checking is called "filtering"
2042updateinfo.xml is missing checksums
2199The RPM rsync distributor breaks when SELinux is enabled
2115The 'skip_fast_forward' in RPM rsync config should be renamed 
to 'force_full'

All bug fixes from Pulp 2.9.2 and earlier are included in Pulp 2.10, as well as 
the fixes
for the two blockers mentioned above.

View this list in redmine:
http://bit.ly/2awB1h4


Fedora Support
==

Fedora 22 has reached its end-of-life. As a result Pulp 2.10 is being built for 
(and tested on)
Fedoras 23 and 24.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9.3 Beta 2 Now Available

[Sean Myers]

Pulp 2.9.3 Beta 2 is now available in the beta repositories:

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

This release includes bug fixes to Pulp Platform, the RPM Plugin,
and the Docker plugin.

Since Beta 1, a few blocking issues were discovered related to upgrading to
2.9 from earlier versions of pulp. Those fixes and a couple other minor bugfixes
have been included in Beta 2.

The blocking upgrade issues also affect 2.10, so we'll be releasing a new 2.10
release candidate as soon as possible.

Upgrading
=

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

After enabling the pulp-2.9-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


Issues Addressed


These issues are fixed in Pulp 2.9.3:

  Docker Support
2198Timestamp not updated for changed docker_tag
2142Units created with 0-byte files when sync runs out of disk space
  Pulp
2121Requires: selinux-policy is broken in spec files
2112Status API does not log Qpid errors
2047directory creation race condition during publish
  RPM Support
2236Upgrading to pulp 2.9 causes sync of repos with DRPM' with a 
"relativepath" field to fail.
2234Upgrading to pulp 2.9 causes sync of repos with SRPM's with a 
filelist field to fail.
2197Error report for file size verification is not generated 
correctly
2134Updating a repo without specifying checksum_type causes KeyError
1926package without epoch in the erratum pkglist is not handled 
correctly during publish
1881pulp-admin fails to display the erratum if not all metadata is 
present
236 Don't re-download rpms if they exist on disk

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


Fedora Support
==

Fedora 22 packages are incidentally included in this release, but are not
supported due to Fedora 22 reaching its end-of-life.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.10 Release Candidate 1 Now Available

[Sean Myers]

Pulp 2.10 Release Candidate 1 is now available, and can be downloaded from
the 2.10 beta repositories:

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

No blocking issues have been discovered since the release of Beta 3, so that 
release has
been promoted to Release Candidate 1. RC 1 should become Generally Available in 
one week
(9/13), but may be pushed back if:

- new blocker issues are discovered
- upgrade testing takes longer than expected
- upgrade testing fails

New features for Pulp 2.10 include the new rsync distributor, new 
high-availability
features for resource managers, as well as some improvements to RPM publishing 
and
package validation. Several bugs were also fixed; all the details can be found 
later
in this announcement.

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.10/testing/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_rpm/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_docker/user-guide/release-notes/2.1.x.html

Try out the new features, and let us know how they work for you!


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, to get to 2.10:

> $ 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


New Features


Here are the specific stories done for 2.10:

  Docker Support
1887As a user, I can use the rsync predistributor with docker web 
distributor
1291As a user, I can sync feeds that require username/password 
authentication
  Pulp
1990Rsync distributor
1963As a user, I can use rsync distributor to publish iso 
repositories
1759As a user, I can use rsync distributor to publish RPM 
repositores
898 As a user I can run multiple pulp_resource_managers 
concurrently with all of them actively participating
  RPM Support
1991As a user, uploaded units which don't pass the signature check 
are not imported
1982As a user, I can force a full sync
1878Support for choosing the checksum type in updateinfo
1156As a user, I can have an "signature" attribute stored for RPMs, 
SRPMs, and DRPMs

View this list in redmine:
http://bit.ly/2axDGKA


Issues Addressed


Here are the bug fixes specific to 2.10:

  Pulp
2082Cannot add importer to the repository
1948Upgrading RPMs on EL6 sometimes fails during pre script
2187rsync as predistributor logic is wrong
2202predistributor logic in platform does not account for 
force_full and updated distributor configs
2030importer config is not validated during the update
2039Not full importer config is validated in the update call
2118Reduce runtime of file path migration
1606API call to install consumers raises 500 if body contains wrong 
data type
2106Pin to flake8 2.6.2
  RPM Support
2188Make GPG signature checking is called "filtering"
2042updateinfo.xml is missing checksums
2199The RPM rsync distributor breaks when SELinux is enabled
2115The 'skip_fast_forward' in RPM rsync config should be renamed 
to 'force_full'

All bug fixes from Pulp 2.9.2 and earlier are included in Pulp 2.10.

View this list in redmine:
http://bit.ly/2awB1h4


Fedora Support
==

Fedora 22 has reached its end-of-life. As a result Pulp 2.10 is being built for 
(and tested on)
Fedoras 23 and 24.




signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9.3 Beta 1 Now Available

[Sean Myers]

Pulp 2.9.3 Beta 1 is now available in the beta repositories:

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

This release includes bug fixes to Pulp Platform, the RPM Plugin,
and the Docker plugin.


Upgrading
=

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

After enabling the pulp-2.9-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


Issues Addressed


These issues are fixed in Pulp 2.9.3:

  Docker Support
2142Units created with 0-byte files when sync runs out of disk space

  Pulp
2112Status API does not log Qpid errors
2121Requires: selinux-policy is broken in spec files

  RPM Support
1881pulp-admin fails to display the erratum if not all metadata is 
present
2134Updating a repo without specifying checksum_type causes KeyError
236 Don't re-download rpms if they exist on disk
1926package without epoch in the erratum pkglist is not handled 
correctly during publish
2197Error report for file size verification is not generated 
correctly

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


Fedora Support
==

Fedora 22 packages are incidentally included in this release, but are not
supported due to Fedora 22 reaching its end-of-life.




signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.10 Beta 3 Now Available

[Sean Myers]

Pulp 2.10 Beta 3 is now available, and can be downloaded from
the 2.10 beta repositories:

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

Our excellent testers discovered a new issue related to SELinux (#2199, listed 
below)
that is fixed in this beta release.

New features for Pulp 2.10 include the new rsync distributor, new 
high-availability
features for resource managers, as well as some improvements to RPM publishing 
and
package validation. Several bugs were also fixed; all the details can be found 
later
in this announcement.

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.10/testing/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_rpm/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_docker/user-guide/release-notes/2.1.x.html

Try out the new features, and let us know how they work for you!


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, to get to 2.10:

> $ 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


New Features


Here are the specific stories done for 2.10:

  Docker Support
1887As a user, I can use the rsync predistributor with docker web 
distributor
1291As a user, I can sync feeds that require username/password 
authentication
  Pulp
1990Rsync distributor
1963As a user, I can use rsync distributor to publish iso 
repositories
1759As a user, I can use rsync distributor to publish RPM 
repositores
898 As a user I can run multiple pulp_resource_managers 
concurrently with all of them actively participating
  RPM Support
1991As a user, uploaded units which don't pass the signature check 
are not imported
1982As a user, I can force a full sync
1878Support for choosing the checksum type in updateinfo
1156As a user, I can have an "signature" attribute stored for RPMs, 
SRPMs, and DRPMs

View this list in redmine:
http://bit.ly/2axDGKA


Issues Addressed


Here are the bug fixes specific to 2.10:

  Pulp
2082Cannot add importer to the repository
1948Upgrading RPMs on EL6 sometimes fails during pre script
2187rsync as predistributor logic is wrong
2202predistributor logic in platform does not account for 
force_full and updated distributor configs
2030importer config is not validated during the update
2039Not full importer config is validated in the update call
2118Reduce runtime of file path migration
1606API call to install consumers raises 500 if body contains wrong 
data type
2106Pin to flake8 2.6.2
  RPM Support
2188Make GPG signature checking is called "filtering"
2042updateinfo.xml is missing checksums
2199The RPM rsync distributor breaks when SELinux is enabled
2115The 'skip_fast_forward' in RPM rsync config should be renamed 
to 'force_full'

All bug fixes from Pulp 2.9.2 and earlier are included in Pulp 2.10.

View this list in redmine:
http://bit.ly/2awB1h4


Fedora Support
==

Fedora 22 has reached its end-of-life. As a result Pulp 2.10 is being built for 
Fedoras 23 and 24.

Our CI system now has a working test environment for Fedora 24, and with this 
beta release Fedora 24
packages are being run through our automated integration testing. (woot!) 
Thanks to Elyézer Rezende
for fixing up the CI environment to make this possible.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.10 Beta 2 Now Available

[Sean Myers]

Pulp 2.10 Beta 2 is now available, and can be downloaded from
the 2.10 beta repositories:

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

New features for Pulp 2.10 include the new rsync distributor, new 
high-availability
features for resource managers, as well as some improvements to RPM publishing 
and
package validation. Several bugs were also fixed; all the details can be found 
later
in this announcement.

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.10/testing/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_rpm/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_docker/user-guide/release-notes/2.1.x.html

Try out the new features, and let us know how they work for you!


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, to get to 2.10:

> $ 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


New Features


Here are the specific stories done for 2.10:

  Docker Support
1887As a user, I can use the rsync predistributor with docker web 
distributor
1291As a user, I can sync feeds that require username/password 
authentication
  Pulp
1990Rsync distributor
1963As a user, I can use rsync distributor to publish iso 
repositories
1759As a user, I can use rsync distributor to publish RPM 
repositores
898 As a user I can run multiple pulp_resource_managers 
concurrently with all of them actively participating
  RPM Support
1991As a user, uploaded units which don't pass the signature check 
are not imported
1982As a user, I can force a full sync
1878Support for choosing the checksum type in updateinfo
1156As a user, I can have an "signature" attribute stored for RPMs, 
SRPMs, and DRPMs

View this list in redmine:
http://bit.ly/2axDGKA


Issues Addressed


Here are the bug fixes specific to 2.10:

  Pulp
2118Reduce runtime of file path migration
2106Pin to flake8 2.6.2
2082Cannot add importer to the repository
2039Not full importer config is validated in the update call
2030importer config is not validated during the update
1948Upgrading RPMs on EL6 sometimes fails during pre script
1606API call to install consumers raises 500 if body contains wrong 
data type
  RPM Support
2188Make sure GPG signature checking is called "filtering"
2115The 'skip_fast_forward' in RPM rsync config should be renamed 
to 'force_full'
2042updateinfo.xml is missing checksums

All bug fixes from Pulp 2.9.2 and earlier are included in Pulp 2.10.

View this list in redmine:
http://bit.ly/2awB1h4


Fedora Support
==

Fedora 22 has reached its end-of-life. As a result 2.10 has been built for 
Fedoras 23 and 24.

Our CI system is still struggling to have a working test environment for Fedora 
24,
so at the moment Fedora 24 packages are not being run through our automated 
integration
testing. This will be fixed before the next 2.10 pre-release.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.7 Generally Available

[Sean Myers]

The Pulp 2.8.7 bugfix release is now available in the stable repositories:

  https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.8/

This release includes a small number of fixes to bugs in Pulp Platform,
the Docker plugin, and crane.


Upgrading
=

After enabling the 2.8 stable repositories, 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


Issues Addressed


  Crane
1893pulp_docker does not support Docker < 1.10 with manifests that 
were published from Docker >= 1.10
  Docker Support
1925v1 sync errors
  Pulp
2144unbound method send()
2124Pulp status check leaves open Pipes
2065Error doing an ostree pull from pulp with an entitlement 
certificate.
2038The nectar config pulp_streamer gets doesn't seem to include 
plugin-level settings
1788The pulp_streamer is subject to requests issue #2863
963 Invalid Content-Encoding HTTP header in REST API

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



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9.2 Generally Available

[Sean Myers]

Pulp 2.9.2 is now generally available in the stable repositories:

  https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.9/

This release includes fixes to Pulp Platform and the RPM Plugin.


Upgrading
=

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

After enabling the pulp-2-stable or pulp-stable 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


Issues Addressed


These critical issues are fixed in Pulp 2.9.2:

  Pulp
1863Exception using regex in filters against associate endpoint
1894unassociate rpms API request using unit_ids removes all rpm 
from repo
1728Please relax input validation on --login for 'pulp-admin user 
create'
  RPM Support
   2135 Repo publish error Unclosed tags: endverbatim
2093errors importing some rpms after upgrading to pulp 2.9
2077publish fails if Django Template Syntax in changelog

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


Fedora Support
==

Fedora 22 packages are incidentally included in this release, but are not
supported due to Fedora 22 reaching its end-of-life.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] 2.10 unblocked

[Sean Myers]

On 08/09/2016 11:32 AM, Sean Myers wrote:
> The fix for issue #2077 was incomplete, so the 2.9.2 release is blocked until
> we fix it. This issue has also been found to affect the 2.10 release,
> which means that release is also blocked.
> 
> fortunately, the more complete fix is already up for review; I'll be putting 
> out
> new builds once the fix is merged. My best ETA for those builds is later 
> today or
> tomorrow, but I'll update on this list if that changes.

As mentioned in the 2.9.2 hotfix notes from earlier today, #2077 and the issue
that was created to complete the first, #2135, have been fixed. They're 
currently
being verified in testing. Assuming no further interruptions, we should see a 
new
beta for 2.10 on Monday.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.7 Beta 3 Now Available

[Sean Myers]

Pulp 2.8.7 Bugfix Release Beta 3 is now available in the beta repositories:

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

This release includes a small number of fixes to bugs in Pulp Platform,
the Docker plugin, and crane.

The new issue in the list below, #2144, is related to the issue that was
blocking this beta, #1788. Both are now fixed, and out integration tests
are all happy again (woot).

Upgrading
=

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

After enabling the 2.8 beta repositories, 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


Issues Addressed


  Crane
1893pulp_docker does not support Docker < 1.10 with manifests that 
were published from Docker >= 1.10
  Docker Support
1925v1 sync errors
  Pulp
2144unbound method send()
2124Pulp status check leaves open Pipes
2065Error doing an ostree pull from pulp with an entitlement 
certificate.
2038The nectar config pulp_streamer gets doesn't seem to include 
plugin-level settings
1788The pulp_streamer is subject to requests issue #2863
963 Invalid Content-Encoding HTTP header in REST API

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



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9.2 Hotfix Beta 2 Now Available

[Sean Myers]

Pulp 2.9.2 Hotfix Beta 2 is now available in the beta repositories:

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

This release includes fixes to Pulp Platform and the RPM Plugin.

This is a hotfix release, which will become Generally Available as
soon as all related bugs (listed below) are tested and verified. Most
changes are verified for this beta already, so once the blocking issues
that were fixed for this release are verified this will become
Generally Available.


Upgrading
=

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

After enabling the pulp-2.9-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


Issues Addressed


These issues are fixed in Pulp 2.9.2:

  Pulp
1863Exception using regex in filters against associate endpoint
1894unassociate rpms API request using unit_ids removes all rpm 
from repo
1728Please relax input validation on --login for 'pulp-admin user 
create'
  RPM Support
   2135 Repo publish error Unclosed tags: endverbatim
2093errors importing some rpms after upgrading to pulp 2.9
2077publish fails if Django Template Syntax in changelog

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


Fedora Support
==

Fedora 22 packages are incidentally included in this release, but are not
supported due to Fedora 22 reaching its end-of-life.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] 2.9.2 and 2.10 currently blocked

[Sean Myers]

On 08/04/2016 02:57 PM, Sean Myers wrote:
> Issues Addressed
> 
> 
>   2077publish fails if Django Template Syntax in changelog

The fix for issue #2077 was incomplete, so the 2.9.2 release is blocked until
we fix it. This issue has also been found to affect the 2.10 release,
which means that release is also blocked.

fortunately, the more complete fix is already up for review; I'll be putting out
new builds once the fix is merged. My best ETA for those builds is later today 
or
tomorrow, but I'll update on this list if that changes.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.7 Beta 2 Now Available

[Sean Myers]

On 08/01/2016 01:08 PM, Sean Myers wrote:
> This morning we reviewed some issues potentially blocking the
> 2.8.7 release, and have determined that this issue must be
> done before we can release 2.8.7:
> 
> https://pulp.plan.io/issues/1788

The fix for #1788 is now available for testing in Pulp 2.8.7 Beta 2,
which is now available in the 2.8 beta repositories.

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

See my original post (Pulp 2.8.7 Beta 1 Now Available) for upgrade notes.


Issues Addressed


Some new bugfixes landed in the Beta 2 build, including #1788, #2124,
and #963, all listed below.

 Crane
1893pulp_docker does not support Docker < 1.10 with manifests that 
were published from Docker >= 1.10
  Docker Support
1925v1 sync errors
  Pulp
1788The pulp_streamer is subject to requests issue #2863
2124Pulp status check leaves open Pipes
2038The nectar config pulp_streamer gets doesn't seem to include 
plugin-level settings
963 Invalid Content-Encoding HTTP header in REST API
2065Error doing an ostree pull from pulp with an entitlement 
certificate.

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



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9.2 Hotfix Beta 1 Now Available

[Sean Myers]

Pulp 2.9.2 Hotfix Beta 1 is now available in the beta repositories:

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

This release includes fixes to Pulp Platform and the RPM Plugin.

This is a hotfix release, which will become Generally Available as
soon as all related bugs (listed below) are tested and verified.


Upgrading
=

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

After enabling the pulp-2.9-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


Issues Addressed


These issues are fixed in Pulp 2.9.2:

  Pulp
1863Exception using regex in filters against associate endpoint
1894unassociate rpms API request using unit_ids removes all rpm 
from repo
1728Please relax input validation on --login for 'pulp-admin user 
create'
  RPM Support
2093errors importing some rpms after upgrading to pulp 2.9
2077publish fails if Django Template Syntax in changelog

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


Fedora Support
==

Fedora 22 packages are incidentally included in this release, but are not
supported due to Fedora 22 reaching its end-of-life.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp 2.10 Beta 1 Now Available

[Sean Myers]

Additionally, users upgrading from pulp 2.8.2 and earlier should read this this
note before upgrading:

http://docs.pulpproject.org/en/2.10/testing/user-guide/release-notes/2.10.x.html#upgrade

Apologies for forgetting this bit. :)



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.10 Beta 1 Now Available

[Sean Myers]

Pulp 2.10 Beta 1 is now available, and can be downloaded from
the 2.10 beta repositories:

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

New features for Pulp 2.10 include the new rsync distributor, new 
high-availability
features for resource managers, as well as some improvements to RPM publishing 
and
package validation. Several bugs were also fixed; all the details can be found 
later
in this announcement.

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.10/testing/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_rpm/user-guide/release-notes/2.10.x.html
http://docs.pulpproject.org/en/2.10/testing/plugins/pulp_docker/user-guide/release-notes/2.1.x.html

Try out the new features, and let us know how they work for you!


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, to get to 2.10:

> $ 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


New Features


Here are the specific stories done for 2.10:

  Docker Support
1887As a user, I can use the rsync predistributor with docker web 
distributor
1291As a user, I can sync feeds that require username/password 
authentication
  Pulp
1990Rsync distributor
1963As a user, I can use rsync distributor to publish iso 
repositories
1759As a user, I can use rsync distributor to publish RPM 
repositores
898 As a user I can run multiple pulp_resource_managers 
concurrently with all of them actively participating
  RPM Support
1991As a user, uploaded units which don't pass the signature check 
are not imported
1982As a user, I can force a full sync
1878Support for choosing the checksum type in updateinfo
1156As a user, I can have an "signature" attribute stored for RPMs, 
SRPMs, and DRPMs

View this list in redmine:
http://bit.ly/2axDGKA


Issues Addressed


Here are the bug fixes specific to 2.10:

  Pulp
2118Reduce runtime of file path migration
2106Pin to flake8 2.6.2
2082Cannot add importer to the repository
2039Not full importer config is validated in the update call
2030importer config is not validated during the update
1948Upgrading RPMs on EL6 sometimes fails during pre script
1606API call to install consumers raises 500 if body contains wrong 
data type
  RPM Support
2115The 'skip_fast_forward' in RPM rsync config should be renamed 
to 'force_full'
2042updateinfo.xml is missing checksums

All bug fixes from Pulp 2.9.2 and earlier are included in Pulp 2.10.

View this list in redmine:
http://bit.ly/2awB1h4

Fedora Support
==

Fedora 22 has reached its end-of-life. As a result 2.10 has been built for 
Fedoras 23 and 24.

Our CI system is still struggling to have a working test environment for Fedora 
24,
so at the moment Fedora 24 packages are not being run through our automated 
integration
testing. This will be fixed before the next 2.10 pre-release.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.7 BLOCKED

[Sean Myers]

This morning we reviewed some issues potentially blocking the
2.8.7 release, and have determined that this issue must be
done before we can release 2.8.7:

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

The fix is already POSTed, so we're merged and tested this
fix, the 2.8.7 release should be unblocked and we'll build
Beta 2.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.7 Beta 1 Now Available

[Sean Myers]

Pulp 2.8.7 Bugfix Release Beta 1 is now available in the beta repositories:

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

This release includes a small number of fixes to bugs in Pulp Platform,
the Docker plugin, and crane.


Upgrading
=

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

After enabling the 2.8 beta repositories, 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


Issues Addressed


  Crane
1893pulp_docker does not support Docker < 1.10 with manifests that 
were published from Docker >= 1.10
  Docker Support
1925v1 sync errors
  Pulp
2038The nectar config pulp_streamer gets doesn't seem to include 
plugin-level settings
2065Error doing an ostree pull from pulp with an entitlement 
certificate.

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



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9.1 Now Generally Available

[Sean Myers]

Pulp 2.9.1 is now available in the stable repositories:

  https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.9/

This release includes fixes to Pulp Platform, as well as the Docker plugin,
RPM plugin, Puppet plugin, and crane.

Of particular interest to RPM users are issues #1949 and #2048, two issues
that were severely impacting errata-related syncing and publishing. See the 
lists of issues below for more details.


Upgrading
=

The pulp-2-stable repository is included in the pulp repo files:
https://repos.fedorapeople.org/repos/pulp/pulp/fedora-pulp.repo for fedora 23
https://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo for RHEL 6 & 7

After enabling the 2.9 stable 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


Issues Addressed


These issues are specific to Pulp 2.9 and are included in this release:

  Pulp
2081All of repo's distributors are updated at end of publish
2060As a user, I want pulp-manage-db to output a message before any 
"known big migrations", so that I am aware that the migration could potentially 
be time-consuming
  ^ This change covered multiple projects (including Python) and 
was handled as a bug fix.
1829pulp-admin repo list -s unexpected error
1673Pulp's worker watcher does not notice workers that got killed 
by OOM killer and their tasks stay "running" forever
  RPM Support
2051Ludicrous number of WARNING logs from publish
2020Cannot provide multiple checksums when uploading an erratum

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


These issues were fixed in the Pulp 2.8 stream and are also included in this 
release:

  Crane
1893pulp_docker does not support Docker < 1.10 with manifests that 
were published from Docker >= 1.10
  Docker Support
1925v1 sync errors
  Pulp
2065Error doing an ostree pull from pulp with an entitlement 
certificate.
2056Distribution storage path migration re-links .treeinfo files 
incorrectly.
2031possible incorrect URL param parsing by streamer
2012alternate content source refresh fails with json serialization 
error
  RPM Support
2048Errata update failure during sync or upload
2032pulp sets reboot_suggested to True for all errata when syncing 
from published repo
1949re-publish takes longer than expected

View this list in Redmine (The issues reflect their state in the 2.8 stream):
http://bit.ly/2a8AjvQ



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Update on Upcoming Releases

[Sean Myers]

Just a quick note about upcoming releases...

2.10 Beta 1 was scheduled for today, but has been delayed by a week.

I've updated the Release Schedule to reflect the change:
https://pulp.plan.io/projects/pulp/wiki/Release_Schedule

2.9.1 was supposed to come out yesterday, but our Jenkins environment
was unstable for the better part of the day which delayed the release.
I'll be releasing that shortly.

2.8.7 Beta 1 should also be released today, barring further Jenkins
instability.

Next week should see the release of 2.9.2 Beta 1 on Monday, and the
releases of 2.10 Beta 1 and 2.8.7 GA on Tuesday.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp 2.9.1 Beta 1 Now Available

[Sean Myers]

We had an odd documentation issue in the docker plugin that Brian
Bouterse took care of[0], so I've pushed a release to just that
plugin, bumping us from 2.0.3-0.1.beta on the docker packages to
2.0.3-0.2.beta. This change has no impact on the code being run,
so no action needs to be taken if you're running the 2.9 beta and
see the new docker plugin get installed. 2.9.1 is still expected to
be Generally Available next Tuesday, July 26, but now we'll release
it with working documentation. :)

/me turns on Homer Simpson's "Everything is OK" alarm[1].

[0]: https://github.com/pulp/pulp_docker/pull/163
[1]: https://simpsonswiki.com/wiki/Everything%27s_OK_alarm



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9.1 Beta 1 Now Available

[Sean Myers]

Pulp 2.9.1 Beta 1 is now available in the beta repositories:

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

This release includes fixes to Pulp Platform, as well as the Docker plugin,
RPM plugin, Puppet plugin, and crane.

Of particular interest to RPM users are issues #1949 and #2048, two issues
that were severely impacting errata-related syncing and publishing. See the 
lists of issues below for more details.


Upgrading
=

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

After enabling the 2.9 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


Issues Addressed


These issues are specific to Pulp 2.9 and are included in this release:

  Pulp
2081All of repo's distributors are updated at end of publish
2060As a user, I want pulp-manage-db to output a message before any 
"known big migrations", so that I am aware that the migration could potentially 
be time-consuming
  ^ This change covered multiple projects (including Python) and 
was handled as a bug fix.
1829pulp-admin repo list -s unexpected error
1673Pulp's worker watcher does not notice workers that got killed 
by OOM killer and their tasks stay "running" forever
  RPM Support
2051Ludicrous number of WARNING logs from publish
2020Cannot provide multiple checksums when uploading an erratum

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


These issues were fixed in the Pulp 2.8 stream and are also included in this 
release:

  Crane
1893pulp_docker does not support Docker < 1.10 with manifests that 
were published from Docker >= 1.10
  Docker Support
1925v1 sync errors
  Pulp
2065Error doing an ostree pull from pulp with an entitlement 
certificate.
2056Distribution storage path migration re-links .treeinfo files 
incorrectly.
2031possible incorrect URL param parsing by streamer
2012alternate content source refresh fails with json serialization 
error
  RPM Support
2048Errata update failure during sync or upload
2032pulp sets reboot_suggested to True for all errata when syncing 
from published repo
1949re-publish takes longer than expected

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




signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp 2.8.6 Generally Available

[Sean Myers]

On 07/18/2016 02:54 PM, Sean Myers wrote:

> Issues Addressed
> 
> 
>   Docker Support
>   1925v1 sync errors

I lied! Due to an oversight on my part, this issue was *not* included in 2.8.6,
But it will be included in Pulp 2.8.7 (in beta next week) and Pulp 2.9.1
(in beta tomorrow). I apologize for the inconvenience.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.6 Generally Available

[Sean Myers]

Pulp 2.8.6 is now Generally Available in the stable repositories with bug fixes:

  https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.8/

This release includes a small number of fixes to severe bugs in Pulp Platform,
the RPM plugin, and the Docker plugin. 

Of particular interest to RPM users are issues #1949 and #2048, two issues
that were severely impacting errata-related syncing and publishing. See the 
list of issues below for more details.

Upgrading
=

The Pulp 2 and Pulp stable repositories are included in the pulp repo files:
https://repos.fedorapeople.org/repos/pulp/pulp/fedora-pulp.repo for fedora 22 & 
23
https://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo for RHEL 6 & 7

After enabling the desired repository (pulp-stable or pulp-2-stable), 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


Issues Addressed


  Docker Support
1925v1 sync errors
  Pulp
2056Distribution storage path migration re-links .treeinfo files 
incorrectly.
2012alternate content source refresh fails with json serialization 
error
2031possible incorrect URL param parsing by streamer
  RPM Support
2048Errata update failure during sync or upload
1949re-publish takes longer than expected
2032pulp sets reboot_suggested to True for all errata when syncing 
from published repo

View the full list in Redmine:
http://bit.ly/29vs1bE



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp + Suse / Sles integration

[Sean Myers]

On 07/14/2016 09:44 AM, Nikos Zaharioudakis wrote:
> Hi list,
> 
> recently I came across the video here :
> http://www.pulpproject.org/2015/12/09/syncing-and-publishing-suse-repositories-with-pulp/
> 
> My question would be if the client host needs to access the pulp (synced
> and exported) repos by yum or zypper respectively. I remember that zypper
> repos have different metadata, but zypper could get in love with yum-only
> repos, as long as you declare it so in the .repo file on the client host.
> 
> Could someone provide some more info ?

I was using zypper in all of my SLES testing. It's been a while since I used it,
but if I recall correctly I didn't have to do anything special to add the repo.
"zypper addrepo  " worked fine, and zypper did all the right 
things.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9.0 Generally Available

[Sean Myers]

The Pulp 2.9.0 is now available, and can be downloaded from
the 2.9 stable repositories:

https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.9/

The Pulp "2" and "latest" repositories have also been updated to point to 2.9.0:

https://repos.fedorapeople.org/repos/pulp/pulp/stable/2/
https://repos.fedorapeople.org/repos/pulp/pulp/stable/latest/

This release includes many new features, as well as bug fixes. Owing to the more
rapid time-based release of 2.9, this release should consist of fewer new
features compared to the release of 2.8.

This release was slightly delayed by two blocking issues (2035 and 2037, seen 
below)
which were fixed in Beta 2. The release timeline of 2.10 has not been impacted 
by
these delays.

More information about our release schedule can be found on the Pulp wiki:
https://pulp.plan.io/projects/pulp/wiki/Release_Schedule

Known Issues


Possible Errata Sync Failure


Several issues were reported against Pulp 2.8 that were not included in the 
Pulp 2.9.0 release
as a result of release timing. The list of issues fixed in 2.8.6[0] outlines 
these bugs, but
there is one issue in particular that can potentially break RPM repository 
syncing after
upgrading: https://pulp.plan.io/issues/2048

This issue is related to resyncing errata from some repositories, and in a 
pulp-admin sync
operation looks like this:

Task Failed

Could not parse errata `updated` field: expected format '%Y-%m-%d %H:%M:%S'.
Fail to update the existing erratum SOME_ERRATUM_ID.

As a workaround, you can choose to skip errata in the feed repository. To do 
this, you can
update the repo to skip errata:

pulp-admin rpm repo update --repo-id  --skip=erratum

This will be fixed in Pulp 2.9.1. If you require errata to be synced from a 
feed repository,
consider delaying an upgrade to Pulp 2.9 until 2.9.1 is released.

[0]: http://bit.ly/29vs1bE

RPM Publish Directory
-

A story related to specifying different package publish directories inside an 
RPM repo[1],
e.g. packages go in a configured packages dir, was included in previous betas 
and the
release candidate for 2.9.0. Testing revealed that the feature didn't perform 
as expected,
so that feature has been pulled from this release. It is likely to return in a 
future
release.

[1]: https://pulp.plan.io/issues/1976

Upgrading
=

The Pulp 2 stable repository (pulp-2-stable) is included in the pulp repo files:
https://repos.fedorapeople.org/repos/pulp/pulp/fedora-pulp.repo for fedora 22 & 
23
https://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo for RHEL 6 & 7

After enabling the pulp-2-stable repository, you'll want to follow the standard
upgrade path, with migrations, to get to 2.9:

> $ 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

Supported Fedora Versions
=

Fedora 22 is no longer a supported Fedora release. We will not be supporting 
Fedora 22
for Pulp 2.9 and onward. Supported Fedora 24 builds will be starting as soon as 
possible.

We'll be updating our docs soon with more details about our Fedora support 
policy than
what's currently there[2]. In the meantime, Pulp users on Fedora 22 are 
encouraged to
upgrade to Fedora 23 to continue to receive supported releases.

[2]: 
http://docs.pulpproject.org/user-guide/installation/index.html#supported-operating-systems

New Features


New features for Pulp 2.9 include optimizations in publishing, repoview support
for yum repos, langpacks support for yum repos, and more:

  Pulp
1724Publish should be a no-op if no units and no settings have 
changed since the last successful publish

  RPM Support
1716As a user, I can have better memory performance on Publish by 
using SAX instead of etree for comps and updateinfo XML production
1543As a user, I would like incremental export to be the same 
format as full export
1367comps langpacks support
1158As a user, I can force full/fresh publish of rpms and not do an 
incremental publish
1003As a user, I can use pulp-admin to upload of package_environment
189 Repoview-like functionality for browsing repositories via the 
web interface

View this list in redmine:
http://bit.ly/1XXtIps

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.9/user-guide/release-notes/2.9.x.html
http://docs.pulpproject.org/en/2.9/plugins/pulp_rpm/user-guide/release-notes/2.9.x.html


Issues Addressed


All bug fixes from Pulp 2.8.5 and earlier are included in Pulp 2.9.

Here are the bug fixes specific to 2.9:

  Pulp
2015rpm repo publish fails with "Incorrect length of data produced" 
error
1928Publish should be operational 

[Pulp-list] 2.8.6 Beta 1 Now Available

[Sean Myers]

Pulp 2.8.6 Bugfix Release Beta 1 is now available in the beta repositories:

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

This release includes a small number of fixes to severe bugs in Pulp Platform,
the RPM plugin, and the Docker plugin. 

Of particular interest to RPM users are issues #1949 and #2048, two issues
that were severely impacting errata-related syncing and publishing. See the 
list of issues below for more details.

Upgrading
=

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

After enabling the 2.8 beta repositories, 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


Issues Addressed


  Docker Support
1925v1 sync errors
  Pulp
2056Distribution storage path migration re-links .treeinfo files 
incorrectly.
2012alternate content source refresh fails with json serialization 
error
2031possible incorrect URL param parsing by streamer
  RPM Support
2048Errata update failure during sync or upload
1949re-publish takes longer than expected
2032pulp sets reboot_suggested to True for all errata when syncing 
from published repo

View the full list in Redmine:
http://bit.ly/29vs1bE



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9 Release Candidate Now Available

[Sean Myers]

The Pulp 2.9 Release Candidate is now available, and can be downloaded from
the 2.9 beta repositories:

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

This release includes many new features, as well as bug fixes. Owing to the more
rapid time-based release of 2.9, this release should consist of fewer new
features compared to the release of 2.8. Try out the new features, and let us
know how they work for you!

This release was slightly delayed by two blocking issues (2035 and 2037, seen 
below)
which were fixed in Beta 2. Barring more blockers discovered in this cycle, the 
2.9
release should be available next Tuesday (July 12).

More information about our release schedule can be found on the Pulp wiki:
https://pulp.plan.io/projects/pulp/wiki/Release_Schedule


Upgrading
=

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

After enabling the 2.9 beta repositories, you'll want to follow the standard
upgrade path, with migrations, to get to 2.9:

> $ 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


New Features


New features for Pulp 2.9 include optimizations in publishing, repoview support
for yum repos, langpacks support for yum repos, and more:

  Pulp
1724Publish should be a no-op if no units and no settings have 
changed since the last successful publish

  RPM Support
1976As user, I can specify directory where all rpms will be 
published
1716As a user, I can have better memory performance on Publish by 
using SAX instead of etree for comps and updateinfo XML production
1543As a user, I would like incremental export to be the same 
format as full export
1367comps langpacks support
1158As a user, I can force full/fresh publish of rpms and not do an 
incremental publish
1003As a user, I can use pulp-admin to upload of package_environment
189 Repoview-like functionality for browsing repositories via the 
web interface

View this list in redmine:
http://bit.ly/1XXtIps

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.9/testing/user-guide/release-notes/2.9.x.html
http://docs.pulpproject.org/en/2.9/testing/plugins/pulp_rpm/user-guide/release-notes/2.9.x.html


Issues Addressed


All bug fixes from Pulp 2.8.5 and earlier are included in Pulp 2.9.

Here are the bug fixes specific to 2.9:

  Pulp
2015rpm repo publish fails with "Incorrect length of data produced" 
error
1928Publish should be operational if override config values were 
specified
1844pulp-admin --config and/or api_prefix option appears to be 
ignored
  RPM Support
2037Migration failing after 2.9 upgrade
2035Errata are published incrementally
2001Make sure sqlite files are generated if repoview is enabled
1969as user, I can export a repo with a specified checksum type
1938force_full is not supported by export_distributor
1876Add example on how to generate PULP_MANIFEST file
1787None in comps.xml
1619as user, I can export repo groups with different checksum than 
sha256
1618--checksum-type is broken

View this list in redmine:
http://bit.ly/1Q5bSOs



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9 Beta 2 Released

[Sean Myers]

Pulp 2.9 Beta 2 is now available, and can be downloaded from
the 2.9 beta repositories:

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

This release includes many new features, as well as bug fixes. Owing to the more
rapid, time-based release of 2.9, this release should consist of fewer new
features compared to the release of 2.8. Try out the new features, and let us
know how they work for you!

This beta release was slightly delayed by two blocking issues (2035 and 2037,
seen below); barring more blockers discovered in this beta cycle, the 2.9 
release
candidate should be available next Tuesday (July 5).

Upgrading
=

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

After enabling the 2.9 beta repositories, you'll want to follow the standard
upgrade path, with migrations, to get to 2.9:

> $ 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

New Features


New features for Pulp 2.9 include optimizations in publishing, repoview support
for yum repos, langpacks support for yum repos, and more:

  Pulp
1724Publish should be a no-op if no units and no settings have 
changed since the last successful publish

  RPM Support
1976As user, I can specify directory where all rpms will be 
published
1716As a user, I can have better memory performance on Publish by 
using SAX instead of etree for comps and updateinfo XML production
1543As a user, I would like incremental export to be the same 
format as full export
1367comps langpacks support
1158As a user, I can force full/fresh publish of rpms and not do an 
incremental publish
1003As a user, I can use pulp-admin to upload of package_environment
189 Repoview-like functionality for browsing repositories via the 
web interface

View this list in redmine:
http://bit.ly/1XXtIps

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.9/testing/user-guide/release-notes/2.9.x.html
http://docs.pulpproject.org/en/2.9/testing/plugins/pulp_rpm/user-guide/release-notes/2.9.x.html


Issues Addressed


All bug fixes from Pulp 2.8 and earlier are included in Pulp 2.9.

Here are the bug fixes specific to 2.9:

  Pulp
2015rpm repo publish fails with "Incorrect length of data produced" 
error
1928Publish should be operational if override config values were 
specified
1844pulp-admin --config and/or api_prefix option appears to be 
ignored
  RPM Support
2037Migration failing after 2.9 upgrade
2035Errata are published incrementally
2001Make sure sqlite files are generated if repoview is enabled
1969as user, I can export a repo with a specified checksum type
1938force_full is not supported by export_distributor
1876Add example on how to generate PULP_MANIFEST file
1787None in comps.xml
1619as user, I can export repo groups with different checksum than 
sha256
1618--checksum-type is broken

View this list in redmine:
http://bit.ly/1Q5bSOs





signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.5 Released with Security and bug fixes!

[Sean Myers]

Pulp 2.8.5 is now available in the stable repositories:

https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.8/

This release addresses two identified Pulp platform security flaws,
and also includes bugfixes for the Pulp platform and all supported plugins.


Upgrading
=

User action is required to address the CVEs associated with this upgrade!

Included in the list of :fixedbugs:`2.8.4` are two CVEs:

CVE-2016-3696: Leakage of CA key in pulp-qpid-ssl-cfg
CVE-2016-3704: Unsafe use of bash $RANDOM for NSS DB password and seed


Upgrade instructions


The CVEs require user interaction to remedy if you have been using qpid, and if
you used pulp-qpid-ssl-cfg to generate the TLS keys. Rabbit users and users who
generated their own keys for qpidd are not affected by these CVEs.

Begin by upgrading to Pulp 2.8.4 and running migrations:

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

Note: You don't need to restart goferd if goferd isn't installed.

Any qpidd CA, server and client certificate and key pairs that were generated 
with
pulp-qpid-ssl-cfg are unsafe and should be replaced. After upgrading to 2.8.4
(as we did above), you can use the script to replace the certificates and keys:

> $ sudo pulp-qpid-ssl-cfg

Now we are ready to start the services again:

> $ sudo systemctl start qpidd httpd pulp_workers pulp_resource_manager 
> pulp_celerybeat goferd


Issues Addressed


  Crane
1958uninstall causes POSTUN script failure
  Docker Support
1994Docker v1 links missed by 0002 (storage path) migration.
1909Repository syncs fail
1831sync of non-existing repo does not report an error
1646It is theoretically possible for a v2 sync to enter an infinite 
recursion loop
1644Users cannot download Blobs in parallel
  Nectar
1820Fix checking for config.proxy_username
1372Nectar logging is vague when a certificate is untrusted.
  OSTree Support
1934OSTree syncs are broken
  Pulp
1937Syncing a puppet module with the same content as a different 
repo results in no content
1923POST /pulp/api/v2/content/actions/delete_orphans/ is broken
1890pulp-qpid-ssl-cfg echoes the NSS DB password
1858CVE-2016-3704: Unsafe use of bash $RANDOM for NSS DB password 
and seed
1854CVE-2016-3696 Leakage of CA key in pulp-qpid-ssl-cfg
1712Our packages that depend on pulp-selinux do not Require: that 
package in our spec file
1113If an instance of pulp_celerybeat dies unexpectedly, Pulp 
incorrectly tries to "cancel all tasks in its queue"
  Puppet Support
1950module upload fails with IOError: [Errno 2] No such file or 
directory
1880PLP: Update failed (The dotted field 
'thomasmckay-rsync-0.4.1-thomasmckay'
1879Incorrect name when syncing puppet module from the filesystem
  Python Support
1973Repo symlinks are not removed after repository delete
  RPM Support
2007Errata install API should expect 'id' as part of unit key
1979metadata unit copy action creates incorrect unit count on repo
1972migration 28 misses distribution symlinks
1955Need a migration to ensure that Distribution units have a 
default value of '' for variant.
1954The distribution storage path migration fails when variant is 
not in the document.
1944YumMetadataFile copy does not save its new storage_path
1910Errata update fails when id of the repo is added to the 
existing collection
1901Fix error handling during the erratum update
1897catalog entries not created for pre-existing units
1895Recursive RPM unit copies are not recursive
1775Content removed from a repository never returns
1462Errata Install to Content Host takes too long and doesn't scale 
well
1288warning log level for "Overwriting existing metadata file" is 
misleading
858 As a user, I would like to receive updated errata metadata

View this list in redmine: http://bit.ly/267OC6f



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Missing distribution files after 2.5 -> 2.8.4 upgrade

[Sean Myers]

On 06/22/2016 09:20 AM, Baird, Josh wrote:
> Does it sound like I may hitting this bug [1]?  If so, will it be fixed in 
> 2.8.5?

Assuming you meant to link to https://pulp.plan.io/issues/1972: I think so, and 
yes.

The 2.8.5 beta is available now if you're able to test it out:
https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.8/



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.9 Beta 1 Released

[Sean Myers]

Pulp 2.9 Beta 1 is now available, and can be downloaded from
the 2.9 beta repositories:

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

This release includes many new features, as well as bug fixes. Owing to the more
rapid, time-based release of 2.9, this release should consist of fewer new
features compared to the release of 2.8. Try out the new features, and let us
know how they work for you!


Upgrading
=

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

After enabling the 2.9 beta repositories, you'll want to follow the standard
upgrade path, with migrations, to get to 2.9:

> $ 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


New Features


New features for Pulp 2.9 include optimizations in publishing, repoview support
for yum repos, langpacks support for yum repos, and more:

  Pulp
1724Publish should be a no-op if no units and no settings have 
changed since the last successful publish

  RPM Support
1976As user, I can specify directory where all rpms will be 
published
1716As a user, I can have better memory performance on Publish by 
using SAX instead of etree for comps and updateinfo XML production
1543As a user, I would like incremental export to be the same 
format as full export
1367comps langpacks support
1158As a user, I can force full/fresh publish of rpms and not do an 
incremental publish
1003As a user, I can use pulp-admin to upload of package_environment
189 Repoview-like functionality for browsing repositories via the 
web interface


View this list in redmine:
http://bit.ly/1XXtIps

More information about these new features can be found in the release notes:
http://docs.pulpproject.org/en/2.9/nightly/user-guide/release-notes/2.9.x.html
http://docs.pulpproject.org/en/2.9/nightly/plugins/pulp_rpm/user-guide/release-notes/2.9.x.html


Issues Addressed


All bug fixes from Pulp 2.8 and earlier are included in Pulp 2.9.

Here are the bug fixes specific to 2.9:

  Pulp
2015rpm repo publish fails with "Incorrect length of data produced" 
error
1928Publish should be operational if override config values were 
specified
1844pulp-admin --config and/or api_prefix option appears to be 
ignored

  RPM Support
2001Make sure sqlite files are generated if repoview is enabled
1938force_full is not supported by export_distributor
1876Add example on how to generate PULP_MANIFEST file
1787None in comps.xml
1618--checksum-type is broken

View this list in redmine:
http://bit.ly/1Q5bSOs



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] [devel] Create a `devel` repository for Pulp

[Sean Myers]

On 06/20/2016 01:49 PM, Jeremy Cline wrote:
> Hi all,
> 
> Currently, we have development-related files and packages spread out
> across our Git repositories on GitHub. It would be nice if it was all
> part of one repository for developers. This would include things like:
> 
>  * The Vagrantfile currently in pulp/pulp
>  * The devel Python packages currently in each repo
>  * Release engineering tooling currently in pulp/pulp
>  * Jenkins jobs definitions currently in pulp/pulp_packaging
>  * Ansible playbooks currently in pulp/pulp and pulp/pulp_packaging
>  * Various tools and scripts living in "playpens"
> 
> It might also be worth breaking out our Ansible roles into their own
> `ansible` repository. Right now we have _two_ sets of Ansible roles
> (one in pulp/pulp and on in pulp/pulp_packaging).
> 
> What do you all think?

Yes. I'm also happy to see the ansible books live in devel since they're 
primarly
used by vagrant and CI, which would both live in devel, and you can't do either
without one or the ansible playbooks.

+1 for 'devel' and not 'pulp_devel', I still sometimes think that we have a
'packaging' plugin because of the 'pulp_packaging' repo name.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.5 Beta Released with Security and bug fixes

[Sean Myers]

Pulp 2.8.5 Beta 1 is now available in the beta repositories:

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

This release addresses two identified Pulp platform security flaws,
and also includes bugfixes for the Pulp platform and all supported plugins.


Upgrading
=

User action is required to address the CVEs associated with this upgrade!

Included in the list of :fixedbugs:`2.8.4` are two CVEs:

CVE-2016-3696: Leakage of CA key in pulp-qpid-ssl-cfg
CVE-2016-3704: Unsafe use of bash $RANDOM for NSS DB password and seed


Upgrade instructions


The CVEs require user interaction to remedy if you have been using qpid, and if
you used pulp-qpid-ssl-cfg to generate the TLS keys. Rabbit users and users who
generated their own keys for qpidd are not affected by these CVEs.

Begin by upgrading to Pulp 2.8.4 and running migrations:

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

Note: You don't need to restart goferd if goferd isn't installed.

Any qpidd CA, server and client certificate and key pairs that were generated 
with
pulp-qpid-ssl-cfg are unsafe and should be replaced. After upgrading to 2.8.4
(as we did above), you can use the script to replace the certificates and keys:

> $ sudo pulp-qpid-ssl-cfg

Now we are ready to start the services again:

> $ sudo systemctl start qpidd httpd pulp_workers pulp_resource_manager 
> pulp_celerybeat goferd


Issues Addressed


  Crane
1958uninstall causes POSTUN script failure
  Docker Support
1994Docker v1 links missed by 0002 (storage path) migration.
1831sync of non-existing repo does not report an error
1644Users cannot download Blobs in parallel
1646It is theoretically possible for a v2 sync to enter an infinite 
recursion loop
1909Repository syncs fail
  Nectar
1372Nectar logging is vague when a certificate is untrusted.
1820Fix checking for config.proxy_username
  OSTree Support
1934OSTree syncs are broken
  Pulp
1923POST /pulp/api/v2/content/actions/delete_orphans/ is broken
1854CVE-2016-3696 Leakage of CA key in pulp-qpid-ssl-cfg
1712Our packages that depend on pulp-selinux do not Require: that 
package in our spec file
1858CVE-2016-3704: Unsafe use of bash $RANDOM for NSS DB password 
and seed
1890pulp-qpid-ssl-cfg echoes the NSS DB password
1937Syncing a puppet module with the same content as a different 
repo results in no content
1113If an instance of pulp_celerybeat dies unexpectedly, Pulp 
incorrectly tries to "cancel all tasks in its queue"
  Puppet Support
1950module upload fails with IOError: [Errno 2] No such file or 
directory
1879Incorrect name when syncing puppet module from the filesystem
1880PLP: Update failed (The dotted field 
'thomasmckay-rsync-0.4.1-thomasmckay'
  Python Support
1973Repo symlinks are not removed after repository delete
  RPM Support
1944YumMetadataFile copy does not save its new storage_path
1954The distribution storage path migration fails when variant is 
not in the document.
2007Errata install API should expect 'id' as part of unit key
1895Recursive RPM unit copies are not recursive
1897catalog entries not created for pre-existing units
858 As a user, I would like to receive updated errata metadata
1462Errata Install to Content Host takes too long and doesn't scale 
well
1955Need a migration to ensure that Distribution units have a 
default value of '' for variant.
1972migration 28 misses distribution symlinks
1775Content removed from a repository never returns
1979metadata unit copy action creates incorrect unit count on repo
1901Fix error handling during the erratum update
1910Errata update fails when id of the repo is added to the 
existing collection
1288warning log level for "Overwriting existing metadata file" is 
misleading
1783figure out how we want to test collections and package lists in 
errata advisories



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] 2.9 Beta Release Delays

[Sean Myers]

On 06/14/2016 03:23 PM, Sean Myers wrote:
> Our release process includes a fair bit of automated testing. At the
> moment, our testing environment is suffering a major outage. Given how long
> it takes to test a build and my avilability going into this evening, I think
> it's pretty unlikely that I'll be able to get the release out today. I've
> expect that this outage will be resolved today, so we should see the
> 2.9 beta release tomorrow.

The outage was resolved last night, but in testing we've discovered a new issue
that blocks the release of the 2.9 beta:

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

This regression does not appear to affect the 2.8 stream, but we're still 
looking
into it to make sure the fix lands in the correct place for all affected 
releases.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] 2.9 Beta Release Delays

[Sean Myers]

Our release process includes a fair bit of automated testing. At the
moment, our testing environment is suffering a major outage. Given how long
it takes to test a build and my avilability going into this evening, I think
it's pretty unlikely that I'll be able to get the release out today. I've
expect that this outage will be resolved today, so we should see the
2.9 beta release tomorrow.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] 2.9-dev branch is open

[Sean Myers]

With the 2.9 beta being built today, I have created the 2.9-dev
branches for pulp, pulp_rpm, and pulp_puppet. Any PRs open against
master most likely should remain open against master. Any PRs merged
to 2.8-dev should be merged forward to 2.9-dev before going
to master. Any new bugfixes that only apply to 2.9 should be opened
against 2.9-dev.

If you have an open PR and need help knowing where to merge it, let
me know and I can help you out.

Git merge strategy summary:

New features merge to master
2.9 bug fixes merge to 2.9-dev and merge forward to master
2.8 bug fixes merge to 2.8-dev, merge forward to 2.9-dev,
  which gets merged forward to master




signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] 2.9 branch at freeze?

[Sean Myers]

Traditionally, we've created the x.y-dev branch after the corresponding
pulp version is released. I was thinking it would be good to create that
branch at the freeze point (pretty much right now) rather than waiting.

Open PRs against master would have to be dealt with specially, but I think
we can avoid mass-closing PRs with some git-merge-fu, since presumably anything
already POSTed can be manually merged backward cleanly to the new dev branch,
and then merged forward normally to close the PR. I'm happy to help with this
if we do go ahead and create the dev branch now.

So, is it branch time?



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp 2.8.4 Hotfix Released

[Sean Myers]

On 06/06/2016 06:32 PM, Kodiak Firesmith wrote:
> Apologies if this is a silly question:  Can I hop from 2.8.2 -> 2.8.4, this
> skipping the problems I reported in #1945?  Or do I need to roll 2.8.2 ->
> 2.8.3 -> pulp-manage-db -> 2.8.4 -> pulp-manage-db?

2.8.2 -> pulp-manage-db -> 2.8.4 should work, and upgrading from 2.8.3
should also work. Either way, you definitely want to run migrations once
2.8.4 is installed before restarting the services.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Q on 2.8.3 -> 2.8.4 server update and noticed I was missing goferd

[Sean Myers]

On 06/06/2016 04:28 PM, James Davis wrote:
> I started with a clean server install on CenOS7 with 2.8.3 and one client to 
> test. Works ok when "yum update" is run on the client.
> 
> I noticed the 2.8.4 hotfix was available. I read the release notes and ran 
> the stop and noticed that I didn't have goferd running - or installed. I 
> can't find anywhere where that is required to be installed by hand or 
> installed by dependency on a pulp server - only on the consumer. Is that an 
> artifact of older server releases or what? The db migration ran without 
> errors and I restarted everything.
> 
> The only thing I haven't tried yet is pushing content from the server.

That's entirely correct; I apologize for being unclear about that in the 
release notes.

You definitely do need to stop all the other services (httpd, pulp_workers,
pulp_resource_manager, pulp_celerybeat) before updating, but if you don't have 
goferd
installed because you aren't running a consumer alongside the pulp server, 
that's fine,
and you can leave it out when stopping and starting services for an upgrade.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.4 Hotfix Released

[Sean Myers]

2.8.4 is a *hotfix* release, and has been pushed to the 2.8 stable repositories:

https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.8/

Due to migration failures discovered after the release of Pulp 2.8.3, Pulp 
2.8.4 is a
hotfix release to address these migration issues.

Follow the 2.8.3 release notes to upgrade:

https://pulp.readthedocs.io/en/latest/user-guide/release-notes/2.8.x.html#pulp-2-8-3

If you have already addressed the security issues fixed in 2.8.3 after 
upgrading to 2.8.3,
then only the first section of the upgrade instructions is needed:

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


Issues Addressed


The following issues address migration failures in the Pulp platform and 
pulp_rpm plugins:

1929The 0023_importer_tls_storage.py migration assumes that Importers 
always have configs when they do not
1931FieldDoesNotExist: The field '_rpm_references' does not exist on the 
document 'Errata'
1945pulp 2.8.3 migration fails on unit 0028
1952Repo sync fails after upgrade to 2.8.3.

You can view this list in Redmine: http://bit.ly/1OPWob4


Puppet Plugin Version
=

The pulp_puppet plugin has had its version incremented to conform to the 
platform release
version, but no changes have been made to its functionality; it is built 
directly from
the 2.8.3-1 release tag.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.4 Hotfix Beta Released

[Sean Myers]

2.8.4 is now a *hotfix* release. Beta 2 has been pushed to the 2.8 repositories:

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

Due to migration failures discovered after the release of Pulp 2.8.3, the 
previously
announced 2.8.4 Beta release (Beta 1) has been preempted by a hotfix release to 
address
these migration issues. All other issues that were being addressed in 2.8.4 
have been
moved to 2.8.5; Beta 2 only addresses critical migration failures.

Given the narrow scope of this fix and the severity of broken migrations, our 
plan is
to make this hotfix Generally Available as quickly as we can.


Issues Addressed


The following issues address migration failures in the Pulp platform and 
pulp_rpm plugins:

1929The 0023_importer_tls_storage.py migration assumes that Importers 
always have configs when they do not
1931FieldDoesNotExist: The field '_rpm_references' does not exist on the 
document 'Errata'
1945pulp 2.8.3 migration fails on unit 0028
1952Repo sync fails after upgrade to 2.8.3.

You can view this list in Redmine: http://bit.ly/1OPWob4


Puppet Plugin Version
=

The pulp_puppet plugin has had its version incremented to conform to the 
platform release
version, but no changes have been made to its functionality; it is built 
directly from
the 2.8.3-1 release tag.


Docker Plugin Version
=

This release does not address my incorrectly built version of the docker plugin,
but no special handling of that case should be needed for this release since
my error was to re-build the latest released version of the docker plugin,
making the current release (2.0.1) functionally identical to the erroneously-
released beta of docker (2.0.2 beta 1). Users that have already installed 2.8.4
beta 1 may still be running the beta version of docker after upgrading to 2.8.4
beta 2. If issues *do* arise as a result of the docker plugin version increment,
I recommend testing the 2.8.4 beta upgrade on a system running Pulp 2.8.3 or 
older,
and not upgrading to 2.8.4 beta 1 from 2.8.4 beta 2.

This will be corrected in the next release of the docker plugin, which should be
be coming along with pulp 2.8.5.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp 2.8.4 Beta Released - Security and Bug fixes

[Sean Myers]

On 05/26/2016 04:05 PM, Sean Myers wrote:
> 2.8.4 is a security and bugfix release. Beta 1 has been pushed to the 2.8 
> repositories
> 

I built the pulp_docker plugin incorrectly. The code released with Pulp 2.8.4 
beta 1 for
pulp_docker 2.0.2 beta 1 is functionally identical to the pulp_docker 2.0.1 
release.

We've got a holiday in the US (my geo) on Monday, so I'll be building 2.8.4 
beta 2 to
include the correct bits for pulp_docker 2.0.2 next Tuesday.

Only the docker plugin is affected by this error.

My apologies, and have a good weekend!



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.4 Beta Released - Security and Bug fixes

[Sean Myers]

2.8.4 is a security and bugfix release. Beta 1 has been pushed to the 2.8 
repositories:

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

User action is required to address the CVEs associated with this upgrade!
Read the upgrade instructions below.

This release includes bug fixes to the Pulp platform, as well as its
RPM, Puppet, and Docker plugins.

Security Issues Addressed
=

Included in the list of :fixedbugs:`2.8.4` are two CVEs:

* `CVE-2016-3696 `_: Leakage of CA key in 
pulp-qpid-ssl-cfg
* `CVE-2016-3704 `_: Unsafe use of bash 
$RANDOM for NSS DB
  password and seed

Upgrade instructions


The CVEs require user interaction to remedy if you have been using qpid, and if 
you used
``pulp-qpid-ssl-cfg`` to generate the TLS keys. Rabbit users and users who 
generated their own keys
for qpidd are not affected by these CVEs. Begin by upgrading to Pulp 2.8.4 and 
running migrations::

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

Any qpidd CA, server and client certificate and key pairs that were generated 
with
``pulp-qpid-ssl-cfg`` are unsafe and should be replaced. After upgrading to 
2.8.4 (as we did above),
you can use the script to replace the certificates and keys::

$ sudo pulp-qpid-ssl-cfg

Now we are ready to start the services again::

$ sudo systemctl start qpidd httpd pulp_workers pulp_resource_manager 
pulp_celerybeat goferd

Issues Addressed


  Docker Support
1909Repository syncs fail
1831sync of non-existing repo does not report an error
1646It is theoretically possible for a v2 sync to enter an infinite 
recursion loop
1644Users cannot download Blobs in parallel
  Nectar
1820Fix checking for config.proxy_username
  Pulp
1929The 0023_importer_tls_storage.py migration assumes that 
Importers always have configs when they do not
1858CVE-2016-3704: Unsafe use of bash $RANDOM for NSS DB password 
and seed
1854CVE-2016-3696 Leakage of CA key in pulp-qpid-ssl-cfg
  Puppet Support
1880PLP: Update failed (The dotted field 
'thomasmckay-rsync-0.4.1-thomasmckay'
1879Incorrect name when syncing puppet module from the filesystem
  RPM Support
1910Errata update fails when id of the repo is added to the 
existing collection
1895Recursive RPM unit copies are not recursive
1775Content removed from a repository never returns
1462Errata Install to Content Host takes too long and doesn't scale 
well
858 As a user, I would like to receive updated errata metadata

You can view these results in Redmine here:

http://bit.ly/1OPWob4

Notable Dependency Updates
==

The nectar dependency has been upgraded to include a fix listed above, #1820.

This fix was erroneously listed in the Pulp 2.8.3 Release Notes, and is actually
included with the 2.8.4 release.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Process Change: No Release Candidate for Bugflix Releases

[Sean Myers]

For bugfix releases (also known as "z" releases due to the incrementing
of the number in the "x.y.z" version representation), we're changing the
process slightly, as indicated in the subject of this mail.

The current process is to release a Beta for testing, and if no blocking
bugs are found in a week, it is promoted to Release Candidate (RC). The
release then sits at Release Candidate for a week before becoming Generally
Available (GA). The process change is that with the next bugfix release,
2.8.4, instead of promoting the Beta release to RC, it will be promoted
directly to GA, which removes a week from the bugfix release cycle timeline,
allowing bugfix releases to happen more frequently.

"y" releases like 2.9, 2.10, etc. are not affected by this process change,
and still include a Release Candidate stage.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Jenkies pull request test failures on platform and plugins

[Sean Myers]

These appear to be environmental and not the same on every platform,
possibly related to the switch to the newer base images for jenkies
slave runners. I don't have anything really useful to add at this
point, but wanted to just at least let you all know that I'm working
on it as of this afternoon, and will update here when it's all sorted
out.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.3 Released - Security & Bug fixes

[Sean Myers]

Pulp 2.8.3 is now available!

Pulp has been updated, along with the Puppet (pulp_puppet) and RPM (pulp_rpm) 
plugins.

This release also includes updates for OSTree plugin (pulp_ostree) version
1.1.1, the Docker plugin (pulp_docker) version 2.0.1, and the Python plugin
(pulp_python) version 1.1.1.

The release is available in the pulp beta repository for 2.8:
https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.8/

Migrations will need to be run for this release. See the Upgrade Instructions
below for more details.


Security Issues Addressed
=

CVE-2016-3111 (Low Impact):
pulp.spec generates its RSA keys for message signing insecurely
https://pulp.plan.io/issues/1837

CVE-2016-3112 (Moderate Impact):
Pulp consumer private keys are world-readable
https://pulp.plan.io/issues/1834

CVE-2016-3107 (Moderate Impact):
Node certificate containing private key stored in world-readable file
https://pulp.plan.io/issues/1833

CVE-2016-3108 (Moderate Impact):
Insecure temporary file used when generating certificate for Pulp Nodes
https://pulp.plan.io/issues/1830

CVE-2016-3106 (Low Impact):
Insecure creation of temporary directory when generating new CA key
https://pulp.plan.io/issues/1827

Additionally, CVE-2013-7450 was announced during this release cycle, even 
though it was fixed in Pulp 2.3.0. Users who have upgraded from Pulp < 2.3.0 
may still be vulnerable, action may be required (see below).
https://bugzilla.redhat.com/show_bug.cgi?id=1003326

See the upgrade instructions below for more information on addressing these
vulnerabilities.


Known Issues


Changes to the squid package in fedora 22 are causing selinux denials to 
prevent squid
from starting on systems using pulp's lazy download features. At this time, all 
other
platforms appear to be working normally: only fedora 22 is affected.

This issue is being tracked in our tracker. Links to upstream issues and 
workarounds
can be found there:

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


Issues Addressed


  Docker Support
1818Add migration - content units to standard storage path.
  Nectar
1820Fix checking for config.proxy_username
  OSTree Support
1106relative_path should be checked for url collision
  Pulp
1576content type mongo id searches not working
1764SELinux denial on Celery attempting to read resolv.conf
1771requests or urllib3 can't read a file which causes Nectar to 
fail mysteriously
1801Pulp celery_beat and resource_manager are running, but logs say 
they are not running
1802Pulp 2.8 client no longer supports sha1 RPM checksum type
1809python 2.6 incompatibility during set_importer
1747Import upload task has unexpected/missing information on error
1784regression: "pulp-admin rpm repo search" with filters does not 
work as expected
1834CVE-2016-3112: Pulp consumer private keys are world-readable
1837CVE-2016-3111: pulp.spec generates its RSA keys for message 
signing insecurely
1791After upgrading from 2.7.1 to pulp 2.8.0 getting 403 error's on 
all my Pulp repo's.
1794A Pulp unit test is failing to find a certificate to be valid
1824iso repo publish fails for file in subdirectories
1827CVE-2016-3106: Insecure creation of temporary directory when 
generating new CA key
1830CVE-2016-3108: Insecure temporary file used when generating 
certificate for Pulp Nodes
1833CVE-2016-3107: Node certificate containing private key stored 
in world-readable file
1601Migrate /var/lib/pulp/content to new 2.8 storage paths.
1815Create a common 2.8 storage path migration to be used by plugins
  Puppet Support
1780PLP: Update failed (The dotted field 
'thomasmckay-rsync-0.4.1-thomasmckay'
1817Add migration - content units to standard storage path.
  Python Support
1855Upload broken
1819Add migration - content units to standard storage path.
  RPM Support
1869Resynchronizing rhel repos seems to be failing after upgrade
1768Unable to sync RHEL 5 repositories with a distribution
1792recursive and depsolving unit copy results in 
PulpExecutionException
1843Pulp publishes invalid PULP_DISTRIBUTION.xml metadata
1778Switching a repository to immediate from on_demand doesn't 
download its packages
1828pulp doesn't sync reference title correctly from errata
1835export fails when units are not downloaded
1782None in generated XML for 
unit with no 'reboot_suggested'
1808exporting a sufficiently large repo with 'on_demand' policy 
results in BSON error
1812Comps.xml upload succeeds but units are not associated to the 
repo.
1813Handle duplicate key error in comps.xml upload
1856publishing ki

Re: [Pulp-list] Pulp 3.0 Technology Stack Justifications

[Sean Myers]

Based on the feedback so far, I haven't seen any issues with what
I've proposed here other than elasticsearch. I'll be digging into
that piece of the stack and revaluating the options out there,
taking the feedback from this thread into account.

Thanks!



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Bug Inquisition?

[Sean Myers]

We have a lot of open bugs that can probably be closed; either
they've already been fixed or they no longer apply to the
current version of pulp. To help deal with this, a monthly meeting
has been proposed to "triage" old bugs. Before considering a
re-triage of these old bugs, it seems like it might be useful to
do an "inquisition" (credit to mhrivnak for the term) and closing
out bugs that are obviously no longer useful.

Unfortunately, there are 970 open bugs in Redmine at the time
I'm writing this, so even if we commit to doing 100 bugs in one
of these monthly sessions, it'll be 10 months before we've gotten
through that backlog, and new bugs will be coming in all the while.

I think it's a really good idea to go through all of these, but we
need to come up with a sort of litmus test to Yea/Nay the closing
of issues that we can apply to our backlog to make cleaning these
issues out less painful. Unfortunately, after looking at this for
a little while, nothing is really popping out at me as a way to
make the process easy, or easy to distribute.

Any ideas?



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Pulp 3.0 Technology Stack Justifications

[Sean Myers]

On 05/12/2016 02:09 PM, Eric Helms wrote:
> Can you expand on why a separate search service is needed and how Postgres
> won't fill your needs?

Unfortunately, Django itself doesn't meet our needs for search when using
postgres as the DB.

To get it, we've got to go out to a plugin. The plugins available for this 
are pretty slim pickings, and haystack stands out as the best option among 
them. Since Django's our interface to the DB, we'd have to bolt on our own 
search functionality to make the DB do this work.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 3.0 Technology Stack Justifications

[Sean Myers]

Early planning for Pulp 3.0 is building up some steam, and it's
a good time to go over the proposed technology stack that we're
looking at right now that we're looking at to build on. For all
of these choices, once Pulp's basic needs are met, the major
deciding factor for what library to use is decided by "meta"
factors, like community support, release processes, etc. Special
thanks to Jeff Ortel for making sure my assumptions about these
tools got challenged so the right choices get made.

We're using postgres as the DB for 3.0. Since we're going
relational, the next thing we'd want is a good ORM. Several team
members have experience with the Django ORM, and Pulp is actually
already using it in its views. It has a fantastic community, is
well documented, and comes with a vast multitude of third-party
plugins to help us fill in any gaps in functionality that may be
found. Our current tasking system is build on Celery[0], which is
among those third-party plugins with excellent Django support,
which potentially means that using Django with a relational DB
can help us get rid of code where we overlap functionality that
may be provided by django-celery.

Other ORM options were considered, but only SQLAlchemy (another
very good ORM) stood out as something we could use if there was
a compelling reason to switch from Django, but at this time there
is no such reason. Django does the job well. Most other ORMs are
either not robust enough in their feature-set or apparently not
being actively maintained, and were rejected as alternatives.
Also rejected outright was not using an ORM (or other form of
data mapper) at all, since my sense is that we all agree that
we don't want to manually be writing SQL. :)

This leads to the next big building block, which is the tool we
should use to build our REST APIs. I've used django-tastypie in
the past, as have a few other team members, and it was my front-
runner for this job. After looking around though, it looks like
django-rest-framework (DRF) is currently dominating this space
in the Django community[0]. Going through some of their tutorials
and examples, it's looking like tastypie is out of the running,
and DRF is the winner. Both would be adequate for Pulp's needs
when it comes to putting a REST API on top of our data model, so
it makes sense to go with the more "popular" option. In addition,
I think its documentation and API are easier to work with than
tastypie's, so it's simultaneously easier to use and easier to
*learn how* to use.

Finally, we're looking at bringing in a search engine for the 
search views in the API. We're currently doing search using
mongodb, using mongo-specific search criteria, but will be
decoupling the search API from the search engine. As with Django,
a few team members have experience using elasticsearch (myself
included). Elasticsearch is java-based, running on top of the
Lucene indexer, with a simple REST API on top of it, and so at
the moment it's my preferred search engine.

I looked at a few other search engines in recent testing, including
the pure-python engine "Whoosh", Solr (also uses lucene), Xapian,
and Sphinx (the search engine, not the document builder). Of these,
only Whoosh and Elasticsearch have first-party support by the
django-haystack project[2], which is both my preferred and the most
commonly used django search plugin[3]. Given my previous positive
experience with Elasticsearch, I think it's probably the best choice
for a search indexer at this time.

The Whoosh plugin for Haystack currently doesn't support a very
useful feature that Whoosh itself does support, which is faceting.
This feature gap is something that would need to be closed (likely
by us) to get feature parity between the elasticsearch and whoosh
backends.

While there are other libraries that appear to live in the same space
as haystack (integrate a search indexer with Django models, providing
Django QuerySet/Model results), none of them have the robust features
and community support seen in haystack. Again, though, decoupling the
search interface from the search implementation means that this piece
is likely to be easy to change out if we find better options in the
future (especially if we write it with this in mind).

Summary:
- Django ORM on postgres
- django-rest-Framework to build API views
- django-haystack to provide search capabilities, using Elasticsearch
  to start, possible switching to Whoosh after some development -- this
  switch should occur before any release of 3.0

[0]: http://docs.celeryproject.org/en/latest/django/
[1]: https://www.djangopackages.com/grids/g/rest/
[2]: http://django-haystack.readthedocs.io/en/stable/backend_support.html
[3]: https://www.djangopackages.com/grids/g/search/



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.3 Release Candidate - Security & Bug fixes

[Sean Myers]

The release candidate for Pulp 2.8.3 is now available.

Pulp has been updated, along with the Puppet (pulp_puppet) and RPM (pulp_rpm) 
plugins.

This release also includes candidatess for OSTree plugin (pulp_ostree) version
1.1.1, the Docker plugin (pulp_docker) version 2.0.1, and the Python plugin
(pulp_python) version 1.1.1.

The release is available in the pulp beta repository for 2.8:
https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.8/

Migrations will need to be run for this release. See the Upgrade Instructions
below for more details.


Security Issues Addressed
=

CVE-2016-3111 (Low Impact):
pulp.spec generates its RSA keys for message signing insecurely
https://pulp.plan.io/issues/1837

CVE-2016-3112 (Moderate Impact):
Pulp consumer private keys are world-readable
https://pulp.plan.io/issues/1834

CVE-2016-3107 (Moderate Impact):
Node certificate containing private key stored in world-readable file
https://pulp.plan.io/issues/1833

CVE-2016-3108 (Moderate Impact):
Insecure temporary file used when generating certificate for Pulp Nodes
https://pulp.plan.io/issues/1830

CVE-2016-3106 (Low Impact):
Insecure creation of temporary directory when generating new CA key
https://pulp.plan.io/issues/1827

Additionally, CVE-2013-7450 was announced during this release cycle, even 
though it was fixed in Pulp 2.3.0. Users who have upgraded from Pulp < 2.3.0 
may still be vulnerable, action may be required (see below).
https://bugzilla.redhat.com/show_bug.cgi?id=1003326

See the upgrade instructions below for more information on addressing these
vulnerabilities.


Known Issues


Changes to the squid package in fedora 22 are causing selinux denials to 
prevent squid
from starting on systems using pulp's lazy download features. At this time, all 
other
platforms appear to be working normally: only fedora 22 is affected.

This issue is being tracked in our tracker. Links to upstream issues and 
workarounds
can be found there:

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


Issues Addressed


  Docker Support
1818Add migration - content units to standard storage path.
  Nectar
1820Fix checking for config.proxy_username
  OSTree Support
1106relative_path should be checked for url collision
  Pulp
1576content type mongo id searches not working
1764SELinux denial on Celery attempting to read resolv.conf
1771requests or urllib3 can't read a file which causes Nectar to 
fail mysteriously
1801Pulp celery_beat and resource_manager are running, but logs say 
they are not running
1802Pulp 2.8 client no longer supports sha1 RPM checksum type
1809python 2.6 incompatibility during set_importer
1747Import upload task has unexpected/missing information on error
1784regression: "pulp-admin rpm repo search" with filters does not 
work as expected
1834CVE-2016-3112: Pulp consumer private keys are world-readable
1837CVE-2016-3111: pulp.spec generates its RSA keys for message 
signing insecurely
1791After upgrading from 2.7.1 to pulp 2.8.0 getting 403 error's on 
all my Pulp repo's.
1794A Pulp unit test is failing to find a certificate to be valid
1824iso repo publish fails for file in subdirectories
1827CVE-2016-3106: Insecure creation of temporary directory when 
generating new CA key
1830CVE-2016-3108: Insecure temporary file used when generating 
certificate for Pulp Nodes
1833CVE-2016-3107: Node certificate containing private key stored 
in world-readable file
1601Migrate /var/lib/pulp/content to new 2.8 storage paths.
1815Create a common 2.8 storage path migration to be used by plugins
  Puppet Support
1780PLP: Update failed (The dotted field 
'thomasmckay-rsync-0.4.1-thomasmckay'
1817Add migration - content units to standard storage path.
  Python Support
1855Upload broken
1819Add migration - content units to standard storage path.
  RPM Support
1869Resynchronizing rhel repos seems to be failing after upgrade
1768Unable to sync RHEL 5 repositories with a distribution
1792recursive and depsolving unit copy results in 
PulpExecutionException
1843Pulp publishes invalid PULP_DISTRIBUTION.xml metadata
1778Switching a repository to immediate from on_demand doesn't 
download its packages
1828pulp doesn't sync reference title correctly from errata
1835export fails when units are not downloaded
1782None in generated XML for 
unit with no 'reboot_suggested'
1808exporting a sufficiently large repo with 'on_demand' policy 
results in BSON error
1812Comps.xml upload succeeds but units are not associated to the 
repo.
1813Handle duplicate key error in comps.xml upload
 

Re: [Pulp-list] [pulp-internal] scrum status

[Sean Myers]

On 05/06/2016 12:38 PM, Michael Hrivnak wrote:
> Randy sent out this recording link yesterday, but it appears to be showing
> "permission denied". Randy, can you adjust the privacy setting for that
> recording?
> 
> https://redhat.bluejeans.com/m/9Ay6/

Once it is available, I plan to pull it down, convert it to an open format,
and upload it to vimeo unless there are objections to doing so. Once that's
done, I'll write down how I did it somewhere. :)




signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.3 Beta 2 released - Security & Bug fixes

[Sean Myers]

Pulp, along with the Puppet (pulp_puppet) and RPM (pulp_rpm) plugins,
has been updated to 2.8.3, Beta 2.

This release also includes betas for OSTree plugin (pulp_ostree) version
1.1.1, the Docker plugin (pulp_docker) version 2.0.1, and the Python plugin
(pulp_python) version 1.1.1.

The release is available in the pulp beta repository for 2.8:
https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.8/

Migrations will need to be run for this release. See the Upgrade Instructions
below for more details.


Security Issues Addressed
=

CVE-2016-3111 (Low Impact):
pulp.spec generates its RSA keys for message signing insecurely
https://pulp.plan.io/issues/1837

CVE-2016-3112 (Moderate Impact):
Pulp consumer private keys are world-readable
https://pulp.plan.io/issues/1834

CVE-2016-3107 (Moderate Impact):
Node certificate containing private key stored in world-readable file
https://pulp.plan.io/issues/1833

CVE-2016-3108 (Moderate Impact):
Insecure temporary file used when generating certificate for Pulp Nodes
https://pulp.plan.io/issues/1830

CVE-2016-3106 (Low Impact):
Insecure creation of temporary directory when generating new CA key
https://pulp.plan.io/issues/1827

Additionally, CVE-2013-7450 was announced during this release cycle, even 
though it was fixed in Pulp 2.3.0. Users who have upgraded from Pulp < 2.3.0 
may still be vulnerable, action may be required (see below).
https://bugzilla.redhat.com/show_bug.cgi?id=1003326

See the upgrade instructions below for more information on addressing these
vulnerabilities.


Issues Addressed


  Docker Support
1818Add migration - content units to standard storage path.
  Nectar
1820Fix checking for config.proxy_username
  OSTree Support
1106relative_path should be checked for url collision
  Pulp
1576content type mongo id searches not working
1764SELinux denial on Celery attempting to read resolv.conf
1771requests or urllib3 can't read a file which causes Nectar to 
fail mysteriously
1801Pulp celery_beat and resource_manager are running, but logs say 
they are not running
1802Pulp 2.8 client no longer supports sha1 RPM checksum type
1809python 2.6 incompatibility during set_importer
1747Import upload task has unexpected/missing information on error
1784regression: "pulp-admin rpm repo search" with filters does not 
work as expected
1834CVE-2016-3112: Pulp consumer private keys are world-readable
1837CVE-2016-3111: pulp.spec generates its RSA keys for message 
signing insecurely
1791After upgrading from 2.7.1 to pulp 2.8.0 getting 403 error's on 
all my Pulp repo's.
1794A Pulp unit test is failing to find a certificate to be valid
1824iso repo publish fails for file in subdirectories
1827CVE-2016-3106: Insecure creation of temporary directory when 
generating new CA key
1830CVE-2016-3108: Insecure temporary file used when generating 
certificate for Pulp Nodes
1833CVE-2016-3107: Node certificate containing private key stored 
in world-readable file
1601Migrate /var/lib/pulp/content to new 2.8 storage paths.
1815Create a common 2.8 storage path migration to be used by plugins
  Puppet Support
1780PLP: Update failed (The dotted field 
'thomasmckay-rsync-0.4.1-thomasmckay'
1817Add migration - content units to standard storage path.
  Python Support
1855Upload broken
1819Add migration - content units to standard storage path.
  RPM Support
1869Resynchronizing rhel repos seems to be failing after upgrade
1768Unable to sync RHEL 5 repositories with a distribution
1792recursive and depsolving unit copy results in 
PulpExecutionException
1843Pulp publishes invalid PULP_DISTRIBUTION.xml metadata
1778Switching a repository to immediate from on_demand doesn't 
download its packages
1828pulp doesn't sync reference title correctly from errata
1835export fails when units are not downloaded
1782None in generated XML for 
unit with no 'reboot_suggested'
1808exporting a sufficiently large repo with 'on_demand' policy 
results in BSON error
1812Comps.xml upload succeeds but units are not associated to the 
repo.
1813Handle duplicate key error in comps.xml upload
1856publishing kickstart repo fails on EL6
1816Add migration - content units to standard storage path.


Upgrade instructions


Some of the CVEs require user interaction to remedy. Begin by upgrading to  
Pulp 2.8.3, and running migrations:

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

Re: [Pulp-list] Pulp 2.8.3 Beta 1 released - Security & Bug fixes

[Sean Myers]

On 04/25/2016 04:39 AM, Sean Myers wrote:
> The following Security issues were addressed in this release:
> 
> CVE-2016-3111 (Low Impact):
> pulp.spec generates its RSA keys for message signing insecurely
> https://pulp.plan.io/issues/1837
> 
> CVE-2016-3112 (Moderate Impact):
> Pulp consumer private keys are world-readable
> https://pulp.plan.io/issues/1834
> 
> CVE-2016-3107 (Moderate Impact):
> Node certificate containing private key stored in world-readable file
> https://pulp.plan.io/issues/1833
> 
> CVE-2016-3108 (Moderate Impact):
> Insecure temporary file used when generating certificate for Pulp Nodes
> https://pulp.plan.io/issues/1830
> 
> CVE-2016-3106 (Low Impact):
> Insecure creation of temporary directory when generating new CA key
> https://pulp.plan.io/issues/1827
> 
> Details on addressing these vulnerabilities will be released in a
> followup email later today, and included in subsequent release
> announcements for 2.8.3 (apologies for not being able to include
> them in this post).

CVE-2013-7450 (https://bugzilla.redhat.com/show_bug.cgi?id=1003326)
-

Additionally, CVE-2013-7450 was announced during this release cycle, even 
though it was fixed in Pulp 2.3.0. Users who have upgraded from Pulp < 2.3.0 
may still be vulnerable, action may be required (see below).

Upgrade instructions


Some of the CVEs require user interaction to remedy. Begin by upgrading to  
Pulp 2.8.3:

$ sudo systemctl stop httpd pulp_workers pulp_resource_manager pulp_celerybeat 
goferd
$ sudo yum upgrade
$ sudo systemctl start httpd pulp_workers pulp_resource_manager pulp_celerybeat 
goferd

CVE-2016-3112 (Part I)
--

The client certificate for consumers 
(/etc/pki/pulp/consumer/consumer-cert.pem) was installed world-readable. This 
issue has been fixed for new certificates issued to consumers, but upgrading 
to 2.8.3 does not modify the permissions of old certificates. It is  
recommended that users regenerate the certificates by unregistering and 
re-registering all consumers. However, the consumers cannot be re-registered 
until CVE-2013-7450, CVE-2016-3095, CVE-2016-3106, and CVE-2016-3111 have 
been addressed below. Thus, start by unregistering each of your consumers (we 
will return to this CVE later to re-register them):

$ sudo pulp-consumer unregister

CVE-2013-7450, CVE-2016-3095, and CVE-2016-3106
---

There are two reasons that you may wish to regenerate Pulp's internal 
certificate authority key and certificate. First, if your Pulp installation 
started off as a version lower than 2.3.0 and you are still using the default 
CA certificate and key that was distributed with those versions of Pulp, then 
you are still vulnerable to CVE-2013-7450 and it is crucial that you generate 
a new unique CA. 

Additionally, CVE-2016-3095 and CVE-2016-3106 made it possible for local 
attackers to read the CA key during generation (which happens during the 
initial installation of Pulp or any time an admin ran 
pulp-gen-ca-certificate). If you are concerned that a local user may have 
read that CA key during the brief window that it was visible it is  
recommended that you regenerate the key and cert.

To regenerate the certificate, you should remove the old one and then you may 
use the provided utility:

# First remove the old files so that the new files get the correct SELinux 
context.

$ sudo rm /etc/pki/pulp/ca.*
$ sudo pulp-gen-ca-certificate

If you choose not to perform the CA regeneration, you may wish to apply the 
correct SELinux type to your existing CA files as versions of Pulp < 2.8.3 
generated this file with an incorrect SELinux type. You don't need to do this 
if you removed the old file and regenerated it with pulp-gen-ca-certificate. 
You can run restorecon recursively on the /etc/pki/pulp folder to fix the 
SELinux label on your existing CA certificate:

# You only need to do this if you didn't regenerate the CA above.
$ sudo restorecon -R /etc/pki/pulp

CVE-2016-3107 and CVE-2016-3108
---

For Nodes users, the /etc/pki/pulp/nodes/node.crt file was installed 
world-readable. Users are recommended to remove this file and regenerate it 
by running pulp-gen-nodes-certificate:

# It is important to remove the file so that the new file has the correct 
permissions.
$ sudo rm /etc/pki/pulp/nodes/node.crt
$ sudo pulp-gen-nodes-certificate

CVE-2016-3111
-

Both the RSA key pair for the Pulp server and RSA key pair for each Pulp 
consumer was generated during installation in an insecure directory. This 
vulnerability allowed a local attacker to read the private key portion of the 
key pair. These keys are used for message authentication between the Pulp 
server and the Pulp consumers. If you are concerned that a local attacker was 
able to read these keys, you can rege

[Pulp-list] Pulp 2.8.3 Beta 1 released - Security & Bug fixes

[Sean Myers]

Pulp, along with the Puppet (pulp_puppet) and RPM (pulp_rpm) plugins,
have been updated to 2.8.3. This release also includes betas for OSTree
plugin (pulp_ostree) version 1.1.1 and the Docker plugin (pulp_docker)
version 2.0.1.

The following Security issues were addressed in this release:

CVE-2016-3111 (Low Impact):
pulp.spec generates its RSA keys for message signing insecurely
https://pulp.plan.io/issues/1837

CVE-2016-3112 (Moderate Impact):
Pulp consumer private keys are world-readable
https://pulp.plan.io/issues/1834

CVE-2016-3107 (Moderate Impact):
Node certificate containing private key stored in world-readable file
https://pulp.plan.io/issues/1833

CVE-2016-3108 (Moderate Impact):
Insecure temporary file used when generating certificate for Pulp Nodes
https://pulp.plan.io/issues/1830

CVE-2016-3106 (Low Impact):
Insecure creation of temporary directory when generating new CA key
https://pulp.plan.io/issues/1827

Details on addressing these vulnerabilities will be released in a
followup email later today, and included in subsequent release
announcements for 2.8.3 (apologies for not being able to include
them in this post).

Bugs fixed in this release:

  OSTree Support
1106relative_path should be checked for url collision
  Pulp
1837CVE-2016-3111: pulp.spec generates its RSA keys for message 
signing insecurely
1834CVE-2016-3112: Pulp consumer private keys are world-readable
1833CVE-2016-3107: Node certificate containing private key stored 
in world-readable file
1830CVE-2016-3108: Insecure temporary file used when generating 
certificate for Pulp Nodes
1827CVE-2016-3106: Insecure creation of temporary directory when 
generating new CA key
1824iso repo publish fails for file in subdirectories
1809python 2.6 incompatibility during set_importer
1802Pulp 2.8 client no longer supports sha1 RPM checksum type
1801Pulp celery_beat and resource_manager are running, but logs say 
they are not running
1794A Pulp unit test is failing to find a certificate to be valid
1791After upgrading from 2.7.1 to pulp 2.8.0 getting 403 error's on 
all my Pulp repo's.
1784regression: "pulp-admin rpm repo search" with filters does not 
work as expected
1771requests or urllib3 can't read a file which causes Nectar to 
fail mysteriously
1764SELinux denial on Celery attempting to read resolv.conf
1601Migrate /var/lib/pulp/content to new 2.8 storage paths.
1576content type mongo id searches not working
  Puppet Support
1780PLP: Update failed (The dotted field 
'thomasmckay-rsync-0.4.1-thomasmckay'
  Python Support
1855Upload broken
  RPM Support
1856publishing kickstart repo fails on EL6
1843Pulp publishes invalid PULP_DISTRIBUTION.xml metadata
1835export fails when units are not downloaded
1828pulp doesn't sync reference title correctly from errata
1813Handle duplicate key error in comps.xml upload
1812Comps.xml upload succeeds but units are not associated to the 
repo.
1808exporting a sufficiently large repo with 'on_demand' policy 
results in BSON error
1792recursive and depsolving unit copy results in 
PulpExecutionException
1782None in generated XML for 
unit with no 'reboot_suggested'
1778Switching a repository to immediate from on_demand doesn't 
download its packages
1768Unable to sync RHEL 5 repositories with a distribution

View the full issue list in redmine here:
http://bit.ly/1Tsld0E



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.2 has been released!

[Sean Myers]

Pulp 2.8.2 has been published to the stable repositories:

https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.8/

Changes
===

Pulp 2.8.2 addresses a security vulnerability that was found after the
announcement of the 2.8.1 release candidate. More information about this
vulnerability, including upgrade instructions, can be found at 
the following address:

http://www.openwall.com/lists/oss-security/2016/04/06/3

Satellite users are unaffected by this vulnerability:

https://access.redhat.com/security/cve/cve-2016-3095

(It's currently in the reserved state, but should be opened up shortly.)

From the access.redhat.com CVE page:

"This issue did not affect the versions of pulp as shipped with Red Hat
Satellite 6.x and Red Hat Update Infrastructure 2.x as they did not include
support for pulp-gen-ca-certificate."

Notes
=

This was discovered after the 2.8.1 release candidate was published, so
the fastest way for us to get this out the door was a rapid-fire hotfix
release. This is a unique situation; two releases of the same pulp minor
version in two days is exceptional and should not become the norm.



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.1 has been released!

[Sean Myers]

Pulp 2.8.1 has been published to the stable repositories:

https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.8/

Changes
===

The following Redmine (pulp.plan.io) issues are addressed in 2.8.1:

  Pulp
1734The Pulp streamer logs a traceback when a ConnectionError 
occurs.
1764SELinux denial on Celery attempting to read resolv.conf
1737The checksum/checksum_type is not being included in the lazy 
catalog
1735Downloading the CentOS base repository fails with lazy and 
--verify-all
1776sync_complete response has changed

  Puppet Support
1607Puppet install distributor fails when deleting repository if 
not published

  RPM Support
1138Install applicable errata consumer task does not report kernel 
packages were updated
1366Advisory package list doesn't match packages in the repository
1548published errata contain packages not in repo
1789Sync fills up /var/cache/pulp/ with rpms

More details regarding these issues can be found in Redmine at the following 
URL:

http://bit.ly/1LHtwWp

Aside from rpm version numbers and the addition of release notes,
no changes to 2.8.1 took place between the 2.8.1 beta release and
this release candidate.

RHEL/CentOS 6 Users
===

The issue with the el6 qpid COPR repository that impacted qpid
installations mentioned in the 2.8.1 release candidate announcemnet
has been resolved. The qpid COPR repository for el6 has since been
rebuilt, so el6 installations of Pulp should proceed normally again.





signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.1 Release Candidate is available

[Sean Myers]

The Pulp 2.8.1 *release candidate* has been published to the beta repositories:

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

Changes
===

The following Redmine (pulp.plan.io) issues are addressed in 2.8.1:

  Pulp
1734The Pulp streamer logs a traceback when a ConnectionError 
occurs.
1764SELinux denial on Celery attempting to read resolv.conf
1737The checksum/checksum_type is not being included in the lazy 
catalog
1735Downloading the CentOS base repository fails with lazy and 
--verify-all
1776sync_complete response has changed

  Puppet Support
1607Puppet install distributor fails when deleting repository if 
not published

  RPM Support
1138Install applicable errata consumer task does not report kernel 
packages were updated
1366Advisory package list doesn't match packages in the repository
1548published errata contain packages not in repo
1789Sync fills up /var/cache/pulp/ with rpms

More details regarding these issues can be found in Redmine at the following 
URL:

http://bit.ly/1LHtwWp

Aside from rpm version numbers, no changes to 2.8.1 took place between the
2.8.1 beta release and this release candidate.

RHEL/CentOS 6 Users
===

There is an issue with the el6 qpid COPR repository that impacts qpid
installations, and so it also impacts el6 pulp installations using qpid.
This issue is not directly related to the 2.8.1 release, but may affect
users upgrading to this rc and so I've included it here.

More details on this issue and how to work around it until the proper fix
is put in place can be found in a message sent to pulp-list yesterday
by mhrivnak, "qpid on el6 fails to install". That mail can also be seen in
the list archive here:

https://www.redhat.com/archives/pulp-list/2016-March/msg00087.html



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.1 beta is available

[Sean Myers]

Pulp 2.8.1 has been published to the beta repositories:

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

The following Redmine (pulp.plan.io) issues have been addressed in this release:

  Pulp
1734The Pulp streamer logs a traceback when a ConnectionError 
occurs.
1764SELinux denial on Celery attempting to read resolv.conf
1737The checksum/checksum_type is not being included in the lazy 
catalog
1735Downloading the CentOS base repository fails with lazy and 
--verify-all
1776sync_complete response has changed

  Puppet Support
1607Puppet install distributor fails when deleting repository if 
not published

  RPM Support
1138Install applicable errata consumer task does not report kernel 
packages were updated
1366Advisory package list doesn't match packages in the repository
1548published errata contain packages not in repo
1789Sync fills up /var/cache/pulp/ with rpms

More details regarding these issues can be found in Redmine at the following 
URL:

http://bit.ly/1LHtwWp



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] vagrant provisioning fails

[Sean Myers]

I think most folks using vagrant recently have hit this, which is that
"vagrant up" explodes on the dnf upgrade provisioning step.

I've been poking at this off and on, and I have a diff that "fixes" it:

---

$ diff -u Vagrantfile.example Vagrantfile
--- Vagrantfile.example 2016-02-25 10:09:05.084514090 -0500
+++ Vagrantfile 2016-03-21 18:38:14.770621087 -0400
@@ -30,32 +28,32 @@
# end

# Comment this line if you would like to disable the automatic update during 
provisioning
- config.vm.provision "shell", inline: "sudo dnf upgrade -y"
+ config.vm.provision "shell", inline: "sudo dnf upgrade -y || sudo dnf upgrade 
-y"

---

"Hey dnf, if you could go ahead and upgrade my system without prompting me, 
that'd be
great. Hmm. Yeah. If that doesn't work, why don't you, y'know, go ahead and 
make sure you
upgrade my system without prompting me. Yeeeh. That'd be great. 
Thnks."[0]

I know there has to be a better "solution", but I found this one simultaneously
useful and hilarious enough to share. It's better than a simple "|| true" in 
that
it doesn't hide actual failures of a dnf upgrade, but for whatever reason it 
does
suppress the failure that's currently annoying many vagrant users.

Meanwhile...does anyone have a clue why dnf is behaving this way?

[0]: https://www.youtube.com/watch?v=Fy3rjQGc6lA



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] New Redmine Field: Target Platform Release

[Sean Myers]

On 03/15/2016 04:53 PM, Sean Myers wrote:
> I put together a quick "Next Release" query demonstrating the change in
> action: https://pulp.plan.io/issues?query_id=59

On the suggestion of Brian Bouterse, I've renamed this report to be
"2.8.1 - Next Bugfix Release". I also created a similar report for the
next 'y' release, "2.9 - Next Feature Release". The plan with both
reports is to update them as-needed to have the correct name and
filtering to match the version number of our next y- and z-stream releases.

Here are those links for your bookmarking pleasure:

y-stream report - https://pulp.plan.io/issues?query_id=61
z-stream report - https://pulp.plan.io/issues?query_id=59



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list