[Yahoo-eng-team] [Bug 1645597] [NEW] NoCloud module doesn't put GATEWAY and DNS* settings in ifcfg-* file in Fedora25/cloud-init 0.7.8
Public bug reported: Hello all! NoCloud module omits setting GATEWAY and DNS* variables while configuring /etc/sysconfig/network-scripts/ifcfg-eth0 file with BOOTPROTO=static. As a result configured system lacks Internet connectivity. meta-data file used: instance-id: $VMID local-hostname: $VMNAME hostname: $VMNAME network-interfaces: | auto eth0 iface eth0 inet static hwaddr $MAC address $IPADDRESS netmask $NETMASK gateway $GATEWAY dns-nameservers $DNSSERVERS dns-search $SEARCHDOMAINS Tis problem takes place on Fedora 25 with cloud-init 0.7.8 ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1645597 Title: NoCloud module doesn't put GATEWAY and DNS* settings in ifcfg-* file in Fedora25/cloud-init 0.7.8 Status in cloud-init: New Bug description: Hello all! NoCloud module omits setting GATEWAY and DNS* variables while configuring /etc/sysconfig/network-scripts/ifcfg-eth0 file with BOOTPROTO=static. As a result configured system lacks Internet connectivity. meta-data file used: instance-id: $VMID local-hostname: $VMNAME hostname: $VMNAME network-interfaces: | auto eth0 iface eth0 inet static hwaddr $MAC address $IPADDRESS netmask $NETMASK gateway $GATEWAY dns-nameservers $DNSSERVERS dns-search $SEARCHDOMAINS Tis problem takes place on Fedora 25 with cloud-init 0.7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1645597/+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 1641816] Re: enable ``cache_on_issue`` by default
Reviewed: https://review.openstack.org/38 Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=7765130bd6d18480f1207dd853601bc4adc8a957 Submitter: Jenkins Branch:master commit 7765130bd6d18480f1207dd853601bc4adc8a957 Author: Matt Fischer Date: Thu Oct 6 12:43:38 2016 -0600 cache_on_issue default to true If caching is globally enabled and enabled for tokens then we should default to have cache_on_issue default to True as well. This commit also adds one clarifying sentence to the config file comments since this value has no effect unless caching is globally enabled and enabled in the [token] section. Closes-Bug: #1641816 Change-Id: I2797964ef0bb5641d8c1a208e1b5dcf567c1437f ** Changed in: keystone Status: In Progress => Fix Released -- 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/1641816 Title: enable ``cache_on_issue`` by default Status in OpenStack Identity (keystone): Fix Released Bug description: keystone provides a configuration option to "pre-cache" a token, it is cached upon issue. In the Newton release this was disabled by default, we should enable it in Ocata. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1641816/+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 1645571] [NEW] keystone-manage mapping_populate fails and gives unhandled exception
Public bug reported: Running keystone-manage mapping_populate --domain-name fails silently with no error message displayed on screen. The logs from keystone.log is displayed below. 2016-11-18 07:22:26.470 1384 CRITICAL keystone [req-a2de669b-a645-42b0-8af6-a36e1cf53c54 - - - - -] UnboundLocalError: local variable 'domain_id' referenced before assignment 2016-11-18 07:22:26.470 1384 ERROR keystone Traceback (most recent call last): 2016-11-18 07:22:26.470 1384 ERROR keystone File "/usr/bin/keystone-manage", line 10, in 2016-11-18 07:22:26.470 1384 ERROR keystone sys.exit(main()) 2016-11-18 07:22:26.470 1384 ERROR keystone File "/usr/lib/python2.7/site-packages/keystone/cmd/manage.py", line 43, in main 2016-11-18 07:22:26.470 1384 ERROR keystone cli.main(argv=sys.argv, config_files=config_files) 2016-11-18 07:22:26.470 1384 ERROR keystone File "/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 1256, in main 2016-11-18 07:22:26.470 1384 ERROR keystone CONF.command.cmd_class.main() 2016-11-18 07:22:26.470 1384 ERROR keystone File "/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 1202, in main 2016-11-18 07:22:26.470 1384 ERROR keystone 'domain': domain_id}) 2016-11-18 07:22:26.470 1384 ERROR keystone UnboundLocalError: local variable 'domain_id' referenced before assignment 2016-11-18 07:22:26.470 1384 ERROR keystone My guess is that instead of printing domain_id, we should print domain_name to avoid the error. ** Affects: keystone Importance: Undecided Status: New ** Summary changed: - keystone-manage mapping_populate fails and try catch doesn't work + keystone-manage mapping_populate fails and gives unhandled exception -- 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/1645571 Title: keystone-manage mapping_populate fails and gives unhandled exception Status in OpenStack Identity (keystone): New Bug description: Running keystone-manage mapping_populate --domain-name fails silently with no error message displayed on screen. The logs from keystone.log is displayed below. 2016-11-18 07:22:26.470 1384 CRITICAL keystone [req-a2de669b-a645-42b0-8af6-a36e1cf53c54 - - - - -] UnboundLocalError: local variable 'domain_id' referenced before assignment 2016-11-18 07:22:26.470 1384 ERROR keystone Traceback (most recent call last): 2016-11-18 07:22:26.470 1384 ERROR keystone File "/usr/bin/keystone-manage", line 10, in 2016-11-18 07:22:26.470 1384 ERROR keystone sys.exit(main()) 2016-11-18 07:22:26.470 1384 ERROR keystone File "/usr/lib/python2.7/site-packages/keystone/cmd/manage.py", line 43, in main 2016-11-18 07:22:26.470 1384 ERROR keystone cli.main(argv=sys.argv, config_files=config_files) 2016-11-18 07:22:26.470 1384 ERROR keystone File "/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 1256, in main 2016-11-18 07:22:26.470 1384 ERROR keystone CONF.command.cmd_class.main() 2016-11-18 07:22:26.470 1384 ERROR keystone File "/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 1202, in main 2016-11-18 07:22:26.470 1384 ERROR keystone 'domain': domain_id}) 2016-11-18 07:22:26.470 1384 ERROR keystone UnboundLocalError: local variable 'domain_id' referenced before assignment 2016-11-18 07:22:26.470 1384 ERROR keystone My guess is that instead of printing domain_id, we should print domain_name to avoid the error. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1645571/+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 1645568] [NEW] keystone-manage mapping_purge fails silently
Public bug reported:
Running the command keystone-manage mapping_purge, no output is given
but I get these messages in keystone.log
2016-11-18 07:41:22.807 2404 CRITICAL keystone [-] ValueError: At least one
option must be provided
2016-11-18 07:41:22.807 2404 ERROR keystone Traceback (most recent call last):
2016-11-18 07:41:22.807 2404 ERROR keystone File "/usr/bin/keystone-manage",
line 10, in
2016-11-18 07:41:22.807 2404 ERROR keystone sys.exit(main())
2016-11-18 07:41:22.807 2404 ERROR keystone File
"/usr/lib/python2.7/site-packages/keystone/cmd/manage.py", line 43, in main
2016-11-18 07:41:22.807 2404 ERROR keystone cli.main(argv=sys.argv,
config_files=config_files)
2016-11-18 07:41:22.807 2404 ERROR keystone File
"/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 1257, in main
2016-11-18 07:41:22.807 2404 ERROR keystone CONF.command.cmd_class.main()
2016-11-18 07:41:22.807 2404 ERROR keystone File
"/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 830, in main
2016-11-18 07:41:22.807 2404 ERROR keystone validate_options()
2016-11-18 07:41:22.807 2404 ERROR keystone File
"/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 813, in
validate_options
2016-11-18 07:41:22.807 2404 ERROR keystone raise ValueError(_('At least
one option must be provided'))
2016-11-18 07:41:22.807 2404 ERROR keystone ValueError: At least one option
must be provided
2016-11-18 07:41:22.807 2404 ERROR keystone
Using --help says arguments needed are optional.
I used --all option to check and the command was executed successfully. The way
I see it is some arguments have been marked optional when they are actually
necessary.
** Affects: keystone
Importance: Undecided
Status: New
--
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/1645568
Title:
keystone-manage mapping_purge fails silently
Status in OpenStack Identity (keystone):
New
Bug description:
Running the command keystone-manage mapping_purge, no output is given
but I get these messages in keystone.log
2016-11-18 07:41:22.807 2404 CRITICAL keystone [-] ValueError: At least one
option must be provided
2016-11-18 07:41:22.807 2404 ERROR keystone Traceback (most recent call last):
2016-11-18 07:41:22.807 2404 ERROR keystone File
"/usr/bin/keystone-manage", line 10, in
2016-11-18 07:41:22.807 2404 ERROR keystone sys.exit(main())
2016-11-18 07:41:22.807 2404 ERROR keystone File
"/usr/lib/python2.7/site-packages/keystone/cmd/manage.py", line 43, in main
2016-11-18 07:41:22.807 2404 ERROR keystone cli.main(argv=sys.argv,
config_files=config_files)
2016-11-18 07:41:22.807 2404 ERROR keystone File
"/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 1257, in main
2016-11-18 07:41:22.807 2404 ERROR keystone CONF.command.cmd_class.main()
2016-11-18 07:41:22.807 2404 ERROR keystone File
"/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 830, in main
2016-11-18 07:41:22.807 2404 ERROR keystone validate_options()
2016-11-18 07:41:22.807 2404 ERROR keystone File
"/usr/lib/python2.7/site-packages/keystone/cmd/cli.py", line 813, in
validate_options
2016-11-18 07:41:22.807 2404 ERROR keystone raise ValueError(_('At least
one option must be provided'))
2016-11-18 07:41:22.807 2404 ERROR keystone ValueError: At least one option
must be provided
2016-11-18 07:41:22.807 2404 ERROR keystone
Using --help says arguments needed are optional.
I used --all option to check and the command was executed successfully. The
way I see it is some arguments have been marked optional when they are actually
necessary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1645568/+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 1641645] Re: PCI: A user who's password has expired must ask an admin to reset their password.
Fix proposed to branch: master Review: https://review.openstack.org/404022 ** Changed in: keystone Status: Opinion => In Progress -- 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/1641645 Title: PCI: A user who's password has expired must ask an admin to reset their password. Status in OpenStack Identity (keystone): In Progress Bug description: As noted in the bug title, this is a cumbersome process, a user should be able to reset their password if it expired. (and potentially if locked out -- that's up for debate) (Discussed at 11/22/16 meeting, locked out from too many attempts should have to ask an admin) To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1641645/+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 1633006] Re: Post metering-label-rules API returns 500 when the body has wrong metering_label_id
*** This bug is a duplicate of bug 1608378 ***
https://bugs.launchpad.net/bugs/1608378
** This bug has been marked a duplicate of bug 1608378
Creating metering-label-rule with non-existent UUID of metering_label_id
raised 500 Internal Server Error
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1633006
Title:
Post metering-label-rules API returns 500 when the body has wrong
metering_label_id
Status in neutron:
In Progress
Bug description:
When we calls metering-label-rules POST API with wrong
metering_label_id, we catch 500 from Neutron server.
$ curl -g -i -X POST
http://127.0.0.1:9696/v2.0/metering/metering-label-rules.json -H "User-Agent:
python-neutronclient" -H "Content-Type: application/json" -H "Accept:
application/json" -H "X-Auth-Token: $TOKEN" -d '{"metering_label_rule":
{"remote_ip_prefix": "10.0.0.0/24", "direction": "ingress",
"metering_label_id": "43e7dfd6-0deb-427b-9abc-5eaf5ada5040"}}'
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 150
X-Openstack-Request-Id: req-7242ca76-283a-4589-ae69-7214622b804b
Date: Thu, 13 Oct 2016 09:22:43 GMT
{"NeutronError": {"message": "Request Failed: internal server error
while processing your request.", "type": "HTTPInternalServerError",
"detail": ""}}
Error log:
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource self._affected_rows
= self._read_query_result(unbuffered=unbuffered)
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 1019, in
_read_query_result
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource result.read()
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 1302, in
read
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource first_packet =
self.connection._read_packet()
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 981, in
_read_packet
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource packet.check_error()
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 393, in
check_error
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource
err.raise_mysql_exception(self._data)
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/pymysql/err.py", line 107, in
raise_mysql_exception
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource raise
errorclass(errno, errval)
2016-10-13 09:22:43.156 TRACE neutron.api.v2.resource DBReferenceError:
(pymysql.err.IntegrityError) (1452, u'Cannot add or update a child row: a
foreign key constraint fails (`neutron`.`meteringlabelrules`, CONSTRAINT
`meteringlabelrules_ibfk_1` FOREIGN KEY (`metering_label_id`) REFERENCES
`meteringlabels` (`id`) ON DELETE CASCADE)') [SQL: u'INSERT INTO
meteringlabelrules (id, direction, remote_ip_prefix, metering_label_id,
excluded) VALUES (%(id)s, %(direction)s, %(remote_ip_prefix)s,
%(metering_label_id)s, %(excluded)s)'] [parameters: {'remote_ip_prefix':
u'10.0.0.0/24', 'direction': u'ingress', 'metering_label_id':
u'43e7dfd6-0deb-427b-9abc-5eaf5ada5040', 'id':
'ee5358b7-7326-42d2-be37-829b97f945af', 'excluded': 0}]
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1633006/+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 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR
** Changed in: anvil Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1608980 Title: Remove MANIFEST.in as it is not explicitly needed by PBR Status in anvil: Invalid Status in craton: Fix Released Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in gce-api: Fix Released Status in Karbor: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: In Progress Status in Kosmos: Fix Released Status in Magnum: Fix Released Status in masakari: Fix Released Status in neutron: Fix Released Status in Neutron LBaaS Dashboard: Confirmed Status in octavia: Fix Released Status in os-vif: In Progress Status in python-searchlightclient: In Progress Status in OpenStack Search (Searchlight): Fix Released Status in Solum: Fix Released Status in Swift Authentication: In Progress Status in OpenStack Object Storage (swift): In Progress Status in Tricircle: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in watcher: Fix Released Status in Zun: Fix Released Bug description: PBR do not explicitly require MANIFEST.in, so it can be removed. Snippet from: http://docs.openstack.org/infra/manual/developers.html Manifest Just like AUTHORS and ChangeLog, why keep a list of files you wish to include when you can find many of these in git. MANIFEST.in generation ensures almost all files stored in git, with the exception of .gitignore, .gitreview and .pyc files, are automatically included in your distribution. In addition, the generated AUTHORS and ChangeLog files are also included. In many cases, this removes the need for an explicit ‘MANIFEST.in’ file To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1608980/+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 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR
** Also affects: os-vif Importance: Undecided Status: New ** Changed in: os-vif Assignee: (unassigned) => Spencer Yu (yushb) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1608980 Title: Remove MANIFEST.in as it is not explicitly needed by PBR Status in anvil: In Progress Status in craton: Fix Released Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in gce-api: Fix Released Status in Karbor: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: In Progress Status in Kosmos: Fix Released Status in Magnum: Fix Released Status in masakari: Fix Released Status in neutron: Fix Released Status in Neutron LBaaS Dashboard: Confirmed Status in octavia: Fix Released Status in os-vif: In Progress Status in python-searchlightclient: In Progress Status in OpenStack Search (Searchlight): Fix Released Status in Solum: Fix Released Status in Swift Authentication: In Progress Status in OpenStack Object Storage (swift): In Progress Status in Tricircle: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in watcher: Fix Released Status in Zun: Fix Released Bug description: PBR do not explicitly require MANIFEST.in, so it can be removed. Snippet from: http://docs.openstack.org/infra/manual/developers.html Manifest Just like AUTHORS and ChangeLog, why keep a list of files you wish to include when you can find many of these in git. MANIFEST.in generation ensures almost all files stored in git, with the exception of .gitignore, .gitreview and .pyc files, are automatically included in your distribution. In addition, the generated AUTHORS and ChangeLog files are also included. In many cases, this removes the need for an explicit ‘MANIFEST.in’ file To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1608980/+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 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR
** Also affects: anvil Importance: Undecided Status: New ** Changed in: anvil Assignee: (unassigned) => Jane Lee (lijing) ** Changed in: anvil Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1608980 Title: Remove MANIFEST.in as it is not explicitly needed by PBR Status in anvil: In Progress Status in craton: Fix Released Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in gce-api: Fix Released Status in Karbor: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: In Progress Status in Kosmos: Fix Released Status in Magnum: Fix Released Status in masakari: Fix Released Status in neutron: Fix Released Status in Neutron LBaaS Dashboard: Confirmed Status in octavia: Fix Released Status in os-vif: In Progress Status in python-searchlightclient: In Progress Status in OpenStack Search (Searchlight): Fix Released Status in Solum: Fix Released Status in Swift Authentication: In Progress Status in OpenStack Object Storage (swift): In Progress Status in Tricircle: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in watcher: Fix Released Status in Zun: Fix Released Bug description: PBR do not explicitly require MANIFEST.in, so it can be removed. Snippet from: http://docs.openstack.org/infra/manual/developers.html Manifest Just like AUTHORS and ChangeLog, why keep a list of files you wish to include when you can find many of these in git. MANIFEST.in generation ensures almost all files stored in git, with the exception of .gitignore, .gitreview and .pyc files, are automatically included in your distribution. In addition, the generated AUTHORS and ChangeLog files are also included. In many cases, this removes the need for an explicit ‘MANIFEST.in’ file To manage notifications about this bug go to: https://bugs.launchpad.net/anvil/+bug/1608980/+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 1645545] [NEW] remove filtering of ANSI escape sequences in the console output
Public bug reported: Since XML output is not supported in v2.1, filtering out ANSI esacpe sequences is unnecessary. This affects our application which replies on those characters when consuming the output of the os-console-output API. ** Affects: nova Importance: Undecided Status: New ** Summary changed: - remove filtering of ensi escape characters in the console output + remove filtering of ANSI escape characters in the console output ** Summary changed: - remove filtering of ANSI escape characters in the console output + remove filtering of ANSI escape sequences in the console output -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1645545 Title: remove filtering of ANSI escape sequences in the console output Status in OpenStack Compute (nova): New Bug description: Since XML output is not supported in v2.1, filtering out ANSI esacpe sequences is unnecessary. This affects our application which replies on those characters when consuming the output of the os-console-output API. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1645545/+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 1645547] [NEW] The qrouter namespace can't be removed when l3-agent rebooting.
Public bug reported: When l3-agent rebooting, if the action removing a qrouter namespace happens, and later l3-agent works correctly, but the qrouter namespace removed still exists in linux net namespace. I try again and again, the action can't be synchronised. ** Affects: neutron Importance: Undecided Assignee: siyingchun (wintersi) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => siyingchun (wintersi) ** Changed in: neutron Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1645547 Title: The qrouter namespace can't be removed when l3-agent rebooting. Status in neutron: In Progress Bug description: When l3-agent rebooting, if the action removing a qrouter namespace happens, and later l3-agent works correctly, but the qrouter namespace removed still exists in linux net namespace. I try again and again, the action can't be synchronised. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1645547/+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 1642517] Re: several resources lack revision_on_change attribute to bump the version of their parent resources
Reviewed: https://review.openstack.org/400161 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3b610a1debdfb99def758406b1604aa3273edeea Submitter: Jenkins Branch:master commit 3b610a1debdfb99def758406b1604aa3273edeea Author: Lujin Date: Mon Nov 21 18:19:04 2016 +0900 Add missing revises_on_change attribute This patch adds revises_on_change attribute to the following models and API tests to ensure the correct behaviour: ExternalNetwork (Network) RouterExtraAttributes (Router) QosPortPolicyBinding (Port) QosNetworkPolicyBinding (Network) PortBindingPort (Port) SegmentHostMapping (Network Segment) Change-Id: I8bda9fc940e99d18bab2b4229198374f1cabf84b Closes-Bug: #1642517 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1642517 Title: several resources lack revision_on_change attribute to bump the version of their parent resources Status in neutron: Fix Released Bug description: I went through some codes related to bumping parent resources revision number when children resources, which are not top-level neutron objects, are update. I found the following children resources lack of "revises_on_change" attribute, which is used to bump parent resources' revision number. * ExternalNetwork (Network) http://paste.openstack.org/show/589687/ * RouterExtraAttributes (Router) http://paste.openstack.org/show/589690/ * QosPortPolicyBinding (Port) http://paste.openstack.org/show/589834/ * QosNetworkPolicyBinding (Network) http://paste.openstack.org/show/589835/ * PortBindingPort (Port) * SegmentHostMapping (Network Segment) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1642517/+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 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR
** Also affects: keystonemiddleware Importance: Undecided Status: New ** Changed in: keystonemiddleware Assignee: (unassigned) => Spencer Yu (yushb) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1608980 Title: Remove MANIFEST.in as it is not explicitly needed by PBR Status in craton: Fix Released Status in DragonFlow: Fix Released Status in ec2-api: Fix Released Status in gce-api: Fix Released Status in Karbor: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in keystonemiddleware: In Progress Status in Kosmos: Fix Released Status in Magnum: Fix Released Status in masakari: Fix Released Status in neutron: Fix Released Status in Neutron LBaaS Dashboard: Confirmed Status in octavia: Fix Released Status in python-searchlightclient: In Progress Status in OpenStack Search (Searchlight): Fix Released Status in Solum: Fix Released Status in Swift Authentication: In Progress Status in OpenStack Object Storage (swift): In Progress Status in Tricircle: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in watcher: Fix Released Status in Zun: Fix Released Bug description: PBR do not explicitly require MANIFEST.in, so it can be removed. Snippet from: http://docs.openstack.org/infra/manual/developers.html Manifest Just like AUTHORS and ChangeLog, why keep a list of files you wish to include when you can find many of these in git. MANIFEST.in generation ensures almost all files stored in git, with the exception of .gitignore, .gitreview and .pyc files, are automatically included in your distribution. In addition, the generated AUTHORS and ChangeLog files are also included. In many cases, this removes the need for an explicit ‘MANIFEST.in’ file To manage notifications about this bug go to: https://bugs.launchpad.net/craton/+bug/1608980/+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 1645528] [NEW] The status of ports always shows "down" in the external network.
Public bug reported:
The ports' status always shows "down" as below, although all of them can
work correctly.
(neutron) port-show 061449d7-e03a-4fd0-8fda-ac05ade4f186
+---+---+
| Field | Value
|
+---+---+
| admin_state_up| True
|
| allowed_address_pairs |
|
| binding:host_id | node-180.domain.tld
|
| binding:profile | {}
|
| binding:vif_details | {"port_filter": true, "ovs_hybrid_plug": true}
|
| binding:vif_type | ovs
|
| binding:vnic_type | normal
|
| device_id | 09fa47f1-d416-4d91-8988-64cc80f6712e
|
| device_owner | network:router_interface
|
| extra_dhcp_opts |
|
| fixed_ips | {"subnet_id": "2db60f9e-39f8-4111-94b3-a9f1221307bb",
"ip_address": "10.1.224.1"} |
| id| 061449d7-e03a-4fd0-8fda-ac05ade4f186
|
| mac_address | fa:16:3e:22:9b:99
|
| name |
|
| network_id| 3ae7acdb-f800-4860-b7cb-58a133067ec8
|
| security_groups |
|
| status| DOWN
|
| tenant_id | 553db80306974742a957cc23e7453ba8
|
+---+---+
** Affects: neutron
Importance: Undecided
Assignee: siyingchun (wintersi)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => siyingchun (wintersi)
** Changed in: neutron
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1645528
Title:
The status of ports always shows "down" in the external network.
Status in neutron:
In Progress
Bug description:
The ports' status always shows "down" as below, although all of them
can work correctly.
(neutron) port-show 061449d7-e03a-4fd0-8fda-ac05ade4f186
+---+---+
| Field | Value
|
+---+---+
| admin_state_up| True
|
| allowed_address_pairs |
|
| binding:host_id | node-180.domain.tld
|
| binding:profile | {}
|
| binding:vif_details | {"port_filter": true, "ovs_hybrid_plug": true}
|
| binding:vif_type | ovs
|
| binding:vnic_type | normal
|
| device_id | 09fa47f1-d416-4d91-8988-64cc80f6712e
|
| device_owner | network:router_interface
|
| extra_dhcp_opts |
|
| fixed_ips | {"subnet_id":
"2db60f9e-39f8-4111-94b3-a9f1221307bb", "ip_address": "10.1.224.1"} |
| id| 061449d7-e03a-4fd0-8fda-ac05ade4f186
|
|
[Yahoo-eng-team] [Bug 1645516] [NEW] openswan package is not available in Ubuntu 16.04
Public bug reported: We plan to launch vpnaas service on xenial node in rally ci, however , it is failed because openswan package is not available, and we found openswan package is likely not available in Ubuntu 16.04. the error print:http://paste.openstack.org/show/590601/ issue with openswan :http://askubuntu.com/questions/801860/openswan- shows-no-installation-candidate-after-running-apt-get-update ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1645516 Title: openswan package is not available in Ubuntu 16.04 Status in neutron: New Bug description: We plan to launch vpnaas service on xenial node in rally ci, however , it is failed because openswan package is not available, and we found openswan package is likely not available in Ubuntu 16.04. the error print:http://paste.openstack.org/show/590601/ issue with openswan :http://askubuntu.com/questions/801860/openswan- shows-no-installation-candidate-after-running-apt-get-update To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1645516/+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 1640049] Re: Action services retain state, and should not
Reviewed: https://review.openstack.org/345145 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=f9b3bc7b2baeefbeafd810f285c692f6dad3983b Submitter: Jenkins Branch:master commit f9b3bc7b2baeefbeafd810f285c692f6dad3983b Author: Richard Jones Date: Thu Jul 21 13:39:27 2016 +1000 Remove use of scope from action service The scope being handed to (and retained on) the action service was being used for two purposes: 1. handing data down to the underlying wizard steps, and 2. receiving data back from the underlying wizard steps. This patch provides a mechanism for passing data down through injection, and removes the need for event-based data return by explicitly passing the captured wizard data to the submit() resolution. It also adds the controller scope to the allowed() and perform() action service handlers to grant access to contextual information without needing to attach state to the service. Change-Id: Ieb293d0a849cd84d15e7aae0a68558fde80fd2c2 Fixes-Bug: 1640049 ** Changed in: horizon Status: In Progress => Fix Released -- 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/1640049 Title: Action services retain state, and should not Status in OpenStack Dashboard (Horizon): Fix Released Bug description: AngularJS services are singletons, so storing state on them is dangerous (using the same service twice in a single context will result in that state data being indeterminate). To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1640049/+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 1598171] Re: neutron router-gateway-set --enable-snat fails
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1598171
Title:
neutron router-gateway-set --enable-snat fails
Status in neutron:
Fix Released
Bug description:
I have a Mitaka environment with 1 control node and 3 compute nodes,
all physical machines running on openSUSE Leap 42.1.
My version of neutron client:
---cut here---
control1:~ # rpm -qi python-neutronclient-3.1.1-1.1.noarch
Name: python-neutronclient
Version : 3.1.1
Release : 1.1
Architecture: noarch
Install Date: Mo 11 Apr 2016 12:13:44 CEST
Group : Development/Languages/Python
Size: 2079132
License : Apache-2.0
Signature : RSA/SHA1, Do 03 Mär 2016 16:46:07 CET, Key ID 893a90dad85f9316
Source RPM : python-neutronclient-3.1.1-1.1.src.rpm
Build Date : Do 03 Mär 2016 16:45:27 CET
Build Host : cloud118
Relocations : (not relocatable)
Vendor : obs://build.opensuse.org/Cloud:OpenStack
URL : http://launchpad.net/python-neutronclient
Summary : Openstack Network (Quantum) API Client
---cut here---
Changing the router property "enable_snat" works only in one direction. The
resource description in Horizon for "resource_types/OS::Neutron::Router/" says:
enable_snat: {description: 'Enables Source [...] update_allowed: true}
So trying to update this property in CLI (as project admin) seems to work:
control1:~ # neutron router-gateway-set --enable-snat
Set gateway for router cbc39730-34cc-4d18-986a-5b6b9b1b4e96
But actually no change has been made:
control1:~ # neutron router-list
+++-+
| id | name | external_gateway_info
|
+++-+
| cbc39730...| router01 | {"network_id": "ID", "enable_snat": false,
[...]|
+++-+
I know there's no such option in the help page for router-gateway-set
command, but if there's not I'd expect an error message. Or if it's a
valid option it should actually change this property.
Steps to reproduce:
1. Create a router with snat disabled
2. Try to enable snat via command line
Expected output:
Along with the success message ("Set gateway for router...") it should either
actually enable snat or throw an error message ("unknown option" or something
similar).
Actual output:
Success message saying router-gateway has been set, but the argument
"--enable-snat" is ignored, no changes have been applied.
I will be out of office for the next three weeks, I'll set my co-
worker in cc to this bug. If there are any questions on this issue he
will try to answer them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1598171/+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 1645509] [NEW] dnsmasq host file entries can return from the grave
Public bug reported: With a Mitaka system, if one creates a Reasonably Large Number (tm) of instances (eg 448) via: neutron port-create neutron floatingip-create nova boot --net portid= and then once they are all created, delete them via: delete all the instances via the cCLI (groups of 10 or 14 at a time waiting for CLI completion) delete all the ports (groups of 10 or 14 at a time waiting for CLI completion) delete the floating IPs (groups of 10 or 14 at a time waiting for CLI completion) then as one watches the wc -l for the dnsmasq host file, one can see it go down to an expected value of three (the three IPs for the network/subnet for DHCP and routing), but then it starts to rebound, as entries appear to return from the grave. The entries are not specific to a given compute node - they are associated with instances across all the compute nodes hosting the instances. In this specific setup, it did not appear to happen for 224 instances, or 112 etc etc. It seems to have happened at least twice out of three attempts at 448 instances. ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1645509 Title: dnsmasq host file entries can return from the grave Status in neutron: Confirmed Bug description: With a Mitaka system, if one creates a Reasonably Large Number (tm) of instances (eg 448) via: neutron port-create neutron floatingip-create nova boot --net portid= and then once they are all created, delete them via: delete all the instances via the cCLI (groups of 10 or 14 at a time waiting for CLI completion) delete all the ports (groups of 10 or 14 at a time waiting for CLI completion) delete the floating IPs (groups of 10 or 14 at a time waiting for CLI completion) then as one watches the wc -l for the dnsmasq host file, one can see it go down to an expected value of three (the three IPs for the network/subnet for DHCP and routing), but then it starts to rebound, as entries appear to return from the grave. The entries are not specific to a given compute node - they are associated with instances across all the compute nodes hosting the instances. In this specific setup, it did not appear to happen for 224 instances, or 112 etc etc. It seems to have happened at least twice out of three attempts at 448 instances. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1645509/+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 1455252] Re: enabling serial console breaks live migration
Reviewed: https://review.openstack.org/275801 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=898bb13304b68f33a130281d5acf425a1b23d171 Submitter: Jenkins Branch:master commit 898bb13304b68f33a130281d5acf425a1b23d171 Author: Markus Zoeller Date: Tue Nov 22 17:08:14 2016 +0100 libvirt: Acquire TCP ports for console during live migration During a live migration process we reserve serial ports on destination host and update domain XML during migration to use the new reserved ports from destination. If the migration succeeds we release ports on the source host. If the migration fails we release reserved ports on the destination host. Co-Authored-By: Sahid Ferdjaoui Change-Id: Ie2524191d22cca2287eb7dbaa22b74d43e43c896 Closes-Bug: #1455252 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1455252 Title: enabling serial console breaks live migration Status in OpenStack Compute (nova): Fix Released Bug description: Version: openstack-nova-compute-2014.2.2-1.el7.noarch Enabling serial console causes the live migration process to fail with the following error in nova-compute.log: nova[12362]: 2015-05-14 21:57:21.108 ERROR nova.virt.libvirt.driver [-] [instance: a4d0bd8f-666e-4606-9e2a-4c583719719e] Live Migration failure: internal error: process exited while connecting to monitor: Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. qemu-kvm: -chardev socket,id=charserial0,host=1.2.3.4,port=1,server,nowait: Failed to bind socket: Cannot assign requested address qemu-kvm: -chardev socket,id=charserial0,host=1.2.3.4,port=1,server,nowait: chardev: opening backend "socket" failed The host IP is coming from the proxyclient_address setting which can't be 0.0.0.0, but even if it is changed to 0.0.0.0 the port number stays the same and will likely conflict on the destination. If there is no port conflict the live migration will succeed. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1455252/+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 1644513] Re: (psycopg2.ProgrammingError) column "deleted" is of type integer but expression is of type boolean
Reviewed: https://review.openstack.org/403756
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=f3a280959a0237fc3b0f3eeaaa3154566f8620c0
Submitter: Jenkins
Branch:master
commit f3a280959a0237fc3b0f3eeaaa3154566f8620c0
Author: Dan Smith
Date: Mon Nov 28 07:24:21 2016 -0800
Check deleted flag in Instance.create()
An attempt to create an instance with the deleted flag set will
not work as intended, especially from instance.create(), which
can't properly pass the yet-to-be-determined deleted=id protocol.
This makes Instance.create() throw an error like the one for
being already created, and fixes the one test where we depend
on this working.
Change-Id: I60d18ca694a2eb7f333c0cf2a898cf8f17eb83dd
Closes-Bug: #1644513
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1644513
Title:
(psycopg2.ProgrammingError) column "deleted" is of type integer but
expression is of type boolean
Status in OpenStack Compute (nova):
Fix Released
Bug description:
The Telemetry gate is broken with PostgreSQL because of nova-api:
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters
[req-8ed9761f-b699-4c92-8793-7dca7296d63e
tempest-TelemetryNotificationAPITest-1553287657
tempest-TelemetryNotificationAPITest-1553287657] DBAPIError exception wrapped
from (psycopg2.ProgrammingError) column "deleted" is of type integer but
expression is of type boolean
LINE 1: ...16-11-24T09:59:34.369835'::timestamp, NULL, NULL, false, 'f2...
^
HINT: You will need to rewrite or cast the expression.
[SQL: 'INSERT INTO instances (created_at, updated_at, deleted_at, deleted,
user_id, project_id, image_ref, kernel_id, ramdisk_id, hostname, launch_index,
key_name, key_data, power_state, vm_state, task_state, memory_mb, vcpus,
root_gb, ephemeral_gb, ephemeral_key_uuid, host, node, instance_type_id,
user_data, reservation_id, launched_at, terminated_at, availability_zone,
display_name, display_description, launched_on, locked, locked_by, os_type,
architecture, vm_mode, uuid, root_device_name, default_ephemeral_device,
default_swap_device, config_drive, access_ip_v4, access_ip_v6,
auto_disk_config, progress, shutdown_terminate, disable_terminate, cell_name,
cleaned) VALUES (%(created_at)s, %(updated_at)s, %(deleted_at)s, %(deleted)s,
%(user_id)s, %(project_id)s, %(image_ref)s, %(kernel_id)s, %(ramdisk_id)s,
%(hostname)s, %(launch_index)s, %(key_name)s, %(key_data)s, %(power_state)s,
%(vm_state)s, %(task_state)s, %(memory_mb)s, %(vcpus)s, %(root_gb)s,
%(ephemeral_gb)s, %(ephemeral_ke
y_uuid)s, %(host)s, %(node)s, %(instance_type_id)s, %(user_data)s,
%(reservation_id)s, %(launched_at)s, %(terminated_at)s, %(availability_zone)s,
%(display_name)s, %(display_description)s, %(launched_on)s, %(locked)s,
%(locked_by)s, %(os_type)s, %(architecture)s, %(vm_mode)s, %(uuid)s,
%(root_device_name)s, %(default_ephemeral_device)s, %(default_swap_device)s,
%(config_drive)s, %(access_ip_v4)s, %(access_ip_v6)s, %(auto_disk_config)s,
%(progress)s, %(shutdown_terminate)s, %(disable_terminate)s, %(cell_name)s,
%(cleaned)s) RETURNING instances.id'] [parameters: {'vm_state': u'building',
'availability_zone': None, 'terminated_at': None, 'ramdisk_id':
u'52b2ce17-7bbd-42e7-beae-04c68862da89', 'instance_type_id': 11, 'user_data':
None, 'cleaned': 0, 'vm_mode': None, 'deleted_at': None, 'reservation_id':
u'r-uo48grph', 'disable_terminate': False, 'display_name':
u'tempest-ceilometer-instance-28537131', 'uuid':
'd575169b-72d8-431c-a604-7073460c8d45', 'default_swap_device': None, 'hostname'
: u'tempest-ceilometer-instance-28537131', 'launched_on': None,
'display_description': u'tempest-ceilometer-instance-28537131', 'key_data':
None, 'deleted': False, 'power_state': 0, 'default_ephemeral_device': None,
'progress': 0, 'project_id': u'859a6fcd13504baa8032ed210dc49501',
'launched_at': None, 'architecture': None, 'node': None, 'ephemeral_gb': 0,
'access_ip_v6': None, 'access_ip_v4': None, 'kernel_id':
u'8e1eaad4-cb0a-4517-95da-cec482d6169c', 'key_name': None, 'updated_at': None,
'host': None, 'root_gb': 0, 'user_id': u'f21c50ce019c40e1af23463735ba2b34',
'task_state': u'scheduling', 'shutdown_terminate': False, 'cell_name': None,
'ephemeral_key_uuid': None, 'locked': False, 'created_at':
datetime.datetime(2016, 11, 24, 9, 59, 34, 369835), 'locked_by': None,
'launch_index': 0, 'memory_mb': 64, 'vcpus': 1, 'image_ref':
u'788e-adda-45ce-8bbc-dbfe4e087941', 'root_device_name': None,
'auto_disk_config': False, 'os_type': None, 'config_drive': u''}]
2016-11-24 09:59:34.431 32192 ERROR oslo_db.sqlalchemy.exc_filters Traceback
(most recent call last):
2016-11-24 09:59:34.431 32192 ERROR oslo_d
[Yahoo-eng-team] [Bug 1645263] Re: Unable to run stack.sh on fresh new Ubuntu Xenial 16.04 LTS, script fails with "No module named 'memcache' "
python-memcache is the canonical version. I don't believe that this is a devstack issue ** Changed in: openstack-requirements Status: New => Opinion -- 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/1645263 Title: Unable to run stack.sh on fresh new Ubuntu Xenial 16.04 LTS, script fails with "No module named 'memcache' " Status in devstack: Incomplete Status in OpenStack Identity (keystone): New Status in OpenStack Global Requirements: Opinion Bug description: Unable to run stack.sh on fresh new Ubuntu Xenial 16.04 LTS, script fails with "No module named 'memcache' " Traceback: +lib/keystone:bootstrap_keystone:630 /usr/local/bin/keystone-manage bootstrap --bootstrap-username admin --bootstrap-password ubuntu --bootstrap-project-name admin --bootstrap-role-name admin --bootstrap-service-name keystone --bootstrap-region-id RegionOne --bootstrap-admin-url http://192.168.0.115/identity_admin --bootstrap-public-url http://192.168.0.115/identity --bootstrap-internal-url http://192.168.0.115/identity 2016-11-28 11:51:39.723 15663 CRITICAL keystone [-] ImportError: No module named 'memcache' 2016-11-28 11:51:39.723 15663 TRACE keystone Traceback (most recent call last): 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/bin/keystone-manage", line 10, in 2016-11-28 11:51:39.723 15663 TRACE keystone sys.exit(main()) 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/cmd/manage.py", line 45, in main 2016-11-28 11:51:39.723 15663 TRACE keystone cli.main(argv=sys.argv, config_files=config_files) 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/cmd/cli.py", line 1269, in main 2016-11-28 11:51:39.723 15663 TRACE keystone CONF.command.cmd_class.main() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/cmd/cli.py", line 365, in main 2016-11-28 11:51:39.723 15663 TRACE keystone klass = cls() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/cmd/cli.py", line 66, in __init__ 2016-11-28 11:51:39.723 15663 TRACE keystone self.load_backends() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/cmd/cli.py", line 129, in load_backends 2016-11-28 11:51:39.723 15663 TRACE keystone drivers = backends.load_backends() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/server/backends.py", line 32, in load_backends 2016-11-28 11:51:39.723 15663 TRACE keystone cache.configure_cache() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/common/cache/core.py", line 124, in configure_cache 2016-11-28 11:51:39.723 15663 TRACE keystone cache.configure_cache_region(CONF, region) 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/oslo_cache/core.py", line 201, in configure_cache_region 2016-11-28 11:51:39.723 15663 TRACE keystone '%s.' % conf.cache.config_prefix) 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/region.py", line 552, in configure_from_config 2016-11-28 11:51:39.723 15663 TRACE keystone "%swrap" % prefix, None), 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/region.py", line 417, in configure 2016-11-28 11:51:39.723 15663 TRACE keystone _config_prefix 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/api.py", line 81, in from_config_dict 2016-11-28 11:51:39.723 15663 TRACE keystone for key in config_dict 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/backends/memcached.py", line 208, in __init__ 2016-11-28 11:51:39.723 15663 TRACE keystone super(MemcacheArgs, self).__init__(arguments) 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/backends/memcached.py", line 108, in __init__ 2016-11-28 11:51:39.723 15663 TRACE keystone self._imports() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/backends/memcached.py", line 287, in _imports 2016-11-28 11:51:39.723 15663 TRACE keystone import memcache # noqa 2016-11-28 11:51:39.723 15663 TRACE keystone ImportError: No module named 'memcache' 2016-11-28 11:51:39.723 15663 TRACE keystone local.conf [[local|localrc]] USE_PYTHON3=True PYTHON3_VERSION=3.5 Python: 3.5.2 Ubuntu version (lsb_release -a): Distributor ID: Ubuntu Description: Ubuntu 16.04 LTS Release: 16.04 Codename: xenial To manage notifications about this b
[Yahoo-eng-team] [Bug 1645499] [NEW] Quota sets (os-quota-sets) Normal response codes documentation
Public bug reported: http://developer.openstack.org/api-ref/compute/?expanded=update-quotas-detail#update-quotas The above link states "Normal response codes: 200", but upon a successful update the actual response code is 201. This is a normal response code and should be listed with the 200. --- Release: 15.0.0.0b2.dev129 on 'Mon Nov 28 19:32:15 2016, commit 6195408' SHA: Source: Can't derive source file URL URL: http://developer.openstack.org/api-ref/compute/ ** Affects: nova Importance: Undecided Status: New ** Tags: api-ref -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1645499 Title: Quota sets (os-quota-sets) Normal response codes documentation Status in OpenStack Compute (nova): New Bug description: http://developer.openstack.org/api-ref/compute/?expanded=update-quotas-detail#update-quotas The above link states "Normal response codes: 200", but upon a successful update the actual response code is 201. This is a normal response code and should be listed with the 200. --- Release: 15.0.0.0b2.dev129 on 'Mon Nov 28 19:32:15 2016, commit 6195408' SHA: Source: Can't derive source file URL URL: http://developer.openstack.org/api-ref/compute/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1645499/+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 1645493] [NEW] Detail view actions do not always pass selection name to modal
Public bug reported: When clicking on actions that require a modal confirmation (such as a delete action), the modal that pops up does not propagate the name of the selected element that was clicked into the message that appears inside the modal. For example, detail views like Project > Compute > Instances > Detail View (/project/instances// or even App Catalog > Environments > Detail View (/app-catalog//services) in Murano Dashboard are affected. ** Affects: horizon Importance: Undecided Assignee: Felipe Monteiro (fm577c) Status: In Progress ** Changed in: horizon Assignee: (unassigned) => Felipe Monteiro (fm577c) -- 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/1645493 Title: Detail view actions do not always pass selection name to modal Status in OpenStack Dashboard (Horizon): In Progress Bug description: When clicking on actions that require a modal confirmation (such as a delete action), the modal that pops up does not propagate the name of the selected element that was clicked into the message that appears inside the modal. For example, detail views like Project > Compute > Instances > Detail View (/project/instances// or even App Catalog > Environments > Detail View (/app-catalog//services) in Murano Dashboard are affected. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1645493/+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 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line
This bug was fixed in the package cloud-init - 0.7.8-61-g2d2ec70-0ubuntu1 --- cloud-init (0.7.8-61-g2d2ec70-0ubuntu1) zesty; urgency=medium * debian/grub-legacy-ec2.install: install post(inst|rm) files correctly. [Simon Deziel] (LP: #1581416) * New upstream snapshot. - OpenStack: extend physical types to include hyperv, hw_veb, vhost_user. [Scott Moser] (LP: #1642679) - tests: fix assumptions that expected no eth0 in system. [Scott Moser] (LP: #1644043) - net/cmdline: Consider ip= or ip6= on command line not only ip= [Scott Moser] (LP: #1639930) - Just use file logging by default [Joshua Harlow] (LP: #1643990) - Improve formatting for ProcessExecutionError [Wesley Wiedenmeier] - flake8: fix trailing white space [Scott Moser] - Doc: various documentation fixes [Sean Bright] - cloudinit/config/cc_rh_subscription.py: Remove repos before adding [Brent Baude] - packages/redhat: fix rpm spec file. [Scott Moser] - main: set TZ in environment if not already set. [Ryan Harper] - Azure: No longer rely on walinux agent. [Scott Moser] (LP: #1538522) - disk_setup: Use sectors as unit when formatting MBR disks with sfdisk. [Daniel Watkins] (LP: #1460715) -- Scott Moser Mon, 28 Nov 2016 16:08:09 -0500 ** Changed in: cloud-init (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1639930 Title: initramfs network configuration ignored if only ip6= on kernel command line Status in cloud-init: Confirmed Status in MAAS: New Status in cloud-init package in Ubuntu: Fix Released Bug description: In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='. The code currently will return with no network configuration found if there is only ip6=... Related bugs: * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1639930/+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 1600229] Re: With only one key pair it should be selected by default in AngularJS Launch Instance
** Changed in: horizon Status: New => Opinion -- 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/1600229 Title: With only one key pair it should be selected by default in AngularJS Launch Instance Status in OpenStack Dashboard (Horizon): Opinion Bug description: In the Launch Instance panel (not the new AngularJS version) when you create a new instance and you have only one key pair, that key pair is selected by default for the instance creation. If there is more than one, anyone is selected by default an you have to select one if you want. In the new Launch Instance panel in AngularJS this is not the behaviour. when you have only one key pair it's not selected by default, you have to selected it. This may cause some unexpected user experience, because a lot of users have only one key pair and they were used to not worry about to select key pair when they create a new instance. Now, with the new panel (AngularJS), they report issues because the instance was not created with their "default key pair" and they can not SSH it. I would like to suggest to come back to the same behaviour, for the key pair selection, that we have in the not AngularJs version of the Launch Instance panel. At least make it configurable via local_settings config file. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1600229/+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 1645464] Re: InstanceNotFound stacktrace in _process_instance_vif_deleted_event
** Also affects: nova/newton Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1645464 Title: InstanceNotFound stacktrace in _process_instance_vif_deleted_event Status in OpenStack Compute (nova): In Progress Status in OpenStack Compute (nova) newton series: New Bug description: Seen in a CI run here: http://logs.openstack.org/16/393416/6/check/gate-tempest-dsvm-full- devstack-plugin-ceph-ubuntu- xenial/44f3329/logs/screen-n-cpu.txt.gz?level=TRACE#_2016-11-28_17_34_36_535 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server [req-8d784631-28c2-41b4-8175-7cfb59480838 nova service] Exception during message handling 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 155, in _process_incoming 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 225, in dispatch 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 195, in _do_dispatch 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/exception_wrapper.py", line 75, in wrapped 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server function_name, call_dict, binary) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server self.force_reraise() 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/exception_wrapper.py", line 66, in wrapped 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/compute/manager.py", line 6800, in external_instance_event 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server event.tag) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/compute/manager.py", line 6755, in _process_instance_vif_deleted_event 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server network_info = instance.info_cache.network_info 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 67, in getter 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server self.obj_load_attr(name) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/objects/instance.py", line 1063, in obj_load_attr 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server self._load_generic(attrname) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/objects/instance.py", line 819, in _load_generic 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server expected_attrs=[attrname]) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 177, in wrapper 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server args, kwargs) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/conductor/rpcapi.py", line 236, in object_class_action_versions 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server args=args, kwargs=kwargs) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/client.py", line 169, in call 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server retry=self.retry) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/transport.py", line 97, in _send 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.
[Yahoo-eng-team] [Bug 1645487] [NEW] Missing PCI-DSS 8.2.6 requiring users to change their password upon first use
Public bug reported: PCI-DSS 8.2.6 requires that users immediately change their password upon first use [1]. However, this requirement was missed in the PCI-DSS spec and implementation [2]. PCI-DSS 8.2.6 needs to be implemented in order for Keystone to be PCI compliant. [1] https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf [2] https://github.com/openstack/keystone-specs/blob/master/specs/keystone/newton/pci-dss.rst ** Affects: keystone Importance: Medium Assignee: Ron De Rose (ronald-de-rose) Status: In Progress ** Changed in: keystone Assignee: (unassigned) => Ron De Rose (ronald-de-rose) ** Changed in: keystone Importance: Undecided => Medium ** Changed in: keystone Milestone: None => ocata-2 -- 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/1645487 Title: Missing PCI-DSS 8.2.6 requiring users to change their password upon first use Status in OpenStack Identity (keystone): In Progress Bug description: PCI-DSS 8.2.6 requires that users immediately change their password upon first use [1]. However, this requirement was missed in the PCI- DSS spec and implementation [2]. PCI-DSS 8.2.6 needs to be implemented in order for Keystone to be PCI compliant. [1] https://www.pcisecuritystandards.org/documents/PCI_DSS_v3-1.pdf [2] https://github.com/openstack/keystone-specs/blob/master/specs/keystone/newton/pci-dss.rst To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1645487/+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 1645484] [NEW] Not able to update default quotas
Public bug reported: Description: Trying to update/increase the default quota for number of security_groups that can be created. Pre-conditions: User- cloud admin Project- admin Step-by-step reproduction steps: neutron $AUTH quota-default-show +-+---+ | Field | Value | +-+---+ | floatingip | 50| | network | 10| | port| 50| | rbac_policy | 10| | router | 10| | security_group | 10| | security_group_rule | 100 | | subnet | 10| | subnetpool | -1| +-+---+ Try to update the default value for security_group as for project admin: openstack $AUTH project list +--+--+ | ID | Name | +--+--+ | 3f3dccb1ec12494ab9f7024e2ddd32de | admin +--+--+ neutron $AUTH quota-update --tenant_id 3f3dccb1ec12494ab9f7024e2ddd32de security_group 15 Invalid values_specs 15 Expected output: Quota should be updated Actual output: Invalid values_specs 15 Version: OpenStack version: Newton ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1645484 Title: Not able to update default quotas Status in neutron: New Bug description: Description: Trying to update/increase the default quota for number of security_groups that can be created. Pre-conditions: User- cloud admin Project- admin Step-by-step reproduction steps: neutron $AUTH quota-default-show +-+---+ | Field | Value | +-+---+ | floatingip | 50| | network | 10| | port| 50| | rbac_policy | 10| | router | 10| | security_group | 10| | security_group_rule | 100 | | subnet | 10| | subnetpool | -1| +-+---+ Try to update the default value for security_group as for project admin: openstack $AUTH project list +--+--+ | ID | Name | +--+--+ | 3f3dccb1ec12494ab9f7024e2ddd32de | admin +--+--+ neutron $AUTH quota-update --tenant_id 3f3dccb1ec12494ab9f7024e2ddd32de security_group 15 Invalid values_specs 15 Expected output: Quota should be updated Actual output: Invalid values_specs 15 Version: OpenStack version: Newton To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1645484/+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 1643964] Re: compressing static assets fails with xstatic-bootswatch 3.3.7.0
** Changed in: horizon (Ubuntu)
Status: New => Fix Released
--
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/1643964
Title:
compressing static assets fails with xstatic-bootswatch 3.3.7.0
Status in OpenStack Dashboard (Horizon):
Invalid
Status in XStatic-bootswatch:
Invalid
Status in horizon package in Ubuntu:
Fix Released
Bug description:
While packaging horizon for ocata milestone 1, we are hitting the
following error while compressing static assets:
CommandError: An error occurred during rendering
/usr/share/openstack-dashboard/openstack_dashboard/templates/horizon/_scripts.html:
'\"../bower_components/respond/dest/respond.min.js\"' isn't accessible via
COMPRESS_URL ('/horizon/static/') and can't be compressed
dpkg: error processing package openstack-dashboard (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of autopkgtest-satdep:
autopkgtest-satdep depends on openstack-dashboard (>= 0~); however:
Package openstack-dashboard is not configured yet.
dpkg: error processing package autopkgtest-satdep (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of
openstack-dashboard-ubuntu-theme:
openstack-dashboard-ubuntu-theme depends on openstack-dashboard (=
3:11.0.0~b1-0ubuntu1); however:
Package openstack-dashboard is not configured yet.
Paste of above error:
http://pastebin.ubuntu.com/23513344/
The 3.3.7.0 release of xstatic-bootswatch includes lines such as:
which corresponds to the file in the compression error.
Link to 3.3.7.0 commit of xstatic-bootswatch:
https://github.com/openstack/xstatic-bootswatch/commit/49c0d56698bc14ae5e5c18cc00c3f2e290d2e724
We currently have the following django and compressor versions in zesty:
python-django| 1.8.7-1ubuntu9| zesty| source, all
python-django-compressor | 2.0-3ubuntu1 | zesty| source, all
which are within the bounds of global-requirements and upper-constraints:
http://paste.ubuntu.com/23517114/
I also attempted using newer versions of django and compressor, with the same
results:
http://paste.ubuntu.com/23517443/
http://paste.ubuntu.com/23517845/
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1643964/+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 1645479] [NEW] ServerExternalEventsController doesn't properly pre-load migration_context
Public bug reported: This code is passing a string for expected_attrs when getting all instances: https://github.com/openstack/nova/blob/4e747092bcb015303efc2ab13da98ef5ce575ec8/nova/api/openstack/compute/server_external_events.py#L72 That's used to join the migration_context from the DB, but it's not doing that as expected_attr should be a list: https://github.com/openstack/nova/blob/4e747092bcb015303efc2ab13da98ef5ce575ec8/nova/objects/instance.py#L73 So we aren't getting the optimization in the API. That was added in https://review.openstack.org/#/c/371048/ which was also backported to stable/newton. ** Affects: nova Importance: Low Assignee: Matt Riedemann (mriedem) Status: Triaged ** Affects: nova/newton Importance: Undecided Status: New ** Tags: api ** Also affects: nova/newton Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1645479 Title: ServerExternalEventsController doesn't properly pre-load migration_context Status in OpenStack Compute (nova): Triaged Status in OpenStack Compute (nova) newton series: New Bug description: This code is passing a string for expected_attrs when getting all instances: https://github.com/openstack/nova/blob/4e747092bcb015303efc2ab13da98ef5ce575ec8/nova/api/openstack/compute/server_external_events.py#L72 That's used to join the migration_context from the DB, but it's not doing that as expected_attr should be a list: https://github.com/openstack/nova/blob/4e747092bcb015303efc2ab13da98ef5ce575ec8/nova/objects/instance.py#L73 So we aren't getting the optimization in the API. That was added in https://review.openstack.org/#/c/371048/ which was also backported to stable/newton. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1645479/+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 1645466] [NEW] ServiceStatusNotification is not in docs for existing versioned notifications
Public bug reported: http://docs.openstack.org/developer/nova/notifications.html#existing- versioned-notifications lists existing versioned notifications, but is missing ServiceStatusNotification which are defined here: https://github.com/openstack/nova/blob/22498982d167f0411170125406b4312aad663814/nova/notifications/objects/service.py And used here: https://github.com/openstack/nova/blob/22498982d167f0411170125406b4312aad663814/nova/objects/service.py#L319 ** Affects: nova Importance: Medium Status: Confirmed ** Tags: notifications -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1645466 Title: ServiceStatusNotification is not in docs for existing versioned notifications Status in OpenStack Compute (nova): Confirmed Bug description: http://docs.openstack.org/developer/nova/notifications.html#existing- versioned-notifications lists existing versioned notifications, but is missing ServiceStatusNotification which are defined here: https://github.com/openstack/nova/blob/22498982d167f0411170125406b4312aad663814/nova/notifications/objects/service.py And used here: https://github.com/openstack/nova/blob/22498982d167f0411170125406b4312aad663814/nova/objects/service.py#L319 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1645466/+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 1604397] Re: [SRU] python-swiftclient is missing in requirements.txt (for glare)
** Changed in: cloud-archive Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1604397 Title: [SRU] python-swiftclient is missing in requirements.txt (for glare) Status in Ubuntu Cloud Archive: Fix Committed Status in Ubuntu Cloud Archive newton series: Fix Committed Status in Glance: New Status in python-glance-store package in Ubuntu: Fix Released Status in python-glance-store source package in Yakkety: Fix Released Status in python-glance-store source package in Zesty: Fix Released Bug description: [Description] [Test Case] I'm using UCA glance packages (version "13.0.0~b1-0ubuntu1~cloud0"). And I've got this error: <30>Jul 18 16:03:45 node-2 glance-glare[17738]: ERROR: Store swift could not be configured correctly. Reason: Missing dependency python_swiftclient. Installing "python-swiftclient" fix the problem. In master (https://github.com/openstack/glance/blob/master/requirements.txt) package "python-swiftclient" is not included in requirements.txt. So UCA packages don't have proper dependencies. I think requirements.txt should be updated (add python-swiftclient there). This change should affect UCA packages. [Regression Potential] Minimal as this just adds a new dependency. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1604397/+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 1645464] [NEW] InstanceNotFound stacktrace in _process_instance_vif_deleted_event
Public bug reported: Seen in a CI run here: http://logs.openstack.org/16/393416/6/check/gate-tempest-dsvm-full- devstack-plugin-ceph-ubuntu- xenial/44f3329/logs/screen-n-cpu.txt.gz?level=TRACE#_2016-11-28_17_34_36_535 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server [req-8d784631-28c2-41b4-8175-7cfb59480838 nova service] Exception during message handling 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 155, in _process_incoming 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 225, in dispatch 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 195, in _do_dispatch 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/exception_wrapper.py", line 75, in wrapped 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server function_name, call_dict, binary) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server self.force_reraise() 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/exception_wrapper.py", line 66, in wrapped 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/compute/manager.py", line 6800, in external_instance_event 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server event.tag) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/compute/manager.py", line 6755, in _process_instance_vif_deleted_event 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server network_info = instance.info_cache.network_info 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 67, in getter 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server self.obj_load_attr(name) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/objects/instance.py", line 1063, in obj_load_attr 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server self._load_generic(attrname) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/objects/instance.py", line 819, in _load_generic 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server expected_attrs=[attrname]) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 177, in wrapper 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server args, kwargs) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/conductor/rpcapi.py", line 236, in object_class_action_versions 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server args=args, kwargs=kwargs) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/client.py", line 169, in call 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server retry=self.retry) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/transport.py", line 97, in _send 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server timeout=timeout, retry=retry) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 467, in send 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server retry=retry) 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 458, in _send 2016-11-28 17:34:36.535 2361 ERROR oslo_messaging.
[Yahoo-eng-team] [Bug 1644817] Re: No need to iterate the image list twice to get the final_images
Reviewed: https://review.openstack.org/402515 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=fca1dabf2611d461bbeed68777adb24c2fa3b59e Submitter: Jenkins Branch:master commit fca1dabf2611d461bbeed68777adb24c2fa3b59e Author: liaozd Date: Fri Nov 25 21:40:46 2016 +0800 implements: make twice list iterations into one Closes-Bug: 1644817 Change-Id: Ie97659230ad59f56a0285e7f693683bde32dca77 ** Changed in: horizon Status: In Progress => Fix Released -- 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/1644817 Title: No need to iterate the image list twice to get the final_images Status in OpenStack Dashboard (Horizon): Fix Released Bug description: The get_available_images() method in the openstack_dashboard.dashboards.project.images.utils, to get the final_images, it iterates twice. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1644817/+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 1644041] Re: heat_stack_owner users could see and delete other projects's heat stack
Just verified after add the following configuration in keystone.conf we
can solve this problem.
admin_project_domain_name = default
admin_project_name = admin
Thanks Rabi.
** Changed in: keystone
Status: New => Invalid
** Changed in: heat
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/1644041
Title:
heat_stack_owner users could see and delete other projects's heat
stack
Status in heat:
Invalid
Status in OpenStack Identity (keystone):
Invalid
Bug description:
In a newton deployment we found that a heat_stack_ower user can delete
a heat stack from other projects
For example, we have two domain domain1 and domain2. In domain1 we
have project: project_domain1 which has user:user1, in domain2 we have
a project:project_domain2 which has a user:user2.
domain1->project_domain1->user1
domain2->project_domain2->user2
create stack1 using user1:
{code}
boston-citron:/opt/openstack # unset ${!OS_*}
boston-citron:/opt/openstack # export OS_PROJECT_DOMAIN_NAME=domain1
boston-citron:/opt/openstack # export OS_USER_DOMAIN_NAME=domain1
boston-citron:/opt/openstack # export OS_PROJECT_NAME=project_domain1
boston-citron:/opt/openstack # export OS_USERNAME=user1
boston-citron:/opt/openstack # export OS_PASSWORD=123
boston-citron:/opt/openstack # export OS_AUTH_URL="$(python
-meci_python_libs.tools.get_keystone_private_endpoint_url)/v3"
boston-citron:/opt/openstack # export OS_IDENTITY_API_VERSION=3
boston-citron:/opt/openstack # openstack --insecure stack create stack1 -t
word.yaml
WARNING: openstackclient.common.utils is deprecated and will be removed after
Jun 2017. Please use osc_lib.utils
+-+--+
| Field | Value
|
+-+--+
| id | e4f909a9-6e87-450a-9bbd-d2a24409367b
|
| stack_name | stack1
|
| description | A simple Heat template that spins up a 3 Tier App
with 1 Web Server, 1 App Server, |
| | and 1 DB Server on private networks and attaches them
to security groups (HOT template in YAML). |
| |
|
| creation_time | 2016-11-22T22:27:49Z
|
| updated_time| None
|
| stack_status| CREATE_IN_PROGRESS
|
| stack_status_reason |
|
+-+--+
{code}
Then create stack2 using user2:
{code}
boston-citron:/opt/openstack # unset ${!OS_*}
boston-citron:/opt/openstack # export OS_PROJECT_DOMAIN_NAME=domain2
boston-citron:/opt/openstack # export OS_USER_DOMAIN_NAME=domain2
boston-citron:/opt/openstack # export OS_PROJECT_NAME=project_domain2
boston-citron:/opt/openstack # export OS_USERNAME=user2
boston-citron:/opt/openstack # export OS_PASSWORD=123
boston-citron:/opt/openstack # export OS_AUTH_URL="$(python
-meci_python_libs.tools.get_keystone_private_endpoint_url)/v3"
boston-citron:/opt/openstack # export OS_IDENTITY_API_VERSION=3
boston-citron:/opt/openstack #
boston-citron:/opt/openstack #
boston-citron:/opt/openstack # openstack --insecure stack create stack2 -t
word.yaml
WARNING: openstackclient.common.utils is deprecated and will be removed after
Jun 2017. Please use osc_lib.utils
+-+--+
| Field | Value
|
+-+--+
| id | b9476401-0da3-4c43-a0e4-3f8273a9e464
|
| stack_name | stack2
|
| descriptio
[Yahoo-eng-team] [Bug 1645359] Re: Vlan Aware VM - after setting trunk status to down, all traffic works
The documentation for vlan trunking is still in flight [1], but from there and the source documentation [2], you can see that the admin status is meant to blocking the management of the trunk (e.g. adding/removing subports) and it does not affect the data plane. [1] https://review.openstack.org/#/c/361776/ [2] https://github.com/openstack/neutron/blob/master/neutron/services/trunk/constants.py#L16 ** Tags added: trunk ** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1645359 Title: Vlan Aware VM - after setting trunk status to down, all traffic works Status in neutron: Invalid Bug description: Newton, openstack-neutron-ml2-9.1.0-6.el7ost.noarch openstack-neutron-bigswitch-agent-9.40.0-1.1.el7ost.noarch openstack-neutron-openvswitch-9.1.0-6.el7ost.noarch openstack-neutron-common-9.1.0-6.el7ost.noarch openstack-neutron-9.1.0-6.el7ost.noarch [stack@undercloud-0 ~]$ openstack network trunk set trunk1 --disable [stack@undercloud-0 ~]$ openstack network trunk list +--++--+-+ | ID | Name | Parent Port | Description | +--++--+-+ | 3b5c8493-7832-4501-a93f-65c5131512bb | trunk1 | 7d749eb0-633d-4114-b322-414d19f86046 | | +--++--+-+ [stack@undercloud-0 ~]$ openstack network trunk show trunk1 +-++ | Field | Value | +-++ | admin_state_up | DOWN | | created_at | 2016-11-28T11:45:54Z | | description | | | id | 3b5c8493-7832-4501-a93f-65c5131512bb | | name| trunk1 | | port_id | 7d749eb0-633d-4114-b322-414d19f86046 | | project_id | af788c6da1fb4388b09040aa99c997bc | | revision_number | 6 | | status | ACTIVE | | sub_ports | port_id='fdb9e48e-582f-43bd-b913-471711b3d2d2', segmentation_id='10', segmentation_type='vlan' | | | port_id='488e4933-9809-4041-84ed-9375bf64333b', segmentation_id='20', segmentation_type='vlan' | | tenant_id | af788c6da1fb4388b09040aa99c997bc | | updated_at | 2016-11-28T15:07:25Z | +-++ ping from all subinterfaces to qdhcps are successful [root@vm-1 ~]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1446 qdisc pfifo_fast state UP qlen 1000 link/ether fa:16:3e:62:e9:43 brd ff:ff:ff:ff:ff:ff inet 192.168.0.55/24 brd 192.168.0.255 scope global dynamic eth0 valid_lft 86013sec preferred_lft 86013sec inet6 fe80::f816:3eff:fe62:e943/64 scope link valid_lft forever preferred_lft forever 3: eth0.10@eth0: mtu 1446 qdisc noqueue state UP qlen 1000 link/ether fa:16:3e:ad:d5:39 brd ff:ff:ff:ff:ff:ff inet 192.168.10.55/24 brd 192.168.10.255 scope global dynamic eth0.10 valid_lft 86022sec preferred_lft 86022sec inet6 fe80::f816:3eff:fead:d539/64 scope link valid_lft forever preferred_lft forever 4: eth0.20@eth0: mtu 1446 qdisc noqueue state UP qlen 1000 link/ether fa:16:3e:5d:1e:73 brd ff:ff:ff:ff:ff:ff inet 192.168.20.3/24 br
[Yahoo-eng-team] [Bug 1645418] [NEW] Image Name does not show up when new instance are launched using horizon dashboard
Public bug reported: After creating a new instance from horizon dashboard with boot source as image, the image name does not show up in the table. Logs shows missing value for "image ref" attribute. NOTE: When the instance is launch using CLI the image name is there on horizon. ** Affects: horizon Importance: Undecided Status: New ** Tags: nova -- 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/1645418 Title: Image Name does not show up when new instance are launched using horizon dashboard Status in OpenStack Dashboard (Horizon): New Bug description: After creating a new instance from horizon dashboard with boot source as image, the image name does not show up in the table. Logs shows missing value for "image ref" attribute. NOTE: When the instance is launch using CLI the image name is there on horizon. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1645418/+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 1645404] [NEW] NoCloud module incompletely configures network interfaces which leads to wrong /etc/resolv.conf configuration in RH-based distros
Public bug reported: Hello all! NoCloud module doesn't put dns-nameservers and dns-search (and hwaddr as well) values to /etc/sysconfig/network-scripts/ifcfg-* files during configuration in Red Hat-based distos, putting it to /etc/resolv.conf instead. As a result having no DNS1, DNS2 and SEARCH defined in ifcfg-* files with PEERDNS=on (default value), /etc/resolv.conf settings get overwritten with settings obtained from DHCP server is there's one around even if BOOTPROTO=static is set. On the other hand, /etc/resolv.conf settings are ignored completely with PEERDNS=off and settings made by cloud-init remain untouched, the downside is that settings obtained over DHCP (if configured) are not written to /etc/resolv.conf as well disabling ability to perform DNS queries. It would be better if NoCloud would put dns-nameservers and dns-search values to DNS1, DNS2 and SEARCH parameters in ifcfg-* files when they are set. The only option so far is to hard code DNS1 and DNS2 settings in custom made cloud image. That will always set these nameservers to /etc/resolv.conf (until you edit them manually in ifcfg-* file) but that's a warranty that system will always be able to perform DNS queries. The problem takes place in CentOS 7 with cloud-init 7.5 installed. ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1645404 Title: NoCloud module incompletely configures network interfaces which leads to wrong /etc/resolv.conf configuration in RH-based distros Status in cloud-init: New Bug description: Hello all! NoCloud module doesn't put dns-nameservers and dns-search (and hwaddr as well) values to /etc/sysconfig/network-scripts/ifcfg-* files during configuration in Red Hat-based distos, putting it to /etc/resolv.conf instead. As a result having no DNS1, DNS2 and SEARCH defined in ifcfg-* files with PEERDNS=on (default value), /etc/resolv.conf settings get overwritten with settings obtained from DHCP server is there's one around even if BOOTPROTO=static is set. On the other hand, /etc/resolv.conf settings are ignored completely with PEERDNS=off and settings made by cloud-init remain untouched, the downside is that settings obtained over DHCP (if configured) are not written to /etc/resolv.conf as well disabling ability to perform DNS queries. It would be better if NoCloud would put dns-nameservers and dns-search values to DNS1, DNS2 and SEARCH parameters in ifcfg-* files when they are set. The only option so far is to hard code DNS1 and DNS2 settings in custom made cloud image. That will always set these nameservers to /etc/resolv.conf (until you edit them manually in ifcfg-* file) but that's a warranty that system will always be able to perform DNS queries. The problem takes place in CentOS 7 with cloud-init 7.5 installed. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1645404/+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 1642160] Re: horizon deployment failure with XStatic-roboto-fontface new release 0.5.0.0
Fixed in other patches. ** Changed in: horizon Status: New => Invalid -- 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/1642160 Title: horizon deployment failure with XStatic-roboto-fontface new release 0.5.0.0 Status in OpenStack Dashboard (Horizon): Invalid Bug description: XStatic-roboto-fontface to new release 0.5.0.0 from https://review.openstack.org/#/c/397303 causes this failure: 2016-11-15 22:53:20.486 | + lib/horizon:init_horizon:151 : django-admin compress --force 2016-11-15 22:53:21.792 | Found 'compress' tags in: 2016-11-15 22:53:21.792 | /opt/stack/new/horizon/openstack_dashboard/templates/horizon/_conf.html 2016-11-15 22:53:21.792 | /opt/stack/new/horizon/openstack_dashboard/templates/horizon/_scripts.html 2016-11-15 22:53:21.792 | /opt/stack/new/horizon/openstack_dashboard/templates/_stylesheets.html 2016-11-15 22:53:34.072 | Compressing... CommandError: An error occurred during rendering /opt/stack/new/horizon/openstack_dashboard/templates/_stylesheets.html: Couldn't find anything to import: /horizon/lib/roboto_fontface/css/roboto-fontface.scss this is under /usr/local/lib/python2.7/dist- packages/xstatic/pkg/roboto_fontface/data/css/roboto/roboto- fontface.css see full log: http://logs.openstack.org/03/397303/2/check/gate-tempest-dsvm-neutron- full-ubuntu- xenial/cc300af/logs/devstacklog.txt.gz#_2016-11-15_22_53_34_072 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1642160/+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 1641013] Re: meter list in resource usage
Ceilometer dashboard has been removed from horizon. ** Changed in: horizon Status: Confirmed => Won't Fix -- 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/1641013 Title: meter list in resource usage Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: Resource usage in Openstack dashboard shows only few specific meters. These meters change from one vm to another whereas in CLI, meter-list displays the full list of meters. Using openstack mitaka on ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1641013/+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 1643689] Re: Error running manage.py compress after https://review.openstack.org/#/c/399771/
This doesn't appear with the constrained version of our requirements, so marking Wont Fix. ** Changed in: horizon Status: Confirmed => Won't Fix -- 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/1643689 Title: Error running manage.py compress after https://review.openstack.org/#/c/399771/ Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: After https://review.openstack.org/#/c/399771/, we are getting following error when running "python manage.py compress": CommandError: An error occurred during rendering /tmp/horizon/openstack_dashboard/templates/_stylesheets.html: Couldn't find anything to import: ../../mixins Extensions: , , Search path: on line 21 of horizon/lib/roboto_fontface/css/roboto/sass/roboto-fontface-regular.scss imported from line 21 of horizon/lib/roboto_fontface/css/roboto/sass/roboto-fontface.scss imported from line 16 of themes/material/bootstrap/_styles.scss imported from line 16 of themes/material/_styles.scss imported from line 1 of u'string:c61b5d22d54bf56c:\n// My Themes\n@import "/themes/material/variables";\n\n// Horizon\n@import "/dashboard/scss/horizon' and exits. Note that this issue is making horizon packaging to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1643689/+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 1645391] [NEW] mapped auth method not included by default
Public bug reported: The mapped auth method is not listed by default in keystone.conf [1]. It should be there since it is required for proper federated authentication. [1] https://github.com/openstack/keystone/blob/master/keystone/conf/constants.py#L20 ** Affects: keystone Importance: Undecided Assignee: Rodrigo Duarte (rodrigodsousa) Status: In Progress -- 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/1645391 Title: mapped auth method not included by default Status in OpenStack Identity (keystone): In Progress Bug description: The mapped auth method is not listed by default in keystone.conf [1]. It should be there since it is required for proper federated authentication. [1] https://github.com/openstack/keystone/blob/master/keystone/conf/constants.py#L20 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1645391/+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 1645392] [NEW] refactor functional tests for IPv6
Public bug reported: A recent change to correct an IPv6 problem [0] monkeypatches FunctionalTest. An alternative would be to do what Stuart suggested on that patch [1], namely: If we wanted to get fancy/avoid this monkey patching, we could potentially define an IPV6FunctionalTest which would be a subclass of FunctionalTest. We could define a get_unused_port method which could be ipv6 in the case of IPV6FunctionalTest and ipv4 in the regular FunctionalTest. Another alternative was suggested by Tomislav on that same patch: It also crossed my mind that I can introduce a new optional parameter in functions get_unused_port and get_unused_port_and_socket in glance/tests/utils.py, e.g. ip_version which would default to 4. And in addition, FunctionalTest class could have additional member (variable) of similar name meaning which would have to be set properly (overridden) before calling setUp. This would definitely improve chances to switch from IPv4 to IPv6 for the whole testing suite with simple change of default value once IPv6 becomes used more often. (Tomislav was worried that creating a subclass would involve duplicating some methods, which would mean more code to maintain.) It would be good to look into this and decide which way of refactoring is best, and put it on the agenda for the glance weekly meeting to get some feedback before/during coding. [0] https://review.openstack.org/394946 [1] https://review.openstack.org/#/c/394946/4/glance/tests/functional/v2/test_images.py@2921 ** Affects: glance Importance: Low Status: Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1645392 Title: refactor functional tests for IPv6 Status in Glance: Triaged Bug description: A recent change to correct an IPv6 problem [0] monkeypatches FunctionalTest. An alternative would be to do what Stuart suggested on that patch [1], namely: If we wanted to get fancy/avoid this monkey patching, we could potentially define an IPV6FunctionalTest which would be a subclass of FunctionalTest. We could define a get_unused_port method which could be ipv6 in the case of IPV6FunctionalTest and ipv4 in the regular FunctionalTest. Another alternative was suggested by Tomislav on that same patch: It also crossed my mind that I can introduce a new optional parameter in functions get_unused_port and get_unused_port_and_socket in glance/tests/utils.py, e.g. ip_version which would default to 4. And in addition, FunctionalTest class could have additional member (variable) of similar name meaning which would have to be set properly (overridden) before calling setUp. This would definitely improve chances to switch from IPv4 to IPv6 for the whole testing suite with simple change of default value once IPv6 becomes used more often. (Tomislav was worried that creating a subclass would involve duplicating some methods, which would mean more code to maintain.) It would be good to look into this and decide which way of refactoring is best, and put it on the agenda for the glance weekly meeting to get some feedback before/during coding. [0] https://review.openstack.org/394946 [1] https://review.openstack.org/#/c/394946/4/glance/tests/functional/v2/test_images.py@2921 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1645392/+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 1628274] Re: No vertical scroll bar when panel list extends past window bottom
Fixed here: https://review.openstack.org/#/c/297733/ ** Changed in: horizon Status: Confirmed => Fix Released -- 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/1628274 Title: No vertical scroll bar when panel list extends past window bottom Status in OpenStack Dashboard (Horizon): Fix Released Bug description: No vertical scroll bars are enabled when the dashboard list on the left extends past the bottom of the window. There is no way to access the hidden list items without re-sizing the window, or lowering the zoom level of the browser window. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1628274/+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 1623483] Re: In placement api links in resource provider representation links to aggregates but we never merged aggregates support
Since aggregates have now merged the behavior is not a big problem.
It could be argued that the pre-1.1 microversion representation of a
resource provider should be changed not to show aggregates, but if
that's the case we should make a specific bug for that. The
representation on 1.1 and beyond is now correct with regard to these
links.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1623483
Title:
In placement api links in resource provider representation links to
aggregates but we never merged aggregates support
Status in OpenStack Compute (nova):
Invalid
Bug description:
The placement api returns a set of links for a resource provider when
GETting a list or a single. These links include a link to
/resource_providers/{uuid}/aggregates but that code was not merged for
newton, so it results in a 404. This is probably no big deal, but I
thought I better mention it.
The code for aggregates is done:
https://review.openstack.org/#/c/362766/
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1623483/+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 1630161] Re: nova image-list is deprecated, but it should work even now
I think this is actually a valid bug in openstackclient. Specifically, the following use case *should* work: $ export OS_COMPUTE_API_VERSION=2.latest $ openstack server create --flavor m1.tiny --image cirros-0.3.4-x86_64 --key-name stack --security-group default --nic net- id=059a48f5-fc8e-4721-b694-f2441cf5226f,tag=bla test2 API version 'API Version Major: 2, Minor: 37' is not supported on 'list' method. It's expected that setting OS_COMPUTE_API_VERSION to latest allows you to boot a server. However, it looks like if the latest on the server side is 2.37 (or later?) booting a VM doesn't work. ** Also affects: python-openstackclient Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1630161 Title: nova image-list is deprecated, but it should work even now Status in OpenStack Compute (nova): Invalid Status in python-novaclient: Invalid Status in python-openstackclient: New Bug description: On newton it looks like: $ nova image-list WARNING: Command image-list is deprecated and will be removed after Nova 15.0.0 is released. Use python-glanceclient or openstackclient instead. ERROR (VersionNotFoundForAPIMethod): API version 'API Version Major: 2, Minor: 37' is not supported on 'list' method. It is supposed to be still supported, since newton is just 14. nova (14.0.0.0rc2.dev21) python-novaclient (6.0.0) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1630161/+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 1642428] Re: Add sha384 and sha512 auth algorithms for vendor drivers
Reviewed: https://review.openstack.org/400827 Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=ef5be1fd1abe2d40638df8e4070674d4ec591385 Submitter: Jenkins Branch:master commit ef5be1fd1abe2d40638df8e4070674d4ec591385 Author: Darla Ahlert Date: Tue Nov 22 09:32:52 2016 -0600 [doc]Add sha256, sha384 and sha512 auth algorithms https://review.openstack.org/#/c/393702/ adds sha284 and sha512 auth algorithms for vendor drivers. This commit adds these auth algorithms as options in the API documentation. Change-Id: I19182dbe82b89c4fa83cb93864daf47210d6c85b Closes-bug: 1642428 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1642428 Title: Add sha384 and sha512 auth algorithms for vendor drivers Status in neutron: Fix Released Bug description: https://review.openstack.org/393702 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit b1530c73da9b8c689c61b3fc726a1ba6e5038ec3 Author: Dongcan Ye Date: Fri Nov 4 18:43:32 2016 +0800 Add sha384 and sha512 auth algorithms for vendor drivers Currently, VPNaaS limits the IPSec and IKE auth algorithm to "sha1" and "sha256". If user add a new driver(eg, Hardware VPN Gateway), and the new driver supports more auth algorithms, such as "sha2-384", "sha2-512", it can not integrated with current VPNaaS plugin. This patch add "sha384" and "sha512" auth algorithms in API and DB side, Because of Openswan, Strongswan, Libreswan and Cisco CSR driver doesn't support these, so we add a validator in ipsec and Cisco CSR service driver, that will raise an exception when creating or updating the IPSec/IKE Policy auth algorithm with "sha384" and "sha512". Other vendors can bypass validate ike_policy and ipsec_policy when creating and updating auth_algorithm, or implement specific logic for themselves. DocImpact APIImpact NOTE: CLI support also needs change. Closes-Bug: #1638152 Change-Id: I87b257ee6500c424fc273955a6d89d972a2823e9 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1642428/+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 1644711] Re: memory leak in glance api when a big image ~300GB is downloaded via glanceclient in kilo
So I'm marking this as won't fix. The S3 driver was removed in Mitaka. Liberty is EOL. Kilo has been EOL for quite a while. Since there's no driver in master to fix this for, it seems as though it's not worth fixing. If you can, however, provide a different configuration that replicates this behaviour, we can reopen this and consider targeting it to the appropriate series. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1644711 Title: memory leak in glance api when a big image ~300GB is downloaded via glanceclient in kilo Status in Glance: Won't Fix Bug description: memory leak in glance api when a big image ~300GB is downloaded via glanceclient in kilo. the backend store is S3. when the glanceclient starts downloading the image, the glanceclient is stopped. After stopping the glanceclient process the memory consumed by associated glance-api starts increasing every second till it consumes 70-80% memory (seen via top) and finally becoming unresponsive. Upon restarting the glance-api service the memory consumed is released. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1644711/+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 1643767] Re: horizon jenkins failed：tempest_horizon.tests.scenario.test_dashboard_basic_ops.TestDashboardBasicOps.test_basic_scenario
This bug was mistakenly assigned to the Blazar project. ** Project changed: blazar => horizon -- 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/1643767 Title: horizon jenkins failed：tempest_horizon.tests.scenario.test_dashboard_basic_ops.TestDashboardBasicOps.test_basic_scenario Status in OpenStack Dashboard (Horizon): New Bug description: You can see the full failure at http://logs.openstack.org/12/399812/4/check/gate-horizon-dsvm-tempest- plugin-ubuntu-xenial/e827ee0/console.html Captured traceback: 2016-11-22 03:49:21.316333 | ~~~ 2016-11-22 03:49:21.316348 | Traceback (most recent call last): 2016-11-22 03:49:21.316392 | File "/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/tempest_horizon/tests/scenario/test_dashboard_basic_ops.py", line 139, in test_basic_scenario 2016-11-22 03:49:21.316405 | self.check_login_page() 2016-11-22 03:49:21.316447 | File "/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/tempest_horizon/tests/scenario/test_dashboard_basic_ops.py", line 85, in check_login_page 2016-11-22 03:49:21.316470 | response = self._get_opener().open(CONF.dashboard.dashboard_url).read() 2016-11-22 03:49:21.316490 | File "/usr/lib/python2.7/urllib2.py", line 435, in open 2016-11-22 03:49:21.316504 | response = meth(req, response) 2016-11-22 03:49:21.316524 | File "/usr/lib/python2.7/urllib2.py", line 548, in http_response 2016-11-22 03:49:21.316541 | 'http', request, response, code, msg, hdrs) 2016-11-22 03:49:21.316572 | File "/usr/lib/python2.7/urllib2.py", line 467, in error 2016-11-22 03:49:21.316586 | result = self._call_chain(*args) 2016-11-22 03:49:21.316607 | File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain 2016-11-22 03:49:21.316619 | result = func(*args) 2016-11-22 03:49:21.316640 | File "/usr/lib/python2.7/urllib2.py", line 654, in http_error_302 2016-11-22 03:49:21.316658 | return self.parent.open(new, timeout=req.timeout) 2016-11-22 03:49:21.316676 | File "/usr/lib/python2.7/urllib2.py", line 435, in open 2016-11-22 03:49:21.316690 | response = meth(req, response) 2016-11-22 03:49:21.316711 | File "/usr/lib/python2.7/urllib2.py", line 548, in http_response 2016-11-22 03:49:21.316728 | 'http', request, response, code, msg, hdrs) 2016-11-22 03:49:21.316747 | File "/usr/lib/python2.7/urllib2.py", line 473, in error 2016-11-22 03:49:21.316761 | return self._call_chain(*args) 2016-11-22 03:49:21.316781 | File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain 2016-11-22 03:49:21.316793 | result = func(*args) 2016-11-22 03:49:21.316815 | File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default 2016-11-22 03:49:21.316835 | raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) 2016-11-22 03:49:21.316853 | urllib2.HTTPError: HTTP Error 500: Internal Server Error 2016-11-22 03:49:21.316860 | --- Below is horizon_error.log, 2016-11-22 03:49:20.957173 Invalid HTTP_HOST header: '127.0.0.1'. You may need to add u'127.0.0.1' to ALLOWED_HOSTS. 2016-11-22 03:49:20.973949 mod_wsgi (pid=719): Exception occurred processing WSGI script '/opt/stack/new/horizon/openstack_dashboard/wsgi/django.wsgi'. 2016-11-22 03:49:20.973969 Traceback (most recent call last): 2016-11-22 03:49:20.973979 File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/wsgi.py", line 189, in __call__ 2016-11-22 03:49:20.974013 response = self.get_response(request) 2016-11-22 03:49:20.974018 File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 207, in get_response 2016-11-22 03:49:20.974027 return debug.technical_500_response(request, *sys.exc_info(), status_code=400) 2016-11-22 03:49:20.974032 File "/usr/local/lib/python2.7/dist-packages/django/views/debug.py", line 97, in technical_500_response 2016-11-22 03:49:20.974245 html = reporter.get_traceback_html() 2016-11-22 03:49:20.974253 File "/usr/local/lib/python2.7/dist-packages/django/views/debug.py", line 384, in get_traceback_html 2016-11-22 03:49:20.974262 return t.render(c) 2016-11-22 03:49:20.974267 File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 210, in render 2016-11-22 03:49:20.974505 return self._render(context) 2016-11-22 03:49:20.974512 File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 202, in _render 2016-11-22 03:49:20.974520 return self.nodelist.render(context) 2016-11-22 03:49:20.974524 File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", l
[Yahoo-eng-team] [Bug 1645359] [NEW] Vlan Aware VM - after setting trunk status to down, all traffic works
Public bug reported: Newton, openstack-neutron-ml2-9.1.0-6.el7ost.noarch openstack-neutron-bigswitch-agent-9.40.0-1.1.el7ost.noarch openstack-neutron-openvswitch-9.1.0-6.el7ost.noarch openstack-neutron-common-9.1.0-6.el7ost.noarch openstack-neutron-9.1.0-6.el7ost.noarch [stack@undercloud-0 ~]$ openstack network trunk set trunk1 --disable [stack@undercloud-0 ~]$ openstack network trunk list +--++--+-+ | ID | Name | Parent Port | Description | +--++--+-+ | 3b5c8493-7832-4501-a93f-65c5131512bb | trunk1 | 7d749eb0-633d-4114-b322-414d19f86046 | | +--++--+-+ [stack@undercloud-0 ~]$ openstack network trunk show trunk1 +-++ | Field | Value | +-++ | admin_state_up | DOWN | | created_at | 2016-11-28T11:45:54Z | | description | | | id | 3b5c8493-7832-4501-a93f-65c5131512bb | | name| trunk1 | | port_id | 7d749eb0-633d-4114-b322-414d19f86046 | | project_id | af788c6da1fb4388b09040aa99c997bc | | revision_number | 6 | | status | ACTIVE | | sub_ports | port_id='fdb9e48e-582f-43bd-b913-471711b3d2d2', segmentation_id='10', segmentation_type='vlan' | | | port_id='488e4933-9809-4041-84ed-9375bf64333b', segmentation_id='20', segmentation_type='vlan' | | tenant_id | af788c6da1fb4388b09040aa99c997bc | | updated_at | 2016-11-28T15:07:25Z | +-++ ping from all subinterfaces to qdhcps are successful [root@vm-1 ~]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1446 qdisc pfifo_fast state UP qlen 1000 link/ether fa:16:3e:62:e9:43 brd ff:ff:ff:ff:ff:ff inet 192.168.0.55/24 brd 192.168.0.255 scope global dynamic eth0 valid_lft 86013sec preferred_lft 86013sec inet6 fe80::f816:3eff:fe62:e943/64 scope link valid_lft forever preferred_lft forever 3: eth0.10@eth0: mtu 1446 qdisc noqueue state UP qlen 1000 link/ether fa:16:3e:ad:d5:39 brd ff:ff:ff:ff:ff:ff inet 192.168.10.55/24 brd 192.168.10.255 scope global dynamic eth0.10 valid_lft 86022sec preferred_lft 86022sec inet6 fe80::f816:3eff:fead:d539/64 scope link valid_lft forever preferred_lft forever 4: eth0.20@eth0: mtu 1446 qdisc noqueue state UP qlen 1000 link/ether fa:16:3e:5d:1e:73 brd ff:ff:ff:ff:ff:ff inet 192.168.20.3/24 brd 192.168.20.255 scope global dynamic eth0.20 valid_lft 86011sec preferred_lft 86011sec inet6 fe80::f816:3eff:fe5d:1e73/64 scope link valid_lft forever preferred_lft forever [root@vm-1 ~]# ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.594 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1.02 ms ^C --- 192.168.0.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 0.594/0.807/1.020/0.213 ms [root@vm-1 ~]# ping 192.168.10.1 PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data. 64 bytes from 192.168.10.1: icmp_seq=1 ttl=64 time=2.18 ms ^C --- 192.168.10.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 2.186/2.186/2.186/0.000 ms [root@vm-1 ~]# ping 192.
[Yahoo-eng-team] [Bug 1643767] [NEW] horizon jenkins failed：tempest_horizon.tests.scenario.test_dashboard_basic_ops.TestDashboardBasicOps.test_basic_scenario
You have been subscribed to a public bug: You can see the full failure at http://logs.openstack.org/12/399812/4/check/gate-horizon-dsvm-tempest- plugin-ubuntu-xenial/e827ee0/console.html Captured traceback: 2016-11-22 03:49:21.316333 | ~~~ 2016-11-22 03:49:21.316348 | Traceback (most recent call last): 2016-11-22 03:49:21.316392 | File "/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/tempest_horizon/tests/scenario/test_dashboard_basic_ops.py", line 139, in test_basic_scenario 2016-11-22 03:49:21.316405 | self.check_login_page() 2016-11-22 03:49:21.316447 | File "/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/tempest_horizon/tests/scenario/test_dashboard_basic_ops.py", line 85, in check_login_page 2016-11-22 03:49:21.316470 | response = self._get_opener().open(CONF.dashboard.dashboard_url).read() 2016-11-22 03:49:21.316490 | File "/usr/lib/python2.7/urllib2.py", line 435, in open 2016-11-22 03:49:21.316504 | response = meth(req, response) 2016-11-22 03:49:21.316524 | File "/usr/lib/python2.7/urllib2.py", line 548, in http_response 2016-11-22 03:49:21.316541 | 'http', request, response, code, msg, hdrs) 2016-11-22 03:49:21.316572 | File "/usr/lib/python2.7/urllib2.py", line 467, in error 2016-11-22 03:49:21.316586 | result = self._call_chain(*args) 2016-11-22 03:49:21.316607 | File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain 2016-11-22 03:49:21.316619 | result = func(*args) 2016-11-22 03:49:21.316640 | File "/usr/lib/python2.7/urllib2.py", line 654, in http_error_302 2016-11-22 03:49:21.316658 | return self.parent.open(new, timeout=req.timeout) 2016-11-22 03:49:21.316676 | File "/usr/lib/python2.7/urllib2.py", line 435, in open 2016-11-22 03:49:21.316690 | response = meth(req, response) 2016-11-22 03:49:21.316711 | File "/usr/lib/python2.7/urllib2.py", line 548, in http_response 2016-11-22 03:49:21.316728 | 'http', request, response, code, msg, hdrs) 2016-11-22 03:49:21.316747 | File "/usr/lib/python2.7/urllib2.py", line 473, in error 2016-11-22 03:49:21.316761 | return self._call_chain(*args) 2016-11-22 03:49:21.316781 | File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain 2016-11-22 03:49:21.316793 | result = func(*args) 2016-11-22 03:49:21.316815 | File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default 2016-11-22 03:49:21.316835 | raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) 2016-11-22 03:49:21.316853 | urllib2.HTTPError: HTTP Error 500: Internal Server Error 2016-11-22 03:49:21.316860 | --- Below is horizon_error.log, 2016-11-22 03:49:20.957173 Invalid HTTP_HOST header: '127.0.0.1'. You may need to add u'127.0.0.1' to ALLOWED_HOSTS. 2016-11-22 03:49:20.973949 mod_wsgi (pid=719): Exception occurred processing WSGI script '/opt/stack/new/horizon/openstack_dashboard/wsgi/django.wsgi'. 2016-11-22 03:49:20.973969 Traceback (most recent call last): 2016-11-22 03:49:20.973979 File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/wsgi.py", line 189, in __call__ 2016-11-22 03:49:20.974013 response = self.get_response(request) 2016-11-22 03:49:20.974018 File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 207, in get_response 2016-11-22 03:49:20.974027 return debug.technical_500_response(request, *sys.exc_info(), status_code=400) 2016-11-22 03:49:20.974032 File "/usr/local/lib/python2.7/dist-packages/django/views/debug.py", line 97, in technical_500_response 2016-11-22 03:49:20.974245 html = reporter.get_traceback_html() 2016-11-22 03:49:20.974253 File "/usr/local/lib/python2.7/dist-packages/django/views/debug.py", line 384, in get_traceback_html 2016-11-22 03:49:20.974262 return t.render(c) 2016-11-22 03:49:20.974267 File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 210, in render 2016-11-22 03:49:20.974505 return self._render(context) 2016-11-22 03:49:20.974512 File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 202, in _render 2016-11-22 03:49:20.974520 return self.nodelist.render(context) 2016-11-22 03:49:20.974524 File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 905, in render 2016-11-22 03:49:20.974529 bit = self.render_node(node, context) 2016-11-22 03:49:20.974533 File "/usr/local/lib/python2.7/dist-packages/django/template/debug.py", line 79, in render_node 2016-11-22 03:49:20.974570 return node.render(context) 2016-11-22 03:49:20.974577 File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 329, in render 2016-11-22 03:49:20.974783 return nodelist.render(context) 2016-11-22 03:49:20.974789 File "/usr/local/lib/python2.7/dist-packages/d
[Yahoo-eng-team] [Bug 1645326] [NEW] The server snapshot metadata information is lost
Public bug reported: Firt,create a server from volume,the server has metadata info. Then,make a snapshot for the server. Next,view the snapshot details,you can see the metadata is empty. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1645326 Title: The server snapshot metadata information is lost Status in OpenStack Compute (nova): New Bug description: Firt,create a server from volume,the server has metadata info. Then,make a snapshot for the server. Next,view the snapshot details,you can see the metadata is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1645326/+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 1645317] [NEW] FIP and router iptables are not apdated when associated port ip address is changed
Public bug reported: Newton, [root@controller-0 ~]# rpm -qa | grep neutron python-neutron-lib-0.4.0-1.el7ost.noarch puppet-neutron-9.4.2-1.el7ost.noarch python-neutron-9.1.0-6.el7ost.noarch openstack-neutron-ml2-9.1.0-6.el7ost.noarch openstack-neutron-bigswitch-agent-9.40.0-1.1.el7ost.noarch openstack-neutron-openvswitch-9.1.0-6.el7ost.noarch openstack-neutron-common-9.1.0-6.el7ost.noarch openstack-neutron-9.1.0-6.el7ost.noarch We have a VM with FIP associated to it. [stack@undercloud-0 ~]$ nova list +--+--+++-+-+ | ID | Name | Status | Task State | Power State | Networks| +--+--+++-+-+ | 1fe84939-5739-4723-8466-5b0e20e29650 | VM-1 | ACTIVE | - | Running | int_net=192.168.0.7, 10.0.0.211 | +--+--+++-+-+ [stack@undercloud-0 ~]$ neutron floatingip-show a009ff12-279e-4be3-bb40-0a1cf8b6c2ea +-+--+ | Field | Value| +-+--+ | created_at | 2016-11-28T12:02:27Z | | description | | | fixed_ip_address| 192.168.0.7 | <<< | floating_ip_address | 10.0.0.211 | | floating_network_id | 7e09c182-b829-4174-ba0b-5e90efc20f54 | | id | a009ff12-279e-4be3-bb40-0a1cf8b6c2ea | | port_id | 7d749eb0-633d-4114-b322-414d19f86046 | | project_id | af788c6da1fb4388b09040aa99c997bc | | revision_number | 4| | router_id | 9696bdb2-a5bd-4f92-a112-3f1f171e823c | | status | ACTIVE | | tenant_id | af788c6da1fb4388b09040aa99c997bc | | updated_at | 2016-11-28T12:22:45Z | +-+--+ After updating the VMport: openstack port set parent_port --fixed-ip subnet=0a0f0ac2-2bc6-423c-9197-7c3313438c2d,ip-address=192.168.0.55 openstack port unset parent_port --fixed-ip subnet=0a0f0ac2-2bc6-423c-9197-7c3313438c2d,ip-address=192.168.0.7 The FIP remained the same and the IP was not changed from 192.168.0.7 to 192.168.0.55. The connectivity to the VM was lost due to unchanged iptable rules on the router [root@controller-0 ~]# ip net e qrouter-9696bdb2-a5bd-4f92-a112-3f1f171e823c iptables -t nat -L | grep 211 SNAT all -- 192.168.0.7 anywhere to:10.0.0.211 <<<- We should have the iptables rule and FIP updated automatically. Connectivity should not be lost. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1645317 Title: FIP and router iptables are not apdated when associated port ip address is changed Status in neutron: New Bug description: Newton, [root@controller-0 ~]# rpm -qa | grep neutron python-neutron-lib-0.4.0-1.el7ost.noarch puppet-neutron-9.4.2-1.el7ost.noarch python-neutron-9.1.0-6.el7ost.noarch openstack-neutron-ml2-9.1.0-6.el7ost.noarch openstack-neutron-bigswitch-agent-9.40.0-1.1.el7ost.noarch openstack-neutron-openvswitch-9.1.0-6.el7ost.noarch openstack-neutron-common-9.1.0-6.el7ost.noarch openstack-neutron-9.1.0-6.el7ost.noarch We have a VM with FIP associated to it. [stack@undercloud-0 ~]$ nova list +--+--+++-+-+ | ID | Name | Status | Task State | Power State | Networks| +--+--+++-+-+ | 1fe84939-5739-4723-8466-5b0e20e29650 | VM-1 | ACTIVE | - | Running | int_net=192.168.0.7, 10.0.0.211 | +--+--+++-+-+ [stack@undercloud-0 ~]$ neutron floatingip-show a009ff12-279e-4be3-bb40-0a1cf8b6c2ea +-+--+ | Field | Value| +-+--+ | created_at | 2016-11-28T12:02:27Z | | description | | | fixed_ip_address| 192.168.0.7
[Yahoo-eng-team] [Bug 1645213] Re: Error API call in Create user operation
This was a choice performed by the CLI, they are choosing to call those API in that order. ** Also affects: python-openstackclient Importance: Undecided Status: New ** Changed in: keystone Status: Confirmed => Invalid ** Changed in: keystone Assignee: Kalaswan Datta (kalaswan-datta) => (unassigned) -- 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/1645213 Title: Error API call in Create user operation Status in OpenStack Identity (keystone): Invalid Status in python-openstackclient: New Bug description: Problem: While create user operation is performed, unnecessary API calls are executed. Details: When User is created through CLI command, the unnecessary API calls are observed. we can see in the logs of Keystone access logs. /var/log/httpd/keystone_wsgi_admin_access.log: -- 1. [22/Nov/2016:13:55:53 +0530] "GET /v3 HTTP/1.1" 200 194 "-" "osc-lib keystoneauth1/2.12.1 python-requests/2.10.0 CPython/2.7.5" 2. [22/Nov/2016:13:55:53 +0530] "POST /v3/auth/tokens HTTP/1.1" 201 5422 "-" "osc-lib keystoneauth1/2.12.1 python-requests/2.10.0 CPython/2.7.5" 3. [22/Nov/2016:13:55:53 +0530] "POST /v3/auth/tokens HTTP/1.1" 201 5422 "-" "osc-lib keystoneauth1/2.12.1 python-requests/2.10.0 CPython/2.7.5" 4. [22/Nov/2016:13:55:53 +0530] "GET / HTTP/1.1" 300 593 "-" "osc-lib keystoneauth1/2.12.1 python-requests/2.10.0 CPython/2.7.5" 5. [22/Nov/2016:13:55:53 +0530] "GET /v3/projects/admin HTTP/1.1" 404 90 "-" "python-keystoneclient" 6. [22/Nov/2016:13:55:53 +0530] "GET /v3/projects/admin HTTP/1.1" 404 90 "-" "python-keystoneclient" 7. [22/Nov/2016:13:55:53 +0530] "GET /v3/projects?name=admin HTTP/1.1" 200 226 "-" "python-keystoneclient" 8. [22/Nov/2016:13:55:53 +0530] "POST /v3/users HTTP/1.1" 201 282 "-" "python-keystoneclient" In the above mentioned logs, Line number #5 and #6 is returning 404 code for GET request to /v3/projects/admin. These two GET request is an overhead. The project information is achieved in line #7 with another GET request. These two API request should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1645213/+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 1645215] Re: Error API call in Delete user operation
This was a choice performed by the CLI, they are choosing to call those API in that order. ** Also affects: python-openstackclient Importance: Undecided Status: New ** Changed in: keystone Status: Confirmed => Invalid ** Changed in: keystone Assignee: Kalaswan Datta (kalaswan-datta) => (unassigned) -- 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/1645215 Title: Error API call in Delete user operation Status in OpenStack Identity (keystone): Invalid Status in python-openstackclient: New Bug description: Problem: While Delete user operation is performed, unnecessary API calls are executed. Details: When User is Deleted through CLI command, the unnecessary API calls are observed. we can see in the logs of Keystone access logs. /var/log/httpd/keystone_wsgi_admin_access.log: -- 1. [22/Nov/2016:13:57:59 +0530] "GET /v3 HTTP/1.1" 200 194 "-" "osc-lib keystoneauth1/2.12.1 python-requests/2.10.0 CPython/2.7.5" 2. [22/Nov/2016:13:57:59 +0530] "POST /v3/auth/tokens HTTP/1.1" 201 5422 "-" "osc-lib keystoneauth1/2.12.1 python-requests/2.10.0 CPython/2.7.5" 3. [22/Nov/2016:13:57:59 +0530] "POST /v3/auth/tokens HTTP/1.1" 201 5422 "-" "osc-lib keystoneauth1/2.12.1 python-requests/2.10.0 CPython/2.7.5" 4. [22/Nov/2016:13:57:59 +0530] "GET / HTTP/1.1" 300 593 "-" "osc-lib keystoneauth1/2.12.1 python-requests/2.10.0 CPython/2.7.5" 5. [22/Nov/2016:13:57:59 +0530] "GET /v3/users/abc HTTP/1.1" 404 85 "-" "python-keystoneclient" 6. [22/Nov/2016:13:57:59 +0530] "GET /v3/users/abc HTTP/1.1" 404 85 "-" "python-keystoneclient" 7. [22/Nov/2016:13:57:59 +0530] "GET /v3/users?name=abc HTTP/1.1" 200 236 "-" "python-keystoneclient" 8. [22/Nov/2016:13:57:59 +0530] "DELETE /v3/users/6ad2a4fc7d19440d9141853d264df5be HTTP/1.1" 204 - "-" "python-keystoneclient" In the above mentioned logs, Line number #5 and #6 is returning 404 code for GET request to /v3/users/abc which is about to create. These two GET request is an overhead. The user information is achieved in line #7 with another GET request. These two API request should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1645215/+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 1614766] Re: ovsdb managers shouldn't be erased/overwritten
Reviewed: https://review.openstack.org/357528 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7d42176853c80545df46c3fa593d7816f12e57cf Submitter: Jenkins Branch:master commit 7d42176853c80545df46c3fa593d7816f12e57cf Author: Isaku Yamahata Date: Thu Aug 18 15:32:12 2016 -0700 ovsdb: don't erase existing ovsdb managers The current existing agent erases already set ovsdb managers entries. In some use cases, cloud admin sets ovsdb managers. eg, for SDN controllers or monitoring purpose. Neutron agent shouldn't unconditionally erase the existing ovsdb managers. This patch implements a new api add_manager (along with get_manager and remove_manager) to the ovsdb api which will allow us to configure a manager on a switch without overriding the existing managers. Closes-Bug: #1614766 Change-Id: Ibf9bd02fac3070d166546cac478ef984e4e43f28 Co-Authored-By: sridhargaddam Co-Authored-By: Terry Wilson ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1614766 Title: ovsdb managers shouldn't be erased/overwritten Status in neutron: Fix Released Bug description: neutron(ovs or dhcp) agent with native ovslib sets to its own ovsdb managers. In some use cases, cloud admin sets ovsdb managers. e.g. monitoring/debug purses, sdn controller. neutron agents shouldn't erase those settings. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1614766/+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 1645306] [NEW] typo in api-paste.ini parameter
Public bug reported: Following line uses "olso_config_project" https://github.com/openstack/nova/blame/f57cc519fde2f177920ce88b8a3ef0618d1419b0/nova/api/openstack/placement/deploy.py#L42 it should be oslo_config_project https://github.com/openstack/nova/blob/f57cc519fde2f177920ce88b8a3ef0618d1419b0/etc/nova/api-paste.ini#L75 ** Affects: nova Importance: Undecided Assignee: Atsushi SAKAI (sakaia) Status: New ** Changed in: nova Assignee: (unassigned) => Atsushi SAKAI (sakaia) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1645306 Title: typo in api-paste.ini parameter Status in OpenStack Compute (nova): New Bug description: Following line uses "olso_config_project" https://github.com/openstack/nova/blame/f57cc519fde2f177920ce88b8a3ef0618d1419b0/nova/api/openstack/placement/deploy.py#L42 it should be oslo_config_project https://github.com/openstack/nova/blob/f57cc519fde2f177920ce88b8a3ef0618d1419b0/etc/nova/api-paste.ini#L75 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1645306/+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 1643080] Re: horizon dashboard can't be loaded properly ASN1 undefined
Please update to latest; I believe this is fixed. It's not terribly helpful reporting bugs from a master branch that is over one month old. ** Changed in: horizon Status: New => Won't Fix -- 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/1643080 Title: horizon dashboard can't be loaded properly ASN1 undefined Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: Uncaught ReferenceError: ASN1 is not defined at fc3281fe5592.js:6115 10.0.10.10/:58 Uncaught TypeError: Cannot set property 'languageCode' of undefined at 10.0.10.10/:58 at 10.0.10.10/:81 e9822d1af741.js:32 Uncaught TypeError: Cannot set property 'string' of undefined at e9822d1af741.js:32 fc3281fe5592.js:818 Uncaught Error: [$injector:nomod] Module 'horizon.app' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument. I am using the master branch on 10/17/2016 There is no Login button on login page, no Cancel button in modal windows and can't select item from drop down list. All those pages have the error above in the browser console. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1643080/+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 1643849] Re: The result of 'qos-minimum-bandwidth-rule-list' is wrong
This looks like it might be a client bug, but I would like someone to confirm if it's that or the API response. ** Tags added: qos ** Also affects: python-neutronclient Importance: Undecided Status: New ** Changed in: python-neutronclient Status: New => Triaged ** Changed in: neutron Status: New => Triaged ** Changed in: neutron Importance: Undecided => High ** Changed in: python-neutronclient Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1643849 Title: The result of 'qos-minimum-bandwidth-rule-list' is wrong Status in neutron: Triaged Status in python-neutronclient: Triaged Bug description: In master branch,I have a policy,and some rules in it as folloss: [root@devstack162 devstack]# neutron qos-policy-show p1 +-++ | Field | Value | +-++ | created_at | 2016-11-22T07:11:02Z | | description | a | | id | d296046b-0a87-496f-93dc-14e8bd5ed638 | | name| p1 | | project_id | 9a5b27e4da8b4aec99df42b222a8a696 | | revision_number | 5 | | rules | 7ba69c66-6911-4176-895d-f5668cc5bbbe (type: bandwidth_limit) | | | d9c021d5-5433-4d7c-8bfa-69cca486aac8 (type: dscp_marking) | | | 8c8fc4de-25c5-4d16-85e6-543d0affe916 (type: minimum_bandwidth) | | shared | False | | tenant_id | 9a5b27e4da8b4aec99df42b222a8a696 | | updated_at | 2016-11-22T11:07:47Z | +-++ and the command result of 'qos-bandwidth-limit-rule-list' is: [root@devstack162 devstack]# neutron qos-bandwidth-limit-rule-list p1 +--++--+ | id | max_burst_kbps | max_kbps | +--++--+ | 7ba69c66-6911-4176-895d-f5668cc5bbbe | 50 |1 | but the command result of 'qos-minimum-bandwidth-rule-list' is: [root@devstack162 devstack]# neutron qos-minimum-bandwidth-rule-list p1 'qos_minimum_bandwidth_rules' I think the result of 'qos-minimum-bandwidth-rule-lis' is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1643849/+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 1641753] Re: Feature support matrix should list support for force-completing a live migration
Reviewed: https://review.openstack.org/397871 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2992f9c00615a29332768100c940443c37451ae Submitter: Jenkins Branch:master commit f2992f9c00615a29332768100c940443c37451ae Author: int32bit Date: Wed Nov 16 02:06:17 2016 +0800 List support for force-completing a live migration in Feature support matrix Change-Id: I0aedc23b8fed2fe6b60088f8ff131b3fa31b974c Closes-Bug: #1641753 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1641753 Title: Feature support matrix should list support for force-completing a live migration Status in OpenStack Compute (nova): Fix Released Bug description: The feature support matrix has a section for virt drivers that support live migration: http://docs.openstack.org/developer/nova/support- matrix.html#operation_live_migrate But the 2.22 microversion added support for forcefully completing a live migration: http://docs.openstack.org/developer/nova/api_microversion_history.html#id20 However, that's currently only supported by the libvirt driver, and even then only in certain cases, like libvirt>=1.3.3, qemu>=2.5.0, and the VIR_MIGRATE_POSTCOPY flag must be set. We should, however, document that this is at least an operation people can try to perform via the REST API and describe what it does and which virt drivers support it. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1641753/+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 1645272] [NEW] Hostname of server is not updated
Public bug reported: 1. create a server with name 'old' 2. update the name of server to 'new' 3. get the details of server from nova, the name has been updated 4. restart (stop and then start)/reboot the nova server 5. login the server, and found the hostname has not been udpate to 'new' ** Affects: nova Importance: Undecided Assignee: huangtianhua (huangtianhua) Status: New ** Changed in: nova Assignee: (unassigned) => huangtianhua (huangtianhua) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1645272 Title: Hostname of server is not updated Status in OpenStack Compute (nova): New Bug description: 1. create a server with name 'old' 2. update the name of server to 'new' 3. get the details of server from nova, the name has been updated 4. restart (stop and then start)/reboot the nova server 5. login the server, and found the hostname has not been udpate to 'new' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1645272/+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 1645263] Re: Unable to run stack.sh on fresh new Ubuntu Xenial 16.04 LTS, script fails with "No module named 'memcache' "
Python3 package for memcache has different name from Python2 package: https://pypi.python.org/pypi/python3-memcached Python2 package: https://pypi.python.org/pypi/python-memcached This is also a problem for: https://bitbucket.org/zzzeek/dogpile.cache And subsequently for Keystone running under Python-3.5.2 with memcached ** Also affects: keystone Importance: Undecided Status: New ** Also affects: openstack-requirements Importance: Undecided Status: New -- 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/1645263 Title: Unable to run stack.sh on fresh new Ubuntu Xenial 16.04 LTS, script fails with "No module named 'memcache' " Status in devstack: New Status in OpenStack Identity (keystone): New Status in OpenStack Global Requirements: New Bug description: Unable to run stack.sh on fresh new Ubuntu Xenial 16.04 LTS, script fails with "No module named 'memcache' " Traceback: +lib/keystone:bootstrap_keystone:630 /usr/local/bin/keystone-manage bootstrap --bootstrap-username admin --bootstrap-password ubuntu --bootstrap-project-name admin --bootstrap-role-name admin --bootstrap-service-name keystone --bootstrap-region-id RegionOne --bootstrap-admin-url http://192.168.0.115/identity_admin --bootstrap-public-url http://192.168.0.115/identity --bootstrap-internal-url http://192.168.0.115/identity 2016-11-28 11:51:39.723 15663 CRITICAL keystone [-] ImportError: No module named 'memcache' 2016-11-28 11:51:39.723 15663 TRACE keystone Traceback (most recent call last): 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/bin/keystone-manage", line 10, in 2016-11-28 11:51:39.723 15663 TRACE keystone sys.exit(main()) 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/cmd/manage.py", line 45, in main 2016-11-28 11:51:39.723 15663 TRACE keystone cli.main(argv=sys.argv, config_files=config_files) 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/cmd/cli.py", line 1269, in main 2016-11-28 11:51:39.723 15663 TRACE keystone CONF.command.cmd_class.main() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/cmd/cli.py", line 365, in main 2016-11-28 11:51:39.723 15663 TRACE keystone klass = cls() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/cmd/cli.py", line 66, in __init__ 2016-11-28 11:51:39.723 15663 TRACE keystone self.load_backends() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/cmd/cli.py", line 129, in load_backends 2016-11-28 11:51:39.723 15663 TRACE keystone drivers = backends.load_backends() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/server/backends.py", line 32, in load_backends 2016-11-28 11:51:39.723 15663 TRACE keystone cache.configure_cache() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/opt/stack/keystone/keystone/common/cache/core.py", line 124, in configure_cache 2016-11-28 11:51:39.723 15663 TRACE keystone cache.configure_cache_region(CONF, region) 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/oslo_cache/core.py", line 201, in configure_cache_region 2016-11-28 11:51:39.723 15663 TRACE keystone '%s.' % conf.cache.config_prefix) 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/region.py", line 552, in configure_from_config 2016-11-28 11:51:39.723 15663 TRACE keystone "%swrap" % prefix, None), 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/region.py", line 417, in configure 2016-11-28 11:51:39.723 15663 TRACE keystone _config_prefix 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/api.py", line 81, in from_config_dict 2016-11-28 11:51:39.723 15663 TRACE keystone for key in config_dict 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/backends/memcached.py", line 208, in __init__ 2016-11-28 11:51:39.723 15663 TRACE keystone super(MemcacheArgs, self).__init__(arguments) 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/backends/memcached.py", line 108, in __init__ 2016-11-28 11:51:39.723 15663 TRACE keystone self._imports() 2016-11-28 11:51:39.723 15663 TRACE keystone File "/usr/local/lib/python3.5/dist-packages/dogpile/cache/backends/memcached.py", line 287, in _imports 2016-11-28 11:51:39.723 15663 TRACE keystone import memcache # noqa 2016-11-28 11:51:39.723 15663 TRACE keystone ImportError: No module named 'memcache' 2016-11-
[Yahoo-eng-team] [Bug 1644697] Re: run_tests.sh should really use upper-constraints
Reviewed: https://review.openstack.org/402291 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a909ed26c2aa6daf2c5fc59a2f575a66cdddbfb5 Submitter: Jenkins Branch:master commit a909ed26c2aa6daf2c5fc59a2f575a66cdddbfb5 Author: Tony Breeds Date: Fri Nov 25 15:48:35 2016 +1100 Add constraints support to run_tests.sh Currently developers need to manually build a constratined venv if they want to match the versions that are tested in the gate. This change adds logic to run_tests.sh and install_venv*.py to default to the same constraints file used in the gate. With constraints enabled the 'churn' in the environment should be minimised so remove the developer optimisation for detecting when packaged versions change and always just install/update. This has the down side of making the script preamble slightly longer but we always print_help() so I don't think it'll be terribly inconvenient. Change-Id: I9bf85adb5aa2c85d8c0f0f22ac9efe5cac3646c0 Closes-Bug: 1644697 ** Changed in: horizon Status: In Progress => Fix Released -- 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/1644697 Title: run_tests.sh should really use upper-constraints Status in OpenStack Dashboard (Horizon): Fix Released Bug description: We're starting to see lots of compatibility issues that will be solved if we have run_tests.sh support upper-constraints. This will not stop us from removing run_tests.sh in Queens, but will allow us avoid issues along the way and to test the changes now and backport to stable. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1644697/+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 1644709] Re: mox errors are not being treated as test failures
Reviewed: https://review.openstack.org/402303 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=f2eaafcc9c7ad5b7b1360446b7fe604ce4962b99 Submitter: Jenkins Branch:master commit f2eaafcc9c7ad5b7b1360446b7fe604ce4962b99 Author: Richard Jones Date: Fri Nov 25 16:58:42 2016 +1100 Fix mox trapped errors Some mox errors were being caught by a too-broad except clause Change-Id: I0352e231425b42456552e7cffd91722ccbb95055 Closes-Bug: 1644709 ** Changed in: horizon Status: In Progress => Fix Released -- 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/1644709 Title: mox errors are not being treated as test failures Status in OpenStack Dashboard (Horizon): Fix Released Bug description: There are some mox errors in test output that should be causing test runs to fail but are not. For example: http://logs.openstack.org/25/222825/28/check/gate-horizon-python27 -ubuntu-xenial/15d5669/console.html#_2016-11-25_01_46_56_495148 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1644709/+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 1644280] Re: duplicate "project id" printed in network objects creation
Hi Alex, This does not seem to be a neutron issue, but more of an openstackclient issue. Besides, can you provide some more details as to which commit tag you verified this ? I cannot find this issue with openstackclient+neutron newton version ** Project changed: neutron => python-openstackclient ** Changed in: python-openstackclient Status: New => Incomplete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1644280 Title: duplicate "project id" printed in network objects creation Status in python-openstackclient: Incomplete Bug description: Newton(ospd10)- [stack@undercloud-0 ~]$ openstack network create int_net_parent +---+--+ | Field | Value| +---+--+ | admin_state_up| UP | | availability_zone_hints | | | availability_zones| | | created_at| 2016-11-23T15:52:07Z | | description | | | headers | | | id| f235bee9-b6b7-4d83-954a-c1a205750777 | | ipv4_address_scope| None | | ipv6_address_scope| None | | mtu | 1446 | | name | int_net_parent | | port_security_enabled | True | | project_id| 2ea92674ed75445c865b0a932664656b |<<< | project_id| 2ea92674ed75445c865b0a932664656b |<<< | provider:network_type | vxlan| | provider:physical_network | None | | provider:segmentation_id | 97 | | qos_policy_id | None | | revision_number | 3| | router:external | Internal | | shared| False| | status| ACTIVE | | subnets | | | tags | [] | | updated_at| 2016-11-23T15:52:07Z | +---+--+ [stack@undercloud-0 ~]$ openstack subnet create int_sub_parent --network int_net_parent --subnet-range 192.168.0.0/24 --dns-nameserver 10.35.28.28 +---+--+ | Field | Value| +---+--+ | allocation_pools | 192.168.0.2-192.168.0.254| | cidr | 192.168.0.0/24 | | created_at| 2016-11-23T15:52:13Z | | description | | | dns_nameservers | 10.35.28.28 | | enable_dhcp | True | | gateway_ip| 192.168.0.1 | | headers | | | host_routes | | | id| 7564921e-dcc9-4c5e-8ec7-b5a25932b679 | | ip_version| 4| | ipv6_address_mode | None | | ipv6_ra_mode | None | | name | int_sub_parent | | network_id| f235bee9-b6b7-4d83-954a-c1a205750777 | | project_id| 2ea92674ed75445c865b0a932664656b |<<< | project_id| 2ea92674ed75445c865b0a932664656b |<<< | revision_number | 2| | service_types | [] | | subnetpool_id | None | | updated_at| 2016-11-23T15:52:13Z | +---+--+ After showing the created object we see the project-id line only once. Does not happen when we use "neutron net-create"/"neutron port-create", happens only when we use " openstack network create" etc . BR To manage notifications about this bug go to: https://bugs.launchpad.net/python-openstackclient/+bug/1644280/+subscriptions -- Mailing list: https://launchpad.net/
