Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJustin Sherrill
2015-05-05 17:07:36 UTC
Description of problem:
If a content view is published with a puppet module that contains a symlink, any future publishes will fail to deploy newer puppet modules.
This can be seen with the puppetlabs-apache-1.0.0 module.
Also to note is that pulp throws no error, so we do not know that the repo publish has failed.
How reproducible:
Always
Steps to Reproduce (note the apache 1.0.0 module is very important here):
* Created a custom product a custom puppet based repository
* Added 2 versions of the puppet lap apache module to said repository
* Created content view PuppetCV and added version 1.0.0 of apache module
* Published PuppetCV
* Created a composite content view named Tutti
* Added PuppetCV to Tutti and published Tutti
Filesystem shows:
# cat /etc/puppet/environments/KT_Default_Organization_Library_Tutti_9/modules/apache/metadata.json |grep version
"version": "1.0.0",
"version_requirement": "3.2.x"
"version_requirement": "3.x"
"version_requirement": ">= 2.4.0"
"version_requirement": ">= 1.0.0"
"manifests/version.pp": "81d6349fd3f4c80e89c8b73c724895d9",
"spec/acceptance/version.rb": "a7d6f86a6c457c29ca36810f3e722a99",
* Updated PuppetCV and updated the version of the apache module to version 1.3.0
* Published PuppetCV again
* Updated Tutti to use newer version of PuppetCV and republished Tutti
Filesystem shows:
# cat /etc/puppet/environments/KT_Default_Organization_Library_Tutti_9/modules/apache/metadata.json |grep version
"version": "1.0.0",
"version_requirement": "3.2.x"
"version_requirement": "3.x"
"version_requirement": ">= 2.4.0"
"version_requirement": ">= 1.0.0"
"manifests/version.pp": "81d6349fd3f4c80e89c8b73c724895d9",
"spec/acceptance/version.rb": "a7d6f86a6c457c29ca36810f3e722a99",
Therefore it doesn't look like the composite content view contains the newer version of apache.
Actual results:
new puppet modules are not deployed
Expected results:
new puppet modules are deployed
Additional info:
This was seen in https://bugzilla.redhat.com/show_bug.cgi?id=1186353
VERIFIED:
# rpm -qa | grep foreman
foreman-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.13-1.el7sat.noarch
foreman-libvirt-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
foreman-postgresql-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-ovirt-1.7.2.21-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
foreman-gce-1.7.2.21-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.6-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.12-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
dell-pem710-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch
foreman-vmware-1.7.2.21-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
foreman-compute-1.7.2.21-1.el7sat.noarch
foreman-debug-1.7.2.21-1.el7sat.noarch
steps:
* Created a custom product a custom puppet based repository
* Added 2 versions of the puppet lap apache module to said repository
* Created content view PuppetCV and added version 1.0.0 of apache module
* Published PuppetCV
* Created a composite content view named Tutti
* Added PuppetCV to Tutti and published Tutti
Filesystem shows:
# cat /etc/puppet/environments/KT_Default_Organization_Library_tutti_6/modules/apache/metadata.json |grep version
"version": "1.0.0",
"version_requirement": "3.2.x"
"version_requirement": "3.x"
"version_requirement": ">= 2.4.0"
"version_requirement": ">= 1.0.0"
"manifests/version.pp": "81d6349fd3f4c80e89c8b73c724895d9",
"spec/acceptance/version.rb": "a7d6f86a6c457c29ca36810f3e722a99",
* Updated PuppetCV and updated the version of the apache module to version 1.3.0
* Published PuppetCV again
* Updated Tutti to use newer version of PuppetCV and republished Tutti
Filesystem shows:
# cat /etc/puppet/environments/KT_Default_Organization_Library_tutti_6/modules/apache/metadata.json |grep version
"version": "1.3.0",
"version_requirement": "3.x"
"version_requirement": "3.x"
{"name":"puppetlabs/stdlib","version_requirement":">= 2.4.0"},
{"name":"puppetlabs/concat","version_requirement":">= 1.1.1"}
new puppet modules are deployed
Description of problem: If a content view is published with a puppet module that contains a symlink, any future publishes will fail to deploy newer puppet modules. This can be seen with the puppetlabs-apache-1.0.0 module. Also to note is that pulp throws no error, so we do not know that the repo publish has failed. How reproducible: Always Steps to Reproduce (note the apache 1.0.0 module is very important here): * Created a custom product a custom puppet based repository * Added 2 versions of the puppet lap apache module to said repository * Created content view PuppetCV and added version 1.0.0 of apache module * Published PuppetCV * Created a composite content view named Tutti * Added PuppetCV to Tutti and published Tutti Filesystem shows: # cat /etc/puppet/environments/KT_Default_Organization_Library_Tutti_9/modules/apache/metadata.json |grep version "version": "1.0.0", "version_requirement": "3.2.x" "version_requirement": "3.x" "version_requirement": ">= 2.4.0" "version_requirement": ">= 1.0.0" "manifests/version.pp": "81d6349fd3f4c80e89c8b73c724895d9", "spec/acceptance/version.rb": "a7d6f86a6c457c29ca36810f3e722a99", * Updated PuppetCV and updated the version of the apache module to version 1.3.0 * Published PuppetCV again * Updated Tutti to use newer version of PuppetCV and republished Tutti Filesystem shows: # cat /etc/puppet/environments/KT_Default_Organization_Library_Tutti_9/modules/apache/metadata.json |grep version "version": "1.0.0", "version_requirement": "3.2.x" "version_requirement": "3.x" "version_requirement": ">= 2.4.0" "version_requirement": ">= 1.0.0" "manifests/version.pp": "81d6349fd3f4c80e89c8b73c724895d9", "spec/acceptance/version.rb": "a7d6f86a6c457c29ca36810f3e722a99", Therefore it doesn't look like the composite content view contains the newer version of apache. Actual results: new puppet modules are not deployed Expected results: new puppet modules are deployed Additional info: This was seen in https://bugzilla.redhat.com/show_bug.cgi?id=1186353