Bug #4580

Override Network Values (IPv4) does not work

Added by Stefan Kooman over 4 years ago. Updated over 4 years ago.

Status:ClosedStart date:06/17/2016
Priority:HighDue date:
Assignee:Carlos Martín% Done:

0%

Category:Sunstone
Target version:Release 5.0.1
Resolution:fixed Pull request:
Affected Versions:OpenNebula 5.0

Description

Instead of allocating the fixed IP specified in the VM template, OpenNebula will pick the first IP in the virtual network instead.

Associated revisions

Revision ca91c193
Added by Carlos Martín over 4 years ago

Bug #4580: Fix VM instantiate when NIC contains a fixed IP

History

#1 Updated by Ruben S. Montero over 4 years ago

This is for onetemplate instantiate, onevm create works as expected

#2 Updated by Ruben S. Montero over 4 years ago

  • Category set to Sunstone
  • Assignee set to Carlos Martín
  • Priority changed from Normal to High

The CLI works, this issue is only through sunstone

#3 Updated by Carlos Martín over 4 years ago

  • Status changed from Pending to Closed
  • Target version set to Release 5.2
  • Resolution set to fixed

#4 Updated by Stefan Kooman over 4 years ago

I have replaced /usr/lib/one/sunstone/public/app/utils/nics-section.js with:

http://dev.opennebula.org/projects/opennebula/repository/revisions/ca91c193a03d07e40f847b667d63bd94c66e43e1/entry/src/sunstone/public/app/utils/nics-section.js

and /usr/lib/one/sunstone/public/app/utils/nics-section/dd.hbs with:

http://dev.opennebula.org/projects/opennebula/repository/revisions/ca91c193a03d07e40f847b667d63bd94c66e43e1/raw/src/sunstone/public/app/utils/nics-section/dd.hbs

And restarted sunstone (apache with passenger). Cleared cache and restarted browser. Problem still persists.

Instantiate VM Template > Force IPv4 does work. But for a template with an already fixed IP this should not be needed.

#5 Updated by Carlos Martín over 4 years ago

Are you using the 'dev' environment in sunstone-server.conf? Can you confirm the changes are present in your browser development console files?

#6 Updated by Stefan Kooman over 4 years ago

I've changed ":env:" to 'dev' and then it works. I can also see the updated javascript in dev console in browser. But, if I change the env to "prod" it fails again ... Do I need to manually recreate some javascript to make it work in production?

#7 Updated by Carlos Martín over 4 years ago

Stefan Kooman wrote:

Do I need to manually recreate some javascript to make it work in production?

Yes, 'prod' uses the minimized javascript files. You can leave it in 'dev', the only difference you will notice is slower loading times. To generate the minimized JS, follow this:
http://docs.opennebula.org/5.0/integration/references/sunstone_dev.html#modifying-js-css-files

#8 Updated by Stefan Kooman over 4 years ago

I've changed the debian/rules file to let the minified files be built during compile time:

override_dh_auto_build:
scons mysql=yes new_xmlrpc=yes sunstone=yes

However, the final debian package does not seem to result in updated minified files. I rebuild the package and re-installed sunstone, re-started apache / browser. At least the issue still is there in "prod" mode.

The issue with running "dev" mode is that the buttons with VM operations are not there when using firefox (while they are visible using chrome).

#9 Updated by Stefan Kooman over 4 years ago

I've made a seperate bug for this issue (buttons not visible in Firefox), see #4598

#10 Updated by Ruben S. Montero over 4 years ago

  • Target version changed from Release 5.2 to Release 5.0.1

Also available in: Atom PDF