[Yahoo-eng-team] [Bug 1514070] Re: network_data.json does not provide information about all ip addresses on nics.
Not a bug. Fixed by changing nova.conf [DEFAULT] use_ipv6=true ** Changed in: nova Status: New => 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/1514070 Title: network_data.json does not provide information about all ip addresses on nics. Status in OpenStack Compute (nova): Invalid Bug description: Environment: centos 7 openstack liberty # rpm -qa|grep nova openstack-nova-api-12.0.0-1.el7.noarch python-novaclient-2.30.1-1.el7.noarch openstack-nova-novncproxy-12.0.0-1.el7.noarch openstack-nova-conductor-12.0.0-1.el7.noarch python-nova-12.0.0-1.el7.noarch openstack-nova-console-12.0.0-1.el7.noarch openstack-nova-common-12.0.0-1.el7.noarch openstack-nova-compute-12.0.0-1.el7.noarch openstack-nova-cert-12.0.0-1.el7.noarch openstack-nova-scheduler-12.0.0-1.el7.noarch Network configuration: # neutron net-list +--+--+---+ | id | name | subnets | +--+--+---+ | 286b3e3c-9075-496f-8899-c9890397f087 | net2 | 0a9ff171-0455-459e-b3c6-486ab90ba83d 10.0.1.0/24 | | | | de602f61-8e05-4337-bc9d-c9f8265bb937 1000:2000::/24 | | a3931414-73c3-40c9-a39b-d93ae38844a2 | net3 | b6ce48ab-9387-4128-baa3-4a893dd27bb7 10.0.2.0/24 | | a5d1181f-bedd-40a5-8b4a-5574b74dba61 | net1 | 72be780a-6df9-47ea-991c-e6fa97396adc 192.168.122.0/24 | +--+--+---+ Network net2 have two subnets. Created new instance: # nova boot \ --flavor 2 \ --image fedora23 \ --config-drive=True \ --nic net-id=a5d1181f-bedd-40a5-8b4a-5574b74dba61 \ --nic net-id=286b3e3c-9075-496f-8899-c9890397f087 \ --nic net-id=a3931414-73c3-40c9-a39b-d93ae38844a2 \ --user-data=/root/cloud-config \ test # nova list +--+--+++-+--+ | ID | Name | Status | Task State | Power State | Networks | +--+--+++-+--+ | d9d76e4b-62c8-4a84-9e4b-66481d303c83 | test | ACTIVE | - | Running | net3=10.0.2.115; net2=10.0.1.100, 1000:2000:3000::1101; net1=192.168.122.116 | +--+--+++-+--+ # nova show test +--+--+ | Property | Value | +--+--+ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | localhost.localdomain | | OS-EXT-SRV-ATTR:hypervisor_hostname | localhost.localdomain | | OS-EXT-SRV-ATTR:instance_name| instance-0012 | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2015-11-07T13:17:00.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | True | | created | 2015-11-07T13:16:50Z | | flavor | m1.small (2) | | hostId
[Yahoo-eng-team] [Bug 1514082] Re: network_data.json does not provide information about ipv6 addresses.
Sorry, not a bug.
Fixed by configure nova.conf:
[DEFAULT]
use_ipv6=true
** Changed in: nova
Status: New => 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/1514082
Title:
network_data.json does not provide information about ipv6 addresses.
Status in OpenStack Compute (nova):
Invalid
Bug description:
Environment:
centos 7
openstack liberty
# rpm -qa|grep nova
openstack-nova-api-12.0.0-1.el7.noarch
python-novaclient-2.30.1-1.el7.noarch
openstack-nova-novncproxy-12.0.0-1.el7.noarch
openstack-nova-conductor-12.0.0-1.el7.noarch
python-nova-12.0.0-1.el7.noarch
openstack-nova-console-12.0.0-1.el7.noarch
openstack-nova-common-12.0.0-1.el7.noarch
openstack-nova-compute-12.0.0-1.el7.noarch
openstack-nova-cert-12.0.0-1.el7.noarch
openstack-nova-scheduler-12.0.0-1.el7.noarch
Steps to reproduce:
1) Create network with ipv6 subnet.
# neutron net-list
+--+--+---+
| id | name | subnets
|
+--+--+---+
| 286b3e3c-9075-496f-8899-c9890397f087 | net2 |
de602f61-8e05-4337-bc9d-c9f8265bb937 1000:2000::/24 |
| a3931414-73c3-40c9-a39b-d93ae38844a2 | net3 |
b6ce48ab-9387-4128-baa3-4a893dd27bb7 10.0.2.0/24 |
| a5d1181f-bedd-40a5-8b4a-5574b74dba61 | net1 |
72be780a-6df9-47ea-991c-e6fa97396adc 192.168.122.0/24 |
+--+--+---+
2) Create instance with 3 nic
# nova boot \
--flavor 2 \
--image fedora23 \
--config-drive=True \
--nic net-id=a5d1181f-bedd-40a5-8b4a-5574b74dba61 \
--nic net-id=286b3e3c-9075-496f-8899-c9890397f087 \
--nic net-id=a3931414-73c3-40c9-a39b-d93ae38844a2 \
--user-data=/root/cloud-config \
test
# nova list
+--+--+++-+--+
| ID | Name | Status | Task State | Power
State | Networks |
+--+--+++-+--+
| 4f159a96-8154-4946-b2a3-50c2638f545b | test | ACTIVE | - | Running
| net3=10.0.2.116; net2=1000:2000:3000::1102; net1=192.168.122.117 |
+--+--+++-+--+
Logon to instance, mount configDrive:
# mount /dev/disk/by-label/config-2 /mnt/
Actual result:
# cat /mnt/openstack/latest/network_data.json | python3 -m json.tool
{
"links": [
{
"ethernet_mac_address": "fa:16:3e:db:48:10",
"id": "tap54d10236-5d",
"mtu": null,
"type": "ovs",
"vif_id": "54d10236-5d15-4e22-b584-2a185d74b553"
},
{
"ethernet_mac_address": "fa:16:3e:db:c2:96",
"id": "tapae9677cb-32",
"mtu": null,
"type": "ovs",
"vif_id": "ae9677cb-327b-4fc9-9b99-88ebd96595a3"
},
{
"ethernet_mac_address": "fa:16:3e:10:37:07",
"id": "tap1baef501-47",
"mtu": null,
"type": "ovs",
"vif_id": "1baef501-47b0-4c76-928f-34ed2827c7d4"
}
],
"networks": [
{
"id": "network0",
"link": "tap54d10236-5d",
"network_id": "a5d1181f-bedd-40a5-8b4a-5574b74dba61",
"type": "ipv4_dhcp"
},
{
"id": "network1",
"ip_address": "10.0.2.116",
"link": "tap1baef501-47",
"netmask": "255.255.255.0",
"network_id": "a3931414-73c3-40c9-a39b-d93ae38844a2",
"routes": [],
"type": "ipv4"
}
],
"services": []
}
network_data.json provide information about ipv4 adresses only.
Expected result:
network_data.json provide information about all ip adresses.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1514082/+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 1514082] [NEW] network_data.json does not provide information about ipv6 addresses.
Public bug reported:
Environment:
centos 7
openstack liberty
# rpm -qa|grep nova
openstack-nova-api-12.0.0-1.el7.noarch
python-novaclient-2.30.1-1.el7.noarch
openstack-nova-novncproxy-12.0.0-1.el7.noarch
openstack-nova-conductor-12.0.0-1.el7.noarch
python-nova-12.0.0-1.el7.noarch
openstack-nova-console-12.0.0-1.el7.noarch
openstack-nova-common-12.0.0-1.el7.noarch
openstack-nova-compute-12.0.0-1.el7.noarch
openstack-nova-cert-12.0.0-1.el7.noarch
openstack-nova-scheduler-12.0.0-1.el7.noarch
Steps to reproduce:
1) Create network with ipv6 subnet.
# neutron net-list
+--+--+---+
| id | name | subnets
|
+--+--+---+
| 286b3e3c-9075-496f-8899-c9890397f087 | net2 |
de602f61-8e05-4337-bc9d-c9f8265bb937 1000:2000::/24 |
| a3931414-73c3-40c9-a39b-d93ae38844a2 | net3 |
b6ce48ab-9387-4128-baa3-4a893dd27bb7 10.0.2.0/24 |
| a5d1181f-bedd-40a5-8b4a-5574b74dba61 | net1 |
72be780a-6df9-47ea-991c-e6fa97396adc 192.168.122.0/24 |
+--+--+---+
2) Create instance with 3 nic
# nova boot \
--flavor 2 \
--image fedora23 \
--config-drive=True \
--nic net-id=a5d1181f-bedd-40a5-8b4a-5574b74dba61 \
--nic net-id=286b3e3c-9075-496f-8899-c9890397f087 \
--nic net-id=a3931414-73c3-40c9-a39b-d93ae38844a2 \
--user-data=/root/cloud-config \
test
# nova list
+--+--+++-+--+
| ID | Name | Status | Task State | Power
State | Networks |
+--+--+++-+--+
| 4f159a96-8154-4946-b2a3-50c2638f545b | test | ACTIVE | - | Running
| net3=10.0.2.116; net2=1000:2000:3000::1102; net1=192.168.122.117 |
+--+--+++-+--+
Logon to instance, mount configDrive:
# mount /dev/disk/by-label/config-2 /mnt/
Actual result:
# cat /mnt/openstack/latest/network_data.json | python3 -m json.tool
{
"links": [
{
"ethernet_mac_address": "fa:16:3e:db:48:10",
"id": "tap54d10236-5d",
"mtu": null,
"type": "ovs",
"vif_id": "54d10236-5d15-4e22-b584-2a185d74b553"
},
{
"ethernet_mac_address": "fa:16:3e:db:c2:96",
"id": "tapae9677cb-32",
"mtu": null,
"type": "ovs",
"vif_id": "ae9677cb-327b-4fc9-9b99-88ebd96595a3"
},
{
"ethernet_mac_address": "fa:16:3e:10:37:07",
"id": "tap1baef501-47",
"mtu": null,
"type": "ovs",
"vif_id": "1baef501-47b0-4c76-928f-34ed2827c7d4"
}
],
"networks": [
{
"id": "network0",
"link": "tap54d10236-5d",
"network_id": "a5d1181f-bedd-40a5-8b4a-5574b74dba61",
"type": "ipv4_dhcp"
},
{
"id": "network1",
"ip_address": "10.0.2.116",
"link": "tap1baef501-47",
"netmask": "255.255.255.0",
"network_id": "a3931414-73c3-40c9-a39b-d93ae38844a2",
"routes": [],
"type": "ipv4"
}
],
"services": []
}
network_data.json provide information about ipv4 adresses only.
Expected result:
network_data.json provide information about all ip adresses.
** Affects: nova
Importance: Undecided
Status: New
** Tags: metadata
--
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/1514082
Title:
network_data.json does not provide information about ipv6 addresses.
Status in OpenStack Compute (nova):
New
Bug description:
Environment:
centos 7
openstack liberty
# rpm -qa|grep nova
openstack-nova-api-12.0.0-1.el7.noarch
python-novaclient-2.30.1-1.el7.noarch
openstack-nova-novncproxy-12.0.0-1.el7.noarch
openstack-nova-conductor-12.0.0-1.el7.noarch
python-nova-12.0.0-1.el7.noarch
openstack-nova-console-12.0.0-1.el7.noarch
openstack-nova-common-12.0.0-1.el7.noarch
openstack-nova-compute-12.0.0-1.el7.noarch
openstack-nova-cert-12.0.0-1.el7.noarch
openstack-nova-scheduler-12.0.0-1.el7.noarch
Steps to reproduce:
1) Create network with ipv6 subnet.
# neutron net-list
+-
[Yahoo-eng-team] [Bug 1514070] [NEW] network_data.json does not provide information about all ip addresses on nics.
Public bug reported:
Environment:
centos 7
openstack liberty
# rpm -qa|grep nova
openstack-nova-api-12.0.0-1.el7.noarch
python-novaclient-2.30.1-1.el7.noarch
openstack-nova-novncproxy-12.0.0-1.el7.noarch
openstack-nova-conductor-12.0.0-1.el7.noarch
python-nova-12.0.0-1.el7.noarch
openstack-nova-console-12.0.0-1.el7.noarch
openstack-nova-common-12.0.0-1.el7.noarch
openstack-nova-compute-12.0.0-1.el7.noarch
openstack-nova-cert-12.0.0-1.el7.noarch
openstack-nova-scheduler-12.0.0-1.el7.noarch
Network configuration:
# neutron net-list
+--+--+---+
| id | name | subnets
|
+--+--+---+
| 286b3e3c-9075-496f-8899-c9890397f087 | net2 |
0a9ff171-0455-459e-b3c6-486ab90ba83d 10.0.1.0/24 |
| | |
de602f61-8e05-4337-bc9d-c9f8265bb937 1000:2000::/24 |
| a3931414-73c3-40c9-a39b-d93ae38844a2 | net3 |
b6ce48ab-9387-4128-baa3-4a893dd27bb7 10.0.2.0/24 |
| a5d1181f-bedd-40a5-8b4a-5574b74dba61 | net1 |
72be780a-6df9-47ea-991c-e6fa97396adc 192.168.122.0/24 |
+--+--+---+
Network net2 have two subnets.
Created new instance:
# nova boot \
--flavor 2 \
--image fedora23 \
--config-drive=True \
--nic net-id=a5d1181f-bedd-40a5-8b4a-5574b74dba61 \
--nic net-id=286b3e3c-9075-496f-8899-c9890397f087 \
--nic net-id=a3931414-73c3-40c9-a39b-d93ae38844a2 \
--user-data=/root/cloud-config \
test
# nova list
+--+--+++-+--+
| ID | Name | Status | Task State | Power
State | Networks
|
+--+--+++-+--+
| d9d76e4b-62c8-4a84-9e4b-66481d303c83 | test | ACTIVE | - | Running
| net3=10.0.2.115; net2=10.0.1.100, 1000:2000:3000::1101;
net1=192.168.122.116 |
+--+--+++-+--+
# nova show test
+--+--+
| Property | Value
|
+--+--+
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | localhost.localdomain
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | localhost.localdomain
|
| OS-EXT-SRV-ATTR:instance_name| instance-0012
|
| OS-EXT-STS:power_state | 1
|
| OS-EXT-STS:task_state| -
|
| OS-EXT-STS:vm_state | active
|
| OS-SRV-USG:launched_at | 2015-11-07T13:17:00.00
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive | True
|
| created | 2015-11-07T13:16:50Z
|
| flavor | m1.small (2)
|
| hostId |
d8d01459db9617763612ca6ed08bea56d168bfeac10eb90dd21b0df0 |
| id | d9d76e4b-62c8-4a84-9e4b-66481d303c83
|
| image| fedora23
(54d9ba46-b4bb-4a39-ae9d-fc0f024d) |
| key_name | -
|
| metadata | {}
|
| name | test
[Yahoo-eng-team] [Bug 1514051] [NEW] Networking info (network_data.json) exist only into ConfigDrive if content is not empty.
Public bug reported:
Networking info (network_data.json) exist only into ConfigDrive if
content is not empty.
Blueprint: https://blueprints.launchpad.net/nova/+spec/metadata-service-
network-info
Environment:
centos 7
openstack liberty.
Steps to reproduce:
1. Up two instances:
# nova boot \
--flavor 2 \
--image fedora23 \
--config-drive=True \
--nic net-id=a5d1181f-bedd-40a5-8b4a-5574b74dba61 \
--nic net-id=286b3e3c-9075-496f-8899-c9890397f087 \
--nic net-id=a3931414-73c3-40c9-a39b-d93ae38844a2 \
--user-data=/root/cloud-config \
test
# nova boot \
--flavor 2 \
--image fedora23 \
--config-drive=True \
--nic net-id=a5d1181f-bedd-40a5-8b4a-5574b74dba61 \
--nic net-id=286b3e3c-9075-496f-8899-c9890397f087 \
--nic net-id=a3931414-73c3-40c9-a39b-d93ae38844a2 \
--user-data=/root/cloud-config \
--file test_file=test_file \
test2
Different between two calls - instance name (test and test2) and --file
parameter (for test2 instance).
Content of the test_file is:
test_file
Logon on two instances and exec on every instance:
# mount /dev/disk/by-label/config-2 /mnt
After it check files into the /mnt folder.
test instance:
# find /mnt
/mnt
/mnt/ec2
/mnt/ec2/2009-04-04
/mnt/ec2/2009-04-04/meta-data.json
/mnt/ec2/2009-04-04/user-data
/mnt/ec2/latest
/mnt/ec2/latest/meta-data.json
/mnt/ec2/latest/user-data
/mnt/openstack
/mnt/openstack/2012-08-10
/mnt/openstack/2012-08-10/meta_data.json
/mnt/openstack/2012-08-10/user_data
/mnt/openstack/2013-04-04
/mnt/openstack/2013-04-04/meta_data.json
/mnt/openstack/2013-04-04/user_data
/mnt/openstack/2013-10-17
/mnt/openstack/2013-10-17/meta_data.json
/mnt/openstack/2013-10-17/user_data
/mnt/openstack/2013-10-17/vendor_data.json
/mnt/openstack/2015-10-15
/mnt/openstack/2015-10-15/meta_data.json
/mnt/openstack/2015-10-15/user_data
/mnt/openstack/2015-10-15/vendor_data.json
/mnt/openstack/latest
/mnt/openstack/latest/meta_data.json
/mnt/openstack/latest/user_data
/mnt/openstack/latest/vendor_data.json
test2 instance:
# find /mnt
/mnt
/mnt/ec2
/mnt/ec2/2009-04-04
/mnt/ec2/2009-04-04/meta-data.json
/mnt/ec2/2009-04-04/user-data
/mnt/ec2/latest
/mnt/ec2/latest/meta-data.json
/mnt/ec2/latest/user-data
/mnt/openstack
/mnt/openstack/2012-08-10
/mnt/openstack/2012-08-10/meta_data.json
/mnt/openstack/2012-08-10/user_data
/mnt/openstack/2013-04-04
/mnt/openstack/2013-04-04/meta_data.json
/mnt/openstack/2013-04-04/user_data
/mnt/openstack/2013-10-17
/mnt/openstack/2013-10-17/meta_data.json
/mnt/openstack/2013-10-17/user_data
/mnt/openstack/2013-10-17/vendor_data.json
/mnt/openstack/2015-10-15
/mnt/openstack/2015-10-15/meta_data.json
/mnt/openstack/2015-10-15/user_data
/mnt/openstack/2015-10-15/vendor_data.json
/mnt/openstack/content
/mnt/openstack/content/
/mnt/openstack/latest
/mnt/openstack/latest/meta_data.json
/mnt/openstack/latest/network_data.json
/mnt/openstack/latest/user_data
/mnt/openstack/latest/vendor_data.json
Different between two instances: file /mnt/openstack/latest/network_data.json
and file /mnt/openstack/content/.
The file network_data.json exist into the test2 instance and does not exist
into the test instance.
How created ConfigDrive?
File /usr/lib/python2.7/site-packages/nova/api/metadata/base.py
446 def metadata_for_config_drive(self):
447 """Yields (path, value) tuples for metadata elements."""
...
479
480 for (cid, content) in six.iteritems(self.content):
481 if self._check_version(LIBERTY, version,
ALL_OPENSTACK_VERSIONS):
482 path = 'openstack/%s/%s' % (version, NW_JSON_NAME)
483 yield (path, self.lookup(path))
484
485 yield ('%s/%s/%s' % ("openstack", CONTENT_DIR, cid),
content)
For test instance self.content = {}
For test2 instance self.content = {'': 'test_file\n'}
If self.content is empty, NW_JSON_NAME will not be added to ConfigDrive.
Patch:
--- /tmp/base.py2015-11-07 08:16:06.98100 +
+++ /usr/lib/python2.7/site-packages/nova/api/metadata/base.py 2015-11-07
08:28:55.97200 +
@@ -477,11 +477,11 @@
path = 'openstack/%s/%s' % (version, VD_JSON_NAME)
yield (path, self.lookup(path))
-for (cid, content) in six.iteritems(self.content):
if self._check_version(LIBERTY, version, ALL_OPENSTACK_VERSIONS):
path = 'openstack/%s/%s' % (version, NW_JSON_NAME)
yield (path, self.lookup(path))
+for (cid, content) in six.iteritems(self.content):
yield ('%s/%s/%s' % ("openstack", CONTENT_DIR, cid), content)
Atfer patching:
Content of the ConfigDrive for test instance:
[root@test ~]# mount /dev/disk/by-label/config-2 /mnt
mount: /dev/sr0 is write-protected, mounting read-only
[root@test ~]# find /mnt
/mnt
/mnt/ec2
/mnt/ec2/2009-04-04
/mnt/ec2/2009-04-04/meta-data
[Yahoo-eng-team] [Bug 1426767] [NEW] On exec glance-api displayed exception "ImportError: No module named boto.exception".
Public bug reported: # pip list|grep glance glance (2015.1.dev40) glance-store (0.1.11) # /usr/bin/glance-api 2015-02-28 15:21:25.949 23107 ERROR stevedore.extension [-] Could not load 's3': No module named boto.exception 2015-02-28 15:21:25.950 23107 ERROR stevedore.extension [-] No module named boto.exception 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension Traceback (most recent call last): 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 162, in _load_plugins 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension verify_requirements, 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 185, in _load_one_plugin 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension plugin = ep.load(require=verify_requirements) 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2025, in load 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension entry = __import__(self.module_name, globals(),globals(), ['__name__']) 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/glance_store/_drivers/s3.py", line 26, in 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension import boto.exception 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension ImportError: No module named boto.exception 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension 2015-02-28 15:21:26.033 23107 ERROR stevedore.extension [-] Could not load 'glance.store.s3.Store': No module named boto.exception 2015-02-28 15:21:26.034 23107 ERROR stevedore.extension [-] No module named boto.exception 2015-02-28 15:21:26.034 23107 TRACE stevedore.extension Traceback (most recent call last): 2015-02-28 15:21:26.034 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 162, in _load_plugins 2015-02-28 15:21:26.034 23107 TRACE stevedore.extension verify_requirements, 2015-02-28 15:21:26.034 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 185, in _load_one_plugin 2015-02-28 15:21:26.034 23107 TRACE stevedore.extension plugin = ep.load(require=verify_requirements) 2015-02-28 15:21:26.034 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2025, in load 2015-02-28 15:21:26.034 23107 TRACE stevedore.extension entry = __import__(self.module_name, globals(),globals(), ['__name__']) 2015-02-28 15:21:26.034 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/glance_store/_drivers/s3.py", line 26, in 2015-02-28 15:21:26.034 23107 TRACE stevedore.extension import boto.exception 2015-02-28 15:21:26.034 23107 TRACE stevedore.extension ImportError: No module named boto.exception 2015-02-28 15:21:26.034 23107 TRACE stevedore.extension boto does not exist to glance_store requirements. After boto installation, issue was fixed. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1426767 Title: On exec glance-api displayed exception "ImportError: No module named boto.exception". Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: # pip list|grep glance glance (2015.1.dev40) glance-store (0.1.11) # /usr/bin/glance-api 2015-02-28 15:21:25.949 23107 ERROR stevedore.extension [-] Could not load 's3': No module named boto.exception 2015-02-28 15:21:25.950 23107 ERROR stevedore.extension [-] No module named boto.exception 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension Traceback (most recent call last): 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 162, in _load_plugins 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension verify_requirements, 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 185, in _load_one_plugin 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension plugin = ep.load(require=verify_requirements) 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2025, in load 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension entry = __import__(self.module_name, globals(),globals(), ['__name__']) 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension File "/usr/lib/python2.7/site-packages/glance_store/_drivers/s3.py", line 26, in 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension import boto.exception 2015-02-28 15:21:25.950 23107 TRACE stevedore.extension Impor
[Yahoo-eng-team] [Bug 1426704] [NEW] "Installing Keystone" document is outdated
Public bug reported: In the web page "Installing Keystone" (http://docs.openstack.org/developer/keystone/installing.html) topic 'Installing from packages: Fedora' is outdated: describe installation on Fedora 17 and provide links to Fedora wiki page with OpenStack Folsom installation. Fedora 17 is outdated (end of life date is 2013-07-30). Current version is Fedora 21. ** Affects: keystone Importance: Undecided Status: New ** Summary changed: - keystone installation documentation is outdated + "Installing Keystone" document is outdated -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1426704 Title: "Installing Keystone" document is outdated Status in OpenStack Identity (Keystone): New Bug description: In the web page "Installing Keystone" (http://docs.openstack.org/developer/keystone/installing.html) topic 'Installing from packages: Fedora' is outdated: describe installation on Fedora 17 and provide links to Fedora wiki page with OpenStack Folsom installation. Fedora 17 is outdated (end of life date is 2013-07-30). Current version is Fedora 21. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1426704/+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
