I have noticed this issue as well, I managed to resolve it by putting host
on maintenance node and removing it and adding it back to CS.

On Sunday, January 12, 2014, David Nalley <da...@gnsa.us> wrote:
> Any thoughts, Brian?
>
> I am noticing the regions icon problem as well on my 4.2.1 deployment.
>
> --David
>
> On Sun, Jan 12, 2014 at 4:15 PM, Cody Rucks <crucks2...@gmail.com> wrote:
>> So, all of these issues seemed to go away with an upgrade to 4.2.1. I
found
>> a similar case someone had and upgrading to 4.2.1 resolved it for them.
>> Luckily, it did for me as well. If anyone wants the logs, let me know. I
>> expired the previous links.
>>
>> The only other thing I can't seem to fix are some UI issues. The regions
>> icon on the navigation pane is missing along with the region logo by the
>> log in/log out drop-down. The CSS is right, the sprites.png is there as
>> well. I compared them to a recent install on a different instance and
>> nothing looks noticeably different. Any ideas?
>>
>>
>> On Sat, Jan 11, 2014 at 9:45 AM, Cody Rucks <crucks2...@gmail.com> wrote:
>>
>>> Good Day,
>>>
>>> I recently added another management server, but did so with 4.2.0. As a
>>> result, the db was upgraded (without a backup). To get the old
management
>>> server working, I had to upgrade it to 4.2.0.
>>>
>>> Now, it seems that we cannot deploy VM's. The pastebin contains some log
>>> information from management-server.log.
>>>
>>> Environment:
>>> CloudStack 4.2.0
>>> XCP (Xen Cloud Platform) 1.6
>>> MS log: http://pastebin.com/fDntzdtB
>>> catalina log: http://pastebin.com/8KKFt8a4
>>>
>>> Earlier, the ssvm and console vm would not create -- I had destroyed
them
>>> when I couldn't get the agent to connect after a reboot. Something is
also
>>> wrong with the secondary management server and after rebooting it and
then
>>> restarting cloudstack-management service on the main MS the system vm's
>>> created.
>>>
>>> The UI on the MS is also missing some icons and such. On the secondary
MS
>>> this isn't the case.
>>>
>>>
>

Reply via email to