Issue on host deletion

Lupindeterd · January 26, 2015, 10:19pm

Hi,

I'm having issue when deleting a host as it's stall (waiting in webgui) and
all I can see on logs(debug mode) are.

web UI delete log

Started DELETE "/hosts/server.fqdn" for 192.168.108.180 at 2015-01-27
09:12:46 +1300

Processing by HostsController#destroy as HTML

API delete log

Started DELETE "/api/v2/hosts/server.fqdn" for 10.102.1.6 at 2015-01-27
10:55:37 +1300

Processing by Api::V2::HostsController#destroy as JSON

Parameters: {"apiv"=>"v2", "id"=>"server.fqdn", :host=>{}}

Authorized user admin(Admin User)

Connecting to database specified by database.yml

Creating scope :completer_scope. Overwriting existing method
Organization.completer_scope.

Creating scope :completer_scope. Overwriting existing method
Location.completer_scope.

To work-around, what I do is to delete the host in VMWare host and wait
for few hours as the Foreman seems to run internal housekeeping.

Any clue, and what's this housekeeping can I invoke this manually?

Cheers

Lupin

dLobatog · January 27, 2015, 8:33am

Hi Lupin

Could you give us numbers about the number of reports & logs these
hosts have? That can currently slow down the host deletion
significantly, there is a pull request to Foreman core now that is
meant to address that. https://github.com/theforeman/foreman/pull/1907

Best,

···

On Mon, Jan 26, 2015 at 11:19 PM, wrote: > Hi, > > I'm having issue when deleting a host as it's stall (waiting in webgui) and > all I can see on logs(debug mode) are. > > ##### web UI delete log ############# > > Started DELETE "/hosts/server.fqdn" for 192.168.108.180 at 2015-01-27 > 09:12:46 +1300 > > Processing by HostsController#destroy as HTML > > > ##### API delete log ##### > > Started DELETE "/api/v2/hosts/server.fqdn" for 10.102.1.6 at 2015-01-27 > 10:55:37 +1300 > > Processing by Api::V2::HostsController#destroy as JSON > > Parameters: {"apiv"=>"v2", "id"=>"server.fqdn", :host=>{}} > > Authorized user admin(Admin User) > > Connecting to database specified by database.yml > > Creating scope :completer_scope. Overwriting existing method > Organization.completer_scope. > > Creating scope :completer_scope. Overwriting existing method > Location.completer_scope. > > To work-around, what I do is to delete the host in VMWare host and wait for > few hours as the Foreman seems to run internal housekeeping. > > > Any clue, and what's this housekeeping can I invoke this manually? > > > Cheers > > Lupin > > -- > 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+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.

–
Daniel Lobato

@elobatoss
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30

Lupindeterd · January 27, 2015, 9:09pm

>
> Hi Lupin
>
> Could you give us numbers about the number of reports & logs these
> hosts have? That can currently slow down the host deletion
> significantly, there is a pull request to Foreman core now that is
> meant to address that. https://github.com/theforeman/foreman/pull/1907
>

The host was been cleaned up by Foreman so I wasn't able to see the number
of reports, one thing I noticed however is that seems auto delete by
Foreman was quick (or it was just coincidence) after I did a "puppet node
deactivate node_name".

Also, thing to note is that this particular host is exporting/importing
resources (sshkeys).

Cheers

···

On Tuesday, January 27, 2015 at 9:33:41 PM UTC+13, Daniel Lobato wrote:

Best,

On Mon, Jan 26, 2015 at 11:19 PM, <lupin...@gmail.com <javascript:>> > wrote:

Hi,

I’m having issue when deleting a host as it’s stall (waiting in webgui)
and
all I can see on logs(debug mode) are.

web UI delete log

Started DELETE “/hosts/server.fqdn” for 192.168.108.180 at 2015-01-27
09:12:46 +1300

Processing by HostsController#destroy as HTML

API delete log

Started DELETE “/api/v2/hosts/server.fqdn” for 10.102.1.6 at 2015-01-27
10:55:37 +1300

Processing by Api::V2::HostsController#destroy as JSON

Parameters: {“apiv”=>“v2”, “id”=>“server.fqdn”, :host=>{}}

Authorized user admin(Admin User)

Connecting to database specified by database.yml

Creating scope :completer_scope. Overwriting existing method
Organization.completer_scope.

Creating scope :completer_scope. Overwriting existing method
Location.completer_scope.

To work-around, what I do is to delete the host in VMWare host and wait
for
few hours as the Foreman seems to run internal housekeeping.

Any clue, and what’s this housekeeping can I invoke this manually?

Cheers

Lupin

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

–
Daniel Lobato

@elobatoss
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30

Lupindeterd · January 27, 2015, 10:13pm

I tried to delete again, same issue the host got 86 reports and have
exported/imported (sshkey)

···

On Wednesday, January 28, 2015 at 10:09:08 AM UTC+13, lupin...@gmail.com wrote: > > > > On Tuesday, January 27, 2015 at 9:33:41 PM UTC+13, Daniel Lobato wrote: >> >> Hi Lupin >> >> Could you give us numbers about the number of reports & logs these >> hosts have? That can currently slow down the host deletion >> significantly, there is a pull request to Foreman core now that is >> meant to address that. https://github.com/theforeman/foreman/pull/1907 >> > > The host was been cleaned up by Foreman so I wasn't able to see the > number of reports, one thing I noticed however is that seems auto delete by > Foreman was quick (or it was just coincidence) after I did a "puppet node > deactivate node_name". > > Also, thing to note is that this particular host is exporting/importing > resources (sshkeys). > > Cheers > > >> Best, >> >> On Mon, Jan 26, 2015 at 11:19 PM, wrote: >> > Hi, >> > >> > I'm having issue when deleting a host as it's stall (waiting in webgui) >> and >> > all I can see on logs(debug mode) are. >> > >> > ##### web UI delete log ############# >> > >> > Started DELETE "/hosts/server.fqdn" for 192.168.108.180 at 2015-01-27 >> > 09:12:46 +1300 >> > >> > Processing by HostsController#destroy as HTML >> > >> > >> > ##### API delete log ##### >> > >> > Started DELETE "/api/v2/hosts/server.fqdn" for 10.102.1.6 at 2015-01-27 >> > 10:55:37 +1300 >> > >> > Processing by Api::V2::HostsController#destroy as JSON >> > >> > Parameters: {"apiv"=>"v2", "id"=>"server.fqdn", :host=>{}} >> > >> > Authorized user admin(Admin User) >> > >> > Connecting to database specified by database.yml >> > >> > Creating scope :completer_scope. Overwriting existing method >> > Organization.completer_scope. >> > >> > Creating scope :completer_scope. Overwriting existing method >> > Location.completer_scope. >> > >> > To work-around, what I do is to delete the host in VMWare host and >> wait for >> > few hours as the Foreman seems to run internal housekeeping. >> > >> > >> > Any clue, and what's this housekeeping can I invoke this manually? >> > >> > >> > Cheers >> > >> > Lupin >> > >> > -- >> > 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-user...@googlegroups.com. >> > To post to this group, send email to forema...@googlegroups.com. >> > Visit this group at http://groups.google.com/group/foreman-users. >> > For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> Daniel Lobato >> >> @elobatoss >> blog.daniellobato.me >> daniellobato.me >> >> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 >> >

Jorick_Astrego · January 28, 2015, 12:20pm

We also have deleted hosts still in the database. I've deleted them an
hour ago and they were instantly removed from the interface.

I now cannot provision the host again with the same name and MAC's etc
because of conflicts. Still running "foreman-1.6.3-1.el6.noarch" because
it's tied to Katello 2.0.

One of the hosts I provisioned yesterday and deleted today, so there
shouldn't be that many:

 65 | gluster-test1.netbulae.test |              
&gt;                     &gt;                 &gt; 2015-01-28 12:16:13       
&gt; 2015-01-28 12:16:15.222642 |                | 2015-01-28
11:16:19.402211
 &gt;                   &gt;                                    &gt;       
&gt;         12288 |           |                 |                   
&gt;                &gt;           &gt;           &gt;           &gt; f
     &gt;         &gt;      &gt;                            &gt;         
&gt;              &gt;          &gt;            &gt; t       |                 
1 | f       |           |            |      |              
      &gt;               1 |                        |         
&gt;                 &gt;             &gt; Host::Managed |     |         
&gt;                    &gt;                  &gt;                 


foreman=# select * from reports where host_id=65;
  id  | host_id |     reported_at     |         created_at        
&gt;         updated_at         | status |                   
metrics

···

------+---------+---------------------+----------------------------+----------------------------+--------+------------------------------------------------ 9569 | 65 | 2015-01-28 11:46:13 | 2015-01-28 11:46:15.565636 | 2015-01-28 11:46:15.565636 | 12288 | --- !ruby/hash:ActionController::Parameters {}

:
 9561 |      65 | 2015-01-28 11:16:13 | 2015-01-28 11:16:19.46055  |
2015-01-28 11:16:19.46055  |  12288 | ---
!ruby/hash:ActionController::Parameters {}
                                                                                                        
:
(2 rows)

And another:

foreman=# select * from reports where host_id=69;
  id  | host_id |     reported_at     |         created_at        
>         updated_at         | status |                   
metrics                    
------+---------+---------------------+----------------------------+----------------------------+--------+------------------------------------------------
 9575 |      69 | 2015-01-28 12:04:29 | 2015-01-28 12:04:32.780189 |
2015-01-28 12:04:32.780189 |  12288 | ---
!ruby/hash:ActionController::Parameters {}
                                                                                                        
:
 9567 |      69 | 2015-01-28 11:34:29 | 2015-01-28 11:34:32.695707 |
2015-01-28 11:34:32.695707 |  12288 | ---
!ruby/hash:ActionController::Parameters {}
                                                                                                        
:
(2 rows)

How do I select the reports from the specific host?

foreman=# select * from logs where host_id=69;
ERROR:  column "host_id" does not exist
LINE 1: select * from logs where host_id=69;

I now resorted to manually cleaning up the datbase but that’s a pain in
the b*t

cheecrs,

Jorick

On 01/27/2015 11:13 PM, lupindeterd@gmail.com wrote:

I tried to delete again, same issue the host got 86 reports and have
exported/imported (sshkey)

On Wednesday, January 28, 2015 at 10:09:08 AM UTC+13, > lupin...@gmail.com wrote:

On Tuesday, January 27, 2015 at 9:33:41 PM UTC+13, Daniel Lobato >     wrote:

    Hi Lupin

    Could you give us numbers about the number of reports & logs
    these
    hosts have? That can currently slow down the host deletion
    significantly, there is a pull request to Foreman core now
    that is
    meant to address that.
    https://github.com/theforeman/foreman/pull/1907
    <https://github.com/theforeman/foreman/pull/1907>


 The host was been cleaned up by Foreman so I wasn't able to see
the number of reports, one thing I noticed however is that seems
auto delete by Foreman was quick (or it was just coincidence)
after I did a "puppet node deactivate node_name".

Also, thing to note is that this particular host is
exporting/importing resources (sshkeys).

Cheers


    Best,

    On Mon, Jan 26, 2015 at 11:19 PM,  <lupin...@gmail.com> wrote:
    > Hi,
    >
    > I'm having issue when deleting a host as it's stall (waiting
    in webgui) and
    > all I can see on logs(debug mode) are.
    >
    > ##### web UI delete log #############
    >
    > Started DELETE "/hosts/server.fqdn" for 192.168.108.180 at
    2015-01-27
    > 09:12:46 +1300
    >
    > Processing by HostsController#destroy as HTML
    >
    >
    > ##### API delete log #####
    >
    > Started DELETE "/api/v2/hosts/server.fqdn" for 10.102.1.6 at
    2015-01-27
    > 10:55:37 +1300
    >
    > Processing by Api::V2::HostsController#destroy as JSON
    >
    >   Parameters: {"apiv"=>"v2", "id"=>"server.fqdn", :host=>{}}
    >
    > Authorized user admin(Admin User)
    >
    > Connecting to database specified by database.yml
    >
    > Creating scope :completer_scope. Overwriting existing method
    > Organization.completer_scope.
    >
    > Creating scope :completer_scope. Overwriting existing method
    > Location.completer_scope.
    >
    >  To work-around, what I do is to delete the host in VMWare
    host and wait for
    > few hours as the Foreman seems to run internal housekeeping.
    >
    >
    > Any clue, and what's this housekeeping can I invoke this
    manually?
    >
    >
    > Cheers
    >
    > Lupin
    >
    > --
    > 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-user...@googlegroups.com.
    > To post to this group, send email to
    forema...@googlegroups.com.
    > Visit this group at
    http://groups.google.com/group/foreman-users
    <http://groups.google.com/group/foreman-users>.
    > For more options, visit https://groups.google.com/d/optout
    <https://groups.google.com/d/optout>.



    -- 
    Daniel Lobato

    @elobatoss
    blog.daniellobato.me <http://blog.daniellobato.me>
    daniellobato.me <http://daniellobato.me>

    GPG:
    http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
    <http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30>

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

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts

Tel: 053 20 30 270 	info@netbulae.eu 	Staalsteden 4-3A 	KvK 08198180
Fax: 053 20 30 271 	www.netbulae.eu 	7547 TA Enschede 	BTW NL821234584B01

Jorick_Astrego · January 28, 2015, 2:42pm

Sorry to hijack the thread. It's a different problem than the one you
are experiencing. Changed my subject…

···

On 01/28/2015 01:20 PM, Jorick Astrego wrote: > We also have deleted hosts still in the database. I've deleted them an > hour ago and they were instantly removed from the interface. > > I now cannot provision the host again with the same name and MAC's etc > because of conflicts. Still running "foreman-1.6.3-1.el6.noarch" > because it's tied to Katello 2.0. > > > One of the hosts I provisioned yesterday and deleted today, so there > shouldn't be that many: > > 65 | gluster-test1.netbulae.test | > > > > 2015-01-28 > 12:16:13 | 2015-01-28 12:16:15.222642 | | > 2015-01-28 11:16:19.402211 > > > > > > 12288 | | | > > > > > > f > > > > > > > > > > t > > 1 | f | | | > > > > 1 | | > > > > Host::Managed | | > > > > > > > foreman=# select * from reports where host_id=65; > id | host_id | reported_at | created_at > > updated_at | status | > metrics > ------+---------+---------------------+----------------------------+----------------------------+--------+------------------------------------------------ > 9569 | 65 | 2015-01-28 11:46:13 | 2015-01-28 11:46:15.565636 > > 2015-01-28 11:46:15.565636 | 12288 | --- > !ruby/hash:ActionController::Parameters {} > > : > 9561 | 65 | 2015-01-28 11:16:13 | 2015-01-28 11:16:19.46055 > > 2015-01-28 11:16:19.46055 | 12288 | --- > !ruby/hash:ActionController::Parameters {} > > : > (2 rows) > > And another: > > > foreman=# select * from reports where host_id=69; > id | host_id | reported_at | created_at > > updated_at | status | > metrics > ------+---------+---------------------+----------------------------+----------------------------+--------+------------------------------------------------ > 9575 | 69 | 2015-01-28 12:04:29 | 2015-01-28 12:04:32.780189 > > 2015-01-28 12:04:32.780189 | 12288 | --- > !ruby/hash:ActionController::Parameters {} > > : > 9567 | 69 | 2015-01-28 11:34:29 | 2015-01-28 11:34:32.695707 > > 2015-01-28 11:34:32.695707 | 12288 | --- > !ruby/hash:ActionController::Parameters {} > > : > (2 rows) > > How do I select the reports from the specific host? > > foreman=# select * from logs where host_id=69; > ERROR: column "host_id" does not exist > LINE 1: select * from logs where host_id=69; > > I now resorted to manually cleaning up the datbase but that's a pain > in the b*t > > cheecrs, > > Jorick > > On 01/27/2015 11:13 PM, lupindeterd@gmail.com wrote: >> I tried to delete again, same issue the host got 86 reports and have >> exported/imported (sshkey) >> >> On Wednesday, January 28, 2015 at 10:09:08 AM UTC+13, >> lupin...@gmail.com wrote: >> >> >> >> On Tuesday, January 27, 2015 at 9:33:41 PM UTC+13, Daniel Lobato >> wrote: >> >> Hi Lupin >> >> Could you give us numbers about the number of reports & logs >> these >> hosts have? That can currently slow down the host deletion >> significantly, there is a pull request to Foreman core now >> that is >> meant to address that. >> https://github.com/theforeman/foreman/pull/1907 >> >> >> >> The host was been cleaned up by Foreman so I wasn't able to see >> the number of reports, one thing I noticed however is that seems >> auto delete by Foreman was quick (or it was just coincidence) >> after I did a "puppet node deactivate node_name". >> >> Also, thing to note is that this particular host is >> exporting/importing resources (sshkeys). >> >> Cheers >> >> >> Best, >> >> On Mon, Jan 26, 2015 at 11:19 PM, wrote: >> > Hi, >> > >> > I'm having issue when deleting a host as it's stall >> (waiting in webgui) and >> > all I can see on logs(debug mode) are. >> > >> > ##### web UI delete log ############# >> > >> > Started DELETE "/hosts/server.fqdn" for 192.168.108.180 at >> 2015-01-27 >> > 09:12:46 +1300 >> > >> > Processing by HostsController#destroy as HTML >> > >> > >> > ##### API delete log ##### >> > >> > Started DELETE "/api/v2/hosts/server.fqdn" for 10.102.1.6 >> at 2015-01-27 >> > 10:55:37 +1300 >> > >> > Processing by Api::V2::HostsController#destroy as JSON >> > >> > Parameters: {"apiv"=>"v2", "id"=>"server.fqdn", :host=>{}} >> > >> > Authorized user admin(Admin User) >> > >> > Connecting to database specified by database.yml >> > >> > Creating scope :completer_scope. Overwriting existing method >> > Organization.completer_scope. >> > >> > Creating scope :completer_scope. Overwriting existing method >> > Location.completer_scope. >> > >> > To work-around, what I do is to delete the host in VMWare >> host and wait for >> > few hours as the Foreman seems to run internal housekeeping. >> > >> > >> > Any clue, and what's this housekeeping can I invoke this >> manually? >> > >> > >> > Cheers >> > >> > Lupin >> > >> > -- >> > 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-user...@googlegroups.com. >> > To post to this group, send email to >> forema...@googlegroups.com. >> > Visit this group at >> http://groups.google.com/group/foreman-users >> . >> > For more options, visit https://groups.google.com/d/optout >> . >> >> >> >> -- >> Daniel Lobato >> >> @elobatoss >> blog.daniellobato.me >> daniellobato.me >> >> GPG: >> http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 >> >> >> >> -- >> 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+unsubscribe@googlegroups.com >> . >> To post to this group, send email to foreman-users@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. > > > > > Met vriendelijke groet, With kind regards, > > Jorick Astrego* > > Netbulae Virtualization Experts * > ------------------------------------------------------------------------ > Tel: 053 20 30 270 info@netbulae.eu Staalsteden 4-3A KvK 08198180 > Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 > > > ------------------------------------------------------------------------ > > -- > 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+unsubscribe@googlegroups.com > . > To post to this group, send email to foreman-users@googlegroups.com > . > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.

Met vriendelijke groet, With kind regards,

Jorick Astrego

Netbulae Virtualization Experts

Tel: 053 20 30 270 	info@netbulae.eu 	Staalsteden 4-3A 	KvK 08198180
Fax: 053 20 30 271 	www.netbulae.eu 	7547 TA Enschede 	BTW NL821234584B01

Lupindeterd · January 29, 2015, 8:42pm

Hi,

Is there an automated settings to limit the number of logs on the logs
table?

In this particular system a
"SELECT COUNT(*) FROM logs WHERE report_id IN ( SELECT id FROM reports
WHERE host_id = xxx);

got a "count | 65858" and this particular system was only up for two days.

Deleting logs take ages to complete.

TIA,
Lupin

···

On Thursday, January 29, 2015 at 3:43:27 AM UTC+13, Jorick Astrego wrote: > > Sorry to hijack the thread. It's a different problem than the one you are > experiencing. Changed my subject... > > > On 01/28/2015 01:20 PM, Jorick Astrego wrote: > > We also have deleted hosts still in the database. I've deleted them an > hour ago and they were instantly removed from the interface., > > I now cannot provision the host again with the same name and MAC's etc > because of conflicts. Still running "foreman-1.6.3-1.el6.noarch" because > it's tied to Katello 2.0. > > > One of the hosts I provisioned yesterday and deleted today, so there > shouldn't be that many: > > 65 | gluster-test1.netbulae.test | | > > > 2015-01-28 12:16:13 | 2015-01-28 12:16:15.222642 > > > 2015-01-28 11:16:19.402211 > > > > > > 12288 | | | > > > > > > f > > > > > > > > > > t | 1 | > f | | | | > > 1 | | > > > > Host::Managed | | > > > > > > > foreman=# select * from reports where host_id=65; > id | host_id | reported_at | created_at > > updated_at | status | > metrics > > ------+---------+---------------------+----------------------------+----------------------------+--------+------------------------------------------------ > 9569 | 65 | 2015-01-28 11:46:13 | 2015-01-28 11:46:15.565636 | > 2015-01-28 11:46:15.565636 | 12288 | --- > !ruby/hash:ActionController::Parameters {} > > : > 9561 | 65 | 2015-01-28 11:16:13 | 2015-01-28 11:16:19.46055 | > 2015-01-28 11:16:19.46055 | 12288 | --- > !ruby/hash:ActionController::Parameters {} > > : > (2 rows) > > And another: > > > foreman=# select * from reports where host_id=69; > id | host_id | reported_at | created_at > > updated_at | status | > metrics > > ------+---------+---------------------+----------------------------+----------------------------+--------+------------------------------------------------ > 9575 | 69 | 2015-01-28 12:04:29 | 2015-01-28 12:04:32.780189 | > 2015-01-28 12:04:32.780189 | 12288 | --- > !ruby/hash:ActionController::Parameters {} > > : > 9567 | 69 | 2015-01-28 11:34:29 | 2015-01-28 11:34:32.695707 | > 2015-01-28 11:34:32.695707 | 12288 | --- > !ruby/hash:ActionController::Parameters {} > > : > (2 rows) > > How do I select the reports from the specific host? > > foreman=# select * from logs where host_id=69; > ERROR: column "host_id" does not exist > LINE 1: select * from logs where host_id=69; > > I now resorted to manually cleaning up the datbase but that's a pain in > the b*t > > cheecrs, > > Jorick > > On 01/27/2015 11:13 PM, lupin...@gmail.com wrote: > > I tried to delete again, same issue the host got 86 reports and have > exported/imported (sshkey) > > On Wednesday, January 28, 2015 at 10:09:08 AM UTC+13, lupin...@gmail.com > wrote: >> >> >> >> On Tuesday, January 27, 2015 at 9:33:41 PM UTC+13, Daniel Lobato wrote: >>> >>> Hi Lupin >>> >>> Could you give us numbers about the number of reports & logs these >>> hosts have? That can currently slow down the host deletion >>> significantly, there is a pull request to Foreman core now that is >>> meant to address that. https://github.com/theforeman/foreman/pull/1907 >>> >> >> The host was been cleaned up by Foreman so I wasn't able to see the >> number of reports, one thing I noticed however is that seems auto delete by >> Foreman was quick (or it was just coincidence) after I did a "puppet node >> deactivate node_name". >> >> Also, thing to note is that this particular host is exporting/importing >> resources (sshkeys). >> >> Cheers >> >> >>> Best, >>> >>> On Mon, Jan 26, 2015 at 11:19 PM, wrote: >>> > Hi, >>> > >>> > I'm having issue when deleting a host as it's stall (waiting in >>> webgui) and >>> > all I can see on logs(debug mode) are. >>> > >>> > ##### web UI delete log ############# >>> > >>> > Started DELETE "/hosts/server.fqdn" for 192.168.108.180 at 2015-01-27 >>> > 09:12:46 +1300 >>> > >>> > Processing by HostsController#destroy as HTML >>> > >>> > >>> > ##### API delete log ##### >>> > >>> > Started DELETE "/api/v2/hosts/server.fqdn" for 10.102.1.6 at >>> 2015-01-27 >>> > 10:55:37 +1300 >>> > >>> > Processing by Api::V2::HostsController#destroy as JSON >>> > >>> > Parameters: {"apiv"=>"v2", "id"=>"server.fqdn", :host=>{}} >>> > >>> > Authorized user admin(Admin User) >>> > >>> > Connecting to database specified by database.yml >>> > >>> > Creating scope :completer_scope. Overwriting existing method >>> > Organization.completer_scope. >>> > >>> > Creating scope :completer_scope. Overwriting existing method >>> > Location.completer_scope. >>> > >>> > To work-around, what I do is to delete the host in VMWare host and >>> wait for >>> > few hours as the Foreman seems to run internal housekeeping. >>> > >>> > >>> > Any clue, and what's this housekeeping can I invoke this manually? >>> > >>> > >>> > Cheers >>> > >>> > Lupin >>> > >>> > -- >>> > 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-user...@googlegroups.com. >>> > To post to this group, send email to forema...@googlegroups.com. >>> > Visit this group at http://groups.google.com/group/foreman-users. >>> > For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> -- >>> Daniel Lobato >>> >>> @elobatoss >>> blog.daniellobato.me >>> daniellobato.me >>> >>> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 >>> >> -- > 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-user...@googlegroups.com . > To post to this group, send email to forema...@googlegroups.com > . > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > > > > > > Met vriendelijke groet, With kind regards, > > Jorick Astrego > > * Netbulae Virtualization Experts * > ------------------------------ > Tel: 053 20 30 270 in...@netbulae.eu Staalsteden 4-3A KvK > 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW > NL821234584B01 > ------------------------------ > > -- > 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-user...@googlegroups.com . > To post to this group, send email to forema...@googlegroups.com > . > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > > > > > > Met vriendelijke groet, With kind regards, > > Jorick Astrego > > *Netbulae Virtualization Experts * > ------------------------------ > Tel: 053 20 30 270 in...@netbulae.eu Staalsteden 4-3A KvK > 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW > NL821234584B01 > ------------------------------ > >