Bug 1395151
| Summary: | Puppet module appear in content view but doesn't appear in lifecycle | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Waldirio M Pinheiro <wpinheir> | ||||
| Component: | Lifecycle Environments | Assignee: | Brad Buckingham <bbuckingham> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.2.4 | CC: | bbuckingham, greartes, jcallaha | ||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-02-21 16:51:07 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Waldirio M Pinheiro
2016-11-15 09:49:05 UTC
Created redmine issue http://projects.theforeman.org/issues/17402 from this bug Proposed Katello PR: https://github.com/Katello/katello/pull/6464 (also on 6.2.4)
In my case, the CV 'BASE RHEL7' has only 1 puppet module (stdlib from puppetlabs).
The CV 'BASE RHEL7' is published and promoted to LIBRARY, DESA, PROD.
As the BZ Description says,
* Open lifecycle and click on Puppet Modules tab
* Will see the message "There are no Puppet Modules that match the criteria."
But there is one 'caveat', i only get the message "There are no Puppet Modules that match the criteria." when the filter is "All Content Views".
I changed it to 'BASE RHEL7', and i got the eternal spinning wheel instead....
In production.log a database error can be seen....
[...TRUNCATED...]
2016-11-30 17:02:20 [app] [I] Started GET "/katello/api/v2/repositories?content_type=puppet&content_view_id=3&environment_id=3&full_result=true&library=true&organization_id=3" for 10.10.0.10 at 2016-11-30 17:02:20 -0300
2016-11-30 17:02:20 [app] [I] Processing by Katello::Api::V2::RepositoriesController#index as JSON
2016-11-30 17:02:20 [app] [I] Parameters: {"content_type"=>"puppet", "content_view_id"=>"3", "environment_id"=>"3", "full_result"=>"true", "library"=>"true", "organization_id"=>"3", "api_version"=>"v2"}
2016-11-30 17:02:20 [app] [I] Rendered /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.82/app/views/katello/api/v2/repositories/index.json.rabl within katello/api/v2/layouts/collection (5.3ms)
2016-11-30 17:02:20 [app] [I] Completed 200 OK in 98ms (Views: 11.1ms | ActiveRecord: 26.9ms)
2016-11-30 17:02:20 [app] [I] Started GET "/katello/api/v2/puppet_modules?content_view_version_id=27&environment_id=3&library=true&page=1&search=" for 10.10.0.10 at 2016-11-30 17:02:20 -0300
2016-11-30 17:02:20 [app] [I] Processing by Katello::Api::V2::PuppetModulesController#index as JSON
2016-11-30 17:02:20 [app] [I] Parameters: {"content_view_version_id"=>"27", "environment_id"=>"3", "library"=>"true", "page"=>"1", "search"=>"", "api_version"=>"v2"}
2016-11-30 17:02:20 [app] [E] PG::Error: ERROR: el mensaje de enlace (bind) entrega 2 parámetros, pero la sentencia preparada «a7» requiere 1
|
| /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/postgresql_adapter.rb:834:in `get_last_result'
[...TRUNCATED...]
2016-11-30 17:02:20 [app] [I] Completed 500 Internal Server Error in 120ms (Views: 0.5ms | ActiveRecord: 32.2ms)
If i got to Content -> Content Views, BASE RHEL7 -> Puppet Modules, the 'stdlib' module is listed.
Cheers.
Verified on Sat6.3 snap 13, after promoting a puppet cv to a lc environment, the associated module is displayed in lc details, see attached screenshot Created attachment 1320554 [details]
screen-lc-modules
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
>
> For information on the advisory, and where to find the updated files, follow the link below.
>
> If the solution does not work for you, open a new bug report.
>
> https://access.redhat.com/errata/RHSA-2018:0336
|