-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"No Realm Detected" when pulling site #82
Comments
Thanks for posting this @aristomenis! @reynoldsalec @gremy it would be great to see if this UUID fail is happening for other people. anyone game to test? ill give it a try as well. |
As an addendum, I'm able to consistently reproduce this at the moment. Just now:
Error: Looks like it is the uuid and uuid portion of git-connect missing. terminatur.aliases.drushrc.php entry: $aliases['my-kalabox-test.dev'] = array(
'uri' => 'dev-my-kalabox-test.gotpantheon.com',
'db-url' => 'mysql://pantheon:f314293a0a0d46a28298b374e886b284@dbserver.dev.7e36105b-7edf-4644-a4d0-4c661716b1cb.drush.in:13465/pantheon',
'db-allows-remote' => TRUE,
'remote-host' => 'appserver.dev.7e36105b-7edf-4644-a4d0-4c661716b1cb.drush.in',
'remote-user' => 'dev.7e36105b-7edf-4644-a4d0-4c661716b1cb',
'ssh-options' => '-p 2222 -o "AddressFamily inet" -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no',
'path-aliases' => array(
'%files' => 'code/sites/default/files',
'%drush-script' => 'drush',
),
'machine-name' => 'my-kalabox-test',
'env' => 'dev',
'uuid' => '',
'built-from' => 'my-kalabox-test.dev',
'terminatur' => array(
'code' => array(
'method' => 'git',
'git-connect' => 'ssh://[email protected]:2222/~/repository.git',
),
'database' => array(
'db-user' => 'pantheon',
'db-pass' => 'f314293a0a0d46a28298b374e886b284',
'db-host' => 'dbserver.dev.7e36105b-7edf-4644-a4d0-4c661716b1cb.drush.in',
'db-port' => '13465',
'db-db' => 'pantheon',
'local-db' => 'my_kalabox_test_kala',
'method' => 'mysql',
'download-bucket' => 'NONE',
),
'files' => array(
'method' => 'rsync',
'rsync' => array(
'options' => '-rlztv --ipv4',
'ssh' => '-e \'ssh -p 2222 -o "AddressFamily inet" -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no\'',
'excludes' => '--exclude \'js\' --exclude \'css\' --exclude \'ctools\' --exclude \'imagecache\' --exclude \'xmlsitemap\' --exclude \'backup_migrate\' --exclude \'styles\' --exclude \'less\'',
'remote-files' => 'dev.7e36105b-7edf-4644-a4d0-4c661716b1cb@appserver.dev.7e36105b-7edf-4644-a4d0-4c661716b1cb.drush.in:files',
),
),
),
); |
awesome! |
K, just spun up a fresh box and have all my UUIDs as expected. Will try your steps to replicate now. |
Hmm, I wonder if something is garbaged up in my setup. |
This was apparently related to the older beta install I had of Kalabox. It had been running the "Updates Available", but apparently something didn't take or got glitched. Did a fresh install with the latest beta download and this is no longer an issue. Thanks! |
This issue also seems resolvable by logging out and logging back in with your pantheon credentials either through the UI or with |
Pirog, that does not work for me. After a clean install of OSX, and installed Kalabox v1, I was able to download three sites OK, but on the fourth I got this issue, and I've tried EVERYTHING, and it doesn't work... something is very buggy here unfortunately. |
It seems that sometimes, a random process of clearing drush cache via drush cc drush and clearing the drush cache dir, rebooting the box, logging in and out, deleting keys from pantheon, etc can make it work again, for an unknown period of time before it suddenly happens again. |
Kalastack works perfect though, except it doesn't make the hostsfile changes. |
Except... when it doesn't... i get the same thing in kalastack now. |
But I can confirm that adding the uuid manually makes it work again. It appears random WHEN it occurs though. |
it might be worth checking on the pantheon side to see if there is anything On Sun, Sep 21, 2014 at 2:49 PM, ibuildit [email protected] wrote:
Cheers, Mike Pirog |
I just ran into this issue. In my case only the UUID was missing in terminatur.aliases.drushrc.php. Manually populating this value fixed the issue. |
MAXIMO! the UUID comes from a terminus API call. I think maybe in some circumstances based likely on organizational permissions on the pantheon end these ID's are not available to all team members. i know @andrewmallis experienced this on the badcamp site as well. maybe @joshkoenig has some insight? |
@pirog Thank you for the quick response =) |
I all of a sudden started having this issue as well, only on new sites I just made Issue references here: I tried updating my terminus only and it didnt fix it |
Hey All, I'll see what I can see. That terminus issue is pretty stale but we can take a look. @labboy0276 can you see if the site uuid is missing from your drush alias? |
@pirog @andrewmallis there isn't a case where a user wouldn't have access to the site UUID, though making a specific API call for just that seems inefficient. Can you give me a bit more context on where/when this call is being made? Also cc @mikevanwinkle ;) |
@joshkoenig Yes it was, I saw that above. So I did a couple thingz. I looked at ~/.ssh in my stack and grabbed that authorized_key and put it into pantheon. Then I ended up doing was this in my stack: $ cd /etc/drush
$ rm -f terminatur.aliases.drushrc.php
$ drush ta It populated all my uuid's for all my sites & all is well. Game on |
This is all great data! On Tuesday, October 14, 2014, John Ouellet [email protected] wrote:
Cheers, Mike Pirog |
Got it. We should figure out how to make the |
Agreed. Been on the docket for awhile but alas THE THINGS. Instead of fixing up terminatur it may make more sense and would be more On Tuesday, October 14, 2014, Josh Koenig [email protected] wrote:
Cheers, Mike Pirog |
I can confirm the missing UUIDs + same symptoms described above have plagued me, and the resolution by @labboy0276 to regenerate terminatur.aliases.drushrc.php solves the problem. |
OHHHH ... I think I might have my finger on the pulse of this one now. Will try out in a sec and report back On Tuesday, October 14, 2014, Andrew_Mallis [email protected]
Cheers, Mike Pirog |
Like andrewmallils, I had the same symptoms and @labboy0276 's resolution worked. Am using the latest version of kalastack. |
I will repeat the last post... Like andrewmallils, I had the same symptoms and @labboy0276 's resolution worked. Am using the latest version of kalastack. |
I'm not sure if this is tied to this issue or not, but this is what I was experiencing on the issue #156 referenced by reynoldsalec. I can't get kalabox to start up at all. Everytime I try I get this window. |
Hello,
Error:
"Request failed: 403 "No realm detected." [failed] Could not clone code from the remote repository. Check that your SSH key is loaded and the codeserver is reachable."
Verified that I could git clone the site from Kalabox's SSH - so no issue with SSH key, and codeserver is reachable.
Same error generated when trying:
drush pullsite mysite.dev --files
Tried updating aliases, but same error.
After a little spelunking, I found that the following fields were vacant in the terminatur.aliases.drushrc.php:
Not sure why this happened, but in case anyone comes across the same issue, here is the fix I used.
Cheers,
Ari
The text was updated successfully, but these errors were encountered: