Greg, I don't know anything like that off the top of my head, if you are able to find the error with the traceback, please post it here and we can look into debugging why you are getting that error to begin with.
Thanks, John Mitsch Red Hat Engineering (860)-967-7285 irc: jomitsch On Thu, Jul 7, 2016 at 11:27 AM, Greg Swift <[email protected]> wrote: > thanks john. That was the first step I had done, and as far as I could > tell the things were there. What i'm wondering is how I would go about > doing a check of what I have defined in katello against what lives in > pulp. Something along the line of mapping output from hammer into > pulp-admin to verify existence. > > I was kinda hoping there might be a script floating around somewhere that > was used for acceptance testing, etc, to make sure things were happening > during dev that I could re-work a bit to run against a prod system. > > -greg > > On Thu, Jul 7, 2016 at 8:06 AM John Mitsch <[email protected]> wrote: > >> Greg, >> >> You can use pulp-admin to view and manage pulp content. If it is not >> already there, "yum install -y pulp-admin-client". You can find your >> password in /etc/pulp/server.conf by searching for 'default_password'. >> >> Hope this helps >> >> John Mitsch >> Red Hat Engineering >> (860)-967-7285 >> irc: jomitsch >> >> On Thu, Jul 7, 2016 at 12:28 AM, Greg Swift <[email protected]> wrote: >> >>> We have been pushing releases out a bit more lately after finally moving >>> some systems fully onto katello. What I'm finding is that often times when >>> cutting a release or promoting a version we have steps fail due to '404 >>> Resource not found'. I've gone manually looking in pulp for what I think >>> its looking for, and they seem to be there. >>> >>> Unfortunately, once the tasks are resumes i can't seem to find the >>> errors via dynflow anymore. I will make sure to capture some next time. >>> >>> So my general ask is, is they any way to run an audit of everything >>> katello thinks is supposed to be in pulp? >>> >>> -greg >>> >> -- >>> You received this message because you are subscribed to the Google >>> Groups "Foreman users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/foreman-users. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
