Project

General

Profile

Bug #11171

Select2 does not work with compute profiles

Added by Marek Hulán about 5 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Web Interface
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

In compute profile, when you add new interface or volume to a form, select box in this form does not work. Reproduced with 1.9-stable branch and nightly.


Related issues

Related to Foreman - Bug #11172: Select2 should be initialized explicitlyClosed2015-07-21
Related to Foreman - Feature #10641: Ability to search VmWare networksClosed2015-05-28
Related to Foreman - Bug #11721: Inconsistency with select2 on compute profile filesNew2015-09-08

Associated revisions

Revision 052d5819 (diff)
Added by Shlomi Zadok about 5 years ago

fixes #11171 - compute profiles nics & volumes select2 are initiated separately

Revision abba66b2 (diff)
Added by Shlomi Zadok about 5 years ago

fixes #11171 - compute profiles nics & volumes select2 are initiated separately

(cherry picked from commit 052d58199494eb5e1eaac9fdbcac76c2d2bb4fb7)

History

#1 Updated by Marek Hulán about 5 years ago

  • Related to Bug #11172: Select2 should be initialized explicitly added

#2 Updated by Marek Hulán about 5 years ago

Whoever will fix this, I'd suggest considering IMHO a proper fix described in #11172

#3 Updated by Dominic Cleal about 5 years ago

#4 Updated by Shlomi Zadok about 5 years ago

  • Assignee set to Shlomi Zadok

#5 Updated by The Foreman Bot about 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2575 added
  • Pull request deleted ()

#6 Updated by Alexandre Barth about 5 years ago

I'd like to test this commit, but i can't find the application.js file in my foreman 1.9 RC2 installation, i don't even have an assets directory in the /usr/share/foreman/app directory.

#7 Updated by Dominic Cleal about 5 years ago

Our packages ship a precompiled version of the Javascript and CSS files that are optimised, combined etc. You'd need to install foreman-assets, patch it, then run foreman-rake assets:precompile.

I'd only suggest you do it on a test installation, as I'm not certain if doing a package upgrade after actually replaces your locally compiled assets with ours again.

#8 Updated by Alexandre Barth about 5 years ago

Still no application.js file to patch after installing foreman-assets package

#9 Updated by Dominic Cleal about 5 years ago

Hm, sorry, you're right. I thought we included that - I must be misremembering.

There probably isn't an easy way to test this then apart from using a development install (http://theforeman.org/contribute.html) or rebuilding the package with the patch applied.

#10 Updated by Alexandre Barth about 5 years ago

Ok no time for this, i give up :) Will you commit this soon in 1.9 RC2, maybe RC3 ?

#11 Updated by Dominic Cleal about 5 years ago

Yep, it'll be in 1.9.0 final for sure, or RC3, whichever comes next.

#12 Updated by Shlomi Zadok about 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#13 Updated by Dominic Cleal almost 5 years ago

  • Related to Bug #11721: Inconsistency with select2 on compute profile files added

Also available in: Atom PDF