[foreman-users] 2.4-3.0 upgrade stuck

[sinux shen]

Hey guys,

when I upgrade katello from 2.4 to 3.0, I found it stuck at 
"update_puppet_repository_distributors (this may take a while)"
Upgrade Step: import_puppet_modules (this may take a while) ...
Upgrade Step: import_subscriptions (this may take a while) ...
Upgrade Step: elasticsearch_message...
Elasticsearch has been removed as a dependency.  The database files can be 
removed manually with #rm -rf /var/lib/elasticsearch.  Some packages are no 
longer needed and can be removed:  #rpm -e ruby193-rubygem-tire 
tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib 
lucene4
Upgrade Step: add_export_distributor (this may take a while) ...
Upgrade Step: remove_docker_v1_content (this may take a while) ...
Upgrade Step: update_puppet_repository_distributors (this may take a while) 
...

the whole system still works though, but I don't know if any impact it will 
has, is there any way that we can manually run to trouble shoot or proceed.?

Thanks
-Sinux

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Boot disk based imaging, katello capsule in the DMZ - server still needs access to main katello srv?

[Dylan Baars]

This is what I'm currently seeing in the installation media (I've removed 
my manually created one)


Here is the available life-cycle environments for the capsule

---|---||--
[root@wellkatellotst ~]# hammer capsule content 
available-lifecycle-environments --id 5
---|--|-
ID | NAME | ORGANIZATION
---|--|-
2  | Library  | NIWA
5  | Test-Desktop | NIWA
3  | VMware Host  | NIWA
6  | Prod-Desktop | NIWA
1  | Library  | Default Organization
7  | Dev-Server   | NIWA
9  | Prod-Server  | NIWA
8  | Test-Server  | NIWA
4  | Kickstart| NIWA
---|--|-

I have synced everything except the *-Desktop environments 

Having read a bit about the installation media, it looks like if Katello 
detects there is installation media available, it should be automatically 
created. I checked under "Manage organizations" > NIWA, > Media, but there 
is no new media available other than the existing 
"NIWA/Library/Centos7/os_x86_64" media (which is already a "selected item"

So I guess I'm asking how do I make installation media available on the 
capsule?

Thanks for your help!
Dylan

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Is it possible to 'audit' pulp based on expected views in katello?

[John Mitsch]

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  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  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  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 foreman-users+unsubscr...@googlegroups.com.
>>> To post to this group, send email to foreman-users@googlegroups.com.
>>> 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 foreman-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> 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 foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> 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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Boot disk based imaging, katello capsule in the DMZ - server still needs access to main katello srv?

[Dylan Baars]

I added it manually as it didn't appear - possible it doesn't even exist 
:-) How do I sync the existing kickstart repo to the capsule?

On Friday, July 8, 2016 at 6:29:23 AM UTC+12, Eric Helms wrote:
>
> When you say you added installation media, did you add it manually or did 
> you sync a kickstart repository?
>
>
>

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] [Katello] subscription-manager fails to connect to Katello 3.0.1

[Chris Duryee]

On 06/23/2016 03:19 AM, Edgars M. wrote:
> From 2.4.4

Sorry, I lost track of this email. Are you still having issues with
registration?

> 
> trešdiena, 2016. gada 22. jūnijs 15:15:44 UTC+2, Chris Duryee rakstīja:
>>
>>
>>
>> On 06/22/2016 03:23 AM, Edgars M. wrote: 
>>> Hi 
>>>
>>> After upgrade to Katello 3.0.1 I cannot subscribe clients to it anymore: 
>>
>> which version did you upgrade from? 
>>
>>>
>>> 2016-06-22 09:14:32,676 [DEBUG] subscription-manager:7854 
>> @ga_loader.py:89 
>>> - ga_loader GaImporterGtk2 
>>> 2016-06-22 09:14:32,679 [DEBUG] subscription-manager:7854 
>> @plugins.py:569 - 
>>> loaded plugin modules: [] 
>>> 2016-06-22 09:14:32,679 [DEBUG] subscription-manager:7854 
>> @plugins.py:570 - 
>>> loaded plugins: {} 
>>> 2016-06-22 09:14:32,679 [DEBUG] subscription-manager:7854 
>> @identity.py:131 
>>> - Loading consumer info from identity certificates. 
>>> 2016-06-22 09:14:32,710 [INFO] subscription-manager:7854 
>> @managercli.py:367 
>>> - Client Versions: {'python-rhsm': '1.16.6-1.el6', 
>> 'subscription-manager': 
>>> '1.16.8-8.el6'} 
>>> 2016-06-22 09:14:32,710 [INFO] subscription-manager:7854 
>> @connection.py:815 
>>> - Connection built: host=katello.local port=443 handler=/rhsm 
>>> auth=identity_cert ca_dir=/etc/rhsm/ca/ verify=True 
>>> 2016-06-22 09:14:32,711 [INFO] subscription-manager:7854 
>> @connection.py:815 
>>> - Connection built: host=katello.local port=443 handler=/rhsm auth=none 
>>> 2016-06-22 09:14:32,711 [INFO] subscription-manager:7854 
>> @managercli.py:342 
>>> - Consumer Identity name=node.local uuid=xxx 
>>> 2016-06-22 09:14:32,712 [DEBUG] subscription-manager:7854 
>>> @connection.py:557 - Making request: GET 
>>> /rhsm/consumers/xxx/certificates/serials 
>>> 2016-06-22 09:14:32,874 [DEBUG] subscription-manager:7854 
>>> @connection.py:589 - Response: status=200 
>>> 2016-06-22 09:14:32,875 [DEBUG] subscription-manager:7854 
>>> @connection.py:557 - Making request: GET 
>>> /rhsm/consumers/xxx/certificates?serials=xxx 
>>> 2016-06-22 09:14:32,912 [DEBUG] subscription-manager:7854 
>>> @connection.py:589 - Response: status=302 
>>> 2016-06-22 09:14:32,913 [ERROR] subscription-manager:7854 
>>> @connection.py:618 - Response: 302 
>>> 2016-06-22 09:14:32,913 [ERROR] subscription-manager:7854 
>>> @connection.py:619 - JSON parsing error: No JSON object could be decoded 
>>> 2016-06-22 09:14:32,913 [ERROR] subscription-manager:7854 
>>> @managercli.py:174 - Unable to perform refresh due to the following 
>>> exception: Network error code: 302 
>>> 2016-06-22 09:14:32,913 [ERROR] subscription-manager:7854 
>>> @managercli.py:175 - Network error code: 302 
>>> Traceback (most recent call last): 
>>>   File "/usr/share/rhsm/subscription_manager/managercli.py", line 622, 
>> in 
>>> _do_command 
>>> self.entcertlib.update() 
>>>   File "/usr/share/rhsm/subscription_manager/certlib.py", line 31, in 
>> update 
>>> self.report = self.locker.run(self._do_update) 
>>>   File "/usr/share/rhsm/subscription_manager/certlib.py", line 17, in 
>> run 
>>> return action() 
>>>   File "/usr/share/rhsm/subscription_manager/entcertlib.py", line 43, in 
>>> _do_update 
>>> return action.perform() 
>>>   File "/usr/share/rhsm/subscription_manager/entcertlib.py", line 129, 
>> in 
>>> perform 
>>> self.install(missing_serials) 
>>>   File "/usr/share/rhsm/subscription_manager/entcertlib.py", line 159, 
>> in 
>>> install 
>>> cert_bundles = self.get_certificates_by_serial_list(missing_serials) 
>>>   File "/usr/share/rhsm/subscription_manager/entcertlib.py", line 248, 
>> in 
>>> get_certificates_by_serial_list 
>>> serials=sn_list) 
>>>   File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 
>> 1138, 
>>> in getCertificates 
>>> return self.conn.request_get(method) 
>>>   File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 
>> 681, 
>>> in request_get 
>>> return self._request("GET", method) 
>>>   File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 
>> 598, 
>>> in _request 
>>> self.validateResponse(result, request_type, handler) 
>>>   File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 
>> 668, 
>>> in validateResponse 
>>> raise NetworkException(response['status']) 
>>> NetworkException: Network error code: 302 
>>>
>>>
>>>
>>
> 

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] puppet modules and default organization view

[Eric D Helms]

Today this is not possible because we are not creating puppet environments
for the default content view in part due to how modules can have multiple
versions upload to a puppet repository. There is an open issue around this
[1] that would be great to get an upvote(s) on and information describing
your workflow to help us prioritize it.

[1] http://projects.theforeman.org/issues/8773

On Wed, Jun 22, 2016 at 11:05 AM, Nathanaël Blanchet <
digitall.fin...@gmail.com> wrote:

>  hello, is it possible to add puppet module to the default organization
> view?
>  I don't want to publish a new view each time I add a new puppet module
> from repo
> I thought it was possible the same way we usually do for getiing
> continuous rpm update with default organization view.
>  I thought it was default, but when looking at
> environment->library->default-organization->puppet modules, it says There
> are no Puppet Modules that match the criteria.
>
> katello 3.0/foreman 1.11.3
>
> --
> 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 foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] [katello 2.4] passenger status broken

[Eric D Helms]

On Tue, Jul 5, 2016 at 10:55 AM, Edson Manners 
wrote:

> I've been struggling with this issue for a while and finally feel the need
> to seek external help.
>
> We used to run Foreman 1.9.3 on RHEL 7.2. the passenger-status command was
> used to tune the puppetmaster when the server got overwhelmed.
>
> [root@foreman ~]# cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 7.2 (Maipo)
> [root@foreman ~]# which passenger-status
> /usr/bin/passenger-status
> [root@foreman ~]# rpm -q --whatprovides /usr/bin/passenger-status
> rubygem-passenger-4.0.18-9.8.el7.x86_64
> [root@foreman ~]# /usr/bin/passenger-status
> Version : 4.0.18
> Date: 2016-07-05 10:44:15 -0400
> Instance: 3376
> --- General information ---
> Max pool size : 48
> Processes : 3
> Requests in top-level queue : 0
>
> --- Application groups ---
> /usr/share/foreman#default:
>   App root: /usr/share/foreman
>   Requests in queue: 0
>   * PID: 18170   Sessions: 0   Processed: 622 Uptime: 4h 24m 28s
> CPU: 0%  Memory  : 232MLast used: 6s ago
> 
> ...
>
>
> We've moved to katello 2.4 on CentOS 7.2 and now passenger-status no
> longer works out of the box.
>
> [root@katello-test emanners]# cat /etc/redhat-release
> CentOS Linux release 7.2.1511 (Core)
> [root@katello-test emanners]# which passenger-status
> /sbin/passenger-status
> [root@katello-test emanners]# rpm -q --whatprovides
> /usr/sbin/passenger-status
> passenger-4.0.53-4.el7.x86_64
> [root@katello-test emanners]# /usr/sbin/passenger-status
> ERROR: Phusion Passenger doesn't seem to be running.
>
> I've managed to find a few posts on Google (not Katello related) that
> suggest the reason is multiple copies of passenger on the host.
> [root@katello-test ~]# locate passenger-status
> /opt/theforeman/tfm/root/usr/bin/passenger-status
>
> /opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.18/bin/passenger-status
> /opt/theforeman/tfm/root/usr/share/man/man8/passenger-status.8.gz
>

This set of passenger libraries are used for running the Foreman web
application under Apache within the SCL. To run the passenger-status
command for the SCL, you'd need to enable the SCL and run it:

scl enable tfm '/opt/theforeman/tfm/root/usr/bin/passenger-status'


> /usr/sbin/passenger-status
> /usr/share/man/man8/passenger-status.8.gz
>

This set of passenger libraries are used for running the puppetmaster that
is installed on the server by default which is running outside the SC and
should work like normal (barring a bug in newer passenger).


> [root@katello-test ~]# /opt/theforeman/tfm/root/usr/bin/passenger-status
> /opt/rh/ruby193/root/usr/bin/ruby: error while loading shared libraries:
> libruby.so.1.9: cannot open shared object file: No such file or directory
> [root@katello-test ~]#
> /opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.18/bin/passenger-status
> *** Phusion Passenger: no passenger_native_support.so found for the
> current Ruby interpreter. Compiling one (set
> PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY=0 to disable)...
> # mkdir -p /root/.passenger/native_support/4.0.18/ruby-2.0.0-x86_64-linux
> # cd /root/.passenger/native_support/4.0.18/ruby-2.0.0-x86_64-linux
> # /usr/bin/ruby
> '/opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.18/ruby_extension_source/extconf.rb'
> /usr/bin/ruby: No such file or directory --
> /opt/theforeman/tfm/root/usr/share/gems/gems/passenger-4.0.18/ruby_extension_source/extconf.rb
> (LoadError)
> Compilation failed.
> ---
> Ruby native_support extension not loaded. Continuing without
> native_support.
> ERROR: Phusion Passenger doesn't seem to be running.
>
>
> So the question is which ones does Katello really need since they were
> both installed during the installer and how do I get this command working
> again without breaking the underlying app?
>
> --
> 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 foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] [Katello 3.0] foreman-installer --help fails ("no documentation found for manifest")

[Eric D Helms]

Please report as an issue with your traceback so that the right developers
can take a look.

On Wed, Jul 6, 2016 at 2:37 AM, Marvin Beckers 
wrote:

> Hello everybody,
>
> recently I've been trying to apply some changes to our Katello 3.0 setup
> through foreman-installer and noticed it fails to run. The last time it
> used to work was June 27th (according to
> /var/log/foreman-installer/foreman.log) when I updated Katello related
> packages and run `foreman-installer --scenario=katello --upgrade`
> afterwards to make sure everything was properly updated. This was the yum
> update on June 27th:
>
> Packages Altered:
> Updated NetworkManager-1:1.0.6-29.el7_2.x86_64   @updates
> Update 1:1.0.6-30.el7_2.x86_64   @updates
> Updated NetworkManager-libnm-1:1.0.6-29.el7_2.x86_64 @updates
> Update   1:1.0.6-30.el7_2.x86_64 @updates
> Updated NetworkManager-team-1:1.0.6-29.el7_2.x86_64  @updates
> Update  1:1.0.6-30.el7_2.x86_64  @updates
> Updated NetworkManager-tui-1:1.0.6-29.el7_2.x86_64   @updates
> Update 1:1.0.6-30.el7_2.x86_64   @updates
> Updated device-mapper-7:1.02.107-5.el7_2.2.x86_64@updates
> Update7:1.02.107-5.el7_2.4.x86_64@updates
> Updated device-mapper-event-7:1.02.107-5.el7_2.2.x86_64  @updates
> Update  7:1.02.107-5.el7_2.4.x86_64  @updates
> Updated device-mapper-event-libs-7:1.02.107-5.el7_2.2.x86_64 @updates
> Update   7:1.02.107-5.el7_2.4.x86_64 @updates
> Updated device-mapper-libs-7:1.02.107-5.el7_2.2.x86_64   @updates
> Update 7:1.02.107-5.el7_2.4.x86_64   @updates
> Updated dracut-033-360.el7_2.x86_64  @updates
> Update 033-360.el7_2.1.x86_64@updates
> Updated dracut-config-rescue-033-360.el7_2.x86_64@updates
> Update   033-360.el7_2.1.x86_64  @updates
> Updated dracut-network-033-360.el7_2.x86_64  @updates
> Update 033-360.el7_2.1.x86_64@updates
> Updated epel-release-7-6.noarch  @
> /epel-release-latest-7.noarch
> Update   7-7.noarch  @epel
> Updated foreman-1.11.2-1.el7.noarch  @foreman
> Update  1.11.3-1.el7.noarch  @foreman
> Updated foreman-compute-1.11.2-1.el7.noarch  @foreman
> Update  1.11.3-1.el7.noarch  @foreman
> Updated foreman-debug-1.11.2-1.el7.noarch@foreman
> Update1.11.3-1.el7.noarch@foreman
> Updated foreman-installer-1:1.11.2-1.el7.noarch  @foreman
> Update1:1.11.3-1.el7.noarch  @foreman
> Updated foreman-installer-katello-3.0.0-10.rc8.el7.noarch@katello
> Update3.0.2-1.el7.noarch @katello
> Updated foreman-postgresql-1.11.2-1.el7.noarch   @foreman
> Update 1.11.3-1.el7.noarch   @foreman
> Updated foreman-proxy-1.11.2-1.el7.noarch@foreman
> Update1.11.3-1.el7.noarch@foreman
> Updated foreman-release-1.11.2-1.el7.noarch  @/foreman
> -release
> Update  1.11.3-1.el7.noarch  @foreman
> Updated foreman-selinux-1.11.2-1.el7.noarch  @foreman
> Update  1.11.3-1.el7.noarch  @foreman
> Updated foreman-vmware-1.11.2-1.el7.noarch   @foreman
> Update 1.11.3-1.el7.noarch   @foreman
> Updated iproute-3.10.0-54.el7.x86_64 @anaconda
> Update  3.10.0-54.el7_2.1.x86_64 @updates
> Updated katello-3.0.0-8.rc8.el7.noarch   @katello
> Update  3.0.0-9.el7.noarch   @katello
> Updated katello-common-3.0.0-8.rc8.el7.noarch@katello
> Update 3.0.0-9.el7.noarch@katello
> Updated katello-debug-3.0.0-8.rc8.el7.noarch @katello
> Update3.0.0-9.el7.noarch @katello
> Updated katello-installer-base-3.0.0-10.rc8.el7.noarch   @katello
> Update 3.0.2-1.el7.noarch@katello
> Updated katello-repos-3.0.0-2.el7.noarch @/katello
> -repos-latest
> Update3.0.0-3.el7.noarch @katello
> Updated 

Re: [foreman-users] Is it possible to 'audit' pulp based on expected views in katello?

[Greg Swift]

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  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  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 foreman-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> 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 foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> 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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Katello 3.0.2 (Saison) Released

[Edgars M.]

Hi

I still cannot install new Katello because of this 
issue: http://projects.theforeman.org/issues/15507

It fails every time.. Does anyone know workaround?

Edgars

trešdiena, 2016. gada 6. jūlijs 22:51:48 UTC+2, Eric Helms rakstīja:
>
> Katello 3.0.2 has been released to supply bug fixes and major upgrade 
> issues found by some awesome users. Please see the changelog for more 
> information (
> https://github.com/Katello/katello/blob/KATELLO-3.0/CHANGELOG.md). 
>
> Installation 
>  
>
> For installation, please see the instructions at: 
>
>Server: http://www.katello.org/docs/3.0/installation/index.html 
>  
>Capsule: http://www.katello.org/docs/3.0/installation/capsule.html 
>  
>
> Bug reporting 
> = 
> If you come across a bug in your testing, please file it and note the 
> version of Katello that you're using in the report and set the release 
> to 3.0.2. 
>
>http://projects.theforeman.org/projects/katello/issues/new 
>
>
> -- 
> Eric D. Helms
> Red Hat Engineering
> Ph.D. Student - North Carolina State University
>

-- 
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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.