Hi James,
Could you please also attach your Scalr logs. The
/opt/scalr-server/var/log/service folder should be sufficient.
Many thanks,
Wm. Marc O'Brien
Scalr Technical Support
On Tuesday, November 29, 2016 at 3:03:24 PM UTC-7, James Smith wrote:
>
> Marc,
>
> That's correct - I terminated the
This has been an issue since we upgraded to the Liberty release of
Openstack. With Kilo this functionality seems to work perfectly fine.
On Tuesday, November 29, 2016 at 2:05:57 PM UTC-7, Jeff Gojkovich wrote:
>
> Hello,
>
> We are trying to launch instances in an Openstack environment. But
Prior to the gevent upgrade, I was getting SSL errors in the
analytics_poller log that a quick internet search suggested was a gevent
bug. Upgrading gevent resolved that issue.
Attached is a screenshot of the openstack credentials screen, as requested.
We're running Openstack Mitaka on CentOS
Hello,
We are trying to launch instances in an Openstack environment. But when we
launch an instance that is supposed to have a cinder volume attached
scalarizr throws an exception.
I am pasting the exception below. Let me know if there are any other logs
to might help in troubleshooting.
Created a new farm from scratch.
--
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 scalr-discuss+unsubscr...@googlegroups.com.
For more options, visit
Alright. Using the officlal chef package (not the SDK) it works again.
Would be interesting why that piece of code is hardcoded in scalr?
On Tuesday, November 29, 2016 at 11:15:22 AM UTC+1, Steffen wrote:
>
> Hi,
>
> just installed the official chefdk, but its located in /opt/chefdk and is
>
Hi,
just installed the official chefdk, but its located in /opt/chefdk and is
causing the same problem.
Steffen
On Tuesday, November 29, 2016 at 9:36:54 AM UTC+1, Steffen wrote:
>
> Hi Marc,
>
> yes we upgraded from an earlier version and seeing now a new chef error
> when deploying
Okay a /opt/scalr-server/bin/scalr-server-ctl reconfigure solved that
problem.
On Tuesday, November 29, 2016 at 10:11:21 AM UTC+1, Steffen wrote:
>
> Hi,
>
> we just updated to 5.11.22 from an earlier version and its not possible to
> create any snapshots. Either EC2 or Openstack is not
Hi,
we just updated to 5.11.22 from an earlier version and its not possible to
create any snapshots. Either EC2 or Openstack is not working.
AWS:
Nov 29, 2016 10:07:25
Snapshot creation failed. Reason: Could not find the service "environment"
in the DI container.. Bundle task status changed
Hi Marc,
yes we upgraded from an earlier version and seeing now a new chef error
when deploying instances. We are running 5.11.22 now.
These are previous farms and worked before the update without any problem.
We are using the public repo and the stable release
(http://update.scalr.net/ -
10 matches
Mail list logo
