Bug #22571
closed
Storage allocation web UI issue with LVM
Added by Alexandre Anriot almost 7 years ago.
Updated over 6 years ago.
Description
Hello,
I'm using Foreman 1.16 on a Debian Stretch (amd64) server, with several Foreman-proxies.
Some compute profiles are configured to use a LVM-based storage pull, with "Full" allocation.
When I change the "Size (GB)" setting on the host creation window, the "Allocation (GB)" field is not updated automatically and I have to:
- choose a different allocation value like "None" or "Size" ;
- switch back to "Full".
Could you tell me if it is the expected behaviour?
The documentation gave me no answer.
Thanks a lot.
Cheers,
- Subject changed from Storage allocation issue with LVM to Storage allocation web UI issue with LVM
- Category set to Web Interface
Hey, this works for me with devel version (Chrome stable, Linux). Can you record a video to verify I understand the problem correctly? Any javascript errors in debug web browser console?
Lukas Zapletal wrote:
Hey, this works for me with devel version (Chrome stable, Linux). Can you record a video to verify I understand the problem correctly? Any javascript errors in debug web browser console?
Hello Lukas,
To avoid storing this temporary file on Redmine, I did just sent a quick screencast to you by mail (Ubuntu + latest Firefox).
I see no JavaScript errors.
Cheers,
A bug in COMPUTE PROFILE perhaps. I can confirm. Without COMPUTE PROFILE it works fine.
Hey Alexandre, possibly you just have to click outside of the field after changing the value?
Could you send me the video as well? egilman@redhat.com
Thanks
Liza Gilman wrote:
Hey Alexandre, possibly you just have to click outside of the field after changing the value?
Hello Liza,
Even when clicking outside, the field doesn't get updated.
Could you send me the video as well? egilman@redhat.com
Thanks
It should be in your inbox now.
Best regards,
- Assignee set to Liza Gilman
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5298 added
Liza,
To begin with, we have upgraded our Foreman platform (server + 2 proxies) to 1.17 RC1, and I can confirm that the same problem still occurs.
How can I apply the 2nd part of the patch as the webpack files are compiled? Could you provide a compiled bundle JS file?
Thanks.
Best regards,
Liza,
Thanks but I don't see any foreman_compute_resource.js file on my server. It has tos compiled, right?
Alexandre Anriot wrote:
Liza,
Thanks but I don't see any foreman_compute_resource.js file on my server. It has tos compiled, right?
s/tos/to be/
It should be at webpack/assets/javascripts/
Liza,
Here is the webpack files list I have:
$ > ls -al /usr/share/foreman/public/webpack
total 3636
drwxr-xr-x 2 foreman foreman 4096 Mar 8 16:03 .
drwxr-xr-x 5 foreman foreman 4096 Mar 7 10:27 ..
-rw-r--r-- 1 foreman foreman 70588 Jan 30 16:57 bundle-4dc8d271027ff6d9a2b7.css
-rw-r--r-- 1 foreman foreman 13400 Jan 30 16:57 bundle-4dc8d271027ff6d9a2b7.css.gz
-rw-r--r-- 1 foreman foreman 109200 Jan 30 16:57 bundle-4dc8d271027ff6d9a2b7.js
-rw-r--r-- 1 foreman foreman 26607 Jan 30 16:57 bundle-4dc8d271027ff6d9a2b7.js.gz
-rw-r--r-- 1 foreman foreman 216 Jan 30 16:57 manifest.json
-rw-r--r-- 1 foreman foreman 2736704 Jan 30 16:57 vendor-8aaef31828f86f16484f.js
-rw-r--r-- 1 foreman foreman 738509 Jan 30 16:57 vendor-8aaef31828f86f16484f.js.gz
- Translation missing: en.field_release set to 330
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF