Bug 1105614
| Summary: | Error trying to use a pulp server that has been idle for a few days | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Pulp | Reporter: | Preethi Thomas <pthomas> | ||||||||
| Component: | async/tasks | Assignee: | pulp-bugs | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | pulp-qe-list | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 2.4 Beta | CC: | bmbouter, mhrivnak, pthomas, skarmark | ||||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||||
| Target Release: | 2.4.0 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2014-06-09 20:23:32 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: |
|
||||||||||
Created attachment 902939 [details]
log
/var/log/messages when running the sync
Created attachment 902941 [details]
log message
I also see this in the log
Any chance that either this had an older version of pulp-common installed than pulp-server, or that this was upgraded from a previous beta and not all of the workers got restarted? I am not able to reproduce this, and looking at the code, I don't think these errors should be possible if everything was running from the 0.19 beta. Yes looks like that is the issue. This was upgraded from .16 and somehow all the deps did not get upgraded [root@pulp-24-server ~]# rpm -qa |grep pulp python-pulp-puppet-common-2.4.0-0.16.beta.el6.noarch pulp-puppet-admin-extensions-2.4.0-0.19.beta.el6.noarch pulp-puppet-consumer-extensions-2.4.0-0.19.beta.el6.noarch pulp-selinux-2.4.0-0.19.beta.el6.noarch python-pulp-client-lib-2.4.0-0.16.beta.el6.noarch python-pulp-common-2.4.0-0.16.beta.el6.noarch createrepo-0.9.9-21.2.pulp.el6.noarch python-pulp-rpm-common-2.4.0-0.16.beta.el6.noarch python-pulp-agent-lib-2.4.0-0.16.beta.el6.noarch pulp-server-2.4.0-0.19.beta.el6.noarch python-kombu-3.0.15-8.pulp.el6.noarch pulp-admin-client-2.4.0-0.19.beta.el6.noarch pulp-rpm-admin-extensions-2.4.0-0.19.beta.el6.noarch pulp-rpm-consumer-extensions-2.4.0-0.19.beta.el6.noarch pulp-puppet-handlers-2.4.0-0.19.beta.el6.noarch pulp-rpm-plugins-2.4.0-0.19.beta.el6.noarch pulp-rpm-handlers-2.4.0-0.19.beta.el6.noarch python-isodate-0.5.0-1.pulp.el6.noarch m2crypto-0.21.1.pulp-8.el6.x86_64 mod_wsgi-3.4-1.pulp.el6.x86_64 python-pulp-bindings-2.4.0-0.16.beta.el6.noarch pulp-consumer-client-2.4.0-0.19.beta.el6.noarch pulp-agent-2.4.0-0.19.beta.el6.noarch pulp-rpm-yumplugins-2.4.0-0.19.beta.el6.noarch pulp-puppet-plugins-2.4.0-0.19.beta.el6.noarch [root@pulp-24-server ~]# Would it be possible to have QE testing occur on a fresh machine each time? Maybe some automation wouldinstall pulp in a fresh machine from a specific version provided by pulp QE archive. I do fresh install with every build. This has been a one off case where I did an upgrade. So I can close this bz. Since we found the root cause for this bug, I'm going to close it as NOTABUG. It's a little strange that you didn't receive the latest python-kombu when you upgraded Pulp. Perhaps because we are mixing versions of rpms offered between the beta and testing repos, and this machine is likely subscribed to both. If Pulp does have some kind of dependency problem, let's re-raise that as its own issue. Thanks for reporting Preethi! |
Created attachment 902937 [details] admin.log Description of problem: I had a pulp server that has been idle for a few days. When I tried to use it again, I encountered an error [root@pulp-24-server ~]# pulp-admin puppet repo sync run --repo-id puppet-repo +----------------------------------------------------------------------+ Synchronizing Repository [puppet-repo] +----------------------------------------------------------------------+ An internal error occurred on the Pulp server. More information can be found in the client log file ~/.pulp/admin.log. [root@pulp-24-server ~]# Version-Release number of selected component (if applicable): [root@pulp-24-server ~]# rpm -qa pulp-server pulp-server-2.4.0-0.19.beta.el6.noarch [root@pulp-24-server ~]# How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: logs attached