Unable delete the discovered hosts from foreman

Anil_Reddy · February 20, 2015, 4:04pm

Hi,

I am unable delete the discovered hosts from foreman, when I attempt to do
it, I am getting following error. I have also ensured environment set to
non discover (production) and cancelled any build in progress.

Warning!

ERROR: update or delete on table "hosts" violates foreign key constraint
"discovery_attribute_sets_host_id_fk" on table "discovery_attribute_sets"
DETAIL: Key (id)=(2) is still referenced from table
"discovery_attribute_sets".

Installed foreman-version:
foreman-1.7.2-1.el6.noarch
ruby193-rubygem-foreman_discovery-2.0.0-0.1.rc2.el6.noarch

Any help appreciated.

Thanks
Anil

Ori_Rabin · February 23, 2015, 12:20pm

Hi Anil,
Does this happen only for hosts you discovered before discovery 2.0? or
only new ones? both?
If you can provide a little bit of the logs before the error that would
help.
You can report the issue and put the details their or answer my questions
here.

···

On Fri, Feb 20, 2015 at 6:04 PM, Anil Reddy wrote:

Hi,

I am unable delete the discovered hosts from foreman, when I attempt to do
it, I am getting following error. I have also ensured environment set to
non discover (production) and cancelled any build in progress.

Warning!

ERROR: update or delete on table “hosts” violates foreign key constraint
"discovery_attribute_sets_host_id_fk" on table “discovery_attribute_sets"
DETAIL: Key (id)=(2) is still referenced from table
"discovery_attribute_sets”.

Installed foreman-version:
foreman-1.7.2-1.el6.noarch
ruby193-rubygem-foreman_discovery-2.0.0-0.1.rc2.el6.noarch

Any help appreciated.

Thanks
Anil

–
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.

Anil_Reddy · February 23, 2015, 3:16pm

Ori,

Thank you for looking into it, this is a brand new install and I have tried
multiple times installing from scratch and it still errors out same way.
Any further help appreciated.

production.log shows following:

Started POST
"/hosts/submit_multiple_destroy?host_ids%5B%5D=4&host_ids%5B%5D=3" for
10.33.6.109 at 2015-02-23 15:11:19 +0000
Processing by HostsController#submit_multiple_destroy as HTML
Parameters: {"utf8"=>"✓",
"authenticity_token"=>"tYacd6J525A45OaKMxhCivSxVFJShGHu8z6HD1aPhYY=",
"host_ids"=>["4", "3"]}
Operation FAILED: ERROR: update or delete on table "hosts" violates
foreign key constraint "discovery_attribute_sets_host_id_fk" on table
"discovery_attribute_sets"
DETAIL: Key (id)=(3) is still referenced from table
"discovery_attribute_sets".

Rendered common/500.html.erb within layouts/application (4.8ms)
Rendered layouts/base.html.erb (1.2ms)
Completed 500 Internal Server Error in 63ms (Views: 13.0ms | ActiveRecord:
8.8ms)

Web console, trace shows following:

PGError
ERROR: update or delete on table "hosts" violates foreign key constraint
"discovery_attribute_sets_host_id_fk" on table "discovery_attribute_sets"
DETAIL: Key (id)=(3) is still referenced from table
"discovery_attribute_sets".
app/controllers/hosts_controller.rb:431:in block in submit_multiple_destroy' app/controllers/hosts_controller.rb:431:insubmit_multiple_destroy'
app/models/concerns/foreman/thread_session.rb:33:in clear_thread' lib/middleware/catch_json_parse_errors.rb:9:incall'

Thanks
Anil

···

On Mon, Feb 23, 2015 at 7:20 AM, Ori Rabin wrote:

Hi Anil,
Does this happen only for hosts you discovered before discovery 2.0? or
only new ones? both?
If you can provide a little bit of the logs before the error that would
help.
You can report the issue and put the details their or answer my questions
here.

On Fri, Feb 20, 2015 at 6:04 PM, Anil Reddy anil.vatti@gmail.com wrote:

Hi,

I am unable delete the discovered hosts from foreman, when I attempt to
do it, I am getting following error. I have also ensured environment set to
non discover (production) and cancelled any build in progress.

Warning!

ERROR: update or delete on table “hosts” violates foreign key constraint
"discovery_attribute_sets_host_id_fk" on table “discovery_attribute_sets"
DETAIL: Key (id)=(2) is still referenced from table
"discovery_attribute_sets”.

Installed foreman-version:
foreman-1.7.2-1.el6.noarch
ruby193-rubygem-foreman_discovery-2.0.0-0.1.rc2.el6.noarch

Any help appreciated.

Thanks
Anil

–
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.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/NP182Z6qlwA/unsubscribe.
To unsubscribe from this group and all its topics, 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.

Anil_Reddy · February 23, 2015, 4:15pm

Ori,

Another additional information on this.

We have staypuft plugin installed and once we assign the discovered systems
to openstack controller or compute nodes and deploy them, then foreman is
not allowing to delete those hosts.

We have even tried by unassign the hosts from openstack deployment and
results is same.

Thanks
Anil

···

On Mon, Feb 23, 2015 at 10:16 AM, Anil Reddy wrote:

Ori,

Thank you for looking into it, this is a brand new install and I have
tried multiple times installing from scratch and it still errors out same
way. Any further help appreciated.

production.log shows following:

Started POST
"/hosts/submit_multiple_destroy?host_ids%5B%5D=4&host_ids%5B%5D=3" for
10.33.6.109 at 2015-02-23 15:11:19 +0000
Processing by HostsController#submit_multiple_destroy as HTML
Parameters: {“utf8”=>“✓”,
“authenticity_token”=>“tYacd6J525A45OaKMxhCivSxVFJShGHu8z6HD1aPhYY=”,
“host_ids”=>[“4”, “3”]}
Operation FAILED: ERROR: update or delete on table “hosts” violates
foreign key constraint “discovery_attribute_sets_host_id_fk” on table
"discovery_attribute_sets"
DETAIL: Key (id)=(3) is still referenced from table
"discovery_attribute_sets".

Rendered common/500.html.erb within layouts/application (4.8ms)
Rendered layouts/base.html.erb (1.2ms)
Completed 500 Internal Server Error in 63ms (Views: 13.0ms | ActiveRecord:
8.8ms)

Web console, trace shows following:

PGError
ERROR: update or delete on table “hosts” violates foreign key constraint
"discovery_attribute_sets_host_id_fk" on table “discovery_attribute_sets"
DETAIL: Key (id)=(3) is still referenced from table
"discovery_attribute_sets”.
app/controllers/hosts_controller.rb:431:in block in submit_multiple_destroy' app/controllers/hosts_controller.rb:431:insubmit_multiple_destroy’
app/models/concerns/foreman/thread_session.rb:33:in clear_thread' lib/middleware/catch_json_parse_errors.rb:9:incall’

Thanks
Anil

On Mon, Feb 23, 2015 at 7:20 AM, Ori Rabin orrabin@gmail.com wrote:

Hi Anil,
Does this happen only for hosts you discovered before discovery 2.0? or
only new ones? both?
If you can provide a little bit of the logs before the error that would
help.
You can report the issue and put the details their or answer my questions
here.

On Fri, Feb 20, 2015 at 6:04 PM, Anil Reddy anil.vatti@gmail.com wrote:

Hi,

I am unable delete the discovered hosts from foreman, when I attempt to
do it, I am getting following error. I have also ensured environment set to
non discover (production) and cancelled any build in progress.

Warning!

ERROR: update or delete on table “hosts” violates foreign key constraint
"discovery_attribute_sets_host_id_fk" on table “discovery_attribute_sets"
DETAIL: Key (id)=(2) is still referenced from table
"discovery_attribute_sets”.

Installed foreman-version:
foreman-1.7.2-1.el6.noarch
ruby193-rubygem-foreman_discovery-2.0.0-0.1.rc2.el6.noarch

Any help appreciated.

Thanks
Anil

–
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.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/NP182Z6qlwA/unsubscribe.
To unsubscribe from this group and all its topics, 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.

Ori_Rabin · February 24, 2015, 12:36pm

Anil,
It looks like you are using discovery 2.0 RC2, could you check with
discovery 2.0?
Also, if you discover hosts and delete them before assigning anything does
it work?

···

On Mon, Feb 23, 2015 at 6:15 PM, Anil Reddy wrote:

Ori,

Another additional information on this.

We have staypuft plugin installed and once we assign the discovered
systems to openstack controller or compute nodes and deploy them, then
foreman is not allowing to delete those hosts.

We have even tried by unassign the hosts from openstack deployment and
results is same.

Thanks
Anil

On Mon, Feb 23, 2015 at 10:16 AM, Anil Reddy anil.vatti@gmail.com wrote:

Ori,

Thank you for looking into it, this is a brand new install and I have
tried multiple times installing from scratch and it still errors out same
way. Any further help appreciated.

production.log shows following:

Started POST
"/hosts/submit_multiple_destroy?host_ids%5B%5D=4&host_ids%5B%5D=3" for
10.33.6.109 at 2015-02-23 15:11:19 +0000
Processing by HostsController#submit_multiple_destroy as HTML
Parameters: {“utf8”=>“✓”,
“authenticity_token”=>“tYacd6J525A45OaKMxhCivSxVFJShGHu8z6HD1aPhYY=”,
“host_ids”=>[“4”, “3”]}
Operation FAILED: ERROR: update or delete on table “hosts” violates
foreign key constraint “discovery_attribute_sets_host_id_fk” on table
"discovery_attribute_sets"
DETAIL: Key (id)=(3) is still referenced from table
"discovery_attribute_sets".

Rendered common/500.html.erb within layouts/application (4.8ms)
Rendered layouts/base.html.erb (1.2ms)
Completed 500 Internal Server Error in 63ms (Views: 13.0ms |
ActiveRecord: 8.8ms)

Web console, trace shows following:

PGError
ERROR: update or delete on table “hosts” violates foreign key constraint
"discovery_attribute_sets_host_id_fk" on table “discovery_attribute_sets"
DETAIL: Key (id)=(3) is still referenced from table
"discovery_attribute_sets”.
app/controllers/hosts_controller.rb:431:in block in submit_multiple_destroy' app/controllers/hosts_controller.rb:431:insubmit_multiple_destroy’
app/models/concerns/foreman/thread_session.rb:33:in clear_thread' lib/middleware/catch_json_parse_errors.rb:9:incall’

Thanks
Anil

On Mon, Feb 23, 2015 at 7:20 AM, Ori Rabin orrabin@gmail.com wrote:

Hi Anil,
Does this happen only for hosts you discovered before discovery 2.0? or
only new ones? both?
If you can provide a little bit of the logs before the error that would
help.
You can report the issue and put the details their or answer my
questions here.

On Fri, Feb 20, 2015 at 6:04 PM, Anil Reddy anil.vatti@gmail.com >>> wrote:

Hi,

I am unable delete the discovered hosts from foreman, when I attempt to
do it, I am getting following error. I have also ensured environment set to
non discover (production) and cancelled any build in progress.

Warning!

ERROR: update or delete on table “hosts” violates foreign key
constraint “discovery_attribute_sets_host_id_fk” on table
"discovery_attribute_sets" DETAIL: Key (id)=(2) is still referenced from
table “discovery_attribute_sets”.

Installed foreman-version:
foreman-1.7.2-1.el6.noarch
ruby193-rubygem-foreman_discovery-2.0.0-0.1.rc2.el6.noarch

Any help appreciated.

Thanks
Anil

–
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.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/NP182Z6qlwA/unsubscribe.
To unsubscribe from this group and all its topics, 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.

–
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.

Anil_Reddy · February 24, 2015, 8:22pm

Ori,

I am able to deleted the discover hosts before assigning anything, it is
only failing with the error after I have assigned it to openstack install.

Same results with 2.0 as well.

Thanks
Anil

···

On Tue, Feb 24, 2015 at 7:36 AM, Ori Rabin wrote:

Anil,
It looks like you are using discovery 2.0 RC2, could you check with
discovery 2.0?
Also, if you discover hosts and delete them before assigning anything does
it work?

On Mon, Feb 23, 2015 at 6:15 PM, Anil Reddy anil.vatti@gmail.com wrote:

Ori,

Another additional information on this.

We have staypuft plugin installed and once we assign the discovered
systems to openstack controller or compute nodes and deploy them, then
foreman is not allowing to delete those hosts.

We have even tried by unassign the hosts from openstack deployment and
results is same.

Thanks
Anil

On Mon, Feb 23, 2015 at 10:16 AM, Anil Reddy anil.vatti@gmail.com >> wrote:

Ori,

Thank you for looking into it, this is a brand new install and I have
tried multiple times installing from scratch and it still errors out same
way. Any further help appreciated.

production.log shows following:

Started POST
"/hosts/submit_multiple_destroy?host_ids%5B%5D=4&host_ids%5B%5D=3" for
10.33.6.109 at 2015-02-23 15:11:19 +0000
Processing by HostsController#submit_multiple_destroy as HTML
Parameters: {“utf8”=>“✓”,
“authenticity_token”=>“tYacd6J525A45OaKMxhCivSxVFJShGHu8z6HD1aPhYY=”,
“host_ids”=>[“4”, “3”]}
Operation FAILED: ERROR: update or delete on table “hosts” violates
foreign key constraint “discovery_attribute_sets_host_id_fk” on table
"discovery_attribute_sets"
DETAIL: Key (id)=(3) is still referenced from table
"discovery_attribute_sets".

Rendered common/500.html.erb within layouts/application (4.8ms)
Rendered layouts/base.html.erb (1.2ms)
Completed 500 Internal Server Error in 63ms (Views: 13.0ms |
ActiveRecord: 8.8ms)

Web console, trace shows following:

PGError
ERROR: update or delete on table “hosts” violates foreign key constraint
"discovery_attribute_sets_host_id_fk" on table “discovery_attribute_sets"
DETAIL: Key (id)=(3) is still referenced from table
"discovery_attribute_sets”.
app/controllers/hosts_controller.rb:431:in block in submit_multiple_destroy' app/controllers/hosts_controller.rb:431:insubmit_multiple_destroy’
app/models/concerns/foreman/thread_session.rb:33:in clear_thread' lib/middleware/catch_json_parse_errors.rb:9:incall’

Thanks
Anil

On Mon, Feb 23, 2015 at 7:20 AM, Ori Rabin orrabin@gmail.com wrote:

Hi Anil,
Does this happen only for hosts you discovered before discovery 2.0? or
only new ones? both?
If you can provide a little bit of the logs before the error that would
help.
You can report the issue and put the details their or answer my
questions here.

On Fri, Feb 20, 2015 at 6:04 PM, Anil Reddy anil.vatti@gmail.com >>>> wrote:

Hi,

I am unable delete the discovered hosts from foreman, when I attempt
to do it, I am getting following error. I have also ensured environment set
to non discover (production) and cancelled any build in progress.

Warning!

ERROR: update or delete on table “hosts” violates foreign key
constraint “discovery_attribute_sets_host_id_fk” on table
"discovery_attribute_sets" DETAIL: Key (id)=(2) is still referenced from
table “discovery_attribute_sets”.

Installed foreman-version:
foreman-1.7.2-1.el6.noarch
ruby193-rubygem-foreman_discovery-2.0.0-0.1.rc2.el6.noarch

Any help appreciated.

Thanks
Anil

–
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.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/NP182Z6qlwA/unsubscribe
.
To unsubscribe from this group and all its topics, 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.

–
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.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/NP182Z6qlwA/unsubscribe.
To unsubscribe from this group and all its topics, 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.

Ori_Rabin · February 25, 2015, 1:59pm

Anil,

There is now a related fix by lzap and hopefully it will be merged soon:
https://github.com/theforeman/foreman_discovery/pull/161
This fix isn't enough to solve your problem, staypuft needs to change the
code for assigning hosts to use the change.
More information here: http://projects.theforeman.org/issues/9546.
You can open up an issue for staypuft to make the needed change here:
https://bugzilla.redhat.com/buglist.cgi?component=rubygem-staypuft&list_id=3263530&product=Red%20Hat%20OpenStack

···

On Tue, Feb 24, 2015 at 10:22 PM, Anil Reddy wrote:

Ori,

I am able to deleted the discover hosts before assigning anything, it is
only failing with the error after I have assigned it to openstack install.

Same results with 2.0 as well.

Thanks
Anil

On Tue, Feb 24, 2015 at 7:36 AM, Ori Rabin orrabin@gmail.com wrote:

Anil,
It looks like you are using discovery 2.0 RC2, could you check with
discovery 2.0?
Also, if you discover hosts and delete them before assigning anything
does it work?

On Mon, Feb 23, 2015 at 6:15 PM, Anil Reddy anil.vatti@gmail.com wrote:

Ori,

Another additional information on this.

We have staypuft plugin installed and once we assign the discovered
systems to openstack controller or compute nodes and deploy them, then
foreman is not allowing to delete those hosts.

We have even tried by unassign the hosts from openstack deployment and
results is same.

Thanks
Anil

On Mon, Feb 23, 2015 at 10:16 AM, Anil Reddy anil.vatti@gmail.com >>> wrote:

Ori,

Thank you for looking into it, this is a brand new install and I have
tried multiple times installing from scratch and it still errors out same
way. Any further help appreciated.

production.log shows following:

Started POST
“/hosts/submit_multiple_destroy?host_ids%5B%5D=4&host_ids%5B%5D=3” for
10.33.6.109 at 2015-02-23 15:11:19 +0000
Processing by HostsController#submit_multiple_destroy as HTML
Parameters: {“utf8”=>“✓”,
“authenticity_token”=>“tYacd6J525A45OaKMxhCivSxVFJShGHu8z6HD1aPhYY=”,
“host_ids”=>[“4”, “3”]}
Operation FAILED: ERROR: update or delete on table “hosts” violates
foreign key constraint “discovery_attribute_sets_host_id_fk” on table
“discovery_attribute_sets”
DETAIL: Key (id)=(3) is still referenced from table
“discovery_attribute_sets”.

Rendered common/500.html.erb within layouts/application (4.8ms)
Rendered layouts/base.html.erb (1.2ms)
Completed 500 Internal Server Error in 63ms (Views: 13.0ms |
ActiveRecord: 8.8ms)

Web console, trace shows following:

PGError
ERROR: update or delete on table “hosts” violates foreign key
constraint “discovery_attribute_sets_host_id_fk” on table
“discovery_attribute_sets” DETAIL: Key (id)=(3) is still referenced from
table “discovery_attribute_sets”.
app/controllers/hosts_controller.rb:431:in block in submit_multiple_destroy' app/controllers/hosts_controller.rb:431:in submit_multiple_destroy’
app/models/concerns/foreman/thread_session.rb:33:in clear_thread' lib/middleware/catch_json_parse_errors.rb:9:in call’

Thanks
Anil

On Mon, Feb 23, 2015 at 7:20 AM, Ori Rabin orrabin@gmail.com wrote:

Hi Anil,
Does this happen only for hosts you discovered before discovery 2.0?
or only new ones? both?
If you can provide a little bit of the logs before the error that
would help.
You can report the issue and put the details their or answer my
questions here.

On Fri, Feb 20, 2015 at 6:04 PM, Anil Reddy anil.vatti@gmail.com >>>>> wrote:

Hi,

I am unable delete the discovered hosts from foreman, when I attempt
to do it, I am getting following error. I have also ensured environment set
to non discover (production) and cancelled any build in progress.

Warning!

ERROR: update or delete on table “hosts” violates foreign key
constraint “discovery_attribute_sets_host_id_fk” on table
“discovery_attribute_sets” DETAIL: Key (id)=(2) is still referenced from
table “discovery_attribute_sets”.

Installed foreman-version:
foreman-1.7.2-1.el6.noarch
ruby193-rubygem-foreman_discovery-2.0.0-0.1.rc2.el6.noarch

Any help appreciated.

Thanks
Anil

–
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.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/NP182Z6qlwA/unsubscribe
.
To unsubscribe from this group and all its topics, 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.

–
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.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/NP182Z6qlwA/unsubscribe.
To unsubscribe from this group and all its topics, 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.

–
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.

Oleg_Mcnoleg · February 25, 2015, 3:52pm

I have the same error when trying to delete a host provisioned using the
discovery plugin.

foreman_discovery-2.0.0-1.el6.noarch

foreman-1.7.2-1.el6

I love the discovery tool. Will this be fixed into an update to the plugin
I can pull down from the repos?

Thanks,

Anil_Reddy · February 26, 2015, 2:41pm

Thank you Ori, logged a bug with staypuft team.

https://bugzilla.redhat.com/show_bug.cgi?id=1196695

···

On Wed, Feb 25, 2015 at 8:59 AM, Ori Rabin wrote:

Anil,

There is now a related fix by lzap and hopefully it will be merged soon:
https://github.com/theforeman/foreman_discovery/pull/161
This fix isn’t enough to solve your problem, staypuft needs to change the
code for assigning hosts to use the change.
More information here: Refactor #9546: Discovery should provide a convinient method to convert discovered host into managed host (aka provision) - Discovery - Foreman.
You can open up an issue for staypuft to make the needed change here:
https://bugzilla.redhat.com/buglist.cgi?component=rubygem-staypuft&list_id=3263530&product=Red%20Hat%20OpenStack

On Tue, Feb 24, 2015 at 10:22 PM, Anil Reddy anil.vatti@gmail.com wrote:

Ori,

I am able to deleted the discover hosts before assigning anything, it is
only failing with the error after I have assigned it to openstack install.

Same results with 2.0 as well.

Thanks
Anil

On Tue, Feb 24, 2015 at 7:36 AM, Ori Rabin orrabin@gmail.com wrote:

Anil,
It looks like you are using discovery 2.0 RC2, could you check with
discovery 2.0?
Also, if you discover hosts and delete them before assigning anything
does it work?

On Mon, Feb 23, 2015 at 6:15 PM, Anil Reddy anil.vatti@gmail.com >>> wrote:

Ori,

Another additional information on this.

We have staypuft plugin installed and once we assign the discovered
systems to openstack controller or compute nodes and deploy them, then
foreman is not allowing to delete those hosts.

We have even tried by unassign the hosts from openstack deployment and
results is same.

Thanks
Anil

On Mon, Feb 23, 2015 at 10:16 AM, Anil Reddy anil.vatti@gmail.com >>>> wrote:

Ori,

Thank you for looking into it, this is a brand new install and I have
tried multiple times installing from scratch and it still errors out same
way. Any further help appreciated.

production.log shows following:

Started POST
"/hosts/submit_multiple_destroy?host_ids%5B%5D=4&host_ids%5B%5D=3" for
10.33.6.109 at 2015-02-23 15:11:19 +0000
Processing by HostsController#submit_multiple_destroy as HTML
Parameters: {“utf8”=>“✓”,
“authenticity_token”=>“tYacd6J525A45OaKMxhCivSxVFJShGHu8z6HD1aPhYY=”,
“host_ids”=>[“4”, “3”]}
Operation FAILED: ERROR: update or delete on table “hosts” violates
foreign key constraint “discovery_attribute_sets_host_id_fk” on table
"discovery_attribute_sets"
DETAIL: Key (id)=(3) is still referenced from table
"discovery_attribute_sets".

Rendered common/500.html.erb within layouts/application (4.8ms)
Rendered layouts/base.html.erb (1.2ms)
Completed 500 Internal Server Error in 63ms (Views: 13.0ms |
ActiveRecord: 8.8ms)

Web console, trace shows following:

PGError
ERROR: update or delete on table “hosts” violates foreign key
constraint “discovery_attribute_sets_host_id_fk” on table
"discovery_attribute_sets" DETAIL: Key (id)=(3) is still referenced from
table “discovery_attribute_sets”.
app/controllers/hosts_controller.rb:431:in block in submit_multiple_destroy' app/controllers/hosts_controller.rb:431:insubmit_multiple_destroy’
app/models/concerns/foreman/thread_session.rb:33:in clear_thread' lib/middleware/catch_json_parse_errors.rb:9:incall’

Thanks
Anil

On Mon, Feb 23, 2015 at 7:20 AM, Ori Rabin orrabin@gmail.com wrote:

Hi Anil,
Does this happen only for hosts you discovered before discovery 2.0?
or only new ones? both?
If you can provide a little bit of the logs before the error that
would help.
You can report the issue and put the details their or answer my
questions here.

On Fri, Feb 20, 2015 at 6:04 PM, Anil Reddy anil.vatti@gmail.com >>>>>> wrote:

Hi,

I am unable delete the discovered hosts from foreman, when I attempt
to do it, I am getting following error. I have also ensured environment set
to non discover (production) and cancelled any build in progress.

Warning!

ERROR: update or delete on table “hosts” violates foreign key
constraint “discovery_attribute_sets_host_id_fk” on table
"discovery_attribute_sets" DETAIL: Key (id)=(2) is still referenced from
table “discovery_attribute_sets”.

Installed foreman-version:
foreman-1.7.2-1.el6.noarch
ruby193-rubygem-foreman_discovery-2.0.0-0.1.rc2.el6.noarch

Any help appreciated.

Thanks
Anil

–
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.

–
You received this message because you are subscribed to a topic in
the Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/NP182Z6qlwA/unsubscribe
.
To unsubscribe from this group and all its topics, 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.

–
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.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/NP182Z6qlwA/unsubscribe.
To unsubscribe from this group and all its topics, 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.

–
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.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/NP182Z6qlwA/unsubscribe.
To unsubscribe from this group and all its topics, 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.

Ori_Rabin · February 26, 2015, 8:18am

Hi Oleg,
do you use staypuft too or just the discovery plugin?
This will be fixed into an update but if you are using staypuft you will
have to get their fix too.

···

On Wed, Feb 25, 2015 at 5:52 PM, Oleg Mcnoleg wrote:

I have the same error when trying to delete a host provisioned using the
discovery plugin.

foreman_discovery-2.0.0-1.el6.noarch

foreman-1.7.2-1.el6

I love the discovery tool. Will this be fixed into an update to the plugin
I can pull down from the repos?

Thanks,

–
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.

Oleg_Mcnoleg · February 26, 2015, 10:40am

Just the discovery plugin.

Thanks,

Oleg_Mcnoleg · February 26, 2015, 7:06pm

I upgraded from 1.5 to 1.7.2.
2. Installed the discovery plugin
ruby193-rubygem-foreman_discovery-2.0.0-1.el6.noarch
3. Restarted foreman
4. Downloaded the FDI image and extracted to /var/lib/tftpboot/boot from
//downloads.theforeman.org/discovery/releases/latest/fdi-image-latest.tar
5. Edited my PXE Global default file and rebuilt the file
6. PXE booted my host - it appeared in my discovered hosts.
7. Provisioned the host - the client installed and booted from local
disk as expected.
8. Tried to delete the host from the UI and got the below:

Processing by HostsController#destroy as HTML
Parameters: {"authenticity_token"=>
"enNfu1zF8MfSQFzZ8JeQ63DIsQuAtEBrkVUbfs7gNfw=", "id"=>
"opunixdev02b.mydomain.com"}
Operation FAILED: ERROR: update or delete on table "hosts" violates
foreign key constraint "tokens_host_id_fk" on table "tokens"
DETAIL: Key (id)=(45) is still referenced from table "tokens".

Rendered common/500.html.erb within layouts/application (5.8ms)
Rendered layouts/base.html.erb (1.8ms)
Completed 500 Internal Server Error in 352ms (Views: 10.0ms | ActiveRecord:
15.8ms)

Ori_Rabin · February 26, 2015, 11:15am

Can you please add the steps to reproduce (I haven't gotten this error just
with discovery)?
Are these new discovered hosts or were they discovered with the previous
discovery?
Can you add part of your logs as well?
I would like to get the same error so I can check that the fix will work
for you.
You can also test it yourself if you'd like:
https://github.com/theforeman/foreman_discovery/pull/161

···

On Thu, Feb 26, 2015 at 12:40 PM, Oleg Mcnoleg wrote:

Just the discovery plugin.

Thanks,

–
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.

Oleg_Mcnoleg · February 26, 2015, 9:18pm

I was able to delete this host using a similar workaround in the below.

https://bugzilla.redhat.com/show_bug.cgi?id=1177145

moved the host to development environment (from Production)
turned the host to "managed" in the UI
and then was able to delete it.

I will try and recreate the issue and report back with full steps.

Ori_Rabin · February 26, 2015, 9:46pm

Anil, thanks for opening the bug.

Oleg, this is a different error, your validation is for 'tokens_host_id_fk'
and not 'discovery_attribute_sets_host_id_fk'.
Did this happen just for hosts that were already discovered and just
rebooted with the new issue or new discovered hosts too?
Did this happen also with hosts you created in the UI or just hosts you
provisioned from discovery?
Glad you found a workaround for now and looking forward to hear if this can
be recreated or exists only on a fresh installation.

···

On Thu, Feb 26, 2015 at 11:18 PM, Oleg Mcnoleg wrote:

I was able to delete this host using a similar workaround in the below.

https://bugzilla.redhat.com/show_bug.cgi?id=1177145

moved the host to development environment (from Production)

turned the host to “managed” in the UI
and then was able to delete it.

I will try and recreate the issue and report back with full steps.

–
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.

Stefan_Lasiewski · February 28, 2015, 1:13am

This is happening to me as well. I've been testing Foreman Discovery 2.0 on
and off since RC1 was released, so I'm not sure my use case would be
helpful for you. What I see is that I cannot delete the host.

stefanl@foreman:~ $ hammer host delete --id 83
Could not delete the host:
ERROR: update or delete on table "hosts" violates foreign key constraint
"tokens_host_id_fk" on table "tokens"
DETAIL: Key (id)=(83) is still referenced from table "tokens".
stefanl@foreman:~ $

How would I apply patch 161 to my Foreman system which was installed using
RPMs?

Would the current fix be to delete the host from the Postgres database?

-= Stefan

···

On Thursday, February 26, 2015 at 1:46:22 PM UTC-8, Ori Rabin wrote: > > Anil, thanks for opening the bug. > > Oleg, this is a different error, your validation is for > 'tokens_host_id_fk' and not 'discovery_attribute_sets_host_id_fk'. > Did this happen just for hosts that were already discovered and just > rebooted with the new issue or new discovered hosts too? > Did this happen also with hosts you created in the UI or just hosts you > provisioned from discovery? > Glad you found a workaround for now and looking forward to hear if this > can be recreated or exists only on a fresh installation. > > > On Thu, Feb 26, 2015 at 11:18 PM, Oleg Mcnoleg > wrote: > >> I was able to delete this host using a similar workaround in the below. >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1177145 >> >> 1. moved the host to development environment (from Production) >> 2. turned the host to "managed" in the UI >> and then was able to delete it. >> >> >> I will try and recreate the issue and report back with full steps. >> >> -- >> 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. >> > >

Stefan_Lasiewski · February 28, 2015, 2:01am

I should point out, I'm not using Staypuft. I'm only using Foreman 1.7 and
Foreman Discovery 2.0.0-1.

-= Stefan

···

On Friday, February 27, 2015 at 5:13:08 PM UTC-8, Stefan Lasiewski wrote: > > This is happening to me as well. I've been testing Foreman Discovery 2.0 > on and off since RC1 was released, so I'm not sure my use case would be > helpful for you. What I see is that I cannot delete the host. > > stefanl@foreman:~ $ hammer host delete --id 83 > Could not delete the host: > ERROR: update or delete on table "hosts" violates foreign key > constraint "tokens_host_id_fk" on table "tokens" > DETAIL: Key (id)=(83) is still referenced from table "tokens". > stefanl@foreman:~ $ > > How would I apply patch 161 to my Foreman system which was installed using > RPMs? > > Would the current fix be to delete the host from the Postgres database? > > -= Stefan > > > > -= Stefan > > > > On Thursday, February 26, 2015 at 1:46:22 PM UTC-8, Ori Rabin wrote: >> >> Anil, thanks for opening the bug. >> >> Oleg, this is a different error, your validation is for >> 'tokens_host_id_fk' and not 'discovery_attribute_sets_host_id_fk'. >> Did this happen just for hosts that were already discovered and just >> rebooted with the new issue or new discovered hosts too? >> Did this happen also with hosts you created in the UI or just hosts you >> provisioned from discovery? >> Glad you found a workaround for now and looking forward to hear if this >> can be recreated or exists only on a fresh installation. >> >> >> On Thu, Feb 26, 2015 at 11:18 PM, Oleg Mcnoleg >> wrote: >> >>> I was able to delete this host using a similar workaround in the below. >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=1177145 >>> >>> 1. moved the host to development environment (from Production) >>> 2. turned the host to "managed" in the UI >>> and then was able to delete it. >>> >>> >>> I will try and recreate the issue and report back with full steps. >>> >>> -- >>> 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. >>> >> >>

Ori_Rabin · February 28, 2015, 4:25pm

Stefan,
patch 161 is not for this case, it fixes Anil's problem but you are getting
another error (the same as Oleg).
Once I have steps to reproduce or answers to what I asked Oleg I will try
and reproduce your error and open up a bug or provide you with a workaround.
If you can provide a part of the log around the error please do.
Thanks

···

On Sat, Feb 28, 2015 at 4:01 AM, Stefan Lasiewski wrote:

I should point out, I’m not using Staypuft. I’m only using Foreman 1.7 and
Foreman Discovery 2.0.0-1.

-= Stefan

On Friday, February 27, 2015 at 5:13:08 PM UTC-8, Stefan Lasiewski wrote:

This is happening to me as well. I’ve been testing Foreman Discovery 2.0
on and off since RC1 was released, so I’m not sure my use case would be
helpful for you. What I see is that I cannot delete the host.

stefanl@foreman:~ $ hammer host delete --id 83
Could not delete the host:
ERROR: update or delete on table “hosts” violates foreign key
constraint “tokens_host_id_fk” on table "tokens"
DETAIL: Key (id)=(83) is still referenced from table “tokens”.
stefanl@foreman:~ $

How would I apply patch 161 to my Foreman system which was installed
using RPMs?

Would the current fix be to delete the host from the Postgres database?

-= Stefan

-= Stefan

On Thursday, February 26, 2015 at 1:46:22 PM UTC-8, Ori Rabin wrote:

Anil, thanks for opening the bug.

Oleg, this is a different error, your validation is for
’tokens_host_id_fk’ and not ‘discovery_attribute_sets_host_id_fk’.
Did this happen just for hosts that were already discovered and just
rebooted with the new issue or new discovered hosts too?
Did this happen also with hosts you created in the UI or just hosts you
provisioned from discovery?
Glad you found a workaround for now and looking forward to hear if this
can be recreated or exists only on a fresh installation.

On Thu, Feb 26, 2015 at 11:18 PM, Oleg Mcnoleg stockf...@gmail.com >>> wrote:

I was able to delete this host using a similar workaround in the below.

https://bugzilla.redhat.com/show_bug.cgi?id=1177145

moved the host to development environment (from Production)

turned the host to “managed” in the UI
and then was able to delete it.

I will try and recreate the issue and report back with full steps.

–
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.

–
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.

Ori_Rabin · February 28, 2015, 4:27pm

Stefan,
I didn't notice you are deleting through hammer,
pleas run 'hammer -d host delete --id 83' to get some more details about
the error

···

On Sat, Feb 28, 2015 at 6:25 PM, Ori Rabin wrote:

Stefan,
patch 161 is not for this case, it fixes Anil’s problem but you are
getting another error (the same as Oleg).
Once I have steps to reproduce or answers to what I asked Oleg I will try
and reproduce your error and open up a bug or provide you with a workaround.
If you can provide a part of the log around the error please do.
Thanks

On Sat, Feb 28, 2015 at 4:01 AM, Stefan Lasiewski stefan@stefanco.com > wrote:

I should point out, I’m not using Staypuft. I’m only using Foreman 1.7
and Foreman Discovery 2.0.0-1.

-= Stefan

On Friday, February 27, 2015 at 5:13:08 PM UTC-8, Stefan Lasiewski wrote:

This is happening to me as well. I’ve been testing Foreman Discovery 2.0
on and off since RC1 was released, so I’m not sure my use case would be
helpful for you. What I see is that I cannot delete the host.

stefanl@foreman:~ $ hammer host delete --id 83
Could not delete the host:
ERROR: update or delete on table “hosts” violates foreign key
constraint “tokens_host_id_fk” on table "tokens"
DETAIL: Key (id)=(83) is still referenced from table “tokens”.
stefanl@foreman:~ $

How would I apply patch 161 to my Foreman system which was installed
using RPMs?

Would the current fix be to delete the host from the Postgres database?

-= Stefan

-= Stefan

On Thursday, February 26, 2015 at 1:46:22 PM UTC-8, Ori Rabin wrote:

Anil, thanks for opening the bug.

Oleg, this is a different error, your validation is for
’tokens_host_id_fk’ and not ‘discovery_attribute_sets_host_id_fk’.
Did this happen just for hosts that were already discovered and just
rebooted with the new issue or new discovered hosts too?
Did this happen also with hosts you created in the UI or just hosts you
provisioned from discovery?
Glad you found a workaround for now and looking forward to hear if this
can be recreated or exists only on a fresh installation.

On Thu, Feb 26, 2015 at 11:18 PM, Oleg Mcnoleg stockf...@gmail.com >>>> wrote:

I was able to delete this host using a similar workaround in the
below.

https://bugzilla.redhat.com/show_bug.cgi?id=1177145

moved the host to development environment (from Production)

turned the host to “managed” in the UI
and then was able to delete it.

I will try and recreate the issue and report back with full steps.

–
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.

–
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.

Stefan_Lasiewski · February 28, 2015, 4:31pm

Oh, you are right. My issue is different from the parent issue. I was
confused by the thread.

I will try and gather more info on Monday. Should I file a bug?

– Stefan

···

On Feb 28, 2015 8:27 AM, "Ori Rabin" wrote:

Stefan,
I didn’t notice you are deleting through hammer,
pleas run ‘hammer -d host delete --id 83’ to get some more details about
the error

On Sat, Feb 28, 2015 at 6:25 PM, Ori Rabin orrabin@gmail.com wrote:

Stefan,
patch 161 is not for this case, it fixes Anil’s problem but you are
getting another error (the same as Oleg).
Once I have steps to reproduce or answers to what I asked Oleg I will try
and reproduce your error and open up a bug or provide you with a workaround.
If you can provide a part of the log around the error please do.
Thanks

On Sat, Feb 28, 2015 at 4:01 AM, Stefan Lasiewski stefan@stefanco.com >> wrote:

I should point out, I’m not using Staypuft. I’m only using Foreman 1.7
and Foreman Discovery 2.0.0-1.

-= Stefan

On Friday, February 27, 2015 at 5:13:08 PM UTC-8, Stefan Lasiewski wrote:

This is happening to me as well. I’ve been testing Foreman Discovery
2.0 on and off since RC1 was released, so I’m not sure my use case would be
helpful for you. What I see is that I cannot delete the host.

stefanl@foreman:~ $ hammer host delete --id 83
Could not delete the host:
ERROR: update or delete on table “hosts” violates foreign key
constraint “tokens_host_id_fk” on table "tokens"
DETAIL: Key (id)=(83) is still referenced from table “tokens”.
stefanl@foreman:~ $

How would I apply patch 161 to my Foreman system which was installed
using RPMs?

Would the current fix be to delete the host from the Postgres database?

-= Stefan

-= Stefan

On Thursday, February 26, 2015 at 1:46:22 PM UTC-8, Ori Rabin wrote:

Anil, thanks for opening the bug.

Oleg, this is a different error, your validation is for
’tokens_host_id_fk’ and not ‘discovery_attribute_sets_host_id_fk’.
Did this happen just for hosts that were already discovered and just
rebooted with the new issue or new discovered hosts too?
Did this happen also with hosts you created in the UI or just hosts
you provisioned from discovery?
Glad you found a workaround for now and looking forward to hear if
this can be recreated or exists only on a fresh installation.

On Thu, Feb 26, 2015 at 11:18 PM, Oleg Mcnoleg stockf...@gmail.com >>>>> wrote:

I was able to delete this host using a similar workaround in the
below.

https://bugzilla.redhat.com/show_bug.cgi?id=1177145

moved the host to development environment (from Production)

turned the host to “managed” in the UI
and then was able to delete it.

I will try and recreate the issue and report back with full steps.

–
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.

–
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.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/NP182Z6qlwA/unsubscribe.
To unsubscribe from this group and all its topics, 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.