POA geni_sharelan

2 views
Skip to first unread message

Ezra Kissel

unread,
Jun 9, 2014, 6:15:45 PM6/9/14
to geni-...@googlegroups.com
Hi,

Earlier today I started a slice and was able to create a shared vlan at
the IG BBN rack. I then needed to make some changes to the resources,
so I deleted the relevant sliver and recreated it. I also unshared the
vlan relating to those resources. The new resources came up but when I
tried to do the POA again, I got this error:

https://boss.instageni.gpolab.bbn.com/spewlogfile.php3?logfile=1130ddc105c23a56dbab41ec1a3e4444

I did the exact same thing just now at PG Utah (different slice) without
any issues. Any ideas?

thanks,
- ezra

Leigh Stoller

unread,
Jun 9, 2014, 6:46:42 PM6/9/14
to geni-...@googlegroups.com
> I did the exact same thing just now at PG Utah (different slice) without any issues. Any ideas?

None, but I just saw message go by that indicates it worked a few
minutes later. Did you do anything in the meantime?

Leigh





Ezra Kissel

unread,
Jun 9, 2014, 7:00:18 PM6/9/14
to geni-...@googlegroups.com
On 6/9/2014 6:46 PM, Leigh Stoller wrote:
>> I did the exact same thing just now at PG Utah (different slice) without any issues. Any ideas?
>
> None, but I just saw message go by that indicates it worked a few
> minutes later. Did you do anything in the meantime?
>
> Leigh
>

I walked away for a while, took some deep breaths, and found where I
went astray. I created the sliver with a different, active slice name
than I was doing the POA command with, and finally realized that "Slice
credential not provided" is apparently the same as "no such sliver
found" in the POA context. I'm learning, slowly, but I'm learning...

I also found a typo in my stitching/shared_vlan rspec that I posted in
that other thread. The stitcher just completed on a second attempt so
I'm hoping everything will be happy now. *crosses fingers*
Reply all
Reply to author
Forward
0 new messages