-
Notifications
You must be signed in to change notification settings - Fork 30
Rackspace RackConnect doesn't work #95
Comments
I can confirm that this is busted. Would it be possible to list this somewhere in the docs on the CoreOS site? I am on RackConnect and its a pretty painful situation now to have put some time into setting up CoreOS only to have the rug pulled out. Thanks for the great work on CoreOS, shame I cant use it! |
@nnnnathann We're continuing to try and work through this with Rackspace. I can assure you, you're not the only customer concerned by this. |
I'm piling on this issue as well. Let me know if you need help with anything - testing, hacking, whatever 👍 |
I would be willing to help as well, FYI :) |
I've heard from Rackspace Support that RackConnect version 3 should be compatible with CoreOS since it does all the network munging underneath the VM, so there's no need to run scripts on the VM itself. RackConnect v3 is out now, but only for new accounts, they haven't offered to upgrade me yet. |
Anyone know anything about the status of this? Otherwise I'm planning on following up with our account manager at Rackspace and see what's going on |
Sorry, I haven't heard anything. Still haven't been able to use CoreOS for work, sadly. |
Same here, I'll let you know what I hear from RS Cheers nathan |
Hey everyone! Racker here! CoreOS is confirmed working with RCv3. Upgrades from RCv2 to RCv3 are currently only possible through manual migration. You can however create another cloud account and connect it to your network device but currently RCv2 and RCv3 don't like to coexist. If you have questions about getting migrated to RCv3 give us a call and talk to your NetSec team about migrating to RCv3. |
Hey guys, Cheers |
Sounds like the answer is to use RCv3. |
No description provided.
The text was updated successfully, but these errors were encountered: