I have installed a fresh Foreman 3.12 server and when configuring the compute attributes for the profiles the Network Interface details and Storage details are missing from the compute attributes edit page. Only the profile name resource name , cpu, memory and image are visible.
Expected outcome:
Network Interface details and Storage details visible on all compute attributes edit pages.
Foreman versions:
3.11 and 3.12
Other relevant data:
This was working as expected in 3.11rc1 and 3.10 (which I have just reinstalled to test). I’m using KVM as the compute resource.
This is what is missing. The screenshot was taken form the 3.10 install.
@ekohl / @lzap / @Marek_Hulan,
Are you already ware of this? Who is best to take a look at this issue?
@ehelms @nofaralfasi can anyone help with this please ?
I think I’ve seen this issue before. It should be fixed in the latest version of Foreman. Could you check your browser console for any errors?
@nofaralfasi thanks for the reply.
Please see attached
It’s not it. I see the same error and I don’t have this issue. Maybe it is something on the rails console? Do you see any errors there?
I know I’ve seen it somewhere, but I can remember where…
How would I get the rails console logs to you.
This problem and the unable to create hosts problem are both the same problem I believe.
Run the following command while you’re loading this page:
tail -f /var/log/foreman/production.log
2024-11-06T16:58:48 [I|app|3da1739b] Started GET “/notification_recipients” for 192.168.0.101 at 2024-11-06 16:58:48 +0000
2024-11-06T16:58:48 [I|app|3da1739b] Processing by NotificationRecipientsController#index as JSON
2024-11-06T16:58:48 [I|app|3da1739b] Completed 200 OK in 10ms (Views: 0.2ms | ActiveRecord: 1.6ms | Allocations: 2410)
2024-11-06T16:58:53 [I|app|e7c663a2] Started GET “/notification_recipients” for 192.168.0.101 at 2024-11-06 16:58:53 +0000
2024-11-06T16:58:53 [I|app|e7c663a2] Processing by NotificationRecipientsController#index as JSON
2024-11-06T16:58:53 [I|app|e7c663a2] Completed 200 OK in 10ms (Views: 0.2ms | ActiveRecord: 1.7ms | Allocations: 2326)
2024-11-06T16:58:54 [I|app|84c9927c] Started GET “/compute_profiles” for 192.168.0.101 at 2024-11-06 16:58:54 +0000
2024-11-06T16:58:54 [I|app|84c9927c] Processing by ComputeProfilesController#index as HTML
2024-11-06T16:58:54 [I|app|84c9927c] Rendered compute_profiles/index.html.erb within layouts/application (Duration: 8.7ms | Allocations: 4409)
2024-11-06T16:58:54 [I|app|84c9927c] Rendered layouts/base.html.erb (Duration: 22.4ms | Allocations: 15772)
2024-11-06T16:58:54 [I|app|84c9927c] Rendered layout layouts/application.html.erb (Duration: 32.9ms | Allocations: 20911)
2024-11-06T16:58:54 [I|app|84c9927c] Completed 200 OK in 56ms (Views: 38.5ms | ActiveRecord: 3.8ms | Allocations: 26978)
2024-11-06T16:58:56 [I|app|c07db551] Started GET “/notification_recipients” for 192.168.0.101 at 2024-11-06 16:58:56 +0000
2024-11-06T16:58:56 [I|app|c07db551] Processing by NotificationRecipientsController#index as JSON
2024-11-06T16:58:56 [I|app|c07db551] Completed 200 OK in 10ms (Views: 0.2ms | ActiveRecord: 1.7ms | Allocations: 2490)
2024-11-06T16:58:56 [I|app|a1bcbced] Started GET “/compute_profiles/auto_complete_search?search=” for 192.168.0.101 at 2024-11-06 16:58:56 +0000
2024-11-06T16:58:56 [I|app|a1bcbced] Processing by ComputeProfilesController#auto_complete_search as JSON
2024-11-06T16:58:56 [I|app|a1bcbced] Parameters: {“search”=>“”}
2024-11-06T16:58:56 [I|app|a1bcbced] Completed 200 OK in 12ms (Views: 0.3ms | ActiveRecord: 2.1ms | Allocations: 3226)
2024-11-06T16:58:58 [I|app|86bb3278] Started GET “/compute_profiles/3-3-Large” for 192.168.0.101 at 2024-11-06 16:58:58 +0000
2024-11-06T16:58:58 [I|app|86bb3278] Processing by ComputeProfilesController#show as HTML
2024-11-06T16:58:58 [I|app|86bb3278] Parameters: {“id”=>“3-3-Large”}
2024-11-06T16:58:58 [I|app|86bb3278] Rendered compute_profiles/show.html.erb within layouts/application (Duration: 12.5ms | Allocations: 3220)
2024-11-06T16:58:58 [I|app|86bb3278] Rendered layouts/base.html.erb (Duration: 20.6ms | Allocations: 15334)
2024-11-06T16:58:58 [I|app|86bb3278] Rendered layout layouts/application.html.erb (Duration: 34.9ms | Allocations: 19167)
2024-11-06T16:58:58 [I|app|86bb3278] Completed 200 OK in 50ms (Views: 31.6ms | ActiveRecord: 6.7ms | Allocations: 22990)
2024-11-06T16:58:59 [I|app|823ea8ff] Started GET “/notification_recipients” for 192.168.0.101 at 2024-11-06 16:58:59 +0000
2024-11-06T16:58:59 [I|app|823ea8ff] Processing by NotificationRecipientsController#index as JSON
2024-11-06T16:58:59 [I|app|823ea8ff] Completed 200 OK in 9ms (Views: 0.2ms | ActiveRecord: 1.4ms | Allocations: 2326)
2024-11-06T16:59:01 [I|app|98fb02f4] Started GET “/compute_profiles/3-3-Large/compute_attributes/3/edit” for 192.168.0.101 at 2024-11-06 16:59:01 +0000
2024-11-06T16:59:01 [I|app|98fb02f4] Processing by ComputeAttributesController#edit as HTML
2024-11-06T16:59:01 [I|app|98fb02f4] Parameters: {“compute_profile_id”=>“3-3-Large”, “id”=>“3”}
2024-11-06T16:59:01 [I|app|98fb02f4] Deface: [WARNING] No :original defined for ‘remove_networks_and_volumes_partial’, you should change its definition to include:
98fb02f4 | :original => ‘eb4c199bc19e113181e82700bff46538b01f8c44’
2024-11-06T16:59:01 [I|app|98fb02f4] Deface: [WARNING] No :original defined for ‘remove_networks_and_volumes_partial’, you should change its definition to include:
98fb02f4 | :original => ‘6dc2ea3d0067fe626ab69b442c12610b066eabf1’
2024-11-06T16:59:01 [E|app|98fb02f4] Deface: [ERROR] The original source for ‘foreman_fog_proxmox/engine_add_from_profile_to_compute_form’ has changed, this override should be reviewed to ensure it’s still valid.
2024-11-06T16:59:02 [I|app|98fb02f4] Rendered compute_attributes/edit.html.erb within layouts/application (Duration: 373.4ms | Allocations: 22061)
2024-11-06T16:59:02 [I|app|98fb02f4] Rendered layouts/base.html.erb (Duration: 21.2ms | Allocations: 15545)
2024-11-06T16:59:02 [I|app|98fb02f4] Rendered layout layouts/application.html.erb (Duration: 395.4ms | Allocations: 37901)
2024-11-06T16:59:02 [I|app|98fb02f4] Completed 200 OK in 416ms (Views: 396.9ms | ActiveRecord: 7.3ms | Allocations: 43180)
2024-11-06T16:59:02 [I|app|be0a6d2e] Started GET “/notification_recipients” for 192.168.0.101 at 2024-11-06 16:59:02 +0000
2024-11-06T16:59:02 [I|app|be0a6d2e] Processing by NotificationRecipientsController#index as JSON
2024-11-06T16:59:02 [I|app|be0a6d2e] Completed 200 OK in 9ms (Views: 0.2ms | ActiveRecord: 1.0ms | Allocations: 2448)
Hi @mnsmithuk , this is a bug in the foreman_fog_proxmox UI which was recently fixed but we have not published a packaged with the fix, yet. Sorry for the inconvenience!
2 Likes
We published a fix for the UI glitch in foreman_fog_proxmox. It should be available by tomorrow. Thanks to packaging team for merging that quickly 
1 Like
Thank you @nadjaheitmann. It worked as expected when I don’t install the proxmox plugin. Looking forward to test the updated proxmox plugin fix tomorrow but the KVM plugin is most important one right now that needs to be working.
Thank you.
I can now confirm that rubygem-foreman_fog_proxmox-0.16.3-1 fixes the issue in Foreman 3.12. Thanks for pushing this through. Foreman 3.13rc1 has foreman_fog_proxmox-0.17.1-1 so will need to also test if this contains the fix.
1 Like
