Ask Your Question

godfrey_tan2001's profile - activity

2019-06-25 08:36:17 -0500 received badge  Notable Question (source)
2019-04-28 05:38:54 -0500 received badge  Notable Question (source)
2019-04-28 05:38:54 -0500 received badge  Popular Question (source)
2019-04-13 02:18:27 -0500 received badge  Famous Question (source)
2019-04-13 02:18:27 -0500 received badge  Notable Question (source)
2019-03-14 02:59:38 -0500 answered a question Failed to connect to server (code: 1006) error

I have solved my own problem. Just configure these in /etc/nova/nova.conf file in Cluster Controller and Compute nodes.

eg on Compute-2 node

my_ip=192.168.1.136 [vnc] enabled=true server_listen=0.0.0.0 server_proxyclient_address=$my_ip novncproxy_base_url=http://192.168.1.133/vnc_auto.html novncproxy_host=0.0.0.0 novncproxy_port=6080

eg on Cluster Controller

my_ip=192.168.1.133 [vnc] enabled=true server_listen=0.0.0.0 server_proxyclient_address=$my_ip novncproxy_base_url=http://192.168.1.133/vnc_auto.html novncproxy_host=0.0.0.0 novncproxy_port=6080

2019-03-14 01:36:57 -0500 answered a question Nova VNC works, but not in Dashboard

Hi here are my configs:

eg on Compute-2 node

my_ip=192,168.1.136 [vnc] enabled=true server_listen=0.0.0.0 server_proxyclient_address=$my_ip novncproxy_base_url=http://192.168.1.133/vnc_auto.html novncproxy_host=0.0.0.0 novncproxy_port = 6080# eg on Cluster Controller

eg on Cluster Controller

my_ip=192.168.1.133 [vnc] enabled=true server_listen=0.0.0.0 server_proxyclient_address=$my_ip novncproxy_base_url=http://192.168.1.133/vnc_auto.html novncproxy_host=0.0.0.0 novncproxy_port = 6080

2019-03-14 00:34:41 -0500 commented answer Nova instance console error: Failed to connect to server (code: 1006)

Hi,

I tried the above. Didn't work for me.

2019-03-13 08:05:39 -0500 received badge  Popular Question (source)
2019-02-18 02:39:50 -0500 received badge  Famous Question (source)
2019-02-15 02:52:45 -0500 asked a question Failed to connect to server (code: 1006) error

Hi,

These are the values in nova.conf file for vnc in Controller node:

server_listen=127.0.0.1

server_proxyclient_address=127.0.0.1

novncproxy_base_url=http://192.168.1.133:6080/vnc_auto.html

xvpvncproxy_host=0.0.0.0

novncproxy_host=0.0.0.0

This is the error message: 2019-02-15 03:29:10.013 20039 INFO nova.console.websocketproxy [-] 192.168.1.8 - - [15/Feb/2019 03:29:10] 192.168.1.8: Plain non-SSL (ws://) WebSocket connection 2019-02-15 03:29:10.014 20039 INFO nova.console.websocketproxy [-] 192.168.1.8 - - [15/Feb/2019 03:29:10] 192.168.1.8: Version hybi-13, base64: 'False' 2019-02-15 03:29:10.014 20039 INFO nova.console.websocketproxy [-] 192.168.1.8 - - [15/Feb/2019 03:29:10] 192.168.1.8: Path: '/websockify' 2019-02-15 03:29:10.204 20039 INFO nova.console.websocketproxy [req-17dadbc5-780b-4dfb-ba94-0c0f149d1119 - - - - -] 2: connect info: {u'instance_uuid': u'9ac7fe8c-c77c-48cb-a199-6849126bc5dd', u'internal_access_path': None, u'last_activity_at': 1550219349.753975, u'console_type': u'novnc', u'host': u'queens-compute-2.godfrey.com', u'token': u'ca199553-01fd-42ac-a3a5-0c1e0bdded83', u'access_url': u'http://192.168.1.133:6080/vnc_auto.html?token=ca199553-01fd-42ac-a3a5-0c1e0bdded83', u'port': u'-1'} 2019-02-15 03:29:10.205 20039 INFO nova.console.websocketproxy [req-17dadbc5-780b-4dfb-ba94-0c0f149d1119 - - - - -] 2: connecting to: queens-compute-2.godfrey.com:-1 2019-02-15 03:29:11.385 20039 INFO nova.console.websocketproxy [req-17dadbc5-780b-4dfb-ba94-0c0f149d1119 - - - - -] handler exception: [Errno -2] No address found

What do I need to set on the Controller and Compute nova.conf file to resolve this?

2019-02-14 04:36:53 -0500 commented question cirros instance can't connect to Internet

Hi Bernd,

You may close the case. Problem solved by setting vSwitch in ESXi with Promiscuous mode, MAC address changes and Forge transmits enabled.

Was not Openstack problem. Thank for the help.

2019-02-13 02:28:18 -0500 received badge  Popular Question (source)
2019-02-13 02:04:00 -0500 commented question cirros instance can't connect to Internet

Hi Bernd,

I have removed the OVN settings. Still no progress.

2019-02-12 07:46:25 -0500 commented question cirros instance can't connect to Internet

Hi Bernd,

Yes correct that I can ping the instance floating IP but not out of it. Ok let me try removing the OVN settings and I will let you know.

2019-02-12 02:45:04 -0500 commented question cirros instance can't connect to Internet

Hi Bernd,

I have followed the steps in the link you send. Same result.

2019-02-12 00:40:47 -0500 commented question cirros instance can't connect to Internet

Hi Bernd,

What would the variable in the answerfile?

I have this in the answerfile already: "CONFIG_NEUTRON_OVN_BRIDGE_MAPPINGS=extnet:br-ex" "CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=extnet:br-ex" "CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-ex:ens192" "CONFIG_NEUTRON_OVN_BRIDGE_IFACES=". This is empty.

2019-02-11 23:47:34 -0500 commented question cirros instance can't connect to Internet

Btw, I can ping the cirros floating ip from centos also. Doing ping 8.8.8.8 just freezes and does nothing. I created cirros2 and both cirros vms' can ping each others IP address and the IP address of br-ex.

2019-02-11 23:46:57 -0500 asked a question cirros instance can't connect to Internet

Hi,

I have all-in-one setup.

br-ex is on 192.168.1.133 and bridge to ethernet interface ens192. I can ping to Internet from centos but can't from the cirros instance. Cirros has floating ip 192.168.1.23 and IP of 172.16.1.4. Virtual router has been created connecting public and mgmt subnet on which Cirros sits.

These are the answer file values.

Connect br-ex to ethernet interfaces

CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-ex:ens192

CIDR network address for the floating IP subnet.

CONFIG_PROVISION_DEMO_FLOATRANGE=192.168.1.0/24

CIDR network address for the floating IP subnet.

CONFIG_PROVISION_TEMPEST_FLOATRANGE=172.24.4.0/24

Anything I have missed?

2019-01-24 00:38:10 -0500 commented answer Instance launch error

Hi Bernd,

Thank you for the instructions in the link. All I had to do was to execute "su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova" on the Cluster Controller and solved the problem. You can close the case.

2019-01-21 02:36:59 -0500 received badge  Editor (source)
2019-01-21 02:27:23 -0500 asked a question Instance launch error

Hi,

I got this error trying to launch a cirros instance in Openstack. "Error: Failed to perform requested operation on instance "cirros", the instance has an error status: Please try again later [Error: Host 'queens-compute-1.godfrey.com' is not mapped to any cell]".

I have queens-compute-1 and queens-compute-2 as host aggregates in nova availability zone.

What is the issue?

2019-01-16 22:50:31 -0500 commented question Multinode Install Problem with Packstack Centos

So its all good now. Do close the case. Thank so much for the support.

2019-01-16 22:49:47 -0500 commented question Multinode Install Problem with Packstack Centos

Hi Bernd,

I edited the /etc/hosts and /etc/sysconfig/network to include hostname and ip address for the compute nodes 1 & 2. I re-installed packstack in a clean centos and configured the answer file. My compute nodes are showing up in "Host Aggregates" with the respective compute nodes IP address

2019-01-16 01:49:43 -0500 commented question Multinode Install Problem with Packstack Centos

I can't see my compute nodes 1 & 2. Fails during applying puppet manifests during packstack installation.

2019-01-16 01:49:14 -0500 commented question Multinode Install Problem with Packstack Centos

Hi Bernd,

I got this problem after running packstack again: Jan 16 15:33:25 localhost.localdomain systemd[1]: openstack-nova-compute.service failed. ^[[0m ^[[mNotice: /Stage[main]/Nova::Deps/Anchor[nova::service::end]: Dependency Service[nova-compute] has failures: true^[[0m ^[[1;33mWarning: /Stage

2019-01-16 01:48:23 -0500 commented question Multinode Install Problem with Packstack Centos

Hi Bernd,

The compute node could not access DNS because DNS was not configure in ifcfg-ens192 interface.

2019-01-15 23:10:11 -0500 commented question Multinode Install Problem with Packstack Centos

Hi Bernd,

I resolved the issue. Thank you. You can close the case.

2019-01-15 22:35:30 -0500 commented question Multinode Install Problem with Packstack Centos

Hi Bernd,

Strange, I do have Internet and can now ping to http://mirrorlist.centos.org but when I run packstack again, I get the same error.

2019-01-15 22:28:25 -0500 commented question Multinode Install Problem with Packstack Centos

Hi Bernd,

I can ping http://yahoo.com but not http://mirrorlist.centos.org. So its either down or moved to another url, but thank you for the comment.

2019-01-15 21:58:16 -0500 asked a question Multinode Install Problem with Packstack Centos

Hi, I got this error below trying to install compute-1 and compute-2 with Packstack. Packstack All-in-One is no problem. Error Message: Pre installing Puppet and discovering hosts' details[ ERROR ]

ERROR : Failed to run remote script, stdout: Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock (http://mirrorlist.centos.org/?release...) error was 14: curl#6 - "Could not resolve host: http://mirrorlist.centos.org; Unknown error"

stderr: Warning: Permanently added '192.168.1.136' (ECDSA) to the list of known hosts. + trap t ERR + yum install -y puppet hiera openssh-clients tar nc rubygem-json

One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=<repoid> ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable <repoid>
    or
        subscription-manager repos --disable=<repoid>

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64 ++ t ++ exit 1 How to resolve this?

2019-01-15 03:26:38 -0500 commented question Multinode local.conf Configuration

Hi Bernd,

Yes your assumption is correct. Already working. Thank you. You can close the case.

2019-01-15 03:25:34 -0500 received badge  Popular Question (source)
2019-01-15 00:11:27 -0500 commented question Multinode local.conf Configuration

Hi Bernd,

Thank you the local.conf works from your mentioned link. However, he public IP address range is 172.24.4/0. br-ex takes the value of 172.24.4.1. What statements are need so that the public IP address range is 192.168.1.0/24, floating_ip range = 192.168.1.20~29 and br-ex=192.168.1.19?

2019-01-14 02:29:32 -0500 commented question Multinode local.conf Configuration

Btw, I want br-ex to take an IP address with DHCP from my router in 192.168.1./0/24 or a fixed IP address that I can specify. After running stack.sh, I can't ping my router at 192.168.1.254 also.

2019-01-14 02:29:32 -0500 received badge  Commentator
2019-01-14 02:27:08 -0500 commented question Multinode local.conf Configuration

Sorry forgot to describe the problem. I can't ping my compute nodes 192.168.1.137 and 192.168.139 after running ./stack.sh. Also br-ex take 192.168.1.1 from the floating range of 192.168.1.0/24. I also want to be able to access the login page at 192.168.1.135 which I can't also.

2019-01-14 01:12:03 -0500 asked a question Multinode local.conf Configuration

Hi,

My host_ip=192.168.1.135 and my compute nodes are 192.168.1.137 & 139. This is my local.conf:

[[local|localrc]]
HOST_IP=192.168.1.135
FLAT_INTERFACE=ens192
FIXED_RANGE=10.4.128.0/20
FIXED_NETWORK_SIZE=4096
FLOATING_RANGE=192.168.1.0/24
Q_FLOATING_ALLOCATION_POOL=start=192.168.1.20,end=192.168.1.29
#PUBLIC_NETWORK_GATEWAY=192.168.1.19
Q_USE_PROVIDERNET_FOR_PUBLIC=true
OVS_PHYSICAL_BRIDGE=br-ex
PUBLIC_BRIDGE=br-ex
OVS_BRIDGE_MAPPINGS=public:br-ex
MULTI_HOST=1
LOGFILE=/opt/stack/logs/stack.sh.log
ADMIN_PASSWORD=devstack
DATABASE_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD
SERVICE_PASSWORD=$ADMIN_PASSWORD

I can ping my compute nodes after running stack.sh. What is wrong? Thank you.

2019-01-11 00:48:37 -0500 received badge  Famous Question (source)
2019-01-08 22:38:02 -0500 received badge  Enthusiast