5:31 p.m.
On Tue, Mar 19, 2019 at 3:09 PM Gianluca Cecchi
<gianluca.cecchi(a)gmail.com> wrote:
On Tue, Mar 19, 2019 at 2:51 PM Miguel Duarte de Mora Barroso
<mdbarroso(a)redhat.com> wrote:
>
> On Tue, Mar 19, 2019 at 2:15 PM Gianluca Cecchi
> <gianluca.cecchi(a)gmail.com> wrote:
> >
> > On Tue, Mar 19, 2019 at 10:25 AM Miguel Duarte de Mora Barroso
<mdbarroso(a)redhat.com> wrote:
> >>
> >> >>
> >> >>
> >> >> @Gianluca Cecchi , I notice that one of your duplicate networks -
> >> >> 'ovn192' - has no ports attached. That makes it the
perfect candidate
> >> >> to be deleted, and see if it becomes 'listable' on engine.
That would
> >> >> help rule out the 'duplicate name' theory.
> >> >
> >> >
> >> > I can try. Can you give me the command to be run?
> >> > It is a test oVirt so It would be not a big problem in case of failures
in this respect.
> >>
> >> You can delete it via the UI; just be sure to delete the one without
> >> ports - it's external ID is 6110649a-db2b-4de7-8fbc-601095cfe510.
> >>
> >> It will ask you if you also want to delete it from the external
> >> provider, say yes.
> >
> >
> >
> > Inside the GUI I see only one ovn192 network and one ovn172 network and their
external ids don't match the ones without ports...
> >
> > - ovn192
> > Id: 8fd63a10-a2ba-4c56-a8e0-0bc8d70be8b5
> > External ID: 32367d8a-460f-4447-b35a-abe9ea5187e0
> >
> > - ovn172
> > Id: 7546d5d3-a0e3-40d5-9d22-cf355da47d3a
> > External ID: 64c4c17f-cd67-4e29-939e-2b952495159f
> >
> > So I think I have to delete from command line
>
> Check pastebin [0], with it you can safely delete those 2 networks.
> Last course of action would be to delete via ovn-nbctl - e.g.
> ovn-nbctl destroy logical_switch <network_id> - but hopefully it won't
> come to that.
>
> [0] - https://paste.fedoraproject.org/paste/mxVUEJZWxG-QHX0mJO1VhA
>
> >
> > Gianluca Cecchi
> >
I get this error from the first part where I should get the token id
{
"error": {
"message": "No JSON object could be decoded",
"code": 400,
"title": "Bad Request"
}
}
In your command there is:
-H 'Postman-Token: 87fa50fd-0d06-497d-b2ac-b66b78ad90b8' \
Remove that, sorry for not noticing it before. Also get rid of the
'Cache-Control: no-cache' header.
The request thus becomes:
curl -k -X POST \
https://localhost:35357/v2.0/tokens \
-H 'Content-Type: application/json' \
-d '{
"auth": {
"passwordCredentials": {
"username": <your_username@your_domain>,
"password": <your_password>
}
}
}
'
what is that sequence? where did you get it?
Also, inside the credential section
"username": XXXX,
"password": YYY
do I have to put my username and password inside single/double quotes or nothing?
eg admin@internal or "admin@internal" or what?
Between quotes - e.g. "admin@internal" and
"whatever-password-you-have".
> Thanks,
> Gianluca
>
>
>