Ideally I would like to see DEBUG and SQL logs for that transactions, but thats flooding your production server.
In the console with both records presnet do something like: ::Nic::Managed.where(:mac => "MA:CA:DDRESS::", :primary => true) On Wed, Oct 11, 2017 at 9:08 PM, 'Konstantin Orekhov' via Foreman users < [email protected]> wrote: > > >> Theoretically if you changed configuration of bootif fact in settings, >> this could happen. But I assume you haven't. Was it also the same FDI >> version, just in case facter changed facts? >> > > Yes, the same system with the same discovery proxy. I'm not using official > FDI, but a netbooted Ubuntu14.04 (Casper-based) with old foreman-proxy > version 1.9.2, smart_proxy_discovery_image-1.0.5.gem and discover-host > from around the same time. I had trouble bringing in later versions of > foreman-proxy to u14.04 because of dependency on ruby 2.x. If the fact that > I run such old versions on a client side is an issue in your opinion, I can > start the work on migrating to u16.04. But so far I have not seen an > indication that this is an issue - duplicate entries happen not too often > and most of the time it is working fine (and I have several thousands of > hosts going through this), especially now with that MySQL patch you gave me > earlier. > > >> If you visit the original discovery host in the UI, do you see >> Interfaces list? What MAC address is there? Is it detected as the >> primary interface there? >> > > Yes, all of the data is in place for both duplicate entries and look > absolutely identical to me: > > > <https://lh3.googleusercontent.com/-Qjn-PntubGE/Wd5qYnQIQGI/AAAAAAAAAEU/nkbpCKnoFdwqGGRF-tWkEXyNK_SFRkq_gCLcBGAs/s1600/Screen%2BShot%2B2017-10-11%2Bat%2B11.57.26%2BAM.png> > > > <https://lh3.googleusercontent.com/-UJCurA1GVa4/Wd5qdFYOUaI/AAAAAAAAAEY/1f-YHzKHI1oNjbEj6_DZ8MAokTDO2zZqwCLcBGAs/s1600/Screen%2BShot%2B2017-10-11%2Bat%2B11.56.28%2BAM.png> > > > >> Do you still have both records in the DB? Can you run rake console and >> try these statements? Or insert Rails.logger.info statements there to >> see the code flow. >> > > I do still have those in a DB, yes. But I don't have that host running a > discover proxy anymore :( > But if I find more duplicate entries, I don't quite understand what you > want me to do - try which statements? Or insert logger statements where > exactly? > > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
