Closed bfilion87 closed 6 months ago
@bfilion87 Same as #9115.
This has been fixed by https://github.com/ManageIQ/manageiq-ui-classic/pull/9116 and https://github.com/ManageIQ/manageiq-ui-classic/pull/9120
Closing. If it's still a problem, we can reopen it.
@jrafanie I applied the fixes for both https://github.com/ManageIQ/manageiq-ui-classic/pull/9116 and https://github.com/ManageIQ/manageiq-ui-classic/pull/9120 but am still getting the same behavior when trying to edit provisioning scope tags on groups.
@jrafanie I applied the fixes for both #9116 and #9120 but am still getting the same behavior when trying to edit provisioning scope tags on groups.
If you're running in dev or prod mode, you need to compile assets. A JS runtime like node is required to do this.
You probably are running into an issue where the precompiled assets have not been updated after you applied the changes. I did the exact same thing:
https://github.com/ManageIQ/manageiq-ui-classic/pull/9120#issuecomment-2003850882
I think I did bin/update
from the manageiq directory. For appliances, I'm not sure what the steps are as you'll be updating the assets coming from the rpms.
@jrafanie I applied the fixes for both #9116 and #9120 but am still getting the same behavior when trying to edit provisioning scope tags on groups.
If you're running in dev or prod mode, you need to compile assets. A JS runtime like node is required to do this.
You probably are running into an issue where the precompiled assets have not been updated after you applied the changes. I did the exact same thing:
I think I did
bin/update
from the manageiq directory. For appliances, I'm not sure what the steps are as you'll be updating the assets coming from the rpms.
Ok sounds good, Ill look into compiling. We are on a Vcenter/Vsphere appliance setup and yeah it appears bin/update does not run from our vmdb/managieq directory.
@jrafanie Do you happen to or can point me to someone who could show me how to properly update the assets on a VMware Vsphere appliance? I have tried numerous combos of trying to update but nothing seems to be doing the trick. We've tried as both our root user on the appliances as well as the manageiq user, all under the vmdb directory.
@bfilion87 I haven't run it but you'll need node relevant to the version of the appliance you're using. For example, petrosian used node 18. I don't know if that's enough as you may need to also install yarn. It may be easier to update to a newer appliance with the fixes merged on March 14 and 20th included. https://releases.manageiq.org/index.html has several master builds that you should be able to test the fix on and consider using.
2024-03-24T08:42:19.074Z 1.4 GB [manageiq-vsphere-master-20240324.ova](https://releases.manageiq.org/manageiq-vsphere-master-20240324.ova)
2024-03-31T08:54:04.504Z 1.4 GB [manageiq-vsphere-master-20240331.ova](https://releases.manageiq.org/manageiq-vsphere-master-20240331.ova)
2024-04-07T08:44:15.754Z 1.4 GB [manageiq-vsphere-master-20240407.ova](https://releases.manageiq.org/manageiq-vsphere-master-20240407.ova)
2024-04-14T08:53:57.182Z 1.4 GB [manageiq-vsphere-master-20240414.ova](https://releases.manageiq.org/manageiq-vsphere-master-20240414.ova)
2024-04-21T08:52:55.374Z 1.4 GB [manageiq-vsphere-master-20240421.ova](https://releases.manageiq.org/manageiq-vsphere-master-20240421.ova)
2024-04-28T08:51:42.355Z 1.4 GB [manageiq-vsphere-master-20240428.ova](https://releases.manageiq.org/manageiq-vsphere-master-20240428.ova)
We discussed precompiling assets on appliances previously in https://github.com/orgs/ManageIQ/discussions/22785#discussioncomment-8157626 but it's unclear if the user was able to get it to work.