[Yahoo-eng-team] [Bug 1811352] [NEW] Include neutron CLI floatingip port-forwarding support

2019-01-11 Thread varocho
Public bug reported:

The floating ip port-forwarding is supported since Rocky by neutron API:

https://developer.openstack.org/api-ref/network/v2/index.html?expanded
=create-port-forwarding-detail#floating-ips-port-forwarding

but the neutron client does not include this option yet.
Also floatingip-update method is missing.

It should include an option similar to this for floatingip
*-create/*-update

$ neutron floatingip-create  --port-forwarding
protocol=tcp,internal_port_id=,internal_port=,external_port=

You should be able to repeat --port-forwarding several times

Also for floatingip-update with and extra option:
--port-forwarding clean

To remove the current port-forwarding rules list.

* Version: OpenStack Rocky

** Affects: neutron
 Importance: Undecided
 Status: New

** Description changed:

- 
- The floating ip port-forwarding is supported since Rocy by neutron API:
+ The floating ip port-forwarding is supported since Rocky by neutron API:
  
  https://developer.openstack.org/api-ref/network/v2/index.html?expanded
  =create-port-forwarding-detail#floating-ips-port-forwarding
  
  but the neutron client does not include this option yet.
  Also floatingip-update method is missing.
  
- 
- It should include an option similar to this for floatingip *-create/*-update
+ It should include an option similar to this for floatingip
+ *-create/*-update
  
  $ neutron floatingip-create  --port-forwarding
  
protocol=tcp,internal_port_id=,internal_port=,external_port=
  
  You should be able to repeat --port-forwarding several times
  
  Also for floatingip-update with and extra option:
  --port-forwarding clean
  
  To remove the current port-forwarding rules list.
  
  * Version: OpenStack Rocky

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1811352

Title:
  Include neutron CLI floatingip port-forwarding support

Status in neutron:
  New

Bug description:
  The floating ip port-forwarding is supported since Rocky by neutron
  API:

  https://developer.openstack.org/api-ref/network/v2/index.html?expanded
  =create-port-forwarding-detail#floating-ips-port-forwarding

  but the neutron client does not include this option yet.
  Also floatingip-update method is missing.

  It should include an option similar to this for floatingip
  *-create/*-update

  $ neutron floatingip-create  --port-forwarding
  
protocol=tcp,internal_port_id=,internal_port=,external_port=

  You should be able to repeat --port-forwarding several times

  Also for floatingip-update with and extra option:
  --port-forwarding clean

  To remove the current port-forwarding rules list.

  * Version: OpenStack Rocky

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1811352/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1809237] Re: application credentials "projec ID" fiield is empty using SSO

2018-12-20 Thread varocho
This is a horizon issue:

https://bugs.launchpad.net/horizon/+bug/1809267


** Changed in: keystone
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1809237

Title:
  application credentials "projec ID" fiield is empty using SSO

Status in OpenStack Identity (keystone):
  Invalid

Bug description:
  Hi

  We found this issue testing the new application credential feature
  from Rocky dashboard. Our external user are using a SSO to get access
  to openstack, they are mapped correctly to an internal project.
  Unfortunately when they request a new application credential the
  "project ID" field is empty so they get this error message when they
  try to use the credential from the client:

  $ openstack application credential list
  need one of hex, bytes, bytes_le, fields, or int (HTTP 400) (Request-ID: 
req-12f90f0f-319f-4b42-895a-a921f274d9ac)

  
  As admin the user's app credential looks like this:

  # openstack application credential list --user 
bb762ad156de46f6888bf2ae1001cade
  
+--+-++--++
  | ID   | Name| Project ID | 
Description  | Expires At |
  
+--+-++--++
  | a7300cb1848341188c408a5cb9069b1b | myappcredential | None   | This is a 
app credential test valid for a month. | 2019-01-31T18:00:00.00 |
  
+--+-++--++

  
  Any clue why we get a null Project ID using a SSO?

  Cheers ant thanks!
  Alvaro

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1809237/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1809267] [NEW] application credentials "projec ID" field is empty using SSO

2018-12-20 Thread varocho
Public bug reported:

Hi

We found this issue testing the new application credential feature from
Rocky dashboard. Our external user are using a SSO to get access to
openstack, they are mapped correctly to an internal project.
Unfortunately when they request a new application credential the
"project ID" field is empty so they get this error message when they try
to use the credential from the client:

$ openstack application credential list
need one of hex, bytes, bytes_le, fields, or int (HTTP 400) (Request-ID: 
req-12f90f0f-319f-4b42-895a-a921f274d9ac)

As admin the user's app credential looks like this:

# openstack application credential list --user bb762ad156de46f6888bf2ae1001cade
+--+-++--++
| ID | Name | Project ID | Description | Expires At |
+--+-++--++
| a7300cb1848341188c408a5cb9069b1b | myappcredential | None | This is a app 
credential test valid for a month. | 2019-01-31T18:00:00.00 |
+--+-++--++

Any clue why we get a null Project ID using a SSO?

Cheers ant thanks!
Alvaro

** Affects: horizon
 Importance: Undecided
 Status: New


** Tags: federated rocky sso

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1809267

Title:
  application credentials "projec ID" field is empty using SSO

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Hi

  We found this issue testing the new application credential feature
  from Rocky dashboard. Our external user are using a SSO to get access
  to openstack, they are mapped correctly to an internal project.
  Unfortunately when they request a new application credential the
  "project ID" field is empty so they get this error message when they
  try to use the credential from the client:

  $ openstack application credential list
  need one of hex, bytes, bytes_le, fields, or int (HTTP 400) (Request-ID: 
req-12f90f0f-319f-4b42-895a-a921f274d9ac)

  As admin the user's app credential looks like this:

  # openstack application credential list --user 
bb762ad156de46f6888bf2ae1001cade
  
+--+-++--++
  | ID | Name | Project ID | Description | Expires At |
  
+--+-++--++
  | a7300cb1848341188c408a5cb9069b1b | myappcredential | None | This is a app 
credential test valid for a month. | 2019-01-31T18:00:00.00 |
  
+--+-++--++

  Any clue why we get a null Project ID using a SSO?

  Cheers ant thanks!
  Alvaro

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1809267/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1809237] [NEW] application credentials "projec ID" fiield is empty using SSO

2018-12-20 Thread varocho
Public bug reported:

Hi

We found this issue testing the new application credential feature from
Rocky dashboard. Our external user are using a SSO to get access to
openstack, they are mapped correctly to an internal project.
Unfortunately when they request a new application credential the
"project ID" field is empty so they get this error message when they try
to use the credential from the client:

$ openstack application credential list
need one of hex, bytes, bytes_le, fields, or int (HTTP 400) (Request-ID: 
req-12f90f0f-319f-4b42-895a-a921f274d9ac)


As admin the user's app credential looks like this:

# openstack application credential list --user bb762ad156de46f6888bf2ae1001cade
+--+-++--++
| ID   | Name| Project ID | Description 
 | Expires At |
+--+-++--++
| a7300cb1848341188c408a5cb9069b1b | myappcredential | None   | This is a 
app credential test valid for a month. | 2019-01-31T18:00:00.00 |
+--+-++--++


Any clue why we get a null Project ID using a SSO?

Cheers ant thanks!
Alvaro

** Affects: keystone
 Importance: Undecided
 Status: New


** Tags: rocky

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1809237

Title:
  application credentials "projec ID" fiield is empty using SSO

Status in OpenStack Identity (keystone):
  New

Bug description:
  Hi

  We found this issue testing the new application credential feature
  from Rocky dashboard. Our external user are using a SSO to get access
  to openstack, they are mapped correctly to an internal project.
  Unfortunately when they request a new application credential the
  "project ID" field is empty so they get this error message when they
  try to use the credential from the client:

  $ openstack application credential list
  need one of hex, bytes, bytes_le, fields, or int (HTTP 400) (Request-ID: 
req-12f90f0f-319f-4b42-895a-a921f274d9ac)

  
  As admin the user's app credential looks like this:

  # openstack application credential list --user 
bb762ad156de46f6888bf2ae1001cade
  
+--+-++--++
  | ID   | Name| Project ID | 
Description  | Expires At |
  
+--+-++--++
  | a7300cb1848341188c408a5cb9069b1b | myappcredential | None   | This is a 
app credential test valid for a month. | 2019-01-31T18:00:00.00 |
  
+--+-++--++

  
  Any clue why we get a null Project ID using a SSO?

  Cheers ant thanks!
  Alvaro

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1809237/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp