Activity
From 10/08/2015 to 11/06/2015
11/06/2015
- 06:58 PM Bug #12305: foreman-one We're sorry, but something went wrong.
- attaching my full strace for saving the compute_profile
- 06:15 PM Bug #12305: foreman-one We're sorry, but something went wrong.
- Well okay, after reading your message again and playing arround I found out I get the same error you have on saving t...
- 06:06 PM Bug #12305: foreman-one We're sorry, but something went wrong.
- Hi Tim,
this error look familiar. I think I had this error too, before using that fork which Eyal suggested. Which... - 09:59 AM Bug #12305: foreman-one We're sorry, but something went wrong.
- Thanks for the hint. Using that fork I get a lot further along. But I still can't save a compute profile. Now I get t...
11/04/2015
- 10:27 AM Bug #12305: foreman-one We're sorry, but something went wrong.
- Tim Verhoeven wrote:
> I'm having the same issue. Basically it looks like the API for plugins and more specific comp... - 09:37 AM Bug #12305: foreman-one We're sorry, but something went wrong.
- I'm having the same issue. Basically it looks like the API for plugins and more specific compute resources has been c...
10/25/2015
- 05:57 PM Bug #12305: foreman-one We're sorry, but something went wrong.
- The ONE plugin seems not to be maintained by the original authors at the moment and is broken since at least Foreman ...
- 03:23 PM Bug #12305: foreman-one We're sorry, but something went wrong.
- Sorry, just realized it's in digital-ocean plugin part.. I don't know how to move it to the correct one..
- 03:21 PM Bug #12305 (New): foreman-one We're sorry, but something went wrong.
- Hi,
I'm getting this error after adding formen-one plugin and trying to edit one of the compute profile (small/med...
Also available in: Atom