Thanks for the moderation whitelist!  I am grateful.

Sure thing!

I have not yet been able to create my own roles form my own images; i'm 
using 100% scalr's ubuntu image (base64-12.04) in AWS US-WEST-2 region.


I should have mentioned that I've already tried to update the installation 
after using the installer-ng script.

root@54:/opt/scalr/current/app/bin# whoami
> root
> root@54:/opt/scalr/current/app/bin# pwd
> /opt/scalr/current/app/bin
> root@54:/opt/scalr/current/app/bin# php upgrade.php
> 24:48 - Scalr is up-to-date
> root@54:/opt/scalr/current/app/bin#
>
>
>

And here's the attached console dump as a screenshot.  Very interesting 
results!


<https://lh5.googleusercontent.com/-5PbWqrVkBdw/VNO8r1EWFII/AAAAAAAAAAo/wgUFEF9jZnI/s1600/Screen%2BShot%2B2015-02-05%2Bat%2B10.32.02.png>


So that's interesting!  There's no image details, but the rest of the 
information is there... the database is 1/2 populated?


-K


On Thursday, February 5, 2015 at 1:41:53 AM UTC-8, Thomas Orozco wrote:
>
> Hi there,
>
> The error actually seems to have to do with your Farm Roles, rather than 
> your Instance Types.
>
> Specifically, the error is happening here: 
> https://github.com/Scalr/scalr/blob/7f0df7fb045787363ab7d7bdfee393377e31c706/app/www/ui2/js/ui/farms/builder.js#L1344
>
> This leads me to think that one of your Farm Roles has no Image (you can 
> lookup the definition of `get:` a few lines above).
>
> Could you:
>
> + Ensure that you've ran all migrations on this instance:
>
> cd /opt/scalr/current/app/bin && php upgrade.php
>
> +  Provide a snapshot of the network request to /farms/{farmId}/edit, wit 
> the following expanded: http://note.io/1DBaqIl
>
> Thanks!
>
> On Tuesday, February 3, 2015 at 8:10:19 PM UTC+1, [email protected] 
> wrote:
>>
>> Hi.
>>
>> I'll try to keep this as canonical as I can.  When I create a farm for 
>> the first time, everything works fine.  100% of the UI is as i'd expect it 
>> to be.  Until I save a farm and attempt to edit it later.
>>
>> When attempting to edit an existing farm, two things happen:
>>
>> 1. The UI for a given role is "missing" fields.  See the attached 
>> screenshot for highlights showing which elements are in-correctly filled 
>> out. The behavior of theses fields is as if they're not 100% set up by the 
>> javascript... which brings me to the second issue
>>
>>
>>
>> <https://lh5.googleusercontent.com/-uX6HV9mVqCs/VNEcvEvz75I/AAAAAAAAAAM/EGPgF1rNfJw/s1600/Screen%2BShot%2B2015-02-03%2Bat%2B10.37.22.png>
>>
>>
>> 2. See the second attached screenshot for the specific JS console error 
>> and the network waterfall graph and, the JSON that comes back from the 
>> /platforms/xGetInstanceTypes call.
>>
>>
>>
>>
>>
>> If I edit the farm, and immediately add a new role to the farm *BEFORE* I 
>> dig into any of the existing roles, then the newly added role's UI will 
>> function 100% as expected. Everything works and functions as it should... 
>> until I attempt to edit any of the existing roles in the farm; they sill 
>> have various UI issues like those shown in the screenshots for point #1 
>> above.
>>
>>
>>
>> I can re-produce this problem on all modern web browsers (Chrome, FF, 
>> Safari.. all on OSX and Android).  The cloud in question is AWS.
>>
>>
>>
>> System information and scalr release information:
>>
>>
>> root@54:/opt/scalr# whoami
>> root
>> root@54:/opt/scalr# uname -r
>> 3.13.0-44-generic
>> root@54:/opt/scalr# lsb_release -a
>> No LSB modules are available.
>> Distributor ID: Ubuntu
>> Description: Ubuntu 14.04.1 LTS
>> Release: 14.04
>> Codename: trusty
>> root@54:/opt/scalr# pwd
>> /opt/scalr
>> root@54:/opt/scalr# ls -l
>> total 16
>> lrwxrwxrwx 1 root scalr   60 Feb  2 22:52 current -> /opt/scalr/releases/
>> cee9a5dfc950daa018c685968a1b88bbb4dfb772
>> drwxr-xr-x 3 root scalr 4096 Feb  2 22:52 releases
>> drwxr-xr-x 3 root scalr 4096 Feb  2 22:52 shared
>> drwxr-xr-x 6 root scalr 4096 Feb  2 23:02 venv
>> root@54:/opt/scalr/current# git fetch origin master
>> From git://github.com/Scalr/scalr
>>  * branch            master     -> FETCH_HEAD
>> root@54:/opt/scalr/current# git status
>> On branch deploy
>> nothing to commit, working directory clean
>>
>>
>>
>>
>> Please let me know if there's anything else that I need to provide to 
>> help you figure out this issue.  Thanks!
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to